proposed hitsc workgroup evolution n.
Skip this Video
Download Presentation
Proposed HITSC Workgroup Evolution

Loading in 2 Seconds...

play fullscreen
1 / 7

Proposed HITSC Workgroup Evolution - PowerPoint PPT Presentation

  • Uploaded on

Proposed HITSC Workgroup Evolution. Steering Committee. Semantic Standards WG (Vocabularies & Information Models). Health IT Standards Committee Chair: Jacob Reider Vice Chair: John Halamka. Content Standards WG (Documents and Data). Transport and Security Standards WG.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Proposed HITSC Workgroup Evolution' - nami

Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
proposed hitsc workgroup evolution
ProposedHITSC Workgroup Evolution

Steering Committee

Semantic Standards WG

(Vocabularies & Information Models)

Health IT Standards Committee

Chair: Jacob Reider

Vice Chair: John Halamka

Content Standards WG

(Documents and Data)

Transport and Security Standards WG

Architecture, Services & APIs WG

Implementation, Certification &Testing WG

*Task Forces may be needed for specific work assignments

steering committee charge
Steering Committee: Charge
  • 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
semantic standards wg charge
Semantic Standards WG : Charge
  • 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
content standards wg charge
Content Standards WG: Charge
  • 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
transport and security charge
Transport and Security: Charge
  • 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
architecture services and application program interfaces apis charge
Architecture, Services and Application Program Interfaces (APIs): Charge
  • 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
implementation certification and testing charge
Implementation, Certification and Testing: Charge
  • 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