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

Clarify description of authorization flow

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • CDS Hooks (FHIR)
    • 1.0
    • Clinical Decision Support
    • (NA)
    • Hide

      Update wording from:

      ...the CDS Service could then request authorization for FHIR resources as they were needed, and then retrieve the resources from the CDS Client's FHIR server.

      to:

      ...the CDS Service could obtain authorization to access the CDS Client's FHIR API, retrieving any resources required via FHIR read or search interactions.

       

      Show
      Update wording from: ...the CDS Service could then request authorization for FHIR resources as they were needed, and then retrieve the resources from the CDS Client's FHIR server. to: ...the CDS Service could obtain authorization to access the CDS Client's FHIR API, retrieving any resources required via FHIR read or search interactions.  
    • Dennis Patterson/Peter Muir: 23-0-0
    • Clarification
    • Non-substantive

    Description

      "the CDS Service could then request authorization for FHIR resources as they were needed, and then retrieve the resources from the CDS Client's FHIR server" – suggest rewriting this as "the CDS Service could obtain authorization to access the CDS Client's FHIR API, retrieving any resources required via FHIR read or search interactions."

      Attachments

        Activity

          People

            Isaac.Vetter Isaac Vetter
            jmandel Josh Mandel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: