Schedule a demo
Segment

Product / service section

Defines a top-level section within a healthcare claim or invoice that groups one or more product/service groups. It carries the provider and payer section numbers, a sequence number, the total billed amount for the section, and a descriptive heading. It appears in EHC claim messages (EHC^E01, EHC^E02) as the outermost organizational unit, enabling payers to process and adjudicate claims by section.

5fields
4required
v2.9HL7 version
pss.py
from zato.hl7v2 import PSS

pss = PSS()
pss.product_service_section_sequence_number = '1'
pss.billed_amount = '4500.00'
pss.section_description_or_heading = 'Inpatient services'

Build PSS segments in Python

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

1

Inpatient section

Top-level claim section grouping all inpatient services with a total billed amount

from zato.hl7v2.v2_9 import PSS
from zato.hl7v2.v2_9 import EI

pss = PSS()
pss.provider_product_service_section_number = EI(
    entity_identifier='SEC001',
    namespace_id='HOSP'
)
pss.payer_product_service_section_number = EI(
    entity_identifier='PSEC001',
    namespace_id='INS'
)
pss.product_service_section_sequence_number = '1'
pss.billed_amount = '4500.00'
pss.section_description_or_heading = (
    'Inpatient services'
)
2

Outpatient section

Claim section for outpatient services billed under a separate heading

from zato.hl7v2.v2_9 import PSS
from zato.hl7v2.v2_9 import EI

pss = PSS()
pss.provider_product_service_section_number = EI(
    entity_identifier='SEC002',
    namespace_id='HOSP'
)
pss.product_service_section_sequence_number = '2'
pss.billed_amount = '1200.00'
pss.section_description_or_heading = (
    'Outpatient services'
)
3

Professional fees section

Section covering physician professional fees within the claim

from zato.hl7v2.v2_9 import PSS
from zato.hl7v2.v2_9 import EI

pss = PSS()
pss.provider_product_service_section_number = EI(
    entity_identifier='SEC003',
    namespace_id='HOSP'
)
pss.payer_product_service_section_number = EI(
    entity_identifier='PSEC003',
    namespace_id='INS'
)
pss.product_service_section_sequence_number = '3'
pss.billed_amount = '2750.00'
pss.section_description_or_heading = (
    'Professional fees'
)

Learn by building

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

Frequently asked questions

PSS defines a top-level section within a healthcare claim. Each section has a sequence number, a total billed amount, and a heading. Sections contain one or more PSG groups, which in turn contain PSL line items, forming a three-level claim hierarchy.

PSS is the outermost level. Each PSS section contains PSG groups, and each PSG group contains PSL line items. The billed_amount in PSS should equal the sum of its child PSG amounts:

from zato.hl7v2.v2_9 import PSS, EI

pss = PSS()
pss.provider_product_service_section_number = EI(
    entity_identifier='SEC001',
    namespace_id='HOSP'
)
pss.billed_amount = '4500.00'

The provider_product_service_section_number uses the EI datatype:

from zato.hl7v2.v2_9 import PSS, EI

pss = PSS()
pss.provider_product_service_section_number = EI(
    entity_identifier='SEC001',
    namespace_id='HOSP'
)

Assign a string to the section_description_or_heading field:

from zato.hl7v2.v2_9 import PSS

pss = PSS()
pss.section_description_or_heading = (
    'Inpatient services'
)

No, payer_product_service_section_number is optional. It is assigned by the payer during adjudication:

from zato.hl7v2.v2_9 import PSS, EI

pss = PSS()
pss.payer_product_service_section_number = EI(
    entity_identifier='PSEC001',
    namespace_id='INS'
)

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.

PSS field reference

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

#Python nameDatatypeUsageRepeatableTable
1provider_product_service_section_numberEIRequiredNo-
2payer_product_service_section_numberEIOptionalNo-
3product_service_section_sequence_numberSIRequiredNo-
4billed_amountCPRequiredNo-
5section_description_or_headingSTRequiredNo-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python