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

Anchor changes or data in context changes?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Deferred (View Workflow)
    • Priority: Highest
    • Resolution: Considered for Future Use
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related Page(s):
      (NA)
    • Related Section(s):
      Event Notification
    • Grouping:
    • Resolution Description:
      Hide

      Kicking the can down the road, because this is hard, something we need to get right and would likely benefit from more real world experience.

       

      Show
      Kicking the can down the road, because this is hard, something we need to get right and would likely benefit from more real world experience.  
    • Resolution Vote:
      Isaac Vetter/Eric Martin: 16-0-2

      Description

      Is this intended to exchange data in context or to signal anchor changes?
      In the case of signalling data in context, how do we handle parallel changes between multiple applications? This could trigger a message storm (they both try to merge the changes, sending updates on the update, which triggers a new merge, …)

      Proposed 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:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: