Schedule a demo
Message type

Request for treatment authorization information

Supports referral and authorization workflows between providers and payers. Key segments include MSH, MSA, PID, OBR. Referral management and authorization systems exchange this.

32segments
11required
6groups
v2.9HL7 version
rpa-i08.py
# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RPA^I08^RPA_I08|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Build and parse RPA^I08 messages in Python

How to construct, send, receive, and extract fields from real-world RPA^I08 messages.

1

Parse an incoming RPA^I08 message

Demonstrates receiving and extracting key fields from a request for treatment authorization information transaction

# Zato
from zato.hl7v2 import HL7Message

# An incoming message ..
raw = 'MSH|^~\&|SENDER|FAC|RCV|DEST|20260701||' \
      'RPA^I08^RPA_I08|MSG001|P|2.9\r' \
      'PID|1||MRN-10045||SMITH^JOHN||19850315|M\r' \
      'PV1|1|I|MED^201^A'

# .. parsed into a Python object ..
msg = HL7Message.parse(raw)

# .. whose fields we can now access.
name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth
patient_class = msg.pv1.patient_class
location = msg.pv1.assigned_patient_location

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

Use the HL7v2 message parser to extract the typed structure. The parsed message gives you direct access to every segment and field by name.

from zato.hl7v2 import HL7Message

raw = 'MSH|^~\&|SENDER|FACILITY|RECEIVER|DEST|20260401120000||RPA^I08^RPA_I08|MSG00001|P|2.9\rMSA|AA|MSG00001\rRF1||ROUTINE^Routine^HL70283||20260401|20260430\rPID|1||MRN-10045||JOHNSON^SARAH^M||19880612|F|||100 Oak Lane^^Portland^OR^97201\rNK1|1|JOHNSON^MICHAEL|SPO^Spouse|100 Oak Lane^^Portland^OR^97201|5035551234\rGT1|1||JOHNSON^SARAH^M||100 Oak Lane^^Portland^OR^97201|5035559876\rACC|20260401\rDG1|1||Z00.00^Encounter for general adult medical exam^I10|||F'
msg = HL7Message.parse(raw)

name = msg.pid.patient_name
dob = msg.pid.date_time_of_birth

Beyond the mandatory MSH header, the required segments are: MSA, AUT, PRD, PID, IN1, PR1, AUT, OBR. Optional segments provide additional detail when available.

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

RPA^I08 segment composition

Segments that make up the RPA^I08 message, in order. Groups are shown with their child segments.

#SegmentUsageRepeatsDescriptionGroup
1MSHRequiredNoMessage header-
2ARVOptionalYesAccess restriction-
3SFTOptionalYesSoftware segment-
4UACOptionalNoUser authentication credential-
5MSARequiredNoMessage acknowledgment-
6RF1OptionalNoReferral information-
7AUTRequiredNoAuthorization informationAUTHORIZATION
8CTDOptionalNoContact dataAUTHORIZATION
9PRDRequiredNoProvider dataPROVIDER
10CTDOptionalYesContact dataPROVIDER
11PIDRequiredNoPatient identification-
12NK1OptionalYesNext of kin / associated parties-
13GT1OptionalYesGuarantor-
14IN1RequiredNoInsuranceINSURANCE
15IN2OptionalNoInsurance additional infoINSURANCE
16IN3OptionalNoInsurance additional info - certificationINSURANCE
17ACCOptionalNoAccident-
18DG1OptionalYesDiagnosis-
19DRGOptionalYesDiagnosis related group-
20AL1OptionalYesPatient allergy information-
21PR1RequiredNoProceduresPROCEDURE
22AUTRequiredNoAuthorization informationPROCEDURE
23CTDOptionalNoContact dataPROCEDURE
24OBRRequiredNoObservation requestOBSERVATION
25PRTOptionalYesParticipation informationOBSERVATION
26NTEOptionalYesNotes and commentsOBSERVATION
27OBXRequiredNoObservation resultOBSERVATION
28PRTOptionalYesParticipation informationOBSERVATION
29NTEOptionalYesNotes and commentsOBSERVATION
30PV1RequiredNoPatient visitVISIT
31PV2OptionalNoPatient visit - additional infoVISIT
32NTEOptionalYesNotes and comments-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python