LIS Interface Manual of BK Series Biochemistry Analyzer-1 [PDF]

Zitiervorschau

BK-200/BK-400/BK-500 Automatic Biochemistry analyzer

HL7 interface instructions

Intellectual property The intellectual property rights of this manual and its corresponding products belong to Jinan Biobase Biotech

Co.Ltd. © 2015 Jinan Biobase Biotech Co.Ltd. reserved all rights (hereinafter referred to as "Biobase") No part of this User's Manual may be reproduced, modified or translated by any person or organization without the written consent of Jinan Biobase Biotech Co.Ltd.

statement Jinan Biobase Biotech Co.Ltd. has the final interpretation of this manual. In response to all of the following requirements, Biobase is considered to be responsible for the safety, reliability and performance of the product, namely: 1 assembly operations, expansion, re-adjustment, improvement and repair are carried out by Biobase authorized personnel; 2 Related electrical equipment in line with national standards; 3 The product is operated according to this instruction manual.

Before using this system, please read it carefully and understand the contents of this interface manual, so that the correct use of the system. Readers of this instruction manual object for the LIS (laboratory information system) development of personnel and other relevant staff need to understand the HL7 interface. Handbook of interface used to guide the LIS system developers to develop the LIS interface, the purpose is to make the LIS system can communicate with the biochemical analyzer system. Developers need to have a certain LIS, HL7 standard knowledge and the ability of network programming. Communication protocol for TCP/IP network layer or Serial port, application layer protocol for the HL7, version 2.3.1. Suggestions on Windows platform using Visual c + +, Visual Basic development tools such as interface development.

E.1 An overview of the interface HL7 is the standardization of health information transmission protocol, is between different applications in the field of medical electronic transmission protocol. HL7 brings together the different vendors to design standard format of the interface between application software, which will allow each medical institutions between heterogeneous systems, data interaction. Initially defined by the United States, it has now been adopted by many countries. Under this interface data transmission format are created according to the HL7 version 2.3.1.

E.1.1 HL7 message structure In HL7 communication protocol, Message is the basic unit of the data exchange between system and each Message has its own Message types, Message type is used to define the Message purpose of triggering events. A message is composed of multiple segments, each segment has a corresponding name, is used to define the content or functionality. And a segment consists of multiple Data fields. A Message in the first paragraph always header section (Message head segment), it pointed out the sending and receiving the program name, Message type, and a unique Message ID number, etc., the next section of the composition is determined by the type of Message. Such as, PID (Patient Identification Data) including the name, address, social security number, etc. A data field and may consist of multiple components. Some messages can be further by the event code segment.

This interface is based on HL7 v2.3.1 to define, details please refer to HL7 Interface Standards Version 2.3.1.

E.1.2 HL7 the underlying protocol Throttling protocol TCP/IP ,Serial port is a word, it does not provide message boundaries. HL7 as upper protocol is based on message, but it also does not provide message termination mechanism. In order to determine the message boundaries, we use the smallest underlying protocol (HL7 Interface Standards Version 2.3.1. This also has a corresponding description). News began to adopt a single character, ending with double characters. Messages sent by the following format: ddddd Among them: = Start Block character (1 byte) ASCII , which is, . Do not get the character SOH or STX of ASCII confused. ddddd = Data (variable number of bytBK) ddddd is the HL7 message,Include only ISO 8859-1 characters (hexadecimal value 20 - FF) and , excluding other controls and characters that can not be printed. = End Block character (1 byte) ASCII , which is, . Do not get the character ETX or EOT of ASCII confused. = Carriage Return (1 byte) ASCII arriage return character,which is .

Minimal Lower Layer Protocol（MLLP） This interface supports the Minimal Lower Layer Protocol (MLLP) of HL7. This protocol is a wrapper for HL7 messages. The MLLP protocol is defined by the HL7 standard specification. The

HL7 message encapsulates a single character for the message and ends with a double character. The HL7 interface uses the default character for the HL7 standard. Start character: Hexadecimal End character: Hexadecimal

E.2 Communication format This interface includes two aspects: transmission of test results and application of sample information. The transmission of test results mainly implements the biochemical analyzer to transmit the sample information and its test results, and control the results to the external system (such as LIS). The way data is transmitted is real-time transmission during testing and batch transmission of historical results. Sample information application refers to the biochemical analyzer from the LIS to obtain the required sample information to the local test. This section will introduce the general syntax of the HL7 interface.

note: If you need a complete and detailed description of the HL7 message syntax, see the HL7 standard provided by the HL7 Standards Committee. Each HL7 message consists of segments that end with . Each segment consists of a three-character segment name and a variable number of fields, consisting of a component and a subcomponent, defining the separators of the constituent elements in the MSH segment of each message. E.g: MSH|^~\&|BIOBASE|BK-200|||20060427194802||ORU^R01|1|P|2.3.1||||0|| UNICODE|||

among them: The five characters after MSH define the delimiters used to distinguish between domains, components, and subcomponents. Although these characters can be any non-text characters, the HL7 standard recommends the following characters:

character |

significance Domain delimiter

^

Component delimiter

&

Subassembly separator

~

Repeat delimiter

\

Escaped characters

The first field of the MSH includes the individual delimiters. Some of the fields behind are empty because they are optional and the HL7 interface does not use it, and detailed domain definitions and selection are described later. Domain 9:

Contains message types and events (ORU, R01)

Domain 10:

Contains a message ID that uniquely identifies the message

Domain 11:

Include processing ID (P for product)

Domain 12:

Define the HL7 version of the message (2.3.1)

For any message, the order of the segments after the MSH segment is specified. The following sections describe these sequences in detail, using these syntax structures to represent segments that are optional or repeated: [] means that the segments are optional. {} Indicates that the segments can be repeated 0 or 1 or more times.

E.2.1 Supported HL7 messages All HL7 messages used by this interface are ORU, ACK, QRY, QCK,DSR. The upload of the test results is as follows:

ORU/ACK: Unsolicited observation report / response. The main role of the ORU ^ R01 message is to use the HL7 to deliver laboratory results, which we use to transmit sample information and its test results to QC results to the LIS system. For the transmission of information and its test results, including the following information: Patient information (patient name, sample number, etc.) Doctor's advice (sample type, check the doctor, test doctor, clinical diagnosis, etc.)

Test result It is a set of messages, each message corresponds to a sample of information (there may be multiple items of test results). The LIS system can use this content as needed. The specific structure is as follows: ORU Observational Results (Unsolicited)

description

MSH

Message header

PID

Patient information

OBR

Observation report

{OBX}

Test results

For transmission test results, include the following information: Item information (item number, item name) QC liquid related information (QC times, QC name, QC batch, etc.) QC date, test results A message will send a QC test. The transmission structure of the QC result is as follows: ORU Observational Results (Unsolicited)

Description

MSH

Message header

OBR

QC Report

ACK^R01: The message is used to respond to the ORU message. The specific structure is as follows: ORU Observational Results (Unsolicited)

Description

MSH

Message header

MSA

Message confirmation

E.2.2 Message segment This section introduces all the fields used in the message segment. Among them, fields with # behind the serial number are the required field set by HL7. We do not omit the unused fields in the message segment for future possible expansion needs.

1. MSH Message Header The first message segment of the HL7 message, start with the MSH segment, typically at the top of the message. The message segment is used to define some of the details of the intent, source, purpose, and message syntax of the message. The MSH segments of this interface use the following fields: No.

The field name

Length

Description

1#

Field Separator

1

Contains the delimiter between the segment ID and the first real field, which defines the field delimiter for the remaining message(|).

2#

Encoding Characters

4

Contains the component separator, repeat separator, escape separator, and subcomponent separators(^~\&).

3

Sending Application

180

Sending terminal application.

4

Sending Facility

180

Empty, preservation. Transmitter device.

5

Receiving Application

180

Receiver application.

6

Receiving Facility

180

Empty, preservation. Receiver device.

7

Date/Time Of Message

26

The time of the current message.

8

Security

40

Empty, preservation. Security

9#

Message Type

7

The type of the message, such as:ORU^R01.

10#

Message Control ID

20

Message Control ID, Uniquely identifies

No.

The field name

Length

Description a message, increments from 1 as the number of messages increases.

11#

Processing ID

3

Processing ID, has been taken P (means product).

12#

Version ID

60

Version ID, HL7 Protocol version: 2.3.1.

13

Sequence Number

15

Empty, preservation. serial number.

14

Continuation Pointer

180

Empty, preservation. Continuous pointer.

15

Accept Acknowledgment

2

Type 16

Application

Empty, preservation. reply receiving type.

2

Acknowledgment Type

The application response type, which means the type of result sending. 0Patient sample test results；1- Calibration results；2- QC results； While, the "1-calibration results" is not supported at present.

17

Country Code

2

Empty, preservation. Country code.

18

Character Set

10

Character set, take UNICODE.

19

Principal Language Of

60

Empty, preservation. Message primary

Message 20

Alternate Character Set Handling Scheme

language. 20

Empty, preservation. Alternate Character Set Processing Scheme.

Note: This section will appear in all messages. In the HL7 message from LIS system to biochemical analyzer, the field value of the third and fourth fields are set by the LIS developers and that for the fifth and sixth field take "BIOBASE" and "BK-200 / BK-400 / BK-500". The tenth and sixteenth field uses integers; all other fields use string types.

2. MSA - message acknowledgment segment The MSA segments of this interface use the following fields: No.

The field name

Length Description

1#

Acknowledgment Code 2

Confirm code, AA for acceptance; AE for error; AR for reject, OK for query, NF for no data, OK and NF only effective for DSR ^ Q03.

2#

Message Control ID

20

The message control ID is the same as the sender's MSH-10.

3

Text Message

80

Text message is a textual description of the event when error or reject happens, which corresponds to the 6th field and can be used to write the error log.

4

Expected Sequence

15

Empty, preservation. Expected serial number.

1

Empty, preservation. Type of confirmation for

Number 5

Delayed Acknowledgment Type

6

Error Condition

delay. 100

Error condition (status code).

The fields of the MSA-6 field are described in the following table: Status code(MSA-6)

Status text(MSA-3)

Success 0

AA Message accepted

Error status code 100

Description / Remarks

Success. AE

Segment sequence

The order of the segments in the

error

message is not correct, or the required segments are missing.

101

Required field missing

A required field is missing in a segment.

Status code(MSA-6)

Status text(MSA-3)

Description / Remarks

102

Data type error

The data type of the field is wrong, such as the number is wrong set as character.

103

Table value not found

Table value is not found, temporarily. Table value is not found, not in use temporarily.

Reject status code 200

AR Unsupported message

The message type is not supported.

type 201

Unsupported event

Event code not supported.

code 202

Unsupported

Processing ID is not supported.

processing id 203

Unsupported version id Version ID is not supported.

204

Unknown key

Unknown keyword identification,

identifier

such as the transmission of non-existent patient information.

205

Duplicate key

Duplicate keyword already exists.

identifier 206

Application record

Transactions cannot be performed at

locked

the application in storage level, such as when a database is locked.

207

Application internal

Unknown internal errors in the

error

application.

Note: This message segment can appear in the ACK ^ R01, QCK^Q02, ACK ^ Q03 messages. The fourth and sixth fields use integers; other fields use string types.

3. PID Patient Identification PID segment is mainly used to build patient information. In the HL7 interface use the following fields: No.

The field name

Length

Description

1

Set ID – PID

10

Confirm different patient message segments

2

Patient ID

20

Empty, preservation. The patient's hospital number.

3#

Patient Identifier List

20

Medical record number.

4

Alternate Patient ID –

20

Bed number

PID 5#

Patient Name

48

The patient's name.

6

Mother’s Maiden

48

Ward and sickroom. Ward and sickroom

Name

are separated by ^. The ward length is 30 and the length of the sickroom is 30.

7

Date/Time of Birth

26

Empty, preservation. Patient's Date of Birth.

8

Sex

1

Gender Male, Send M; Female, Send F; Others, Send O.

9

Patient Alias

48

Empty, preservation. Blood type.

10

Race

80

Empty, preservation. Empty, preservation. Race.

11

Patient Address

106

Empty, preservation. Patient Address.

12

County Code

4

Empty, preservation. County Code(Post code).

13

Phone Number -Home

40

Empty, preservation. Phone Number.

14

Phone Number

40

Empty, preservation. Empty, preservation.

-Business 15

Primary Language

Phone Number -Business. 60

Empty, preservation. Empty, preservation.

No.

The field name

Length

Description Primary Language.

16

Marital Status

80

Empty, preservation. Empty, preservation. Marital Status.

17

Religion

80

Empty, preservation. Empty, preservation. Religion.

18

Patient Account

20

Patient category.

Number 19

SSN Number -Patient

16

Medical insurance account.

20

Driver's License

25

Charge type.

Number – Patient 21

Mother's Identifier

20

Empty, preservation. Mother identifier.

22

Ethnic Group

80

Ethnic Group.

23

Birth Place

60

Empty, preservation. Birth Place.

24

Multiple Birth

1

Empty, preservation. Empty, preservation.

Indicator

The multiple-tire indicator, Y for Yes and N for No.

25

Birth Order

2

Empty, preservation. Birth order, an integer greater than 0.

26

Citizenship

80

Remarks.

27

Veterans Military

60

Empty, preservation. Veterans Military

Status

Status.

28

Nationality

80

Empty, preservation. Nationality.

29

Patient Death Date and

26

Empty, preservation. Patient Death Date

Time 30

Patient Death Indicator

and Time. 1

Empty, preservation. The patient death indicator, Y for Yes and N for No.

Note: The message segment is used only in the ORU ^ R01 message. Age fields in first, twenty fifth use the integer data type; age fields in twenty four,thirty use the boolean data type;other fields use the string data type. 4. OBR Observation Request The OBR section is used to transmit the information related to the doctor's advice information. When the patient sample test result is being transmitted (when MSH-16 = 0), the OBR segment of the interface uses the following fields:

No.

The field name

Length

Description

1

Set ID – OBR

10

Identify different OBR fields.

2

Placer Order Number

22

Requestor's order number, used as sample bar code number.

3

Filler Order Number

22

Executor order number, used as sample number.

4#

Universal Service ID

200

General Service Identifier.use BIOBASE^BK-200/BK-400/BK-500

5

Priority

2

Emergency, Y for Yes and N for No.

6

Requested Date/time

26

Empty, preservation. Requested Date/time.

7

Observation Date/Time

26

Observation Date/Time, Used to check the date / time.

8

Observation End

26

Date/Time

Empty, preservation. Observation End Date/Time.

9

Collection Volume

20

Empty, preservation.Collection Volume

10

Collector Identifier

60

Empty, preservation.Collector Identifier.

11

Specimen Action Code

1

Empty, preservation. Specimen Action Code.

12

Danger Code

60

Empty, preservation. Danger Code.

13

Relevant Clinical Info.

300

Relevant Clinical Info, Information for

No.

The field name

Length

Description clinical diagnosis of patients.

14

Specimen Received

26

Specimen Received Date/Time.

300

Specimen Source, as for sample types, such

Date/Time 15

Specimen Source

as serum, plasma, urine and so on. 16

Ordering Provider

120

Ordering Provider, as for the doctor.

17

Order Callback Phone

40

Used for inspection departments.

60

Sample traits (jaundice, hemolysis, lipid

Number 18

Placer Field 1

blood). 19

Placer Field 2

60

Number of blood bags.

20

Filler Field 1

60

doctor in charge of the case

21

Filler Field 2

60

Treatment department.

22

Result Rpt/Status

26

Empty, preservation.Result Report /State

Change – Date/Time

change-Date / Time.

23

Charge to Practice

40

Empty, preservation. Implementation cost.

24

Diagnostic Serv Sect

10

Empty, preservation. Diagnostic part ID.

ID 25

Result Status

1

Empty, preservation. Result status.

26

Parent Result

200

Empty, preservation. Father doctor's advice result.

27

Quantity/Timing

200

Empty, preservation. Quantity / time.

28

Result Copies To

150

Empty, preservation. Result Copies.

29

Parent

150

Empty, preservation. Father doctor's advice.

30

Transportation Mode

20

Empty, preservation. Transportation Mode.

31

Reason for Study

300

Empty, preservation. Reason for Study.

32

Principal Result

200

Principal Result Interpreter, as for audit

Interpreter

doctor.

No.

The field name

Length

Description

33

Assistant Result

200

Empty, preservation. Assistant Result

Interpreter

Interpreter.

34

Technician

200

Empty, preservation. Technician.

35

Transcriptionist

200

Empty, preservation. Transcriptionist.

36

Scheduled Date/Time

26

Empty, preservation. Scheduled Date/Time.

37

Number of Sample

4

Empty, preservation. Number of Sample

Containers 38

Transport Logistics of

Containers. 60

Collected Sample

Empty, preservation. Transport Logistics of Collected Sample.

39

Collector’s Comment

200

Empty, preservation. Collector’s Comment.

40

Transport Arrangement

60

Empty, preservation. Transport

Responsibility 41

Transport Arranged

Arrangement Responsibility. 30

Empty, preservation. Transportation is scheduled.

42

Escort Required

1

Empty, preservation. Escort Required.

43

Planned Patient

200

Empty, preservation. Planned Patient

44

Transport Comment

Transport Comment.

Ordering Facility Name 60

Empty, preservation. Ordering Facility Name.

45

Ordering Facility

106

Address 46

Ordering Facility

Address. 48

Phone Number 47

Ordering Provider Address

Empty, preservation. Ordering Facility

Empty, preservation. Ordering Facility Phone Number

106

Empty, preservation. Ordering Provider Address.

Note: This message segment is only used in the ORU ^ R01 message. The first, third,thirty seventh field use the integer data type; The nineth field use the floating point data type; the other fields use the string data type.

If the item QC test results is being transmitted (MSH-16 is 1), the field definition is as follows: Leng

No.

The field name

1

Set ID – OBR

10

Confirm different OBR fields.

2

Placer Order Number

22

Requestor's order number, used as sample bar

th

Description

code number. 3

Filler Order Number

22

Executor order number, used as sample number.

4#

Universal Service ID

200

General Service Identifier. Use BIOBASE^BK-200/BK-400/BK-500

5

Priority

2

Empty, preservation.Priority

6

Requested Date/time

26

Empty, preservation. Requested Date/time.

7

Observation Date/Time

26

Observation Date/Time, Used to check the date / time.

8

Observation End

26

Date/Time 9

Collection Volume

Empty, preservation. Observation End Date/Time.

20

Empty, preservation.0-single-point linearity; 1-two-point linearity; 2-point linearity;3-Logistic-Log4P； 4-Logistic-Log5P；5-Exponential 5P； 6-Polynomial 5P ；7-Parabola ；8-Spline 。

10

Collector Identifier

60

Empty, preservation.Collector Identifier.

11

Specimen Action Code

1

The number of calibration fluid

12

Danger Code

60

The code of calibration fluid

13

Relevant Clinical Info.

300

The name of calibration fluid

14

Specimen Received

26

The lot number of calibration fluid

Date/Time 15

Specimen Source

300

The valid period of calibration fluid

16

Ordering Provider

120

Standard concentration of calibration fluid

No.

The field name

17

Order Callback Phone

Leng th 40

Number

Description Calibration fluid concentration level. High-H; medium-M; low-L

18

Placer Field 1

60

Reactivity.

19

Placer Field 2

60

Number of calibration parameters

20

Filler Field 1

60

Calibration parameter value

21

Filler Field 2

60

Empty, preservation.

22

Result Rpt/Status

26

Empty, preservation. Result Report / state

Change – Date/Time

change-Date / Time.

23

Charge to Practice

40

Empty, preservation.Charge to Practice

24

Diagnostic Serv Sect

10

Empty, preservation. Diagnostic part ID.

ID 25

Result Status

1

Empty, preservation. Result status.

26

Parent Result

200

Empty, preservation. Result of Father doctor's advice.

27

Quantity/Timing

200

Empty, preservation. Quantity/Timing.

28

Result Copies To

150

Empty, preservation. Result Copies To.

29

Parent

150

Empty, preservation. Father doctor's advice.

30

Transportation Mode

20

Empty, preservation. Transportation Mode.

31

Reason for Study

300

Empty, preservation. Reason for Study.

32

Principal Result

200

Empty, preservation. Principal Result

Interpreter 33

Assistant Result

Interpreter. 200

Interpreter

Empty, preservation. Assistant Result Interpreter.

34

Technician

200

Empty, preservation. Technician.

35

Transcriptionist

200

Empty, preservation. Transcriptionist.

36

Scheduled Date/Time

26

Empty, preservation. Scheduled Date/Time.

37

Number of Sample

4

Empty, preservation. Number of Sample

No.

The field name

Leng th

Containers 38

Transport Logistics of

Description Containers.

60

Collected Sample

Empty, preservation. Transport Logistics of Collected Sample.

39

Collector’s Comment

200

Empty, preservation. Collector’s Comment.

40

Transport Arrangement

60

Empty, preservation. Transport Arrangement

Responsibility 41

Transport Arranged

Responsibility. 30

Empty, preservation. Transportation is scheduled or not.

42

Escort Required

1

Empty, preservation. Escort Required.

43

Planned Patient

200

Empty, preservation. Arranged patient

Transport Comment

transport notes.

44

Ordering Facility Name 60

Empty, preservation. Ordering Facility Name.

45

Ordering Facility

Empty, preservation. Ordering Facility

106

Address 46

Ordering Facility

Address. 48

Phone Number 47

Ordering Provider Address

Empty, preservation. Ordering Facility Phone Number

106

Empty, preservation. Ordering Provider Address.

Note: The message segment is used only in the ORU ^ R01 message. Column 1, 9, 11, 19, 37 field uses integer data type; field 10 uses floating point data type; other fields use string data type. The contents of fields 12 to 18 are based on the number of calibration liquids in the format V1 ^ V2 ^ ... Vi. The 20th field is based on the number of scaling parameters, and the different values are separated by the separator. Different calibration rules have different calibration parameters. For single-point linear scaling, two-point linear scaling and multi-point linear scaling, there are two calibration parameters K, R0. For Logistic-Log4P, there are four scaling parameters K, R0, a, b. For Logistic-Log5P and Exponential 5P, there are five scaling parameters K,

R0, a, b, c. For Polynomial 5P, there are five scaling parameters R0, a, b, c, d. For Spline, there are 4 * (n-1) scaling parameters R0i, ai, bi, ci. Where n is the number of calibration fluid.

If the item QC test results is being transmitted (MSH-16 is 2), the field definition is as follows: No.

The field name

Length

Description

1

Set ID – OBR

10

Identify different OBR fields

2

Placer Order Number

22

3

Filler Order Number Universal Service ID

22

The requestor's questionnaires are used as item numbers Executor's Doctors, used as project name Generic service identifier, use

4#

200

BIOBASE^BK-200/BK-400/BK -500

6 7 8 9

11 12 13

Priority

2

Empty, preservation. Priority

Requested Date/time Observation Date/Time Observation End Date/Time Collection Volume

26

20

Empty, preservation. Requested Date/time Observation date/time,as for QC time Empty, preservation. Observation end date/time Empty, preservation.

Collector Identifier

60

Empty, preservation.

Specimen Action Code Danger Code

1

QC solution number

60

QC solution code

300

QC solution name

26 26

Relevant Clinical Info. Specimen Received Date/Time Specimen Source

26

lot number of QC solution

300

Valid period of QC solution

16

Ordering Provider

120

Empty, preservation.

17

Order Callback Phone Number

40

18

Placer Field 1

60

QC solution concentration level. High-H; medium-M; low-L Mean value of the control

14

Placer Field 2

60

Filler Field 1

60

solution (average concentration) Standard deviation of QC solution Test results (concentration)

21

Filler Field 2

60

Empty, preservation.

22

Result Rpt/Status Change – Date/Time Charge to Practice

26

Empty, preservation.Result rpt/status change – date/time

40

Diagnostic Serv Sect ID Result Status

10

26

Parent Result

200

27

Quantity/Timing

200

28

Result Copies To

150

29

Parent

150 20

31

Transportation Mode Reason for Study

Empty, preservation.Charge to Practice Empty, preservation. Diagnostic Serv Sect ID Empty, preservation.Result Status Empty, preservation. Father doctor's advice. Empty, preservation. Quantity/timing Empty, preservation.Result copies to Empty, preservation.Father doctor's advice. Empty, preservation. Transportation mode Empty, preservation.Reason for study Empty, preservation.Principal Result Interpreter Empty, preservation. Assistant Result Interpreter Empty, preservation. Technician Empty, preservation. Transcriptionist Empty, preservation. Scheduled date/time Empty, preservation.Number of sample containers Empty, preservation. Transport logistics of

19

23 24

1

300

32

Principal Result Interpreter

200

33

200

34

Assistant Result Interpreter Technician

35

Transcriptionist

200

36

Scheduled Date/Time Number of Sample Containers Transport Logistics of Collected

26

37 38

200

4 60

Sample 39

collected sample

41

Collector’s Comment Transport Arrangement Responsibility Transport Arranged

30

42

Escort Required

1

43

Planned Patient Transport Comment Ordering Facility Name Ordering Facility Address Ordering Facility Phone Number

200

Ordering Provider Address

106

40

44 45 46

47

200 60

60 106 48

Empty, preservation. Collector’s comment Empty, preservation. Transport arrangement responsibility Empty, preservation. Transport arranged or not Empty, preservation.Escort required Empty, preservation.Planned Patient Transport Comment Empty, preservation. Ordering Facility Name Empty, preservation. Ordering Facility Address Empty, preservation. Ordering Facility Phone Number Empty, preservation. Ordering Provider Address

Note: This message field is only used in ORU ^ R01 messages. The first, 11, and 37 fields use integer data types; other fields use string data types. The 12th, 13th, 14th, 15th, 17th, 18th, 19th and 20th fields are in the format of V1 ^ V2 ^ ... Vi. It should be noted that, for daytime quality control, each quality control test to form a message to send. And real-time and day quality control, it is a number of quality control tests together to form a message to send. 5. OBX Observation OBX is primarily used to pass observed information in a report message. If the sample information is transmitted (when MSH-16 = 0), a patient may have more than one OBXs. The OBX segment of this interface uses the following fields:

No.

The field name

Length

Description

1

Set ID – OBX

10

Identify different OBX fields.

2

Value Type

3

Value type.

No.

The field name

Length

Description The type used to identify the test result, NM (numeric), represents a numeric value; used to quantify items ST (string) Represents a string value; Used for qualitative test.

3#

Observation Identifier

590

The observation identifier is used as the item ID number.

4

Observation Sub-ID

20

Observation Sub-ID,As for the item name

5

Observation Value

65536

Observation Value As for test result values (result concentration or negative, positive, etc.).

6

Units

90

Units, As for the unit for checking the result value.

7

References Range

90

References Range, Check the value of the normal range.

8

Abnormal Flags

5

Abnormal Flags, To check test results normal or not(description), L for low, H for high and N for normal.

9

Probability

5

Empty, preservation. Probability.

10

Nature of Abnormal

2

Empty, preservation. Nature of Abnormal

Test

Test

11#

Observe Result Status

1

Observe Result Status. Take F-final results

12

Date Last Observe

26

Empty, preservation. Last Date when

Normal Values 13

User Defined Access

Observe the normal values. 20

Checks 14

Date/Time of the

original result. 28

Observation 15

Producer's ID

Date Last Observe Normal Values, as for

Date/Time of the Observation, Used to detect date / time.

60

Empty, preservation.Producer's ID.

No.

The field name

Length

Description

16

Responsible Observer

80

Responsible Observer, laboratory physician.

17

Observation Method

60

Empty, preservation. Observation Method.

Note: This message field appears only in the ORU ^ R01 message. Fields 1, 3, and 9 use integer data types; fields 5 and 13 use floating point data types; other fields use string data types. Need note that when the SI project is tested, the format of the 5th and 13th fields is the result 1 ^ result 2 ^ result 3, where the result 1 is turbidity (L), the result 2 is hemolysis (H), the result 3 is Jaundice (I), respectively, the SI project of the three results. 6. QRD - query definition segment The QRD section of this interface uses the following fields: No.

The field name

Length

Description

1#

Query Date/Time

26

The query time, take the system time

2#

Query Format Code

1

Query format code, take R (record-oriented formate).

3#

Query Priority

1

Query priority, take D (deferred).

4#

Query ID

10

Query ID, characterization of different queries, with the number of queries from 1 increase.

5

Deferred Response

1

Type 6

Deferred Response

type. 26

Date/Time 7#

Quantity Limited

Empty, preservation. Delayed response

Empty, preservation. Deferred Response Date/Time.

10

Request

Quantitative limit request, take RD (Records).

8#

Who Subject Filter

60

Who Subject Filter. as the sample bar code.

9#

What Subject Filter

60

Query content filter.set OTH when query, set CAN when canceled

10#

What Department Data

60

Empty, preservation. Department Data

No.

The field name

Length

Code 11

What Data Code Value

Description Code

20

Empty, preservation.Data Code Value Qual.

1

Empty, preservation. Query result level,

Qual. 12

Query Results Level

take T (Full results). Note: The message segment may appear in the QRY ^ Q02 message and the DSR ^ Q03 message. The 8th field is the sample barcode number in real time and is empty when batch is fetched. Field 4 is an integer data type; other fields use string data types. 7. QRF - query filter segment The QRF segment is used in conjunction with QRD to further refine the original query content. The QRF segment of this interface uses the following fields:

No.

The field name

Length

Description

1#

Where Subject Filter

20

Querier Location Filter.take BK-200/BK-400/BK-500

2

When Data Start

26

Date/Time

Record start date / time. Used as the beginning of the sample receiving time at query time.

3

When Data End

26

Date/Time

Record end date / time. Used as the ending of the sample receiving time at query time.

4

What User Qualifier

60

Empty, preservation. User Qualified logo.

5

Other QRY Subject

60

Empty, preservation. Other QRFs accept

Filter 6

Which Date/Time

the filter character. 12

Qualifier

Target type, take RCT（Specimen receipt date/time, receipt of specimen in filling ancillary (Lab)）.

7

Which Date/Time

12

Target state, take COR（Corrected only (no

No.

The field name

Length

final with corrections)）.

Status Qualifier 8

Date/Time Selection

12

Date / Time selection qualifier, take ALL （All values within the range）.

Qualifier 9

Description

When Quantity/Timing

60

Empty, preservation. Time interval.

Qualifier Note: This message segment appears in the QRY ^ Q02 and DSR^Q03 message. The third and fourth fields are querying zero point and the time when the query occurs, to be used as the query time interval conditions. All fields use the string type. 8. ERR - error segment The ERR segment is used to add an error description to the acknowledgment message. The ERR segment of the HL7 interface uses the following fields:

No. 1#

The field name Error CodeLocation

and

length

Description

80

Error code and location

Note: The message segment may be in the QCK ^ Q02, DSR ^ Q03 or ACK ^ Q03 messages (see the message error status code table for details). The message field has only one field, using the integer data type. 9. QAK - query acknowledgment segment The QAK segment contains some information following the query response, and the QAK segment of the HL7 interface uses the following fields: No.

The field name

length Description

1

Query Tag

32

Query mark, take SR (that is the sample application information)

2

Query Response Status

2

Query the response status OK：Data found, no errors NF：No data found, no errors

AE：Application error AR：Application reject

Note: The message segment appears in the QCK ^ Q02 and DSR ^ Q03 messages. All fields use string data types.

E.3 Example of Communication E.3.1Process of sending test data The biochemical analyzer sends sample information and test results to the LIS server in units of samples. That is, a sample and its included test results are sent together as a message. After determining the message, LIS server makes the appropriate response.

Among them, the ORU message contains segments with MSH, PID, OBR, OBX (if a sample contains multiple items, then there are multiple OBX segments. The MSH is the message header, which is contained in any message.An example of its formatting is as follows (the text in parentheses in each field is the interpretation language, the non-field itself): MSU | ^ ~ \ BIOBASE (Manufacturer name) | BK-200 (device model) | 20120423101830 (system time, format yyyymmddhhMMss) || ORU ^ R01 (message type) | 1 (message control ID, (From fixed value, indicating product) | 2.3.1 (version number of HL7 protocol used) |||| 0 (sample test result is 0, other home space) | | UNICODE (character set) ||| Note: In all of the following message examples, if the 14-digit field is in the field representing time, the time format is year (4 digits) month (2 digits) day (2 digits) (2 digits) ) Seconds (2 digits); for 8 digits, the time format is year (4 digits) month (2 digits) day (2 digits).

Assuming that there is a patient, the information is as follows: Field Meaning

Value

Patient name

Mike

Gender

Male

Date of birth

1985.10.1

Sample barcode

12345678

Sample Type

serum

Sample number

10

Whether emergency or not

Yes

Item Number

2、5、6

Item name

TBil、ALT 、AST

Date of submission

2011/03/21

Test result

100、98.2 、26.4

Result unit

umol/L、umol/L、umol/L

The ORU ^ R01 message sent to the LIS server is:

1-Company Name;

2-Equipment model;

3-system time;

4-Message type;

5-Message Control ID, which represents the unique ID of the message, is incremented from 1, and the original number in the reply message is returned; 6-Product label;

7-HL7 version;

8-Sample test results;

9-Character Encoding;

10-Patient name;

11-Date of birth;

12-gender;

13-Sample barcode;

14-Sample number, internal using without being resolved; 15 - Emergency sign;

16 - Test date/time;

17-Sample type; 18-Quantitative items; 19-Item number, string, has been converted, is the server-side number; 20-Project name, similar to the annotation function, do not have to resolve; 21-Test result; 23-Original results;

22-Item unit; 24-Test date / time

After receiving the message, LIS server will first determine the legitimacy of the message and the message type, and then make the appropriate response. The following is a normal response:

1-Message type: ORU message response;

2-The message is accepted;

3-Text message, annotation;

4-error code

If the LIS server checks for errors in the received ORU message, you can set the corresponding error code in the MSA segment. The biochemical software will do the error and give an alarm. If the LIS server has a deny error of code 206, the ACK message for its response is:

1-Message type: ORU message response;

2-The message is accepted;

3-Text message, annotation;

4-error code