Stream: fhircast-github
Topic: docs / PR #53 describe considerations for synchronization...
Github Notifications (FHIRcast) (Dec 12 2018 at 23:24):
isaacvetter opened PR
from sync-considerations to master
Create a page describing considerations for synchronization error and failure.
Github Notifications (FHIRcast) (Feb 08 2019 at 21:06):
NiklasSvenzen updated PR #53
from sync-considerations to master
Create a page describing considerations for synchronization error and failure.
Github Notifications (FHIRcast) (Feb 08 2019 at 21:33):
NiklasSvenzen updated PR #53
from sync-considerations to master
Create a page describing considerations for synchronization error and failure.
Github Notifications (FHIRcast) (Feb 08 2019 at 21:55):
NiklasSvenzen updated PR #53
from sync-considerations to master
Create a page describing considerations for synchronization error and failure.
Github Notifications (FHIRcast) (Feb 14 2019 at 15:26):
daliboz submitted PR Review
Github Notifications (FHIRcast) (Feb 14 2019 at 15:26):
daliboz submitted PR Review
Github Notifications (FHIRcast) (Feb 14 2019 at 15:26):
daliboz created PR Review Comment
Should this (or general error scenarios) be described more generally? IE: is the the only operationOutcome that can be sent or is OperationOutcome in general the way this would be done?
Github Notifications (FHIRcast) (Feb 14 2019 at 15:26):
daliboz created PR Review Comment
if this is truly intended to be FHIR, the code needs to be from the valueset. IE: is this transient? Processing?
The details (we should define a valueSet) and diagnostics fields could be used for what is shown in code above.
Last updated: Apr 12 2022 at 19:14 UTC
