visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

18.4.157 RQA/RPA - Request Patient Authorization Message (Event I08) (11.4.1)

All trigger events in this group use the following message definition.

Segment Cardinality Implement Status
RQA^I08-I11^RQA_I08
MSH

Message Header

[1..1] SHALL
ARV

Access Restriction

  v2.9
UAC

User Authentication Credential Segment

[0..1]  
RF1

Referral Information

[0..1]  
AUTHORIZATION [0..1]  
AUT

Authorization Information

[1..1] SHALL
CTD

Contact Data

[0..1]  
PROVIDER [1..*] SHALL
PRD

Provider Data

[1..1] SHALL
CTD

Contact Data

 
PID

Patient Identification

[1..1] SHALL
NK1

Next of Kin / Associated Parties

 
GUARANTOR_INSURANCE [0..1]  
GT1

Guarantor

 
INSURANCE [1..*] SHALL
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 [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  
OBX

Observation/Result

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
VISIT [0..1]  
PV1

Patient Visit

[1..1] SHALL
PV2

Patient Visit - Additional Information

[0..1]  
NTE

Notes and Comments

 

 

RQA_I08

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - RPA^I08-I11^RPA_I08
NE AL - RPA^I08-I11^RPA_I08
AL, SU, ER AL ACK^I08-I11^ACK RPA^I08-I11^RPA_I08
We need some ER7 examples...
We need some XML examples...
Segment Cardinality Implement Status
RPA^I08-I11^RPA_I08
MSH

Message Header

[1..1] SHALL
ARV

Access Restriction

  v2.9
UAC

User Authentication Credential Segment

[0..1]  
MSA

Message Acknowledgment

[1..1] SHALL
RF1

Referral Information

[0..1]  
AUTHORIZATION [0..1]  
AUT

Authorization Information

[1..1] SHALL
CTD

Contact Data

[0..1]  
PROVIDER [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 [1..*] SHALL
PR1

Procedures

[1..1] SHALL
AUTHORIZATION [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  
OBX

Observation/Result

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
VISIT [0..1]  
PV1

Patient Visit

[1..1] SHALL
PV2

Patient Visit - Additional Information

[0..1]  
NTE

Notes and Comments

 

 

RPA_I08

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank - -
NE NE - -
AL, SU, ER NE ACK^I08-I11^ACK -
We need some ER7 examples...
We need some XML examples...
Note: The abstract message definitions for both the RPA and RQA include the patient visit segments (PV1 and PV2). The PV1 and PV2 segments appear in the RPA and RQA as an optional grouping to specify the visit or encounter that generated the referral authorization request. The PV1 and PV2 should not be used to provide suggested information for a future encounter or visit generated by the referral authorization request.

The trigger events that use this message definition are described in sections 11.4.2, "RQA/RPA - Request for Treatment Authorization Information (Event I08)," through 11.4.5, "RQA/RPA - Request for Cancellation of an Authorization (Event I11)."