...
| Field | o/r/i | s/so | Default Usage |
|---|---|---|---|
| MSH-3 | o | so | Sending Application. Incoming: Expected value can be configured (default empty) in custo diagnostic and works as a filter - meaning messages with deviant content in MSH-3 are ignored. Outgoing: Sending Application, e.g. "CUSTO" can be configured in custo diagnostic. |
| MSH-4 | o | so | Sending Facility Incoming: Expected value can be configured in custo diagnostic and works as a filter - meaning messages with deviant content in MSH-4 are ignored. Outgoing: Sending Application, e.g. "CUSTO" can be configured in custo diagnostic. When a tenant system (german "Mandantensystem") is configured, this field contains the information about the tenant. See "Tenant System" above. |
| MSH-5 | o | so | Receiving Application Incoming: Expected value can be configured (default empty) in custo diagnostic and works as a filter - meaning messages with deviant content in MSH-3 are ignored. Outgoing: Receiving Application, can be configured (default empty) in custo diagnostic e.g. "HIS". |
| MSH-6 | o | so | Receiving Facility Incoming: Expected value can be configured in custo diagnostic and works as a filter - meaning messages with deviant content in MSH-3 are ignored. When a tenant system (german "Mandantensystem") is configured, this field should contain the information about the tenant. See "Tenant System" above. Outgoing: Receiving Facility, can be configured (default empty) in custo diagnostic e.g. "HIS". |
| MSH-7 | r | s | Date/Time Of Message, see HL7 Standard. ##DTM## |
| MSH-9 | r | s | Message Type. By default, custo diagnostic sends Messagetype^Event^Message-Structure, e.g. ORU^R01^ORU_R01. |
| MSH-10 | r | s | Message Control ID, see HL7 Standard |
| MSH-12 | r | s | Version ID (see section General HL7 information) |
| MSH-13 | r ## | s- | Sequence Number, see HL7 Standard |
| MSH-15 | s | Accept Acknowledge see below "Accept / Application Acknowledge" | |
| MSH-16 | i | s | Application Acknowledge Receiving: ignored. Sending: Always set to "NE" see below "Accept / Application Acknowledge" |
| MSH-18 | i | s | Character Set Receiving messages: custo diagnostic considers the character set specified in MSH-18. custo diagnostic can be configured to use a specific character set. In general Windows-1252 is used and send out via MSH-18. This one The general setting is used for alle outgoing messages. |
...
| Field | o/r/i | s/so | Default Usage | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PID-3 | r | s | PID-3-1 is used to identify the patient in custo diagnostic. It must be unique in one custo diagnostic installation, otherwise an appropriate tenant system must be used (see tenant system above). | ||||||||||
| PID-5 | r | s | PID-5-1, PID-5-2, PID-5-3, PID-5-4, PID-5-6: Family Name, Given Name, Second Name, Suffic, Degree/Title Required: PID-5-1 | ||||||||||
| PID-7 | r | s | Date of birth | ||||||||||
| PID-8 | r | s | Administrative Sex. Supported Values are F, M, ?? Other Values are interpeted as ... ##zu prüfen##
| ||||||||||
| PID-11 | o | s | Address of the patient | ||||||||||
| PID-19 | o | s | Social Security Number |
PV1 - Segment
...
| Field | o/r/i | s/so | Default Usage | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| PV1-2 / PV1-21 | o | Patient Visit price indicator. ###
| ||||||||||||||||||||||
| PV1-3 | o | s | Patient Visit location (Processed: PV1-3-1, PV1-3-2, PV1-3, PV1-3-4, PV1-3-5, PV1-3-7, PV1-3-8, PV1-3-9 (not supported PV1-3-6) | |||||||||||||||||||||
| PV1-19 | r | s | Visit-ID. The visit id is used to identify the visit in custo diagnostic It must be unique in one custo diagnostic installation, otherwise an appropriate tenant system must be used (see "tenant system" above). | |||||||||||||||||||||
| PV1-44 | o | - | Admission Date: custo diagnostic can store this information, even it is not shown in the user interface. Its done for future usage. | |||||||||||||||||||||
| PV1-45 | o | - | Discharge Date/Time: custo diagnostic can store the discharge date/time to filter out discharged patients in patient search lists. It can be defined, how custo diagnostic interpretes an empty discharge date/time - either als missing, unknown information, or as the information, that the discharge date should be deleted in custo diagnostic. |
...
| Field | o/r/i | s/so | Default Usage | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OBR-1 / OBR-5 | r | s/so | Order Control The combination of OBR-1 and OBR-5 can be configured as order control: Default:
By default, OBR-5 is not evaluated, but can be configured to specific values. In this case the combination of OBR-1 and OBR-5 must match. Outgoing: See also "Sending Observation Status via ORR / ORU Messages" | |||||||||||||||
| OBR-2 | r | s | Placer ID | |||||||||||||||
| OBR-3 | i | s | Outgoing: Consecutive Number with an alphanumeric prefix, e.g. "CM00001234" or a GUID,. This can be configured by a fixed length consecutive number, with an arbitrary alphanumeric prefix, e.g. "CM00001234", or an GUID e.g. "36eea93b-bc1b-4769-a84e-4ebeaaaf387e" | |||||||||||||||
| OBR-4-1 / -2 | r | s | OBR-4-1/OBR-4-2 contains information about the type of observation which should by executed. OBR-4-1 is a coded value which must be defined/agreed between interface partner. OBR-4-2 when incoming, OBR-4-2 is shown to the user, e.g. "Resting ECG", must be defined/agreed between interface partner. OBR-4-1 and OBR-4-2 is required, other components optional. Outgoing: The software sends OBR-4 as received with the order. | |||||||||||||||
| OBR-4-4 | o | so | Alternate Order ID. This might be an additional id, given bei the ordering system, to handle several observation requests in one common order (ORC). In DICOM environments, OBR-4-4 is used as Study Instance UID. | |||||||||||||||
| OBR-5 | see OBR-1 | |||||||||||||||||
| OBR-7-1 | i | s | Time of Acquisition | |||||||||||||||
| OBR-20 | o | so | Incoming: Flexible text-fields which can be used to show additional information regarding this order to the user. | |||||||||||||||
| OBR-21 | o | so | Incoming: Flexible text-fields which can be used to show additional information regarding this order to the user. | |||||||||||||||
| OBR-32-1-2 | i | s | User-Account, entering/confirming the report | |||||||||||||||
| OBR-36 | o | - | Scheduled Date / Time |
OBX-Segment
| Field | o/r/i | s/so | Default Usage |
|---|---|---|---|
| OBX-1 | 1) | s | Set-ID |
| OBX-2 | 1) | s | Value Type (ST, NM, FT, RP, ED) |
| OBX-3 | 1) | s | observation identifier, see below OBX-3-1 code, OBX-3-2 text/human readable |
| OBX-5 | 1) | s | observation value, see below |
| OBX-6 | 1) | s | OBX-6-1 empty, OBX-6-2 units |
| OBX-11 | 1) | so | Observation Result Status. (see above, section "Observation Result Status") |
1) Incoming: See section "Orders"
Most used OBX-3 Codes:
| OBX-2 | OBX-3-1 (Code) | OBX-3-2 (Human Readable Text) | OBX-5-1 | OBX-5-3 | OBX-5-4 |
|---|---|---|---|---|---|
| FT | AKT_BEF | Report | Formatted Report, as typed in or automatcially generated by the software | ||
| RP | FILE_PDF | PDF File | Points to an PDF-File, including path. | ||
| ED | FILE_PDF | PDF File | Base64 | ||
| ST | STUDYUID_DCM | Study Instance UID | In combination with DICOM, that Study Instance UID of the DICOM object. | ||
TXA-Segment
(Use Case: PDF Export)
| Field | s/so | Default Usage |
|---|---|---|
| TXA-2 | s | Always CD |
| TXA-3 | Always AP | |
| TXA-4-1 | s | Acquisition Time of Evaluation |
| TXA-6-1 | s | Export Time / Creation Time of Document |
| TXA-9-2-1 | s | User-Account, created the report |
| TXA-15-1 | Filler ID |
(Use Case: PDF Export)
Physical Transport
...