The EDU (Educational Detail) segment records a staff member's or practitioner's formal education. It captures the academic degree earned, the school that granted it, the relevant date ranges, and the major field of study. EDU is repeatable, so a practitioner with multiple degrees can carry one EDU occurrence per credential within a single staff record.
EDU belongs to the same personnel detail family as AFF (Professional Affiliation) and LAN (Language Detail). These segments together describe a practitioner's credentials, training, and capabilities, and they share consistent personnel and credential terminology across the staff master file.
Purpose
The purpose of EDU is to express where and when a practitioner was educated and what degree resulted. Typical examples include a Doctor of Medicine from a named medical school, a Bachelor of Science in Nursing, or a Master of Public Health. Each EDU occurrence binds the degree to the granting institution and to its address, and records the dates the program ran, the dates the person participated, and when the degree was granted — enough context for credential verification and provider-directory enrichment.
EDU is a detail segment and never stands alone. It supplements a staff record introduced by STF and qualified by PRA (Practitioner Detail). The education it describes belongs to the person identified earlier in that staff record.
Used in
EDU 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 degree the staff member holds. The MFN^M02 message synchronizes practitioner master data between systems, and EDU contributes the educational 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/EDU.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 |
|---|---|---|---|---|---|---|---|
| EDU-1 | Set ID - EDU | si | — | R | — | — | Sequence number for this EDU occurrence |
| EDU-2 | Academic Degree | is | — | O | — | — | Degree earned by the practitioner |
| EDU-3 | Academic Degree Program Date Range | dr | — | O | — | — | Start and end dates of the degree program |
| EDU-4 | Academic Degree Program Participation Date Range | dr | — | O | — | — | Dates the practitioner participated in program |
| EDU-5 | Academic Degree Granted Date | dt | — | O | — | — | Date the academic degree was granted |
| EDU-6 | School | xon | — | O | — | — | Institution that granted the degree |
| EDU-7 | School Type Code | ce | — | O | — | — | Coded type of educational institution |
| EDU-8 | School Address | xad | — | O | — | — | Postal address of the granting school |
| EDU-9 | Major Field of Study | cwe | — | O | Y | — | Field of study or specialization earned |
Most-used fields
EDU-1 (Set ID) is mandatory and numbers the degrees within the staff record. EDU-2 (Academic Degree) and EDU-6 (School) are the two fields that carry the substance of the segment — the credential and the institution that issued it — and are almost always present when EDU is sent. EDU-5 (Academic Degree Granted Date) is widely used for credential verification because it anchors when the qualification became valid. EDU-9 (Major Field of Study) is the only repeating field and is used when a degree spans more than one discipline. The two DR date ranges, EDU-3 and EDU-4, are frequently omitted when only the grant date matters.
Version differences (2.3 to 2.8.2)
EDU was introduced alongside the staff/practitioner master file segments in HL7 v2.3 and has kept its nine-field shape through v2.8.2. The biggest evolution is in EDU-9 (Major Field of Study): the underlying coded type was tightened toward CWE (coded with exceptions) in v2.5.1, where earlier and some later editions describe it with closely related coded types. EDU-2 (Academic Degree) remains an IS field bound to a user-defined degree table throughout. The XON type for EDU-6 and the XAD type for EDU-8 gained extra components in later versions, but no EDU fields were added, removed, or renumbered, so EDU parsers are broadly portable across the range.
Common mistakes
A common mistake is sending a free-text degree string in EDU-2 instead of the expected coded value, which defeats normalized degree lookups. Another is confusing EDU-3 (program date range) with EDU-4 (participation date range); the program range describes the program itself, while the participation range describes when this individual was enrolled. Implementers also sometimes place the grant date inside a DR range field rather than in EDU-5, which is a single DT. Finally, because EDU-9 is the only repeating field, teams occasionally try to repeat the whole segment to express multiple majors when they should instead repeat EDU-9 within one occurrence.
Examples
Minimal EDU (Set ID, degree, and school only):
EDU|1|MD|||
Fully-populated EDU:
EDU|1|MD^Doctor of Medicine^HL70360|20040901^20080601|20040901^20080601|20080601|2231^Johns Hopkins University School of Medicine^L|U^University^HL70402|733 N Broadway^^Baltimore^MD^21205^USA|MED^Medicine^L~RES^Clinical Research^L
Annotated breakdown:
EDU|1|MD^Doctor of Medicine^HL70360|20040901^20080601|...|20080601|2231^Johns Hopkins...^L|U^University^HL70402|733 N Broadway^...|MED^Medicine^L~RES^...
| | | | | | | |
| | | | | | | +--> EDU-9 Major Field of Study (CWE, repeats)
| | | | | | +-------------------> EDU-8 School Address (XAD)
| | | | | +-----------------------------------------> EDU-7 School Type Code (CE)
| | | | +--------------------------------------------------------------------> EDU-6 School (XON)
| | | +-----------------------------------------------------------------------------> EDU-5 Degree Granted Date (DT) 2008-06-01
| | +-------------------------------------------------------------------------------------------------------> EDU-3 Program Date Range (DR)
| +------------------------------------------------------------------------------------------------------------------------------------> EDU-2 Academic Degree (IS)
+---------------------------------------------------------------------------------------------------------------------------------------> EDU-1 Set ID (SI) = 1
In-context excerpt 1 — EDU inside an MFN^M02 staff master-file message, following STF and PRA, with two degrees:
MSH|^~&|HRPORTAL|VORRO|REGISTRY|STATE|20260610120000||MFN^M02^MFN_M02|MSG00051|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
EDU|1|MD^Doctor of Medicine^HL70360|||20080601|2231^Johns Hopkins University School of Medicine^L|U^University^HL70402|733 N Broadway^^Baltimore^MD^21205^USA|MED^Medicine^L
EDU|2|BS^Bachelor of Science^HL70360|||20040515|1187^University of Lagos^L|U^University^HL70402|^^Lagos^^^NGA|BIO^Biology^L
In-context excerpt 2 — EDU inside an MFN^M02 for a nursing degree:
MSH|^~&|HRPORTAL|VORRO|REGISTRY|STATE|20260610123000||MFN^M02^MFN_M02|MSG00052|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
EDU|1|BSN^Bachelor of Science in Nursing^HL70360|||20120520|3344^University of Washington^L|U^University^HL70402|1959 NE Pacific St^^Seattle^WA^98195^USA|NUR^Nursing^L
FHIR mapping
There is no segment-level ConceptMap published in the v2-to-FHIR Implementation Guide for EDU, so the target is "Not mapped at the segment level." Conceptually, EDU aligns with Practitioner.qualification: EDU-2 (Academic Degree) corresponds to qualification.code, EDU-6 (School) corresponds to qualification.issuer, and EDU-5 (Academic Degree Granted Date) informs qualification.period. Any EDU-to-Practitioner.qualification transform must be defined locally and verified per interface, because no normalized mapping is standardized.
Engine considerations
EDU is a repeating detail segment, so an engine must group all EDU occurrences under the preceding STF/PRA and preserve the EDU-1 Set ID ordering on re-serialization. Both EDU-3 and EDU-4 use the DR type and require range-aware parsing into start and end dates, while EDU-5 is a single DT and must not be treated as a range. EDU-9 repeats within a single occurrence using the repetition delimiter, so engines should expand it into a list rather than concatenating values. When EDU-2 carries an IS code, engines should resolve it against the configured degree table rather than passing the raw string through unmapped.
How Vorro parses and produces EDU
When Vorro parses EDU, each occurrence becomes a normalized education record linked to the practitioner from STF/PRA. EDU-2 is resolved against the degree table, EDU-6 is decomposed into its XON components so the school name and identifier are stored separately, and the DR ranges in EDU-3 and EDU-4 are expanded into discrete start and end dates. EDU-5 is stored as a single grant date, and the repeating EDU-9 majors are captured as a list. EDU-1 is kept as the stable ordering key.
When Vorro produces EDU, it emits one segment per degree on the source record, assigns EDU-1 sequentially from 1, and writes the normalized degree and school back into their respective IS and XON structures. Date ranges are reassembled into DR format for EDU-3 and EDU-4, the grant date is placed in EDU-5, and multiple majors are emitted as repetitions within EDU-9.
Related pages
- STF Segment: Staff Identification
- PRA Segment: Practitioner Detail
- MFN^M02 Message: Master File Notification - Staff/Practitioner
- AFF Segment: Professional Affiliation
- LAN Segment: Language Detail
