HSPC Technical Specification Workgroup

The HSPC Technical Specifications details the requirements to which implementing HSPC enabled applications and platforms adhere. This is a collaborative space to further the work of the spec.

Current version of the HSPC Technical Specification.

HSPC Technical Specification Project Roadmap Proposal

Horizontal functional service specifications:

Proposed Specification	Description	Status	Implementations	Priority	Related Standards	Use Cases
Eventing
Publish & Subscribe	Common mechanism for platforms to publish and consumers to subscribe to useful events occurring inside the platform/EHR.	ACTIVE	HSPC	HIGH	HL7 EPS, OMG DDS, (FHIR Subscription model)	HiMSS 2016 Example Use Cases
Communication
Alerts/Notifications	Define a way for platform consumers to raise (write) alerts, reminders and/or notifications inside the platform/EHR. Should leverage roles, delivery channels, user preferences, etc..	PROPOSED		HIGH	HL7 UCOM	HiMSS 2016 Example Use Cases
*Security*
Server-to-server Authorization	Allows for headless interactions between application and platforms/EHRs	ACTIVE	HSPC	HIGH	OAUTH2	HiMSS 2016 Example Use Cases
Data Obfuscation	Applies policies to ensure no sensitive data is transmitted				XCML
Validation
Conformance check	Performs a syntactic validation on a Resource, checking for conformance against a structural definition	PROPOSED		MEDIUM	FHIR SD, (W3C ShEx)
Transreption	Converts a resource from a model to another, preserving the semantics of its content	PROPOSED
Care Coordination
Master Patient Index	Allows to link records between different (EHR) systems	PROPOSED			HL7 IS/IXS
Knowledge / Content Management
Knowledge Module Repository	A store for common knowledge artifacts - rules, quality measures, terminologies, etc..	PROPOSED
*Terminology*
Terminology server	Resolve coded concepts, valuesets and post-coordinated expressions	PROPOSED			OMG CTS-2, (FHIR ValueSet model)

Vertical functional service specifications:

Proposed Specification	Description	Status	Implementations	Related Standards
Eventing
Communication
*Security*
Patient Consent	Filter patient data based on informed consent
Care Coordination
Knowledge / Content Management
Clinical Decision Support	Invoke CDS logic on a (fragment of the) patient record	PROPOSED	OpenCDS	HL7 DSS
*Terminology*

Content

Proposed Specification	Status	Contributors	Related Standards	Use Cases
Eventing
Common Event Definitions	PROPOSED			HiMSS 2016 Example Use Cases
*Security*
Validation
Common Profiles	PROPOSED	CIMI
Knowledge / Content Management
Common Alerts / Reminders
Common Quality Measures
*Terminology*
Common Terminology Systems			SNOMED-CT, LOINC, RxNORM