Appointment.order can't work at present

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Administration
    • STU
    • Appointment
    • Hide

      The "Order" Property will be removed as is of the incorrect type.

      Appointments can already be associated with CarePlans and ClinicalImpressions.

      Note: Making Order work with appointments will be tackled post DSTU2.

      Show
      The "Order" Property will be removed as is of the incorrect type. Appointments can already be associated with CarePlans and ClinicalImpressions. Note: Making Order work with appointments will be tackled post DSTU2.
    • Brian/Iryna:5-1-0
    • Correction
    • Non-compatible
    • Yes
    • DSTU1 [deprecated]

      The Order class can't stand alone. It's a workflow resource that has to point to an "order/request" resource. For example, DiagnosticOrder, MedicationPrescription, etc. If the Appointment was going to point to anything, it would be what the Order points to, not Order. And it's not clear what that something would be. Referral?

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

              Created:
              Updated:
              Resolved: