FHIR IG analytics| Package | hl7.ehrs.us.medlistfp |
| Resource Type | Requirements |
| Id | Requirements-MEDLISTFP-PH.2.5.2.json |
| FHIR Version | R5 |
| Source | https://build.fhir.org/ig/HL7/medlistfp-ig/Requirements-MEDLISTFP-PH.2.5.2.html |
| URL | http://hl7.org/ehrs/us/medlistfp/Requirements/MEDLISTFP-PH.2.5.2 |
| Version | 1.0.0 |
| Status | active |
| Date | 2026-07-24T07:22:03+00:00 |
| Name | PH_2_5_2 |
| Title | PH.2.5.2 (Function) |
| Realm | us |
| Authority | hl7 |
| Description | Manage the PHR Account Holder’s medication list. |
| Purpose | Medication lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. All pertinent dates, including medication start, modification, and end dates can be stored. Medication histories, (for example, alternative supplements, over-the-counter medications, and herbal medications) may be relevant for review. Medication lists are not limited to medication orders recorded by providers, but may include, for example, pharmacy dispense/supply records, patient-reported medications, and additional information such as age-specific dosage. Example(s): The system maintains a medication list that may be followed by the PHR Account Holder and referenced by his or her providers and pharmacists. Copies of the PHR medication list may be kept by their providers in their EHRs. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
| PH.2.5.2#01 | SHOULD profiled | The system SHOULD provide the ability to capture PHR Account Holder -specific medication data from a provider's EHR system, a pharmacy system, or from other sources. |
| PH.2.5.2#02 | SHOULD | The system SHOULD provide the ability to capture and update a fill status for each prescription. |
| PH.2.5.2#03 | SHOULD profiled | The system SHOULD provide the ability to capture medication-related dates (e.g., start date, fill date, end date). |
| PH.2.5.2#04 | SHALL | The system SHALL provide the ability to capture medications that are not on the PHR Account Holder's existing medication list(s) or the existing medication history(s). |
| PH.2.5.2#05 | SHOULD | The system SHOULD provide the ability for the PHR Account Holder to render a notification to a prescriber or provider that the PHR Account Holder believes that a medication was erroneously captured or duplicated. |
| PH.2.5.2#06 | SHOULD | The system SHOULD provide the ability to capture and update a dispensing status for each medication order. |
| PH.2.5.2#07 | SHALL | The system SHALL present the list of medications to be self-administered. |
| PH.2.5.2#08 | SHALL profiled | The system SHALL provide the ability to render the timing, route of administration, and dose of all medications on the medication list. |
| PH.2.5.2#09 | MAY | The system MAY provide the ability to capture available instructions regarding the administration of selected items on the medication list (e.g., by receiving administration instruction from the family physician, or by downloading information from the pharmacy). |
| PH.2.5.2#10 | MAY conditional | IF the system captures available instructions regarding the administration of selected items on the medication list, THEN the system MAY provide the ability for the PHR Account Holder to render available instructions regarding the administration of selected items on the medication list (e.g., to help the PHR Account Holder determine whether to discuss with their provider adjusting the dosing of Warfarin after receiving the results of an updated International Normalized Ratio (INR) laboratory test). |
| PH.2.5.2#11 | SHOULD | The system SHOULD render a notification to the PHR Account Holder regarding a specific medication administration subject to the PHR Account Holder’s preconfigured modalities for transmitting various types of notifications. For example, on a specific date/time via text message, or for a specific event (such as strenuous exercise via email), or for a specific condition (such as failure to complete an activity of daily living via a phone call to a family member). |
| PH.2.5.2#12 | SHOULD | The system SHOULD provide the ability to capture medication self-administration details (e.g., timestamps, observations, complications, and/or the reason that a medication dose was not taken). For example, a mother could capture an indication that her baby was unwilling or unable to swallow a pill/liquid. |
| PH.2.5.2#13 | SHOULD profiled | The system SHOULD provide the ability for the PHR Account Holder to transmit refill (both refill and renewal) requests to a pharmacy or prescribing provider. |
| PH.2.5.2#14 | SHOULD profiled | The system SHOULD provide the ability to annotate the entire medication list with a field for text comments. |
| PH.2.5.2#15 | MAY | The system MAY provide the ability to render a medication list containing only medications selected by the PHR Account Holder. |
| PH.2.5.2#16 | SHALL profiled | The system SHALL provide the ability for the PHR Account Holder to update the medication list by indicating those medications that are actually being taken. |
| PH.2.5.2#17 | SHALL profiled | The system SHALL provide the ability for the PHR Account Holder to maintain the medication list by updating the status of the medication self-administration (e.g., no longer being taken or completed the regime). |
| PH.2.5.2#18 | SHOULD | The system SHOULD provide the ability to capture, maintain, and render prescription and non-prescription items (including dietary supplements) as discrete data and/or as lists. |
| PH.2.5.2#19 | SHOULD profiled | The system SHOULD provide the ability to receive current medications and a medication history from an external source (e.g., an EHR system, an insurance plan, a payer, or a pharmacy). |
| PH.2.5.2#20 | SHOULD | The system SHOULD provide the ability to receive, maintain, and render information from an external source (e.g., from an EHR system or from a pharmacy system) regarding the difference between medications that were ordered and medications that were actually dispensed. |
| PH.2.5.2#21 | MAY | The system MAY provide the ability to capture instructions regarding the cessation of selected items on the medication list. For example, the PHR Account holder could receive instructions from the family physician, the pharmacist, or from the medication manufacturer regarding behaviors that are permitted based on the cessation of a given medication. Another example is that the PHR Account Holder could be informed that the use of a blood thinner (e.g., Warfarin) must not be stopped abruptly. Finally, the PHR Account Holder could be informed that it is necessary to take the full course of a given prescribed medication. |
| PH.2.5.2#22 | SHOULD new | The system SHOULD provide the ability to specify query selection criteria (e.g., encounter type (inpatient, ER...), how far to look back (query back to date), medications ordered and dispensed, over the counter medications). |
| PH.2.5.2#23 | SHALL new | The system SHALL provide the ability to capture, maintain and render the query/response for a the medication list associated with the most recent medication reconciliation event, for example: - Constrained to the last outpatient encounter, ER visit, discharge from inpatient or extended care encounter; - Constrained to EHR systems of other providers; - Constrained to event date/time, organization, practitioner, encounter type. |
| PH.2.5.2#24 | SHOULD new | The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to the patient's pharmacy benefits manager (PBM) (e.g., a query via FHIR or API) |
| PH.2.5.2#25 | SHOULD new | The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to the patient's pharmacy dispensing system (e.g., a query via FHIR or API) |
| PH.2.5.2#26 | SHOULD new | The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to any system (e.g., EHR systems of other providers, PHR systems used by the patient). |
| PH.2.5.2#27 | SHALL new | The system SHALL capture and maintain separate medication lists from each external system responding to a query, until a subsequent step which then disambiguates and incorporates each unique medication into a single list. |
| PH.2.5.2#28 | SHALL new | The system SHALL provide the ability to capture, maintain and render a list of source systems (and providers) from which current (active) or past medications were received. |
| PH.2.5.2#29 | SHALL new | The system SHALL provide the ability to capture, store and render the medication list from a previous patient-centric medication list management session. |
| PH.2.5.2#30 | SHALL new | The system SHALL provide the ability to capture, maintain and render the patient's current medication list, incorporating lists captured from external sources (i.e., an "as taken" medication list authored by the patient). |
| PH.2.5.2#31 | SHALL new | The system SHALL provide the ability to determine the aggregation of medication lists from multiple sources via a disambiguation function. Disambiguation compares the following elements to decide if medications match, partially match or do not match: generic name, trade (brand) name(s), dose, dose units, route, and frequency. |
| PH.2.5.2#32 | SHALL new | The system SHALL provide the ability to capture, maintain and render the results of disambiguation of the medication list. |
| PH.2.5.2#33 | SHALL new | The system SHALL provide the ability to render each medication using a reference source for representation of the medication name, dose, and other structured medication information (e.g., use of reference sources such as RxNorm, pharmacy compendia). |
| PH.2.5.2#34 | SHALL new | The system SHALL provide the ability to capture, maintain and render confirmation that the patient is currently taking a particular medication, including medication name, dose, dose units, route, frequency, comments, and adherence details. |
| PH.2.5.2#35 | SHALL new | The system SHALL provide the ability to capture, maintain and render the addition of a medication to the patient medication list, including medication generic and brand name(s), dose, dose units, route, frequency, comments, adherence details, and ordering prescriber, using a reference source for representation and management of structured medication information (e.g., type-ahead pick lists, duplicate checking, presriber information). |
| PH.2.5.2#36 | SHALL new | If a medication has been added, the system SHALL determine whether new drug-drug interactions are identified. |
| PH.2.5.2#37 | SHALL conditional new | IF drug-drug interactions or other clinical safety related risks are identified, THEN the system SHALL provide the ability to manage related information (e.g., source of concern, severity of potential interaction, alerting user that interaction may need to be reviewed by clinician). |
| PH.2.5.2#38 | SHALL new | The system SHALL provide the ability to capture, maintain and render the modification (change) of a medication on the patient medication list, including dose, frequency, comments, and adherence, reason for update, and ordering prescriber. |
| PH.2.5.2#39 | SHALL new | The system SHALL provide the ability to update (i.e., modify/change) a medication after it has been added to the medication list. |
| PH.2.5.2#40 | SHALL new | The system SHALL provide the ability to capture, maintain and render a notation that the patient is not currently taking a medication and the current status of the medication. Status includes that the medication is: - Stopped, as directed by clinician; - Stopped by patient; - On hold, as directed by clinician; - On hold by patient. |
| PH.2.5.2#41 | SHALL new | The system SHALL provide the ability to capture, maintain and render the reason the patient is not taking a medication (e.g., taking alternative medication; side effects / adverse reaction / intolerance; course completed; no longer indicated; cannot afford; not covered by insurance; etc.). |
| PH.2.5.2#42 | SHOULD new | The system SHOULD provide the ability to capture the number of doses remaining for each medication. |
| PH.2.5.2#43 | SHOULD new | The system SHOULD provide the ability to capture, maintain and render medication refill requests based on remaining dose thresholds (e.g., system calculation to message patient to request a refill of a regularly taken medication). |
| PH.2.5.2#44 | MAY new | The system MAY provide the ability to determine upcoming refills needed from calculations based on pill counts, dates and frequencies as ordered. |
| PH.2.5.2#45 | SHALL new | The system SHALL present visual feedback to the patient (e.g., row color changes, strikethrough, other indicators) as the status of each medication is actioned upon during reconciliation. |
| PH.2.5.2#46 | SHALL new | The system SHALL present visual feedback to the patient (e.g., absence of change in row color) highlighting medications awaiting review during reconciliation. |
| PH.2.5.2#47 | SHALL new | The system SHALL provide the ability to render reports for printing or export (e.g., using a style sheet) per the preference of the patient - recommended presentation examples include: - Grouped by time of day, then alpha sort of generic (+ trade) name of medications with dosages as grouped sections (e.g., list of medications taken once a day in the AM); - Calendar (grid) week view, with x-axis as day of week and y-axis as time of day; - Include graphical version options with color pictures of the pills, pill markings; - Medical Assistant view – alpha sort of generic + (trade) name, dosage, and timing; with patient notes; - Clinician view – by discipline, grouped by confirm / not taking / update / add, then alpha sort of generic + (trade) name, dosage, and timing; with patient notes; - Patient-generated medication list (as electronic output) – all fields. |
| PH.2.5.2#48 | SHALL new | The system SHALL provide the ability to transmit a reviewed and/or updated medication list following patient-performed medication reconciliation (e.g., in preparation for an upcoming encounter): - Assembled as a data bundle (e.g., as a FHIR data bundle per a FHIR specification) - Incuding patient annotations. |
{
"resourceType": "Requirements",
"id": "MEDLISTFP-PH.2.5.2",
"meta": {
"profile": [
"http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"
]
},
"text": {
"status": "extensions",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "informative"
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "ehr"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 1,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/ehrs/us/medlistfp/ImplementationGuide/hl7.ehrs.us.medlistfp"
}
]
}
}
],
"url": "http://hl7.org/ehrs/us/medlistfp/Requirements/MEDLISTFP-PH.2.5.2",
"version": "1.0.0",
"name": "PH_2_5_2",
"title": "PH.2.5.2 (Function)",
"status": "active",
"date": "2026-07-24T07:22:03+00:00",
"publisher": "HL7 International / Electronic Health Records",
"contact": [
{
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description": "Manage the PHR Account Holder’s medication list.",
"jurisdiction": [
{
"coding": [
{
"system": "urn:iso:std:iso:3166",
"code": "US"
}
]
}
],
"purpose": "Medication lists are managed over time, whether over the course of a visit or stay, or the lifetime of a patient. All pertinent dates, including medication start, modification, and end dates can be stored. Medication histories, (for example, alternative supplements, over-the-counter medications, and herbal medications) may be relevant for review. Medication lists are not limited to medication orders recorded by providers, but may include, for example, pharmacy dispense/supply records, patient-reported medications, and additional information such as age-specific dosage.\n\nExample(s): The system maintains a medication list that may be followed by the PHR Account Holder and referenced by his or her providers and pharmacists. Copies of the PHR medication list may be kept by their providers in their EHRs.",
"derivedFrom": [
"http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-PH.2.5.2"
],
"statement": [
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-01",
"label": "PH.2.5.2#01",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture PHR Account Holder -specific medication data from a provider's EHR system, a pharmacy system, or from other sources.",
"derivedFrom": "PH.2.5.2#1"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-02",
"label": "PH.2.5.2#02",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture and update a fill status for each prescription.",
"derivedFrom": "PH.2.5.2#2"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-03",
"label": "PH.2.5.2#03",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture medication-related dates (e.g., start date, fill date, end date).",
"derivedFrom": "PH.2.5.2#3"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-04",
"label": "PH.2.5.2#04",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture medications that are not on the PHR Account Holder's existing medication list(s) or the existing medication history(s).",
"derivedFrom": "PH.2.5.2#4"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-05",
"label": "PH.2.5.2#05",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability for the PHR Account Holder to render a notification to a prescriber or provider that the PHR Account Holder believes that a medication was erroneously captured or duplicated.",
"derivedFrom": "PH.2.5.2#5"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-06",
"label": "PH.2.5.2#06",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture and update a dispensing status for each medication order.",
"derivedFrom": "PH.2.5.2#6"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-07",
"label": "PH.2.5.2#07",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL present the list of medications to be self-administered.",
"derivedFrom": "PH.2.5.2#7"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-08",
"label": "PH.2.5.2#08",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to render the timing, route of administration, and dose of all medications on the medication list.",
"derivedFrom": "PH.2.5.2#8"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-09",
"label": "PH.2.5.2#09",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "The system MAY provide the ability to capture available instructions regarding the administration of selected items on the medication list (e.g., by receiving administration instruction from the family physician, or by downloading information from the pharmacy).",
"derivedFrom": "PH.2.5.2#9"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-10",
"label": "PH.2.5.2#10",
"conformance": [
"MAY"
],
"conditionality": true,
"requirement": "IF the system captures available instructions regarding the administration of selected items on the medication list, THEN the system MAY provide the ability for the PHR Account Holder to render available instructions regarding the administration of selected items on the medication list (e.g., to help the PHR Account Holder determine whether to discuss with their provider adjusting the dosing of Warfarin after receiving the results of an updated International Normalized Ratio (INR) laboratory test).",
"derivedFrom": "PH.2.5.2#10"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-11",
"label": "PH.2.5.2#11",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD render a notification to the PHR Account Holder regarding a specific medication administration subject to the PHR Account Holder’s preconfigured modalities for transmitting various types of notifications. For example, on a specific date/time via text message, or for a specific event (such as strenuous exercise via email), or for a specific condition (such as failure to complete an activity of daily living via a phone call to a family member).",
"derivedFrom": "PH.2.5.2#11"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-12",
"label": "PH.2.5.2#12",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture medication self-administration details (e.g., timestamps, observations, complications, and/or the reason that a medication dose was not taken). For example, a mother could capture an indication that her baby was unwilling or unable to swallow a pill/liquid.",
"derivedFrom": "PH.2.5.2#12"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-13",
"label": "PH.2.5.2#13",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability for the PHR Account Holder to transmit refill (both refill and renewal) requests to a pharmacy or prescribing provider.",
"derivedFrom": "PH.2.5.2#13"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-14",
"label": "PH.2.5.2#14",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to annotate the entire medication list with a field for text comments.",
"derivedFrom": "PH.2.5.2#14"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-15",
"label": "PH.2.5.2#15",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "The system MAY provide the ability to render a medication list containing only medications selected by the PHR Account Holder.",
"derivedFrom": "PH.2.5.2#15"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-16",
"label": "PH.2.5.2#16",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability for the PHR Account Holder to update the medication list by indicating those medications that are actually being taken.",
"derivedFrom": "PH.2.5.2#16"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-17",
"label": "PH.2.5.2#17",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability for the PHR Account Holder to maintain the medication list by updating the status of the medication self-administration (e.g., no longer being taken or completed the regime).",
"derivedFrom": "PH.2.5.2#17"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-18",
"label": "PH.2.5.2#18",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture, maintain, and render prescription and non-prescription items (including dietary supplements) as discrete data and/or as lists.",
"derivedFrom": "PH.2.5.2#18"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "C"
}
],
"key": "MEDLISTFP-PH.2.5.2-19",
"label": "PH.2.5.2#19",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to receive current medications and a medication history from an external source (e.g., an EHR system, an insurance plan, a payer, or a pharmacy).",
"derivedFrom": "PH.2.5.2#19"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-20",
"label": "PH.2.5.2#20",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to receive, maintain, and render information from an external source (e.g., from an EHR system or from a pharmacy system) regarding the difference between medications that were ordered and medications that were actually dispensed.",
"derivedFrom": "PH.2.5.2#20"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "NC"
}
],
"key": "MEDLISTFP-PH.2.5.2-21",
"label": "PH.2.5.2#21",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "The system MAY provide the ability to capture instructions regarding the cessation of selected items on the medication list. For example, the PHR Account holder could receive instructions from the family physician, the pharmacist, or from the medication manufacturer regarding behaviors that are permitted based on the cessation of a given medication. Another example is that the PHR Account Holder could be informed that the use of a blood thinner (e.g., Warfarin) must not be stopped abruptly. Finally, the PHR Account Holder could be informed that it is necessary to take the full course of a given prescribed medication.",
"derivedFrom": "PH.2.5.2#21"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-22",
"label": "PH.2.5.2#22",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to specify query selection criteria (e.g., encounter type (inpatient, ER...), how far to look back (query back to date), medications ordered and dispensed, over the counter medications)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-23",
"label": "PH.2.5.2#23",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the query/response for a the medication list associated with the most recent medication reconciliation event, for example:\n- Constrained to the last outpatient encounter, ER visit, discharge from inpatient or extended care encounter;\n- Constrained to EHR systems of other providers;\n- Constrained to event date/time, organization, practitioner, encounter type."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-24",
"label": "PH.2.5.2#24",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to the patient's pharmacy benefits manager (PBM) (e.g., a query via FHIR or API)"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-25",
"label": "PH.2.5.2#25",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to the patient's pharmacy dispensing system (e.g., a query via FHIR or API)"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-26",
"label": "PH.2.5.2#26",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture, maintain and render the most recent query/response for a medication list to any system (e.g., EHR systems of other providers, PHR systems used by the patient)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-27",
"label": "PH.2.5.2#27",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL capture and maintain separate medication lists from each external system responding to a query, until a subsequent step which then disambiguates and incorporates each unique medication into a single list."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-28",
"label": "PH.2.5.2#28",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render a list of source systems (and providers) from which current (active) or past medications were received."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-29",
"label": "PH.2.5.2#29",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, store and render the medication list from a previous patient-centric medication list management session."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-30",
"label": "PH.2.5.2#30",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the patient's current medication list, incorporating lists captured from external sources (i.e., an \"as taken\" medication list authored by the patient)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-31",
"label": "PH.2.5.2#31",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to determine the aggregation of medication lists from multiple sources via a disambiguation function. Disambiguation compares the following elements to decide if medications match, partially match or do not match: generic name, trade (brand) name(s), dose, dose units, route, and frequency. "
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-32",
"label": "PH.2.5.2#32",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the results of disambiguation of the medication list. "
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-33",
"label": "PH.2.5.2#33",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to render each medication using a reference source for representation of the medication name, dose, and other structured medication information (e.g., use of reference sources such as RxNorm, pharmacy compendia)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-34",
"label": "PH.2.5.2#34",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render confirmation that the patient is currently taking a particular medication, including medication name, dose, dose units, route, frequency, comments, and adherence details."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-35",
"label": "PH.2.5.2#35",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the addition of a medication to the patient medication list, including medication generic and brand name(s), dose, dose units, route, frequency, comments, adherence details, and ordering prescriber, using a reference source for representation and management of structured medication information (e.g., type-ahead pick lists, duplicate checking, presriber information). "
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-36",
"label": "PH.2.5.2#36",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "If a medication has been added, the system SHALL determine whether new drug-drug interactions are identified."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-37",
"label": "PH.2.5.2#37",
"conformance": [
"SHALL"
],
"conditionality": true,
"requirement": "IF drug-drug interactions or other clinical safety related risks are identified, THEN the system SHALL provide the ability to manage related information (e.g., source of concern, severity of potential interaction, alerting user that interaction may need to be reviewed by clinician)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-38",
"label": "PH.2.5.2#38",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the modification (change) of a medication on the patient medication list, including dose, frequency, comments, and adherence, reason for update, and ordering prescriber. \n\n"
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-39",
"label": "PH.2.5.2#39",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to update (i.e., modify/change) a medication after it has been added to the medication list."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-40",
"label": "PH.2.5.2#40",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render a notation that the patient is not currently taking a medication and the current status of the medication. Status includes that the medication is:\n- Stopped, as directed by clinician;\n- Stopped by patient;\n- On hold, as directed by clinician;\n- On hold by patient."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-41",
"label": "PH.2.5.2#41",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to capture, maintain and render the reason the patient is not taking a medication (e.g., taking alternative medication; side effects / adverse reaction / intolerance; course completed; no longer indicated; cannot afford; not covered by insurance; etc.)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-42",
"label": "PH.2.5.2#42",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture the number of doses remaining for each medication."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-43",
"label": "PH.2.5.2#43",
"conformance": [
"SHOULD"
],
"conditionality": false,
"requirement": "The system SHOULD provide the ability to capture, maintain and render medication refill requests based on remaining dose thresholds (e.g., system calculation to message patient to request a refill of a regularly taken medication)."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-44",
"label": "PH.2.5.2#44",
"conformance": [
"MAY"
],
"conditionality": false,
"requirement": "The system MAY provide the ability to determine upcoming refills needed from calculations based on pill counts, dates and frequencies as ordered."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-45",
"label": "PH.2.5.2#45",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL present visual feedback to the patient (e.g., row color changes, strikethrough, other indicators) as the status of each medication is actioned upon during reconciliation. "
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-46",
"label": "PH.2.5.2#46",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL present visual feedback to the patient (e.g., absence of change in row color) highlighting medications awaiting review during reconciliation."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-47",
"label": "PH.2.5.2#47",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to render reports for printing or export (e.g., using a style sheet) per the preference of the patient - recommended presentation examples include: \n- Grouped by time of day, then alpha sort of generic (+ trade) name of medications with dosages as grouped sections (e.g., list of medications taken once a day in the AM);\n- Calendar (grid) week view, with x-axis as day of week and y-axis as time of day;\n- Include graphical version options with color pictures of the pills, pill markings;\n- Medical Assistant view – alpha sort of generic + (trade) name, dosage, and timing; with patient notes;\n- Clinician view – by discipline, grouped by confirm / not taking / update / add, then alpha sort of generic + (trade) name, dosage, and timing; with patient notes;\n- Patient-generated medication list (as electronic output) – all fields."
},
{
"extension": [
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
"valueBoolean": false
},
{
"url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-change-info",
"valueCode": "N"
}
],
"key": "MEDLISTFP-PH.2.5.2-48",
"label": "PH.2.5.2#48",
"conformance": [
"SHALL"
],
"conditionality": false,
"requirement": "The system SHALL provide the ability to transmit a reviewed and/or updated medication list following patient-performed medication reconciliation (e.g., in preparation for an upcoming encounter):\n- Assembled as a data bundle (e.g., as a FHIR data bundle per a FHIR specification)\n- Incuding patient annotations."
}
]
}