Build Hungarian e-Prescription Event (EESZT eRecept record)

Skill: Convert a prescription into an eRecept event recorded in EESZT

Region: Hungary (Magyarország) Category: Health care Does: Takes a prescriber's medication order and assembles the eRecept / eVény prescription-event record for electronic submission to the EESZT (Elektronikus Egészségügyi Szolgáltatási Tér) — declaring the prescriber, the patient, the prescribed product (with subsidy basis), dosage, and the resulting prescription identifier used at dispensing. Spec: EESZT — eRecept / eVény event interface (current EESZT version)

EESZT is Hungary's central e-health space; prescriptions are written as electronic prescription events (eRecept / eVény) recorded centrally rather than only on paper. The pharmacy later retrieves and dispenses against the EESZT record, and a dispensing event (kiadás) is recorded back. Records are created per prescription at the point of care. Element names below follow the eRecept event structure, not a verbatim XSD; the EESZT interface is versioned, so confirm the current release.

When this applies

• A licensed prescriber (orvos) issues a medication or medical-aid prescription that is registered as an EESZT event.
• The patient is identified for the central record; dispensing at the pharmacy reads the EESZT prescription and writes back a dispensing event.
• Covers reimbursed (támogatott) and full-price prescriptions, including renewals and cancellations of an existing prescription event.

Structure (eRecept event → record)

header        event type (felírás / módosítás / visszavonás), EESZT identifiers,
              software / institution identification, interface version
prescriber    physician seal/identifier (pecsétszám), institution, service point
patient       TAJ (9-digit) or other identification, name, birth data
product       medicinal product code (e.g. TTT / brand), quantity/package,
              dosage instructions, subsidy/reimbursement basis (jogcím)
result        EESZT prescription identifier (event id) for later dispensing

Data rules

• Patient identified by TAJ (or substitute id where TAJ absent); prescriber identified by physician seal number (pecsétszám) and institution.
• Product coded to the central catalogue (e.g. TTT code) with the subsidy basis (jogcím) where reimbursed; this links to the NEAK reimbursement record at dispensing.
• Event type (felírás / módosítás / visszavonás) governs the lifecycle; a cancellation references the original event id.
• The created EESZT event identifier is what the pharmacy uses to dispense; no monetary settlement is computed here (that follows at dispensing/NEAK).
• This is a clinical/event record — contains sensitive health data; handle per EESZT access-control and data-protection rules.

Worked example (outline)

header:    type=felírás, version=<current>
prescriber: pecsétszám=12345, institution=<ID>
patient:   TAJ=123456789, Kiss Anna
product:   TTT=<kód>, 1 package, dosage 1×1 daily, jogcím=<támogatási kód>
result:    EESZT event id=<assigned>

The event is recorded in EESZT; the pharmacy retrieves it by the event id, dispenses, and writes back a dispensing (kiadás) event.

Validation checklist

• Current EESZT eRecept interface version used; event type correct
• Prescriber identified by pecsétszám + institution/service point
• Patient identified by TAJ (or valid substitute); birth data consistent
• Product coded to central catalogue (TTT/brand) with quantity and dosage
• Subsidy basis (jogcím) set where reimbursed; links to NEAK at dispensing
• Cancellations/modifications reference the original EESZT event id
• Sensitive-data handling per EESZT access-control rules

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.