- WG-RIUP - mailman.kantarainitiative.org

Re: RIUP WG 'brief' meeting tomorrow to vote on revisions to the Digital Identifier Inclusion doc.
by Salvatore D'Agostino 06 Aug '24

06 Aug '24

Human (Social) vs. Technical, you need both. Good not to conflate. Good conversation and references. Best, Sal IDmachines 4 Lamson Place Cambridge, MA 02139-2612 +1 617.201.4809 https://IDmachines.com ________________________________ From: Noreen Whysel <nwhysel(a)gmail.com> Sent: Tuesday, August 6, 2024 7:54:52 AM To: peace(a)acm.org <peace(a)acm.org> Cc: jim kragh <kragh65(a)gmail.com>; Salvatore D'Agostino <sal(a)idmachines.com>; Simone Alcorn <salcorn(a)easydynamics.com>; Bev Corwin <bevcorwin(a)gmail.com>; Isha Chhatwal <ichhatwa(a)gmail.com>; Thomas Sullivan <tsullivan(a)drfirst.com>; Jeff Brennan <jeff_brennan(a)sbcglobal.net>; Justin Byrd <justin(a)machi-systems.com>; Jorge Flores <jorge(a)entidad.io>; wg-riup <wg-riup(a)kantarainitiative.org>; Kay Chopard Cohen <kay(a)kantarainitiative.org>; Amanda Gay <amanda(a)kantarainitiative.org> Subject: Re: RIUP WG 'brief' meeting tomorrow to vote on revisions to the Digital Identifier Inclusion doc. I like your explanation, Bev. Most people are probably not thinking about data transfer and digital identifiers. They just want care. Noreen On Aug 6, 2024, at 7:41 AM, Noreen Whysel <nwhysel(a)gmail.com> wrote: Sorry, Tom. I posted that before I saw your note about not knowing what a Trust Relationship is. Here is an example of a definition from ONC: <https://www.healthit.gov/isp/understanding-emerging-api-based-standards> Understanding Emerging API-Based Standards<https://www.healthit.gov/isp/understanding-emerging-api-based-standards> healthit.gov<https://www.healthit.gov/isp/understanding-emerging-api-based-standards> <https://www.healthit.gov/isp/understanding-emerging-api-based-standards> <favicon.ico> * Trust Relationship – For interoperability using FHIR to work, a trust relationship must be established between entities (ie an EHR/clinical system and an app). This is currently being accomplished by establishing siloed ecosystems. Without an established trust relationship, access to information is not possible regardless of the standards used. The Trust Relationship that Jim is talking about is one that is established in interpersonal relationships between an individual and a care team or service provider that does not include a digital certificate. For example, “We have met before.” Do we need to define these two aspects of trust relationship separately? Or do we need a new term for the human to human trust relationship? A reason to define them separately would be to acknowledge that in healthcare and other care situations involving an underserved individual where a digital identity is not available there may be a relationship established in human trust between two individuals that is not certified digitally. Example user scenarios: * A med kit is provided on a work site that employs undocumented workers. * A defib kit used (properly) on an unconscious person at a restaurant. In both cases trust is established between worker or dining customer and the establishment that safe conditions are maintained and that in the event of an emergency qualified care is provided. While establishment trusts that the affected person will be able to use/respond to the equipment or prevent an emergency in the first place. Noreen On Aug 6, 2024, at 7:04 AM, Noreen Whysel <nwhysel(a)gmail.com> wrote: That is helpful, Tom. So to be clear, for the purposes of identification, a Trust Relationship is established in a data transaction once a trust anchor is verified? Ie certificate exists and data is transferred, therefore entity A is now in a Trust Relationship with Entity B. Is this true only in a software transaction or could one diagram it in a human trust relationship that Jim is talking about? It could be that you are talking about something on two very different levels. Noreen On Aug 6, 2024, at 1:42 AM, Tom Jones <thomasclinganjones(a)gmail.com> wrote: The problem with that is that the relationship is defined AFTER the transaction completes, whereas the value in the request is prior to to the formation of the trust relationship. The trust Anchor for health interchange is defined by onc/tefca which cannot be altered or approved by the patient. BTW, that piece was NOT added while I was editing the doc so I cannot justify it. thx ..Tom (mobile) On Mon, Aug 5, 2024, 7:20 PM Noreen Whysel <nwhysel(a)gmail.com<mailto:nwhysel@gmail.com>> wrote: Yes. Do we need to define “trust relationship” in our lists of terms? Can we say that the trust relationship is the human component of assurance in which an individual shares data with a provider they deem trustworthy, and that the trust anchor is the technology component, embodied in a root certificate, for example, that provides identity assurance of the individual? Noreen On Aug 5, 2024, at 9:59 PM, kragh65(a)gmail.com<mailto:kragh65@gmail.com> wrote: Tom, in the healthcare sector, especially in underserved communities a relationship with a nurse, social worker or a non-profit entity or faith based entity serving that community is where relational trust is nurtured and built. In my 20+ years in the healthcare sector, I have never heard the term “trust anchor’ used as it relates to a ‘trusted’ relationship, especially a health care relationship. But understanding you are the DII Editor and there is a taxonomy in the DII that defines what a TA is in that domain, so be it. I am grateful for your leadership and support is making this document a reality, a foundation for a potential project. On be half of our WG collogues and Kantara, thank you. I will support your recommendation. Jim From: Tom Jones <thomasclinganjones(a)gmail.com<mailto:thomasclinganjones@gmail.com>> Sent: Monday, August 05, 2024 8:41 PM To: jim kragh <kragh65(a)gmail.com<mailto:kragh65@gmail.com>> Cc: Noreen Whysel. Brett <nwhysel(a)gmail.com<mailto:nwhysel@gmail.com>>; Salvatore D'Agostino <sal(a)idmachines.com<mailto:sal@idmachines.com>>; Simone Alcorn <salcorn(a)easydynamics.com<mailto:salcorn@easydynamics.com>>; Bev Corwin <bevcorwin(a)gmail.com<mailto:bevcorwin@gmail.com>>; Isha Chhatwal <ichhatwa(a)gmail.com<mailto:ichhatwa@gmail.com>>; Thomas Sullivan <tsullivan(a)drfirst.com<mailto:tsullivan@drfirst.com>>; Jeff Brennan <jeff_brennan(a)sbcglobal.net<mailto:jeff_brennan@sbcglobal.net>>; Justin Byrd <justin(a)machi-systems.com<mailto:justin@machi-systems.com>>; Jorge Flores <jorge(a)entidad.io<mailto:jorge@entidad.io>>; wg-riup <wg-riup(a)kantarainitiative.org<mailto:wg-riup@kantarainitiative.org>>; Kay Chopard Cohen <kay(a)kantarainitiative.org<mailto:kay@kantarainitiative.org>>; Amanda Gay <amanda(a)kantarainitiative.org<mailto:amanda@kantarainitiative.org>> Subject: Re: RIUP WG 'brief' meeting tomorrow to vote on revisions to the Digital Identifier Inclusion doc. as i indicated the last time this came up, I don't know what a trust relationship is or why that would exist. The Trust Anchor is at least defined in the taxonomy. Be the change you want to see in the world ..tom On Mon, Aug 5, 2024 at 5:26 PM jim kragh <kragh65(a)gmail.com<mailto:kragh65@gmail.com>> wrote: I was informed last week that we have a new 'Join Zoom Meeting #:and access code: ATTENTION WE HAVE A N NEW Join Zoom Meeting link: https://us06web.zoom.us/j/87605872193?pwd=HQI7AJKhLvpgtUxKyOYANVUKzsZW3U.1 Meeting ID: 876 0587 2193 Passcode: 157149 A list of call numbers was not provided and if a list of # 's are available I will ask Amanda to share such with us tomorrow morning.. Good evening! The revised DII document link is below and Tom, Sal, Noreen and I again reviewed and addressed items that needed attention that were accepted. The attached DII has a few fine tuning thoughts by Noreen and me for your review, comments and or corrections. Please read the document and be prepared to vote or provide a proxy so we can forward the DII to the LC Chair; thank you. The Kantara Leadership Council will be meeting next week, and if tomorrow our WG accepts changes made, we should be able to place the DII in their hands for a final review and acceptance. Once that is accomplished, maybe we can find a funding source and a demonstration partner. Tom shared with us a Homeland Security notice of six 'wallet' projects DHS was funding; surely there are others out there - let's discuss.. Have a nice evening, Jim Kantara RIUP WG Digital Identifier Inclusion Draft 9 5 15 24_ENDORSED.docx<https://docs.google.com/document/d/1jaY6yNopxCFC_3sBgeddnmM1psVkLmnS/edit?u…>

1 0

Updated invitation: RIUP WG @ Every 2 weeks from 1pm to 2pm on Tuesday from Tue Aug 6 to Mon Nov 11 (EDT) (wg-riup@kantarainitiative.org)
by Kantara Initiative 30 Jul '24

30 Jul '24

This event has been updated Changed: location, description RIUP WG Every 2 weeks from 1pm to 2pm on Tuesday from Tuesday Aug 6 to Monday Nov 11 Eastern Time - New York Location https://us06web.zoom.us/j/87605872193?pwd=HQI7AJKhLvpgtUxKyOYANVUKzsZW3U.1 https://www.google.com/url?q=https%3A%2F%2Fus06web.zoom.us%2Fj%2F8760587219… Zoom info updated for August 2024Resilient Identifiers for Underserved Populations (RIUP) Work Group - Meeting weekly on the first and third Tuesday's at 1PM ESTTopic: RIUPJoin Zoom Meetinghttps://us06web.zoom.us/j/87605872193?pwd=HQI7AJKhLvpgtUxKyOYANVUKzsZW3U.1Meeting ID: 876 0587 2193Passcode: 157149Topic: RIUP Working GroupTime: Sep 19, 2023 01:00 PM Eastern Time (US and Canada) Every 2 weeks on Tue, until Nov 28, 2023, 6 occurrence(s) Sep 19, 2023 01:00 PM Oct 3, 2023 01:00 PM Oct 17, 2023 01:00 PM Oct 31, 2023 01:00 PM Nov 14, 2023 01:00 PM Nov 28, 2023 01:00 PMPlease download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://us06web.zoom.us/meeting/tZMpfuCppz8tHNVQbiIRnAIOWuTndZJ8mbJV/ics?ic… tap mobile+13052241968,,87499194761#,,,,*837815# US+13092053325,,87499194761#,,,,*837815# US---Dial by your location• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 301 715 8592 US (Washington DC)• +1 253 205 0468 US• +1 253 215 8782 US (Tacoma)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 669 444 9171 US• +1 689 278 1000 US• +1 719 359 4580 US• +1 720 707 2699 US (Denver)• +353 1 536 9320 Ireland• +353 1 653 3895 Ireland• +353 1 653 3897 Ireland• +353 1 653 3898 Ireland• +353 6 163 9031 Ireland• +353 1 240 8941 Ireland• +39 021 241 28 823 Italy• +39 069 480 6488 Italy• +39 020 066 7245 Italy• +1 438 809 7799 Canada• +1 587 328 1099 Canada• +1 647 374 4685 Canada• +1 647 558 0588 Canada• +1 778 907 2071 Canada• +1 780 666 0144 Canada• +1 204 272 7920 Canada• +61 8 7150 1149 Australia• +61 2 8015 6011 Australia• +61 3 7018 2005 Australia• +61 7 3185 3730 Australia• +61 8 6119 3900 Australia• +43 72 011 5988 Austria• +43 120 609 3072 Austria• +43 12 535 501 Austria• +43 12 535 502 Austria• +43 670 309 0165 Austria• +44 203 481 5237 United Kingdom• +44 203 481 5240 United Kingdom• +44 203 901 7895 United Kingdom• +44 208 080 6591 United Kingdom• +44 208 080 6592 United Kingdom• +44 330 088 5830 United Kingdom• +44 131 460 1196 United KingdomMeeting ID: 874 9919 4761Passcode: 837815Find your local number: https://us06web.zoom.us/u/kc6npe25Uy Guests nwhysel(a)gmail.com kragh65(a)gmail.com Kantara Staff armin(a)kantarainitiative.org thomasclinganjones(a)gmail.com Kay Chopard ichhatwa(a)gmail.com wg-riup(a)kantarainitiative.org Salvatore D'Agostino amanda(a)kantarainitiative.org View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=MTExZDk2ZnY2ZTMy… Reply for wg-riup(a)kantarainitiative.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=MTExZDk2ZnY2ZTMy… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. To stop receiving future updates for this event, decline this event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 0

NIST Resources
by Salvatore D'Agostino 29 Jul '24

29 Jul '24

https://www.digitalbenefitshub.org/about Interesting that this is being represented as public benefit. Very much in line with ANCR transparency performance specification as public resource for digital transparency/trust IDmachines 4 Lamson Place Cambridge, MA 02139-2612 +1 617.201.4809 https://IDmachines.com

1 0

Hhs onc reorg
by Tom Jones 25 Jul '24

25 Jul '24

National Coordinator Micky Tripathi will be named Assistant Secretary for Technology Policy/National Coordinator for Health Information Technology. In response to the President’s Executive Order on Safe, Secure, and Trustworthy AI, Assistant Secretary Tripathi has also been named the department’s Acting Chief AI Officer. ASTP/ONC has launched a search to fill the permanent positions of Chief Technology Officer, Chief AI Officer, and Chief Data Officer to build dedicated talent for this vital team. ASTP/ONC will host a webinar about these opportunities on August 1, 2024 at 12:00pm ET. Interested parties can register at https://www.zoomgov.com/webinar/register/WN_HyKwXML0T06QCH40KRXqbQ#/registr… . “ONC already plays a critical role in health IT across our agencies and with industry. This reorganization builds on those capabilities to advance all our strategic, mission-focused technology, data, and AI policies and activities,” said HHS Deputy Secretary Andrea Palm. “These organizational changes will ensure that HHS is best situated to serve the American people during this incredibly dynamic time in the technology space.” Additional information about this organizational change can be found on the Federal Register . https://www.federalregister.gov/public-inspection/2024-16571/statement-of-o… thx ..Tom (mobile)

2 1

DHS privacy enhancing grants
by Tom Jones 25 Jul '24

25 Jul '24

https://www.dhs.gov/science-and-technology/news/2024/07/08/homeland-securit… thx ..Tom (mobile)

1 0

Hi assurance dids
by Tom Jones 23 Jul '24

23 Jul '24

https://www.ietf.org/archive/id/draft-carter-high-assurance-dids-with-dns-0… thx ..Tom (mobile)

1 0

we had the chance to get ahead of the inclusion problem
by Tom Jones 19 Jul '24

19 Jul '24

But everyone else is getting there ahead of us. and with a worse answer. ustpc-mandatory-accessibity-standards-statement.pdf (acm.org) <https://www.acm.org/binaries/content/assets/public-policy/ustpc-mandatory-a…> ..tom

1 0

CANCILED : RIUP WG meeting for July, next WG meeting will be August 6, 2024, 1PM EDT
by jim kragh 15 Jul '24

15 Jul '24

I was notified that the Leadership Council was canceling their July meeting for a Summer break so the RIUP WG will do the same. Enjoy family and friends; BE SAFE, look forward to linking up with you August 6, 2024; 1 PM; EDT (will send a reminder). Jim

1 0

Reminder: RIUP WG meeting tomorrow, July 2nd, 1 PM EDT final approval of the DII document changes
by jim kragh 02 Jul '24

02 Jul '24

https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Meeting ID: 874 9919 4761 *Passcode: 837815* Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 Good evening to all! After our last WG meeting, having discussed feedback from the Leadership Council, Sal and I reviewed the forward page of the Digital Identifier Inclusion document and specifically the Abstract section. We tagged teamed, with me taking the first step in putting pen to paper and then exchanged content; Sal was spot on in keeping the theme simple and to the point. Now it is your turn to contribute to the final *Abstract *content with the goal being that we will have a majority WG acceptance of the DII document. A short time ago, Sal requested some time to share some other minor changes for consideration. Yes that is acceptable and will also include others on the call, keeping in mind such recommendations are minor; not content change -this document has been review by the Leadership Council *Abstract:* This document is based on the principle that all humans with rights or privileges should have access to digital identifiers and the means to use those rights and privileges. This must be required in our increasingly connected world to support the underserved. Examples of harm and inefficiencies from the exclusion to digital resources are briefly described, along with solutions, in the pages that follow. This report presents requirements for Digital Public Infrastructure (DPI), with digital identifier inclusion by default in design, deployment, use and maintenance over its lifecycle.. Have a restful evening, JIm

3 2

FW: [privacyframework] Concept Paper Release and More Updates for the Privacy Framework 1.1 + Data Governance and Management Profile Workshop!
by Salvatore D'Agostino 18 Jun '24

18 Jun '24

From: privacyframework <privacyframework(a)list.nist.gov> Sent: Tuesday, June 18, 2024 12:28 PM To: privacyframework <privacyframework(a)list.nist.gov> Subject: [privacyframework] Concept Paper Release and More Updates for the Privacy Framework 1.1 + Data Governance and Management Profile Workshop! Dear Colleagues,    We have released concept papers for the NIST Privacy Framework (PF) Version 1.1 update as well as the Data Governance and Management (DGM) Profile. These concept papers will support discussion sessions at next week’s hybrid workshop. We encourage you to familiarize yourself with the material prior to participating in the workshop. If you would like to provide informal feedback on this material in addition to or in lieu of participating in the workshop, please send it to privacyframework(a)nist.gov<mailto:privacyframework@nist.gov> by July 31, 2024. We have also extended the deadline for in-person registration only to 11:59 PM EDT on Thursday, June 20. Please be aware that breakout sessions are filling up quickly for in-person participants, so please register as soon as possible, if you have not already. Registration is free and required for this event. Event registration, agenda, speakers, and other workshop information is available here<https://www.nist.gov/news-events/events/2024/06/ready-set-update-privacy-fr…>. If you have any questions, please email us at privacyframework(a)nist.gov<mailto:privacyframework@nist.gov>. We look forward to seeing you next week! Best, NIST Privacy Framework Team -- To unsubscribe, email privacyframework+unsubscribe(a)list.nist.gov<mailto:privacyframework+unsubscribe@list.nist.gov> Visit this group at https://list.nist.gov/privacyframework To unsubscribe from this group and stop receiving emails from it, send an email to privacyframework+unsubscribe(a)list.nist.gov<mailto:privacyframework+unsubscribe@list.nist.gov>.

1 0