HL7 LCC (Location Charge Code) | Integration Soup HL7 Reference Guide

HL7 LCC Location Charge Code

Master-file and catalog fields from experience.

HL7 field reference LCC fields from HL7 v2.5.1 Show fields

These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.

Fields

Field	Name	Required	Repeatable	Type	Table
LCC.1	Primary Key Value - LCC	Yes	No	PL
LCC.2	Location Department	Yes	No	CE	0264
LCC.3	Accommodation Type	No	Yes	CE	0129
LCC.4	Charge Code	Yes	Yes	CE	0132

LCC attaches charge codes to locations so location-based billing or costing can be configured.

The standard describes LCC this way: The optional LCC segment identifies how a patient location room can be billed by a certain department. A department can use different charge codes for the same room or bed, so there can be multiple LCC segments following an LDP segment.

Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.

Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.

The v2.5.1 structures show LCC in MFN_M05 - Patient location master file, MFR_M05 - Patient location master file, and RSP_Q11 - QBP - Query by parameter requesting an RSP segment pattern response. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.

For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.

LCC-1 Primary Key Value - LCC RequiredR SingleS TypePL

LCC-1 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.

LCC-2 Location Department RequiredR SingleS TypeCE Table0264

LCC-2 places the master-file record in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.

The generated panel links this to HL7 table 0264; many real interfaces narrow that list further, so follow the receiver's implementation guide.

LCC-3 Accommodation Type OptionalO RepeatableR TypeCE Table0129

LCC-3 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.

Use the agreed value set, starting from HL7 table 0129. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.

LCC-4 Charge Code RequiredR RepeatableR TypeCE Table0132

LCC-4 identifies the Charge Code for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.

If there are several identifiers, use repetitions deliberately and make each repeat self-explanatory rather than relying on position alone.

HL7^® Reference Guide