HTTP schemes in CapabilityStatement

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • CapabilityStatement (Conformance)
    • Hide

      For instances, this is conveyed in instance.url. For general requirements, we don't see a value in calling out this particular piece of security given that implementations could make different choices. The implementation guide publisher allows you to set a value for this in the OpenAPI template.

      Show
      For instances, this is conveyed in instance.url. For general requirements, we don't see a value in calling out this particular piece of security given that implementations could make different choices. The implementation guide publisher allows you to set a value for this in the OpenAPI template.
    • Ewout Kramer/Grahame Grieve: 5-0-0
    • Enhancement

      Hi Team,

      I have a request on defining the http scehems for an FHIR interface. On the 'rest' model, CapabilityStatement doesn't explicitely specify if the implementation support HTTP/HTTPS schema. Can we define it in the similar way that is defined for messaging "CapabilityStatement.messaging.endpoint.protocol". If we want to read CapabilityStatement as the input to generate API specification like a Swagger file, then this information will be very useful to define the "schemes" element in Swagger.

      Regards,

      Shovan

            Assignee:
            Unassigned
            Reporter:
            shovanroy_hl7
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: