HL7 ADT messages carry patient demographic information for HL7 communications for Admit, Discharge, and Transfers.
is a flexible health standard which uses the XML language and is unique in that it can be read by the human eye or processed by a machine.
The HL7 standard is often called the “non-standard standard.” While not entirely fair, it does reflect the fact that almost every hospital, clinic, imaging center, lab, and care facility is “special” and, therefore, there is no such thing as a standard business or clinical model for interacting with patients, clinical data, or related personnel.
Whether you build or buy, the process is still essentially the same. If you are considering adding an subsystem to your healthcare application—provider or vendor, the process you need to undertake is essentially the same. The questions below encompass what we believe are the key questions to answer prior to building or buying and then implementing your HL7 subsystem.
Answering these questions will help make your HL7 implementation easier to understand, and less time-consuming, and less costly in the long term.
Although the 2.X messaging standard is the most widely used standard in the United States for the exchange of clinical patient data, it varies greatly in how it is implemented by each medical device and application. Consequently, it is often called the “non-standard standard”. The purpose of HL7 2.X is to provide a framework for negotiation so that each healthcare interface is closer to 20% custom rather than 100%.
Most hospital departments utilize an interfacing application to route and process messages throughout the hospital system. These interfaces are typically built in a point-to-point manner by the hospital IT staff or may be built on an interface engine platform.
Hospitals of all sizes are discovering it can be more productive for an individual department to create and manage its own connections.