HSPC Architecture Workgroup

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

The architecture informs the current version of the HSPC Technical Specification, which implements the architectural principles defined by this Workgroup using open, state of the art technologies.

HSPC Architecture Roadmap Proposals

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
Interaction
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
Task Management	Traces and manages tasks (e.g. orders), including escalation and delegation
*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
Identity Management
Record linkage	Correlates records (entries), discovering identities	PROPOSED			HL7 IS/IXS
Directory	Manage an organization's entities and roles				LDAP
Knowledge / Content Management
Knowledge 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 Terminology Service	Most clinical applications, tools and services

Vertical functional service specifications:

Proposed Specification	Description	Status	Implementations	Related Standards
*Security*
Patient Consent	Filter patient data based on informed consent
Care Coordination
Master Patient Index	Tracks different views of the same patient across multiple systems
Clinical Pathways and Plans
Pathway Eligibility	Determines whether a patient is a candidate for enrollment
Pathway Enrollment	Coordinates workflow to ensure a patient is enrolled
Pathway Monitoring	Monitors a patient for compliance w.r.t. a clinical pathway. Positions a patient w.r.t. the expected course of care, detects deviations and recommends next steps
Decision Support
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
Validation
Common Profiles	PROPOSED	CIMI
*Clinical Quality*
Common Alerts / Reminders
Common Order Sets
Common Cohort Definitions
Common Quality Measures
*Terminology*
Common Terminology Systems			SNOMED-CT, LOINC, RxNORM