thetes?ngprogramwebinar - the sequoia project

1 Copyright © 2015 The Sequoia Project. All rights reserved.

An ini%a%ve of

The Tes?ng Program Webinar Didi Davis, Tes?ng Program Director MaG Blackmon, Tes?ng Analyst

June 19, 2015

Healtheway rebrands to reflect expanding mission for health IT interoperability, including:

•  Increasing number of collabora?ve ini?a?ves •  Enhancing interoperability educa?on •  Promo?ng industry-‐wide best prac?ces


Why “The Sequoia Project”?

•  Sequoia trees are among the most enduring, massive living things. •  An interconnected root system allows individual trees to support each

other, making the en?re system stronger.

A thriving health IT community requires interconnected organizaAons working together for the benefit of all.

Connected We Stand.


Con?nued Support for Carequality and eHealth Exchange

•  The Sequoia Project will con?nue to serve as the steward of its independent ini?a?ves.

•  The ini?a?ves will con?nue to be governed independently by its respec?ve members.

•  The Sequoia Project will be ac?vely pursuing addi?onal interoperability ini?a?ves that will aid in making secure data exchange a reality in the U.S. More informa?on will be forthcoming within the year.


Disclaimer

This webinar is a brief program descrip?on of the eHealth Exchange Tes?ng Programs. It does not cons?tute the full program policies and procedures of the eHealth Exchange Tes?ng Program. Those policies and procedures are contained within the valida?on plan and the applicant agreement.


Agenda

1.  History and Overview of the eHealth Exchange 2.  Introduc?on to the eHealth Exchange Tes?ng Program and 2010/2011

Specifica?ons 3.  The Valida?on Tes?ng Programs Documenta?on 4.  Conformance Tes?ng Checklists 5.  Automated Tes?ng: The Developers Integra?on Lab (DIL) 6.  Gecng Started in the Tes?ng Program and How to Join the eHealth

Exchange 7.  The Tes?ng Workgroup


This conference was recorded and posted.


An ini%a%ve of

History and Overview of the eHealth Exchange

10 Years of Progress

2006

ONC sponsors prototype architectures, followed by trial implementa?ons.

8

2008 Focus shiied to

suppor?ng produc?on pilots

2009 First produc?on

exchange between Social Security Administra?on

and MedVirginia, followed by Veterans Health Administra?on and Kaiser Permanente

2012 Exchange

transi?ons to The Sequoia Project. Private sector par?cipa?on increases

2015 Na?onwide

implementa?on across 50 states

Copyright © 2015 The Sequoia Project. All rights reserved.

Rapidly growing network for securely sharing health informaAon over the Internet

Tech Vendors

Federal Govt

States

Pharmacies Payers

HIEs

Care FaciliAes

Shared Governance and Trust Agreement Common Standards, Specifica?ons & Policies


17,000+ medical groups

1000+ dialysis centers

8,200 pharmacies

Suppor?ng more than 100 million pa?ents

Largest Health Informa?on Exchange Network in the U.S. Now in 2015, the eHealth Exchange connects:

All 50 states

Four federal agencies (DoD, VA, HHS including

CMS, and SSA)

30% of U.S. hospitals

2015 Assump?ons: •  Totals include organiza?ons that have completed the applica?on process and are in the onboarding queue. •  Data from non-‐par?cipants was self-‐reported from the applica?on or based on published data.


eHealth Exchange Growth (2015 Projected)

•  Operations supported by ONC

•  Network doubles

•  Growth fueled by MU2 TOC measures

•  Testing Program launched

ONC Initiative: NwHIN Exchange

2009 2013 2014 2015 2011

•  Network matures

•  Product Testing Program launched

•  Increased network adoption

•  New use case

•  New types of participants / networks

•  Enhanced capabilities

•  Streamlined testing / onboarding

44 Total

Participants Total

Participants

23 Total Participants

4

81 Total

Participants

150+ Projected

Participants


eHealth Exchange Overview

eHealth Exchange Provides –  Legal Agreement and Governing CommiGee –  Opera?ng Policies and Procedures –  Program Support (via Healtheway)

Technical Services –  UDDI (phone book of other network Par?cipants) –  Security (x.509 Managed CA) –  Automated tes?ng using Aegis plaoorm

12 12 Copyright © 2015 The Sequoia Project. All rights reserved.

Sample Use Cases Treatment / Care CoordinaAon Allows access to cri?cal informa?on (e.g., test results, medica?on history, allergy info, immuniza?ons) and makes available to providers when pa?ent is transferred.

Responder Only Profile SupporAng the Treatment Use case (New) Allows other networks (e.g., release of info companies and SAAS model vendors) to respond to queries from eHealth Exchange Par?cipants on behalf of their client.

Military/Veteran Health DoD and VA exchange ac?ve service members and veterans’ records to provide government and private caregivers with up-‐to-‐date medical histories

Disability DeterminaAon Social Security Administra?on requests claimant records electronically to make disability determina?ons. Cuts down claims processes from months to days.

Quality ReporAng for the End Stage Renal Disease Program -‐ CMS Allows Dialysis centers to send quality data to CMS to assure that individuals with End Stage Renal Disease receive the highest quality of care


eHealth Exchange Query Workflow


(AcAng as an IniAator)

(AcAng as a Responder)

PaAent Discovery (IHE XCPD)

Query for Documents (IHE XCA)

Searches for paAents

Found paAent

Retrieve Documents (IHE XCA)

Searches for Document(s)

Lists zero or more found documents

Transmits Document(s)

Returns zero or more documents

eHealth Exchange ParAcipant Gateway

eHealth Exchange ParAcipant Gateway

eHealth Exchange: Benefits Benefit How eHealth Exchange Achieves Benefit

Reducing Costs

Using common standards, legal agreements and governance enables par?cipants to reduce legal fees and avoid building custom interfaces with trading partners.

Improving Clinical and Business Decisions

Access to a na?onwide data sharing network provides secure access to the comprehensive health data that healthcare providers, pharmacies and payers require to improve clinical decision making, pa?ent safety, process improvement and fair payment.

Exchanging Data with Government Agencies

Federal par?cipa?on in the eHealth Exchange supports data sharing among all par?cipants and with agencies such as Centers for Medicare & Medicaid Services, the Department of Defense, the Social Security Administra?on and the Department of Veterans Affairs.

Planning for the Future

Because the eHealth Exchange is governed by a representa?ve set of par?cipants, its mul?-‐purpose interoperability plaoorm has the ability to evolve and incorporate new use cases, standards, etc.



An ini%a%ve of

Introduc?on to the eHealth Exchange Tes?ng Program And the 2010/2011 Specifica?ons

What is the Tes?ng Program of the eHealth Exchange? •  Developed to test compliance for Health Informa?on Exchange (HIE)

standards as required by the eHealth Exchange Coordina?ng CommiGee •  Purpose is to enable organiza?ons that wish to par?cipate to validate the

compliance of their Health Informa?on Technology (HIT) with the eHealth Exchange Performance and Service Specifica?ons.

•  Designed to ensure interoperability and assure specifica?on compliance and minimal implementa?on

•  eHealth Exchange staff developed and operate valida?on programs to implement tes?ng in groupings of service sets, test scenarios and test cases

•  Implementa?on-‐hardened by years of opera?ons •  Evolves as new interoperability issues arise (The Specifica?on Factory) •  Intends to publish a mul?-‐year roadmap (Tes?ng Workgroup) •  The community has developed a large body of test cases, tes?ng data, and

conformity assessment tools including nega?ve tes?ng •  The tes?ng programs leverage AEGIS test lab Developers Integra?on Lab (DIL)


Who can leverage the Tes?ng Program? The eHealth Exchange Tes?ng program supports:

–  Applicants who wish to join the eHealth Exchange as Par?cipants; –  Exis?ng eHealth Exchange Par?cipants who wish to test new capabili?es or

retest as a condi?on of con?nued par?cipa?on in the eHealth Exchange; and

–  Developers of systems who wish to have their product validated as eHealth Exchange compliant.

The eHealth Exchange Tes?ng program verifies that a System Under Test (SUT):

–  Complies with the eHealth Exchange SpecificaAons; –  Has the ability to interoperate with other eHealth Exchange Par?cipant

Systems; and –  Has implemented key security features as demonstrated by nega?ve

tes?ng.



OperaAonal Infrastructure

Discovery, Message Security and Privacy

InformaAon Exchange

Profiles

Security Infrastructure (Managed PKI) Web Services Discovery (UDDI)

Web Services Discovery (UDDI) Message Plaoorm Authoriza?on Framework

Pa?ent Discovery

Query for Documents

Retrieve Documents

Pa?ent Consent Push Publish /

Subscribe

Care Summary Exchange Quality / Admin Data Push Claims Eligibility

Run?me systems suppor?ng the eHealth Exchange

Message security, privacy, and interoperable healthcare data exchange

Employing lower-‐level layers to enable basic message exchange paGerns

Employing exchange paGerns to enable clinical data enabled workflows

eHealth Exchange Architectural Layers/Specifica?ons


IHE Mappings to eHealth Exchange Architecture

OperaAonal Infrastructure

Discovery, Message Security and Privacy

InformaAon Exchange

Profiles

Security Infrastructure (Managed PKI) Web Services Discovery (UDDI)

Web Services Discovery (UDDI) Message Plaoorm Authoriza?on Framework

Pa?ent Discovery

Query for Documents

Retrieve Documents

Pa?ent Consent Push Publish /

Subscribe

Care Summary Exchange Quality / Admin Data Push Claims Eligibility

Run?me systems suppor?ng the eHealth Exchange

Message security, privacy, and interoperable healthcare data exchange

Employing lower-‐level layers to enable basic message exchange paGerns

Employing exchange paGerns to enable clinical data enabled workflows

C32 IHE PCC Content

IHE XCPD IHE XCA IHE XCA IHE BPPC IHE XDR/XDM

IHE XUA

IHE ATNA

2010 Ini?al Product Specifica?ons These produc?on specifica?ons are in effect now, and are currently being used by the majority of exis?ng produc?on Par?cipants but they are being sunset at a date to be determined by the eHealth Exchange Coordina?ng CommiGee. •  Access Consent Policies Produc?on Specifica?on – v1.0 [PDF – 154 KB] •  Administra?ve Distribu?on Produc?on Specifica?on – v2.0 [PDF – 157 KB] •  Document Submission Produc?on Specifica?on v2.0 [PDF – 192 KB] •  Health Informa?on Event Messaging Produc?on Specifica?on v2.0 [PDF – 133

KB] •  Messaging Plaoorm Produc?on Specifica?on v2.0 [PDF – 189 KB] •  Pa?ent Discovery Produc?on Specifica?on v1.0 [PDF – 199 KB] •  Query for Documents Produc?on Specifica?on v2.0 [PDF – 178 KB] •  Retrieve Documents Produc?on Specifica?on v2.0 [PDF – 150 KB] •  Web Services Registry Produc?on Specifica?on v2.0 [PDF – 359 KB]


2011 Current Specifica?ons (Produc?on Eff. Date 3/1/12) These specifica?on were approved for produc?on use for the eHealth Exchange Coordina?ng CommiGee on 2012-‐03-‐01 and should be used by new eHealth Exchange Par?cipants. Note that Par?cipants should consult with their key Exchange partners to coordinate their adop?on of 2010 vs. 2011 specifica?ons. •  CAQH CORE X12 Document Submission Service Interface Specifica?on v 1.0 3/6/2012 [PDF –

390 KB] •  Electronic Submission of Medical Documenta?on (esMD) X12 Profile v 1.0 3/6/2012 [PDF –

783 KB] •  Web Services Registry Web Service Interface Specifica?on v 3.1 3/6/2012 [PDF – 405 KB] •  Messaging Plaoorm v3.0 approved by NTCon 6/27/2011 [PDF – 232 KB] •  Pa?ent Discovery v2.0 approved by NTCon 6/27/2011 [PDF – 234 KB] •  Query for Documents v3.0 approved by NTCon 6/27/2011 [PDF – 201 KB] •  Retrieve Documents v3.0 approved by NTCon 6/27/2011 [PDF – 153 KB] •  Authoriza?on Framework v3.0 approved by NTCon 7/25/2011 [PDF – 226 KB] •  Web Services Registry v3.0 approved by NTCon 7/25/2011 [PDF – 376 KB] •  Electronic Submission of Medical Documenta?on (esMD) XDR Produc?on Specifica?on

v1.0 [PDF – 324 KB] •  Administra?ve Distribu?on Produc?on Specifica?on v2.0 [PDF – 144 KB] •  Document Submission Produc?on Specifica?on v2.0 [PDF – 192 KB]


What Specifica?ons are Tested Today?

There are six eHealth Exchange specifica?ons tested as part of the par?cipant and product tes?ng program.

u  Authoriza?on Framework u  Messaging Plaoorm u  Pa?ent Discovery u  Query for Documents u  Retrieval of Documents u  Access Consent Policy (added June 2015)



An ini%a%ve of

The Valida?on Tes?ng Programs Documenta?on Tes?ng for Par?cipants and HIT Product Vendors

eHealth Exchange Valida?on Programs

ParAcipant TesAng Program –  Enables organiza?ons wishing to par?cipate in the eHealth Exchange

network to validate the compliance of their implemented HIT with the eHealth Exchange Performance and Service Specifica?ons

Product TesAng Program –  Focus on compliance and interoperability tes?ng –  Reduces cost and burden for par?cipants to onboard by approximately

50% –  Minimizes the level of vendor / developer support of providers / HIOs

onboarding –  Reduces risk of interoperability issues being introduced into produc?on,

including the cost and burden of fixing interoperability issues and deploying patches


hGp://sequoiaproject.org/ehealth-‐exchange/tes?ng-‐overview/

eHealth Exchange Par?cipant & Product Tes?ng Fees

Notes: 1Op?onal Content tes?ng: 1) Basic C32; 2) Bridge C32 and 3) C-‐CDA. Content tes?ng is waived if Applicant uses a product that was cer?fied for the 2011 or 2014 edi?on of EHR cer?fica?on for Stage 1 or Stage 2 meaningful use. ($3,000 for each type of content to be tested.) Applicants using an eHealth Exchange Validated Product ONLY complete Smoke Tes?ng.

Product ValidaAon TesAng $34,000 Smoke Test Cases, Security Test Cases (Required and Provisional)

2010 Specs 2011 Specs

Smoke Tests (Essen?al tests to verify connec?vity and core func?onality)

No charge $11,000

Security Tests N/A $8,000

Content (Basic C32, Bridge C32, C-‐CDA)1

ParAcipaAon ValidaAon TesAng:



Vendors conduct rigorous set of tests to validate:

•  Conformance to underlying standards and specifica?ons

•  Systems are free from known interoperability issues -‐ transport, security, transac?ons and content (if not MU cer?fied)

•  Configured and operate securely (nega?ve security tests)

Product Tes?ng Program

Content Tes?ng Documenta?on

•  The Basic C32 (ONC 2011 Edi?on) •  The Bridge C32 •  The Consolidated CDA (C-‐CDA) (ONC 2014 Edi?on)


Test Case Hierarchy


Smoke Tests Summary Smoke Tests Summary The Smoke Tests Service Sets, Test Scenarios and Test Cases can be summarized as below for the Participant and Product Testing Programs: 2010$Service$set$ 2010$Scenario$ 2010$Test$Case$ Participant! Product!SS: PRL-0000.0-2010 TS: PRL-I-0000.0-2010 TC: PD-I-0000.0-2010 X! Peer!to!Peer!SS: PRL-0000.0-2010 TS: PRL-I-0000.0-2010 TC: QD-I-0000.0-2010 X! Peer!to!Peer!SS: PRL-0000.0-2010 TS: PRL-I-0000.0-2010 TC: RD-I-0000.0-2010 X! Peer!to!Peer!SS: PRL-0000.0-2010 TS: PRL-R-0000.0-2010 TC: PD-R-0000.0-2010 X! Peer!to!Peer!SS: PRL-0000.0-2010 TS: PRL-R-0000.0-2010 TC: QD-R-0000.0-2010 X! Peer!to!Peer!SS: PRL-0000.0-2010 TS: PRL-R-0000.0-2010 TC: RD-R-0000.0-2010 X! Peer!to!Peer!

