HL7 PSS Segment: Product/Service Section

The PSS (Product/Service Section) segment heads a section of related product/service groups and line items within a bill. PSS was introduced in HL7 v2.6 alongside PSG and PSL, and the structure has remained stable through v2.8.1 — five fields that together identify the section and carry its rolled-up amount and human-readable heading.

Purpose

PSS provides the top of the section → group → line hierarchy used by product/service billing exchanges. It identifies the section using both provider-assigned and payer-assigned numbers, sequences it within the surrounding message, carries the section-level billed amount, and provides a description or heading suitable for display on an itemised statement. Each PSS is normally followed by one or more PSG groups, which in turn contain PSL line items.

Used in

PSS is used in product/service billing flows carried by financial and master-file messages such as DFT (Detailed Financial Transaction) and PMU events that exchange billable activity. See the DFT message page for the typical envelope.

Field-by-field reference

Source: HAPI HL7v2 v2.8.1 javadocs (https://hapifhir.github.io/hapi-hl7v2/v281/apidocs/ca/uhn/hl7v2/model/v281/segment/PSS.html) for sequence, name, data type, and repetition. Length is not published in the javadocs (—); Required and Table # are filled from the HL7 v2 standard where well-established.

Seq	Name	Data Type	Length	Req	Repeat	Table #	Description
PSS-1	Provider Product/Service Section Number	ei	—	R	—	—	Provider-assigned section identifier
PSS-2	Payer Product/Service Section Number	ei	—	O	—	—	Payer-assigned section identifier
PSS-3	Product/Service Section Sequence Number	si	—	R	—	—	Ordinal position of section in message
PSS-4	Billed Amount	cp	—	O	—	—	Total billed amount for the section
PSS-5	Section Description or Heading	st	—	O	—	—	Free-text section heading

Most-used fields

PSS-1 Provider Product/Service Section Number is the primary key emitted by every sender; receivers key on it to attach child PSG / PSL segments.
PSS-3 Product/Service Section Sequence Number lets receivers preserve display ordering of sections on an itemised statement.
PSS-4 Billed Amount is the rolled-up section total used by payer systems to verify that the sum of child PSG amounts matches the section total.
PSS-5 Section Description or Heading is what most receivers print verbatim as a section header, so trailing whitespace and casing matter.

Version differences

Introduced in HL7 v2.6 with the same five fields published today.
v2.7 did not change PSS structurally; tables on neighbouring segments were updated.
v2.7.1, v2.8, and v2.8.1 carry PSS forward unchanged.
v2.8.2 publishes editorial-only clarifications; the field set is identical.

Common mistakes

Sending PSG or PSL without a preceding PSS — many engines silently drop subsequent segments because they have no section to anchor to.
Re-using PSS-1 across messages without scoping by namespace ID; downstream reconciliation systems then merge unrelated sections.
Letting PSS-4 disagree with the sum of child PSG-5 values without an explicit adjustment line, which forces the payer into manual review.
Putting a CPT code or numeric code in PSS-5 — PSS-5 is intended for human-readable section headings, not coded content.
Emitting multiple PSS segments with the same PSS-3 sequence number; receivers will usually keep only one.

Examples

Minimal:

PSS|SEC-301^^VORRO^EI|||1

Fully populated:

PSS|SEC-301^^VORRO^EI|PAYSEC-880^^AETNA^EI|1|600.00^USD|Imaging

Annotated breakdown:

PSS | SEC-301^^VORRO^EI            # PSS-1 Provider section number
    | PAYSEC-880^^AETNA^EI         # PSS-2 Payer section number
    | 1                             # PSS-3 Section sequence
    | 600.00^USD                    # PSS-4 Section billed amount
    | Imaging                       # PSS-5 Section heading

In-context excerpt, DFT P03 with two sections:

MSH|^~&|VORRO|HOSP-A|AETNA|PAYER|20260610101500||DFT^P03^DFT_P03|MSG00060|P|2.8.1
EVN|P03|20260610101500
PID|1||MRN-22310^^^VORRO^MR||OKAFOR^ADA^N||19880220|F
PV1|1|I|WARD-3^310^A^HOSP-A
PSS|SEC-301^^VORRO^EI||1|600.00^USD|Imaging
PSG|GRP-7781^^VORRO^EI||1|Y|600.00^USD|MRI studies
PSL|LINE-9001^^VORRO^EI||1|||A^Active^HL70776|72148^MRI lumbar w/o^CPT|||20260610||1^study^UCUM|300.00^USD|1|300.00^USD|300.00^USD
PSL|LINE-9002^^VORRO^EI||2|||A^Active^HL70776|72149^MRI lumbar w/^CPT|||20260610||1^study^UCUM|300.00^USD|1|300.00^USD|300.00^USD
PSS|SEC-302^^VORRO^EI||2|420.00^USD|Laboratory
PSG|GRP-7782^^VORRO^EI||1|Y|420.00^USD|Hematology panel
PSL|LINE-9101^^VORRO^EI||1|||A^Active^HL70776|85025^CBC w/ diff^CPT|||20260610||1^test^UCUM|135.00^USD|1|135.00^USD|135.00^USD
PSL|LINE-9102^^VORRO^EI||2|||A^Active^HL70776|80053^Comp metabolic panel^CPT|||20260610||1^test^UCUM|285.00^USD|1|285.00^USD|285.00^USD

In-context excerpt, DFT P11 with a single section spanning multiple groups:

MSH|^~&|VORRO|CLINIC-B|UHG|PAYER|20260610113000||DFT^P11^DFT_P11|MSG00061|P|2.8.1
EVN|P11|20260610113000
PID|1||MRN-44021^^^VORRO^MR||SMITH^JOHN^Q||19601122|M
PSS|SEC-410^^VORRO^EI||1|980.00^USD|Outpatient visit
PSG|GRP-8810^^VORRO^EI||1|Y|240.00^USD|E/M services
PSL|LINE-9201^^VORRO^EI||1|||A^Active^HL70776|99213^Office visit^CPT|||20260610||1^visit^UCUM|240.00^USD|1|240.00^USD|240.00^USD
PSG|GRP-8811^^VORRO^EI||2|N|740.00^USD|Laboratory panel
PSL|LINE-9202^^VORRO^EI||1|||A^Active^HL70776|80053^Comp metabolic panel^CPT|||20260610||1^test^UCUM|285.00^USD|1|285.00^USD|285.00^USD
PSL|LINE-9203^^VORRO^EI||2|||A^Active^HL70776|85025^CBC w/ diff^CPT|||20260610||1^test^UCUM|135.00^USD|1|135.00^USD|135.00^USD
PSL|LINE-9204^^VORRO^EI||3|||A^Active^HL70776|84443^TSH^CPT|||20260610||1^test^UCUM|320.00^USD|1|320.00^USD|320.00^USD

FHIR mapping

PSS has no segment-level ConceptMap in the official v2-to-FHIR Implementation Guide. Conceptually, a PSS aligns with a grouping construct above Claim.item that FHIR does not model directly:

PSS-1 typically becomes an identifier extension on Claim or Invoice, or is used as a Claim.item.subDetail parent reference;
PSS-4 maps to a Claim.total.amount rolled up to the section, or to an Invoice.totalNet for an invoice subsection;
PSS-5 carries through as a human-readable label on the resource (e.g., Invoice.lineItem.extension or a display string).

Because FHIR Claim flattens grouping, implementations frequently encode the section hierarchy in a sender-specific extension and rely on PSS-3 to preserve order.

Engine considerations

HAPI v2.8.1 exposes PSS via ca.uhn.hl7v2.model.v281.segment.PSS with typed accessors getProviderProductServiceSectionNumber(), getProductServiceSectionSequenceNumber(), getBilledAmount(), and getSectionDescriptionOrHeading().
Mirth Connect represents PSS as the outer wrapper of the PSS_PSG_PSL group; iterate PSS before descending into PSG and PSL.
Rhapsody and Cloverleaf treat PSS as a normal flat segment but most published mappers stop at PSL — custom JavaScript or filter scripts are usually needed to surface PSS-4 and PSS-5 onto the outbound message.
Carry PSS-4's CP currency identifier end-to-end; dropping the second component is a common silent loss when routing through systems that assume a single global currency.

How Vorro parses and produces PSS

Vorro models PSS as a ProductServiceSection node containing ordered ProductServiceGroup children, preserving the original PSS-3 sequence value alongside Vorro's own normalised index so downstream consumers can re-emit segments in the order they arrived. On the producer side, Vorro recomputes PSS-4 from the child PSG billed amounts and emits a route-configurable warning when the recomputed total disagrees with an incoming PSS-4 by more than one cent. PSS-5 is preserved verbatim including whitespace and casing so printed statements look identical to the source.

Sources

← Back to HL7 v2 Guide