Presentation is loading. Please wait.

Presentation is loading. Please wait.

Health IT Standards Committee Workgroup Evolution Discussion

Similar presentations


Presentation on theme: "Health IT Standards Committee Workgroup Evolution Discussion"— Presentation transcript:

1 Health IT Standards Committee Workgroup Evolution Discussion
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage 3 Standards Gaps analysis Health IT Standards Committee Workgroup Evolution Discussion April 24, 2014

2 ONC’s Interoperability Strategy
Support the success of MU1 and MU2 Continue to expand the value of the portfolio of standards to support ACOs, payment reform, DoD/VA systems acquisitions, and other admin priorities Modernize standards portfolio to include newer, simpler & more powerful standards

3 Office of Standards and Technology Guiding Principles
Leverage government as a platform for innovation to create conditions of interoperability Health information exchange is not one-size-fits-all; create a portfolio of solutions that support all uses and users Build in incremental steps – “don’t let the perfect be the enemy of the good” ONC’s operating principles for standards development and interoperability arethree-fold: Do what government does best – use our powers of convening to help bring together members of the health IT community to prioritize and develop solutions to common health IT challenges. Rather than doing what we THINK is right – gather the community and have them TELL us what is right. We need to make sure we are creating a portfolio of solutions, because different health IT users will have different uses and needs for interoperable health information exchange. Make sure that all interests are considered. Finally, don’t let the perfect be the enemy of the good…we have to build incrementally or we will never get anywhere!

4 Standard Interoperability “Building Blocks”
Vocabulary How should well-defined values be coded so that they are universally understood? Data Structure How should the message be formatted so that it is computable? Transport How does the message move from A to B? NOTE: the IEEE definition of INTEROPERABILITY is the EXCHANGE of INFORMATION and then the USE OF THAT INFORMATION to support patient care, research, etc. We break down the foundations of interoperability into what we call “Standards building blocks.” Building blocks for Health IT can be broken into 4 areas: Security and transport: Syntactic Interop Content Structure and Vocab: Semantic Interoper Security How do we ensure that messages are secure and private? Services How do health information exchange participants find each other?

5 Proposed HITSC Workgroup Evolution
Steering Committee Vocabulary and Information Models Health IT Standards Committee Chair: Jon Perlin Vice Chair: John Halamka Document and Data Structure Transport and Security Services and APIs Certification and Testing

6 Coordination between HITPC/HITSC
HITSC members will be identified to participate in HITPC workgroups HITPC members will be identified to participate in HITSC workgroups Cross membership will help ensure continuity across committees

7 Use Case: Patient Generated Health Data (PGHD)
Recommendations approved by HITSC Recommendations reviewed with Steering Cmte Recommendations from Document and Data Structure Workgroup Assigned to the Document and Data Structure Workgroup Type of problem: Content HITPC: Standards to support PGHD? Steering Cmte identifies type of problem to be solved and WG to review

8 Interested in joining a workgroup?
Current members should contact Michelle Consolazio to identify workgroup interests Others interested in participating should apply through the ONC FACA database:


Download ppt "Health IT Standards Committee Workgroup Evolution Discussion"

Similar presentations


Ads by Google