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

Adjust QI-Core Medication Not Requested 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 Medication Not Requested
    • Hide

      Consider the following resolution - some items require discussion.  Note that, unless the element has a MS flag in US Core 6.1.0, we should include those Keep element in the Key Elements Table for QICore but not add an MS Flag. Add (QM) to description of all Keep or Add elements such that that will be included in the Key Elements Table for QI-Core.  This set of elements is consistent with the FHIR-41474 disposition for QI-CoreMedicationRequest and USCoreMedicationRequest to assure harmonization across QI-Core and with the US Core version 6.1.0 version.

      QI-Core Profile-based path Action Include in QI-Core 6.0 Justification
      QICoreMedicationNotRequested.authoredOn Keep YES USCDI element required in US Core and needed to identify timing of the documentation to "not order".
      QICoreMedicationNotRequested.intent Keep YES USCDI element MS with US Core and required to indicate the medication ordered, planned, or proposed
      QICoreMedicationNotRequested.medication[x] Keep YES Keep and retain specific extension for notDoneValueSet
      QICoreMedicationNotRequested.reported[x] Keep with modification YES (Change) Required element in US Core MedicationRequest and the item is a USCDI element. US Core includes reference only to USCorePractitioner. Keep current QICore references to QICorePractitioner, QICorePatient, QICoreRelatedPerson since the field is required in US Core to identify a patient-reported medication and have it appear on the medication list.  REMOVE reference to QICorePractitionerRole as an overreach since determining specific details about the practitioner making the request is likely to be challenging to collect and retrieve.
      QICoreMedicationNotRequested.status Keep YES MS element US Core MedicationRequest 6.1.0 using the same value set binding as in QI-Core MedicationRequest 5.0.1. Required for all patterns using FHIR
      QICoreMedicationNotRequested.statusReason DO NOT ADD NO QDM to QI-Core mapping included status.Reason but it is not use in measures or in the MedicationNotRequested. It is not supported in US Core MedicationRequest. DO NOT add to MedicationNotRequested
      QICoreMedicationNotRequested.category (Slices for categorycategory:us-core) Keep YES MS element US Core MedicationRequest 6.1.0 using the same value set binding as in QI-Core MedicationRequest 5.0.1. Required for all patterns using FHIR. category is currently used to indicate specific prescriptions written while the patient is in a hospital and intended for dispensing and administration in the community settings.
      QICoreMedicationNotRequested.dosageInstruction Keep YES MS in US Core and USCDI element. includes data to determine dose and for cumulative medication duration. Since cardinality is 0..* the element should not be included in the Pattern as MedicationNotRequested has no prescription
      QICoreMedicationNotRequested.reasonCode Keep YES (Modify) This element is listed in US Core 6.1.0 with extensible binding to https://build.fhir.org/ig/HL7/US-Core/ValueSet-us-core-condition-code.html. Keep but change in QI-Core to extensible binding to QICore Negation Reason Codes 
      QICoreMedicationNotRequested.implicitRules Keep YES Present in Key Elements table in QI-Core and in US Core
      QICoreMedicationNotRequested.doNotPerform Keep YES (Modify to Fixed Value) Present in US Core Key Elements table even though not MS. And, to assure the profile is disjoint from QICoreMedicationNotRequested, QICoerMedicationRequest.doNotPerform has a Fixed Value: True. 
      QICoreMedicationNotRequested.subject Keep YES (Modify reference) Required USCDI element in US Core and required to indicate the request is for a patient. Reference to QICorePatient rather than USCore reference to USCorePatient
      QICoreMedicationNotRequested.encounter Keep YES (Modify Reference) Required USCDI element in US Core - reference QICoreEncounter instead of USCoreEncounter
      QICoreMedicationNotRequested.requester Keep (Modify) YES (Modify References) Required USCDI element in US Core. Reference QICorePractitioner instead of USCorePractitioner. REMOVE reference to QICorePractitionerRole and QICorePatient since PractitionerRole data are unlikely to be retrievable and since US Core and QI-Core create medication lists from MedicationRequest but patients cannot write medication orders so a patient-reported vaccine should be entered as ordered by practitioner (requester) and reported by patient.
      QICoreMedicationNotRequested.recorder Remove NO US Core does not have MS or requirement for recorder. Requester should be sufficient. May be in QDM to QI-Core mapping tables which will be modified once all changes to QI-Core are complete.
      Show
      Consider the following resolution - some items require discussion.  Note that, unless the element has a MS flag in US Core 6.1.0, we should include those Keep element in the Key Elements Table for QICore but not add an MS Flag. Add (QM) to description of all Keep or Add elements such that that will be included in the Key Elements Table for QI-Core.  This set of elements is consistent with the FHIR-41474 disposition for QI-CoreMedicationRequest and USCoreMedicationRequest to assure harmonization across QI-Core and with the US Core version 6.1.0 version. QI-Core Profile-based path Action Include in QI-Core 6.0 Justification QICoreMedicationNotRequested. authoredOn Keep YES USCDI element required in US Core and needed to identify timing of the documentation to "not order". QICoreMedicationNotRequested. intent Keep YES USCDI element MS with US Core and required to indicate the medication ordered, planned, or proposed QICoreMedicationNotRequested. medication[x] Keep YES Keep and retain specific extension for  notDoneValueSet QICoreMedicationNotRequested. reported[x] Keep with modification YES (Change) Required element in US Core MedicationRequest and the item is a USCDI element. US Core includes reference only to USCorePractitioner. Keep current QICore references to QICorePractitioner, QICorePatient, QICoreRelatedPerson since the field is required in US Core to identify a patient-reported medication and have it appear on the medication list.   REMOVE reference to QICorePractitionerRole as an overreach since determining specific details about the practitioner making the request is likely to be challenging to collect and retrieve. QICoreMedicationNotRequested. status Keep YES MS element US Core MedicationRequest 6.1.0 using the same value set binding as in QI-Core MedicationRequest 5.0.1. Required for all patterns using FHIR QICoreMedicationNotRequested.statusReason DO NOT ADD NO QDM to QI-Core mapping included status.Reason but it is not use in measures or in the MedicationNotRequested. It is not supported in US Core MedicationRequest. DO NOT add to MedicationNotRequested QICoreMedicationNotRequested.category ( Slices for category ,  category:us-core ) Keep YES MS element US Core MedicationRequest 6.1.0 using the same value set binding as in QI-Core MedicationRequest 5.0.1. Required for all patterns using FHIR. category is currently used to indicate specific prescriptions written while the patient is in a hospital and intended for dispensing and administration in the community settings. QICoreMedicationNotRequested. dosageInstruction Keep YES MS in US Core and USCDI element. includes data to determine dose and for cumulative medication duration. Since cardinality is 0..* the element should not be included in the Pattern as MedicationNotRequested has no prescription QICoreMedicationNotRequested. reasonCode Keep YES (Modify) This element is listed in US Core 6.1.0 with extensible binding to https://build.fhir.org/ig/HL7/US-Core/ValueSet-us-core-condition-code.html . Keep but change in QI-Core to extensible binding to  QICore Negation Reason Codes   QICoreMedicationNotRequested. implicitRules Keep YES Present in Key Elements table in QI-Core and in US Core QICoreMedicationNotRequested. doNotPerform Keep YES (Modify to Fixed Value) Present in US Core Key Elements table even though not MS. And, to assure the profile is disjoint from QICoreMedicationNotRequested, QICoerMedicationRequest.doNotPerform has a Fixed Value: True.  QICoreMedicationNotRequested. subject Keep YES (Modify reference) Required USCDI element in US Core and required to indicate the request is for a patient. Reference to QICorePatient rather than USCore reference to USCorePatient QICoreMedicationNotRequested. encounter Keep YES (Modify Reference) Required USCDI element in US Core - reference QICoreEncounter instead of USCoreEncounter QICoreMedicationNotRequested. requester Keep (Modify) YES (Modify References) Required USCDI element in US Core. Reference QICorePractitioner instead of USCorePractitioner. REMOVE reference to QICorePractitionerRole and QICorePatient since PractitionerRole data are unlikely to be retrievable and since US Core and QI-Core create medication lists from MedicationRequest but patients cannot write medication orders so a patient-reported vaccine should be entered as ordered by practitioner (requester) and  reported  by patient. QICoreMedicationNotRequested. recorder Remove NO US Core does not have MS or requirement for recorder. Requester should be sufficient. May be in QDM to QI-Core mapping tables which will be modified once all changes to QI-Core are complete.
    • 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: