2015May core #3 - Appointment/Encounter Referencing

XMLWordPrintableJSON

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

      The appointment has a new status "proposed" which has been added (tracker 5713) and the start/end dates are now optional when in this status (or cancelled).

      There is a new field included minutesDuration which permits the recording of the duration of the requested appointment, and the details of what you would like to have scheduled should be entered in the comments property.

      Show
      The appointment has a new status "proposed" which has been added (tracker 5713) and the start/end dates are now optional when in this status (or cancelled). There is a new field included minutesDuration which permits the recording of the duration of the requested appointment, and the details of what you would like to have scheduled should be entered in the comments property.
    • Brian/Iryna 5-0-0
    • Enhancement
    • Compatible, substantive
    • Yes
    • DSTU1 [deprecated]

      Existing Wording: reference/Appointment

      Comment:

      Need a way to communicate planned encounters that are not yet scheduled. Appointmet requires start and end elements. Need to be able to communicate encounter in the next month or encounter in the next year or encounter every six weeks, etc. Suggest adding scheduledString or adding encounter resource as a reference so that the planned state of the encounter is captured.

            Assignee:
            Unassigned
            Reporter:
            Emma Jones
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: