| Name | Source | Ver | Description |
| [HMW] Logical Model for administration | ihe.pharm.mpd#current | R5 | [HMW] Logical Model for administration |
| [HMW] Logical Model for dispense | ihe.pharm.mpd#current | R5 | [HMW] Logical Model for dispense |
| [HMW] Logical Model for medication order | ihe.pharm.mpd#current | R5 | [HMW] Logical Model for medication order |
| [HMW] Logical Model for Pharmaceutical Advice | ihe.pharm.mpd#current | R5 | [HMW] Logical Model for Pharmaceutical Advice |
| [IHE MM] Logical Model for administration | ihe.pharm.mpd#current | R5 | Logical Model for administration |
| [IHE MM] Logical Model for medication dispense | ihe.pharm.mpd#current | R5 | A medication dispense relates to zero or one prescription item of one prescription. There are cases when a medication is dispensed before the prescription is created. Medications dispensed outside the context of any prescription are considered as self-prescribed by the professional who dispenses. Thus they are still attached to a pseudo-prescription. A medication dispense is issued by one pharmacy staff. It is related to zero (community use case) or one (hospital use case) encounter of care. |
| [IHE MM] Logical Model for order | ihe.pharm.mpd#current | R5 | A prescription is issued by one ordering healthcare professional for one patient, in the context of zero or one encounter (between the patient and the ordering physician and/or the healthcare institution). |
| [IHE MM] Logical Model for pharmaceutical advice | ihe.pharm.mpd#current | R5 | Pharmaceutical advice relates to one or more prescription items of one prescription. It is issued by one pharmacist. It may be associated with one or more observations. |
| [IHE PHARM White Paper] Logical Model for medication dispense | ihe.pharm.mpd#current | R5 | A medication dispense relates to zero or one prescription item of one prescription. There are cases when a medication is dispensed before the prescription is created. Medications dispensed outside the context of any prescription are considered as self-prescribed by the professional who dispenses. Thus they are still attached to a pseudo-prescription. A medication dispense is issued by one pharmacy staff. It is related to zero (community use case) or one (hospital use case) encounter of care. |
| [IHE PHARM White Paper] Logical Model for order | ihe.pharm.mpd#current | R5 | A prescription is issued by one ordering healthcare professional for one patient, in the context of zero or one encounter (between the patient and the ordering physician and/or the healthcare institution). |
| [IHE PHARM White Paper] Logical Model for pharmaceutical advice | ihe.pharm.mpd#current | R5 | Pharmaceutical advice relates to one or more prescription items of one prescription. It is issued by one pharmacist. It may be associated with one or more observations. |
| [Logical Model] - Administration | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing and reporting an administration of a product. |
| [Logical Model] - Dispense | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing a product dispense. |
| [Logical Model] - Prescription | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing a product order. |
| [Logical Model] - Scheduled Administration | ihe-fhir-pharm-medicationrecord#current | R5 | A model for a record of a single planned administration event. |
| [Logical Model] - Summary View | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing a summary view of a patient's medication. |
| [Logical Model] - Usage | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing medication usage. |
| CDS Hook Extension Definition for DaVinci Configuration (Test) | hl7.fhir.uv.tools#current | R5 | This structure is defines the CRD Configuration (Test only). TODO: This content will be moved to the CDS Hooks specification in the future |
| CDS Hook Extension Definition for DaVinci Configuration Options (Test) | hl7.fhir.uv.tools#current | R5 | This structure is defines the CRD Configuration Options (Test only). TODO: This content will be moved to the CDS Hooks specification in the future |
| CDS Hook Specific Context (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Request Context. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDS Hook Specific Context for order-select (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks order-select context. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDS Hook Specific Context for order-sign (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Order-Sign context. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDS Hook Specific Context for patient-view (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Patient-View context. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDSHooks Request (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Request Body. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDSHooks Response (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Response body. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDSHooks Services Base Extensible Element | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Services Element with Extensions. TODO: This content will be moved to the CDS Hooks specification in the future |
| CDSHooks Services Request (Logical Definition) | hl7.fhir.uv.tools#current | R5 | This structure is defined to allow the FHIR Validator to validate a CDSHooks Services response body. TODO: This content will be moved to the CDS Hooks specification in the future |
| Dosaging | ihe.pharm.meow#current | R5 | Usage instructions. Instructions about requested administration of the product. Based on FHIR Dosage complex data type. |
| Dosaging | ihe.pharm.mpd#current | R5 | Usage instructions. Instructions about requested administration of the product. Based on FHIR Dosage complex data type. |
| ePrescription | ihe.pharm.mpd#current | R5 | |
| Food Allergy Logical Model | hl7.eetest.fhir.foodallergy#current | R4 | Food Allergy information model |
| Food Allergy Logical Model | mycompany.fhir.foodallergyExample#current | R4 | Food Allergy information model |
| InventoryStatusModel | ihe.pharm.supply#current | R5 | This is the logical model for the Inventory Status report - an information about the current status of a given inventory position. This is to be typically used in inventory counts - physical counts or estimates. It supports a report per status, per location, or a combination of both (which is how typically items are counted and reported). |
| InventoryUpdateModel | ihe.pharm.supply#current | R5 | This is the logical model for the Inventory Change notification - an information about a change of items being added or removed from a given inventory position. This is to be typically used in differential inventory updates (e.g. "Since last time, the following items have been consumed") or to register items added or subtracted (e.g. "The following 2 items were just discarded and should be deducted from inventory ") |
| ItemModel | ihe.pharm.supply#current | R5 | This is the logical model for the Inventory Change notification - an information about a change of items being added or removed from a given inventory position. This is to be typically used in differential inventory updates (e.g. "Since last time, the following items have been consumed") or to register items added or subtracted (e.g. "The following 2 items were just discarded and should be deducted from inventory ") |
| Medication | ihe.pharm.mpd#current | R5 | Medication information. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile. |
| Medication dispensation | ihe.pharm.mpd#current | R5 | Logical model for medication dispensation (based on request or independently) |
| Medication for clinical workflows | ihe.pharm.meow#current | R5 | Medication information. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile. |
| Medication Overview - logical model | ihe.pharm.meow#current | R5 | A model for the whole medication overview (medication schema) |
| Medication prescription/request/order | ihe.pharm.mpd#current | R5 | Logical model for medication request (incl prescription, or some other form of order) |
| Medication Record - Medication Treatment | ihe-fhir-pharm-medicationrecord#current | R5 | A model for the Medication Treatment. |
| Medication Record logical model | ihe-fhir-pharm-medicationrecord#current | R5 | A model for a structure collection of a patient's medication history. |
| Medication Record Treatment Line - logical model | ihe-fhir-pharm-medicationrecord#current | R5 | A model for representing a Treatment Line. |
| Medication Treatment - logical model | ihe.pharm.meow#current | R5 | Grouping of treatment lines that are somehow related to eachother (the same purpose, other) |
| Medication Treatment Line - logical model | ihe.pharm.meow#current | R5 | A model for representing a Treatment Line. |
| Medicinal Product Logical Model | idmp-datafeed#current | R5 | Logical model for a pilot product list's medicinal product |
| My Logical Model | example.fhir.uv.myig#current | R4 | A profile showing the use of Logical Models to author profiles |
| MyLogicalModel | my-ig#current | R4 | MyLogicalModel |
| OAuth Authentication Request | mitre.fast.access-control#current | R4 | This structure defines an OAuth authentication response body |
| OAuth Authentication Response | mitre.fast.access-control#current | R4 | This structure defines an OAuth authentication response body |
| OAuth Registration Request | mitre.fast.access-control#current | R4 | This structure defines an OAuth registration request body |
| OAuth Registration Response | mitre.fast.access-control#current | R4 | This structure defines an OAuth registration response body |
| OAuth Token Response | mitre.fast.access-control#current | R4 | This structure defines an OAuth token response body |
| Patient | ihe.pharm.meow#current | R5 | Basic patient data relevant for this use case |
| Patient | ihe.pharm.mpd#current | R5 | Basic patient data relevant for this use case |
| Patient Gender | hl7.fhir.uv.sdc.r4#3.0.0 | R4 | Data element SDC Profile Example |
| Practitioner | ihe.pharm.mpd#current | R5 | Basic prescribing/dispensing practitioner's data relevant for this use case |
| Practitioner | ihe.pharm.meow#current | R5 | Basic prescribing/dispensing/caretaking practitioner's data relevant for this use case |
| ProductModel | ihe.pharm.supply#current | R5 | This is the logical model for a Product |
| ReceiptNoticeModel | ihe.pharm.supply#current | R5 | This is the logical model for the ReceiptNotice |
| SDC Question Library | hl7.fhir.uv.sdc.r4#3.0.0 | R4 | An example library of questions showing how questions can be compiled into a library for use by modular questionnaires |
| ShipmentNoticeModel | ihe.pharm.supply#current | R5 | This is the logical model for the ShipmentNotice |
| SupplyRequestModel | ihe.pharm.supply#current | R5 | This is the logical model for the SupplyRequest |
| SupplyRequestStatusModel | ihe.pharm.supply#current | R5 | This is the logical model for the Supply Request Status |
| View Definition | hl7.fhir.uv.sql-on-fhir#current | R5 | View definitions are a tabular projection of a FHIR resource, where the columns and inclusion criteria are defined by FHIRPath expressions. |
Produced 08 Sep 2023