4010 Testing Workgroup

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.

Test Profile Templates

The Test Profile Template is used by trading partners to document their test readiness, capability and methodology. Use of the document facilitates communication between trading partners in order to expedite direct testing and establish reasonable expectations. Historically, this exchange has been the result of multiple communications with trading partner contacts resulting in incomplete or contradictory information regarding testing. The template is designed to solicit the collection of consistent information serving both the sender and the recipient of a given transaction (e.g. 837/835 etc).

Test Scenario Template

The Test Scenario Template identifies generic, provider-neutral scenarios which should be considered for inclusion in direct testing based upon the originator's business lines and provided services. The scenario list is not exhaustive in its entirety but is intended to provide a basis for ensuring that representative test cases are included and sufficiently simulates production data exchanges. The template provides the originator with the opportunity to input specific test case scenarios, which once input, can be retained to facilitate future testing initiatives. Submission of a completed test scenario template should accompany the actual test file exchange unless already submitted with a prior test.

Test Non-Compliance Issues List Template

Due to issues of timing or originator capability, non-compliance issues may result in obstacles to obtaining full compliance with WEDI-SNIP testing types 1-7. At that point, negotiation with a trading partner may establish that it is mutually beneficial to proceed with testing despite non-compliance. The Non-Compliance Issues List facilitates the communication of non-compliant issues between trading partners and documents the necessity of regression testing once full compliance is achieved.

Recommendations for File Size Limitations

Some of the ASC X12N Implementation Guides contain recommendations relative to maximum file sizes per transaction type. The Collaborative supports these recommendations until either ASC X12N or DHHS publishes further file size limitations.

Recommendations for File Naming Conventions

HIPAA regulations, the ASC X12N implementation guides and Minnesota regulations are relatively silent on the subject of naming standards for the generation and transmission of HIPAA-compliant transactions. In the absence of any such purported standard, the Collaborative felt it was valuable to propose a file naming convention that seems logical, intuitive and easy to execute.

The definition of a Clearinghouse and its role in 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 Process Guidelines - When to Test/Retest

A list of when Providers and Payers should test or retest.

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.

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.

How to Upload Your Test Files

A PDF file that will walk you through the testing process