Release 4B 5

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0: R5 - STU ). The This is the current published version which supercedes in it's permanent home (it will always be available at this version is 5.0.0 . URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R5 R4B R4 R3 R2

11.4 Resource MedicationStatement - Content

Pharmacy icon Work Group Maturity Level : 3 4   Trial Use Security Category : Patient Compartments : Encounter , Patient , Practitioner , RelatedPerson

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 medication statement medicationstatement and a medication administration 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 medication statement 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 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.

11.4.1 Scope and Usage

Common usage includes:

  • the recording of non-prescription and/or recreational drugs
  • the recording of an intake medication list upon admission to hospital
  • the summarization of a patient's "active medications" in a patient profile

A MedicationStatement may SHALL NOT be used to record substance abuse or the use of other agents such as tobacco or alcohol. This would typically be done if these substances are intended to be included in clinical decision support checking (for example, interaction checking) and as part of an active medication list. If the intent is to populate social history and/or to include additional information (for example, desire to quit, amount per day, negative health effects), then it is better to record alcohol UNLESS those agents have been prescribed, e.g. nicotine patches or gum, long term care alcohol, etc. These should recorded as an Observation that could then be used to populate Social History. History Observations.

This resource does not produce a medication list, but it does produce individual medication statements that may be used in the List resource to construct various types of medication lists. Note that other medication lists can also be constructed from the other Pharmacy resources (e.g., MedicationRequest, MedicationAdministration).

A medication statement is not a part of the prescribe -> dispense -> administer sequence, but is a report by a patient, significant other or a clinician that one or more of the prescribe, dispense or administer actions has occurred, resulting is a belief that the patient is, has, or will be using a particular medication.

MedicationStatement includes an adherence element. Note that this adherence is specific to that instance of MedicationStatement. If MedicationStatement.adherence is being tracked over time, then instances of MedicationStatement would report adherence for the interval noted in effectivePeriod.

MedicationStatement is an event resource from a FHIR workflow perspective - see Workflow Event

11.4.2 Boundaries and Relationships

The MedicationStatement resource is used to record a medications or substances that the patient reports as being taken, not taking, have taken in the past or may take in the future. It can also be used to record medication use that is derived from other records such as a MedicationRequest. The statement is not used to request or order a medication, supply or device. When requesting medication, supplies or devices when there is a patient focus or instructions regarding their use, a MedicationRequest , SupplyRequest or DeviceRequest should be used instead

The Medication domain includes a number of related resources

MedicationRequest An order for both supply of the medication and the instructions for administration of the medicine to a patient.
MedicationDispense Provision of a supply of a medication with the intention that it is subsequently consumed by a patient (usually in response to a prescription).
MedicationAdministration When a patient actually consumes a medicine, or it is otherwise administered to them
MedicationStatement This is a record of a medication being taken by a patient or that a medication has been given to a patient, where the record is the result of a report from the patient or another clinician, or derived from supporting information (for example, Claim, Observation or MedicationRequest). A medication statement is not a part of the prescribe->dispense->administer sequence but is a report that such a sequence (or at least a part of it) did take place, resulting in a belief that the patient has received a particular medication.

This resource is distinct from MedicationRequest , MedicationDispense and MedicationAdministration . Each of those resources refers to specific events - an individual order, an individual provisioning of medication or an individual dosing. MedicationStatement is a broader assertion covering a wider timespan and is independent of specific events. The existence of resource instances of any of the preceding three types may be used to infer a medication statement. However, medication statements can also be captured on the basis of other information, including an assertion by the patient or a care-giver, the results of a lab test, etc.

To indicate the link between a MedicationStatement instance and the Medication Request, Dispense, or Administration that was used to derive the MedicationStatement, the reference should be placed in the MedicationStatement.derivedFrom element.

11.4.3 References to this Resource

This resource is referenced by

11.4.4 Resource Content

Structure

Σ active | completed Additional supporting
Name Flags Card. Type Description & Constraints doco
. . MedicationStatement TU DomainResource Record of medication being taken by a patient

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier External identifier

. . . basedOn partOf 0..* Reference ( MedicationRequest | CarePlan | ServiceRequest ) Fulfils plan, proposal or order partOf Σ 0..* Reference ( MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation MedicationStatement ) Part of referenced event

. . . status ?! Σ 1..1 code recorded | entered-in-error | intended | stopped | on-hold | unknown | not-taken draft
Binding: MedicationStatement Status Codes ( Required ) statusReason 0..* CodeableConcept Reason for current status SNOMED CT Drug Therapy Status codes ( Example )
. . medication[x] . medication Σ 1..1 CodeableReference ( Medication ) What medication was taken
Binding: SNOMED CT Medication Codes ( Example ) medicationCodeableConcept CodeableConcept medicationReference Reference ( Medication )
. . . subject Σ 1..1 Reference ( Patient | Group ) Who is/was taking the medication
. . . context encounter Σ 0..1 Reference ( Encounter | EpisodeOfCare ) Encounter / Episode associated with MedicationStatement
. . . effective[x] Σ 0..1 The date/time or interval when the medication is/was/will be taken
. . . . effectiveDateTime dateTime
. . . . effectivePeriod Period
. . . . effectiveTiming Timing
. . . dateAsserted Σ 0..1 dateTime When the statement usage was asserted?
. . . informationSource 0..1 0..* Reference ( Patient | Practitioner | PractitionerRole | RelatedPerson | Organization ) Person or organization that provided the information about the taking of this medication

. . . derivedFrom 0..* Reference ( Any ) Link to information used to derive the MedicationStatement

. . reasonCode . reason 0..* CodeableConcept CodeableReference ( Condition | Observation | DiagnosticReport ) Reason for why the medication is being/was taken
Binding: Condition/Problem/Diagnosis Codes ( Example )

. . reasonReference . note 0..* Annotation Further information about the usage

. . . relatedClinicalInformation 0..* Reference ( Condition | Observation | DiagnosticReport Condition ) Condition or observation that supports why Link to information relevant to the usage of a medication is being/was taken

. . note . renderedDosageInstruction 0..* 0..1 Annotation markdown Further information about Full representation of the statement dosage instructions
. . . dosage 0..* Dosage Details of how medication is/was taken or should be taken

. . . adherence Σ 0..1 BackboneElement Indicates whether the medication is or is not being consumed or administered
.... code Σ 1..1 CodeableConcept Type of adherence
Binding: MedicationStatement Adherence Codes ( Example )
.... reason 0..1 CodeableConcept Details of the reason for the current use of the medication
Binding: SNOMED CT Drug Therapy Status codes ( Example )

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

MedicationStatement ( DomainResource ) 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 identifier : Identifier [0..*] A plan, proposal or order that is fulfilled in whole or in part by this event basedOn : Reference [0..*] « MedicationRequest | CarePlan | ServiceRequest » A larger event of which this particular event MedicationStatement is a component or step partOf : Reference [0..*] « MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation MedicationStatement » A code representing the patient or other source's judgment about the state status of recording the medication used that this statement is about. Generally, this will be active or completed (this element modifies the meaning of other elements) status : code [1..1] « null (Strength=Required) MedicationStatement Status MedicationStatementStatusCodes ! » Captures the reason for the current state Type of medication statement (for example, drug classification like ATC, where meds would be administered, legal category of the MedicationStatement medication.) statusReason category : CodeableConcept [0..*] « null (Strength=Example) SNOMEDCTDrugTherapyStatusCodes MedicationRequestAdministrati... ?? » Indicates where the medication is expected to be consumed or administered category : CodeableConcept [0..1] « null (Strength=Preferred) Medication usage category ? » 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 medication[x] medication : Element CodeableReference [1..1] « CodeableConcept | Reference ( Medication ); ; null (Strength=Example) SNOMEDCTMedicationCodes ?? » The person, animal or group who is/was taking the medication subject : Reference [1..1] « Patient | Group » The encounter or episode of care that establishes the context for this MedicationStatement context encounter : Reference [0..1] « Encounter | EpisodeOfCare » 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.taken MedicationStatement.adherence element is No) Not Taking) effective[x] : Element DataType [0..1] « dateTime | Period | Timing » The date when the medication statement Medication Statement was asserted by the information source dateAsserted : dateTime [0..1] 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 informationSource : Reference [0..1] [0..*] « Patient | Practitioner | PractitionerRole | RelatedPerson | Organization » Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement derivedFrom : Reference [0..*] « Any » A reason for why the medication is being/was taken reasonCode : CodeableConcept [0..*] « null (Strength=Example) Condition/Problem/DiagnosisCo... ?? » concept, Condition or observation that supports why the medication is being/was taken reasonReference reason : Reference CodeableReference [0..*] « Condition | Observation | DiagnosticReport ; null (Strength=Example) ConditionProblemDiagnosisCodes ?? » Provides extra information about the medication statement Medication Statement that is not conveyed by the other attributes note : Annotation [0..*] Link to information that is relevant to a medication statement, for example, illicit drug use, gestational age, etc relatedClinicalInformation : Reference [0..*] « Observation | Condition » 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 renderedDosageInstruction : markdown [0..1] Indicates how the medication is/was or should be taken by the patient dosage : Dosage [0..*] Adherence Type of the adherence for the medication code : CodeableConcept [1..1] « null (Strength=Example) MedicationStatementAdherenceC... ?? » Captures the reason for the current use or adherence of a medication reason : CodeableConcept [0..1] « null (Strength=Example) SNOMEDCTDrugTherapyStatusCodes ?? » Indicates whether the medication is or is not being consumed or administered adherence [0..1]

XML Template 

<The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">

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." class="dict">MedicationStatement xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External identifier --></identifier>
 <</basedOn>
 <|
   </partOf>
 <
 <</statusReason>
 <</category>
 <</medication[x]>

 <partOf><!-- 0..* Reference(MedicationStatement|Procedure) Part of referenced event --></partOf>
 <status value="[code]"/><!-- 1..1 recorded | entered-in-error | draft -->
 <category><!-- 0..* CodeableConcept Type of medication statement --></category>
 <medication><!-- 1..1 CodeableReference(Medication) What medication was taken --></medication>

 <subject><!-- 1..1 Reference(Group|Patient) Who is/was taking  the medication --></subject>
 <</context>
 <</effective[x]>
 <
 <|

 <encounter><!-- 0..1 Reference(Encounter) Encounter associated with MedicationStatement --></encounter>
 <effective[x]><!-- 0..1 dateTime|Period|Timing The date/time or interval when the medication is/was/will be taken --></effective[x]>
 <dateAsserted value="[dateTime]"/><!-- 0..1 When the usage was asserted? -->
 <informationSource><!-- 0..* Reference(Organization|Patient|Practitioner|

   PractitionerRole|RelatedPerson) Person or organization that provided the information about the taking of this medication --></informationSource>
 <</derivedFrom>
 <</reasonCode>
 <</reasonReference>
 <</note>

 <derivedFrom><!-- 0..* Reference(Any) Link to information used to derive the MedicationStatement --></derivedFrom>
 <reason><!-- 0..* CodeableReference(Condition|DiagnosticReport|Observation) Reason for why the medication is being/was taken --></reason>
 <note><!-- 0..* Annotation Further information about the usage --></note>
 <relatedClinicalInformation><!-- 0..* Reference(Condition|Observation) Link to information relevant to the usage of a medication --></relatedClinicalInformation>
 <renderedDosageInstruction value="[markdown]"/><!-- 0..1 Full representation of the dosage instructions -->

 <dosage><!-- 0..* Dosage Details of how medication is/was taken or should be taken --></dosage>
 <adherence>  <!-- 0..1 Indicates whether the medication is or is not being consumed or administered -->
  <code><!-- 1..1 CodeableConcept Type of adherence --></code>
  <reason><!-- 0..1 CodeableConcept Details of the reason for the current use of the medication --></reason>
 </adherence>

</MedicationStatement>

JSON Template 

{doco
  "resourceType" : "The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">",

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." class="dict">MedicationStatement",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External identifier
  "
  "|
   
  "
  "
  "
  
  " },
  " },

  "partOf" : [{ Reference(MedicationStatement|Procedure) }], // Part of referenced event
  "status" : "<code>", // R!  recorded | entered-in-error | draft
  "category" : [{ CodeableConcept }], // Type of medication statement
  "medication" : { CodeableReference(Medication) }, // R!  What medication was taken

  "subject" : { Reference(Group|Patient) }, // R!  Who is/was taking  the medication
  "
  
  ">",
  " },
  "
  "|
   
  "
  "
  "
  "
  "

  "encounter" : { Reference(Encounter) }, // Encounter associated with MedicationStatement
  // effective[x]: The date/time or interval when the medication is/was/will be taken. One of these 3:

  "effectiveDateTime" : "<dateTime>",
  "effectivePeriod" : { Period },
  "effectiveTiming" : { Timing },
  "dateAsserted" : "<dateTime>", // When the usage was asserted?
  "informationSource" : [{ Reference(Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) }], // Person or organization that provided the information about the taking of this medication

  "derivedFrom" : [{ Reference(Any) }], // Link to information used to derive the MedicationStatement
  "reason" : [{ CodeableReference(Condition|DiagnosticReport|Observation) }], // Reason for why the medication is being/was taken
  "note" : [{ Annotation }], // Further information about the usage
  "relatedClinicalInformation" : [{ Reference(Condition|Observation) }], // Link to information relevant to the usage of a medication
  "renderedDosageInstruction" : "<markdown>", // Full representation of the dosage instructions
  "dosage" : [{ Dosage }], // Details of how medication is/was taken or should be taken
  "adherence" : { // Indicates whether the medication is or is not being consumed or administered
    "code" : { CodeableConcept }, // R!  Type of adherence
    "reason" : { CodeableConcept } // Details of the reason for the current use of the medication
  }

}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">;

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." class="dict">MedicationStatement;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:
  fhir:
  fhir:|
  
  fhir:
  fhir:
  fhir:
  # . One of these 2
    fhir: ]
    fhir:) ]
  fhir:
  fhir:
  # . One of these 2
    fhir: ]
    fhir: ]
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External identifier
  fhir:partOf  ( [ Reference(MedicationStatement|Procedure) ] ... ) ; # 0..* Part of referenced event
  fhir:status [ code ] ; # 1..1 recorded | entered-in-error | draft
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Type of medication statement
  fhir:medication [ CodeableReference(Medication) ] ; # 1..1 What medication was taken
  fhir:subject [ Reference(Group|Patient) ] ; # 1..1 Who is/was taking  the medication
  fhir:encounter [ Reference(Encounter) ] ; # 0..1 Encounter associated with MedicationStatement
  # effective[x] : 0..1 The date/time or interval when the medication is/was/will be taken. One of these 3
    fhir:effective [  a fhir:dateTime ; dateTime ]
    fhir:effective [  a fhir:Period ; Period ]
    fhir:effective [  a fhir:Timing ; Timing ]
  fhir:dateAsserted [ dateTime ] ; # 0..1 When the usage was asserted?
  fhir:informationSource  ( [ Reference(Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ] ... ) ; # 0..* Person or organization that provided the information about the taking of this medication
  fhir:derivedFrom  ( [ Reference(Any) ] ... ) ; # 0..* Link to information used to derive the MedicationStatement
  fhir:reason  ( [ CodeableReference(Condition|DiagnosticReport|Observation) ] ... ) ; # 0..* Reason for why the medication is being/was taken
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Further information about the usage
  fhir:relatedClinicalInformation  ( [ Reference(Condition|Observation) ] ... ) ; # 0..* Link to information relevant to the usage of a medication
  fhir:renderedDosageInstruction [ markdown ] ; # 0..1 Full representation of the dosage instructions
  fhir:dosage  ( [ Dosage ] ... ) ; # 0..* Details of how medication is/was taken or should be taken
  fhir:adherence [ # 0..1 Indicates whether the medication is or is not being consumed or administered
    fhir:code [ CodeableConcept ] ; # 1..1 Type of adherence
    fhir:reason [ CodeableConcept ] ; # 0..1 Details of the reason for the current use of the medication
  ] ;

]

Changes since from both R4 and R4B

MedicationStatement
MedicationStatement.partOf
  • No Changes Type Reference: Removed Target Types MedicationAdministration, MedicationDispense, Observation
MedicationStatement.status
  • Remove codes active , completed , intended , stopped , on-hold , unknown , not-taken
  • Add codes recorded , draft
MedicationStatement.category
  • Max Cardinality changed from 1 to *
MedicationStatement.medication
  • Renamed from medication[x] to medication
  • Add Type CodeableReference
  • Remove Types CodeableConcept, Reference(Medication)
MedicationStatement.encounter
  • Renamed from context to encounter
  • Type Reference: Removed Target Type EpisodeOfCare
MedicationStatement.effective[x]
  • Add Type Timing
MedicationStatement.informationSource
  • Max Cardinality changed from 1 to *
MedicationStatement.reason
  • Added Element
MedicationStatement.relatedClinicalInformation
  • Added Element
MedicationStatement.renderedDosageInstruction
  • Added Element
MedicationStatement.adherence
  • Added Element
MedicationStatement.adherence.code
  • Added Mandatory Element
MedicationStatement.adherence.reason
  • Added Element
MedicationStatement.basedOn
  • Deleted
MedicationStatement.statusReason
  • Deleted
MedicationStatement.reasonCode
  • Deleted (-> reason)
MedicationStatement.reasonReference
  • Deleted (-> reason)

See the Full Difference for further information

This analysis is available for R4 as XML or JSON . Conversions between R3 and R4 for R4B as XML or JSON .

See R3 <--> R4 <--> R5 Conversion Maps (status = 7 tests that all execute ok. 3 fail round-trip testing and 7 r3 resources are invalid (0 errors). ) See Conversions Summary .)

Structure

Σ active | completed Additional supporting
Name Flags Card. Type Description & Constraints doco
. . MedicationStatement TU DomainResource Record of medication being taken by a patient

Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier External identifier

. . . basedOn partOf 0..* Reference ( MedicationRequest | CarePlan | ServiceRequest ) Fulfils plan, proposal or order partOf Σ 0..* Reference ( MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation MedicationStatement ) Part of referenced event

. . . status ?! Σ 1..1 code recorded | entered-in-error | intended | stopped | on-hold | unknown | not-taken draft
Binding: MedicationStatement Status Codes ( Required ) statusReason 0..* CodeableConcept Reason for current status SNOMED CT Drug Therapy Status codes ( Example )
. . medication[x] . medication Σ 1..1 CodeableReference ( Medication ) What medication was taken
Binding: SNOMED CT Medication Codes ( Example ) medicationCodeableConcept CodeableConcept medicationReference Reference ( Medication )
. . . subject Σ 1..1 Reference ( Patient | Group ) Who is/was taking the medication
. . . context encounter Σ 0..1 Reference ( Encounter | EpisodeOfCare ) Encounter / Episode associated with MedicationStatement
. . . effective[x] Σ 0..1 The date/time or interval when the medication is/was/will be taken
. . . . effectiveDateTime dateTime
. . . . effectivePeriod Period
. . . . effectiveTiming Timing
. . . dateAsserted Σ 0..1 dateTime When the statement usage was asserted?
. . . informationSource 0..1 0..* Reference ( Patient | Practitioner | PractitionerRole | RelatedPerson | Organization ) Person or organization that provided the information about the taking of this medication

. . . derivedFrom 0..* Reference ( Any ) Link to information used to derive the MedicationStatement

. . reasonCode . reason 0..* CodeableConcept CodeableReference ( Condition | Observation | DiagnosticReport ) Reason for why the medication is being/was taken
Binding: Condition/Problem/Diagnosis Codes ( Example )

. . reasonReference . note 0..* Annotation Further information about the usage

... relatedClinicalInformation 0..* Reference ( Condition | Observation | DiagnosticReport Condition ) Condition or observation that supports why Link to information relevant to the usage of a medication is being/was taken

. . note . renderedDosageInstruction 0..* 0..1 Annotation markdown Further information about Full representation of the statement dosage instructions
. . . dosage 0..* Dosage Details of how medication is/was taken or should be taken

. . . adherence Σ 0..1 BackboneElement Indicates whether the medication is or is not being consumed or administered
.... code Σ 1..1 CodeableConcept Type of adherence
Binding: MedicationStatement Adherence Codes ( Example )
.... reason 0..1 CodeableConcept Details of the reason for the current use of the medication
Binding: SNOMED CT Drug Therapy Status codes ( Example )

doco Documentation for this format icon

See the Extensions for this resource

UML Diagram ( Legend )

MedicationStatement ( DomainResource ) 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 identifier : Identifier [0..*] A plan, proposal or order that is fulfilled in whole or in part by this event basedOn : Reference [0..*] « MedicationRequest | CarePlan | ServiceRequest » A larger event of which this particular event MedicationStatement is a component or step partOf : Reference [0..*] « MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation MedicationStatement » A code representing the patient or other source's judgment about the state status of recording the medication used that this statement is about. Generally, this will be active or completed (this element modifies the meaning of other elements) status : code [1..1] « null (Strength=Required) MedicationStatement Status MedicationStatementStatusCodes ! » Captures the reason for the current state Type of medication statement (for example, drug classification like ATC, where meds would be administered, legal category of the MedicationStatement medication.) statusReason category : CodeableConcept [0..*] « null (Strength=Example) SNOMEDCTDrugTherapyStatusCodes MedicationRequestAdministrati... ?? » Indicates where the medication is expected to be consumed or administered category : CodeableConcept [0..1] « null (Strength=Preferred) Medication usage category ? » 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 medication[x] medication : Element CodeableReference [1..1] « CodeableConcept | Reference ( Medication ); ; null (Strength=Example) SNOMEDCTMedicationCodes ?? » The person, animal or group who is/was taking the medication subject : Reference [1..1] « Patient | Group » The encounter or episode of care that establishes the context for this MedicationStatement context encounter : Reference [0..1] « Encounter | EpisodeOfCare » 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.taken MedicationStatement.adherence element is No) Not Taking) effective[x] : Element DataType [0..1] « dateTime | Period | Timing » The date when the medication statement Medication Statement was asserted by the information source dateAsserted : dateTime [0..1] 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 informationSource : Reference [0..1] [0..*] « Patient | Practitioner | PractitionerRole | RelatedPerson | Organization » Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement derivedFrom : Reference [0..*] « Any » A reason for why the medication is being/was taken reasonCode : CodeableConcept [0..*] « null (Strength=Example) Condition/Problem/DiagnosisCo... ?? » concept, Condition or observation that supports why the medication is being/was taken reasonReference reason : Reference CodeableReference [0..*] « Condition | Observation | DiagnosticReport ; null (Strength=Example) ConditionProblemDiagnosisCodes ?? » Provides extra information about the medication statement Medication Statement that is not conveyed by the other attributes note : Annotation [0..*] Link to information that is relevant to a medication statement, for example, illicit drug use, gestational age, etc relatedClinicalInformation : Reference [0..*] « Observation | Condition » 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 renderedDosageInstruction : markdown [0..1] Indicates how the medication is/was or should be taken by the patient dosage : Dosage [0..*] Adherence Type of the adherence for the medication code : CodeableConcept [1..1] « null (Strength=Example) MedicationStatementAdherenceC... ?? » Captures the reason for the current use or adherence of a medication reason : CodeableConcept [0..1] « null (Strength=Example) SNOMEDCTDrugTherapyStatusCodes ?? » Indicates whether the medication is or is not being consumed or administered adherence [0..1]

XML Template 

<The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">

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." class="dict">MedicationStatement xmlns="http://hl7.org/fhir"> doco

 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External identifier --></identifier>
 <</basedOn>
 <|
   </partOf>
 <
 <</statusReason>
 <</category>
 <</medication[x]>

 <partOf><!-- 0..* Reference(MedicationStatement|Procedure) Part of referenced event --></partOf>
 <status value="[code]"/><!-- 1..1 recorded | entered-in-error | draft -->
 <category><!-- 0..* CodeableConcept Type of medication statement --></category>
 <medication><!-- 1..1 CodeableReference(Medication) What medication was taken --></medication>

 <subject><!-- 1..1 Reference(Group|Patient) Who is/was taking  the medication --></subject>
 <</context>
 <</effective[x]>
 <
 <|

 <encounter><!-- 0..1 Reference(Encounter) Encounter associated with MedicationStatement --></encounter>
 <effective[x]><!-- 0..1 dateTime|Period|Timing The date/time or interval when the medication is/was/will be taken --></effective[x]>
 <dateAsserted value="[dateTime]"/><!-- 0..1 When the usage was asserted? -->
 <informationSource><!-- 0..* Reference(Organization|Patient|Practitioner|

   PractitionerRole|RelatedPerson) Person or organization that provided the information about the taking of this medication --></informationSource>
 <</derivedFrom>
 <</reasonCode>
 <</reasonReference>
 <</note>

 <derivedFrom><!-- 0..* Reference(Any) Link to information used to derive the MedicationStatement --></derivedFrom>
 <reason><!-- 0..* CodeableReference(Condition|DiagnosticReport|Observation) Reason for why the medication is being/was taken --></reason>
 <note><!-- 0..* Annotation Further information about the usage --></note>
 <relatedClinicalInformation><!-- 0..* Reference(Condition|Observation) Link to information relevant to the usage of a medication --></relatedClinicalInformation>
 <renderedDosageInstruction value="[markdown]"/><!-- 0..1 Full representation of the dosage instructions -->

 <dosage><!-- 0..* Dosage Details of how medication is/was taken or should be taken --></dosage>
 <adherence>  <!-- 0..1 Indicates whether the medication is or is not being consumed or administered -->
  <code><!-- 1..1 CodeableConcept Type of adherence --></code>
  <reason><!-- 0..1 CodeableConcept Details of the reason for the current use of the medication --></reason>
 </adherence>

</MedicationStatement>

JSON Template 

{doco
  "resourceType" : "The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">",

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." class="dict">MedicationStatement",

  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External identifier
  "
  "|
   
  "
  "
  "
  
  " },
  " },

  "partOf" : [{ Reference(MedicationStatement|Procedure) }], // Part of referenced event
  "status" : "<code>", // R!  recorded | entered-in-error | draft
  "category" : [{ CodeableConcept }], // Type of medication statement
  "medication" : { CodeableReference(Medication) }, // R!  What medication was taken

  "subject" : { Reference(Group|Patient) }, // R!  Who is/was taking  the medication
  "
  
  ">",
  " },
  "
  "|
   
  "
  "
  "
  "
  "

  "encounter" : { Reference(Encounter) }, // Encounter associated with MedicationStatement
  // effective[x]: The date/time or interval when the medication is/was/will be taken. One of these 3:

  "effectiveDateTime" : "<dateTime>",
  "effectivePeriod" : { Period },
  "effectiveTiming" : { Timing },
  "dateAsserted" : "<dateTime>", // When the usage was asserted?
  "informationSource" : [{ Reference(Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) }], // Person or organization that provided the information about the taking of this medication

  "derivedFrom" : [{ Reference(Any) }], // Link to information used to derive the MedicationStatement
  "reason" : [{ CodeableReference(Condition|DiagnosticReport|Observation) }], // Reason for why the medication is being/was taken
  "note" : [{ Annotation }], // Further information about the usage
  "relatedClinicalInformation" : [{ Reference(Condition|Observation) }], // Link to information relevant to the usage of a medication
  "renderedDosageInstruction" : "<markdown>", // Full representation of the dosage instructions
  "dosage" : [{ Dosage }], // Details of how medication is/was taken or should be taken
  "adherence" : { // Indicates whether the medication is or is not being consumed or administered
    "code" : { CodeableConcept }, // R!  Type of adherence
    "reason" : { CodeableConcept } // Details of the reason for the current use of the medication
  }

}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication.  A medication statement 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." class="dict">;

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." class="dict">MedicationStatement;

  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:
  fhir:
  fhir:|
  
  fhir:
  fhir:
  fhir:
  # . One of these 2
    fhir: ]
    fhir:) ]
  fhir:
  fhir:
  # . One of these 2
    fhir: ]
    fhir: ]
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:identifier  ( [ Identifier ] ... ) ; # 0..* External identifier
  fhir:partOf  ( [ Reference(MedicationStatement|Procedure) ] ... ) ; # 0..* Part of referenced event
  fhir:status [ code ] ; # 1..1 recorded | entered-in-error | draft
  fhir:category  ( [ CodeableConcept ] ... ) ; # 0..* Type of medication statement
  fhir:medication [ CodeableReference(Medication) ] ; # 1..1 What medication was taken
  fhir:subject [ Reference(Group|Patient) ] ; # 1..1 Who is/was taking  the medication
  fhir:encounter [ Reference(Encounter) ] ; # 0..1 Encounter associated with MedicationStatement
  # effective[x] : 0..1 The date/time or interval when the medication is/was/will be taken. One of these 3
    fhir:effective [  a fhir:dateTime ; dateTime ]
    fhir:effective [  a fhir:Period ; Period ]
    fhir:effective [  a fhir:Timing ; Timing ]
  fhir:dateAsserted [ dateTime ] ; # 0..1 When the usage was asserted?
  fhir:informationSource  ( [ Reference(Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ] ... ) ; # 0..* Person or organization that provided the information about the taking of this medication
  fhir:derivedFrom  ( [ Reference(Any) ] ... ) ; # 0..* Link to information used to derive the MedicationStatement
  fhir:reason  ( [ CodeableReference(Condition|DiagnosticReport|Observation) ] ... ) ; # 0..* Reason for why the medication is being/was taken
  fhir:note  ( [ Annotation ] ... ) ; # 0..* Further information about the usage
  fhir:relatedClinicalInformation  ( [ Reference(Condition|Observation) ] ... ) ; # 0..* Link to information relevant to the usage of a medication
  fhir:renderedDosageInstruction [ markdown ] ; # 0..1 Full representation of the dosage instructions
  fhir:dosage  ( [ Dosage ] ... ) ; # 0..* Details of how medication is/was taken or should be taken
  fhir:adherence [ # 0..1 Indicates whether the medication is or is not being consumed or administered
    fhir:code [ CodeableConcept ] ; # 1..1 Type of adherence
    fhir:reason [ CodeableConcept ] ; # 0..1 Details of the reason for the current use of the medication
  ] ;

]

Changes since Release 4 from both R4 and R4B

MedicationStatement
MedicationStatement.partOf
  • No Changes Type Reference: Removed Target Types MedicationAdministration, MedicationDispense, Observation
MedicationStatement.status
  • Remove codes active , completed , intended , stopped , on-hold , unknown , not-taken
  • Add codes recorded , draft
