Kick-Off Meeting

Implementation, Certification, and Testing

November 19, 2014

2

Agenda

• Welcome and Introductions• Overview• Workgroup Charge• Workplans• Next Steps• Public Comment

3

Current Member list

Name OrganizationCris Ross, co-chair Mayo

Liz Johnson, co-chair Tenet Healthcare CorporationSarah Corley Next GenUdayan Mandavia iPatientCareRick Moore National Committee for Quality AssuranceAndrey Ostrovsky Care at HandDanny Rosenthal Inova Health SystemJohn Travis Cerner Corp.Steve Waldren American Academy of Family PhysiciansZabrina Gonzaga Lantana Kyle Meadors Drummond Group Inc.Brett Andriesen, staff lead Office of the National Coordinator for Health IT

Content StandardsChair: Andy Wiesenthal

Co-chair: Rich Elmore

HITSC Workgroups and Chairs

4

Architecture, Services & APIsChair: David McCallie Co-chair: Arien Malec

Transport and Security StandardsChair: Dixie Baker

Co-chair: Lisa Gallagher

Semantic StandardsCo-chair: Jamie Ferguson

Co-chair: Becky Kush

Health IT Standards Committee

Chair: Jacob ReiderVice Chair: John Halamka

Implementation, Certification &TestingCo-chair: Liz Johnson

Co-chair: Cris Ross

Steering CommitteeChair: Jacob Reider

Co-chair: John Halamka

*Task Forces may be needed for specific work assignments

Member Responsibilities

• Thanks for volunteering to serve on the Implementation, Certification, and Testing! Our best work happens when we have full participation. Accordingly, ONC has set up some guidelines for your participation.

• Workgroup members are expected to be actively engaged in their workgroup– Membership of the workgroups will be reviewed on a quarterly basis to ensure active

participation– Members missing more than 5 meetings in a year will be removed from membership

(unless extenuating circumstances)– Differing opinions are welcome and encouraged but should be done in a respectful

manner– Participants should be prompt and do their best to minimize personal interruptions

(e.g., mute phones)• Meeting materials are due at least 24 hours in advance of meetings

– Members are expected to review materials in advance and be actively engaged in the discussion with questions prepared in advance

– When commenting be as concise as possible and use examples to explain your point of view

5

6

HIT Policy and HIT Standards Committees Information Flow

7

Workgroup Charge

• Review implementation challenges with existing standards and provide recommendations for how to improve existing standards and testing

• Recommend testing process that support the goals of interoperability and information exchange

• Evaluate sustainable and inclusive approaches to certification and test method development

• Identify the necessary health IT functions and standards that must be tested

• Recommend stages of maturity in a certification testing model

2014 Q4 2015 Q1 2015 Q2 2015 Q3

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Upcoming FACA Milestones

8 Kick-off Federal Milestone

Joint HITPC/HITSC Meeting

Federal HIT Strategic Plan Posted for Comment

Interoperability Roadmap Recs prior to posting for comment

FACA HIT Strategic Plan Comments

Interoperability Roadmap Posted for Comment

HITPC comments on MU3 NPRMHITSC comments on Certification NPRM

All workgroups kicked off

FACA Milestone

FACA Interoperability Roadmap Comments

(estimate)

9

Workplans

Tasks Start Date Due Date 14-Nov

14-Dec

15-Jan

15-Feb

15-Mar

15-Apr

15-May

15-Jun

15-Jul

15-Aug

15-Sep

Workgroup Kick-Off 11/19/2014 11/19/2014

Improving Testing Efficiency and Open Test Methods

11/19/2014 1/28/2015      

Comment on Certification NPRM

TBD - Q1 TBD - Q1                      

Alternative Testing Tools and Testing Simplification Recommendations

4/22/15 6/24/15                      

Interoperability Testing Recommendations

6/24/15 09/22/15      

Community Contribution in Test Methods

TBD Q3 TBD Q3      

Current Testing Challenges and opportunities for Improvements

TBD Q3 TBD Q3

10

Detailed Workplans

Meetings Task

November, 19, 2014 - Workgroup Kickoff

• Review charge, introduce member and review draft work plan

December, 04, 2014 11:00 ET • Improving Testing Efficiency and Open Test Methods• Review Open Test Method Recommendations• Discuss the key challenges in conducting testing and

recommendations to address challenges

January, 06, 2015 11:00 ET • Review presentation of Certification NPRM overview and prepare to comment

January, 15, 2015 9:00 ET • Discuss Certification NPRM Comments

February 10, 2015 – HITSC Meeting

• Deliver Certification NPRM Comments to HITSC

February, 13 2015 12:00 ET Discuss how ONC can consider modifying community-driven process to enhance the value it delivers and provide recommendations.

February, 27 2015 12:00 ET • Discuss testing criteria that could be used to address multiple testing requirements and provide recommendations.

March 13,2015 12:00pm ET • Review alternative testing tools and testing simplification recommendations

11

Improving Testing and Open Test Methods Recommendations

• What are the opportunities to improve testing?– What are the key challenges in conducting testing?

• What are options and recommendations to address those challenges? • Presentation on Open Test Method pilot, involvement and results (December)• In what ways/how can ONC scale the community-driven test procedure

development process while factoring in the need for timely published test procedures post-final rule?

• Should ONC consider modifying its community-driven process to enhance the value it delivers? – What are the community needs that it currently does not address? – Should the community-driven process focus on tying certification criteria together for

scenario/sequenced testing and finding ways to optimize testing?– What are the options and recommendations for meeting those needs?

• Are there testing criteria that could be used to address multiple testing requirements? (Framework/characteristics based on 2014 Edition criteria)

12

Alternative Testing Tools and Testing Simplification Recommendations

• In what ways is it advisable for testing to include reference to usage of proprietary tools if the ATL would have to pay for or license the tool? – Or is the test tool responsibility something that should

remain solely a government funded process?• What is a practical approach and balance regarding

product capabilities designed just for testing purposes?– This refers to features that make testing more efficient but

generally may not have any use beyond testing (e.g., the ability to batch import a set of test patients compared to hand entering them)

13

Interoperability Testing Recommendations

• How could ONC, or third parties, develop testing tools that show products are interoperable?

• What criteria are necessary to determine if a test is successful?