REF: Patient referral
This page lists the structures and trigger events REF defines, taken from the standard. The written commentary that theADT page carries has not been written for REF.
Recognising REF messages
REF announces itself in MSH-9 like this:
REF^I12^REF_I12- MSH-9.1
REFmessage code: what kind of message this is - MSH-9.2
I12trigger event: what happened in the real world: patient referral - MSH-9.3
REF_I12message structure: which segments to expect, and in what order
How to use these specifications explains MSH-9 in full, with a worked example.
Message structures
REF takes 1 structure.
REF_I12: Patient Referral
No trigger event in the standard names this structure.
You must always send: MSH, PRD, PID. Everything else is optional, or required only inside a group you chose to send.
| Segment | Name | OPT | Cardinality |
|---|---|---|---|
| MSH | R | 1..1 | |
| SFT | O | 0..* | |
| RF1 | O | 0..1 | |
| AUTHORIZATION_CONTACT | a group of 2 segments, repeated together | O | 0..1 |
| AUTin AUTHORIZATION_CONTACT | R | 1..1 | |
| CTDin AUTHORIZATION_CONTACT | O | 0..1 | |
| PROVIDER_CONTACT | a group of 2 segments, repeated together | R | 1..* |
| PRD | R | 1..1 | |
| CTD | O | 0..* | |
| PID | R | 1..1 | |
| NK1 | O | 0..* | |
| GT1 | O | 0..* | |
| INSURANCE | a group of 3 segments, repeated together | O | 0..* |
| IN1in INSURANCE | R | 1..1 | |
| IN2in INSURANCE | O | 0..1 | |
| IN3in INSURANCE | O | 0..1 | |
| ACC | O | 0..1 | |
| DG1 | O | 0..* | |
| DRG | O | 0..* | |
| AL1 | O | 0..* | |
| PROCEDURE | a group of 2 segments, repeated together | O | 0..* |
| PR1in PROCEDURE | R | 1..1 | |
| AUTHORIZATION_CONTACTin PROCEDURE | a group of 2 segments, repeated together | O | 0..1 |
| AUTin AUTHORIZATION_CONTACT | R | 1..1 | |
| CTDin AUTHORIZATION_CONTACT | O | 0..1 | |
| OBSERVATION | a group of 3 segments, repeated together | O | 0..* |
| OBRin OBSERVATION | R | 1..1 | |
| NTEin OBSERVATION | O | 0..* | |
| RESULTS_NOTESin OBSERVATION | a group of 2 segments, repeated together | O | 0..* |
| OBXin RESULTS_NOTES | R | 1..1 | |
| NTEin RESULTS_NOTES | O | 0..* | |
| PATIENT_VISIT | a group of 2 segments, repeated together | O | 0..1 |
| PV1in PATIENT_VISIT | R | 1..1 | |
| PV2in PATIENT_VISIT | O | 0..1 | |
| NTE | O | 0..* |
R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 8 such groups: AUTHORIZATION_CONTACT, PROVIDER_CONTACT, INSURANCE, PROCEDURE, AUTHORIZATION_CONTACT, OBSERVATION, RESULTS_NOTES, PATIENT_VISIT.
Trigger events
The trigger event is the real-world thing that made the message get sent. REF defines 0.
| Event | Name | Structure |
|---|