飞利浦Health Level Seven (HL7)接口规范

preview
试读
32页
编程语言
健康医疗
网络
网络
需积分: 0 0 下载量 94 浏览量 更新于2024-10-19 收藏 588KB PDF 举报
本文描述了用于与信息系统接口的HL7编程规范。 HL7在医疗保健领域意味着什么？ 提供一组标准程序，组织使用这些程序将电子健康信息从一个实体传输到另一个实体。健康级别七（HL7）是一个医疗信息标准。 医疗保健中的HL7接口是什么？ HL7接口是医疗软件和硬件之间通信的标准方式。它定义了软件和医疗设备之间如何交换数据。
HA1669 – Vue PACS 12.2.8 HL7 Interface Specifications Rev A Page 1 of 32
HA1669 Rev A
Vue PACS 12.2.8
HL7 Interface Specifications
Part # HA1669
2021-03-26
HA1669 – Vue PACS 12.2.8 HL7 Interface Specifications Rev A Page 2 of 32
HA1669 Rev A
Table of Contents
1 Introduction ............................................................................................................................................ 4
1.1 Who Should Use This Document? ................................................................................................ 4
1.2 IS Link Introduction ....................................................................................................................... 4
2 Communication Protocol and Standard Definitions ............................................................................... 5
2.1 HL7 Messages .............................................................................................................................. 5
2.2 Segments ...................................................................................................................................... 5
2.3 Fields ............................................................................................................................................. 6
2.4 Position (Sequence Within the Segment) ..................................................................................... 6
2.5 Maximum Length ........................................................................................................................... 6
2.6 Data Type ...................................................................................................................................... 6
2.7 Optionality ..................................................................................................................................... 7
2.8 Repetition ...................................................................................................................................... 7
2.9 Message Delimiters ....................................................................................................................... 7
3 General Concepts .................................................................................................................................. 9
4 Messages ............................................................................................................................................. 10
4.1 ADT A01 – Admit a Patient ......................................................................................................... 10
4.2 ADT A02 – Transfer a Patient ..................................................................................................... 10
4.3 ADT A03 – Discharge a Patient .................................................................................................. 10
4.4 ADT A04 – Register a Patient ..................................................................................................... 10
4.5 ADT A05 – Pre-admit a Patient ................................................................................................... 11
4.6 ADT A06 – Out-patient to In-patient ............................................................................................ 11
4.7 ADT A07 – In-patient to Out-patient ............................................................................................ 11
4.8 ADT A08 – Update Patient Information ....................................................................................... 11
4.9 ADT A11 – Cancel Admit/Visit Notification ................................................................................. 11
4.10 ADT A12 – Cancel Patient Transfer ............................................................................................ 12
4.11 ADT A13 – Cancel Patient Discharge ......................................................................................... 12
4.12 ADT A18 – Merge Patient Information ........................................................................................ 12
4.13 ADT A23 – Delete a Patient Visit ................................................................................................ 12
4.14 ADT A24 – Link Patients ............................................................................................................. 12
4.15 ADT A28 – Add Person Information ............................................................................................ 12
4.16 ADT A31 – Update Person Information ...................................................................................... 12
4.17 ADT A34 – Merge Patient Information – Patient ID Only ............................................................ 13
4.18 ADT A35 – Merge Patient Information – Account Number Only ................................................. 13
4.19 ADT A37 – Unlink patients .......................................................................................................... 13
4.20 ADT A38 – Cancel Patient Pre-admission .................................................................................. 13
HA1669 – Vue PACS 12.2.8 HL7 Interface Specifications Rev A Page 3 of 32
HA1669 Rev A
4.21 ADT A45 – Move Visit Information .............................................................................................. 13
4.22 ORM O01 – General Order Message ......................................................................................... 13
4.23 ORU R01 – Observational Results ............................................................................................. 14
5 Segments ............................................................................................................................................. 15
5.1 MSH – Message Header ............................................................................................................. 15
5.2 PID – Patient Identification and Details ....................................................................................... 15
5.3 PV1 – Patient Visit Details .......................................................................................................... 17
5.4 MRG – Merge Information ........................................................................................................... 19
5.5 ORC – Order Control Segment ................................................................................................... 21
5.6 OBR – Order Segment ................................................................................................................ 22
5.7 PR1 – Procedure Segment ......................................................................................................... 25
5.8 IN1 – Insurance Segment ........................................................................................................... 25
5.9 OBX – Observation/Report Segment .......................................................................................... 26
5.10 MSA – Message Acknowledgement Segment ............................................................................ 27
5.11 ZDS Segment .............................................................................................................................. 27
5.12 ZLK Segment .............................................................................................................................. 28
5.13 ZAO Segment.............................................................................................................................. 28
5.14 ZEB Segment .............................................................................................................................. 29
5.15 ZAP Segment .............................................................................................................................. 30
5.16 ZAV Segment .............................................................................................................................. 30
6 Queries ................................................................................................................................................ 31
6.1 QBP Q23 – Get Corresponding Identifiers .................................................................................. 31
6.2 RSP K23 – Corresponding Patient Identifiers ............................................................................. 31
HA1669 – Vue PACS 12.2.8 HL7 Interface Specifications Rev A Page 4 of 32
HA1669 Rev A
1 Introduction
This document describes IS Link HL7 dialect for interfacing with information systems.
1.1 Who Should Use This Document?
This document is intended for customers.
1.2 IS Link Introduction
IS Link includes two main processes:
1. Listener process—Receives HL7 messages from a RIS, usually via an interface engine, and
stores it in a message queue in IS Link’s database. The listener uses the HL7 Start-Stop
communication protocol. It expects to receive messages on the TCP/IP socket where the start of
a message is signaled by start bytes (header) and the end of the message is signaled by stop
bytes (trailer). These can be configured in the configuration file.
2. Converter process—Fetches HL7 messages from the message queue and processes them. This
process separates the message into segments according to a segment separator (a byte contains
0x0D) and parses the segments according to the syntax described in this document.
HA1669 – Vue PACS 12.2.8 HL7 Interface Specifications Rev A Page 5 of 32
HA1669 Rev A
2 Communication Protocol and Standard Definitions
IS Link HL7 interface is based on version 2.3.1 of the HL7 standard.
IS Link is a server application. It waits on a specified port for TCP/IP connections from clients (usually a
RIS). After establishing the connection, the client application sends IS Link HL7 messages. IS Link uses
the HL7 “Minimal Lower Layer Protocol” as described in section C.4 of appendix C – “Lower Level
Protocols” in the HL7 (version 2.3.1) Implementation Support Guide.
Note: The V2.3 Implementation Support Guide, which is from Health Level Seven International, is
available on the Internet with the proper login information.
Each HL7 message is sent over the TCP/IP connection as byte buffer enclosed by special characters to
form a block. The format is as follows:
<SB>dddd<EB><CR>
<SB> Start Block character (1 byte)—ASCII <VT>, i.e., 0x0B in hexadecimal.
dddd Data bytes (variable number of bytes). This is the HL7 data content of the block (the HL7
message itself). The data can contain any displayable ASCII characters and the carriage
return character, ASCII <CR>, 0x0D in hexadecimal that serves as a separator between
HL7 segments.
<EB> End Block character (1 byte)—ASCII <FS>, i.e., 0x1C in hexadecimal.
<CR> Carriage Return (1 byte)—The ASCII carriage return character, i.e., 0x0D in
hexadecimal.
2.1 HL7 Messages
A message is the smallest 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. For example, the ADT Message type is used
to transmit portions of a patient’s Patient Administration (ADT) data from one system to another. A three-
character code contained within each message identifies its type.
The real-world event that initiates an exchange of messages is called a trigger event. See section 2.2.1
“Trigger Events” of the HL7 2.3 Standard Specifications for more a detailed description of trigger events.
These codes represent values such as “A patient is admitted” or “An order event occurred.”
Note: The V2.3 Implementation Support Guide, which is from Health Level Seven International, is
available on the Internet with the proper login information.
There is a one-to-many relationship between message types and trigger event codes. The same trigger
event code may not be associated with more than one message type.
2.2 Segments
A segment is a logical grouping of data fields. Segments of a message may be required or optional. They
may occur only once in a message or they may be allowed to repeat.
Each segment is given a name. For example, the ADT message may contain the following segments:
• Message Header (MSH)
• Event Type (EVN)
• Patient ID (PID)
• Patient Visit (PV1).
Each segment is identified by a unique three-character code known as the Segment ID.

剩余31页未读，继续阅读

资源推荐
资源评论
多年菜鸟
  • 粉丝: 2
  • 资源: 1
上传资源 快速赚钱
voice
center-task 前往需求广场，查看用户热搜

最新资源