Standards Harmonization Readiness Criteria

1. Standards Harmonization Readiness Criteria TIER 1 March 2, 2006 HITSP Standards Harmonization Criteria Committee

2. Purpose • The Readiness Criteria presented here are “Tier 1” or the highest level. • Although they will require further definition and detail, to fully meet intended use in harmonization by HITSP, they represent a starting point for Panel approval and preliminary use by the Technical Committees. • We anticipate further iterations and changes and welcome feedback.

3. Foundation for Standards Harmonization • We are planning recommendations to HITSP to adopt a primary goal and basic set of objectives as the foundation for harmonizing healthcare standards.

4. Harmonization Readiness Explained • Harmonization Readiness is determined by applying specific criteria that will allow the HITSP to select the initial set of standards most ready for use as an interlocking set to implement in support of breakthrough use cases. • An interlocking (harmonized) set of standards requires: • Selection of initial standards based on criteria • Resolution of gaps and overlaps between selected standards • Coordinated maintenance of the set of standards based upon feedback from use • Readiness is relative to an action for interoperability and must be understood at the messaging level with constrained vocabulary. (delete)

5. The Community Defines a Breakthrough ONC Coordinates Breakthroughs with long term strategy Refines breakthroughs into use cases HITSP Harmonizes relevant HC standards to support widespread interoperability and interchange Based on Community directed - use case driven process r R e e d c i o s n m o m c e o n t d s R d C r a T d o n o l a t f s o r f o h a s r e m i r o o n t i z n a e t i v o n n I Inventory of Standards Inventory Committee Standards Readiness Criteria Committee Gathers existing inventories and suggests how Develop tool for TCs to use in making to maintain recommendations to HITSP and for HITSP to to support harmonization use in harmonization I n n v a e t n s t d o r e i d e n s e o m f m s t o a c n e d r a g r n d i t s c e t l o e s c o r o n f s l i o d o e T r C R Technical Committees Develop business and technical requirements Survey landscape for candidates , gaps , duplicate standards Propose standards for harmonization Publish implementation guide and testing Readiness Criteria within Standards Harmonization Flow Criteria for Inventories Recommended Use Case Standards Charter s d r a d Recommend changes based upon user feedback

6. Criteria as Filters Suitable for purpose Organization and process Costs Life cycle maturity

7. Suitable for Purpose • To be determined suitable, standard(s) must: • Align with ONC Strategic Framework for HIT • Meet the use case business and technical criteria • Be compatible with other standards, framework, architecture and models as determined by HITSP. • Demonstrate the flexibility and extensibility to adapt over time • Backward, lateral and forward compatibility considerations (Delete) • Includes a documented discovery process of standards landscape (Delete)

8. Organization and Process Initial Criteria for SDOs: • Balance and lack of dominance by any single interest group • Applies both to leadership and approval process • Formal development and approval processes • Includes process for responding to input/feedback from implementers • Effective governance and funding to be responsible stewards, open to stakeholders and able to maintain and enhance their standards • Domain relevance with history of commitment • Favorable intellectual property and licensing terms • Willingness to collaborate with other standards developers and HITSP • Adequate consumer voice in the development process • Technology and vendor neutrality

9. Costs • Total life cycle costs including development, licensing, and use • Lack of barriers, ease of access

10. Life Cycle Maturity • Where is standard in Life Cycle from Initial Development to Implementation? SDO standards either, ‘draft’ or ‘approved and published’ Standard is tested Standard matures and ITS products are developed Standard implementation and change • What is the level of standards developer support and market adoption? This must be a balance, particularly when dealing new standards, gaps and duplications.

11. Other Considerations • Existing resources of “harmonized” standards information • National Committee on Vital and Health Statistics (NCVHS) • Consolidated Health Informatics (CHI) • ANSI Health Informatics Standards Board (HISB) • etc • Jurisdictional laws and regulations (HIPAA, Medicare Part D (ePrescribing), etc.) • Accepted best practices and recommendations