NEWFree ROI Calculators — quantify what prior auth and siloed data are costing your organization.Prior Auth ROI Siloed Data ROI
HL7 v2Segment4 min read

HL7 PSC: not a defined HL7 v2 segment (identity note)

Important identity note up front: there is no segment named PSC in HL7 v2. It does not appear in the HAPI v2.5.1 segment package, nor in any other published HAPI version (verified against the segment package summary). A blueprint hint labeled "PSC" as "Product Service Group Adjustment," but that phrase does not name a real HL7 v2 segment — it fuses two distinct, real Claims and Reimbursement segments: PSG (Product/Service Group) and ADJ (Adjustment). This page states the truth and routes you to the genuine segments rather than presenting an invented field table.

Purpose

The purpose of this page is disambiguation. HL7 v2's Claims and Reimbursement chapter (chapter 16) models invoices with a specific segment set. The name "Product Service Group Adjustment" most likely points a reader toward:

  • PSG — Product/Service Group: a logical grouping of line items, patients, and response summaries within an invoice.
  • PSL — Product/Service Line Item: an individual product delivered or service rendered.
  • PSS — Product/Service Section: a section grouping within an invoice.
  • ADJ — Adjustment: provider/payer adjustments such as tax, dispensing fees, and mark-ups applied to a line item or response summary.

There is no combined "PSC" segment; these responsibilities are split across the segments above.

Used in

Nothing — PSC is not part of any HL7 v2 message structure. The real segments are used in Claims and Reimbursement messages (the invoice/billing message family in chapter 16), where an invoice is built from IVC, PSS, PSG, PSL, and ADJ segments to identify the invoice, its sections, its product/service groups, its line items, and their adjustments.

Field-by-field reference

There are no fields to list, because PSC is not a defined segment. The row below records the verified status. Source: HAPI HL7v2 v2.5.1 javadocs (segment package summary); the real PSG definition was confirmed at v2plus.hl7.org.

SeqNameData TypeLengthReqRepeatTable #Description
(no PSC segment defined)HL7 v2 defines no PSC segment. Use PSG (group), PSL (line item), PSS (section), and ADJ (adjustment) instead.

Most-used fields

Not applicable — there is no PSC segment. In the real Claims model, the most-used segments are PSL (each billable line) and ADJ (each adjustment to a line or summary), grouped under PSG.

Version differences (2.3 to 2.8.2)

No version of HL7 v2 from 2.3 through 2.8.2 defines a PSC segment. The Claims and Reimbursement segment family it is confused with (IVC, PSS, PSG, PSL, ADJ) was introduced with the chapter 16 billing content in the later 2.x line and is carried through 2.8.2. If a partner emits a non-standard PSC line, it is a local/custom Z-style segment defined by that partner, not by the HL7 standard.

Common mistakes

  • Expecting a standard PSC segment. There is none; any PSC|... line is non-conformant or a local custom segment.
  • Collapsing "group" and "adjustment" into one segment. In HL7 v2 these are separate: PSG groups, ADJ adjusts.
  • Building a PSC field map from a third-party cheat sheet. Only the trading partner emitting a custom PSC can define its layout.

Examples

There is no valid standard PSC segment, so no conformant example can be shown. The example below illustrates the real intent — a product/service group with a line item and an adjustment — using the genuine segments:

PSG|GRP1^ProviderGroup|||20260701
PSL|1|LINE1^ProviderLine||99213^Office Visit^CPT|||100.00
ADJ|1|P|TAX^Sales Tax^HL70565|||8.25

Annotated breakdown (illustrative field roles; confirm exact positions against the target version):

PSG|GRP1^ProviderGroup...   ← Product/Service Group: groups the line items below
PSL|1|LINE1^ProviderLine... ← Product/Service Line Item: one billable service
ADJ|1|P|TAX^Sales Tax...    ← Adjustment: a provider adjustment (tax) on the line

FHIR mapping

Not mapped, because PSC is not a defined segment and has no ConceptMap in the v2-to-FHIR IG. The real segments map toward FHIR billing resources: PSG/PSL toward Claim.item groupings and line items, and ADJ toward adjudication/adjustment structures on ClaimResponse. Implementations define the exact projection locally.

Engine considerations

  • Do not register a standard PSC handler. If a feed contains PSC, treat it as a custom segment and require an explicit local definition from the sender.
  • When someone reports "PSC — Product Service Group Adjustment," split the concern: grouping belongs to PSG, the billable line to PSL, and adjustments to ADJ.

How Vorro parses and produces PSC

Vorro has no built-in PSC segment because HL7 v2 defines none. If a partner sends a custom PSC line, Vorro treats it as a locally defined Z-style segment governed by that partner's specification. For the Claims and Reimbursement intent behind the name, Vorro parses and produces the real segments — PSG, PSL, PSS, and ADJ — and maps them toward the FHIR Claim/ClaimResponse resources on output.

  • PSG — Product/Service Group, the real grouping segment.
  • PSL — Product/Service Line Item, the real billable-line segment.
  • ADJ — Adjustment, the real adjustment segment.

Sources

← Back to HL7 v2 Guide

Ready to Integrate This Into Your Workflow?

Talk to a Vorro expert about implementing HL7 v2 in your specific environment.

Browse HL7 v2 Guides
HL7 PSC: not a defined HL7 v2 segment (identity note) | Vorro Academy | Vorro