Medication Prescription and Delivery (MPD)
0.1.0 - ci-build
Medication Prescription and Delivery (MPD)
0.1.0 - ci-build
Medication Prescription and Delivery (MPD), published by Integrating the Healthcare Enterprise (IHE). This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/pharm-mpd and changes regularly. See the Directory of published versions
| Active as of 2024-04-15 |
Definitions for the PatientBasic logical model.
Guidance on how to interpret the contents of this table can be found here
| 0. PatientBasic | |
| Definition | Basic patient data relevant for this use case |
| Short | Patient - Data Model |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. PatientBasic.identifier | |
| Definition | Patient identifier |
| Short | Patient identifier |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..* |
| Type | Element(II) |
| 4. PatientBasic.name | |
| Definition | Patient's name, incl first name, last name, or any other relevant name parts |
| Short | Patient's name, incl first name, last name, or any other relevant name parts |
| Control | 1..* |
| Type | Element(EN) |
| 6. PatientBasic.gender | |
| Definition | Question: eHDSI prescription emphasisis the biological gender, but I think the reality is that most systems would have administrative gender or somekindof gender |
| Short | Gender |
| Control | 0..1 |
| Type | Element(CD) |
| 8. PatientBasic.dateOfBirth | |
| Definition | eHDSI |
| Short | Date of birth |
| Control | 0..1 |
| Type | Element(DT) |
| 10. PatientBasic.insuranceInformation | |
| Definition | Question: shall we go here and how deep? |
| Short | Insurance information |
| Control | 0..1 |
| Type | BackboneElement(Class) |
| 12. PatientBasic.relatedHealthInformation | |
| Definition | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Short | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Control | 0..* |
| Type | Element(ANY) |
Guidance on how to interpret the contents of this table can be found here
| 0. PatientBasic | |
| Definition | Basic patient data relevant for this use case Base definition for all types defined in FHIR type system. |
| Short | Patient - Data ModelBase for all types and resources |
| Control | 0..* |
| Is Modifier | false |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. PatientBasic.identifier | |
| Definition | Patient identifier |
| Short | Patient identifier |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..* |
| Type | Element(II) |
| 4. PatientBasic.name | |
| Definition | Patient's name, incl first name, last name, or any other relevant name parts |
| Short | Patient's name, incl first name, last name, or any other relevant name parts |
| Control | 1..* |
| Type | Element(EN) |
| 6. PatientBasic.gender | |
| Definition | Question: eHDSI prescription emphasisis the biological gender, but I think the reality is that most systems would have administrative gender or somekindof gender |
| Short | Gender |
| Control | 0..1 |
| Type | Element(CD) |
| 8. PatientBasic.dateOfBirth | |
| Definition | eHDSI |
| Short | Date of birth |
| Control | 0..1 |
| Type | Element(DT) |
| 10. PatientBasic.insuranceInformation | |
| Definition | Question: shall we go here and how deep? |
| Short | Insurance information |
| Control | 0..1 |
| Type | BackboneElement(Class) |
| 12. PatientBasic.relatedHealthInformation | |
| Definition | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Short | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Control | 0..* |
| Type | Element(ANY) |
Guidance on how to interpret the contents of this table can be found here
| 0. PatientBasic | |
| Definition | Basic patient data relevant for this use case |
| Short | Patient - Data Model |
| Control | 0..* |
| Is Modifier | false |
| Logical Model | Instances of this logical model are not marked to be the target of a Reference |
| 2. PatientBasic.identifier | |
| Definition | Patient identifier |
| Short | Patient identifier |
| Note | This is a business identifier, not a resource identifier (see discussion) |
| Control | 1..* |
| Type | Element(II) |
| 4. PatientBasic.name | |
| Definition | Patient's name, incl first name, last name, or any other relevant name parts |
| Short | Patient's name, incl first name, last name, or any other relevant name parts |
| Control | 1..* |
| Type | Element(EN) |
| 6. PatientBasic.gender | |
| Definition | Question: eHDSI prescription emphasisis the biological gender, but I think the reality is that most systems would have administrative gender or somekindof gender |
| Short | Gender |
| Control | 0..1 |
| Type | Element(CD) |
| 8. PatientBasic.dateOfBirth | |
| Definition | eHDSI |
| Short | Date of birth |
| Control | 0..1 |
| Type | Element(DT) |
| 10. PatientBasic.insuranceInformation | |
| Definition | Question: shall we go here and how deep? |
| Short | Insurance information |
| Control | 0..1 |
| Type | BackboneElement(Class) |
| 12. PatientBasic.relatedHealthInformation | |
| Definition | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Short | Related health information, such as allergies, conditions, recent procedures, or certain lab results are not part of patient or prescription core data. IPS specification can be used for use-case-specific patient summary. |
| Control | 0..* |
| Type | Element(ANY) |
IG © 2021+ Integrating the Healthcare Enterprise (IHE). Package ihe.pharm.mpd#0.1.0 based on FHIR 5.0.0. Generated 2024-04-15
Links: Table of Contents |
QA Report
Version History |
|
Propose a change