Term
| HL7 Organization Definition |
|
Definition
| Health Level Seven is one of several American National Standards Institute (ANSI) -accredited Standards Developing Organizations (SDOs) operating in the healthcare arena. Most SDOs produce standards (sometimes called specifications or protocols) for a particular healthcare domain such as pharmacy, medical devices, imaging or insurance (claims processing) transactions. Health Level Seven’s domain is clinical and administrative data |
|
|
Term
|
Definition
HL7 provides a method for disparate systems to communicate clinical and administration information in a normalized format with acknowledgement of receipt.
Vast majority of HL7 messaging done using approximately
HL7 2.3 or HL72.3.2 (HL7 2.x standard for moving data, HL7
3.0 and CCD standards for moving documents. |
|
|
Term
|
Definition
| American Standard Code for information interchange, No formatting (Bolding, Italics, Color, Fonts), Represents letters as numbers, 127 codes |
|
|
Term
|
Definition
HL7 is written from the assumption that an event in the real world of healthcare creates the need for the exchange of data between systems
Mine: Trigger events are events that register (ADT – admission discharge transfer – the most common type of message) and would want to send this over to an interface engine. This would trigger a discharge (Trigger event is the event that makes the thing happen) |
|
|
Term
|
Definition
| the is the automatic unit of data transferred between systems. It is comprised of a group of segments in a defined sequence. Each message has a message type that defines its purpose |
|
|
Term
|
Definition
| a logical group of fields in a defined sequence |
|
|
Term
|
Definition
|
|
Term
|
Definition
| are special character used to indicate segment termination, field, component, sub-component and repletion separation and escape character |
|
|
Term
| The 3 most common Message Types are: |
|
Definition
- Admission, Discharge, and Transfer (ADT)
- Order Entry (ORM)
- Ancillary Data Reporting (ORU) |
|
|
Term
|
Definition
| a data dictionary for the format of message segment |
|
|
Term
|
Definition
- Every HL7 message is made up of two or more HL7 segments
- Every HL7 message has an MSH segment
- Every HL7 segment ends with a carriage return ◄ Since the - carriage return is a ASCII code 13
- (non printable character), you will not see it when viewing the message |
|
|
Term
| MSH Segment (Message Header) |
|
Definition
- Every HL7 message has an Message Header Segment (MSH) segment
- The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message.
- The MSH also contains the Message Control ID (MCI). The MCI is used to acknowledge a receipt of an HL7 message. This will be discussed in more detail. |
|
|
Term
|
Definition
- Admission, Discharge, and Transfer (ADT)
- Send patient demographic, visit, insurance, and diagnosis information typically from Admissions (ADM)
- Every HL7 message is generated based on an Event Trigger.
The most common HL7 Interface is the ADT |
|
|
Term
| ORM Segment (Order Entry) - ORM are used to send |
|
Definition
Order Entry
- Radiology Orders
- Order Entry (OE) Orders
- ORM events are triggered on NEW, CANCEL, EDIT, HOLD, REACTIVATE
- Laboratory Orders (MIC/BBK/PTH/LAB) |
|
|
Term
| ORU Segment: ORU are used to send |
|
Definition
Results:
- Radiology Reports
- Department Reports
- Nursing Results
- Laboratory Results (MIC/BBK/PTH/LAB)
- ORU Events are triggered by NEW, CANCEL, or UPDATE. |
|
|
Term
|
Definition
- 2.X is for data ONLY and in ASCI very simple and vanilla
- Version 3.x is a departure from the 2.x version in how the messages are formatted, but does offer some advantages for Web publishing and self documenting.
- Version 3.x is based on XML, which is a Web based language.
- Version 3.x is NOT backward compatible
- Most organizations use 2.x if legacy system interfaces are required |
|
|
Term
| Meaningful use Stage I allowed for |
|
Definition
|
|
Term
| Meaningful use Stage II allowed for |
|
Definition
|
|
Term
| HL7 Clinical Document Architecture (CDA) |
|
Definition
- A document markup standard that specifies structure and semantics of Clinical documents for the purpose of exchange HL7 release 2
- Focuses on document exchange not message exchange
- A document is “packaged” inside a message during exchange |
|
|
Term
|
Definition
–sets the context for the clinical document as a whole:
- enables clinical document exchange across and within institutions
- facilitates clinical document management
- facilitates compilation of and individual patient’s clinical document into a electronic patient record |
|
|
Term
|
Definition
| contains the clinical report and and can contains an unstructured “blob” or structured content organized in one or more Sections |
|
|
Term
|
Definition
| allow “human-readability” of a CDA document. Within a document section, the narrative block represents content to be rendered for viewing |
|
|
Term
|
Definition
| allow “machine readability” (e.g. decision support applications). Within a document section, an entry represents structured content for further computer processing |
|
|
