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

Move content sharing to content sharing

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Withdrawn
    • DiagnosticsReport open event [deprecated]
    • Hide

      Content sharing is now positioned as part of the main spec (see FHIR-37120).

      That makes this comment no longer relevant.

      Show
      Content sharing is now positioned as part of the main spec (see FHIR-37120 ). That makes this comment no longer relevant.
    • Catie Ladd / Nick Radov : 6-0-1
    • Clarification
    • Non-substantive
    • Yes

    Description

      If a Hub supports content sharing, when it distributes a DiagnosticReport-open event the Hub associates a context.versionId with the anchor context. Subscribed applications MUST submit this context.versionId in subsequent DiagnosticReport-update requests. If a client will neither make a DiagnosticReport-update request or respond to DiagnosticReport-update events, the versionId can be safely ignored.

      The mandatory elements should be made part of the content sharing chapter.

      Does an application participates in the network, wants to receive diagnostic-open and close events but does not participate in the context sharing have to follow this requirement? If so, this should not be the case as it breaks the generic event pattern.

      ps. Is it versionId or timestamp?

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: