Study Notes
AdvaPACS supports HL7 v2.5.1 messages for exchanging Study Notes between external systems (e.g., RIS, HIS) and AdvaPACS.
This feature allows notes to be read and sent through the OBX segment, ensuring that study-related remarks are synchronized across connected systems.
Supported OBX Fields
| Field | Description | Usage |
|---|---|---|
| OBX-2 | Value Type | Must be ST (String Data) |
| OBX-3-2 | Observation Identifier (subfield 2) | Must be NOTE |
| OBX-3-5 | Observation Identifier (subfield 5) | Contains the Note Type (e.g., Clinical, Technical, Admin) |
| OBX-4 | Observation Sub-ID | Optional. Contains a unique Note ID if available |
| OBX-5 | Observation Value | Contains the Note Content |
| OBX-11 | Observation Result Status | Ignored unless the value is D, which indicates the note should be deleted |
| OBX-14 | Date/Time of Observation | Represents the Date/Time of the Note |
| OBX-16 | Responsible Observer | Represents the User who created the Note |
Behavior and Processing Rules
-
Receiving Notes
- When AdvaPACS receives an HL7 message containing OBX segments with
OBX-3-2 = NOTE, the system will:- Create or update a study note based on the provided data.
- If
OBX-11 = D, the corresponding note will be deleted.
- If
OBX-4(Note ID) is not provided, AdvaPACS will automatically assign a unique internal ID.
- When AdvaPACS receives an HL7 message containing OBX segments with
-
Sending Notes
- When AdvaPACS sends study notes to external systems, each note is represented as an OBX segment following the above structure.
- Notes include:
- Type, Content, Creator, and Date.
- Optional unique Note ID.
-
Note Inheritance
- Notes received via HL7 are attached to the related Order.
- When the Order is viewed in AdvaPACS, the corresponding Study Notes are inherited and displayed with the study.
Example OBX Segment
OBX|1|ST|NOTE^NOTE^99ADV^NOTE^Clinical|12345|Patient has mild cough, follow-up required|N|||20251015|USR001