Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-41472

Adjust QI-Core Medication Administration Not Done must supports

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US QI Core (FHIR)
    • current
    • Clinical Quality Information
    • QICore MedicationAdministration Not Done
    • Hide

      l. See modifications suggested:

      QI-Core Profile-based path Action Include in QI-Core 6.0 Justification
      QICoreMedicationAdministration.implicitRules Keep Yes required for extension for recorded
      QICoreMedicationAdministration.extension:recorded Keep Yes Required to identify the time the decision/reason not to administer occurred
      QICoreMedicationAdministration.status Keep YES (MODIFY) To be disjoint from MedicationAdministration, the status should be FIXED VALUE = not-done. Note, the MedicationAdministration was limited to Non-Negative MedicationAdministration Status to remove not-done. The QI-Core 5.0 profile should ONLY include a fixed value here but it includes the full required MedicationAdministration Status Codes.
      QICoreMedicationAdministration.statusReason KEEP YES Extensible binding to QICore Negation Reason Codes
      QICoreMedicationAdministration.medication[x] Keep YES preferred binding to Medication Clinical Drug
      QICoreMedicationAdministration.medication[x].extension:notDoneValueSet Keep YES The medication not administered
      QICoreMedicationAdministration.context Keep YES [BRYN Review] References QICore Encounter; EpisodeOfCare. eCQMs generally identify the relationship of administration to and encounter using CQL expression timing. However, relationship to the encounter is valuable.
      QICoreMedicationAdministration.subject Keep YES Reference QICorePatient
      QICoreMedicationAdministration.effective[x] Keep Yes Need to retain since base resource includes cardinality of 1..1 even though not directly used for QDM negation rationale concept
      QICoreMedicationAdministration.request Keep YES adds ability to reference MedicationRequest that generated the administration action
      QICoreMedicationAdministration.category DO NOT ADD NO No existing use case - category is used for MedicationRequest to specify a medication order (prescription) written for dispensing and administration in the ambulatory setting. However, that is a limited use case for MedicationRequest, not for administration.
      QICoreMedicationAdministration.dosage DO NOT ADD NO This is a negation use case
      QICoreMedicationAdministratoin.dosage.route Remove NO  This is negation use case
      QICoreMedicationAdministration.dosage.dose (Simple Quantity) Remove NO  This is negation use case
      Show
      l. See modifications suggested: QI-Core Profile-based path Action Include in QI-Core 6.0 Justification QICoreMedicationAdministration. implicitRules Keep Yes required for extension for  recorded QICoreMedicationAdministration.extension: recorded Keep Yes Required to identify the time the decision/reason not to administer occurred QICoreMedicationAdministration. status Keep YES (MODIFY) To be disjoint from MedicationAdministration, the status should be FIXED VALUE = not-done . Note, the MedicationAdministration was limited to  Non-Negative MedicationAdministration Status to remove  not-done . The QI-Core 5.0 profile should ONLY include a fixed value here but it includes the full required MedicationAdministration Status Codes . QICoreMedicationAdministration. statusReason KEEP YES Extensible binding to QICore Negation Reason Codes QICoreMedicationAdministration. medication[x] Keep YES preferred binding to Medication Clinical Drug QICoreMedicationAdministration.medication [x] .extension: notDoneValueSet Keep YES The medication not administered QICoreMedicationAdministration. context Keep YES  [BRYN Review] References QICore Encounter ; EpisodeOfCare . eCQMs generally identify the relationship of administration to and encounter using CQL expression timing. However, relationship to the encounter is valuable. QICoreMedicationAdministration. subject Keep YES Reference QICorePatient QICoreMedicationAdministration. effective[x] Keep Yes Need to retain since base resource includes cardinality of 1..1 even though not directly used for QDM negation rationale concept QICoreMedicationAdministration. request Keep YES adds ability to reference MedicationRequest that generated the administration action QICoreMedicationAdministration.category DO NOT ADD NO No existing use case - category is used for MedicationRequest to specify a medication order (prescription) written for dispensing and administration in the ambulatory setting. However, that is a limited use case for MedicationRequest, not for administration. QICoreMedicationAdministration. dosage DO NOT ADD NO This is a negation use case QICoreMedicationAdministratoin.dosage. route Remove NO  This is negation use case QICoreMedicationAdministration.dosage. dose (Simple Quantity) Remove NO  This is negation use case
    • Floyd Eisenberg/Abdullah Rafiqi: 23-0-1
    • Enhancement
    • Non-compatible

    Description

      Adjust the set of Must Support elements for this profile based on the rationale in tracker FHIR-41340

      Attachments

        Activity

          People

            jen_seeman Jennifer Seeman
            karlnaden Karl Naden
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: