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

Anchor changes or data in context changes?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Considered for Future Use
    • Icon: Highest 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

    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

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: