Schedule a demo
Healthcare/HL7 v2/LCC
Segment

Location charge code

Defines how a patient location is billed by a specific department, carrying the accommodation type and charge codes applicable to that location. Multiple LCC segments can follow an LDP segment, one per charge code. It is used in MFN location master file messages to cross-reference the bed and room master with the charge master, enabling automatic charge generation when patients are assigned to beds.

4fields
3required
v2.9HL7 version
lcc.py
from zato.hl7v2.v2_9 import LCC
from zato.hl7v2.v2_9 import CWE, PL

lcc = LCC()
lcc.primary_key_value_lcc = PL(
    point_of_care='WELL',
    room='SCR-1',
)
lcc.location_department = CWE(
    identifier='SCREEN',
    text='Screening suite',
    name_of_coding_system='HL70264',
)
lcc.charge_code = CWE(
    identifier='SCRFEE',
    text='Screening fee',
    name_of_coding_system='HL70132'
)
Python examples

Build LCC segments in Python

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

1

Screening room fee bundle

Ambulatory accommodation with screening and coach charge codes

from zato.hl7v2.v2_9 import LCC
from zato.hl7v2.v2_9 import CWE, PL

lcc = LCC()
lcc.primary_key_value_lcc = PL(
    point_of_care='WELL',
    room='SCR-1',
    facility='MAIN',
)
lcc.location_department = CWE(
    identifier='SCREEN',
    text='Screening suite',
    name_of_coding_system='HL70264',
)
lcc.accommodation_type = CWE(
    identifier='AMB',
    text='Ambulatory',
    name_of_coding_system='HL70129'
)
lcc.charge_code = [
    CWE(
        identifier='SCRFEE',
        text='Screening fee',
        name_of_coding_system='HL70132',
    ),
    CWE(
        identifier='COACH',
        text='Coach session',
        name_of_coding_system='HL70132',
    ),
]
2

Fitness assessment pricing

Movement lab PL with single performance charge code

from zato.hl7v2.v2_9 import LCC
from zato.hl7v2.v2_9 import CWE, PL

lcc = LCC()
lcc.primary_key_value_lcc = PL(
    point_of_care='WELL',
    room='MOVE-LAB',
    facility='FIT',
)
lcc.location_department = CWE(
    identifier='FITDEPT',
    text='Fitness assessment',
    name_of_coding_system='HL70264',
)
lcc.charge_code = CWE(
    identifier='MOVE',
    text='Movement screen',
    name_of_coding_system='HL70132'
)
3

Nutrition consultation fee

Counseling suite with dual meal-planning charge entries

from zato.hl7v2.v2_9 import LCC
from zato.hl7v2.v2_9 import CWE, PL

lcc = LCC()
lcc.primary_key_value_lcc = PL(
    point_of_care='WELL',
    room='NUT-3',
    facility='MAIN',
)
lcc.location_department = CWE(
    identifier='NCDEPT',
    text='Nutrition counseling',
    name_of_coding_system='HL70264',
)
lcc.accommodation_type = CWE(
    identifier='AMB',
    text='Ambulatory',
    name_of_coding_system='HL70129'
)
lcc.charge_code = [
    CWE(
        identifier='MEAL',
        text='Meal planning',
        name_of_coding_system='HL70132',
    ),
    CWE(
        identifier='FOLLOW',
        text='Follow-up visit',
        name_of_coding_system='HL70132',
    ),
]
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 LCC

MFI Master file identification MFE Master file entry LOC Location identification LCH Location characteristic LDP Location department LRL Location relationship
FAQ

Frequently asked questions

Field 4 lists every billable item tied to the location, for example a screening fee plus a coaching add-on when both post to the same suite.

LDP describes department services and hours, while LCC carries finance codes so wellness passes and nutrition visits price correctly per room.

Use optional CWE repeats from HL70129 when the same department needs distinct accommodation buckets:

from zato.hl7v2.v2_9 import LCC
from zato.hl7v2.v2_9 import CWE

lcc = LCC()
lcc.accommodation_type = CWE(
    identifier='AMB',
    text='Ambulatory',
    name_of_coding_system='HL70129'
)

Use the same PL convention as your LOC and LDP rows so charge routing software can join screening desks to their posted fee schedule.

Omit field 3 when accommodation does not split pricing, such as a single flat fitness assessment fee for the whole studio.

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

LCC field reference

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

#Python nameDatatypeUsageRepeatableTable
1▶primary_key_value_lccPLRequiredNo-
2▶location_departmentCWERequiredNoHL70264
3▶accommodation_typeCWEOptionalYesHL70129
4▶charge_codeCWERequiredYesHL70132

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs
Open source In Python