Drop VisionPrescription in favor of parameterized DeviceRequest - 2018-May Core STU #135

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Financial Mgmt
    • VisionPrescription
    • Hide

      The vision industry, including vision services insurers, would benefit from a fit for purpose resource and not from multiple and more generic resources.

      Suggest that the proponant bring forward an implementer focussed business case to an FM session at the next WGM where Vision and insurance SMEs can review.

      Show
      The vision industry, including vision services insurers, would benefit from a fit for purpose resource and not from multiple and more generic resources. Suggest that the proponant bring forward an implementer focussed business case to an FM session at the next WGM where Vision and insurance SMEs can review.
    • Mary Kay McDaniel/Varvara Semenova: 5-0-1
    • Correction

      Comment:

      Everything in VisionPrescription can now be adequately expressed using DeviceRequest. Orders for eyeglasses are no more special than orders for prosthetics, wheelchairs or other parameterized devices - and we're not going to have separate resources for each category of device. As such, VisionPrescription should be withdrawn and replaced with a profile on DeviceRequest

      Summary:

      Drop VisionPrescription in favor of parameterized DeviceRequest

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Lloyd McKenzie
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: