0% found this document useful (0 votes)
150 views7 pages

URIT-3010 Protocol (HL7)

The document discusses communication settings and data formats for transferring sample data and analyzer information from an instrument to an external computer. It covers hexadecimal and ASCII formats, including frame formats, field definitions, and message structures.

Uploaded by

william vigoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
150 views7 pages

URIT-3010 Protocol (HL7)

The document discusses communication settings and data formats for transferring sample data and analyzer information from an instrument to an external computer. It covers hexadecimal and ASCII formats, including frame formats, field definitions, and message structures.

Uploaded by

william vigoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Appendix C: Communication

The system transfers sample data and analyzer information to outer computer
through RS-232 COM. This operation can be done automatically after analysis or
manually when the instrument is in idle mode. This appendix explains the
settings of communication parameters and data communication formatter for
easy operation.
Before communication, please ensure the analyzer has connected with outer
computer through appropriate COM.
Communication can be done in hexadecimal format or ASCII format.

1. Hexadecimal Format Communication

1.1 Data Link MAC Sublayer Parameters Convention


Baud Rate: 115200
Parity Digit: None
Data Bit: 8 bits
Stop Bit: 1 bit

1.2 Data Link Layer Frame Format

1.2.1 Frame Format

STX LENGTH Message ETX LRC

1.2.2 Meaning of Each Field or Control Field

Name Meaning Value


STX Start of Text 0x02
ETX End of Text 0x03
Message Sending Message Determine by Message content.
LENGTH Length (2 bytes) Determine by Message length
Determine by the content among
LRC Checksum
STX and ETX, exclude STX.
1.2.3 Convention

Comply with Big-Enddian format, high byte is prior when transferring.


1.3 Message Field Structure

1.3.1 Message Structure

TYPE DATA
Field Definition:
Field Length
1 TYPE 1
2 DATA xx

TYPE Value:
Type Value
TRANS_CONDITION 0x42
1.3.2 DATA Field Definition

DATA Type(1Byte) DATA Content(depends on specific DATA type)

TYPE Value of DATA Field:


DATA Type Value Definition Receive Transmit
CON_TRANS 0x01 Request online status Yes
TRANS_CON 0x02 Transmit online status Yes

DATA Field Content:


If TYPE value of DATA field is TRANS_CON and the opposite party can receive
0x01 message which sent by us, it means online is normal.

2. ASCII Format Communication

2.1 Message Transfer Format


Message transfer formats are <SB> ddddd <EB><CR>.
<SB> means the start of massage and its corresponding ASCII sign is <VT>,
namely 0x0B;
<EB> means the end of message and its corresponding ASCII sigh is <FS>,
namely 0x1C;
<CR> means the confirmation of termination and the field mark of different
message, namely 0x0D;
ddddd is the actual transfer content. It includes several fields, each field will end
with <CR>, namely 0x0D.
2.2 Massage Grammar
| Field mark
^ Component mark
& Child component mark
~ Repeat mark
\ Escape character

2.3 Data Type


CX extended composite id which checks digit
CE code element
CM composite
CQ composite quantity with units
DR datetime range
DT data
DLN driver’s license number
EI entity identifier
HD hierarchic designator
FN family name
FT formatter text
IS coded value for user-defined Tables
ID coded values for HL7 Tables
JCC job code
NM numeric
PT processing type
PL person location
ST string
SI sequence ID
TS time stamp
TQ timing quantity
TX text data
XAD extended address
XCN extended composite ID number and name
XON extended composite name and ID number for organizations
XPN extended person name
XTN extended telecommunications number
VID version identifier

2.4 Message Type

The structure of message is as follows:


MSH //Message Header
{
[PID] //Patient
Data
{
OBR // Medical
Advice
[OBX] //Inspection
Result
}
}

Definition of MSH (Message Header):


Number Field Type Length Remark

1 Field mark ST 1
2 Encoding chars ST 4
3 Sending Application EI 180

4 Sending Facility EI 180


5 Receiving Application EI 180

6 Receiving Facility EI 180


7 DateTime Message TS 26
8 Security ST 40
9 MessageType CM 7
10 Message Control ID ST 20
11 Processing ID PT 3
12 VersinID VID 60
13 Keep
14 Keep
15 Keep
16 Keep
17 Keep
18 Encoder ST Encoding (with UNICODE)

Example:
MSH|^~\&|URIT|UT-3020|LIS|PC|20100930100436||ORU^R01|URIT-
BLD|P|2.3.1||||||UNICODE

Definition of PID(Patient Data) Field:


Number Field Type Length Remark
1 Set ID PID SI 4 Confirm different fields,
generally set 1

2 Patient ID EI 20

3 Patient Identifier List CX 20

4 Alternate Patient ID CX 20

5 PatientName XPN 48
6 Mother Maiden Name XPN 48 Set null

7 Date/Time of Birth TS 26
8 Sex IS 1 M or F
9 Patient Alias XPN 48 Keep
10 Race CE 80 Keep
11 Patient Address XAD 106 Keep
12 County Code IS 4 Keep
13 Phone Number XTN 40 Keep
13 Phone Number Bus XTN 40 Keep
14 Primary Language CE 60 Keep
15 Marital Status CE 80 Keep
16 Religion CE 80 Keep

Basically, the Latter



parts do not need to fill

Example: PID|1|1010051|A1123145|15|Jame||19811011|M

OBR Field:
Number Field Type Length Remark
Confirm different fields,
1 Set ID OBR SI 4
generally set 1 or null
2 Placer Order Number EI 22
3 Assigned Patient Location EI 22
4 Universal Service ID CE 200
5 Priority ID 2 Set null
6 Requested DateTime TS 26
7 ObservationDatetime TS 26
8 Observation DateTime end TS 26 Set null
9 Collection Volume CQ 20 Set null
10 Collector Identifier XCN 60 Set null
11 SPE ActionCode ID 1 Set null
12 Danger Code CE 60
Clinical information,
13 Relevant Clinical Info ST 300
diagnosis or remark etc.
14 SPE Received DateTime TS 26
15 SPE Source CM 300 Blood, urine or others
16 Ordering Provider XCN 120
OrderCallback Phone Set null
17 XTN 40
Number
18 Placer Field1 ST 60 Inspection applicant
19 Placer Field2 ST 60 Set null
20 Filler Field1 ST 60 Set null
… Do not need to fill basically Set null
Example:
OBR|1|1010051|000001|URIT^UT-3020||20101010093020|20101010093500||||||
Jaundice||BLD|Tom||011

OBX:
Number Field Type Length Remark
1 Set ID OBX SI Confirm different fields,
4
generally use 1 or null
2 Value Type ID NM indicates number type,
3
ST indicates value type
3 Observation CE Observation
590
Identifier Identifier or item ID
4 Observation SubID ST 20
5 Observation value ST 65535 Test result
6 Units CE 90
7 References Range ST 90
8 Abnormal Flags ID 5 Value mark: L H N
9 Probability ID 5 Set null
10 Nature of Abnormal ID Set null
2
Test
11 Observe Status ID Observe results and take F
1
as final result
12 Date Last Observe TS 26 Set null
13 User Defined Access ST Original result, such as
20
Checks absorbance
14 DateTime TS 28 Use for biochemical result
15 Producer ID
16 Responsible
Observer
17 Observation Method CE Use for biochemical
60
analyzer
A complete ASCII data example:
<SB>
MSH|^~\&|[CompanyName]|[InstrName]|LIS|PC|[ResultTime]||ORU^R01|[Ins
trType]|P|2.3.1||||||UNICODE<CR>
PID|[PatType]|[PatID]|[PatBarCode]|[PatBedCode]|[PatName]||[PatBirth]|[Pat
Sex]<CR>
OBR|[SampleType]|[REQID]|[SampleID]|[CompanyName]^[InstrName]||[Sa
mpleTime]|[StartTime]||||||[Symptom]||[SanpleType]|[SendDOCName]||[SendDP]<
CR>

OBX|[ResultType]|[ValueType]|[ItemID]|[ItemName]|[TestResult]|[Unit]|[Cons
ultValue]|[Flag]|||F||||[DocDP]|[DOCName]|<CR>
OBX|1|NM|[ItemID]^LeftLine||[TestResult]||||||F||||[DocDP]|[DOCName]|<CR>
OBX|1|NM|[ItemID]^RightLine||[TestResult]||||||F||||[DOCDP]|[DOCName]|<C
R>
OBX|1|ED|[
ItemID]||[InstrID]^Histogram^32Byte^HEX^[TestResult]||||||F||||[DOCDP]|[DOCNa
me]|<CR>
<EB>
<CR>

3 Communication Operations
If choose hexadecimal as transmission mode, the system will send data in
hexadecimal format. Likewise, choose ASCII, the system will send data in ASCII
format.
If automatic transmission is on, then after finish each analysis, the system will
transmit data through COM automatically. If you do not need, please choose off
in setting interface. Users can press “Trans.” in main menu screen to transmit
data.

You might also like