Build Hungarian Medical-Event Record (EESZT egészségügyi esemény)

Skill: Convert a clinical encounter into an EESZT reportable medical event

Region: Hungary (Magyarország) Category: Health care Does: Takes a clinical encounter (examination, treatment, discharge, document) and assembles the medical-event / EHR record (egészségügyi esemény) for electronic submission to the EESZT (Elektronikus Egészségügyi Szolgáltatási Tér) — declaring the service provider, the patient, the event type and time, the relevant diagnosis (BNO) and procedure codes, and any attached health document. Spec: EESZT — medical-event / EHR submission interface (current EESZT version)

Healthcare providers must report medical events (egészségügyi esemény) to EESZT — encounters, examinations, treatments, hospital admissions/discharges, and the associated documents (e.g. discharge summary, lab result) — to build the patient's central health record (EHR). Events are reported per encounter, generally at or shortly after the point of care. Element names below follow the medical-event structure, not a verbatim XSD; the EESZT interface is versioned, so confirm the current release.

When this applies

• A provider records an outpatient/inpatient encounter, diagnostic result, or treatment that is reportable to EESZT.
• The event is reported at or near the time of care; documents (zárójelentés, lelet) are uploaded and linked to the event.
• Covers creation, correction, and revocation of an event, and document upload/replacement.

Structure (medical event → record)

header        event type (vizsgálat / ellátás / felvétel / elbocsátás / dokumentum),
              event timestamp, institution/service-point id, software & interface version
patient       TAJ (9-digit) or substitute id, name, birth data
clinical      diagnosis code(s) (BNO / ICD), procedure/intervention codes,
              department, attending physician (pecsétszám)
document      attached health document(s) (type, identifier, content reference)
result        EESZT event identifier

Data rules

• Patient identified by TAJ (or substitute); provider/department and attending physician (pecsétszám) identified per the institution register.
• Diagnosis coded with BNO (the Hungarian ICD coding) and procedures with the relevant intervention codes; the timestamp records when care occurred.
• Event type governs the record; corrections/revocations reference the original EESZT event identifier.
• Documents (e.g. discharge summary) are linked to the event; consent and access-control (self-rendelkezés) rules apply to who may read the record.
• This is a clinical record with sensitive health data — handle strictly per EESZT data-protection and access rules; no monetary settlement is computed here.

Worked example (outline)

header:   type=ambuláns ellátás, time=2026-06-04T10:30, institution=<ID>, version=<current>
patient:  TAJ=123456789, Kiss Anna
clinical: BNO=<kód>, procedure=<kód>, attending pecsétszám=12345
document: zárójelentés/ambuláns lap linked
result:   EESZT event id=<assigned>

The event and its document are recorded in EESZT and become part of the patient's central EHR, readable subject to consent rules.

Validation checklist

• Current EESZT medical-event interface version used; event type and timestamp correct
• Patient identified by TAJ (or valid substitute); birth data consistent
• Institution/service-point and attending physician (pecsétszám) identified
• Diagnosis coded with BNO; procedure/intervention codes present
• Documents linked to the event with correct type/identifier
• Corrections/revocations reference the original EESZT event id
• Consent / access-control (self-rendelkezés) and sensitive-data handling respected

Last updated: 2026-06-04 — confirm the current schema/version, identifiers, rounding, and deadline against current authority (eeszt / e-egeszsegugy.gov.hu) guidance before use.