...
##bitte nochmal OBX prüfen. Stimmt OBX-25?
| OBX-11/OBXOBR-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. |
...
| 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 | OBX-6-1 empty, OBX-6-2 units |
| OBX-11 | so | Observation Result Status. (see above, section "Observation Result Status") |
...
It is recommended to use the OBX-3-1 as a filter, and OBX-3-2 as the text which is shown to a user.
Medical Document (MDM)
Supported Message Types: MDM^T01, MDM^T02, MDM^T07, MDM^T08, MDM^T11
When the results the following documents can be exported via MDM:
- PDF File
- Picture Data (PNG)
- DICOM ECG Data
- RTF File
Please note: Picture Data and RTF File may be subject to be declared as obsolete in the next versions. DICOM: In general, the separate DICOM store functionality should be used, instead of the HL7 export.
The export is done via TXA Segment and points to the file in the file share:
Additionally an OBX Segment can be added to the MDM message which follows the same syntax as in ORU message. (see section "OBX-Segment" above).