ADJ carries a single financial adjustment line — a payer or provider change applied to a charge, a product/service line item, or a payment. A surcharge such as tax, a dispensing fee, a discount, a penalty, or a contractual write-off is each expressed as one ADJ. The segment names who made the adjustment (provider versus payer), classifies it by category, attaches a reason code, and states the amount. ADJ is a relatively uncommon segment: it appears only in financial messages that itemize adjustments, and it was introduced into the standard around v2.6, so older interfaces never emit it.
Note: ADJ is a v2.6+ segment. This page keeps version: "2.5.1" in the frontmatter for consistency with the rest of this reference set, but ADJ does not exist in 2.5.1 — see Version differences below.
Purpose
ADJ records one adjustment to a financial item. Each ADJ ties a provider adjustment number and a payer adjustment number together, sequences itself relative to sibling adjustments on the same item, classifies the adjustment by category, and carries the monetary amount plus an optional reason code. Multiple adjustments to one item are sent as multiple ADJ segments, each with its own sequence number.
Used in
ADJ appears in financial and billing messages where adjustments are itemized — most commonly within DFT (Detailed Financial Transaction) messages, attached to the financial transaction it modifies. It is also used in claim and payment/remittance message structures introduced alongside it in v2.6+. ADJ is always subordinate to the item it adjusts (for example an FT1 financial transaction); it never stands alone.
Field-by-field reference
Source: ADJ has no published segment-level map in the HL7 v2-to-FHIR IG, so this table is built from the HL7 v2.6+/2.8 standard ADJ definition. R = required (cardinality min ≥ 1), O = optional. Repeat = field may repeat. Length is — (not reproduced here). Table numbers are shown only where well established.
Confidence note: ADJ is a less-common segment and is not defined in v2.5.1. The field list below reflects the v2.6+/2.8 standard and should be treated as lower-confidence than the high-traffic segments in this reference. Verify the exact sequence, optionality, and table assignments against the HL7 v2.8 base standard before relying on them for a production interface.
| Seq | Name | Data Type | Length | Req | Repeat | Table # | Description |
|---|---|---|---|---|---|---|---|
| ADJ-1 | Provider Adjustment Number | EI | — | R | — | — | Unique adjustment number assigned by the provider application. |
| ADJ-2 | Payer Adjustment Number | EI | — | R | — | — | Unique adjustment number assigned by the payer application. |
| ADJ-3 | Adjustment Sequence Number | SI | — | R | Y | — | Sequence of this adjustment among adjustments on the same item — starts at 1, then 2, and so on. |
| ADJ-4 | Adjustment Category | CWE | — | R | — | HL70564 | Category of adjustment; determines which reason table applies. |
| ADJ-5 | Adjustment Amount | CP | — | O | — | — | Monetary amount of the adjustment (composite price). |
| ADJ-6 | Adjustment Quantity | CQ | — | O | — | HL70560 | Quantity the adjustment applies to. |
| ADJ-7 | Adjustment Reason PA | CWE | — | O | — | HL70565 | Reason for the adjustment (payer adjustment reason). |
| ADJ-8 | Adjustment Description | ST | — | O | — | — | Free-text description of the adjustment. |
| ADJ-9 | Original Value | NM | — | O | — | — | Value before the adjustment. |
| ADJ-10 | Substitute Value | NM | — | O | — | — | Value after the adjustment. |
| ADJ-11 | Adjustment Action | CWE | — | O | — | HL70569 | Action taken as a result of the adjustment. |
| ADJ-12 | Provider Adjustment Number Cross Reference | EI | — | O | — | — | Links this adjustment to a related provider adjustment number. |
| ADJ-13 | Provider Product/Service Line Item Number Cross Reference | EI | — | O | — | — | Links the adjustment to a provider product/service line item. |
| ADJ-14 | Adjustment Date | DTM | — | R | — | — | Date/time the adjustment was made. |
| ADJ-15 | Responsible Organization | XON | — | O | — | — | Organization responsible for the adjustment. |
Most-used fields
ADJ-4 Adjustment Category is the field that classifies the adjustment and decides which reason vocabulary applies, so it is read first by any consumer that branches on adjustment type.
ADJ-5 Adjustment Amount carries the money — a composite price (CP) value — and is what most downstream accounting logic actually consumes.
ADJ-7 Adjustment Reason PA explains why the adjustment exists (for example a contractual discount or a coverage denial). ADJ-1 and ADJ-2 (provider and payer adjustment numbers) are the correlation handles that let provider and payer systems reconcile the same adjustment, and ADJ-3 Adjustment Sequence Number disambiguates multiple adjustments stacked on one item.
Version differences (2.3 to 2.8.2)
- 2.3 / 2.4 / 2.5 / 2.5.1: ADJ does not exist. Financial adjustments in these versions are handled inside other financial segments (for example FT1) rather than in a dedicated adjustment segment.
- 2.6: ADJ introduced as a dedicated adjustment segment to itemize provider and payer adjustments on financial line items.
- 2.7 / 2.8 / 2.8.2: ADJ field set carried forward and refined; the core fields (ADJ-1 through ADJ-15 above) are stable in this range. Receivers built for 2.5.1 or earlier will not recognize ADJ at all.
Common mistakes
- Sending ADJ to a receiver pinned to v2.5.1 or earlier, which has no definition for it — the segment is silently dropped or rejected.
- Treating ADJ-5 Adjustment Amount as a plain number when it is a composite price (CP) data type with currency components.
- Reusing or omitting ADJ-3 Adjustment Sequence Number, which collapses multiple distinct adjustments on the same item into one.
- Failing to populate both ADJ-1 (provider) and ADJ-2 (payer) adjustment numbers, breaking provider/payer reconciliation.
- Picking a reason code in ADJ-7 from the wrong table because ADJ-4 Adjustment Category was not set correctly.
Examples
Minimal ADJ (required fields only — provider/payer numbers, sequence, category, date):
ADJ|PADJ-1001|YADJ-2001|1|DISC^Discount^HL70564||||||||||20260609
Fully-populated ADJ:
ADJ|PADJ-1001|YADJ-2001|1|DISC^Discount^HL70564|USD^25.00^USD|1^^HL70560|45^Contractual adjustment^HL70565|Network contractual discount|125.00|100.00|ADJ^Adjudicated^HL70569|PADJ-1000|PSLI-7788|20260609120000|VORRO BILLING INC^^^^^^^^^987654321
Annotated breakdown of the minimal example:
ADJ ← segment ID
PADJ-1001 ← ADJ-1 Provider Adjustment Number
YADJ-2001 ← ADJ-2 Payer Adjustment Number
1 ← ADJ-3 Adjustment Sequence Number
DISC^Discount^HL70564 ← ADJ-4 Adjustment Category
← ADJ-5..13 empty (amount, quantity, reason, etc.)
20260609 ← ADJ-14 Adjustment Date
In-context inside a DFT^P03 (post detail financial transaction), with ADJ following the FT1 it adjusts:
MSH|^~&|BILLING|HOSP_A|PAYER|PLAN_B|20260609120000||DFT^P03^DFT_P03|CTRL-7001|P|2.6
EVN|P03|20260609120000
PID|1||123456^^^HOSP^MR||DOE^JOHN^A||19800101|M
FT1|1|TXN-5501||20260609|20260609|CG|99213^Office Visit^CPT|||1|125.00
ADJ|PADJ-1001|YADJ-2001|1|DISC^Discount^HL70564|USD^25.00^USD||45^Contractual adjustment^HL70565|||||||20260609
In-context with two adjustments stacked on the same line item (note the incrementing ADJ-3):
FT1|1|TXN-5502||20260609|20260609|CG|80053^Metabolic Panel^CPT|||1|90.00
ADJ|PADJ-1100|YADJ-2100|1|DISC^Discount^HL70564|USD^10.00^USD||45^Contractual adjustment^HL70565|||||||20260609
ADJ|PADJ-1101|YADJ-2101|2|TAX^Tax^HL70564|USD^2.50^USD||T1^Sales tax^HL70565|||||||20260609
FHIR mapping
No segment-level ConceptMap is published in the v2-to-FHIR IG for ADJ. The HL7 v2-to-FHIR IG segment maps index does not list an ADJ map, so there is no authoritative field-by-field crosswalk to cite.
In FHIR, the concepts ADJ carries are not represented as a standalone resource. They live inside adjudication structures: ClaimResponse.adjudication (and .item.adjudication) for amounts and reasons applied during claim processing, and PaymentReconciliation.detail for adjustments expressed in a remittance. Mapping ADJ therefore means decomposing it into those elements rather than projecting it onto a single target resource.
| ADJ field | Likely FHIR target (no IG ConceptMap) |
|---|---|
| ADJ-4 Adjustment Category | ClaimResponse.adjudication.category |
| ADJ-5 Adjustment Amount | ClaimResponse.adjudication.amount / PaymentReconciliation.detail.amount |
| ADJ-7 Adjustment Reason PA | ClaimResponse.adjudication.reason |
| ADJ-1 / ADJ-2 Adjustment Numbers | PaymentReconciliation.detail.identifier |
| ADJ-14 Adjustment Date | PaymentReconciliation.detail.date |
The table above is illustrative, not an IG mapping. Confirm against your own profiles before implementing.
Engine considerations
- Version gate: only emit ADJ on channels negotiated at v2.6 or later. Sending it downstream to a 2.5.1 receiver will fail or be dropped.
- ADJ-5 is a CP (composite price) — parse and produce its currency components, do not coerce to a bare decimal.
- Keep ADJ adjacent to and after the financial item it modifies (for example the FT1), and preserve segment order; the adjustment's binding to its item is positional.
- Maintain ADJ-3 sequence integrity when an item carries several adjustments — renumber on merge/split rather than letting duplicates collapse.
- Because there is no IG ConceptMap, any FHIR transform for ADJ is bespoke; treat it as custom logic and test it against your adjudication profiles.
How Vorro parses and produces ADJ
Vorro parses ADJ only on channels declared v2.6+, binding each ADJ to the preceding financial item and preserving ADJ-3 sequence so stacked adjustments stay distinct. The composite price in ADJ-5 is decomposed into amount and currency rather than flattened. On the produce side, Vorro assigns provider and payer adjustment numbers (ADJ-1/ADJ-2) for reconciliation, sets ADJ-4 from the configured category table, and — because no segment-level FHIR map exists — routes ADJ through a bespoke transform into ClaimResponse.adjudication or PaymentReconciliation.detail per channel configuration.
Related pages
- FT1 — the financial transaction segment ADJ typically adjusts.
- IN1 — insurance segment that establishes the coverage an adjustment is applied under.
- DFT messages — the financial message where ADJ is itemized.
