...
Drübergehen DTM Format?
""
Gewicht / Größe / Medication
Key
Not listed fields are ignored
...
The software supports the following message types.
- ADT
- ORM
- ORR
- ORU
- ORR
- DFT
- MDM
- ACK
The message types must be licenced individually - which means not in all installations all message types will be available.
...
HL7 Segments
Optionality Key
Incoming
| r | required | This value is required for a proper function of the software |
| o | optional | This value is not required but may be used for some functionality in custo diagnostic. |
| i | ignored | This value is ignored |
Outgoing
| s | send | This value will be send by default, in case the data is available |
| so | send optiontal | This value will be send, in case it is agreed between the communication partners. |
MSH - Segment
| 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" below. |
| 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" below. 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, Outgoing: Custo diagnostic supports Version 2.3, 2.5 ##Verhalten bei eingehenden Nachrichten noch prüfen, wenn 2.7 2.9 oder 1.5 o.ä. drin steht## |
| 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 (##bitte prüfen). 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 setting is used for alle outgoing messages. |
...
| Field | o/r/i | Default Usage | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| OBR-1 / OBR-5 | r | 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. | |||||||||||||||
| OBR-2 | r | Placer ID | |||||||||||||||
| OBR-3 | o | Outgoing: Consecutive Number with an alphanumeric prefix, e.g. "CM00001234" or some GUID, e.g. "36eea93b-bc1b-4769-a84e-4ebeaaaf387e" | |||||||||||||||
| OBR-4 | r | OBR-4 contains information about the type of observation which should by executed. OBR-4-1 is a coded value which must be defined. OBR-4-2 when incomfing, OBR-4-2 is shown to the user, e.g. "Resting ECG" OBR-4-1 and OBR-4-2 is requried, other components optional. ##bitte prüfen - when OBR-4-2 in eingehender Nachricht abweichen zur Konfiguration in "Untersuchung" - welcher Text wird dabei angezeigt - der aus der Konfig, oder der aus der Nachricht? | |||||||||||||||
| OBR-5 | see OBR-1 | ||||||||||||||||
| OBR-20 | o | Incoming: Flexible text-fields which can be used to show additional information regarding this order to the user. | |||||||||||||||
| OBR-21 | o | Incoming: Flexible text-fields which can be used to show additional information regarding this order to the user. |
...
By default, custo diagnostic send back the tenant code in MSH-4.
Order Data
...
/ Order Entry Workflow
The software supports all messages to provide a full HL7 order-entry workflow and methods to update the superior system about the current order status.
Orders
custo diagnostic receives orders and show them as a worklist to the users. One order is (by default) identified by the Placer Number, and may contain several observation requests, identified by Alternate Order ID. A clinical question is visible to the user, which can contain a free text and , The intention of the clinical question is to avoid unstructured communication by E-Mail/Phone etc.
The user choose the requested observation, and custo diagnostic determines the diagnostic mode by the service identified given in OBR-4, e.g. Spirometry or , Resting-ECG, Holter.
When receiving an order, the software also supports additional information, which is optional
| OBX-3-1 | OBX-3-2 |
|---|---|
| BODY WEIGHT | Weight |
| BODY HEIGHT | Height |
| MEDICATION | Medication |
Even this information is transfered with an order - it is stored/updates the visit information.
Order Status
The acquired recording may be processed several times in the software by several users, before it is finally reported. This workflow must be stipulated for the specific customer.
custo supports three methods to update the superior system (placer of the order) about the current state of the observation:
- ORR Messages
- ORU Status Messages (OBR-1/OBR-5)
- Obervation Result Status in (OBX-11)
Furthermore the software can be configured, that the only specific users/results with specific status can be transferred to the superior system.
When the orders are processed, custo diagnostic adds an internal "Filler ID" . This can be configured by a fixed length consecutive number, with an arbitrary alphanumeric prefix, e.g. "CM00001234", or an GUID.
...