!2011$Service$set$ 2011$Scenario$ 2011$Test$Case$ Participant! Product!SS: PRL-0000.0-2011 TS: PRL-I-0000.0-2011 TC: PD-I-0000.0-2011 X! X!SS: PRL-0000.0-2011 TS: PRL-I-0000.0-2011 TC: QD-I-0000.0-2011 X! X!SS: PRL-0000.0-2011 TS: PRL-I-0000.0-2011 TC: RD-I-0000.0-2011 X! X!SS: PRL-0000.0-2011 TS: PRL-R-0000.0-2011 TC: PD-R-0000.0-2011 X! X!SS: PRL-0000.0-2011 TS: PRL-R-0000.0-2011 TC: QD-R-0000.0-2011 X! X!SS: PRL-0000.0-2011 TS: PRL-R-0000.0-2011 TC: RD-R-0000.0-2011 X! X!


eHealth Exchange Test Case Documenta?on

2010 SpecificaAons for ParAcipants & Product Vendors

•  2010 Smoke Test Cases (6 required)

2011 SpecificaAons for ParAcipants

•  2011 Smoke Test Cases (6 required) •  Security Test Cases (19 required for Par?cipants) •  Provisional Security Test Cases applicable to Product Tes1ng ONLY (52 provisional) 2011 SpecificaAons for Product Vendors

•  2011 Smoke Test Cases (6 required) •  Security Test Cases (35 required for Product Vendors) •  Provisional Security Test Cases applicable to Product Tes1ng ONLY (52 provisional)


eHealth Exchange Service Set Documenta?on


eHealth Exchange Test Scenario Documenta?on


eHealth Exchange Test Case Documenta?on


ACP Test Cases and checklists – Approved by CC June 2015

•  A pilot was facilitated under the direc?on of the CC, with three organiza?ons (IOD, Mirth and MRO). IOD and MRO represent two releases of informa?on (ROI) companies who manage medical records releases for their provider customers. Mirth is an HIE vendor. All three pilot par?cipants provide gateways that can be leveraged for the eHealth Exchange requirements.

•  The three pilot par?cipants agreed to complete the exis?ng eHealth Exchange Smoke Tests and Security Tests and then pilot the newly developed ACP-‐SSA set of test cases.

•  The Spec factory approved moving the ACP-‐SSA tes?ng program documenta?on and tes?ng tools from pilot to produc?on. The P&T Task Group reviewed the documenta?on and had no addi?ons / objec?ons.

•  The tes?ng documenta?on has been posted for public comment here: –  hGp://ehealthexchange.wikispaces.com/Documents+Posted+for+30+Day+Comment+Period


Fast Track Tes?ng Process for Applicants/Par?cipants Using a Qualified Technology Solu?on – Approved by CC June 2015 •  Qualified Technology Solu?on is a system that sa?sfies the following:

–  Is an eHealth Exchange validated solu?on; –  Has a standardized produc?on-‐level configura?on that complies with the eHealth Exchange Performance and Service

Specifica?ons; –  Has a minimum of four (4) produc?on Par?cipants in the eHealth Exchange network who have successfully completed

tes?ng without any issues. Those produc?on Par?cipants may not have any outstanding technical issues which impede their ability to exchange informa?on with other eHealth Exchange par?cipants; and

–  Has a history of demonstra?ng reproducible compliance with the Performance and Service Specifica?ons as previously validated under the par?cipant tes?ng program.

–  Only Applicants or Par?cipants who use Qualified Technology Solu?ons may u?lize the Qualified Technology Solu?on Tes?ng Process.

•  An organiza?on using a Qualified Technology Solu?on will be able to move directly into produc?on tes?ng. This will accelerate the tes?ng process, and reduce the level of effort and cost to onboard.

•  The risk for produc?on interoperability issues is expected to be minimal. Partner tes?ng will help verify that configura?ons of a Qualified Technology Solu?on are interoperable in a produc?on environment. The current tes?ng process verifies the configura?ons in a test environment. As a result, it does not detect configura?ons in a produc?on environment.

•  The drai eHealth Exchange Tes?ng Op?on has been posted for public comment effec?ve 6/19/2015 at:

