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

Align Request resources' asNeeded and reason

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • Orders & Observations
    • DeviceRequest (was DeviceUseRequest)
      MedicationRequest
      NutritionOrder (was NutritionRequest)
      ServiceRequest (Diagnostic/Procedure/ReferralRequest)
      SupplyRequest
    • Hide

      Given the work done in FHIR-26674, this is not persuasive. 

      Show
      Given the work done in FHIR-26674 , this is not persuasive. 
    • Marti Velezis / JD Nolen : 4 - 0 - 1

    Description

      There seems to be some variation in how we record why a request is being made (reason), and how we record "on demand" usage. It isn't clear that this variation is intentional, rather than just separate evolution.

      Do all the resources need a boolean asNeeded?

      Do they need an asNeededCodableConcept or asNeededFor? Is the meaning the same? Is the intent "as needed when" rather than "as needed for"?

      Is it clear about how "as needed" is distinct from the reason for the request?

      Suggest using the same structure and definitions across all resources.

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: