Sending a Notification of a Patient’s Admission, Discharge and/or Transfer Status to Other Providers

Type	Standard / Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally required	Cost	Test Tool Availability
Standard	HL7® 2.5.1 (or later) ADT message	Final	Production		No	Free	No
Implementation Specification	IHE Patient Administration Management (PAM) Integration Profile	Final	Feedback requested	Feedback Requested	No	Free	No
Implementation Specification	HL7 FHIR® DaVinci Unsolicited Notifications Implementation Guide	Balloted Draft	Pilot		No	Free	No
Implementation Specification	Event Notifications via the Direct Standard™	Balloted Draft	Pilot	Feedback Requested	No	Free	No
Emerging Implementation Specification	Carequality Subscription Implementation Guide for Push Notifications	In Development	Pilot	Feedback Requested	No	Free	No

Limitations, Dependencies, and Preconditions for Consideration	Applicable Security Patterns for Consideration
A variety of transport protocols are available for use for ADT message delivery. Trading partners will need to determine which transport tools best meet their interoperability needs, however, Direct (referenced further in Exchange/Services - "Push" Exchange), has been noted as a prominent option for transport, particularly where HIE networks are not in place or not being used for this purpose. DirectTrust Standards Implementation Guide "Event Notifications via the Direct Standard" provides a profile for the payload included in event notifications when Direct is the transport. The guide standardizes HL7 2.5.1 usage and maps metadata elements to support appropriate routing and workflow for receiving systems. Human readable text is also stipulated as a part of the specification to support uncomplicated edge systems. The Implementation Guide is expected to go to final ballot in 2021. 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.

Limitations, Dependencies, and Preconditions for Consideration

Applicable Security Patterns for Consideration

A variety of transport protocols are available for use for ADT message delivery. Trading partners will need to determine which transport tools best meet their interoperability needs, however, Direct (referenced further in Exchange/Services - "Push" Exchange), has been noted as a prominent option for transport, particularly where HIE networks are not in place or not being used for this purpose.
DirectTrust Standards Implementation Guide "Event Notifications via the Direct Standard" provides a profile for the payload included in event notifications when Direct is the transport. The guide standardizes HL7 2.5.1 usage and maps metadata elements to support appropriate routing and workflow for receiving systems. Human readable text is also stipulated as a part of the specification to support uncomplicated edge systems. The Implementation Guide is expected to go to final ballot in 2021.
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.

Comment

Submitted by kwboone on 2017-11-20

Consider IHE Patient…

Consider IHE Patient Administration Management profile for this message: http://wiki.ihe.net/index.php/Patient_Administration_Management

About the ISA

ISA Content

ISA Sections

Appendices

Specialty Care and Settings

ISA Publications

Recent ISA Updates

Sending a Notification of a Patient’s Admission, Discharge and/or Transfer Status to Other Providers

Comment

Consider IHE Patient…