MedicationStatement.category
  • Max Cardinality changed from 1 to *
MedicationStatement.medication
  • Renamed from medication[x] to medication
  • Add Type CodeableReference
  • Remove Types CodeableConcept, Reference(Medication)
MedicationStatement.encounter
  • Renamed from context to encounter
  • Type Reference: Removed Target Type EpisodeOfCare
MedicationStatement.effective[x]
  • Add Type Timing
MedicationStatement.informationSource
  • Max Cardinality changed from 1 to *
MedicationStatement.reason
  • Added Element
MedicationStatement.relatedClinicalInformation
  • Added Element
MedicationStatement.renderedDosageInstruction
  • Added Element
MedicationStatement.adherence
  • Added Element
MedicationStatement.adherence.code
  • Added Mandatory Element
MedicationStatement.adherence.reason
  • Added Element
MedicationStatement.basedOn
  • Deleted
MedicationStatement.statusReason
  • Deleted
MedicationStatement.reasonCode
  • Deleted (-> reason)
MedicationStatement.reasonReference
  • Deleted (-> reason)

See the Full Difference for further information

This analysis is available for R4 as XML or JSON . Conversions between R3 and R4 for R4B as XML or JSON .

See R3 <--> R4 <--> R5 Conversion Maps (status = 7 tests that all execute ok. 3 fail round-trip testing and 7 r3 resources are invalid (0 errors). ) See Conversions Summary .)

 

See the Profiles & Extensions and the alternate Additional definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis

11.4.4.1 Terminology Bindings

MedicationStatement.statusReason MedicationStatement.category MedicationStatement.medication[x] MedicationStatement.reasonCode
Path Definition ValueSet Type Reference Documentation
MedicationStatement.status MedicationStatementStatusCodes Required

MedicationStatement Status Codes

MedicationStatement.category MedicationRequestAdministrationLocationCodes Example SNOMEDCTDrugTherapyStatusCodes

MedicationRequest Administration Location Codes

MedicationStatement.medication SNOMEDCTMedicationCodes Preferred Example Medication usage category

This value set includes all drug or medicament substance codes and all pharmaceutical/biologic products from SNOMED CT - provided as an exemplar value set.

MedicationStatement.reason ConditionProblemDiagnosisCodes Example SNOMEDCTMedicationCodes

Example value set for Condition/Problem/Diagnosis codes.

MedicationStatement.adherence.code MedicationStatementAdherenceCodes Example Condition/Problem/DiagnosisCodes

MedicationStatement Adherence Codes

MedicationStatement.adherence.reason SNOMEDCTDrugTherapyStatusCodes Example

This value set includes some taken and not taken reason codes from SNOMED CT - provided as an exemplar

11.4.5 Search Parameters

Search parameters for this resource. See also the full list of search parameters for this resource , and check the Extensions registry for search parameters on extensions related to this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
category adherence token Returns statements of this category of medicationstatement based on adherence or compliance MedicationStatement.category MedicationStatement.adherence.code
code category token Return Returns statements of this medication code category of MedicationStatement (MedicationStatement.medication as CodeableConcept) MedicationStatement.category
context code reference token Returns Return statements for a specific context (episode or episode of Care). this medication code MedicationStatement.context ( EpisodeOfCare , Encounter ) MedicationStatement.medication.concept 22 Resources
effective date Date when patient was taking (or not taking) the medication MedicationStatement.effective MedicationStatement.effective.ofType(dateTime) | MedicationStatement.effective.ofType(Period)
identifier encounter token reference Return Returns statements with this external identifier for a specific encounter MedicationStatement.identifier MedicationStatement.encounter
( Encounter ) 		29 Resources
medication identifier reference token Return statements of with this medication reference external identifier (MedicationStatement.medication as Reference) ( Medication ) MedicationStatement.identifier 65 Resources
part-of medication reference Returns Return statements that are part of another event. this medication reference MedicationStatement.partOf ( MedicationDispense , Observation , MedicationAdministration , Procedure , MedicationStatement ) MedicationStatement.medication.reference 4 Resources
patient reference Returns statements for a specific patient. MedicationStatement.subject.where(resolve() is Patient)
( Patient ) 		66 Resources
source reference Who or where the information in the statement came from MedicationStatement.informationSource
( Practitioner , Organization , Patient , PractitionerRole , RelatedPerson )
status token Return statements that match the given status MedicationStatement.status 4 Resources
subject reference The identity of a patient, animal or group to list statements for MedicationStatement.subject
( Group , Patient )