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

Are all objects included in the request Context Change?

    XMLWordPrintableJSON

    Details

    • Type: Question
    • Status: Resolved - No Change (View Workflow)
    • Priority: Highest
    • Resolution: Considered - Question answered
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related Page(s):
      (NA)
    • Related Section(s):
      Request Context Change Event Object Parameters
    • Grouping:
    • Scheduling:
    • Resolution Description:
      Hide

      The only objects to be included are those defined within the specification. Unlike FHIR Subscriptions, FHIRcast events are user-initiated and only occur within a user's session. Volume overall will be substantially less than a FHIR Subscription to a hospital's ADT feed, for example.

      Show
      The only objects to be included are those defined within the specification. Unlike FHIR Subscriptions, FHIRcast events are user-initiated and only occur within a user's session. Volume overall will be substantially less than a FHIR Subscription to a hospital's ADT feed, for example.

      Description

      Are all objects included? In other events effort is spend on reducing the size of the events, here the opposite is occurring. The size of these messages can become very large, e.g. when Binary resources are included.
      Needs more thought

      Existing Wording:

      An array of named FHIR objects corresponding to the user's context after the given event has occurred. Common FHIR resources are: Patient, Encounter, ImagingStudy and List.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bvdh Bas van den Heuvel
              Request in-person:
              Bas van den Heuvel
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: