Schedule a demo
Segment

Adjustment

Carries financial adjustment details applied to a healthcare claim or invoice line, including the adjustment category, amount, quantity, reason code, and the responsible organization. It appears in claims and remittance advice messages (EHC^E01, EHC^E02, EHC^E04) to communicate payer-initiated or provider-initiated modifications to billed amounts, enabling reconciliation between submitted and adjudicated charges.

15fields
5required
v2.9HL7 version
adj.py
from zato.hl7v2 import ADJ

adj = ADJ()
adj.adjustment_sequence_number = '1'
adj.adjustment_amount = '150.00'
adj.adjustment_description = 'Contractual write-off'

Build ADJ segments in Python

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

1

Contractual write-off

Payer adjustment reducing the billed amount due to a contractual agreement with the provider

from zato.hl7v2.v2_9 import ADJ
from zato.hl7v2.v2_9 import EI, CWE

adj = ADJ()
adj.provider_adjustment_number = EI(
    entity_identifier='ADJ001',
    namespace_id='HOSP'
)
adj.payer_adjustment_number = EI(
    entity_identifier='PAY001',
    namespace_id='INS'
)
adj.adjustment_category = CWE(
    identifier='CO',
    text='Contractual',
    name_of_coding_system='HL70564'
)
adj.adjustment_amount = '150.00'
adj.adjustment_description = (
    'Contractual write-off'
)
adj.original_value = '500.00'
adj.substitute_value = '350.00'
adj.adjustment_date = '20240315'
2

Denial adjustment

Full denial of a claim line with the reason code and adjustment action indicating a reversal

from zato.hl7v2.v2_9 import ADJ
from zato.hl7v2.v2_9 import EI, CWE

adj = ADJ()
adj.provider_adjustment_number = EI(
    entity_identifier='ADJ002',
    namespace_id='HOSP'
)
adj.payer_adjustment_number = EI(
    entity_identifier='PAY002',
    namespace_id='INS'
)
adj.adjustment_sequence_number = '1'
adj.adjustment_category = CWE(
    identifier='PR',
    text='Patient responsibility',
    name_of_coding_system='HL70564'
)
adj.adjustment_amount = '250.00'
adj.adjustment_reason_pa = CWE(
    identifier='NCA',
    text='Not covered',
    name_of_coding_system='HL70565'
)
adj.adjustment_description = (
    'Non-covered service'
)
adj.original_value = '250.00'
adj.substitute_value = '0.00'
adj.adjustment_action = CWE(
    identifier='REV',
    text='Reversal',
    name_of_coding_system='HL70569'
)
adj.adjustment_date = '20240501'
3

Quantity-based correction

Adjustment reducing billed quantity with a cross-reference to the original line item

from zato.hl7v2.v2_9 import ADJ
from zato.hl7v2.v2_9 import EI, CWE, XON

adj = ADJ()
adj.provider_adjustment_number = EI(
    entity_identifier='ADJ003',
    namespace_id='HOSP'
)
adj.payer_adjustment_number = EI(
    entity_identifier='PAY003',
    namespace_id='INS'
)
adj.adjustment_sequence_number = '2'
adj.adjustment_category = CWE(
    identifier='OA',
    text='Other adjustment',
    name_of_coding_system='HL70564'
)
adj.adjustment_amount = '75.00'
adj.adjustment_description = (
    'Qty correction'
)
adj.original_value = '300.00'
adj.substitute_value = '225.00'
adj.provider_product_service_line_item_number_cross_reference = EI(
    entity_identifier='PSL001',
    namespace_id='HOSP'
)
adj.adjustment_date = '20240610'
adj.responsible_organization = XON(organization_name='Blue Cross')

Learn by building

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

Frequently asked questions

ADJ communicates financial adjustments to healthcare claims. It carries the adjustment category (contractual, patient responsibility, etc.), the amount, a reason code, original and substitute values, and the date. It appears in EHC claim and remittance messages to reconcile billed vs. paid amounts.

The adjustment_category field uses the CWE datatype with HL7 table 0564:

from zato.hl7v2.v2_9 import ADJ, CWE

adj = ADJ()
adj.adjustment_category = CWE(
    identifier='CO',
    text='Contractual',
    name_of_coding_system='HL70564'
)

The adjustment_reason_pa field uses CWE with HL7 table 0565:

from zato.hl7v2.v2_9 import ADJ, CWE

adj = ADJ()
adj.adjustment_reason_pa = CWE(
    identifier='NCA',
    text='Not covered',
    name_of_coding_system='HL70565'
)

Use the provider_product_service_line_item_number_cross_reference field with the EI datatype:

from zato.hl7v2.v2_9 import ADJ, EI

adj = ADJ()
adj.provider_product_service_line_item_number_cross_reference = EI(
    entity_identifier='PSL001',
    namespace_id='HOSP'
)

The responsible_organization field uses the XON (extended composite name and identification number for organizations) datatype:

from zato.hl7v2.v2_9 import ADJ, XON

adj = ADJ()
adj.responsible_organization = XON(organization_name='Blue Cross')

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.

ADJ field reference

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

#Python nameDatatypeUsageRepeatableTable
1provider_adjustment_numberEIRequiredNo-
2payer_adjustment_numberEIRequiredNo-
3adjustment_sequence_numberSIRequiredNo-
4adjustment_categoryCWERequiredNoHL70564
5adjustment_amountCPOptionalNo-
6adjustment_quantityCQOptionalNoHL70560
7adjustment_reason_paCWEOptionalNoHL70565
8adjustment_descriptionSTOptionalNo-
9original_valueNMOptionalNo-
10substitute_valueNMOptionalNo-
11adjustment_actionCWEOptionalNoHL70569
12provider_adjustment_number_cross_referenceEIOptionalNo-
13provider_product_service_line_item_number_cross_referenceEIOptionalNo-
14adjustment_dateDTMRequiredNo-
15responsible_organizationXONOptionalNo-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python