© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. Action Plan For v2/v3/CDA Strategy Draft

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. Action Plan Urgent need to develop strategic plan related to issues, problems and strategies related to v2 messaging, v3 messaging, and CDA Board appointed Task Force to develop report with strategy recommendations Hire facilitator with support to carry out work Facilitator to develop methodology for obtaining required info for report

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. Action Plan (2) Funding for effort from CEO discretionary fund. Presented to Board on Tuesday. If approved, work will start immediately Report due in January 2010

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V2 Messaging What is business case? What business requirements does v2 address? Who are customers, stakeholders, influencers? How will we address those needs? Should v2 coexist with v3? What is future of v2?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V2 Messaging (2) Should development be continued? Use of v2 continue to be supported in US and worldwide? What v3 features should be integrated into v2? Should delimiter syntax be replaced by XML tags? What would a V2/V3 hybrid look like?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V2 Messaging (3) Should v2 messages simply become v3 messages? How do we market the transition from v2 to v3 messaging?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V3 Messaging Why is v3 messaging viewed to be so complex? What needs to be “fixed” in v3 messaging? What is business case for v3? Who are customers, stakeholders, influencers? How will we address those specific needs?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V3 Messaging (2) What business requirements does v3 messaging address better than any other choice? Should v3 always be first choice for data interchange? Is v3 messaging a viable product? What are differences in v3 users? What are classes of users>

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V3 Messaging (3) Will a library of v3 messages that can be directly implemented be a solution to complexity? How many v3 messages do we need? How do we avoid similar but different messages? Can v3 messages be made shorter without loss of functionality?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V3 Messaging (4) Can a variant of XML be used Can a v3 message only carry what is specific for that dat6aload, including only the data and enough logic structure to provide interoperability? Can v3 messaging be simplified? What does an implementer need to borrow to implement v3 messages?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. V3 messaging (5) How important is establishing a user base? How can v3 messaging to made more approachable to novices? What is a reasonable pathway from v2 to v3? Is the absence of such a pathway a barrier to transition?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. CDA Who are customers, stakeholders, influencers? How will we address those needs? How do templates, clinical statements, DCM, and archetypes relate to CDA? Is CDA a proper method for exchange of data? What are options?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. CDA (2) When should CDA be used and when should messages be use to exchange data? Is there a place for both CDA and v3 messaging for data interchange? How many CDAs should there be? How do we control CDAs with minor differences, developed by different groups? How can CDA complexity be reduced?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. CDA (3) What process might we use for building and maintaining a library of CDA templates? When is CDA the best choice? When is v3 messaging the best choice?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. General Issues What is HL7’s interoperability strategy? What should be the next generation of data interchange standards? What new technology needs to be integrated/adopted? What other “issues” must be addressed to meet its customer requirements? For example, what should HL7 do related to termonology/templates/data elements?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. General Issues (2) What are the business requirements for HL7 standards? Who is the real HL7 customers, or are there multiple customers with different needs? Should we begin thinking about a v4?  How would it differ?  What are its characteristics?  Do we have the resources?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. General Issues (3) What is HL7’s product strategy? Are there key gaps that need to be addressed? What is the role of SOA in overarching strategy? How might service be integrated into other product lines?

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. Deliverables Characteristics of full set of HL7 customers, influencers, sponsors, funding sources Define set of concrete steps that vendors and implementers can depend on White paper (report) addressing charge with sufficient detail for action Communication plan to communicate and share plans with membership and broader community

© 2009 Health Level Seven ®, Inc. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Office. Deliverables (2) Promote through media Develop overall funding plan including requirements, products, and funding sources Deliverables due before January 2010 Working Group meeting. Big party at January 2010 meeting!!!