HL7 EDU Educational Detail
HL7 field reference EDU 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 |
|---|---|---|---|---|---|
| EDU.1 | Set ID - EDU | Yes | No | SI | |
| EDU.2 | Academic Degree | No | No | IS | 0360 |
| EDU.3 | Academic Degree Program Date Range | No | No | DR | |
| EDU.4 | Academic Degree Program Participation Date Range | No | No | DR | |
| EDU.5 | Academic Degree Granted Date | No | No | DT | |
| EDU.6 | School | No | No | XON | |
| EDU.7 | School Type Code | No | No | CE | 0402 |
| EDU.8 | School Address | No | No | XAD | |
| EDU.9 | Major Field of Study | No | Yes | CWE |
EDU carries education and training details for a practitioner, staff member, or master-file person record.
The standard describes EDU this way: The EDU segment adds detailed educational information to the staff member identified by the STF segment. An EDU segment may optionally follow an STF segment. An EDU segment must always have been preceded by a corresponding STF 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 EDU in MFN_M02 - Master file - staff practitioner, PMU_B01 - Add personnel record, and RSP_K25 - RSP - Personnel Information by Segment 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.
EDU-1 is the sequence number for this EDU segment within its repeating group. It keeps multiple EDU lines in order; it is not the business identifier for the master-file record.
EDU-2 carries Academic Degree for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0360; many real interfaces narrow that list further, so follow the receiver's implementation guide.
EDU-3 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
EDU-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
EDU-5 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
EDU-6 carries School for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
EDU-7 identifies the School Type 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.
The generated panel links this to HL7 table 0402; many real interfaces narrow that list further, so follow the receiver's implementation guide.
EDU-8 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
EDU-9 carries Major Field of Study for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
Related links
- MFI - Master File Identification
- MFE - Master File Entry
- MFA - Master File Acknowledgment
- LOC - Location Identification
- STF - Staff Identification
- PRA - Practitioner Detail
- OM1 - General Segment
- CDM - Charge Description Master
- MFN_M02 - Master file - staff practitioner
- PMU_B01 - Add personnel record