Exchanging Immunization Data with Immunization Registries

Type	Standard / Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally required	Cost	Test Tool Availability
Implementation Specification	HL7® 2.5.1 Implementation Guide for Immunization Messaging, Release 1.4	Final	Production		Yes	Free	No
Implementation Specification	HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5	Final	Production		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, and obtain a jurisdictional implementation guide if applicable. There is near universal adoption of the transport standard CDC-EHR-IIS Interoperability Enhancement Project Transport Layer Protocol Recommendation Formal Specification, Version 1.2, though stakeholders should still confirm accepted processes with the health department in their jurisdiction. HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5 – Addendum is also available..	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.

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, and obtain a jurisdictional implementation guide if applicable.
There is near universal adoption of the transport standard CDC-EHR-IIS Interoperability Enhancement Project Transport Layer Protocol Recommendation Formal Specification, Version 1.2, though stakeholders should still confirm accepted processes with the health department in their jurisdiction.
HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.5 – Addendum is also available..

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.

Comment

Submitted by mbkurilo@immre… on 2023-10-06

AIRA Comments on Exchanging Immunization Data

AIRA recommends that the following statement be updated:

“…and determine which transport methods are acceptable for submitting immunization registry data as there may be jurisdictional variation or requirements.”

We have validated through our testing that there is near universal IIS adoption of the preferred transport standard referenced here: https://www.healthit.gov/isa/transport-immunization-submission-and-queryresponse. We would recommend that the statement acknowledge this wide adoption and link to the standard above.

Submitted by mbkurilo@immre… on 2023-10-06

AIRA Comments on Exchanging Immunization Data

AIRA recommends that the following statement be updated:

“…and determine which transport methods are acceptable for submitting immunization registry data as there may be jurisdictional variation or requirements.”

Submitted by csnewman on 2022-09-29

Adoption level for Release 1.5

The Release 1.5 implementation guide is widely adopted and should rate a 5 on the scale.

Submitted by chris.baumgart… on 2022-09-20

WA State Dept. of Health - Immunizations Comment

Washington State Department of Health appreciates having the standards listed on the “Exchanging Immunization Data with Immunization Registries” page and does not have any recommended changes at this time.

Submitted by mbkurilo@immre… on 2022-05-06

AIRA Comments - Adoption Level

AIRA recommends the adoption level of 1.5 to be all 5 bullets (high or widespread adoption). As of 12/31/2020 – the latest CDC published data from the IIS Annual Report, there were just over 121,000 live HL7 V2 interfaces.

Submitted by chris.baumgart… on 2021-09-29