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

The timestamp SHOULD be used by subscribers to establish message affinity – as the order is not guaranteed, we should make this stronger.

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related Page(s):
      (NA)
    • Related Section(s):
      Event Notification
    • Grouping:
    • Resolution Description:
      Hide

      Adopt Bas' ended change from MAY to SHOULD.

      Show
      Adopt Bas' ended change from MAY to SHOULD.
    • Resolution Vote:
      Isaac Vetter / Eric Martin : 5-0-0
    • Change Category:
      Correction
    • Change Impact:
      Compatible, substantive

      Description

      The timestamp SHOULD be used by subscribers to establish message affinity – as the order is not guaranteed, we should make this stronger.

      Existing Wording:

      The timestamp MAY be used by subscribers to establish message affinity (message ordering) through the use of a message queue.

      Proposed Wording:

      The timestamp SHOULD be used by subscribers to establish message affinity (message ordering) through the use of a message queue.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: