Schedule a demo
Healthcare/HL7 v2/PRC
Segment

Pricing

Defines pricing information for chargeable items in the charge description master, specifying price, applicable facility, department, valid patient classes, minimum and maximum quantity, and effective date range. It is used in MFN (Master File Notification) messages to distribute and synchronize charge master data from a financial or billing system to other systems across a healthcare enterprise. PRC supports multi-facility and multi-department pricing differentiation.

18fields
1required
v2.9HL7 version
prc.py
from zato.hl7v2.v2_9 import PRC
from zato.hl7v2.v2_9 import CWE, CP, MO

prc = PRC()
prc.primary_key_value_prc = CWE(
    identifier='WEL001',
    text='Wellness Assessment'
)
prc.price = CP(price='75.00')
Python examples

Build PRC segments in Python

How to construct and work with real-world PRC segments.

1

Annual checkup pricing with facility and department

Defines pricing for an annual wellness checkup at a specific facility and department with an outpatient patient class

from zato.hl7v2.v2_9 import PRC
from zato.hl7v2.v2_9 import CP, CWE

prc = PRC()
prc.primary_key_value_prc = CWE(
    identifier='WEL001',
    text='Annual Wellness Checkup',
    name_of_coding_system='L'
)
prc.facility_id_prc = CWE(
    identifier='FAC01',
    text='Sunrise Clinic',
    name_of_coding_system='L'
)
prc.department = CWE(
    identifier='PREV',
    text='Preventive Care',
    name_of_coding_system='L'
)
prc.valid_patient_classes = CWE(
    identifier='O',
    text='Outpatient',
    name_of_coding_system='HL70004'
)
prc.price = CP(price='75.00')
2

Lab panel pricing with effective dates

Sets pricing for a nutrition lab panel with start and end dates to define the period during which the price is valid

from zato.hl7v2.v2_9 import PRC
from zato.hl7v2.v2_9 import CP, CWE

prc = PRC()
prc.primary_key_value_prc = CWE(
    identifier='LAB050',
    text='Nutrition Lab Panel',
    name_of_coding_system='L'
)
prc.valid_patient_classes = CWE(
    identifier='O',
    text='Outpatient',
    name_of_coding_system='HL70004'
)
prc.price = CP(price='45.00')
prc.effective_start_date = '20240101'
prc.effective_end_date = '20241231'
3

Consultation fee with min/max price range

Defines a wellness consultation fee with minimum and maximum price bounds and an active status flag

from zato.hl7v2.v2_9 import PRC
from zato.hl7v2.v2_9 import CWE, MO

prc = PRC()
prc.primary_key_value_prc = CWE(
    identifier='CON010',
    text='Wellness Consultation',
    name_of_coding_system='L'
)
prc.facility_id_prc = CWE(
    identifier='FAC02',
    text='Greenvalley Center',
    name_of_coding_system='L'
)
prc.minimum_price = MO(
    quantity='120.00',
    denomination='USD'
)
prc.maximum_price = MO(
    quantity='200.00',
    denomination='USD'
)
prc.chargeable_flag = 'Y'
prc.active_inactive_flag = 'A'
Tutorials

Learn by building

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

MLLP
Receive and parse HL7 v2 messages
Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.
Start tutorial Build
Build and send HL7 v2 messages
Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.
Start tutorial
Related segments

Commonly used with PRC

GP1 Grouping/reimbursement - visit GP2 Grouping/reimbursement - procedure line item CDM Charge description master FT1 Financial transaction
FAQ

Frequently asked questions

PRC contains pricing information including charge codes, prices, and effective dates for wellness services and preventive care programs.

Use effective_start_date and effective_end_date fields:

prc.effective_start_date = DTM('20240101')
prc.effective_end_date = DTM('20241231')

CDM defines charge description master entries while PRC contains the actual pricing. PRC can have multiple prices for different facilities or time periods for the same CDM entry.

Yes, use facility_id_prc to specify facility-specific pricing. This allows different wellness centers to have different rates for the same service.

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.

Reference

PRC field reference

Complete list of fields in the PRC segment, HL7 v2.9.

#Python nameDatatypeUsageRepeatableTable
1▶primary_key_value_prcCWERequiredNoHL70132
2▶facility_id_prcCWEOptionalYesHL70464
3▶departmentCWEOptionalYesHL70184
4▶valid_patient_classesCWEOptionalYesHL70004
5▶priceCPOptionalYes-
6formulaSTOptionalYes-
7minimum_quantityNMOptionalNo-
8maximum_quantityNMOptionalNo-
9▶minimum_priceMOOptionalNo-
10▶maximum_priceMOOptionalNo-
11effective_start_dateDTMOptionalNo-
12effective_end_dateDTMOptionalNo-
13▶price_override_flagCWEOptionalNoHL70268
14▶billing_categoryCWEOptionalYesHL70293
15chargeable_flagIDOptionalNoHL70136
16active_inactive_flagIDOptionalNoHL70183
17▶costMOOptionalNo-
18▶charge_on_indicatorCWEOptionalNoHL70269

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs
Open source In Python