eHealth Exchange

Participant Testing

eHealth Exchange Participant Testing is required for new applicants to validate the compliance with the eHealth Exchange Performance and Service Specifications as established by the DURSA. 

Participant Testing is also required when existing eHealth Exchange participants undergo a major system upgrade or change their technology. 

There are three components to Participant Testing: 

  1. Security tests (fees waived if using an eHealth Exchange Validated Product)
  2. Smoke tests to validate the basic functionality and stability of the software being used (fees waived if using a Qualified Technology Solution (QTS))
  3. Tests for content data quality (free to all participants)

Upon successful completion, a Participant Testing Summary Report is issued detailing the results generated by the test lab, as well as independent verification of conformance checks. 

Security tests

eHealth Exchange uses The Sequoia Project’s Interoperability Testing Platform which leverages the Gazelle Security Suite.

Required Files to Execute the Retrieve Documents Test Cases 
This document contains the information required to execute the test cases, including patient demographics, document metadata, as well as the mapping of the documents to the patients. The data must be put into your Test Environment exactly as prescribed in the spreadsheet, and all attributes must be loaded (unless the attribute is an optional element and is not supported by your system).

Smoke Tests

This program is used by eligible organizations (such as health information exchange organizations, health systems, pharmacies, etc.) in order to onboard and to become participants on the eHealth Exchange and includes the following:

Required Files to Execute the Retrieve Documents Test Cases  This document contains the information required to execute the test cases, including patient demographics, document metadata, as well as the mapping of the documents to the patients. The data must be put into your Test Environment exactly as prescribed in the spreadsheet, and all attributes must be loaded (unless the attribute is an optional element and is not supported by your system).

Content Testing

eHealth Exchange is the only nationwide network whose participants must pass rigorous content validation tests. This means all data exchanged is truly interoperable and usable.

On February 5, 2018, the eHealth Exchange launched an enhanced content testing program. 

Content Validation Guidance

C-CDA Content Testing Scope / Documentation (Approved / Effective January 11, 2017)

IN CASE YOU MISSED IT: WEBINAR ON IMPROVING DATA QUALITY

eHealth Exchange has been collaborating with the Veterans Health Information Exchange (VHIE) since 2016 to improve the quality of data exchanged for the care of veterans across the US. The exchange of clinical data for the treatment of veterans leverage the eHealth Exchange network to improve continuity of care, reduce duplicative tests, and avoid clinical errors when patients see health care providers from different practices or networks.

On August 25, 2020, we hosted a webinar about how the eHealth Exchange network has been working with participants and the vendors to improve the quality of data exchanged to better understand a patient’s health history, develop safe, more effective treatment plans and to make sharing more seamless and secure for a patient’s care team.

View Recording | Download Slides

The Validation Plan

Orient your organization with the Validation Plan and related testing documentation which will be used to validate that your system satisfies the technical requirements for participation in eHealth Exchange.

Have questions about eHealth Exchange?

We’ve got answers. Fill out this form to be contacted by a member of the eHealth Exchange team.

"*" indicates required fields

This form is not to be used to request patient data. Please visit our information handling practices for more information.

Request a meeting

Fill in your details and we'll be in touch.

This form is not to be used to request patient data. Please see our information handling practices for more information.