Thoughts on combining SupplyRequest, DeviceUseRequest and VisionPrescription - 2016-09 core #371

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Unresolved
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Workflow
    • 12.1.3
    • Hide

      Feb 06 2017 Grahame Grieve/Eric Haas: 8-0-0

      Ballot Resolution: Considered for Future Use

      This will not be addressed in STU 3 but will be considered for Release 4

      --------------------------------------------

      This will not be resolved in time for STU 4 but will be considered for Release 5

      Show
      Feb 06 2017 Grahame Grieve/Eric Haas: 8-0-0 Ballot Resolution : Considered for Future Use This will not be addressed in STU 3 but will be considered for Release 4 -------------------------------------------- This will not be resolved in time for STU 4 but will be considered for Release 5
    • Enhancement

      Existing Wording: Supply Request, DeviceUseRequest, VisionPrescription

      Comment:

      Patient is required in DeviceUseRequest, while optional in the other two - IF that remains the case, then need to stay separate.

      VisionPrescription does have specific elements that the others dont have and is common, so whether it is a standard extension on DeviceUseRequest or its own resource does not matter so much - so keep separate

      Summary:

      Thoughts on combining SupplyRequest, DeviceUseRequest and VisionPrescription

        1. Screen Shot 2017-12-07 at 12.51.30 PM.png
          113 kB
          Eric Haas
        2. Screen Shot 2017-12-07 at 12.51.30 PM.png
          113 kB
          Eric Haas

            Assignee:
            Unassigned
            Reporter:
            Ulrike Merrick
            Watchers:
            2 Start watching this issue

              Created:
              Updated: