Schedule a demo
Healthcare/HL7 v2/IVC
Segment

Invoice segment

Serves as the header segment for healthcare services invoices, carrying provider and payer invoice numbers, invoice type, invoice date, total billed amount, provider and payer organization identifiers, and payment terms. It is sent by a provider application to a payer application in EHC (Submit HealthCare Services Invoice) messages and is echoed in all subsequent interactions for that invoice. IVC is the anchor segment for the claims and reimbursement message group.

30fields
9required
v2.9HL7 version
ivc.py
from zato.hl7v2.v2_9 import IVC
from zato.hl7v2.v2_9 import EI, CP, CWE

ivc = IVC()
invoice_number = EI(entity_identifier='INV202401150001')
ivc.provider_invoice_number = invoice_number
ivc.invoice_amount = CP(price='75.00')
ivc.invoice_type = CWE(
    identifier='FS',
    text='Fee for Service'
)
Python examples

Build IVC segments in Python

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

1

Wellness service invoice

Invoice for fitness assessment

from zato.hl7v2.v2_9 import IVC
from zato.hl7v2.v2_9 import EI, CP, CWE, DTM, XON

ivc = IVC()
ivc.provider_invoice_number = EI(entity_identifier='INV202401150001')
ivc.invoice_type = CWE(
    identifier='FS',
    text='Fee for Service'
)
ivc.invoice_amount = CP(price='75.00')
ivc.invoice_date_time = DTM('20240115')
ivc.payer_organization = XON(
    organization_name='HealthFirst Insurance',
    organization_identifier='HLTH001'
)
2

Nutrition services invoice

Invoice for dietary counseling

from zato.hl7v2.v2_9 import IVC
from zato.hl7v2.v2_9 import EI, CP, CWE, DTM, XON

ivc = IVC()
ivc.provider_invoice_number = EI(entity_identifier='INV202401160002')
ivc.invoice_type = CWE(
    identifier='FS',
    text='Fee for Service'
)
ivc.invoice_amount = CP(price='95.00')
ivc.invoice_date_time = DTM('20240116')
ivc.payer_organization = XON(
    organization_name='WellCare Insurance',
    organization_identifier='HLTH002'
)
3

Preventive care invoice

Invoice for annual wellness screening

from zato.hl7v2.v2_9 import IVC
from zato.hl7v2.v2_9 import EI, CP, CWE, DTM, XON

ivc = IVC()
ivc.provider_invoice_number = EI(entity_identifier='INV202401170003')
ivc.invoice_type = CWE(
    identifier='FS',
    text='Fee for Service'
)
ivc.invoice_amount = CP(price='150.00')
ivc.invoice_date_time = DTM('20240117')
ivc.payer_organization = XON(
    organization_name='HealthFirst Insurance',
    organization_identifier='HLTH001'
)
Tutorials

Learn by building

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

MLLP
Receive and parse HL7 v2 messages
Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.
Start tutorial Build
Build and send HL7 v2 messages
Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.
Start tutorial
Related segments

Commonly used with IVC

IPR Invoice processing results GP1 Grouping/reimbursement - visit GP2 Grouping/reimbursement - procedure line item FT1 Financial transaction
FAQ

Frequently asked questions

IVC contains invoice information including invoice numbers, amounts, dates, and payer details for wellness program billing and claims.

Common invoice types include FS (Fee for Service), which is typical for wellness and preventive care services.

Use payer_organization field with XON datatype:

ivc.payer_organization = XON(
    organization_name='HealthFirst Insurance',
    organization_identifier='HLTH001'
)

IVC contains the invoice details while IPR contains the processing results. IPR segments follow IVC to report adjudication outcomes.

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.

Reference

IVC field reference

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

#Python nameDatatypeUsageRepeatableTable
1▶provider_invoice_numberEIRequiredNo-
2▶payer_invoice_numberEIOptionalNo-
3▶contract_agreement_numberEIOptionalNo-
4▶invoice_controlCWERequiredNoHL70553
5▶invoice_reasonCWERequiredNoHL70554
6▶invoice_typeCWERequiredNoHL70555
7invoice_date_timeDTMRequiredNo-
8▶invoice_amountCPRequiredNo-
9payment_termsSTOptionalNo-
10▶provider_organizationXONRequiredNo-
11▶payer_organizationXONRequiredNo-
12▶attentionXCNOptionalNo-
13last_invoice_indicatorIDOptionalNoHL70136
14invoice_booking_periodDTMOptionalNo-
15originSTOptionalNo-
16▶invoice_fixed_amountCPOptionalNo-
17▶special_costsCPOptionalNo-
18▶amount_for_doctors_treatmentCPOptionalNo-
19▶responsible_physicianXCNOptionalNo-
20▶cost_centerCXOptionalNo-
21▶invoice_prepaid_amountCPOptionalNo-
22▶total_invoice_amount_without_prepaid_amountCPOptionalNo-
23▶total_amount_of_vatCPOptionalNo-
24vat_rates_appliedNMOptionalYes-
25▶benefit_groupCWERequiredNoHL70556
26provider_tax_idSTOptionalNo-
27payer_tax_idSTOptionalNo-
28▶provider_tax_statusCWEOptionalNoHL70572
29▶payer_tax_statusCWEOptionalNoHL70572
30sales_tax_idSTOptionalNo-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs
Open source In Python