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

Provide proper details on authentication

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Persisting Application State [deprecated]
    • Hide

      Will delete the referenced paragraph and replace it a statement that if the app is a SMART app (and not a native application) that it SHALL use SMART backend authentication and will also provide a link to the SMART backend authentication process which provides the full protocol and details. 

      Show
      Will delete the referenced paragraph and replace it a statement that if the app is a SMART app (and not a native application) that it SHALL use SMART backend authentication and will also provide a link to the SMART backend authentication process which provides the full protocol and details. 
    • Bob Dieterle / Jeff Brown : 12-0-2
    • Correction
    • Compatible, substantive

    Description

      "When registering, the DTR app should be given a shared client secret and a public key, which can be used to prove its identity."

      This should be covered in the EHR/Smart app-to-payer authentication space, not here.  And we should be pointing to the SMART backend authentication process which provides a full protocol and details.  This level of information is not useful.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: