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

Some OO requests need basedOn to RequestOrchestration

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Orders & Observations
    • NutritionOrder (was NutritionRequest)
      ServiceRequest (Diagnostic/Procedure/ReferralRequest)
      VisionPrescription
    • Hide

      add basedOn to VisionPrescription

       basedOn   0..* Reference CarePlan | RequestOrchestration | NutritionOrder | ServiceRequest)

      add RequestOrchestration as Reference to basedOn in the Resources:

      • ServiceRequest
      • VisionPrescription (see above)
      • NutritionOrder
      • DeviceRequest
      Show
      add basedOn to VisionPrescription   basedOn   0..* Reference CarePlan | RequestOrchestration | NutritionOrder  |  ServiceRequest ) add RequestOrchestration as Reference to basedOn in the Resources: ServiceRequest VisionPrescription (see above) NutritionOrder DeviceRequest
    • Elliot Silver / David Barwin : 6 - 0 - 3
    • Enhancement
    • Compatible, substantive
    • R6

    Description

      Any of these might be done in fulfillment of part of a complex order with interdependencies - which is what RequestOrchestration is for.  (VisionPrescription doesn't actually have basedOn at all - it should probably also point to at least CarePlan and ServiceRequest.)

      Attachments

        Activity

          People

            jdlnolen John D.L. Nolen
            lloyd Lloyd McKenzie
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: