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

Inconsistency in the use of https.

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Highest
    • Resolution: Persuasive
    • CDS Hooks (FHIR)
    • 1.0
    • Clinical Decision Support
    • (NA)
    • Calling a CDS Service
    • Hide

      Changed from:

      >The scheme should be `https`

      to:

      >The scheme MUST be `https`.

       

      Because, it really should be and because we already require all exchanges to use TLS; however, this is still technically a breaking change.

      Show
      Changed from: >The scheme should be `https` to: >The scheme MUST be `https`.   Because, it really should be and because we already require all exchanges to use TLS; however, this is still technically a breaking change.
    • Ricardo Quintano/Sarah Shaw: 15-0-5
    • Correction
    • Non-substantive
    • Yes

    Description

      This is inconsisted with the text on using https in the introduction. Why is it optional here and mandatory elsewhere?

      Existing Wording:

      Two optional methods are provided. First, FHIR resources MAY be obtained by passing "prefetched" data from the CDS Client to the CDS Service in the service call. FHIR resources requested in the CDS Service description are passed as key-value pairs, with each key matching a key described in the CDS Service description, and each value being a FHIR resource. Note that in the case of searches, this resource may be a searchset Bundle. If data are to be prefetched, the CDS Service registers a set of "prefetch templates" with the CDS Client, as described in the Prefetch Template section below.

      Proposed Wording:

      The base URL of the CDS Client's FHIR server.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: