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) MedicationOrder Profile vs QICore-MedicationOrder

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
MedicationOrder.dosageInstruction.asNeeded[x]No left Value set at MedicationOrder.dosageInstruction.asNeeded[x]
MedicationOrder.dosageInstruction.methodNo left Value set at MedicationOrder.dosageInstruction.method
Notes about differences (e.g. definitions)
MedicationOrderElements differ in definition for definition:
"An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationOrder" rather than "MedicationPrescription" to generalize the use across inpatient and outpatient settings as well as for care plans, etc."
"Profile of medication prescription, indicating which elements must be supported in rule and measure interpreters."

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
.. MedicationOrder 0..*MedicationOrderPrescription of medication to for 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
... dateWritten S 0..1dateTimeWhen prescription was authorized
... status ?! S0..1codeactive | on-hold | completed | entered-in-error | stopped | draft
Binding: MedicationOrderStatus (required)
... dateEnded 0..1dateTimeWhen prescription was stopped
... reasonEnded 0..1CodeableConceptWhy prescription was stopped
... patient S 1..1Reference(DAF-Patient)Who prescription is for
... prescriber S 0..1Reference(U.S. Data Access Framework (DAF) Practitioner Profile)Who ordered the medication(s)
... encounter S 0..1Reference(U.S. Data Access Framework (DAF) Encounter profile)Created during encounter / admission / stay
... reason[x] 0..1Condition, Reference(Condition)Reason or indication for writing the prescription
Binding: Problem Value Set (preferred)
... note 0..1stringInformation about the prescription
... medication[x] S 1..1QICore-Medication, Reference(QICore-Medication)Medication to be taken
... dosageInstruction S 0..1BackboneElementHow medication should be taken
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text S 0..1stringDosage instructions expressed as text
.... additionalInstructions 0..1CodeableConceptSupplemental instructions - e.g. "with meals"
.... timing 0..1TimingWhen medication should be administered
.... asNeeded[x] S 0..1boolean, CodeableConceptTake "as needed" (for x)
Binding: (unbound) (required)
.... site[x] 0..1BodySite, Reference(BodySite)Body site to administer to
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S 0..1CodeableConceptHow drug should enter body
Binding: SNOMED CT Route Codes (example)
.... method S 0..1CodeableConceptTechnique for administering medication
Binding: (unbound) (required)
.... dose[x] S 0..1SimpleQuantity, SimpleQuantityAmount of medication per dose
.... rate[x] 0..1Ratio, RangeAmount of medication per unit of time
.... maxDosePerPeriod 0..1RatioUpper limit on medication per unit of time
... dispenseRequest 0..1BackboneElementMedication supply authorization
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... medication[x] 0..1Medication, Reference(Medication)Product to be supplied
.... validityPeriod 0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed 0..1positiveInt# of refills authorized
.... quantity 0..1SimpleQuantityAmount of medication to supply per dispense
.... expectedSupplyDuration 0..1DurationDays supply per dispense
... substitution 0..1BackboneElementAny restrictions on medication substitution?
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... type 1..1CodeableConceptgeneric | formulary +
Binding: ActSubstanceAdminSubstitutionCode (example)
.... reason 0..1CodeableConceptWhy should substitution (not) be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription 0..1Reference(MedicationOrder)An order/prescription that this supersedes

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
.. MedicationOrder 0..*MedicationOrderPrescription of medication to for 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
... dateWritten S 0..1dateTimeWhen prescription was authorized
... status ?! S0..1codeactive | on-hold | completed | entered-in-error | stopped | draft
Binding: MedicationOrderStatus (required)
... dateEnded 0..1dateTimeWhen prescription was stopped
... reasonEnded 0..1CodeableConceptWhy prescription was stopped
... patient S 0..1Reference(#1)Who prescription is for
... prescriber S 0..*Reference(#3)Who ordered the medication(s)
... encounter S 0..*Reference(#4)Created during encounter / admission / stay
... reason[x] 0..1CodeableConcept, Reference(Condition)Reason or indication for writing the prescription
Binding: Problem Value Set (example)
... note 0..1stringInformation about the prescription
... medication[x] S 1..1CodeableConcept, Reference(Medication)Medication to be taken
... dosageInstruction S 0..*BackboneElementHow medication should be taken
.... pharmacy-core-doseType 0..1CodeableConceptExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-doseType
Binding: SNOMED CT Dosages Codes (preferred)
.... pharmacy-core-infuseOver 0..1DurationExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-infuseOver
.... pharmacy-core-maxDeliveryRate 0..1RatioExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-maxDeliveryRate
.... pharmacy-core-maxDeliveryVolume 0..1QuantityExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-maxDeliveryVolume
.... pharmacy-core-minDosePerPeriod 0..1RatioExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-minDosePerPeriod
.... pharmacy-core-rateGoal 0..1RatioExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-rateGoal
.... pharmacy-core-rateIncrement 0..1RatioExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-rateIncrement
.... pharmacy-core-rateIncrementInterval 0..1DurationExtension
URL: http://hl7.org/fhir/StructureDefinition/pharmacy-core-rateIncrementInterval
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... text S 0..1stringDosage instructions expressed as text
.... additionalInstructions 0..1CodeableConceptSupplemental instructions - e.g. "with meals"
.... timing 0..1TimingWhen medication should be administered
.... asNeeded[x] S 0..1boolean, CodeableConceptTake "as needed" (for x)
Binding: (unbound) (required)
.... site[x] 0..1CodeableConcept, Reference(BodySite)Body site to administer to
Binding: SNOMED CT Anatomical Structure for Administration Site Codes (example)
.... route S 0..1CodeableConceptHow drug should enter body
Binding: SNOMED CT Route Codes (example)
.... method S 0..1CodeableConceptTechnique for administering medication
Binding: (unbound) (required)
.... dose[x] S 0..1Range, SimpleQuantityAmount of medication per dose
.... rate[x] 0..1Ratio, RangeAmount of medication per unit of time
.... maxDosePerPeriod 0..1RatioUpper limit on medication per unit of time
... dispenseRequest 0..1BackboneElementMedication supply authorization
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... medication[x] 0..1CodeableConcept, Reference(Medication)Product to be supplied
.... validityPeriod 0..1PeriodTime period supply is authorized for
.... numberOfRepeatsAllowed 0..1positiveInt# of refills authorized
.... quantity 0..1SimpleQuantityAmount of medication to supply per dispense
.... expectedSupplyDuration 0..1DurationDays supply per dispense
... substitution 0..1BackboneElementAny restrictions on medication substitution?
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... type 1..1CodeableConceptgeneric | formulary +
Binding: ActSubstanceAdminSubstitutionCode (example)
.... reason 0..1CodeableConceptWhy should substitution (not) be made
Binding: SubstanceAdminSubstitutionReason (example)
... priorPrescription 0..1Reference(MedicationOrder)An order/prescription that this supersedes

doco Documentation for this format