Anchor changes or data in context changes?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Event Notification
    • 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.  
    • Isaac Vetter/Eric Martin: 16-0-2

      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.

        1. image-2020-05-18-15-14-16-872.png
          image-2020-05-18-15-14-16-872.png
          53 kB

            Assignee:
            Unassigned
            Reporter:
            Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: