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

Access Token must not be included in appContext

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • current
    • Clinical Decision Support
    • Retrieval of Payer Resources [deprecated]
    • 4.4.1.1
    • Hide

      Will remove access token and add language regarding payers being cautious about prepopulating Questionnaires with sensitive information, because, in the rare situation, where a malicious application attempts to access information that was not authorized by the EHR.

      Show
      Will remove access token and add language regarding payers being cautious about prepopulating Questionnaires with sensitive information, because, in the rare situation, where a malicious application attempts to access information that was not authorized by the EHR.
    • Bob Dieterle / Jeff Brown : 12-0-2
    • Correction
    • Compatible, substantive

    Description

      At https://hl7.org/fhir/us/davinci-dtr/specification__behaviors__retrieval_of_payer_resources.html#authentication-of-smart-on-fhir-application-to-payer-api in section 4.4.1.1, it says

      • In the case that authentication is required, the following JSON structure SHALL be populated by the payer system.

       Two concerns with this:

      1. It is not clear, WHERE the payer shall populate this JSON.
      2. If the language is intended to mean, the payer shall include this JSON in the appContext, then passing a FHIR Authorization through appContext IMO is not appropriate from a security perspective, and I would like to request a security review of this.  Especially, elsewhere in the spec, we say that the CRD Client can ignore the App URL, and use the appContext to launch some other App.

      Also note that DTR needs to contact the Payer and authenticate, even when a CRD interaction did not happen before that. So I would even argue that DTR must need no information from the CRD AppContext to work.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            m_varghese Varghese Mathew
            Varghese Mathew
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: