The LAN (Language Detail) segment records the languages a staff member or practitioner can use, along with how they can use each one and how well. It pairs a language code with one or more ability codes (such as read, write, or speak) and a proficiency code (such as excellent, good, or fair). LAN is repeatable, so a multilingual practitioner can carry one LAN occurrence per language within a single staff record.
LAN belongs to the same personnel detail family as AFF (Professional Affiliation) and EDU (Educational Detail). Together these segments describe a practitioner's credentials, training, and capabilities and share consistent personnel and credential terminology across the staff master file.
Purpose
The purpose of LAN is to express the linguistic capabilities of a practitioner so that scheduling, matching, and directory systems can connect patients with providers who speak their language. Each LAN occurrence names a language, describes the abilities the practitioner has in that language, and rates the proficiency. This supports tasks such as routing a Spanish-speaking patient to a Spanish-speaking clinician or flagging when an interpreter is needed.
LAN is a detail segment and never stands alone. It supplements a staff record introduced by STF and qualified by PRA (Practitioner Detail). The language capability it describes belongs to the person identified earlier in that staff record.
Used in
LAN is a staff/practitioner detail segment used in the MFN^M02 message (Master File Notification - Staff/Practitioner). Within that message it follows the STF and PRA segments, repeating once per language the staff member can use. The MFN^M02 message synchronizes practitioner master data between systems, and LAN contributes the language-capability portion of that record.
Field-by-field reference
Source: HAPI HL7v2 v2.5.1 javadocs (https://hapifhir.github.io/hapi-hl7v2/v251/apidocs/ca/uhn/hl7v2/model/v251/segment/LAN.html) for sequence, name, data type, and repetition. Length is not published in the javadocs (—); Required and Table # are filled from the HL7 v2.5.1 standard where well-established.
| Seq | Name | Data Type | Length | Req | Repeat | Table # | Description |
|---|---|---|---|---|---|---|---|
| LAN-1 | Set ID - LAN | si | — | R | — | — | Sequence number for this LAN occurrence |
| LAN-2 | Language Code | ce | — | O | — | HL70296 | Language the practitioner can use |
| LAN-3 | Language Ability Code | ce | — | O | Y | HL70403 | How the practitioner uses the language |
| LAN-4 | Language Proficiency Code | ce | — | O | — | HL70404 | How well the practitioner uses language |
Most-used fields
LAN-1 (Set ID) is mandatory and numbers the languages within the staff record. LAN-2 (Language Code) is the central field and is bound to user-defined table HL70296; it identifies which language the occurrence is about and is effectively always present. LAN-3 (Language Ability Code), bound to HL70403, is the only repeating field and lets a single language carry several abilities such as speak, read, and write. LAN-4 (Language Proficiency Code), bound to HL70404, qualifies the overall skill level and is commonly populated when proficiency must drive patient-provider matching.
Version differences (2.3 to 2.8.2)
LAN was introduced with the staff/practitioner master file segments in HL7 v2.3 and has retained its compact four-field structure through v2.8.2. The fields and their CE data types are stable across the range; the main evolution is terminological, as the language, ability, and proficiency tables (HL70296, HL70403, HL70404) were clarified and, in some editions, recommended for binding to external vocabularies. The CE type itself gained alternate-coding handling refinements in later versions, but no LAN field was added, removed, or renumbered, making LAN one of the most portable personnel detail segments.
Common mistakes
A frequent mistake is sending only a free-text language name in LAN-2 without a coded value from HL70296, which prevents reliable language matching. Another is collapsing multiple abilities into one LAN-3 value or repeating the whole segment instead of repeating LAN-3, when the standard expects multiple abilities as repetitions within a single occurrence. Implementers also confuse ability (LAN-3, what the person can do) with proficiency (LAN-4, how well), placing a proficiency value in the ability field. Finally, omitting LAN-1 or reusing the same Set ID across occurrences breaks downstream sequencing.
Examples
Minimal LAN (Set ID and language only):
LAN|1|spa^Spanish^HL70296
Fully-populated LAN:
LAN|1|spa^Spanish^HL70296|1^Read^HL70403~2^Write^HL70403~3^Speak^HL70403|1^Excellent^HL70404
Annotated breakdown:
LAN|1|spa^Spanish^HL70296|1^Read^HL70403~2^Write^HL70403~3^Speak^HL70403|1^Excellent^HL70404
| | | |
| | | +--> LAN-4 Language Proficiency Code (CE) = Excellent
| | +-------------------------------------------------> LAN-3 Language Ability Code (CE, repeats) = Read, Write, Speak
| +--------------------------------------------------------------------> LAN-2 Language Code (CE) = Spanish
+-----------------------------------------------------------------------> LAN-1 Set ID (SI) = 1
In-context excerpt 1 — LAN inside an MFN^M02 staff master-file message, following STF and PRA, with two languages:
MSH|^~&|HRPORTAL|VORRO|REGISTRY|STATE|20260610120000||MFN^M02^MFN_M02|MSG00061|P|2.5.1
MFI|PRA^Practitioner Master^HL70175|||UPD|20260610120000
MFE|MAD|||PROV4471
STF|PROV4471|9988776^^^NPI|Okafor^Adaeze^N|P|F|19840712|A
PRA|PROV4471|VORRO^Vorro Health^L|CARD^Cardiology^HL70358|||MD^Doctor of Medicine^HL70360
LAN|1|eng^English^HL70296|1^Read^HL70403~2^Write^HL70403~3^Speak^HL70403|1^Excellent^HL70404
LAN|2|spa^Spanish^HL70296|3^Speak^HL70403|2^Good^HL70404
In-context excerpt 2 — LAN inside an MFN^M02 for a multilingual nurse:
MSH|^~&|HRPORTAL|VORRO|REGISTRY|STATE|20260610123000||MFN^M02^MFN_M02|MSG00062|P|2.5.1
MFI|PRA^Practitioner Master^HL70175|||UPD|20260610123000
MFE|MAD|||PROV5512
STF|PROV5512|6655443^^^NPI|Lindqvist^Erik^J|P|M|19900223|A
PRA|PROV5512|VORRO^Vorro Health^L|MED^Medical-Surgical^HL70358|||RN^Registered Nurse^HL70360
LAN|1|eng^English^HL70296|1^Read^HL70403~2^Write^HL70403~3^Speak^HL70403|1^Excellent^HL70404
LAN|2|swe^Swedish^HL70296|1^Read^HL70403~2^Write^HL70403~3^Speak^HL70403|1^Excellent^HL70404
LAN|3|fre^French^HL70296|3^Speak^HL70403|3^Fair^HL70404
FHIR mapping
There is no segment-level ConceptMap published in the v2-to-FHIR Implementation Guide for LAN, so the target is "Not mapped at the segment level." Conceptually, LAN aligns with Practitioner.communication: LAN-2 (Language Code) corresponds to the communication language CodeableConcept, while LAN-3 (ability) and LAN-4 (proficiency) have no direct standard FHIR element and are typically dropped or carried as extensions. Any LAN-to-Practitioner.communication transform must be defined locally and verified per interface.
Engine considerations
LAN is a repeating detail segment, so an engine must group all LAN occurrences under the preceding STF/PRA and keep the LAN-1 Set ID order on re-serialization. LAN-3 repeats within a single occurrence using the repetition delimiter, so engines should expand it into a list of abilities rather than concatenating them. Because LAN-2, LAN-3, and LAN-4 are all CE fields bound to HL70296, HL70403, and HL70404, engines should resolve each against its configured table and preserve the coding system identifier so that downstream matching is deterministic. Free-text-only language values should be flagged for normalization.
How Vorro parses and produces LAN
When Vorro parses LAN, each occurrence becomes a normalized language-capability record linked to the practitioner from STF/PRA. LAN-2 is resolved against the language table (HL70296), the repeating LAN-3 abilities are captured as a list resolved against HL70403, and LAN-4 proficiency is resolved against HL70404. LAN-1 is retained as the stable ordering key.
When Vorro produces LAN, it emits one segment per language on the source record, assigns LAN-1 sequentially from 1, and writes the normalized language code into LAN-2 with its coding system. Each ability is emitted as a repetition within LAN-3, and the proficiency is placed in LAN-4, each carrying its proper table reference rather than free text alone.
Related pages
- STF Segment: Staff Identification
- PRA Segment: Practitioner Detail
- MFN^M02 Message: Master File Notification - Staff/Practitioner
- AFF Segment: Professional Affiliation
- EDU Segment: Educational Detail
