| Tool |
Description |
| 270/271
Batch Connectivity Specifications |
The purpose of this
document is to define the various parameters around using OpenSSH
on the public Internet to connect directly to participating payer
systems for transmission and receipt of the ANSI ASC X12N 270/271
Eligibility Inquiry and Response transaction. |
| 270/271
Real Time Connectivity Specifications |
The purpose of this
document is to define the various parameters around using HTTPS
(HTTP over SSL) on the public Internet to connect directly to
participating payer systems for transmission and receipt of the
ANSI ASC X12N 270/271 Eligibility Inquiry and Response
transaction. |
| 270/271
Search Parameters Detail |
The following is the
proposed framework for conducting an eligibility search by payers
when responding to 270 Eligibility transactions received from
providers, clearinghouses, and other sanctioned third-party
organizations. This framework identifies 6 unique scenarios -
endorsed by payers who are participating on the 270/271 Advanced
Eligibility project in the Minnesota community. |
Clearinghouse Role in
Testing |
The definition of a Clearinghouse and its role
in the testing process |
| Electronic
NPI Upload File high level process flow |
This document provides
an overview of the preparation, submission and error
reconciliation process between a submitter and receiver who choose
to use the ENUF for bulk Type 1 NPI notification. |
| Electronic
NPI Upload File Instructions |
This document describes
the various data elements contained in the Electronic NPI Upload
File (ENUF). ENUF is intended for bulk notification of Type 1 NPIs.
The ENUF would typically be generated by a provider organization
to notify the MN HIPAA Collaborative payers and providers of the
Type 1 NPIs their employed practitioners have received. The
purpose of this document is to define the specific data elements,
their attributes, whether they are required or optional, and
guidelines for using this notification process. |
| ENUF
XML Schema |
The XML schema documents
are available as a Microsoft Word document and as an .xsd file
that contains the XML structure for building the ENUF file. |
| Electronic
NPI Data Elements PDF document |
|
| How to Upload Your Test Files |
A PDF file that will walk you through the
testing process |
Recommended
Acceptance Testing Criteria |
This criteria defines what levels of test
quality are sufficient to move to the next testing phase, or in the case of direct
testing, migration to a production status. |
| Recommended
Connectivity Methods |
A list of the security and connectivity
methods that the Collaborative Members support |
Recommended Process Guidelines - When to
Test/Retest |
A list of when Providers and Payers should
test or retest. |
| Testing Process Flow – 837/270/276 |
This Testing Process Flow outlines the general
functional steps required for a trading partner to proceed from the point of initial
registration with the MN HIPAA Collaborative Community to a production implementation.
This particular flow addresses the outbound 837, 270 and 276 transactions and is intended
to be used as a general guideline in understanding testing process steps, work product
usage and the recommended test continuum. |
| Testing Process Flow - 835/271/277 |
This Testing Process Flow outlines the inbound
835, 271 and 277 transactions. Like the outbound process flow, it is to be used as a
general guideline in understanding the testing process steps, work product usage and
recommended testing continuum. |
| Testing Templates |
Templates include: 837 and 837 Test Profile
Templates and Instructions; 837 Test Scenario Template and Instructions; Non-Compliance
Issues List Template and Instructions; Collaborative Members' Test Profile Availability |
Transaction Companion
Guides
|
Guides and Instructions for 837P and
837I claim transactions, 835 remittance advice transaction, 270/271 Eligibility
Benefits and Inquiry and 276/277 Health Care Claim Status Request
and Response |
| Transaction
Contacts |
This is the list of
contact names for each of the Collaborative members |
