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

Please rename and document NDH Dynamic Registration extension

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • National Directory of Healthcare Providers and Services (NDH) (FHIR)
    • 1.0.0-ballot
    • Patient Administration
    • STU
    • Exchange Artifacts
    • 27.122.1
    • Hide

      include better description and examples of this extension and is use in relationship to the access control mechanism extension

      Show
      include better description and examples of this extension and is use in relationship to the access control mechanism extension
    • Bob Dieterle / David Pike : 6-0-0
    • Clarification
    • Non-substantive

      The NDH Dynamic Registration extension provides a critical value, which is identifying which trust mechanism is used (at this time, for FHIR it's UDAP or SMART). But it is misnamed and not documented. Dynamic registration is just one part of the OAuth 2 workflow, and it follows Discovery, where you either hit <FHIRBase>.well-known/smart-configuration or <FHIRBase>.well-known/udap. Is the field intended only to differentiate between OAuth 2 profiles? If so, then call it something like OAuth 2 Discovery. If it's broader, to include mechanisms like mTLS, then call it something like trust mechanism. Also, please document its meaning.

            Unassigned Unassigned
            jlamy Joseph M. Lamy
            Joseph M. Lamy
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: