Interoperability Need: Reporting Administered Immunizations to Immunization Registry

Interoperability Need: Reporting Administered Immunizations to Immunization Registry
Type	Standard/Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally Required	Cost	Test Tool Availability
Standard	HL7 2.5.1	Final	Production		Yes	Free	No
Implementation Specification	HL7 2.5.1 Implementation Guide for Immunization Messaging, Release 1.4	Final	Production		Yes	Free	Yes
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, 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- serve 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 – specified policies access control. Credential Tokenizer – encapsulate credentials as a security token for reuse (e.g., – SAML, Kerberos). User Role – identifies the role asserted by the individual initiating the transaction. Purpose of Use - Identifies the purpose for the transaction.

No comments have been posted yet.

HealthIT.gov