- WG-UMA - mailman.kantarainitiative.org

Agenda for UMA telecon 2022-01-06
by Alec Laws 05 Jan '22

05 Jan '22

1 0

Draft Minutes of UMA telecon 2021-12-23
by Alec Laws 23 Dec '21

23 Dec '21

Please note we will cancel the call on Dec 30 for the US/CAN holiday https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-23 MinutesRoll call - Quorum: No Approve minutes - Approve minutes of UMA telecon 2021-09-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-09> , UMA telecon 2021-09-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-16> , UMA telecon 2021-09-23 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-23> , UMA telecon 2021-09-30 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-30> , UMA telecon 2021-10-14 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-14> , UMA telecon 2021-10-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-21> , UMA telecon 2021-10-28 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-28> , UMA telecon 2021-11-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-04> , UMA telecon 2021-11-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-18> , UMA telecon 2021-12-02 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-02> , UMA telecon 2021-12-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-09> , UMA telecon 2021-12-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-16> Deferred Working Session on BLT Use-Case Report Please find the new working document here: Julie Use-case Report <https://kantarainitiative.org/confluence/display/uma/Julie+Use-case+Report> *There are updates on the **Julie Use-case Report <https://kantarainitiative.org/confluence/display/uma/Julie+Use-case+Report> page.* Please feel free to comment directly there! (Hint: If you 'watch' the page in confluence you can receive notification when changes are made) These are the core messages: 1. Share data with another provider, probably at a granular level by resource, using UMA. 1. This is were we explain *why UMA over oAuth* and *highlight higher security in this process* 2. This is my note to Eve in the current outline: For the first section, when our use case describes basic UMA, I think this will be a good place to explain what UMA has over oAuth and highlight the increased security. If we can nail that part of the message it may help in all healthcare UMA implementations. 1. Julie comes of age and can control her own access – Delegation process (at 13yo) 2. Julie gets a bit older and needs to keep sensitive information private (sexual and sti history) 1. Sharing at a granular level by sensitivity settings 3. Alec, I know that at some point you want to add in additional policy and we can define where we want to do that in the story and then weave it into the how. Upcoming Conferences - https://identiverse.com/ Call for presentations is open, accepting proposals until early January. - Identity North is Jan 25-26 - Internet Identity Workshop <https://internetidentityworkshop.com/> 34 is April 26-28 AOB We will cancel the call next week Dec 30 due to US holiday. 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. Domenico 2. Eve 3. Alec 4. Sal Non-voting participants: 1. Joe Regrets: 1. Nancy

1 0

Agenda for UMA telecon 2021-12-23
by Alec Laws 22 Dec '21

22 Dec '21

1 0

Agenda for UMA telecon 2021-12-16
by Alec Laws 15 Dec '21

15 Dec '21

1 0

Draft minutes of UMA telecon 2021-12-09
by Alec Laws 09 Dec '21

09 Dec '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-09 MinutesRoll call - Quorum: No Approve minutes - Approve minutes of UMA telecon 2021-09-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-09> , UMA telecon 2021-09-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-16> , UMA telecon 2021-09-23 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-23> , UMA telecon 2021-09-30 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-30> , UMA telecon 2021-10-14 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-14> , UMA telecon 2021-10-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-21>, UMA telecon 2021-10-28 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-28>, UMA telecon 2021-11-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-04>, UMA telecon 2021-11-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-18>, UMA telecon 2021-12-02 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-02> Deferred Working Session on BLT Use-Case Report Please find the new working document here: Julie Use-case <https://kantarainitiative.org/confluence/display/uma/Julie+Use-case> https://kantarainitiative.org/confluence/pages/viewpageattachments.action?p… Goal for today: - Focus on one healthcare use-cases → outline for content we want to create - Use first pp2pi use case and apply to UMA and UMA legal. - Be empathetic in the language Notes: - we should always try to qualify the word "policy" to disambiguate (eg insurance policy, sharing policy) Once you describe the relationship between people and technical systems (AS, RS), it becomes much easier to define what policy exists and where is can be applied. There is a tension between a patient's right to privacy and a providers (doctor's) need to have a complete medical history. There are many levels of policy, from federal (state, region, city, organization) and finally down to the individual patient. Also many types of policy (legal, compliance... UMA enables patient driven policy, while other levels of policy are about risk management and liability. UMA is able to provide human rights enforcement. There has been recent shift and regulation to patient driven consent, wth the hope of giving them greater access and control over their data UMA can align the incentives of people and organization at all of these policy levels, between those who have the most risk and liability to manage, and the lack of control given to the patient because of those risks. Things are not fine-grained enough to enable sharing in safe ways, resulting in NO access. This is what info-blocking rules are starting to address, organizations have to do better to give control of the data to the subject 9patient) "architecture of the future of consent, we need to rectify the asymmetry that exists today through peer based, asynchronous and human consent" the pyramid: data protection, transparency, control. Only the middle layer is *maybe* appropriate to hold on a blockchain... Notice of risk and proof of notice is required before consent can be meaningfully gathered. Use-Case (initial state): - Julie is a adolescent woman, age 16 - She has a GP, and also see's an asthma specialist at a health organization - The health organization provide a patient portal, including proxy access features - The health organization provides a provider portal, with greater access to the data - The health organization provides a HCProvider identity provider/directory services, includes roles and patient roster - Julie has given her mother proxy access to this health portal - Julies' mother tells the provider about her history with abuse, this is noted in the record, but should be hidden from Julie be default - Julie wants to hide reproductive health data from her mother (eg STI test history) in the portal, and her asthma specialist who can also access the record - Her fathers insurance covers most of her medical care - The insurance invoices should redact specific health information about Julie from her father, while he has a want(need?) to know what he's paying for (was the service even performed?!) Examples of sensitive/conf health information areas, relevant to some providers - depending on role, hidden by default to th parent - social status (hungry, safe at home?) - sexual status (active? using condoms? STI?) - smoking and drug status - mental health status Technical Approaches: - HEART based sensitivity and confidentiality tagging. Different coding is mapped and tagged with this information (eg STI history observation get's tagged as sensitive) - to a proxy, can have default policy (share by default, hide by default) - use of the btg code, can turn an 'out of scope' access into a auditable and appropriate type of access - audit through 'privacy log' Out of scope: - big ad-tech and unintentional disclosure of information (eg Alice searches for X, and my parent starts seeing ads for dX) - multiple data subjects involved (parent, child) eg parent information sharing policy towards the child (history of domestic violence) - non-techinical data flows, eg phone calls etc where the human needs to make a fuzzy policy decision - (future) in the bow tie today, the AS 'licenses perm granting to' the RS, however isn't it the RS that is delegation the PDP to the AS? The RS is the responsible custodian of the data Design Pattern of state changes: - specific to the resource, the RS is responsible to track resources, the resource subject(s) and other tagging Outline of proposed document 1. Intro/Scope statement - what this report will cover 1. overall objective of the document, what we will cover, what the reader should understand by the end 1. Julie's use-case... how it is complex but typical. how to solve it in a way that's: technically feasible, respects Julie's rights to privacy and access to her information, respects the legal/regulatory policy requirements of the health system 2. understanding UMA's unique value to aid this use-case (why can't it just be OAuth??) 1. don't have to use *all* of UMA, parts can be used to address different challenges 2. how to make hard problems easier though UMA 3. how UMA's interacts with other protocols (OIDC, FHIR/SMARTonFHIR/HEART, OAuth) 2. What's not being covered 2. *Description of concrete use-case (Julie)* 1. *actors, data, systems (Primary care EMR, Specialist EMR, Pharmacy system, Payer system), identities *needs a diagram* 2. *capabilities and responsibilities of actors (Julie, HCP, Organization) eg link to Policy?* 3. *Policy that impacts the use-case* 1. *risk/liability vs patient agency * 2. *tension between policies (eg obligations to protect data vs obligation to enable sharing)* 4. Core UMA/HEART overview - why were even talking about UMA in this context 5. UMA application to use-case (steady state) *needs a diagram 6. Delegation state changes, 1. how the health journey affects state. 2. concrete events that create changes 1. Julie turns 17, 2. Julie sees asthma specialist 3. Father get's invoice from health provider, submits claim to insurance provider 4. Julie get's medication to treat STI, Provide create Rx, Pharmacist fills Rx and needs access to record (ie to see drug interactions) 7. Discussion? Tough corners, future topics 8. Conclusion 9. References, learn more Who will take the responsibility to create a draft? - Nancy to take a run at section 2/3 - Eve will work on the 16th ahead of the meeting When can we meet next? - we want a draft for next session (Dec 16) and use it as a working session - start an hour earlier and have a 2hour call - How much can we use graphics vs paragraphs? Do we want a page budget to limit scope? - yes 3-5 pages, try to not explain completely, just enough for the reader to understand How specific do we want to be around policy (eg HIPPA, CCPA)? - can we refer to other docs, and pull the most relevant observations out Future ideas: - exact same outline applied to financial services AOB - Should we cancel some of the meeting at the end of the month, eg Dec 23 and Dec 30? - Who would attend those sessions? - Alec to send a proposed meeting schedule for the rest of the year - https://identiverse.com/ Call for presentations is open, accepting proposals until early January. It 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. Steve 3. Alec 4. Sal 5. Andi Non-voting participants: 1. Scott 2. Nancy 3. George Regrets:

1 0

"Relationships" deck
by Eve Maler 09 Dec '21

09 Dec '21

Here is the deck I presented today, as revised. If anyone needs the source, let me know. Eve Maler | cell and Signal +1 425.345.6756

1 0

Agenda for UMA telecon 2021-12-09
by Alec Laws 08 Dec '21

08 Dec '21

1 0

Draft minutes of UMA telecon 2021-12-02
by Alec Laws 02 Dec '21

02 Dec '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-12-02 MinutesRoll call - Quorum: No Approve minutes - Approve minutes of UMA telecon 2021-09-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-09> , UMA telecon 2021-09-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-16> , UMA telecon 2021-09-23 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-23> , UMA telecon 2021-09-30 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-30> , UMA telecon 2021-10-14 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-14> , UMA telecon 2021-10-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-21> , UMA telecon 2021-10-28 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-28> , UMA telecon 2021-11-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-04> , UMA telecon 2021-11-18 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-18> Deferred *The Kantara All members meeting is Dec 8th, 11-1230ET (it's virtual, link TBD)* Delegation Use Cases Reviewed more pp2pi <https://www.drummondgroup.com/pp2pi/> use-cases, broken down by objective and mapped to whether uma or uma delegation can meet the goal Will continue this discussion next week Second use case is around geriatrics. There is less delegation requirements and seems to be a better pure UMA use-case. - 75yo man delegates some but not all of his health record with his wife. His wife also has a POA - which complicates the authorities - how does this case work? - does the man provide a next of kin with the RS or AS? how is it kept current? - the interaction with the RO is often infrequent, or based on specific health events How do we take these use cases to the next step? simple write up, how to use UMA to accomplish? Prep for next week's working session https://kantarainitiative.org/confluence/pages/viewpageattachments.action?p… Next will we will extend the meeting from 930-1230ET. The group reviewed the 4 documents in the link above - is there ordering between the relationships? (implicit or explicit) - how can we better overlay identity with UMA. One of the biggest anecdotal gaps is how identity integrates to UMA - eg RS may run their own identity process, or federate to another IDP - which could be the UMA AS?? - RO required IAL 2/3, easy to show with 1 IDP running the federation process. in practice there will be many more IDPs that need to collaborate AOB - ForgeRock getting more UMA use cases live - POA in Hawaii - Blue Cross - Florida - Blue Cross - CMS mandate has helped drive implementation - Should we cancel some of the meeting at the end of the month, eg Dec 23 and Dec 30? - Who would actually attend those sessions? Topic Candidates (from previous telcons) - Delegation and Guardianship - Outcome of user stories discussion - PDP architecture includes the concept of governance registry/discovery - TOIP/SSI are starting to define this ecosystem function - ANCR records update - Privacy as Expected/ANCR update : 2/3 weeks out (Sal?) 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. Alec Non-voting participants: 1. Scott G 2. Joe 3. Nancy Regrets:

1 0

Agenda for UMA telecon 2021-12-02
by Alec Laws 02 Dec '21

02 Dec '21

1 0

Draft minutes of UMA telecon 2021-11-18
by Alec Laws 29 Nov '21

29 Nov '21

https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-18 UMA telecon 2021-11-18Date and Time - *Primary-week Thursdays 06:30am PT; Secondary-week Thursdays 10:00am PT* - Screenshare and dial-in: https://zoom.us/j/99487814311?pwd=dTAvZi9uN0ZmeXJReWRrc1Zycm5KZz09 - 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-09-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-09> , UMA telecon 2021-09-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-16> , UMA telecon 2021-09-23 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-23> , UMA telecon 2021-09-30 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-30> , UMA telecon 2021-10-14 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-14> , UMA telecon 2021-10-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-21> , UMA telecon 2021-10-28 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-28> , UMA telecon 2021-11-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-04> , UMA telecon 2021-11-11 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-11> - Delegation Use Cases - Proof of Chain of Possession (POCOP) Tokens - AOB MinutesRoll call - Quorum: No Approve minutes - Approve minutes of UMA telecon 2021-09-09 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-09> , UMA telecon 2021-09-16 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-16> , UMA telecon 2021-09-23 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-23> , UMA telecon 2021-09-30 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-09-30> , UMA telecon 2021-10-14 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-14> , UMA telecon 2021-10-21 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-21> , UMA telecon 2021-10-28 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-10-28> , UMA telecon 2021-11-04 <https://kantarainitiative.org/confluence/display/uma/UMA+telecon+2021-11-04> Deferred *The Kantara All members meeting is Dec 8th, 11-1230ET (it's virtual, link TBD)* Delegation Use Cases Reviewed more pp2pi <https://www.drummondgroup.com/pp2pi/> use-cases, broken down by objective and mapped to whther uma or uma delegation can meet the goal Will continue this discussion next week - payer insurance codes are often opaque to the patient/covered person Proof of Chain of Possession (POCOP) Tokens https://github.com/uma-email/poc A client can use any IDToken with any UMA ticket. The Correlated Authorization mechanism ensures that there is some open UMA transactional context included in any pushed ID claims What is the threat that Proof of Possession <https://datatracker.ietf.org/doc/html/draft-ietf-oauth-dpop-04> (or mTLS) doens't address that requires the "chronological tamper-resistant record"? Report on FHIR Vulns reviewed some initial diagrams for this: https://docs.google.com/presentation/d/1aDTD6nv5vza8gDsSRGV6X5tzRoQdIv5V9aU… - FHIR itself is simply the data model - FHIR had the author refine their statement that it was 'FHIR Implmentations' that had the vulnerabilities - SMART on FHIR is the HL7 'approved' authorization strategy - UDAP → artifacts that needs to exist from a trust framework to support DCR/wide-access - HEART → profiles of OAuth/UMA for SMARTonFHIR scopes AOB - We are planning a 3 hour working session on December 9th, we will use extend the normal call from 930-1230ET - Want to make progress on some of the in-progress docs, have them in a consistent state - Eve, Nancy, Alec, Andi - If you're up to attend, please email Alec, or leave a comment on these minutes Topic Candidates (from previous telcons) - Delegation and Guardianship - Outcome of user stories discussion - PDP architecture includes the concept of governance registry/discovery - TOIP/SSI are starting to define this ecosystem function - ANCR records update - Privacy as Expected/ANCR update : 2/3 weeks out (Sal?) 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. Alec Non-voting participants: 1. Scott G 2. Scott F Regrets: 1. Sal 2. Nancy 3. Eve

3 4