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

Websocketsupport in conformance statement

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 3.0.0-ballot
    • Infrastructure & Messaging
    • Conformance
    • 2.7.1
    • Hide

      All FHIRcast implementations, starting with STU2 requires the support of websockets. And the STU3 publication removes the alternate webhook capability entirely, so this element is extraneous either with STU3 or a future publication.

      Deprecating this element is a breaking change, without any functional improvement. 

      Renaming this element is a breaking change, with the potential future functional capability of additional communication channels. Additional communication channels seem like a bad thing to me, because they would introduce significant and fundamental optionality thereby decreasing interoperability.

      Show
      All FHIRcast implementations, starting with STU2 requires the support of websockets. And the STU3 publication removes the alternate webhook capability entirely, so this element is extraneous either with STU3 or a future publication. Deprecating this element is a breaking change, without any functional improvement.  Renaming this element is a breaking change, with the potential future functional capability of additional communication channels. Additional communication channels seem like a bad thing to me, because they would introduce significant and fundamental optionality thereby decreasing interoperability.

      Deprecate and remove the field 'websocketSupport' or change it to 'supportedChannels' with one allowed value: 'websocket'.

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

              Created:
              Updated:
              Resolved: