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

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Request Context Change Event Object Parameters
    • 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

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: