...
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 Obervation 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 some 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 | r | s | 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? Outgoing: The software sends OBR-4 as received with the order. | |||||||||||||||
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. | ||||||||||||||||
OBR-32 | s | ##to be done, siehe DS-815 |
Patient Data Logic (ADT)
Patient / Visit Identification
...
Even this information is transfered with an order - it is stored/updates the visit information.
Order Status
##bitte einheiten noch prüfen - rechnet er um in cm/m/inch? müsste in OBX-6 stehen
Order Status
The acquired recording may 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.
...
##bitte nochmal OBX prüfen. Stimmt OBX-25?
OBX-11/OBX-25 | Meaning |
---|---|
R | The results are entered or automatically generated. |
P | The results are preconfirmed, in general not by an accountable person. |
F | The results are confirmed by an accountable person. |
Observation Results (ORU)
As mentioned above, an order / observation may be processed in different steps by different persons. This implies, that it may be send with different observation status several times to hte place, as stipulated for this specific installation and observation type. The observation gets and internal filler ID as soons as the observation is created.
In most installations, the manually typed in Report-Text (german "Befund") and a created PDF-File (also base64-embedded) are the most important data of the observation.
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) | so | observation identifier, see below OBX-3-1 code, OBX-3-2 text/human readable |
OBX-5 | 1) | so | observation value, see below |
OBX-6 | 1) | so | units |
OBX-11 | so | Observation Result Status. (see above, section "Observation Result Status") |
1) Incoming: See section "Orders" above.
Sending specific observation data
custo diagnostic can send specific observation data. The most common one is the manually typed in report or the entire observation as PDF / base64 embedded, but more than hundred specific numeric values can be defined which are described more specific below.
OBX-2 | OBX-3-1 | OBX-3-2 | OBX-5-1 | OBX-5-3 | OBX-5-4 |
---|---|---|---|---|---|
FT | AKT_BEF | Report | Formatted Report | ||
RP | FILE_PDF | PDF File | Points to an PDF-File, including path. | ||
ED | FILE_PDF | PDF File | Base64 | ||
Sample:
Medical Document (MDM)
Physical Transport
...