Clarify use of Service Request

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US QI Core (FHIR)
    • STU3
    • Clinical Quality Information
    • STU
    • QICore ServiceRequest
    • 7.20.0
    • Hide

      Proposed resolution: Persuasive with mod

      Update QDM mapping to clarify:

      QDM datatypes referencing Order always use ServiceRequest.intent = order; QDM datatypes referencing Recommended always use ServiceRequest.intent = plan (specifically for Assessment, Encounter, Laboratory Test, Physical Exam and Diagnostic Study).

      Note that all QDM datatypes include reference to a QI-Core status (e.g., completed) such that other options (e.g., on-hold, etc.) are precluded in the mappings.

      ServiceRequest.category references classification of service. The related value set provides examples (e.g., laboratory, counseling, imaging, education, surgical procedure). Since the item code / value set requested generally references the specific category, adding a requirement for ServiceRequest.category seems unnecessary.

      Show
      Proposed resolution: Persuasive with mod Update QDM mapping to clarify: QDM datatypes referencing Order always use ServiceRequest.intent = order; QDM datatypes referencing Recommended always use ServiceRequest.intent = plan (specifically for Assessment, Encounter, Laboratory Test, Physical Exam and Diagnostic Study). Note that all QDM datatypes include reference to a QI-Core status (e.g., completed) such that other options (e.g., on-hold, etc.) are precluded in the mappings. ServiceRequest.category references classification of service. The related value set provides examples (e.g., laboratory, counseling, imaging, education, surgical procedure). Since the item code / value set requested generally references the specific category, adding a requirement for ServiceRequest.category seems unnecessary.
    • Rob Samples/Peter Muir: 25-0-0
    • Clarification
    • Non-substantive

      Suggest repeating the "standard Service Request" rows rather than say "As in standard Service Request". Also,separate "X, Order" from "X, Recommended". Make it clear if ServiceRequest.status is constrained when ServiceRequest.intent is "plan" (i.e., for Recommended). Does active, on-hold, and completed status all apply to plan/recommended?

      Use of ServiceRequest.category needs further explanation; it is not clear how it help differentiate "intervention" from "procedure". This page also includes Assessment, Encounter, Laboratory Test, and Physical Exam, but does not say if or how ServiceRequest.category is used for these. The FHIR base definition for http://hl7.org/fhir/R4/valueset-servicerequest-category.html is not very clear, so perhaps QI-Core should constrain the codes to at least distinguish among the QDM types.

            Assignee:
            matthew_tiller
            Reporter:
            Paul Denning
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: