DSTU2 QA Preview

This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.16 Resource MedicationStatement - Content

Pharmacy Work GroupMaturity Level: 0Compartments: Patient, Practitioner, RelatedPerson

A record of a medication that is being consumed by a patient. A medication statements 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 e.g. the patients’ 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 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.

4.16.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

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. Medication Order, Medication Administration.

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.

4.16.2 Boundaries and Relationships

The Medication domain includes a number of related resources

MedicationOrder 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 medication being taken by a patient, or that the medication has been given to a patient where the record is the result of a report from the patient, or another clinician. 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 MedicationOrder, MedicationDispense and MedicationAdministration. Each of those resources refer 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 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.

This resource is referenced by goal

4.16.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationStatement Σ IDomainResourceRecord of medication being taken by a patient
Reason for use is only permitted if wasNotTaken is false
Reason not taken is only permitted if wasNotTaken is true
... identifier Σ0..*IdentifierExternal Identifier
... patient Σ1..1Reference(Patient)Who was/is taking medication
... informationSource Σ0..1Reference(Patient | Practitioner | RelatedPerson)
... dateAsserted Σ0..1dateTimeWhen the statement was asserted?
... status ?! Σ1..1codeactive | completed | entered-in-error | intended
MedicationStatementStatus (Required)
... wasNotTaken ?! Σ0..1booleanTrue if medication is/was not being taken
... reasonNotTaken Σ I0..*CodeableConceptTrue if asserting medication was not given
Reason Medication Not Given Codes (Example)
... reasonForUse[x] Σ0..1
.... reasonForUseCodeableConceptCodeableConcept
.... reasonForUseReferenceReference(Condition)
... effective[x] Σ0..1Over what period was medication consumed?
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... note Σ0..1stringFurther information about the statement
... supportingInformation Σ0..*Reference(Any)Additional supporting information
... medication[x] Σ1..1What medication was taken?
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(Medication)
... dosage Σ0..*BackboneElementDetails of how medication was taken
.... text Σ0..1stringReported dosage information
.... timing Σ0..1TimingWhen/how often was medication taken?
.... asNeeded[x] Σ0..1Take "as needed" f(or x)
..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site[x] Σ0..1Where on body was medication administered?
SNOMED CT Anatomical Structure for Administration Site Codes (Example)
..... siteCodeableConceptCodeableConcept
..... siteReferenceReference(BodySite)
.... route Σ0..1CodeableConceptHow did the medication enter the body?
SNOMED CT Route Codes (Example)
.... method Σ0..1CodeableConceptTechnique used to administer medication
.... quantity[x] Σ0..1Amount administered in one dose
..... quantityQuantitySimpleQuantity
..... quantityRangeRange
.... rate[x] Σ0..1Dose quantity per unit of time
..... rateRatioRatio
..... rateRangeRange
.... maxDosePerPeriod Σ0..1RatioMaximum dose that was consumed per unit of time

doco Documentation for this format

UML Diagram

MedicationStatement (DomainResource)External identifier - FHIR will generate its own internal IDs (probably URLs) which do not need to be explicitly managed by the resource. The identifier here is one that would be used by another non-FHIR system - for example an automated medication pump would provide a record each time it operated; an administration while the patient was off the ward might be made with a different system and entered after the event. Particularly important if these records have to be updatedidentifier : Identifier [0..*]The person or animal who is /was taking the medicationpatient : Reference [1..1] « Patient »The person who provided the information about the taking of this medicationinformationSource : Reference [0..1] « Patient|Practitioner| RelatedPerson »The date when the medication statement was asserted by the information sourcedateAsserted : dateTime [0..1]A code representing the patient or other source’s judgment about the state of 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] « A set of codes indicating the current status of a MedicationStatement (Strength=Required)MedicationStatementStatus! »Set this to true if the record is saying that the medication was NOT taken (this element modifies the meaning of other elements)wasNotTaken : boolean [0..1]A code indicating why the medication was not takenreasonNotTaken : CodeableConcept [0..*] « A set of codes indicating the reason why the MedicationAdministration is negated (Strength=Example)Reason Medication Not Given ?? »A reason for why the medication is being/was takenreasonForUse[x] : Type [0..1] « CodeableConcept|Reference(Condition) »The interval of time during which it is being asserted that the patient was taking the medication (or was not taking, when the 'wasNotGiven' attribute is true)effective[x] : Type [0..1] « dateTime|Period »Provides extra information about the medication statement that is not conveyed by the other attributesnote : string [0..1]Allows linking the MedicationStatement to the underlying MedicationOrder, or to other information that supports the MedicationStatementsupportingInformation : Reference [0..*] « Any »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 medicationsmedication[x] : Type [1..1] « CodeableConcept|Reference(Medication) »DosageFree text dosage information as reported about a patient's medication use. When coded dosage information is present, the free text may still be present for display to humanstext : string [0..1]The timing schedule for giving the medication to the patient. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013"timing : Timing [0..1]Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept). Specifically if 'boolean' datatype is selected, then the following logic applies: If set to True, this indicates that the medication is only taken when needed, within the specified scheduleasNeeded[x] : Type [0..1] « boolean|CodeableConcept »A coded specification of or a reference to the anatomic site where the medication first enters the bodysite[x] : Type [0..1] « CodeableConcept|Reference(BodySite); A coded concept describing the site location the medicine enters into or onto the body (Strength=Example)SNOMED CT Anatomical Structur...?? »A code specifying the route or physiological path of administration of a therapeutic agent into or onto a subjectroute : CodeableConcept [0..1] « A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject (Strength=Example)SNOMED CT Route ?? »A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. Examples: Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequentlymethod : CodeableConcept [0..1]The amount of therapeutic or other substance given at one administration eventquantity[x] : Type [0..1] « Quantity(SimpleQuantity)|Range »Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Currently we do not specify a default of '1' in the denominator, but this is being discussed. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hoursrate[x] : Type [0..1] « Ratio|Range »The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. E.g. 1000mg in 24 hoursmaxDosePerPeriod : Ratio [0..1]Indicates how the medication is/was used by the patientdosage[0..*]

XML Template

<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>
 <patient><!-- 1..1 Reference(Patient) Who was/is taking medication --></patient>
 <informationSource><!-- 0..1 Reference(Patient|Practitioner|RelatedPerson)  --></informationSource>
 <dateAsserted value="[dateTime]"/><!-- 0..1 When the statement was asserted? -->
 <status value="[code]"/><!-- 1..1 active | completed | entered-in-error | intended -->
 <wasNotTaken value="[boolean]"/><!-- 0..1 True if medication is/was not being taken -->
 <reasonNotTaken><!-- ?? 0..* CodeableConcept True if asserting medication was not given --></reasonNotTaken>
 <reasonForUse[x]><!-- 0..1 CodeableConcept|Reference(Condition)  --></reasonForUse[x]>
 <effective[x]><!-- 0..1 dateTime|Period Over what period was medication consumed? --></effective[x]>
 <note value="[string]"/><!-- 0..1 Further information about the statement -->
 <supportingInformation><!-- 0..* Reference(Any) Additional supporting information --></supportingInformation>
 <medication[x]><!-- 1..1 CodeableConcept|Reference(Medication) What medication was taken? --></medication[x]>
 <dosage>  <!-- 0..* Details of how medication was taken -->
  <text value="[string]"/><!-- 0..1 Reported dosage information -->
  <timing><!-- 0..1 Timing When/how often was medication taken? --></timing>
  <asNeeded[x]><!-- 0..1 boolean|CodeableConcept Take "as needed" f(or x) --></asNeeded[x]>
  <site[x]><!-- 0..1 CodeableConcept|Reference(BodySite) Where on body was medication administered? --></site[x]>
  <route><!-- 0..1 CodeableConcept How did the medication enter the body? --></route>
  <method><!-- 0..1 CodeableConcept Technique used to administer medication --></method>
  <quantity[x]><!-- 0..1 Quantity(SimpleQuantity)|Range Amount administered in one dose --></quantity[x]>
  <rate[x]><!-- 0..1 Ratio|Range Dose quantity per unit of time --></rate[x]>
  <maxDosePerPeriod><!-- 0..1 Ratio Maximum dose that was consumed per unit of time --></maxDosePerPeriod>
 </dosage>
</MedicationStatement>

JSON Template

{doco
  "resourceType" : "MedicationStatement",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Identifier
  "patient" : { Reference(Patient) }, // R!  Who was/is taking medication
  "informationSource" : { Reference(Patient|Practitioner|RelatedPerson) }, // 
  "dateAsserted" : "<dateTime>", // When the statement was asserted?
  "status" : "<code>", // R!  active | completed | entered-in-error | intended
  "wasNotTaken" : <boolean>, // True if medication is/was not being taken
  "reasonNotTaken" : [{ CodeableConcept }], // C? True if asserting medication was not given
  // reasonForUse[x]: . One of these 2:
  "reasonForUseCodeableConcept" : { CodeableConcept },
  "reasonForUseReference" : { Reference(Condition) },
  // effective[x]: Over what period was medication consumed?. One of these 2:
  "effectiveDateTime" : "<dateTime>",
  "effectivePeriod" : { Period },
  "note" : "<string>", // Further information about the statement
  "supportingInformation" : [{ Reference(Any) }], // Additional supporting information
  // medication[x]: What medication was taken?. One of these 2:
  "medicationCodeableConcept" : { CodeableConcept },
  "medicationReference" : { Reference(Medication) },
  "dosage" : [{ // Details of how medication was taken
    "text" : "<string>", // Reported dosage information
    "timing" : { Timing }, // When/how often was medication taken?
    // asNeeded[x]: Take "as needed" f(or x). One of these 2:
    "asNeededBoolean" : <boolean>,
    "asNeededCodeableConcept" : { CodeableConcept },
    // site[x]: Where on body was medication administered?. One of these 2:
    "siteCodeableConcept" : { CodeableConcept },
    "siteReference" : { Reference(BodySite) },
    "route" : { CodeableConcept }, // How did the medication enter the body?
    "method" : { CodeableConcept }, // Technique used to administer medication
    // quantity[x]: Amount administered in one dose. One of these 2:
    "quantityQuantity" : { Quantity(SimpleQuantity) },
    "quantityRange" : { Range },
    // rate[x]: Dose quantity per unit of time. One of these 2:
    "rateRatio" : { Ratio },
    "rateRange" : { Range },
    "maxDosePerPeriod" : { Ratio } // Maximum dose that was consumed per unit of time
  }]
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationStatement Σ IDomainResourceRecord of medication being taken by a patient
Reason for use is only permitted if wasNotTaken is false
Reason not taken is only permitted if wasNotTaken is true
... identifier Σ0..*IdentifierExternal Identifier
... patient Σ1..1Reference(Patient)Who was/is taking medication
... informationSource Σ0..1Reference(Patient | Practitioner | RelatedPerson)
... dateAsserted Σ0..1dateTimeWhen the statement was asserted?
... status ?! Σ1..1codeactive | completed | entered-in-error | intended
MedicationStatementStatus (Required)
... wasNotTaken ?! Σ0..1booleanTrue if medication is/was not being taken
... reasonNotTaken Σ I0..*CodeableConceptTrue if asserting medication was not given
Reason Medication Not Given Codes (Example)
... reasonForUse[x] Σ0..1
.... reasonForUseCodeableConceptCodeableConcept
.... reasonForUseReferenceReference(Condition)
... effective[x] Σ0..1Over what period was medication consumed?
.... effectiveDateTimedateTime
.... effectivePeriodPeriod
... note Σ0..1stringFurther information about the statement
... supportingInformation Σ0..*Reference(Any)Additional supporting information
... medication[x] Σ1..1What medication was taken?
.... medicationCodeableConceptCodeableConcept
.... medicationReferenceReference(Medication)
... dosage Σ0..*BackboneElementDetails of how medication was taken
.... text Σ0..1stringReported dosage information
.... timing Σ0..1TimingWhen/how often was medication taken?
.... asNeeded[x] Σ0..1Take "as needed" f(or x)
..... asNeededBooleanboolean
..... asNeededCodeableConceptCodeableConcept
.... site[x] Σ0..1Where on body was medication administered?
SNOMED CT Anatomical Structure for Administration Site Codes (Example)
..... siteCodeableConceptCodeableConcept
..... siteReferenceReference(BodySite)
.... route Σ0..1CodeableConceptHow did the medication enter the body?
SNOMED CT Route Codes (Example)
.... method Σ0..1CodeableConceptTechnique used to administer medication
.... quantity[x] Σ0..1Amount administered in one dose
..... quantityQuantitySimpleQuantity
..... quantityRangeRange
.... rate[x] Σ0..1Dose quantity per unit of time
..... rateRatioRatio
..... rateRangeRange
.... maxDosePerPeriod Σ0..1RatioMaximum dose that was consumed per unit of time

doco Documentation for this format

UML Diagram

MedicationStatement (DomainResource)External identifier - FHIR will generate its own internal IDs (probably URLs) which do not need to be explicitly managed by the resource. The identifier here is one that would be used by another non-FHIR system - for example an automated medication pump would provide a record each time it operated; an administration while the patient was off the ward might be made with a different system and entered after the event. Particularly important if these records have to be updatedidentifier : Identifier [0..*]The person or animal who is /was taking the medicationpatient : Reference [1..1] « Patient »The person who provided the information about the taking of this medicationinformationSource : Reference [0..1] « Patient|Practitioner| RelatedPerson »The date when the medication statement was asserted by the information sourcedateAsserted : dateTime [0..1]A code representing the patient or other source’s judgment about the state of 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] « A set of codes indicating the current status of a MedicationStatement (Strength=Required)MedicationStatementStatus! »Set this to true if the record is saying that the medication was NOT taken (this element modifies the meaning of other elements)wasNotTaken : boolean [0..1]A code indicating why the medication was not takenreasonNotTaken : CodeableConcept [0..*] « A set of codes indicating the reason why the MedicationAdministration is negated (Strength=Example)Reason Medication Not Given ?? »A reason for why the medication is being/was takenreasonForUse[x] : Type [0..1] « CodeableConcept|Reference(Condition) »The interval of time during which it is being asserted that the patient was taking the medication (or was not taking, when the 'wasNotGiven' attribute is true)effective[x] : Type [0..1] « dateTime|Period »Provides extra information about the medication statement that is not conveyed by the other attributesnote : string [0..1]Allows linking the MedicationStatement to the underlying MedicationOrder, or to other information that supports the MedicationStatementsupportingInformation : Reference [0..*] « Any »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 medicationsmedication[x] : Type [1..1] « CodeableConcept|Reference(Medication) »DosageFree text dosage information as reported about a patient's medication use. When coded dosage information is present, the free text may still be present for display to humanstext : string [0..1]The timing schedule for giving the medication to the patient. The Schedule data type allows many different expressions, for example. "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013"timing : Timing [0..1]Indicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option), or it indicates the precondition for taking the Medication (CodeableConcept). Specifically if 'boolean' datatype is selected, then the following logic applies: If set to True, this indicates that the medication is only taken when needed, within the specified scheduleasNeeded[x] : Type [0..1] « boolean|CodeableConcept »A coded specification of or a reference to the anatomic site where the medication first enters the bodysite[x] : Type [0..1] « CodeableConcept|Reference(BodySite); A coded concept describing the site location the medicine enters into or onto the body (Strength=Example)SNOMED CT Anatomical Structur...?? »A code specifying the route or physiological path of administration of a therapeutic agent into or onto a subjectroute : CodeableConcept [0..1] « A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject (Strength=Example)SNOMED CT Route ?? »A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. Examples: Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequentlymethod : CodeableConcept [0..1]The amount of therapeutic or other substance given at one administration eventquantity[x] : Type [0..1] « Quantity(SimpleQuantity)|Range »Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Currently we do not specify a default of '1' in the denominator, but this is being discussed. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hoursrate[x] : Type [0..1] « Ratio|Range »The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. E.g. 1000mg in 24 hoursmaxDosePerPeriod : Ratio [0..1]Indicates how the medication is/was used by the patientdosage[0..*]

XML Template

<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>
 <patient><!-- 1..1 Reference(Patient) Who was/is taking medication --></patient>
 <informationSource><!-- 0..1 Reference(Patient|Practitioner|RelatedPerson)  --></informationSource>
 <dateAsserted value="[dateTime]"/><!-- 0..1 When the statement was asserted? -->
 <status value="[code]"/><!-- 1..1 active | completed | entered-in-error | intended -->
 <wasNotTaken value="[boolean]"/><!-- 0..1 True if medication is/was not being taken -->
 <reasonNotTaken><!-- ?? 0..* CodeableConcept True if asserting medication was not given --></reasonNotTaken>
 <reasonForUse[x]><!-- 0..1 CodeableConcept|Reference(Condition)  --></reasonForUse[x]>
 <effective[x]><!-- 0..1 dateTime|Period Over what period was medication consumed? --></effective[x]>
 <note value="[string]"/><!-- 0..1 Further information about the statement -->
 <supportingInformation><!-- 0..* Reference(Any) Additional supporting information --></supportingInformation>
 <medication[x]><!-- 1..1 CodeableConcept|Reference(Medication) What medication was taken? --></medication[x]>
 <dosage>  <!-- 0..* Details of how medication was taken -->
  <text value="[string]"/><!-- 0..1 Reported dosage information -->
  <timing><!-- 0..1 Timing When/how often was medication taken? --></timing>
  <asNeeded[x]><!-- 0..1 boolean|CodeableConcept Take "as needed" f(or x) --></asNeeded[x]>
  <site[x]><!-- 0..1 CodeableConcept|Reference(BodySite) Where on body was medication administered? --></site[x]>
  <route><!-- 0..1 CodeableConcept How did the medication enter the body? --></route>
  <method><!-- 0..1 CodeableConcept Technique used to administer medication --></method>
  <quantity[x]><!-- 0..1 Quantity(SimpleQuantity)|Range Amount administered in one dose --></quantity[x]>
  <rate[x]><!-- 0..1 Ratio|Range Dose quantity per unit of time --></rate[x]>
  <maxDosePerPeriod><!-- 0..1 Ratio Maximum dose that was consumed per unit of time --></maxDosePerPeriod>
 </dosage>
</MedicationStatement>

JSON Template

{doco
  "resourceType" : "MedicationStatement",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Identifier
  "patient" : { Reference(Patient) }, // R!  Who was/is taking medication
  "informationSource" : { Reference(Patient|Practitioner|RelatedPerson) }, // 
  "dateAsserted" : "<dateTime>", // When the statement was asserted?
  "status" : "<code>", // R!  active | completed | entered-in-error | intended
  "wasNotTaken" : <boolean>, // True if medication is/was not being taken
  "reasonNotTaken" : [{ CodeableConcept }], // C? True if asserting medication was not given
  // reasonForUse[x]: . One of these 2:
  "reasonForUseCodeableConcept" : { CodeableConcept },
  "reasonForUseReference" : { Reference(Condition) },
  // effective[x]: Over what period was medication consumed?. One of these 2:
  "effectiveDateTime" : "<dateTime>",
  "effectivePeriod" : { Period },
  "note" : "<string>", // Further information about the statement
  "supportingInformation" : [{ Reference(Any) }], // Additional supporting information
  // medication[x]: What medication was taken?. One of these 2:
  "medicationCodeableConcept" : { CodeableConcept },
  "medicationReference" : { Reference(Medication) },
  "dosage" : [{ // Details of how medication was taken
    "text" : "<string>", // Reported dosage information
    "timing" : { Timing }, // When/how often was medication taken?
    // asNeeded[x]: Take "as needed" f(or x). One of these 2:
    "asNeededBoolean" : <boolean>,
    "asNeededCodeableConcept" : { CodeableConcept },
    // site[x]: Where on body was medication administered?. One of these 2:
    "siteCodeableConcept" : { CodeableConcept },
    "siteReference" : { Reference(BodySite) },
    "route" : { CodeableConcept }, // How did the medication enter the body?
    "method" : { CodeableConcept }, // Technique used to administer medication
    // quantity[x]: Amount administered in one dose. One of these 2:
    "quantityQuantity" : { Quantity(SimpleQuantity) },
    "quantityRange" : { Range },
    // rate[x]: Dose quantity per unit of time. One of these 2:
    "rateRatio" : { Ratio },
    "rateRange" : { Range },
    "maxDosePerPeriod" : { Ratio } // Maximum dose that was consumed per unit of time
  }]
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

4.16.3.1 Terminology Bindings

PathDefinitionTypeReference
MedicationStatement.status A set of codes indicating the current status of a MedicationStatementRequiredMedicationStatementStatus
MedicationStatement.reasonNotTaken A set of codes indicating the reason why the MedicationAdministration is negatedExampleReason Medication Not Given Codes
MedicationStatement.dosage.asNeeded[x] A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.UnknownNo details provided yet
MedicationStatement.dosage.site[x] A coded concept describing the site location the medicine enters into or onto the bodyExampleSNOMED CT Anatomical Structure for Administration Site Codes
MedicationStatement.dosage.route A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subjectExampleSNOMED CT Route Codes
MedicationStatement.dosage.method A coded concept describing the technique by which the medicine is administeredUnknownNo details provided yet

4.16.3.2 Constraints

  • mst-1: Reason not taken is only permitted if wasNotTaken is true (xpath: not(exists(f:reasonNotTaken) and f:wasNotTaken/@value='false'))
  • mst-2: Reason for use is only permitted if wasNotTaken is false (xpath: not(exists(*[starts-with(local-name(.), 'reasonForUse')]) and f:wasNotTaken/@value='true'))

4.16.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
codetokenReturn administrations of this medication codeMedicationStatement.medicationCodeableConcept
effectivedatedateDate when patient was taking (or not taking) the medicationMedicationStatement.effective[x]
identifiertokenReturn statements with this external identityMedicationStatement.identifier
medicationreferenceReturn administrations of this medication referenceMedicationStatement.medicationReference
(Medication)
patientreferenceThe identity of a patient to list statements forMedicationStatement.patient
(Patient)
sourcereferenceWho the information in the statement came fromMedicationStatement.informationSource
(Patient, Practitioner, RelatedPerson)
statustokenReturn statements that match the given statusMedicationStatement.status