Product Testing Program

Transcription

1 Product Testing Program Vendor Forum January 9,

2 Discussion Topics Purpose Desired outcomes Scope of product testing Testing process Retesting policy Proposed fee schedule Value Proposition Launch Plan and Timeline 2

3 Product Testing Program: Purpose To provide a high degree of assurance that systems developed for use by ehealth Exchange Participants: Conform to ehealth Exchange specifications and underlying standards; and Interoperate with other systems without error or further customization, while remaining conformant. To minimize the risk that known interoperability issues will be introduced and perpetuated in production. To reduce the burden, level of effort and cost to Participants in the ehealth Exchange. 3

4 Product Testing Program: Desired Outcomes Conformance A standardized configuration of a production-ready system conforms to the specifications, and demonstrates this by passing 100% of a rigorous set of conformance tests. Interoperability in a Production Environment System should be tested once and capable of interoperating with other product-ready systems. ehealth Exchange Participants are able to use the validated system to exchange, process and utilize the data for decision support purposes without subsequent testing or manual intervention for the declared profiles (e.g. transport, transaction and payload). Production systems securely interconnect, exchange messages; both transport and transactions work; and Participants can consume payload and interpret the information as was intended by the submitting organization and use the information for decision support. 4

5 Product Testing Scope* Required tests: 2011 smoke tests 2011 security tests 19 tests covered in participant testing 17 additional tests which validate known production issues Content (only if the product has not already been certified for the 2011 / 2014 edition of the EHR certification program) Provisional tests: A set of high-value tests which address known production issues, but that were either revised following the pilot or tested by only one pilot participant. System developers will be asked to run the tests to assess whether the tests perform and qualify for inclusion in the next iteration of the program. Provisional tests will not count toward the results. 5 * See Test Case List for Details

6 ehealth Exchange Product Testing Process System Developer Submit Application Package Complete Practice Testing. Ready for Validation? Yes: Submit tests and Unique Exec IDs Validated System No Healtheway No Package Complete? Ready to Test? Yes e No: Retest Validate Results. Passed Tests? Yes Aegis Test Lab Environment (DIL) NIST CDA validator tools Practice test ehealth Exchange Product Testing 6

7 ehealth Exchange Retesting Policy Ongoing compliance with the ehealth Exchange Performance and Service Specifications (PSS) is required for: System developers to remain an ehealth Exchange validated system; and ehealth Exchange Participants to retain Participant status, in compliance with the DURSA System developers shall evaluate whether changes to its previously validated system ( Modified System ) impact compliance with the PSS. Use testing tools and resources to self-test and verify compliance Reporting to Healtheway is not required. Ongoing testing is strongly encouraged. System developers shall notify Healtheway if there are Substantive Changes, including, at a minimum: Identify the Modified System, including system name and version. Summary of the Substantive Changes made, including impact regarding compliance with the PSS. Healtheway will determine, in consultation with system developer whether retesting is warranted. 7

8 Proposed Product Testing Pricing Schedule & Related Participant Testing Fees Product Testing Scenarios Total Required + Provisional Tests (No Content/Payload Testing) $ 37,000 Required + Provisional Tests (with Content/Payload Testing) $ 34,000 Participant Testing Scenarios Total Onboarding without an ehealth Exchange Validated System $ 22,000 Onboarding with an ehealth Exchange Validated System $ 11,000 8

9 Value Proposition Saves time and money Reduces cost and burden for providers / HIOs to onboard by approximately 50% Minimizes the level of vendor / developer support of providers / HIOs onboarding Reduces risk of interoperability issues being introduced into production, including the cost and burden of fixing interoperability issues and deploying patches Maximizes value of your system and the HIE connectivity Enables MU2 measures for transitions of care Enables interoperability for users of validated systems 9

10 Launch Plan Publish provisional tests cases 1/9/14 Share test cases and product testing program plans in monthly communications call 1/10/14 Coordinating Committee approval of the provisional test cases 1/14/14 ehealth Exchange and vendor community input on proposed provisional test cases Jan 2014 Healtheway board approval to launch product testing program - 1/23/14 Program Launch Feb

11 Discussion 11