–  hGp://ehealthexchange.wikispaces.com/Documents+Posted+for+30+Day+Comment+Period


Formal Change Process Milestones Approval Milestones Fast Track

TesAng Policy Target Approval

ACP Test Cases Target

Approval

Present to CC for Approval (Drai): 6/8 April

Par?cipant Input (Post drai to eHealth Exchange Wiki):

6/18 May

Par?cipant Input (Webinar to review updates):

6/19 6/19

eHealth Exchange Informa?onal Call 7/7 7/7

CC Approval: 6/30 6/16

Public Comment no?ce to par?cipants: 7/2 6/19

Objec?on Period Ends: 7/31 8/6

Target Effec?ve Date: 8/1 8/7

37 Copyright © 2015 The Sequoia Project. All rights reserved. 37


An ini%a%ve of

Conformance Tes?ng Checklists

Conformance Checklists Test Cases TesAng DocumentaAon (Test Steps) •  The Test Steps field contains a list of steps that should be executed for the Test Case. •  Each step has informa?on that relates to the ac?vity that is being accomplished. Within

these test steps there is a call out to the checklists that are also part of the overall tes?ng programs for the eHealth Exchange.

•  The CL: MA SOAP Request and CL: MA SOAP Response checklists specifically validate conformance to the Messaging Plaoorm (M) and Authoriza?on Framework (A) Specifica?ons, see sample excerpt below:


Overall format…too small to read in this view


Prefix

Example: “PD”

In this example, “Pa?ent

Discovery” 42 Copyright © 2015 The Sequoia Project. All rights reserved.

ID

Example: “200”

“ID” iden?fies the Checklist Test Item Number

In this example, Item 200 43 Copyright © 2015 The Sequoia Project. All rights reserved.

Field being verified

Example: “S:Envelope”

“Field” iden?fies which node is under examina?on.

In this example, it is the SOAP envelope.



Field Level

Example: “0”

“Field level” iden?fies the level of subordina?on of the node.

In this example, it is “0”, or top level.

Verify Presence

Example: “R”

“Verify Presence” indicates whether the field is Required, Op?onal, or Condi?onal.

In this example, it is “R” for Required.


MulAple Possible

Example: “ “ [blank]

“Mul?ple Possible” indicates if there can be more than one instance of this node.

In this example, it is blank, meaning no.


AddiAonal VerificaAon, DescripAon, example

Example: Verify: using the Messaging & Authoriza?on SOAP Request Checklist, verify the en?re SOAP envelope.

This field provides the direct checklist instruc?ons

In this example, it directs the user to another checklist for verifica?on.


Exchange Spec Reference

Example: “PD v2.0”

This field provides the reference to the relevant eHealth Exchange Specifica?on.

In this example, it refers to Pa?ent Discovery, version 2.0 (2011)

Column H


Underlying SpecificaAon

Example: “XCPD Sec?on 3.55.4.1.2.1”

This field provides the reference to the underlying specifica?on sec?on.

In this example, it refers to the IHE Cross-‐Community Pa?ent Discovery

(XCPD), sec?on 3.55.4.1.2.1

Column I


2nd Underlying Spec

Example: “HL7 v3 Domain: Transmission Infrastructure, Sec?on 1.2” PRPA_IN201305UV02.MCCI_MT000100UV01.MessageThis field provides the reference to any underlying secondary

specifica?on(s) sec?on(s).

In this example, it refers to the HL7® version 3 specifica?on “Domain: Transmission Infrastructure” Sec?on 1.2

Column J



An ini%a%ve of

Automated Tes?ng

The Developers Integra?on Lab (DIL) hGp://dil.aegis.net

What is the DIL?


SUT Adapter

SUT Adapter

SUT Adapter

How does the DIL work?


Gecng Started

•  OID and Assigning Authority ID •  Health IT gateway •  Pa?ent Database •  DIL UDDI Connec?on Informa?on •  Before execu?ng any tests in the DIL, the following tasks need to be

completed: –  Registering in the DIL –  Publishing endpoints –  Downloading and Installing AEGIS cer?ficates –  Finalizing UDDI configura?on

•  Paperwork/checklist process with Healtheway for customer support



An ini%a%ve of

Gecng Started in the Tes?ng Program and How to Join the eHealth Exchange

Preparing for eHealth Exchange Tes?ng ParAcipant TesAng (New & ExisAng ParAcipants) Product TesAng (For Vendors) Apply to eHealth Exchange (New Applicants) •  eHealth Exchange Applica?on (New Applicants: The

Tes?ng Services Agreement is included in the Applica?on) •  DURSA (Version September 30, 2014) •  eHealth Exchange Par?cipa?on Agreement •  Tes?ng Services Agreement •  hGp://www.sequoiaproject.org/images/Content/

Documents/Applica?on-‐Package/ehex-‐tes?ng-‐readiness-‐checklist_2014-‐04-‐03.zip (You may need to enlist your vendor's help to complete this checklist)

•  Apply to the Product Tes?ng Program •  Submit Product Tes?ng Applica?on •  Submit Signed Tes?ng Services Agreement •  Complete DIL Setup Checklist •  Pay Tes?ng Fees

Coordina?ng CommiGee Approves Applica?on for Par?cipa?on and Refers Applicant to Begin Prac?ce Tes?ng

N/A

Setup and Conduct Prac?ce Tes?ng in the DIL Setup and Conduct Prac?ce Tes?ng in the DIL

Run Tests and Submit Results Run Tests and Submit Results

Coordina?ng CommiGee Approves Applicant Test Results The Sequoia Project Approves Applicant Test Results

Ac?vate in Produc?on Environment N/A


Onboarding & Tes?ng Process

Staff Reviews



An ini%a%ve of

The Tes?ng Workgroup

Call for Par?cipa?on – Tes?ng Workgroup •  On behalf of the Coordina?ng CommiGee, the eHealth Exchange announces

an open call for par?cipa?on in the new Tes?ng Workgroup launching June 2015.

•  The Tes?ng Workgroup will develop func?onal and conformance tes?ng requirements to test and validate Health IT Modules to the eHealth Exchange criteria.

•  The Tes?ng Workgroup will be responsible to create, review and approve tes?ng documenta?on, checklists and Use Cases.

•  The workgroup will determine interoperability tes?ng requirements to enable robust tes?ng of informa?on exchange among par?cipants of the eHealth Exchange for Coordina?ng CommiGee-‐approved use cases.

•  The Tes?ng Workgroup shall focus on the broad industry needs by remaining grounded in exis?ng capabili?es implemented in produc?on as well as iden?fying gaps or issues with informa?on exchange among technology plaoorms and architectures.

•  We invite your par?cipa?on in the Tes?ng Workgroup by signing up at :hGp://goo.gl/forms/RfCOlfdM9p


Tes?ng Workgroup Deliverables •  Work on items as tasked by the eHealth Exchange Coordina?ng CommiGee •  Provide subject maGer exper?se, and to work with other subject maGer experts, to support

development and maintenance of the tes?ng materials to support the eHealth Exchange. •  Create or recommend adop?on of the following ar?facts:

–  Test Procedures (at various levels of detail); –  Test Specifica?ons; –  Tests Cases; –  Valida?on Scripts (actual crea?on, opera?on, and implementa?on of the tests may be included or

excluded from the scope of the Tes?ng Workgroup); and –  Test Data (sample pa?ents and documents). –  Related documenta?on in order to test the various specifica?ons and func?onal requirements

•  Coordinate pilots of new tes?ng documenta?on and tooling. •  Facilitate an open change management process that allows maintenance of the tes?ng

ar?facts and expansion of the programs to meet industry needs. •  Obtain cross-‐workgroup approval of all tes?ng ar?facts by the eHealth Exchange

Specifica?on Factory, and the Policy and Technical Task Group, prior to submission for approval to the Coordina?ng CommiGee.

•  Determine how best to facilitate tes?ng of the eHealth Exchange between differing technology plaoorms and architectures, as well as differing transport protocols (e.g. SOAP, RESTful, etc.) and data types (e.g. document-‐based exchange, message-‐based exchange, API-‐based, etc.)



An ini%a%ve of

Ques?ons and Answers

For further ques?ons, please contact [email protected]