CH EMED (R4)
3.0.0 - STU3
This page is part of the CH EMED (R4) (v3.0.0: STU 3) based on FHIR R4. . For a full list of available versions, see the Directory of published versions
When creating/publishing an eMedication document, there may be one or more authors. A differentiation is made between the author of the document and the author of the medical decision. Use cases are described below to illustrate these different cases for the various document types and to show where the corresponding information is mapped.
The general practitioner Dr. med. Familien Hausarzt recommends medication treatment with Triatec to Monika Wegmüller. He documents his therapy decision using the Medication Treatment Plan document.
In this case, the author of the document and the medical decision is the same. In the eMedication document Dr. med. Familien Hausarzt is mapped once.
The specialist Dr. med. Sandra Meier orders Monika Wegmüller to be treated with Aspirin and also issues a prescription. The medical practice assistant Andrew Stabilo creates the corresponding eMedication documents (MTP, PRE).
In this case, the author of the document and the author of the medical decision are different. In the eMedication documents, these two authors are mapped differently.
Document level | One author/person | Different authors/persons |
---|---|---|
Document (Composition.author) | Author document & author medical decision (person) | Author document (person) |
Section (Composition.section.author) | x | Author medical decision (person) |
Entries (MedicationStatement, MedicationRequest, MedicationDispense, Observation) | x | x |
The pharmacist Peter Pharma creates a Medication Plan document for Mona Muster, which provides the patient with an overview of her current medication. Mona Muster is currently taking Aspirin cardio. This medication was initiated and authored by the general practitioner Dr. med. Familien Hausarzt (MTP). The specialist Dr. med. Sandra Meier later adjusted the dosage and the medical practice assistant Andrew Stabilo documented this accordingly (PADV).
The pharmacist wants to get an overview of Mona Muster’s current medication and therefore requests his Medication List document. (Same use case as described above for CARD.)
Document level | Medication Card document | Medication List document |
---|---|---|
Document (Composition.author) | Author document (person or device) | Author document (device, which dynamically generates the document) |
Section (Composition.section.author) | x | x |
Entries: Author medical decision | MedicationStatement.informationSource* (person) | MedicationStatement.informationSource (person), MedicationRequest.performer (person), MedicationDispense.performer.actor (person), Observation.performer (person) |
Entries: Author original document (if different from the author of the medical decision) | MedicationStatement.extension:authorDocument* (person) | MedicationStatement.extension:authorDocument (person), MedicationRequest.extension:authorDocument (person), MedicationDispense.extension:authorDocument (person), Observation.extension:authorDocument (person) |
*: The CARD is an aggregation of all medications, respectively all documents, which may have had different authors. The “last author” (author of the last input for this treatment) is indicated in each case.