Inconsistencies in MedicationAdministration, Statement and Immunization - 2016-09 core #172

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Pharmacy
    • Immunization
      MedicationAdministration
      MedicationStatement
    • 11.3 & 11.5 & 11.6
    • Hide

      Pharmacy reviewed with PHER the issues raised in this tracker item on Sept 20, 2016. We reached agreement to align names for wasNotGiven, reasonNotGiven and reasonGiven. In addition we also reviewed the Search parameter names and will update those to keep them in synch. PHER will update their Immunization resource to align with reasonNotGiven, wasNotGiven and reasonGiven. They have also agreed to remove the Explanation portion of their model and move those attribute into the main resource.

      1. Pharmacy will continue to evaluate the harmonization between Medication Administration and Medication Statement - reasonnotgiven/taken - Sept 22: Will change "wasNotGiven" on MedicationAdministration to "notGiven" and will leave names on MedicationStatement as is. Considered a more generic term of "used" but it does not fit in the context of immunization or administration. From a business perspective, believe the existing terms are appropriate.

      2. Clean up names of search parameters to meet QA requirements - (e.g. not-given)

      3. Will add reason-given and reason-not-given as search parameters to medicationAdministration.

      Show
      Pharmacy reviewed with PHER the issues raised in this tracker item on Sept 20, 2016. We reached agreement to align names for wasNotGiven, reasonNotGiven and reasonGiven. In addition we also reviewed the Search parameter names and will update those to keep them in synch. PHER will update their Immunization resource to align with reasonNotGiven, wasNotGiven and reasonGiven. They have also agreed to remove the Explanation portion of their model and move those attribute into the main resource. 1. Pharmacy will continue to evaluate the harmonization between Medication Administration and Medication Statement - reasonnotgiven/taken - Sept 22: Will change "wasNotGiven" on MedicationAdministration to "notGiven" and will leave names on MedicationStatement as is. Considered a more generic term of "used" but it does not fit in the context of immunization or administration. From a business perspective, believe the existing terms are appropriate. 2. Clean up names of search parameters to meet QA requirements - (e.g. not-given) 3. Will add reason-given and reason-not-given as search parameters to medicationAdministration.
    • Jenni/Yunwei: 7-0-0
    • Clarification
    • Compatible, substantive
    • DSTU2

      Comment:

      There are a few unnecessary inconsistencies between MedicationAdministration (MA), MedicationStatement (MS), and Immunization (I).

      • MA.wasNotGiven vs. I.notTaken vs. MS.wasNotGiven: Consider dropping "was" from MA and MS "wasNotGiven" or adding "was" to I "notGiven".
      • I has "notgiven" as a search parameter, but MA has "wasnotgiven". These are both inconsistent with parameter naming conventions (they should be "not-given" or "was-not-given") – and they are inconsistent with each other.
      • I has an "explanation" component that contains "reason" and "reasonNotGiven"; MS has top-level "reasonNotTaken", "reasonForUseCode", and "reasonForUseReference" attributes; and MA has top-level "reasonNotGiven" and "reasonGiven" attributes. Again, there is opportunity for improved consistency here. In addition, if MS wants multiple reasonForUse types, why is it not represented as a reasonForUse[x] (or reasonTaken[x] to be more consistent with verb in "notTaken")?

      Summary:

      Inconsistencies in MedicationAdministration, Statement and Immunization

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: