Operationalizing the HSPC Roadmap

CIMI

Model Development Pipeline

Model Versioning and Governance 

Project based - ....

ACOG/ OPA FPAR 2.0

Skin Wound Assessment

Common Labs

Vital Signs

1,  Intermountain

2. Mitre, Penrad

3. ACOG

4. HL7

1. Lab, VS, PE

2. Cancer Interoperability

3. FPAR

4. KNART

NICU Pilot

CIMI Transformation

Haug

Lario

A general environment that supports the use of models in clinical applications, this will be a part of the tooling allowing developers to specify and configure models of data, events, orders, etc. within their applications.  The authoring environment will:

-  Allow for the creation of new models in a variety of knowledge areas
-  Support different types of users
-  Support the full artifact lifecycle governance 

Conformance and Certification Principles

Determine what needs to be certified as HSPC Conformant

Determine how HSPC will state something is HSPC conformant

Marketplace Resource Advertisement

Marketplace Marketing 

Tooling

• Model Development
• Model Request
• Model Transformation

Baseline services necessary prior to the implementation of new and improved capabilities Services and capabilities assumed at the beginning, to include:  

• Identity: establish means to classify discrete users.
• Authentication: Verifying users are who they say they are.
• Authorization: Confirm users are supposed to have access to the resources requested
• Audit: Record user access to resources and for what purposes.
• Confidentiality: Prevent unauthorized access to information.
• Integrity: guard against unauthorized modification of healthcare information

This milestone merges concepts of electronic patient consent, and choice (individual control of their own information as provided by law).  This typically involves “authorizations” (approvals and/or directions to share and “restrictions” (patient policy restricting access to certain information to authorized persons organizations.).   It also includes “Directions” to healthcare organizations to transmit a copy of their own information to destinations of their choice under patient right of access law.  Electronic patient permissions regarding disclosure of their own protected health information.

1. Implement HAPI FHIR Term Server;
2. Implement SOLOR content

1. Complete
2. In progress

Multiple

• Developers Engineering Space
• Environment Operations and Maintenance
• Providing Educational Resources
• Outreach

Architectural Principles

Platform

Reference Architecture Workstream

Build Marketplace Infrastructure

1. Renew contract. 

Healthcare Community Cloud

Marketplace Community Implementation

Vendor and Provider Neutral Marketplace Requirements

In order to be truly interoperable, data will need to be transformed from a source terminology (standard or proprietary) to a secondary terminology. Applications, including decision support services, will also need to access terminology in order to resolve terms, domains, and term relationships. Translations may also be needed for terminology within knowledge assets. The Terminology Services API will provide open, standards-based methods for handling these terminology functions at run-time.

1. FHIR term services to HAPI FHIR Term Server

1. Complete

1. Rubin 

2. TBD

1. outlines the functions that a KR needs to support, including artifact storage capabilities, metadata requirements, artifact access services,

2. governance policies. 

see Roadmap section...