Interoperability Need: Electronic Transmission of Reportable Lab Results to Public Health Agencies

Interoperability Need: Electronic Transmission of Reportable Lab Results to Public Health Agencies

Interoperability Need: Electronic Transmission of Reportable Lab Results to Public Health Agencies
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 Version 2.5.1: Implementation Guide: Electronic Laboratory Reporting to Public Health (US Realm), Release 1 with Errata and Clarifications and ELR 2.5.1 Clarification Document for EHR Technology Certification	Final	Production		Yes	Free	Yes
*Emerging Implementation Specification*	HL7 Version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 2 (US Realm), Draft Standard for Trial Use, Release 1.1	Balloted Draft	Pilot	Feedback requested	No	Free	No

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 ELR as there may be jurisdictional variation or requirements. Note the Public Health Profile as specified in the HL7 Version 2.5.1 Implementation Guide: S&I Framework Laboratory Results Interface Implementation Guide, Release 1 DSTU Release 2 - US Realmis harmonized with the Lab US Realm suite of Implementation Guides and improves on the ELR emerging implementation specification. Both are scheduled for revision in the HL7 January 2017 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.