This field encodes the following portions of the CMR:OBR stands for observation request. In the reporting of medical data, this segment serves as the report header, identifying the observation set represented by the contained atomic observations, including ordering information when applicable. It contains many attributes relevant to all of the included observations.
CMR attribute type comments Note: *Note Number NM *Date DT *Text ST *Problem Object Inpatient Boolean
In this application, the OBR segment is used as a header to send notes, the OBR segment contains data on where it is from, the OBX segment contains the actual note.
The complete table (figure 7-6) of which field is fillable is to be found on page 7-17 of the version 2.2 edition. The fields are described starting on page 4-28.
The values in italics are the actual values as expected in the message.
| Field name | value | comments |
|---|---|---|
| Set ID - observation request | sequence number of OBRs | start with 1. Enocdes Note Number from the CMR |
| Placer order number | no value | only relevant if the OBR was ordered |
| Filler order number | unique ID^responding application ID | The first sub-field identifies this OBR from all others, the second identifies the sending application |
| Universal service ID | identifier of observation/ request/battery | which coding system should be used has to be worked out on a per-site basis to begin with. |
| Priority ID | not used | |
| Request date/time | Timestamp of request of this item | |
| Observation date/time | Timsetamp of the observation. This encodes Date from the CMR. | |
| Observation end date/time | Timestamp of end of observation | |
| Collection volume | no value | see 1 |
| Collector identifier | no value | see 1 |
| Specimen action code | no value | see 1 |
| Danger code | code and/or text indicating known or suspected patient hazard | no coding system has been decided on yet |
| Relevant clinical information | additional information about patient | if necessary, the information here may be sent trhough OBX segments |
| Specimen received date/time | no value | see 1 |
| Specimen source | no value | see 1 |
| Ordering provider | at least the name of the person who ordered the test | |
| Order Callback Phone Number | no value | no reporting required |
| Placer field #1 | no value | |
| Placer field #2 | no value | |
| Filler field #1 | Segment ID^Number | see 2 |
| Filler field #2 | undefined | will be ignored by agglutinator |
| Results rpt/status change - date/time | no value | unnecessary |
| Charge to practice | no value | unnecessary |
| Diagnostic serv sect | section relevant to observation | see values in table 0074 |
| Result status | no value | see 1 |
| Parent result | no value | not necessary |
| Quantity/timing | no value | not necessary |
| Reult copies to | no value | not necessary |
| Parent number | no value | not necessary |
| Transportation mode | code from table 0124 | only when applicable |
| Reason for study | no value | not necessary |
| Principal result interpreter | Full ID, timestamp, location | identity of clinician responsible for report content, time of involvment and location |
| Assistant result interpreter | Full ID, timestamp, location | Clinician who assisted with the interpretation of this report, time of involvment and location |
| Technician | Full Id, timestamp, location | Technician responsible for this observation, time of involvment and location |
| Transcriptionist | Full ID, timestamp, location | Report transcriber, timestamp of involvment and location |
| Scheduled | no value | not necessary |
1 These fields are only relevant when an OBR is associated with a specimen, which doesn't happen in this project.
2 This pointer is coonstructed thus: the first sub-segment will contain the three letter code with which the kind of segment pointed to can be identified, like PV1 or PRB, if the segment is being transferred in the same message. The second sub-segment will contain the sequence number of the relevant segment within the set of segments. If no link is to be implied, nothing should be filled in.
The OBX segment is used here as a sub-segment for the OBR segment.The OBX segment transmits a single observation or observation fragment. It represents the smallest indivisible unit of a report. In our system, the OBX segment is used to transfer a note, and the values have been defined accordingly.
This segment is described in figure 7-7 on page 7-18 of the version 2.2 standard.
The values in italics are the actual values as expected in the message.
| field number | Field name | value | comments |
|---|---|---|---|
| 2 | Value type | TX | Notes usually will be text |
| 5 | Observation value | the actual note | Up to 65K can be transmitted. This encodes Text from the CMR. |
| 11 | Observation result status | F | The note is a final result |
| 16 | Responsible observer | the source of the note | if available |