HL7 - REFACTORED

18.4.150 REF/RRI - Patient Referral Message (11.5.1)

The trigger events that use this message definition are described in Sections 11.5.2, "REF/RRI - Patient Referral (Event I12)," through 11.5.5, "REF/RRI - Request Patient Referral Status (Event I15)."

Message
ACK Choreography
FHIR Structure Definition
v2.xml XSD
ER7 Example
XML Example

Segment	Cardinality	Implement	Status
REF^I12-I15^REF_I12
MSH Message Header	[1..1]	SHALL
ARV Access Restriction			v2.9
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
RF1 Referral Information	[0..1]
AUTHORIZATION_CONTACT2	[0..1]
AUT Authorization Information	[1..1]	SHALL
CTD Contact Data	[0..1]
PROVIDER_CONTACT	[1..*]	SHALL
PRD Provider Data	[1..1]	SHALL
CTD Contact Data
PID Patient Identification	[1..1]	SHALL
NK1 Next of Kin / Associated Parties
GT1 Guarantor
INSURANCE
IN1 Insurance	[1..1]	SHALL
IN2 Insurance Additional Information	[0..1]
IN3 Insurance Additional Information, Certification	[0..1]
ACC Accident	[0..1]
DG1 Diagnosis
DRG Diagnosis Related Group
AL1 Patient Allergy Information
PROCEDURE
PR1 Procedures	[1..1]	SHALL
AUTHORIZATION_CONTACT2	[0..1]
AUT Authorization Information	[1..1]	SHALL
CTD Contact Data	[0..1]
OBSERVATION
OBR Observation Request	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
RESULTS_NOTES
OBX Observation/Result	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
PATIENT_VISIT	[0..1]
PV1 Patient Visit	[1..1]	SHALL
PV2 Patient Visit - Additional Information	[0..1]
NTE Notes and Comments

REF_I12

MSH-15	MSH-16	Immediate ACK	Application Ack
Blank	Blank	-	RPI^I12-I15^RPI_I12
NE	AL	-	RPI^I12-I15^RPI_I12
AL, SU, ER	AL	ACK^I12-I15^ACK	RPI^I12-I15^RPI_I12

We need some ER7 examples...

We need some XML examples...

Message
ACK Choreography
FHIR Structure Definition
v2.xml XSD
ER7 Example
XML Example

Segment	Cardinality	Implement	Status
RRI^I12-I15^RRI_I12
MSH Message Header	[1..1]	SHALL
ARV Access Restriction			v2.9
SFT Software Segment
UAC User Authentication Credential Segment	[0..1]
MSA Message Acknowledgment	[0..1]
RF1 Referral Information	[0..1]
AUTHORIZATION_CONTACT2	[0..1]
AUT Authorization Information	[1..1]	SHALL
CTD Contact Data	[0..1]
PROVIDER_CONTACT	[1..*]	SHALL
PRD Provider Data	[1..1]	SHALL
CTD Contact Data
PID Patient Identification	[1..1]	SHALL
ACC Accident	[0..1]
DG1 Diagnosis
DRG Diagnosis Related Group
AL1 Patient Allergy Information
PROCEDURE
PR1 Procedures	[1..1]	SHALL
AUTHORIZATION_CONTACT2	[0..1]
AUT Authorization Information	[1..1]	SHALL
CTD Contact Data	[0..1]
OBSERVATION
OBR Observation Request	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
RESULTS_NOTES
OBX Observation/Result	[1..1]	SHALL
PRT Participation Information
NTE Notes and Comments
PATIENT_VISIT	[0..1]
PV1 Patient Visit	[1..1]	SHALL
PV2 Patient Visit - Additional Information	[0..1]
NTE Notes and Comments

RRI_I12

MSH-15	MSH-16	Immediate ACK	Application Ack
Blank	Blank	-	-
NE	NE	-	-
AL, SU, ER	NE	ACK^I12-I15^ACK	-

We need some ER7 examples...

We need some XML examples...

Note: The abstract message definitions for both the REF and RRI include the patient visit segments (PV1 and PV2). The PV1 and PV2 segments appear in the REF as an optional grouping to specify the visit or encounter that generated the referral. The PV1 and PV2 should not be used to provide suggested information for a future encounter or visit generated by the referral.

The PV1 and PV2 are also included in the RRI message definition. It should be noted that these segments do not merely mirror the segments in the originating REF message. Rather, they may contain information regarding the visit or encounter that resulted from the referral.