Exchanging Immunization Data with Immunization Registries

Printer Friendly, PDF & Email
Type Standard Implementation/Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Standard
Final
Production
Rating 5
Yes
Free
No
Implementation Specification
Final
Production
Rating 5
Yes
Free
Yes
Implementation Specification
Final
Production
Rating 3
Yes
Free
Yes
Limitations, Dependencies, and Preconditions for Consideration Applicable Security Patterns for Consideration
  • Stakeholders should refer to the health department in their state or local jurisdiction to determine onboarding procedures, obtain a jurisdictional implementation guide if applicable, and determine which transport methods are acceptable for submitting immunization registry data as there may be jurisdictional variation or requirements.
  • HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5 – Addendum is also available.
  • See HL7 V2 projects in the Interoperability Proving Ground.
  • 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.

Comments