MedicationStatement

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

Properties

Name	Required	Type	Description
identifier		Identifier[]	External identifier Details 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. This is a business identifier, not a resource identifier.
basedOn		Reference< MedicationRequest | CarePlan | ServiceRequest >[]	Fulfils plan, proposal or order Details A plan, proposal or order that is fulfilled in whole or in part by this event.
partOf		Reference< MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Observation >[]	Part of referenced event Details A larger event of which this particular event is a component or step.
status	✓	code	active | completed | entered-in-error | intended | stopped | on-hold | unknown | not-taken Details 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. MedicationStatement is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for MedicationStatement.status contains codes that assert the status of the use of the medication by the patient (for example, stopped or on hold) as well as codes that assert the status of the medication statement itself (for example, entered in error). This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
statusReason		CodeableConcept[]	Reason for current status Details Captures the reason for the current state of the MedicationStatement. This is generally only used for "exception" statuses such as "not-taken", "on-hold", "cancelled" or "entered-in-error". The reason for performing the event at all is captured in reasonCode, not here.
category		CodeableConcept	Type of medication usage Details Indicates where the medication is expected to be consumed or administered.
medication[x]	✓	CodeableConcept, Reference<Medication>	What medication was taken Details 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. 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.
subject	✓	Reference<Patient | Group>	Who is/was taking the medication Details The person, animal or group who is/was taking the medication.
context		Reference<Encounter | EpisodeOfCare>	Encounter / Episode associated with MedicationStatement Details The encounter or episode of care that establishes the context for this MedicationStatement.
effective[x]		dateTime, Period	The date/time or interval when the medication is/was/will be taken Details 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 element is No). 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 at the time the statement is recorded, the "end" date will be omitted. 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.
dateAsserted		dateTime	When the statement was asserted? Details The date when the medication statement was asserted by the information source.
informationSource		Reference< Patient | Practitioner | PractitionerRole | RelatedPerson | Organization >	Person or organization that provided the information about the taking of this medication Details 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.
derivedFrom		Reference<Resource>[]	Additional supporting information Details Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement. 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.
reasonCode		CodeableConcept[]	Reason for why the medication is being/was taken Details A reason for why the medication is being/was taken. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference.
reasonReference		Reference< Condition | Observation | DiagnosticReport >[]	Condition or observation that supports why the medication is being/was taken Details Condition or observation that supports why the medication is being/was taken. This is a reference to a condition that is the reason why the medication is being/was taken. If only a code exists, use reasonForUseCode.
note		Annotation[]	Further information about the statement Details Provides extra information about the medication statement that is not conveyed by the other attributes.
dosage		Dosage[]	Details of how medication is/was taken or should be taken Details Indicates how the medication is/was or should be taken by the patient. 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.

Search Parameters

Name	Type	Description	Expression
code	token	Return statements of this medication code	MedicationStatement.medication
identifier	token	Return statements with this external identifier	MedicationStatement.identifier
patient	reference	Returns statements for a specific patient.	MedicationStatement.subject
medication	reference	Return statements of this medication reference	MedicationStatement.medication
status	token	Return statements that match the given status	MedicationStatement.status
category	token	Returns statements of this category of medicationstatement	MedicationStatement.category
context	reference	Returns statements for a specific context (episode or episode of Care).	MedicationStatement.context
effective	date	Date when patient was taking (or not taking) the medication	MedicationStatement.effective
part-of	reference	Returns statements that are part of another event.	MedicationStatement.partOf
source	reference	Who or where the information in the statement came from	MedicationStatement.informationSource
subject	reference	The identity of a patient, animal or group to list statements for	MedicationStatement.subject

Inherited Properties

Name	Required	Type	Description
id		string	Logical id of this artifact Details The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
meta		Meta	Metadata about the resource Details The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicitRules		uri	A set of rules under which this content was created Details A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
language		code	Language of the resource content Details The base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
text		Narrative	Text summary of the resource, for human interpretation Details A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
contained		Resource[]	Contained, inline Resources Details These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
extension		Extension[]	Additional content defined by implementations Details May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
modifierExtension		Extension[]	Extensions that cannot be ignored Details May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.