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

Again, DTR <-> Payer should use SMART backend services

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium

    Description

      >For EHRs that cannot support this protocol, the data will be stored on the payer server in a DocumentReference resource. Data stored in this way shall only be available for supporting the DTR workflow. Additionally, the DocumentReference may only be accessed by the app which created them. Smart apps and payer systems should be registered such that the payer system can establish identity of the smart app prior to granting access to the DocumentReference. When registering, the DTR app should be given a shared client secret and a public key, which can be used to prove its identity.

      The spec should clarify that SMART backend services are the specific mechanism used to do the above – also use keypairs, not string passwords. 

      Attachments

        Activity

          People

            michael_donnelly Michael Donnelly
            Isaac.Vetter Isaac Vetter
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: