| 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. | | HSPC | | HL7 EPS, OMG DDS,
(FHIR Subscription model) | |
| 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.. | | | | HL7 UCOM | |
| 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 | | HSPC | | OAUTH2 | |
| 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 | | | | FHIR SD, (W3C ShEx) | |
| 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) systemsIdentity Management |
| Record linkage | Correlates records (entries), discovering identities | | | | HL7 IS/IXS | |
| Knowledge / Content Management |
| Knowledge Module Repository | A store for common knowledge artifacts - rules, quality measures, terminologies, etc.. | | | | | |
| Terminology |
| Terminology server | Resolve coded concepts, valuesets and post-coordinated expressions | | | | OMG CTS-2,
(FHIR ValueSet model) | |