| Type |
Standard / Implementation Specification |
Standards Process Maturity |
Implementation Maturity |
Adoption Level |
Federally required |
Cost |
Test Tool Availability |
|
Implementation Specification
|
|
Final
|
Production
|
 |
No
|
Free
|
Yes
|
|
Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
Yes
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
 |
No
|
Free
|
Yes
Yes
|
|
Emerging Implementation Specification
|
|
Balloted Draft
|
Pilot
|
Feedback Requested |
No
|
Free
|
N/A
|
= Federal FHIR Action Plan: Marks standards for coordinated federal adoption. See Appendix V: Federal FHIR Action Plan for more details.
| Federal FHIR Action Plan Alignment |
HL7® FHIR® Subscriptions R5 Backport Implementation Guide (Subscriptions IG) - This implementation specification allows clients to request notifications from FHIR servers when events occur. Once a subscription is established, a FHIR server can proactively notify the client when new information is added or existing information is updated within its system.
- ASTP regulation recognizes Subscriptions IG Version 1.1.0 as compatible with FHIR Release 4 (R4) and suitable for addressing health IT needs within the current landscape. The R4 Subscriptions IG includes a subset of the capabilities available in the redesigned R5 version. Implementers interested in these capabilities should consider adopting the R4 specification.
- The R5 Subscriptions framework underwent a significant redesign, introducing topic-based subscriptions, enhanced clarity, greater flexibility, and additional notification types. Looking ahead, ASTP anticipates that the Subscriptions framework will become even more advanced with the release of FHIR Release 6 (R6).
|
| Limitations, Dependencies, and Preconditions for Consideration |
Applicable Security Patterns for Consideration
|
- The listed eHealth Exchange Specification will be deprecated in the future in favor of the emerging IHE DSUB specification and/or the equivalent FHIR profile.
|
- Secure Communication – Create a secure channel for client-to-server and server-to-server communication.
- Secure Message Router – Securely route and enforce policy on inbound and outbound messages without interruption of delivery.
- Authentication Enforcer – Centralized authentication processes.
- Authorization Enforcer – Specifies access control policies.
- Credential Tokenizer – Encapsulate credentials as a security token for reuse (e.g., SAML, Kerberos).
- Assertion Builder – Define processing logic for identity, authorization and attribute statements.
- User Role – Identifies the role asserted by the individual initiating the transaction.
- Purpose of Use – Identifies the purpose for the transaction.
|
Submitted by John Moehrke on
IHE - Document Sharing
The IHE Document Sharing infrastructure is well suited for Publish and Subscribe. See section 3.2.4 Notifications in the white paper on Document Shairng
https://profiles.ihe.net/ITI/HIE-Whitepaper/index.html#:~:text=BPPC%20and%20others-,3.2.4%20Notifications,-The%20XDS%20Profile