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

Clarifications on dynamic client registration and first token request

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci PDex (FHIR)
    • current
    • Financial Mgmt
    • Payer-to-Payer Exchange [deprecated]
    • Hide

      A section has been added to the PayerToPayerExchange page. 

      OAuth2.0 Dynamic Client Registration

      Once payers have setup a secure mTLS connection, the new Payer will query the Dynamic Client Registration Protocol (DCRP) endpoint of the target (old) payer to obtain a client credential with scopes that enable queries to be made to the $member-match operation endpoint.

       

      Examples of the request and response will also be added.

      Show
      A section has been added to the PayerToPayerExchange page.  OAuth2.0 Dynamic Client Registration Once payers have setup a secure mTLS connection, the new Payer will query the Dynamic Client Registration Protocol (DCRP) endpoint of the target (old) payer to obtain a client credential with scopes that enable queries to be made to the $member-match operation endpoint.   Examples of the request and response will also be added.
    • Bob Dieterle / MaryKay McDaniel: 8-0-0
    • Clarification
    • Compatible, substantive
    • Yes
    • 2.0.0-ballot [deprecated]

      The implementation guide does not specify which kind of client registration to perform (probably client credentials?) in step 1b and which kind of OAuth 2.0 token request to perform in step 2a. 

      Exact details of the expected requests and response - with examples - are needed.

            Unassigned Unassigned
            michelemottini Michele Mottini
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: