This CapabilityStatement defines the expected capabilities of the SMP Client actor when conforming to the SMP Implementation Guide (IG). It is intended to be used together with the US Core CapabilityStatement. Combined, they describe the complete set of profiles and RESTful operations that SMP clients support. Client requirements may also be influenced by local jurisdictional rules and other contextual considerations.

This resource defines the expected capabilities of the SMP Server actor when conforming to the SMP IG and It is expected that it will be used in conjunction with the US Core CapabilityStatement. Together they describe the complete list of actual profiles and RESTful operations supported by SMP servers. SMP Server requirements may also be impacted by the rules of local jurisdictions or other contextual requirements.

Optional operation to request an individual patient's medication history

Optional operation to submit an individual patient's medication history list for storage

A Medication Action Plan is a pharmacist-evaluation of a patient’s medications, and other clinical factors (e.g.: conditions, allergies). It identifies potential drug therapy related issues, recommended interventions and medication list.

This profile tailors the Parameters resource to convey status result of request to store medication history.

This profile tailors the Parameters resource to convey medication History operation inputs.

This profile tailors the Parameters resource to convey medication History operation outputs.

This profile tailors the Parameters resource to convey medication History operation inputs for storage.

A US Core DocumentReference constrained for references to SMP collection bundles by fixing the document type to LOINC 70006-2 Medication Management Note and limiting the subject to a US Core Patient.

A single package that contains a collection of medication action plans and supporting metadata on the medication reconciliaton review and recommended actions.

A single package that contains a specific kind of medication list with all supporting MedicationStatements and possibly other supporting resources.

A way to define and create a specific kind of medication list and the various medications that are on the list in a single transaction.

A description of a patient medication, may be used for non-prescription medications. Contains specifics about the type and strength that can be used to inform medication reconciliation.

A pharmacist-generated care plan that identifies issues and risks as well as recommended interventions and actions. These plans are normally created in response to a comprehensive medication review.

An issues or risk related to a given medication, therapy, or regimen. May include interventions and actions that mitigate the issue.

A related set of descriptions of individual medications a patient is or has received. May be a currently being administered list, a list of medications for discharge or a list of discontinued medications (with reasons). The list is point in time.

Defines the actual giving of a drug or compound to a patient for the purposes of treatment.

The description of a medication or drug that a patient is taking or prescribed. Or a medication or drug that a patient did take or was prescribed in the past. MedicationStatement can be created from a number of sources and may be anecdotal which can be useful in the recording of non-prescription, over-the-counter items. MedicationRequest and MedicationAdministration are a formal record of medications prescribed and given.

This profile supports the capture of medication adherence information within the MedicationStatement resource. Implementers SHOULD pre-adopt the FHIR MedicationStatement adherence extension as proposed for future FHIR releases.

• The adherence extension SHOULD be included in MedicationStatement resources when information about a patient's adherence to a medication regimen is available.
• The extension enables documentation of adherence status (e.g., 'taking as prescribed', 'not taking as prescribed') and, where applicable, the reason for non-adherence.
• Systems SHOULD support the extension to facilitate interoperability and the exchange of clinically significant adherence data.

A medication request for alprazolam 0.5 MG Oral Tablet

Example Med Action Plan (MAP) - Alprazolam and metoclopramide concurrent therapy as DetectedIssue with risk for falls.

A medication request for metoclopramide 10 MG Oral Tablet

A sample US Core patient

A sample practitioner

A sample US Core practitioner

Example of a List resource for a patient's SMP list

Example of a List resource for a patient's SMP primary care medication list

Example of a SMP Medication Action Plan Composition

Example Alprazolam Medication Statement

Example Metoclopramide Medication Statement

Example of a Bundle resource used to transmit a patient's SMP medication list and contents

Example DocumentReference for an SMP medication collection bundle.

Example of a Bundle resource used to create a medication list with a single entry

Example of a Bundle resource used to create multiple medication lists (hospital admission and discharge lists) in a single transaction

Example of a Parameters resource used to request a patient's medication history

Example of a Parameters resource used to respond to a request a patient's medication history

Example of a Medication resource in a patient's SMP list

Example of a MedicationAdministration resource for a patient's SMP list

Example of a MedicationStatement resource in a patient's SMP list

Example of a MedicationStatement resource in a patient's SMP list with a reference to a MedicationAdministration

Example of a MedicationStatement resource in a patient's SMP list for Amlodipine

Example of a MedicationStatement that uses effectivePeriod instead of effectiveDateTime

Example of a Parameters resource used to submit a patient's medication history

Example of a Parameters resource used to respond to a submission of a patient's medication history