1 / 9

HITSC Workgroups and Chairs

HITSC Workgroups and Chairs. Steering Committee Chair: John Halamka Co-chair: TBD. Semantic Standards Co-chair: Jamie Ferguson Co-chair: Becky Kush. Health IT Standards Committee Chair: Jacob Reider Vice Chair: John Halamka. Content Standards Chair: Andy Wiesenthal

heller
Télécharger la présentation

HITSC Workgroups and Chairs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HITSC Workgroups and Chairs Steering Committee Chair: John Halamka Co-chair: TBD Semantic Standards Co-chair: Jamie Ferguson Co-chair: Becky Kush Health IT Standards Committee Chair: Jacob Reider Vice Chair: John Halamka Content Standards Chair: Andy Wiesenthal Co-chair: Rich Elmore Transport and Security Standards Chair:  Dixie Baker Co-chair:  Lisa Gallagher Architecture, Services & APIs Chair: David McCallie Co-chair: Arien Malec Implementation, Certification &Testing Co-chair: Liz Johnson Co-chair: CrisRoss *Task Forces may be needed for specific work assignments

  2. Workgroup Transition Plan DRAFT Architecture, Services & APIs Transport & Security Standards Semantic Standards Content Standards JASON TF NwHIN PT Implementation Implementation, Certification, & Testing Work complete Kick-off workgroup

  3. Appendix: Workgroup Charges

  4. Steering Committee Charge DRAFT • Coordinate and review HITPC policy recommendations to charge HITSC workgroups • Define the standards problems/options posed by the HITPC • Assure that all stakeholder interests are integrated across all workgroups • Assure overall coordination across HITSC workgroups • Report outcomes back to appropriate HITPC workgroups for continuity

  5. Semantic Standards Charge DRAFT • Assure a consistent approach to semantics standards for CEHRT • Identify existing standards (vocabularies and/or information models) that can be leveraged for other uses, while ensuring consistent semantic standards across all use cases • Identify semantic standards requirements for CEHRT • Evaluate new standards or approaches (vocabularies and information models) for representing semantics • Recommend a strategy for maintaining a consistent and sustainable approach to semantic standards • Assure consistent linking of semantic standards and content standards

  6. Content Standards Charge DRAFT • Evaluate current content standards and propose incremental improvements that achieve greater interoperability • Recommend an appropriate balance between optionality and constraints in content standards • Provide recommendation on key standards initiatives, some examples may include: • recommendations regarding FHIR in future HIT standards • support for common data elements (CDEs) • used across use cases • granular data expression • promote structured approaches for patient interventions • genomic data • consumer activity • Evaluate systems and standards that are resilient to big data approaches • Develop a strategy that can accommodate the movement from document-centric standards to data-centric standards

  7. Transport and Security Charge DRAFT • Support standards for security and transport in certification criteria • Support alignment with the National Strategy for Trusted Identities in Cyberspace (NSTIC) • Support standards, examples may include: • securing data at rest • security for application programming interfaces and RESTful approaches that support modular application integration • data segmentation for privacy • digital signature

  8. Architecture, Services and Application Program Interfaces (APIs) Charge DRAFT • Promote the migration to platform independence “application programming interfaces” (APIs) that allow third-party programmers to bridge from existing systems to a future software ecosystem that will be built on top of the stored data • Determine API architectural framework (e.g. presentation layer, middleware layer, semantic layer, data layer, security layer) • Develop an incremental API strategy for open APIs to Standardized APIs • Support migration from interoperability based on “what to build” (specifications) to interoperability based on “how to use” (APIs) • Determine use cases for API portfolio • Be opportunistic in moving toward more APIs, e.g. Leverage the Data Access Framework and Provider Directory activities

  9. Implementation, Certification and Testing Charge DRAFT • Review implementation challenges with existing standards and provide recommendations for how to improve existing standards and testing • Recommend testing methods that support the goals of interoperability and information exchange • Establish recommendations for how to test workflow and usability • Evaluate sustainable and inclusive approaches to certification and test method development

More Related