- WG-UMA - mailman.kantarainitiative.org

Fwd: [KI-LC] Wednesday June 16 2021 - FIRE WG presenting
by Alec Laws 14 Jun '21

14 Jun '21

From: Andrew Hughes <andrewhughes3000(a)gmail.com> Date: Mon, Jun 14, 2021 at 11:37 AM Subject: [KI-LC] Wednesday June 16 2021 - FIRE WG presenting To: Kantara Leadership Council <lc(a)kantarainitiative.org> Hi everyone - this month, Jim Kragh and Tom Jones of the FIRE WG will be talking about recent work on the Trust Registry and how this work is being introduced to various organizations. Please forward this note to your WG/DG - The call is open to all. The call is 9am Pacific / noon Eastern on Wednesday June 16 2021. We use the first 30 minutes for invited presentations and follow with a 60 minute LC business call. Call details: *Leadership Council * https://global.gotomeeting.com/join/112012805 <https://www.google.com/url?q=https://global.gotomeeting.com/join/112012805&…> You can also dial in using your phone. United States: +1 (646) 749-3129 Access Code: 112-012-805 *Andrew Hughes *CISM CISSP *In Turn Information Management Consulting* m +1 250.888.9474 5043 Del Monte Ave., Victoria, BC V8Y 1W9 AndrewHughes3000(a)gmail.com *https://www.linkedin.com/in/andrew-hughes-682058a <https://www.linkedin.com/in/andrew-hughes-682058a>* *Digital Identity | International Standards | Information Security * _______________________________________________ LC mailing list LC(a)kantarainitiative.org https://kantarainitiative.org/mailman/listinfo/lc

1 0

Draft minutes of UMA telecon 2021-06-10
by Alec Laws 10 Jun '21

