2015May core #840 - MedicationAdministration.dosage.method duplication

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Low
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Pharmacy
    • MedicationAdministration
    • 4.14.7
    • Hide

      Agree. ?Clean up the definitions on all resources where dosage attributes are used.

      August 28, 2015: Update definition for MedicationAdministration.dosage.method MedicaitonOrder.dosage.method MedicationDispense.dosage.method and MedicationStatement.dosage.methdo to:

      A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. Examples: Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequently.

      Show
      Agree. ?Clean up the definitions on all resources where dosage attributes are used. August 28, 2015: Update definition for MedicationAdministration.dosage.method MedicaitonOrder.dosage.method MedicationDispense.dosage.method and MedicationStatement.dosage.methdo to: A coded value indicating the method by which the medication is intended to be or was introduced into or on the body. This attribute will most often NOT be populated. It is most commonly used for injections. Examples: Slow Push, Deep IV. One of the reasons this attribute is not used often, is that the method is often pre-coordinated with the route and/or form of administration. This means the codes used in route or form may pre-coordinate the method in the route code or the form code. The implementation decision about what coding system to use for route or form code will determine how frequently the method code will be populated e.g. if route or form code pre-coordinate method code, then this attribute will not be populated often; if there is no pre-coordination then method code may be used frequently.
    • Marla/Melva: 2-0-1
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Terminologies used often pre-coordinate this term with the route and or form of administration

      Comment:

      well, ok, that's true. But what does it mean? Would you also use route, site, form in this case, or would you not? There should be a little more discussion in order to set expectations (my recommendation: no duplication - see similar notes on Observation.code vs Observation.bodySite)

            Assignee:
            Unassigned
            Reporter:
            Grahame Grieve (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: