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) Medication Administration Profile vs QICore-MedicationAdministration

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
MedicationAdministration.dosage.methodNo left Value set at MedicationAdministration.dosage.method
Notes about differences (e.g. definitions)
MedicationAdministrationElements differ in definition for definition:
"Profile of MedicationAdministration for clinical quality rules and measures."
"Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner."
MedicationAdministration.dosage.routeExample/preferred bindings differ at MedicationAdministration.dosage.route using binding from U.S. Data Access Framework (DAF) Medication Administration Profile
MedicationAdministration.dosage.routeElements differ in definition for binding.description:
"This identifies the route of substance administration."
"A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject"

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
.. MedicationAdministration ∑0..*MedicationAdministrationAdministration of medication to a patient
... 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
... status ?! S∑1..1codein-progress | on-hold | completed | entered-in-error | stopped
Binding: MedicationAdministrationStatus (required)
... patient S ∑1..1Reference(DAF-Patient)Who received medication?
... practitioner S ∑0..1Reference(U.S. Data Access Framework (DAF) Practitioner Profile)Who administered substance?
... encounter S ∑0..1Reference(U.S. Data Access Framework (DAF) Encounter profile)Encounter administered as part of
... prescription S ∑0..1Reference(U.S. Data Access Framework (DAF) MedicationOrder Profile)Order administration performed against
... wasNotGiven ?! S∑0..1booleanTrue if medication not administered
... reasonNotGiven S ∑I0..1CodeableConceptReason administration not performed
Binding: Reason Medication Not Given Codes (example)
mad-2: Reason not given is only permitted if wasNotGiven is true
... reasonGiven S ∑I0..*CodeableConceptReason administration performed
Binding: Reason Medication Given Codes (example)
mad-3: Reason given is only permitted if wasNotGiven is false
... effectiveTime[x] S ∑1..1dateTime, PeriodStart and end time of administration
... medication[x] S ∑1..1QICore-Medication, Reference(QICore-Medication)What was administered?
Binding: Medication Clinical Drug (RxNorm) (preferred)
... device S ∑0..*Reference(QICore-Device)Device used to administer
... note ∑0..1stringInformation about the administration
... dosage S ∑I0..1BackboneElementDetails of how medication was taken
mad-1: SHALL have at least one of dosage.quantity and dosage.rate
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text ∑0..1stringDosage Instructions
.... site[x] ∑0..1BodySite, Reference(BodySite)Body site administered to
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S ∑0..1CodeableConceptPath of substance into body
Binding: Medication Route FDA Value Set (preferred)
.... method S ∑0..1CodeableConceptHow drug was administered
Binding: (unbound) (required)
.... quantity S ∑0..1SimpleQuantityAmount administered in one dose
.... rate[x] ∑0..1Ratio, RangeDose quantity 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
.. MedicationAdministration ∑0..*MedicationAdministrationAdministration of medication to a patient
... 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
... status ?! S∑1..1codein-progress | on-hold | completed | entered-in-error | stopped
Binding: MedicationAdministrationStatus (required)
... patient S ∑1..1Reference(#1)Who received medication?
... practitioner S ∑0..1Reference(#3 | QICore-Patient | QICore-RelatedPerson)Who administered substance?
... encounter S ∑0..1Reference(#4)Encounter administered as part of
... prescription S ∑0..1Reference(#16)Order administration performed against
... wasNotGiven ?! S∑0..1booleanTrue if medication not administered
... reasonNotGiven S ∑I0..*CodeableConceptReason administration not performed
Binding: Reason Medication Not Given Codes (example)
mad-2: Reason not given is only permitted if wasNotGiven is true
... reasonGiven S ∑I0..*CodeableConceptReason administration performed
Binding: Reason Medication Given Codes (example)
mad-3: Reason given is only permitted if wasNotGiven is false
... effectiveTime[x] S ∑1..1dateTime, PeriodStart and end time of administration
... medication[x] S ∑1..1CodeableConcept, Reference(Medication)What was administered?
Binding: Medication Clinical Drug (RxNorm) (example)
... device S ∑0..*Reference(Device)Device used to administer
... note ∑0..1stringInformation about the administration
... dosage S ∑I0..*BackboneElementDetails of how medication was taken
mad-1: SHALL have at least one of dosage.quantity and dosage.rate
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text ∑0..1stringDosage Instructions
.... site[x] ∑0..1CodeableConcept, Reference(BodySite)Body site administered to
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S ∑0..1CodeableConceptPath of substance into body
Binding: ???? (preferred)
.... method S ∑0..1CodeableConceptHow drug was administered
Binding: (unbound) (required)
.... quantity S ∑0..1SimpleQuantityAmount administered in one dose
.... rate[x] ∑0..1Ratio, RangeDose quantity per unit of time

doco Documentation for this format