Identifiers associated with this Medication Usage 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.

A code representing the status of recording the medication usage.

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

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

A coded concept indicating the current status of a MedicationUsage.

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

A coded concept identifying where the medication included in the MedicationUsage is expected to be consumed or administered.

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.

A coded concept identifying the substance or product being taken.

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

The encounter that establishes the context for this MedicationUsage.

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

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

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

Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationUsage comes from creating a MedicationUsage 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 MedicationUsage from.

A concept, Condition or observation that supports 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.

A coded concept identifying why the medication is being taken.

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

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.

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

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

The dates included in the dosage on a Medication Usage 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 Usage is derived from a MedicationRequest.

Type of the adherence for the medication.

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

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