10 Jun '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-06-10 MinutesRoll call Quorum was reached. Approve minutes - Approve minutes of UMA telecon 2021-04-22 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-22> , UMA telecon 2021-04-29 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-29> , UMA telecon 2021-05-06 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-06> , UMA telecon 2021-05-13 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-13> , UMA telecon 2021-05-20 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-20> , UMA telecon 2021-05-27 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-27> , UMA telecon 2021-06-03 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-06-03> Eve moves to approve. Steve seconds. Motion Passes! Charter Refresh (vote) Please review the Draft Charter 2021 <https://kantarainitiative.org/confluence/display/uma/Draft+Charter+2021>, changes have been highlighted in red. Steve moves to approve the Draft Charter 2021 document as the new group Charter. Thomas seconds. Motion Passes! (Alec will update the draft and inform the leader council after the call) Group Leadership (review nominations, vote) Eve moves to nominate Alec for Chair Alec moves to nominate Steve for Vice-Chair Hearing no objection. Passes by Acclamation! The group would like to thank Eve for her unwavering support of the group and role as Chair over these many years! Identiverse Coming-up Soon Will any one be there "in-person"? Steve will there if anyone would like to join him There will be a few virtual attendees Colin in moderating a mDL panel, and participated in a CAIRN Alliance panel. Kantara will have a general presentation available. Sal has a pre-recorded session on facial recognition. Relationship Manager - draft with credentials # UMA Resource Server Management This document extends [UMA Fedz] in order to specify the interface provided by the RS to the RO for resource management. This is achieved by introducing a Resource Management API which is used by a Resource Manager Client to view available resources and direct the AS to use for protection. ** This API could also allows the RO to - view access history - set direct policy (ie Adrian clause) - establish credentials required in AS, (smarthealth.card) Reqs: - The RO must authenticate to the RS, in order to authorize access to this API - (this capability of the RS is implied by UMA) - The RO can see a list of resources available at this RS (either protected or not) - The RO can modify the protection of resources (ie which AS to protect) - The RO can see AS's available for protection - can the RO direct the RS to get a PAT from a new AS? This is tricky depending on how PAT's are issued (ie may require end-user redirection) Possible API Names: - resource management - resource declaration - available resources - resource access management (RAM) This document introduces the following new concepts: - Resource Management API The API presented by the RS to the Resource Manager. This API is OAuth protected - Resource Management Token (RMT) (what scope should this Access Token capture?) "uma_management" - Resource Owner credentials The credentials registered by the resource owner within the resource server - Resource Owner Token (or Policies "the VC/VP") A token signed using the resource owner credentials. Allows the resource server to independently verify the the resource owner's intention - Policy Management API The API presented by the AS to the Resource Manager. This API is OAuth protected - Policy Management Token (PMT) (what scope should this Access Token capture?) "uma_policy" - would also be great if during UMA Grant, the AS could send the RqP to their Relationship Manager in order for new policy to be created 'just in time' (ciba-ish...) - this has been the 'cascading AS' discussion is past. RM provides a OIDC interface to facilitate the redirect (could be SIOP now?) ### 1.3 HTTP Usage, API Security, and Identity Context - add link between RM API and RM Token informative The use of the `uma_management` scope when requesting a RMT may indicate to the RS's authorization server that establishment of one or more PATs with an available UMA AS is 'useful' #### The `Resource Management API` allows the Resource Owner to: - View the available resources hosted at this RS, and their current protection - Register a Resource Owner Credential - (eg dyn client registration, posting a DID) - (for discussion) have verifiable credentials issued by the RS to the RO - not strictly necessary since the ROT can be created by the resource owner - This is a good outcome, since the burden on the RP is moved to the RO. The RO can present/delegate these VC's further - Should this draft specify the framework or the specific tech (oauth client vs w3c) and further profiling of the technical (similar to the uma grant claims types) - ~View the UMA Authorization Servers available to be used to protect~ - ~Manage the UMA protection of available resources~ Starting Conditions RMA: - The RS hosts resources for the RO - The RS supports resource protection from an UMA AS - The RS has a UMA PAT at one or more UMA ASs - **for discussion**A RS that support this profile does not need resource owner specific PATs. If the ROT is embedded in the RPT, no PAT or introspection is even required. One RS level PAT to allow introspection, and opaque RPTs to be issued - are situations where the RS doens't even know/trust the AS too far? No? - the RS implicitly trusts the AS since it includes the authority of the RO, outcome is RO can use any ASs, moves challenges for having an AS per RO Step 0 The Resource Manager obtains an OAuth Access Token valid for use at the Resource API. The Access Token must allow the RS to determine the RO's resources. - is there a purpose for NOT the RO to use this interface? Is this 'delegation' too early in - *trying to stay away from defining the identity system. - not necessary to identify the person, instead the RS needs to know the rights over the resources Step 1 (Get Info) The RM obtains a list of available resources Step 2 (Manage Credential) The RM registers credentials with the RO - Viewing and modifying registered credentials - Registering a new credential Step 3 (Optional?) The RM requests resources to be issued as Verifiable Credentials against one of the registered resource owner credentials - this would use something akin to https:// mattrglobal.github.io/oidc-client-bound-assertions-spec/ RM->RS: POST /give-me-a-crednetial-for { my_credential(step2), the resource(step1) } -> issued VC Ending Conditions RMA: - The RM has a list of available resources for the RO at this RS - maybe, the RM has w3c VC's representing the resources - The RS has attached the ROC(s) to the user account (public part / shared secret ) - The RM has the RO credentials (private part / shared secret ) #### The `Policy Management API ` allows the Resource Owner(or resource rights administrator??) to: - (is this the general resource rights administrator?) doens't need to be the same as the RO if there has been some RO->RRA delegation in the background - view existing policies for them - create new policies for resources (registered or not?) Starting Conditions PMA: - the RMA start and end conditions - The AS supports the policy management for the Step 0 The Resource Manager obtains an OAuth Access Token valid for use at the Policy API. The Access Token must allow the AS to determine the User(RO/RqP)'s policy. Step 1 (Get Info) The RM obtains a list of their existing policies and the AS supported policy claims Step 2 (Create Policy) The RM uses a ROC + resource description + support policy to create the resource owner token. The ROT is registered at the AS #### ## The Resource Owner Token ( Verifiable Credential or Presentation ) resource owner credential has two part: a identifier and the actual credential (oauth client id and oauth client secret) (did + private key) ``` ROT = a JWT signed by the ROC { id: rm create policy id? resource_owner_id : identifier portion of the ROC resources: [ resource_server: resource_id: (similar to how the path identifies the RO to the RS) resource_location: ?? allowed_scope: [ out of the available scopes ] ] allowed_rqp: client_id, other claims { email: bob(a)email.com } } ``` ## Available Resources Endpoint (RS) The API available at the available resources endpoint enables the resource manager to have knowledge of the resources hosted by the resource server for the resource owner. \_rs_id is a resource server defined identifier for a resource. Before a resource is registered at an AS, there is no handle/reference available (unless the RS provides one) GET /my-resources/ ``` [ { "_resource_id" "ABC", "resource_scopes":[ "view", "http://photoz.example.com/dev/scopes/print" ], "description":"Collection of digital photographs", "icon_uri":"http://www.example.com/icons/flower.png", "name":"Photo Album", "type":"http://www.example.com/rsrcs/photoalbum", // uri/location of the resource? }, ] ``` Protected Resources ``` [ { "_resource_id" "ABC", "authorization_sever_resource_id" : "_as_id" "authorization_server" : "as_identifier", "registered_scopes" : [ "view" ] }, { "_resource_id" "ABC", "authorization_sever_resource_id" : "_as_id_2" "authorization_server" : "as_identifier_2", "registered_scopes" : [ "view", " http://photoz.example.com/dev/scopes/print" ] } ] ``` In dashboard world, rs_id = PeI (pension identifier) - to confirm, is the PeI the same as the as_id? ie is it created by the RS or the AS RS_1 holds pension A with identifier a RS_1 registers pension A single person, single resource, single rs: can have multiple resource registration, eg with different scopes Resource = Patient Registered Resource 1: Just the Patient Object Registered Resource 2: The Patient + Sub Objects ### Available Resource Description A registered resource is a JSON document that extends the resource description from [UMA Fedz 3.1 Resource Description](1) with the following parameters: authorization_server OPTIONAL A string identifying the authorization server that protects this resource ** could also be the AS policy uri from resource registration? (1 https:// docs.kantarainitiative.org/uma/wg/rec-oauth-uma-federated-authz-2.0.html#re… ) #### List Available Resource Descriptions #### Update Available Resources Description ## Resource Owner Credentials Endpoint (RS) This API available at the Resource Owner Credentials Endpoint enables the resource manager to view and manage credentials registered for the resource owner. GET /my-credentials ``` [ { _id: cred_id, cred_type: did | client cred_value: { <a did > ...or <oauth_client metadata> } } ] ``` ## Resource Owner Policy Endpoint This API available at the Resource Owner Policy Endpoint enables the resource manager to view and manager policy registered for the authorized user ## [UMA Fedz] 5. Token Introspection Endpoint - needs modification to include the ROT, either to replace a permission, or an an 'authority' within a specific permission (to be bw compatible) ``` HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store ... { "active":true, "exp":1256953732, "iat":1256912345, "permissions":[ { "resource_id":"112210f47de98100", "resource_scopes":[ "view", "http://photoz.example.com/dev/actions/print" ], "exp":1256953732, "authority": ROT.JWT.VALUE } ] } ``` ## [UMA Grant] 3.3.4 Authorization Assessment and Results Determination - describe set math changes - ANCR receipt could be used on first contact with the AS (from the RM). Establishes the initial terms of this relationship and the delegation of authority - (Anchor Notice & Consent Receipt is a extension of the Consent Receipt (CR 1.2.1), including how it fits into protocol flows) Next steps: - defines the change to the AS authorization assessment - AS → RM. "i don't have a policy right now, maybe you RqP can create one that fulfills this clients request" - into ideas of a RO/RqP relationship manager (aka Wallet) AOB Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Michael, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve, Steve) Voting: 1. Eve 2. Michael 3. Alec 4. Domenico 5. Thomas 6. Steve 7. Sal Non-voting participants: 1. Scott 2. Colin

