The base requirement is that the same timestamp may not be used twice.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • FHIRCast (FHIR)
    • 0.1 [deprecated]
    • Imaging Integration
    • (NA)
    • Event Notification Errors
    • Hide

      Recommendation:

      • a syncerror's event notification should not have special logic around its timestamp nor id. Rather, the timestamp should be the time at which the synerror occurred and the id should be a unique identifier, specific to the syncerror event (not the previously used id from the event that error'd). 

      To communicate the id of the errored event, we should require that implementers send this id in the fhir operationoutcome in the context of the seyncerror, like so:

      ```

      {{ "timestamp": "<the timestamp at which the sync error occurred>", "id": "<a new id specific to the syncerror event>", "event": { "hub.topic": "fdb2f928-5546-4f52-87a0-0648e9ded065", "hub.event": "syncerror", "context": [{ "key": "operationoutcome", "resource": { "resourceType": "OperationOutcome", "issue": [

      Unknown macro: { "severity"}

      ] } }] }}

      ```

      Show
      Recommendation: a syncerror's event notification should not have special logic around its timestamp nor id. Rather, the timestamp should be the time at which the synerror occurred and the id should be a unique identifier, specific to the syncerror event (not the previously used id from the event that error'd).  To communicate the id of the errored event, we should require that implementers send this id in the fhir operationoutcome in the context of the seyncerror, like so: ``` {{ "timestamp": "<the timestamp at which the sync error occurred>", "id": "<a new id specific to the syncerror event>", "event": { "hub.topic": "fdb2f928-5546-4f52-87a0-0648e9ded065", "hub.event": "syncerror", "context": [{ "key": "operationoutcome", "resource": { "resourceType": "OperationOutcome", "issue": [ Unknown macro: { "severity"} ] } }] }} ```
    • Eric Martin / Isaac Vetter: 10-0-0
    • Enhancement
    • Compatible, substantive

      The sync-error, the time of the event is already in the attached event. This should follow the base spec and reflect the time when the event is send. Also the spec says that the same timestamp may not be used twice.

      Existing Wording:

      ISO 8601-2 timestamp in UTC describing the time at which the event occurred with subsecond accuracy.

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

              Created:
              Updated:
              Resolved: