This page is part of the Data Access Framework (v1.6.0: STU 2 Ballot 1) based on FHIR v1.6.0. . For a full list of available versions, see the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON

D.4.1 StructureDefinition: DAF-core-medicationstatement

Both the MedicationOrder and MedicationStatement resources can be used to record a patient’s medication. For more information about the context for their usages, refer to the medication domains’s boundaries section. This profile sets minimum expectations for the MedicationStatement resource to record, search and fetch medications associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.

Example Usage Scenarios:

The following are example usage scenarios for the DAF-MedicationStatement profile:

• Query for active medications being taken by a patient
• Query for all patients who are taking a particular medication
• Query for all patients who are/were taking a particular medication within a particular time period

Mandatory Data Elements and Terminology

The following data-elements are mandatory (i.e data MUST be present). These are presented below in a simple human-readable explanation. Profile specific guidance and an example are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each MedicationStatement must have:

1. a status
2. a medication
3. a patient
4. a date or date range

Profile specific implementation guidance:

• The MedicationStatement and MedicationOrder resources can represent a medication, using either a code or refer to a Medication resource. The server application can choose one way or both methods, but the client application must support both methods. More specific guidance is provided in the conformance resource for this profile

Example: MedicationStatement Example: example

D.4.1.1 Formal Views of Profile Content

The official URL for this profile is:

http://hl7.org/fhir/us/daf/StructureDefinition/daf-core-medicationstatement

This profile was published on Mon Aug 01 00:00:00 AEST 2016 as a draft by Health Level Seven International (FHIR-Infrastructure).

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

Downloads: StructureDefinition: (XML, JSON), Schema: XML Schematron

 

D.4.1.2 Terminology Bindings

Terminology Bindings

Path	Name	Conformance	ValueSet
MedicationStatement.language	Common Languages	extensible	Common Languages
MedicationStatement.status	MedicationStatementStatus	required	MedicationStatementStatus
MedicationStatement.medication[x]	Medication Clinical Drug (RxNorm)	extensible	Medication Clinical Drug (RxNorm)
MedicationStatement.reasonNotTaken	?ext	example
MedicationStatement.reasonForUseCode	Condition/Problem/Diagnosis Codes	example	Condition/Problem/Diagnosis Codes
MedicationStatement.category	MedicationStatementCategory	example	MedicationStatementCategory
MedicationStatement.dosage.additionalInstructions	SNOMED CT Additional Dosage Instructions	example	SNOMED CT Additional Dosage Instructions
MedicationStatement.dosage.asNeeded[x]	SNOMED CT Medication As Needed Reason Codes	example	SNOMED CT Medication As Needed Reason Codes
MedicationStatement.dosage.site[x]	SNOMED CT Anatomical Structure for Administration Site Codes	example	SNOMED CT Anatomical Structure for Administration Site Codes
MedicationStatement.dosage.route	SNOMED CT Route Codes	example	SNOMED CT Route Codes
MedicationStatement.dosage.method	SNOMED CT Administration Method Codes	example	SNOMED CT Administration Method Codes

D.4.1.3 Constraints

Constraints

Id	Path	Details	Requirements
dom-2	MedicationStatement	If the resource is contained in another resource, it SHALL NOT contain nested Resources XPath: not(parent::f:contained and f:contained)
dom-1	MedicationStatement	If the resource is contained in another resource, it SHALL NOT contain any narrative XPath: not(parent::f:contained and f:text)
dom-4	MedicationStatement	If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated XPath: not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
dom-3	MedicationStatement	If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource XPath: not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
mst-3	MedicationStatement	Reason for use reference is only permitted if notTaken is false XPath: not(exists(*[starts-with(local-name(.), 'reasonForUseReference')]) and f:notTaken/@value=true())
mst-1	MedicationStatement	Reason not taken is only permitted if notTaken is true XPath: not(exists(f:reasonNotTaken) and f:notTaken/@value=false())
mst-2	MedicationStatement	Reason for use code is only permitted if notTaken is false XPath: not(exists(*[starts-with(local-name(.), 'reasonForUseCode')]) and f:notTaken/@value=true())

.