Recepta elektroniczna w FHIR

Recepta elektroniczna to priorytetowa kategoria Europejskiej Przestrzeni Danych dotyczących Zdrowia (art. 14 ust. 1 lit. (b) rozporządzenia (UE) 2025/327). Stosuje się ją od 26 marca 2029. HL7 Europe obejmuje ją przewodnikami: mpd 1.0.0.

Rozporządzenie
Regulation (EU) 2025/327, Article 14(1)(b), Annex I
Stosuje się od
26 marca 2029
Przewodniki HL7 Europe
hl7.fhir.eu.mpd 1.0.0, opublikowany
Modele logiczne Xt-EHR
EHDSMedicationPrescription
Walidator
Otwórz walidator profili EHDS

Co mówi rozporządzenie

Załącznik I do rozporządzenia opisuje główne cechy tej kategorii. Tekst jest angielskim oryginałem.

Electronic prescriptions

Electronic health data constituting a prescription for a medicinal product as defined in Article 3, point (k), of Directive 2011/24/EU.

Profile FHIR 3

Profile zdefiniowane przez powyższe przewodniki. Kolumna reguł liczy elementy, w których profil wykracza poza bazowy FHIR (wymagane, zakazane lub ograniczone) i które sprawdza walidator; spośród slice’ów sprawdzane są tylko wymagane, które odróżnia stała wartość lub typ zasobu.

ProfilZasóbPrzewodnik HL7 EuropeSprawdzane regułySlice’y sprawdzane / zdefiniowane
Medication: MPDhttp://hl7.eu/fhir/mpd/StructureDefinition/Medication-eu-mpd
Medicationmpd00 / 12
MedicationDispense: MPDhttp://hl7.eu/fhir/mpd/StructureDefinition/MedicationDispense-eu-mpd
MedicationDispensempd20 / 3
MedicationRequest: MPDhttp://hl7.eu/fhir/mpd/StructureDefinition/MedicationRequest-eu-mpd
MedicationRequestmpd20 / 7

Powiązania terminologiczne 0

Value sets, z którymi profile tej kategorii wiążą elementy powiązaniem required lub extensible. Powiązanie required dopuszcza tylko kody z value set; extensible oczekuje ich, chyba że żaden nie pasuje. Value sets definiowane w pakietach HL7 Europe są wypisane z kodami w wykazie value sets.

Profile tej kategorii nie określają własnych powiązań required ani extensible. Profile określają też powiązania: preferred – 0, example – 4.

Rozszerzenia 1

Rozszerzenia HL7 Europe, które zawierają profile tej kategorii, z elementem, który je przechowuje.

RozszerzenieKontekstWartośćUżyte w
Medication: Package typehttp://hl7.eu/fhir/StructureDefinition/medication-package-type
Medication
CodeableConcept
MedicationEuMpd extension:packageType 0..1

Model logiczny EHDSMedicationPrescription 30

Elementy modelu logicznego Xt-EHR z licznością i obowiązkami. Obowiązki mówią producentom i odbiorcom danych, co system MUSI lub POWINIEN robić z każdym elementem.

Obowiązki według uczestnika

Ile elementów EHDSMedicationPrescription niesie dany obowiązek dla danego uczestnika.

ObowiązekUczestnikElementy
SHALL:able-to-populateproducent11
SHALL:processodbiorca11
SHOULD:able-to-populateproducent5
SHOULD:displayodbiorca2
SHOULD:processodbiorca3

Elementy 30