1 0

Nominations for 2021 Chair & Vice-Chair
by Alec Laws 08 Jun '21

08 Jun '21

Hi all, Couple items for the groups attention 1. We're meant to renew the Chair and Vice-Chair roles on a yearly basis. As per Eve's latest update, she's not able to continue in her role as Chair. *Please respond with your interest or nominations for these roles*. I'm more than happy to continue in as chair/vice-chair for this upcoming year 2. If you haven't already, please review the proposed draft Charter [link <https://kantarainitiative.org/confluence/display/uma/Draft+Charter+2021>] and reply with any further comments Best, - Alec

1 0

Agenda for UMA telecon 2021-06-10
by Alec Laws 08 Jun '21

08 Jun '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-06-10 Date and Time - *Primary-week Thursdays 6:30am PT* - Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> - United States: +1 (224) 501-3316, Access Code: 485-071-053 - See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar Agenda - Approve minutes of UMA telecon 2021-04-22 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-22> , UMA telecon 2021-04-29 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-29> , UMA telecon 2021-05-06 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-06> , UMA telecon 2021-05-13 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-13> , UMA telecon 2021-05-20 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-20> , UMA telecon 2021-05-27 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-27> , UMA telecon 2021-06-03 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-06-03> - Charter Refresh (tentative vote) - Group Leadership (review nominations, tentative vote) - Relationship Manager - draft with credentials - AOB

1 0

Draft minutes of UMA telecon 2021-06-03
by Alec Laws 03 Jun '21

03 Jun '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-06-03 MinutesRoll call Quorum was reached. Approve minutes - Approve minutes of UMA telecon 2021-04-22 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-22> , UMA telecon 2021-04-29 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-29> , UMA telecon 2021-05-06 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-06> , UMA telecon 2021-05-13 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-13> , UMA telecon 2021-05-20 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-20> , UMA telecon 2021-05-27 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-27> Deferred Charter Review/Refresh Please review the Draft Charter 2021 <https://kantarainitiative.org/confluence/display/uma/Draft+Charter+2021>, changes have been highlighted in red. (5) - A horizontal UMA security profile, considering other profiles including HEART, FAPI, and OAuth 2.1 Changes to Group Leadership - we need to renew our annual voting roles, Chair and Vice-Chair - Next quorum we'll need to discuss and ideally vote on this topic - *Feel free to send nominations to the list* so we're prepared at our next quorum. Alec will send a separate note to the list to raise this request - If you have a voting membership, please let Alec know if you can/can't attend next week Relationship Manager The last session was recorded, check it out so these will make sense Discussed the merits of having a credential (public key) registered at the RS for a Resource Owner, and the different use-cases it starts to enable, both for UMA and getting into VC/SSI. - RO can sign policy it writes to the AS. The RS can have less trust in the AS since it's really trusting the RO - Today the RS trusts the AS as the RO. With the credential, the RS can trust *any* AS - Give the RO some more fiduciary capability aside from system-system (RS-AS) trust. This is part of Decentralized ID value prop - RO can delegate directly to other RqPs - Can this help the RS, not have to trust the RO as much? ANCR established the RO establish terms with any other system - Binding is the most critical bit of the trust flow. CIBA also solves for this, in a way that a RqP - UMA helps Alice ensure, that Bob is who he says, such that her policy can be applied to his request for Access - CIBA helps Bob ensure Alice is who she is. Currently we don't strongly bind Alice to the AS - Can we bind Alice to the AS, in a way the requesting party can confirm who she is? - ANCR wants to capture all this trusted state so that all parties can have this transparency, including getting Witnesses just in time. (parallels to a KERI witnesses, there is cryptogrpahic binding + attestation over an identifier) - ie UMA pushed claims, where the AS can 'ask for more' from a trusted third party (the Witness) - RS can issue to Alice, VCs. Either resource's as a VC, or actually data-containing VCs. Alice is then free to delegate and use from there. (The ssi credential exchange api) RS <strong trust> RO <> AS RS <> AS <> RqP <> RPT{Alice's proof} <> RS Alec will update the last RM Draft to: - Add back the credential, drop Authorization Servers API from it. - We're shifting the trust from the Fedz Auth api to the RO through their credential. AOB - will be looking to setup an ANCR presentation to the Group is around a month. Sal will let us know when he's ready Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Michael, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve, Steve) Voting: 1. Michael 2. Steve 3. Eve 4. Alec 5. Sal 6. Domenico Non-voting participants: 1. Scott 2. Colin Regrets:

1 0

Agenda for UMA telecon 2021-06-03
by Alec Laws 03 Jun '21

03 Jun '21

1 0

Update
by Eve Maler 02 Jun '21

02 Jun '21

Hi everybody– I’m sorry for having to miss so many meetings in the last few months, but very grateful to Alec for stepping in and taking such a big leadership role in the WG, and everybody for continuing to contribute all the great work. While healthwise I'm okay now, given my day-to-day responsibilities I do need to “share” regular participation with more of my colleagues, Steve in particular. This will be a good thing! However, I think it means the end of my official chairmanship. I’m happy to to continue to pitch in on wiki editing, public speaking, and other assistance in a “chair emeritus” role, if there’s such a thing. Just let me know how I can help. Eve Maler | cell and Signal +1 425.345.6756

1 0

Towards AEMS
by Igor Zboran 01 Jun '21

01 Jun '21

Hi Eve, Alec, everyone, I drove the idea of ticket challenge further, to the concept of UMA-compliant communications platform, that does not interfere with the existing email infrastructure. Interaction with SMTP and IMAP servers is used only if the user has to explicitly demonstrate control of their email address – usually if WebFinger is not available to bootstrap the discovery of claims provider configuration from the email address. I will use this concept to complete the AEMS project. Please see the updated sequence diagrams at: https://github.com/uma-email/poc Regards -Igor

1 0

Draft minutes of UMA telecon 2021-05-27
by Alec Laws 27 May '21

27 May '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-27 MinutesRoll call Quorum was reached. Approve minutes - Approve minutes of UMA telecon 2021-04-22 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-22> , UMA telecon 2021-04-29 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-29> , UMA telecon 2021-05-06 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-06> , UMA telecon 2021-05-13 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-13> , UMA telecon 2021-05-20 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-20> Deferred Genomics is a very interesting topic as the data always have multiple subjects. There are many complex layers to genesis data, chunk, sequence, images, etc. Eve has heard of a group working on set of permissions around the use of genomics data, could be made into APIS. Nancy notes another group, PP2PI (patient privacy 2 promote interoperability). Reach out to Nancy if you want to see the group Charter Review/Refresh (2) purpose "For example, working with the Kantara Consent and Information Sharing Work Group" → Kantara or external consent-oriented work groups (add some examples, eConsent) "To promote interoperability of independent implementations of UMA", (keep this and add:) could this support wider interop? such as with HEART/OIDC - "To promote interoperability between UMA and other related - "To promote the use of UMA to provide authorization capabilities to - Consider 3rd party requests to standardize profiles and extensions where there is wider applicability of the profile - Review, evaluation and recommendation of submitted implementation profiles of UMA - (already covered by point 1) (3) (4) remove "Business Model Clause Templates for User-Managed Access (this may be a report instead; final title to be determined)" add Relationship Manager/Policy Manager/Resource Definition drafts (5) - GNAP / OAuth 2.1, (sender constrained tokens, no implicit, pkce) we're there other oauth extensions pulled in, or 2.1 is only OAuth2 + BCP? - would we accept an UMA profile based on GNAP instead of OAuth? Should UMA be GNAP-ready when it is released? - transition from Oauth to GNAP? - evaluation of UMA-like things on different authorization protocols, profile of GNAP - evaluation of claims token beyond IDTokens (VCs?) DO we need to define the different between implementation(/deployment profiles and guidance** - implementations = the vendors who have UMA impls - deployments = 'fully baked' systems that use UMA (PDP, FPX) UMA + X, profiles - HEART, FAPI, Consent Receipt * This draft consolidates the functionality in OAuth 2.0 [RFC6749], OAuth 2.0 for Native Apps ([RFC8252]), Proof Key for Code Exchange ([RFC7636]), OAuth 2.0 for Browser-Based Apps ([I-D.ietf-oauth-browser-based-apps]), OAuth Security Best Current Practice ([I-D.ietf-oauth-security-topics]), and Bearer Token Usage ([RFC6750]). * Where a later draft updates or obsoletes functionality found in the original [RFC6749], that functionality in this draft is updated with the normative changes described in a later draft, or removed entirely. * A non-normative list of changes from OAuth 2.0 is listed below: * The authorization code grant is extended with the functionality from PKCE ([RFC7636]) such that the default method of using the authorization code grant according to this specification requires the addition of the PKCE parameters * Redirect URIs must be compared using exact string matching as per Section 4.1.3 of [I-D.ietf-oauth-security-topics] * The Implicit grant ("response_type=token") is omitted from this specification as per Section 2.1.2 of [I-D.ietf-oauth-security-topics] * The Resource Owner Password Credentials grant is omitted from this specification as per Section 2.4 of [I-D.ietf-oauth-security-topics] * Bearer token usage omits the use of bearer tokens in the query string of URIs as per Section 4.3.2 of [I-D.ietf-oauth-security-topics] * Refresh tokens should either be sender-constrained or one-time use as per Section 4.12.2 of [I-D.ietf-oauth-security-topics] UMA + Consent Receipts City University Birmingham have a demo showing how UMA works with Consent Receipts. Was in a healthcare context Is there interest in setting up a joint UMA + CR WG call to review this? yes. Sal is going to dig up the link and share on the mailing list OIDF Liaison Any one interested in creating an UMA FAPI profile? There was a draft shared, but never signed. Do we need to finish this, and what is the purpose? To support maintenance of HEART + future FAPI UMA profile Relationship Manager Review Deferred AOB Attendees As of October 26, 2020, quorum <http://kantarainitiative.org/confluence/display/uma/Participant+Roster> is 5 of 9. (Michael, Domenico, Peter, Sal, Thomas, Andi, Alec, Eve, Steve) Voting: 1. Steve 2. Michael 3. Eve 4. Thomas 5. Alec Non-voting participants: 1. Colin 2. Scott 3. Tim 4. George 5. Zhen - learned about group from ONC AGM. Training in biomedical informatics, interested in genomic privacy. Patients hardly ever in the use of their data! 6. Nancy 7. Sal Regrets:

1 0

Agenda for UMA telecon 2021-05-27
by Alec Laws 26 May '21

26 May '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-27 UMA telecon 2021-05-27Date and Time - *Primary-week Thursdays 6:30am PT* - Screenshare and dial-in: https://global.gotomeeting.com/join/485071053 <https://www.google.com/url?q=https://global.gotomeeting.com/join/485071053&…> - United States: +1 (224) 501-3316, Access Code: 485-071-053 - See UMA calendar for additional details: http://kantarainitiative.org/confluence/display/uma/Calendar Agenda - Approve minutes of UMA telecon 2021-04-22 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-22> , UMA telecon 2021-04-29 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-04-29> , UMA telecon 2021-05-06 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-06> , UMA telecon 2021-05-13 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-13> , UMA telecon 2021-05-20 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-05-20> - Relationship Manager Review, discuss credential concept - AOB

1 0