move to capstatement documentation

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR R5 Subscriptions Backport (FHIR)
    • 0.1.0 [deprecated]
    • FHIR Infrastructure
    • (NA)
    • Hide

      Will move the narrative text into the Capability Statement rendering.

       

      Will also add the conformance note in the existing section:

      To declare conformance with this IG, a server should include the following URL in its CapabilityStatement.instantiates: http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement/backport-subscription-server

      Show
      Will move the narrative text into the Capability Statement rendering.   Will also add the conformance note in the existing section: To declare conformance with this IG, a server should include the following URL in its CapabilityStatement.instantiates:  http://hl7.org/fhir/uv/subscriptions-backport/CapabilityStatement/backport-subscription-server
    • Bas van den Heuvel / Gino Canessa : 14-0-0
    • Enhancement
    • Compatible, substantive

      Conformance: "Some options of the Subscriptions Framework are not easily expressed in a CapabilityStatement. In addition to the basic support in the CapabilityStatement (e.g., resources, interactions, and operations), a conformant server SHALL support at least one Payload Type and SHOULD support one Channel Type listed in this IG."

      These are easily added to the CS docuementation and no need to repeat here if rendered properly. 

      To state in the ig narrative put it the introductions to the appropriate sections. eg payload and channel sections. rather than here.

            Assignee:
            Unassigned
            Reporter:
            Eric Haas
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: