UDAP gaps - HRex #119

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • STU3
    • Financial Mgmt
    • Profile overview [deprecated]
    • Hide

      We will look at including additional guidance around the use of UDAP - either as recommended coming out of FAST or as brought forward based on initial implementation experience in a future release of HRex

      Show
      We will look at including additional guidance around the use of UDAP - either as recommended coming out of FAST or as brought forward based on initial implementation experience in a future release of HRex
    • Bob Dieterle / Russ Leftwich: 8-0-0

      Comment:

      This may be better addressed to the UDAP group, but we've put it here due to the uncertainty of how closely this group has been working with UDAP.

      The UDAP spec leaves some decisions up to the implementer (e.g. "an auth server may cancel a previous registration if a key is re-used") - I think we should provide guidance on some of those points. For instance, if a key is re-used, the subsequent request should be rejected. The original app should first be deleted via the delete request at the management endpoint defined in RFC 7592.

      Summary:

      UDAP gaps

            Assignee:
            Unassigned
            Reporter:
            Michael Clifton
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: