Clearly specify who is responsible for handling failure modes of Hubs and Apps.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • All
    • Hide

      As of now, the intent of the FHIRcast specification is to provide enough information for each app to know if it is out of sync, but not to prescribe behavior when an app falls out of sync. It is incumbent upon the application to determine the appropriate reaction to falling out of sync. This is described here:http://fhircast.org/syncconsiderations/

      As we begin to see more production-grade usage of FHIRcast over the next year, we should look for potential opportunities to improve synchronization failure edge-cases – optimally without breaking backward compatibility. 
       

      Show
      As of now, the intent of the FHIRcast specification is to provide enough information for each app to know if it is out of sync, but not to prescribe behavior when an app falls out of sync. It is incumbent upon the application to determine the appropriate reaction to falling out of sync. This is described here: http://fhircast.org/syncconsiderations/ As we begin to see more production-grade usage of FHIRcast over the next year, we should look for potential opportunities to improve synchronization failure edge-cases – optimally without breaking backward compatibility.   
    • Isaac Vetter/Eric Martin: 16-0-2

      Synchronizing context between applications is a topic that is important in the risk evaluation of medical products. The current specification is silent on who, in the FHIR Cast ecosystm, is responsible for maintaining state and handling failure modes of HUBs and Applications.
      This must be addressed in the specification. Suggestion: FHIRCast is event-hub only.

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

              Created:
              Updated:
              Resolved: