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

U.S. Data Access Framework (DAF) MedicationStatement Profile vs QICore-MedicationStatement

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
MedicationStatement.dosage.asNeeded[x]No left Value set at MedicationStatement.dosage.asNeeded[x]
MedicationStatement.dosage.methodNo left Value set at MedicationStatement.dosage.method
Notes about differences (e.g. definitions)
MedicationStatementElements differ in definition for definition:
"Statement that a medication is/was actively taken by a patient."
"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."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationStatement ∑ I0..*MedicationStatementRecord of medication being taken by a patient
mst-2: Reason for use is only permitted if wasNotTaken is false
mst-1: Reason not taken is only permitted if wasNotTaken is true
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierExternal Identifier
... patient S ∑1..1Reference(DAF-Patient)Who was/is taking medication
... informationSource S ∑0..1Reference(U.S. Data Access Framework (DAF) Practitioner Profile | DAF-Patient | U.S. DAF Related Person Profile)
... dateAsserted S ∑0..1dateTimeWhen the statement was asserted?
... status ?! S∑1..1codeactive | completed | entered-in-error | intended
Binding: MedicationStatementStatus (required)
... wasNotTaken ?! S∑0..1booleanTrue if medication is/was not being taken
... reasonNotTaken ∑0..*CodeableConceptTrue if asserting medication was not given
Binding: Reason Medication Not Given Codes (example)
... reasonForUse[x] ∑0..1QICore-Condition, Reference(QICore-Condition)Binding: v3 Code System ActReason (preferred)
... effectivePeriod S ∑0..1PeriodOver what period was medication consumed?
... note ∑0..1stringFurther information about the statement
... supportingInformation ∑0..*Reference(Resource)Additional supporting information
... medication[x] S ∑1..1QICore-Medication, Reference(QICore-Medication)What medication was taken?
Binding: Medication Clinical Drug (RxNorm) (preferred)
... dosage S ∑0..*BackboneElementDetails of how medication was taken
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text ∑0..1stringReported dosage information
.... timing S ∑0..1TimingWhen/how often was medication taken?
.... asNeeded[x] S ∑0..1boolean, CodeableConceptTake "as needed" f(or x)
Binding: (unbound) (required)
.... site[x] ∑0..1BodySite, Reference(BodySite)Where on body was medication administered?
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S ∑0..1CodeableConceptHow did the medication enter the body?
Binding: SNOMED CT Route Codes (example)
.... method S ∑0..1CodeableConceptTechnique used to administer medication
Binding: (unbound) (required)
.... quantity[x] ∑0..1SimpleQuantity, SimpleQuantityAmount administered in one dose
.... rate[x] ∑0..1Ratio, RangeDose quantity per unit of time
.... maxDosePerPeriod S ∑0..1RatioMaximum dose that was consumed per unit of time

doco Documentation for this format

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationStatement ∑ I0..*MedicationStatementRecord of medication being taken by a patient
mst-2: Reason for use is only permitted if wasNotTaken is false
mst-1: Reason not taken is only permitted if wasNotTaken is true
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional Content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierExternal Identifier
... patient S ∑1..1Reference(#1)Who was/is taking medication
... informationSource S ∑0..1Reference(#3 | #1 | #5)
... dateAsserted S ∑0..1dateTimeWhen the statement was asserted?
... status ?! S∑1..1codeactive | completed | entered-in-error | intended
Binding: MedicationStatementStatus (required)
... wasNotTaken ?! S∑0..1booleanTrue if medication is/was not being taken
... reasonNotTaken ∑0..*CodeableConceptTrue if asserting medication was not given
Binding: Reason Medication Not Given Codes (example)
... reasonForUse[x] ∑0..1CodeableConcept, Reference(Condition)Binding: v3 Code System ActReason (example)
... effectivePeriod S ∑0..1Period, dateTimeOver what period was medication consumed?
... note ∑0..1stringFurther information about the statement
... supportingInformation ∑0..*Reference(Resource)Additional supporting information
... medication[x] S ∑1..1CodeableConcept, Reference(Medication)What medication was taken?
Binding: Medication Clinical Drug (RxNorm) (example)
... dosage S ∑0..*BackboneElementDetails of how medication was taken
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text ∑0..1stringReported dosage information
.... timing S ∑0..1TimingWhen/how often was medication taken?
.... asNeeded[x] S ∑0..1boolean, CodeableConceptTake "as needed" f(or x)
Binding: (unbound) (required)
.... site[x] ∑0..1CodeableConcept, Reference(BodySite)Where on body was medication administered?
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S ∑0..1CodeableConceptHow did the medication enter the body?
Binding: SNOMED CT Route Codes (example)
.... method S ∑0..1CodeableConceptTechnique used to administer medication
Binding: (unbound) (required)
.... quantity[x] ∑0..1SimpleQuantity, RangeAmount administered in one dose
.... rate[x] ∑0..1Ratio, RangeDose quantity per unit of time
.... maxDosePerPeriod S ∑0..1RatioMaximum dose that was consumed per unit of time

doco Documentation for this format