R6 Ballot (1st Draft)

This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions

Pharmacy icon Work GroupMaturity Level: 4 Trial UseSecurity Category: Patient Compartments: Encounter, Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the MedicationStatement resource.

MedicationStatement
Element IdMedicationStatement
Definition

A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient's memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.

The primary difference between a medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the Medication Statement information may come from the patient's memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information.

The MedicationStatement resource was previously called MedicationStatement.

Short DisplayRecord of medication being taken by a patient
Cardinality0..*
TypeDomainResource
Alternate NamesMedicationStatement
Summaryfalse
MedicationStatement.identifier
Element IdMedicationStatement.identifier
Definition

Identifiers associated with this Medication Statement that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.

Short DisplayExternal identifier
NoteThis is a business identifier, not a resource identifier (see discussion)
Cardinality0..*
TypeIdentifier
Summarytrue
Comments

This is a business identifier, not a resource identifier.

MedicationStatement.partOf
Element IdMedicationStatement.partOf
Definition

A larger event of which this particular MedicationStatement is a component or step.

Short DisplayPart of referenced event
Cardinality0..*
TypeReference(Procedure | MedicationStatement)
HierarchyThis reference is part of a strict Hierarchy
Summaryfalse
MedicationStatement.status
Element IdMedicationStatement.status
Definition

A code representing the status of recording the medication statement.

Short Displayrecorded | entered-in-error | draft
Cardinality1..1
Terminology BindingMedicationStatement Status Codes (Required)
Typecode
Is Modifiertrue (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summarytrue
Comments

This status concerns just the recording of the medication statement. MedicationStatement.adherence should be used for indicating a patient's adherence to the information in this resource. Note, the statuses are different than in previous releases for MedicationStatement or MedicationStatement.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

MedicationStatement.category
Element IdMedicationStatement.category
Definition

Type of medication statement (for example, drug classification like ATC, where meds would be administered, legal category of the medication.).

Short DisplayType of medication statement
Cardinality0..*
Terminology BindingmedicationRequest Administration Location Codes (Example)
TypeCodeableConcept
Summarytrue
MedicationStatement.medication
Element IdMedicationStatement.medication
Definition

Identifies the medication being administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.

Short DisplayWhat medication was taken
Cardinality1..1
Terminology BindingSNOMED CT Medication Codes (Example)
TypeCodeableReference(Medication)
Summarytrue
Comments

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.

MedicationStatement.subject
Element IdMedicationStatement.subject
Definition

The person, animal or group who is/was taking the medication.

Short DisplayWho is/was taking the medication
Cardinality1..1
TypeReference(Patient | Group)
Summarytrue
MedicationStatement.encounter
Element IdMedicationStatement.encounter
Definition

The encounter that establishes the context for this MedicationStatement.

Short DisplayEncounter associated with MedicationStatement
Cardinality0..1
TypeReference(Encounter)
Summarytrue
MedicationStatement.effective[x]
Element IdMedicationStatement.effective[x]
Definition

The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.adherence element is Not Taking).

Short DisplayThe date/time or interval when the medication is/was/will be taken
Cardinality0..1
TypedateTime|Period|Timing
[x] NoteSee Choice of Datatypes for further information about how to use [x]
Summarytrue
Comments

This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken and is expected to continue indefinitely at the time the usage is recorded, the "end" date will be omitted. If the end date is known, then it is included as the "end date". The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.

MedicationStatement.dateAsserted
Element IdMedicationStatement.dateAsserted
Definition

The date when the Medication Statement was asserted by the information source.

Short DisplayWhen the usage was asserted?
Cardinality0..1
TypedateTime
Summarytrue
MedicationStatement.informationSource
Element IdMedicationStatement.informationSource
Definition

The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest.

Short DisplayPerson or organization that provided the information about the taking of this medication
Cardinality0..*
TypeReference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
Summaryfalse
MedicationStatement.derivedFrom
Element IdMedicationStatement.derivedFrom
Definition

Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement.

Short DisplayLink to information used to derive the MedicationStatement
Cardinality0..*
TypeReference(Any)
Summaryfalse
Comments

Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from.

MedicationStatement.reason
Element IdMedicationStatement.reason
Definition

A concept, Condition or observation that supports why the medication is being/was taken.

Short DisplayReason for why the medication is being/was taken
Cardinality0..*
Terminology BindingCondition/Problem/Diagnosis Codes (Example)
TypeCodeableReference(Condition | Observation | DiagnosticReport | Procedure)
Summaryfalse
Comments

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference.

MedicationStatement.note
Element IdMedicationStatement.note
Definition

Provides extra information about the Medication Statement that is not conveyed by the other attributes.

Short DisplayFurther information about the usage
Cardinality0..*
TypeAnnotation
Summaryfalse
MedicationStatement.relatedClinicalInformation
Element IdMedicationStatement.relatedClinicalInformation
Definition

Link to information that is relevant to a medication statement, for example, illicit drug use, gestational age, etc.

Short DisplayLink to information relevant to the usage of a medication
Cardinality0..*
TypeReference(Observation | Condition)
Summaryfalse
MedicationStatement.renderedDosageInstruction
Element IdMedicationStatement.renderedDosageInstruction
Definition

The full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses.

Short DisplayFull representation of the dosage instructions
Cardinality0..1
Typemarkdown
Requirements

The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.

Summaryfalse
MedicationStatement.dosage
Element IdMedicationStatement.dosage
Definition

Indicates how the medication is/was or should be taken by the patient.

Short DisplayDetails of how medication is/was taken or should be taken
Cardinality0..*
TypeDosage
Summaryfalse
Comments

The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, "from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily." It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest.

MedicationStatement.adherence
Element IdMedicationStatement.adherence
Definition

Indicates whether the medication is or is not being consumed or administered.

Short DisplayIndicates whether the medication is or is not being consumed or administered
Cardinality0..1
Summarytrue
Comments

This element can be used to indicate whether a patient is following a course of treatment as instructed/prescribed or whether they are taking medications of their own volition. It can also be used to indicate that a patient is not taking a medication, either because they were told not to or because they decided on their own.

MedicationStatement.adherence.code
Element IdMedicationStatement.adherence.code
Definition

Type of the adherence for the medication.

Short DisplayType of adherence
Cardinality1..1
Terminology BindingMedicationStatement Adherence Codes (Example)
TypeCodeableConcept
Summarytrue
MedicationStatement.adherence.reason
Element IdMedicationStatement.adherence.reason
Definition

Captures the reason for the current use or adherence of a medication.

Short DisplayDetails of the reason for the current use of the medication
Cardinality0..1
Terminology BindingSNOMED CT Drug Therapy Status codes (Example)
TypeCodeableConcept
Summaryfalse
Comments

This is generally only used for "exception" statuses such as "entered-in-error". The reason for performing the event at all is captured in reasonCode, not here.