| 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. |
| 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. |
