IHE Pharmacy Medication Overview
1.0.0-preview - Preview
This page is part of the IHE Pharmacy Medication Overview (v1.0.0-preview: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Medication Overview Consumer |
CapabilityStatement for the Medication Overview Consumer actor in the IHE PHARM MEOW profile. The Consumer is a client that queries a Medication Overview Repository or Creator to retrieve a patient's medication overview. It supports PHARM-11 (Query Medication Resources) as a required capability, and optionally PHARM-12 (Retrieve Medication Document) when the Document Option is declared. |
| Medication Overview Responder |
CapabilityStatement for the Medication Overview Responder actor in the IHE PHARM MEOW profile. The Responder is a server that stores and/or assembles medication overview data for patients and serves it in response to Consumer requests. It supports PHARM-11 (Query Medication Resources) as a required capability, and optionally PHARM-12 (Retrieve Medication Document) when the Document Option is declared. How the Responder obtains its data (continuous store, on-demand aggregation, document assembly) is an implementation concern outside the scope of this profile. |
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| Dosaging (model) |
Logical model for usage instructions for administring the requested product. Based on FHIR Dosage complex data type. |
| Medication Overview (model) |
Logical model for the whole medication overview (medication schema) |
| Medication Treatment (model) |
Logical model for subgroups of treatment lines that are somehow related to eachother (the same purpose, other) |
| Medication Treatment Line (model) |
Logical model for representing one line/medication in medication overview. |
| Medicinal product (model) |
Logical model for prescribed/dispensed medication. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile. |
| Patient (model) |
Logical model for patient (basic data relevant for this use case) |
| Practitioner (model) |
Logical model for practitioner (basic data relevant for this use case) |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Medication Overview Bundle |
The profile for the full Medication overview as a Bundle type Document |
| Medication Overview Composition |
The profile for how to organize the information in a medication overview |
| Medication Treatment |
The profile for Medication Treatment in a Medication Record - a set of treatment lines/items |
| Medication Treatment Line |
The profile for Medication Treatment Line - a single recorded item/line of a medication treatment |
| Medicinal product |
Medication for clinical use cases. This could be a branded product or a generic concept, also allowing describing pack size and components of complex products. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Medication - Classification |
Medication classification/category. Allows the product to be classified by various systems, e.g ATC, narcotic class, legal status of supply, etc.. |
| Medication - Device |
Device, typically an administration device, included in the medicinal product. |
| Medication - Product Name |
Name of the medicinal product. Optionally the type of name (Full official name, prescribing name, invented name) and language of the name can be specified. The extension is a simplified approach of what is used in MedicinalProductDefinition resource. |
| Medication - Size of Item |
Size of a manufactured item or unit of presentation. For example, size of one vial in a package that may contain several vials. |
| MedicationStatement - Substitution |
Whether and which type of substitution is allowed for this medication treatment line |
| MedicationStatement - Verification Information |
Verification of medication line. The overview is verified as a whole, but each line is equipped with the information. The actual functional meaning and impact of this validation depends on the implementation. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| 01A-Cefuroxime1500GenericExplicit |
1A. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Generic product, defined by attributes. |
| 01B-Cefuroxime1500GenericConcept |
1B. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Generic product, defined by a code system (receiving system is expected to have access to the code system for additional attributes or display names). |
| 01C-Cefuroxime1500Branded |
1C. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Branded packaged product, defined by attributes. |
| 02A-ClotrimazoleCanifugCremolum |
2A. Clotrimazole cream 10mg/g and 6 pessaries 100g. Branded packaged product, consisting of different medication items. Defined by attributes. |
| 02A1-CanifugCremolumCreamItem |
2A2. Clotrimazole cream (10mg/g, 1 tube of 20g) as part of Canifug Cremolum product (ISO IDMP manufactured item) |
| 02A2-CanifugCremolumPessaryItem |
2A1. Clotrimazole pessary (6 pessaries of 100mg) as part of Canifug Cremolum product (ISO IDMP manufactured item) |
| 03B-VitaminBComplexBranded |
3B. Milgamma N, B-vitamin complex. Branded packaged product, defined by attributes. |