ElementLicz.ObowiązkiOpis
header1..1
Prescription header
subject1..1
SHALL:able-to-populate producentSHALL:process odbiorca
System SHALL process the patient information for identification purposes.
The person for whom the medication is prescribed/ordered. [Used for searching]
identifier1..*
SHALL:able-to-populate producent
For a single-item prescription these identifiers SHALL match prescriptionItem.identifier.
SHALL:process odbiorca
System SHALL use this prescription identifier for reference in the dispense record.
Business identifier(s) for the prescription. [Used for searching]
author[x]1..*
SHALL:able-to-populate producent
System SHALL support at least EHDSHealthProfessional data type for the element.
SHALL:process odbiorca
The prescriber, the person who made the prescription, and who takes the responsibility for the treatment. [Used for searching]
date1..1
SHALL:able-to-populate producentSHALL:process odbiorca
Time of issuing (signing) the prescription by health care professional. [Used for searching]
status1..1
SHALL:able-to-populate producentSHALL:process odbiorca
System SHALL process the prescription status together with other information to determine dispensability.
Status of authorisation for dispensing the prescription items. This should not be the status of treatment. For a multiple-item prescription, this conveys the aggregate status of the entire prescription. In case of a single-item prescription, prescriptionItem.status shall be the same as EHDSMedicationPrescription.header.status. [Used for searching]
source0..0
Source of information (e.g. patient, patient's proxy). Used in case the patient has authored the information or the author has submitted patient-stated information.
language0..1
Language in which the resource is written. Language is expressed by the IETF language tag.
statusReason[x]0..1
Reason for the current status of prescription, for example the reason why the prescription was made invalid or changed from a previous state.
presentedForm0..*
SHOULD:able-to-populate producent
System SHOULD be able to provide a rendered, human-readable version of the prescription.
SHOULD:display odbiorca
Entire prescription as issued. Various formats could be provided, PDF format is recommended.
prescriptionItem1..*
SHALL:able-to-populate producentSHALL:process odbiorca
Prescription line for one medication. In many countries, only one item is allowed and there shall be no expectation to be able to manage multiple items. In case multiple medications are allowed, all items need to be authored together.
identifier1..*
SHALL:able-to-populate producent
For a single-item prescription these identifiers SHALL match .identifier.
SHALL:process odbiorca
System SHALL use this prescription identifier for reference in the dispense record.
Identifier for a single item on prescription, if exists. In case of single-item prescription, this identifier is typically the same as prescription identifier. [Used for searching]
status1..1
SHALL:able-to-populate producentSHALL:process odbiorca
System SHALL process the prescription status together with other information to determine dispensability.
Status of a single item of a multi-item prescription. In case of single-item prescriptions, the status of prescription has the same meaning as the status of the item. [Used for searching]
statusReason[x]0..1
Reason for the current status of prescription, for example the reason why the prescription was made invalid or why the prescription was changed from previous
medication1..1
SHALL:able-to-populate producentSHALL:process odbiorca
Prescribed product, branded, generic, virtual, extemporal, etc
indication[x]0..*
Reason for the prescription (typically diagnosis, or a procedure)
intendedUseType0..1
Intent of the prescription - prophylaxis, treatment, anesthesia, etc
periodOfUse0..1
Period over which the medication is to be taken (in case of multiple dosage schemes, this would be the overall period of all dosages.)
quantityPrescribed0..1
SHOULD:able-to-populate producentSHOULD:process odbiorca
Overall quantity of prescribed product (e.g number of packages or number of tablets).
dosageInstructions1..1
SHALL:able-to-populate producentSHALL:process odbiorca
Dosage and administration instructions
validityPeriod0..1
SHOULD:able-to-populate producentSHOULD:process odbiorca
The period over which the prescription is considered valid and dispensable. validityPeriod.start is, if missing, is assumed to be the date of issuing the prescription.
substitution0..1
SHOULD:able-to-populate producentSHOULD:process odbiorca
Whether and which type of substitution is allowed for this prescription. The legislation in the country of dispense applies, e.g. if this information is missing.
allowed[x]0..1
SHALL:able-to-populate producent
System SHALL support at least the boolean data type.
SHALL:process odbiorca
System SHALL support at least the boolean data type.
Whether and to what extent substitution is allowed.
reason[x]0..1
Reason for the substitution requirement (e.g. Biological product, Patient allergic to an excipient in alternative products, etc)
numberOfRepeats0..1
Number of refills authorised - how many times the prescription item can be dispensed in addition to the original dispense. The default value is 0 (no repeats).
minimumDispenseInterval0..1
Minimum dispense interval. If a prescription allows for repeated dispensations, the interval between dispensations shall be stated here.
offLabel0..1
Indicates that the prescriber has knowingly prescribed the medication for an indication, age group, dosage, or route of administration that is not approved by the regulatory agencies and is not mentioned in the prescribing information for the drug
isOffLabelUse1..1
Indicates off-label use. Must be 'true' when .reason is provided.
reason[x]0..*
Reason or related clarification for off-label use
note0..1
SHOULD:able-to-populate producentSHOULD:display odbiorca
Additional information or comments, e.g. message to the dispenser

Odwzorowanie EHDSMedicationPrescription na FHIR 29

Jak każdy element logiczny trafia do FHIR, według przewodnika HL7 Europe. Odwzorowane na: MedicationRequestEuMpd.

ElementRelacjaZasób FHIRElement FHIRUwagi
headerpowiązany zMedicationRequest.Backbone element
subjectrównoważnyMedicationRequestsubjectReference to Patient.
identifierwęższy niż celMedicationRequestidentifierPrescription identifier and prescription item identifier are usually the same in environments using single-item prescriptions.
identifierwęższy niż celMedicationRequestgroupIdentifierUse as the shared prescription identifier for MedicationRequest instances that belong to the same multi-item prescription.
author[x]równoważnyMedicationRequestrequester
daterównoważnyMedicationRequestauthoredOn
statusrównoważnyMedicationRequeststatus
statusReason[x]równoważnyMedicationRequeststatusReasonThe model also allows string data type which maps to CodeableConcept.text , but note element may also be used for additional clarifications.
presentedFormbrak odwzorowaniaMedicationRequestReference a DocumentReference containing the rendered prescription.
prescriptionItemrównoważnyMedicationRequest.Create one MedicationRequest per prescription item.
identifierrównoważnyMedicationRequestidentifier
statusrównoważnyMedicationRequeststatusFor single-item prescriptions, same meaning as header.status.
statusReason[x]równoważnyMedicationRequeststatusReasonThe model also allows string data type which maps to CodeableConcept.text , but note element may also be used for additional clarifications.
medicationrównoważnyMedicationRequestmedication[x] 〔R4〕 medication 〔R5〕
indication[x]równoważnyMedicationRequestreasonCode 〔R4〕 reason 〔R5〕The model also allows string data type which maps to CodeableConcept.text , but note element may also be used for additional clarifications.
intendedUseTypewęższy niż celMedicationRequestcategoryUse dedicated category code or custom extension if additional granularity is required.
periodOfUsepowiązany zMedicationRequestextension:effectiveDosePeriod 〔R4〕 effectiveDosePeriod 〔R5〕
quantityPrescribedrównoważnyMedicationRequestdispenseRequest.extension:prescribedQuantity
dosageInstructionsrównoważnyMedicationRequestdosageInstructionMap each EHDSDosage entry to dosageInstruction .
validityPeriodrównoważnyMedicationRequestdispenseRequest.validityPeriod
substitutionrównoważnyMedicationRequestsubstitution
allowed[x]równoważnyMedicationRequestsubstitution.allowed[x]The guide requires support for at least Boolean data type.
reason[x]równoważnyMedicationRequestsubstitution.reasonThe model also allows string data type which maps to CodeableConcept.text , but note element may also be used for additional clarifications.
numberOfRepeatsrównoważnyMedicationRequestdispenseRequest.numberOfRepeatsAllowed
minimumDispenseIntervalrównoważnyMedicationRequestdispenseRequest.dispenseInterval
offLabelpowiązany zMedicationRequestextension:offLabelUse
isOffLabelUsepowiązany zMedicationRequestextension:offLabelUse
reason[x]powiązany zMedicationRequestextension:offLabelUse.reasonThe model also allows string data type which maps to CodeableConcept.text , but note element may also be used for additional clarifications.
noterównoważnyMedicationRequestnote.textUse note.author / note.time if available.

Dokumenty CDA (eHDSI)

Tę samą kategorię niosą w CDA te szablony dokumentów eHDSI. Ich struktura, zbiory wartości i walidator dokumentów CDA są w przewodniku CDA.

Źródła

Rozporządzenie (UE) 2025/327, Dziennik Urzędowy Unii Europejskiej; przewodniki wdrożeniowe FHIR HL7 Europe; modele logiczne Xt-EHR (xtehr.eu.ehds.models). Przewodniki w ballocie mogą się jeszcze zmienić. Ten przewodnik ma charakter informacyjny: nie jest poradą prawną ani certyfikacją zgodności.