| Proposed Specification | NotesDescription | ReleaseStatus | 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. | | | | HL7 EPS, OMG DDS | |
| Event Model | Common way to represent events | | | | | |
| Initial Set of Event Definitions | An initial set of event types defined by a common terminology | | | | |
| Communication |
| Alerts/Notifications | Define a way for platform consumers to raise (write) alerts and/or notifications inside the platform/EHR. | | | HL7 UCOM | |
| Security |
| Server-to-server Authorization | Allows for headless interactions between application and platforms/EHRs | | | | OAUTH2 | |
| Validation |
| Conformance check | Performs a syntactic validation on a Resource, checking for conformance against a structural definition | | MEDIUM | | | | |
| Transreption | Converts a resource from a model to another, preserving the semantics of its content | | | | |
| Care Coordination |
| Master Patient Index | Allows to link records between different (EHR) systems | | | | |
| CDS |
| Knowledge Module Repository | A store for common knowledge artifacts - rules, quality measures, terminologies, etc.. | | | | |
Knowledge Module Specification | Common format(s) for sharing knowledge | | | | |
| CDS Interface and Protocols | Invoke CDS logic on a (fragment of the) patient record | | | HL7 DSS | |
| Terminology |
| Terminology server | Resolve coded concepts, valuesets and post-coordinated expressions | | | CTS-2 | |