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

Adjust QI-Core ServiceRequest 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 ServiceRequest
    • Hide

      Modify QI-Core ServiceRequest as follows (to align with US Core and to address element usage in existing measures). All items imported from US Core 6.1.0 that are identical to the QI-Core version are expected to be present. Only modifications or additions are listed in this table.

      Note, all items identified as KEEP in this table should have MS flags only if they exist in the US Core ServiceRequest profile; other items listed as KEEP should appear in the QI-Core Key Elements table for ServiceRequest but NOT include a MS flag:

       

      QI-Core Profile-based path Action Include in QI-Core 6.0 Justification      
      QICoreServiceRequest QICoreServiceRequest.authoredOn Keep Same as US Core      
      QICoreServiceRequest QICoreServiceRequest.code Keep Same as US Core with extensible binding to US Core Procedure Codes      
      QICoreServiceRequest QICoreServiceRequest.intent Keep Same as US Core      
      QICoreServiceRequest QICoreServiceRequest.status Keep Same as US Core      
      QICoreServiceRequest.reasonCode Add Discuss with CQI Exists in current measures and present in US Core Key Element Table. HOWEVER, US Core has extensible binding to US Core Condition Codes. The QI-Core Key Element table reference to reasonCode has an example binding to ProcedureReasonCodes. Suggest ALIGN and keep US Core Condition Code extensible binding which will allow use of value sets related to procedure codes.      
      QICoreServiceRequest.approachBodyStructure(extension) Remove NO Not in use and not addressed in US Core      
      QICoreServiceRequest.appropriatenessScore(extension) Remove NO Not in use and not addressed in US Core. Originally intended to address orders by adding the RAND appropriateness score to address CMS rules for specific procedures (imaging)      
      QICoreServiceRequest. Slices for modifierExtension Remove NO – Depends on Bryn review of appropriatenessScore Not addressed in US Core and since the existing 2 extensions are to be removed from QI-Core, no longer needed. Inherit US Core 6.0 modifierExtension      
      QICoreServiceRequest.modifierExtension:isElective Remove NO – Depends on Bryn review of appropriatenessScore Not addressed in US Core and since the existing 2 extensions are to be removed from QI-Core, no longer needed      
      QICoreServiceRequest.doNotPerform Keep YES (retain Fixed value = False) Keep with fixed value = false - accommodates disjoint QICoreServiceNotRequested (also in Key Element table for US Core without constraint to fixed value)      
      QICoreServiceRequest.subject Keep YES (Reference QICorePatient) Same as US Core except references QICorePatient rather than USCorePatient, retain reference to QICorePatient      
      QICoreServiceRequest.encounter Remove NO Not in US Core Key Element table and not used in existing measures      
      QICoreServiceRequest.occurrence[x] Keep YES – align with US Core
       
      Present in US Core Key Element table; however, US Core lists only Occurence.period. Therefore, align directly with US Core and only list Occurrence.period in Key Element Table (I.e., not list OccurrenceDateTime or OccurrenceTiming). Rationale - not used.  NOTE - Definition of Occurrence is time when event should occur so it does not address the time the ServiceRequest was created.      
      QICoreServiceRequest.asNeeded[x] Remove NO Not in US Core Key Element table and not used in existing measures. Definition: A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.      
      QICoreServiceRequest.requester Keep YES Same as US Core      
      QICoreServiceRequest.performer Remove NO Not in US Core Key Element table and not used in existing measures. Definition: Requested performer ---- was initially included in QICore to address attribution but not in use.      
      QICoreServiceRequest.reasonReference Keep YES Reference QICore Condition Encounter Diagnosis and QICore Condition Problems Health Concerns Present in US Core Key Element Table.  Delta is the US Core References include Condition, Observation, DiagnosticReport, DocumentReference (Note, these are not referencing US Core profiles for any of these referenced items). QI-Core references QICore Condition Encounter Diagnosis and QICore Condition Problems Health Concerns.  Suggest retain the existing QI-Core references rather than those listed in the US Core 6.1.0 profile especially since their references are to base FHIR resources.      
      QICoreServiceRequest.specimen Remove NO Not in US Core Key Element table and not used in existing measures.       
      QICoreServiceRequest.bodySite Remove NO Not in US Core Key Element table and not used in existing measures.       

       

      Show
      Modify QI-Core ServiceRequest as follows (to align with US Core and to address element usage in existing measures). All items imported from US Core 6.1.0 that are identical to the QI-Core version are expected to be present. Only modifications or additions are listed in this table. Note, all items identified as KEEP in this table should have MS flags only if they exist in the US Core ServiceRequest profile; other items listed as KEEP should appear in the QI-Core Key Elements table for ServiceRequest but NOT include a MS flag:   QI-Core Profile-based path Action Include in QI-Core 6.0 Justification       QICoreServiceRequest QICoreServiceRequest.authoredOn Keep Same as US Core       QICoreServiceRequest QICoreServiceRequest.code Keep Same as US Core with extensible binding to US Core Procedure Codes       QICoreServiceRequest QICoreServiceRequest.intent Keep Same as US Core       QICoreServiceRequest QICoreServiceRequest.status Keep Same as US Core       QICoreServiceRequest. reasonCode Add Discuss with CQI Exists in current measures and present in US Core Key Element Table. HOWEVER, US Core has extensible binding to  US Core Condition Codes . The QI-Core Key Element table reference to reasonCode has an example binding to  ProcedureReasonCodes . Suggest ALIGN and keep US Core Condition Code extensible binding which will allow use of value sets related to procedure codes.       QICoreServiceRequest. approachBodyStructure (extension) Remove NO Not in use and not addressed in US Core       QICoreServiceRequest. appropriatenessScore (extension) Remove NO Not in use and not addressed in US Core. Originally intended to address orders by adding the RAND appropriateness score to address CMS rules for specific procedures (imaging)       QICoreServiceRequest.  Slices for modifierExtension Remove NO – Depends on Bryn review of appropriatenessScore Not addressed in US Core and since the existing 2 extensions are to be removed from QI-Core, no longer needed. Inherit US Core 6.0  modifierExtension       QICoreServiceRequest. modifierExtension:isElective Remove NO – Depends on Bryn review of appropriatenessScore Not addressed in US Core and since the existing 2 extensions are to be removed from QI-Core, no longer needed       QICoreServiceRequest. doNotPerform Keep YES (retain Fixed value = False) Keep with fixed value = false - accommodates disjoint QICoreServiceNotRequested (also in Key Element table for US Core without constraint to fixed value)       QICoreServiceRequest. subject Keep YES (Reference QICorePatient) Same as US Core except references QICorePatient rather than USCorePatient, retain reference to QICorePatient       QICoreServiceRequest. encounter Remove NO Not in US Core Key Element table and not used in existing measures       QICoreServiceRequest. occurrence[x] Keep YES – align with US Core   Present in US Core Key Element table; however, US Core lists only Occurence.period. Therefore, align directly with US Core and only list Occurrence.period in Key Element Table (I.e., not list OccurrenceDateTime or OccurrenceTiming). Rationale - not used.  NOTE - Definition of Occurrence is time when event should occur so it does not address the time the ServiceRequest was created.       QICoreServiceRequest. asNeeded[x] Remove NO Not in US Core Key Element table and not used in existing measures. Definition: A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.       QICoreServiceRequest. requester Keep YES Same as US Core       QICoreServiceRequest. performer Remove NO Not in US Core Key Element table and not used in existing measures. Definition: Requested performer ---- was initially included in QICore to address attribution but not in use.       QICoreServiceRequest. reasonReference Keep YES Reference  QICore Condition Encounter Diagnosis  and  QICore Condition Problems Health Concerns Present in US Core Key Element Table.  Delta is the US Core References include Condition, Observation, DiagnosticReport, DocumentReference (Note, these are not referencing US Core profiles for  any  of these referenced items). QI-Core references  QICore Condition Encounter Diagnosis  and  QICore Condition Problems Health Concerns .  Suggest retain the existing QI-Core references rather than those listed in the US Core 6.1.0 profile especially since their references are to base FHIR resources.       QICoreServiceRequest. specimen Remove NO Not in US Core Key Element table and not used in existing measures.        QICoreServiceRequest. bodySite Remove NO Not in US Core Key Element table and not used in existing measures.         
    • 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: