2020-01-07 Meeting notes

Standards updates 

Jim Kragh

Jim shared some high-level information about CARIN code requirements and new Federal requirements for 800-63 and authenticated digital identities.  

Vote to Reaffirm Distributed Identity Assurance Specification

@Salvatore D'Agostino (Unlicensed)  

Motion to reaffirm the approved Draft 1, “Distributed Identity Assurance Specification” was made by Sal and seconded by Jim.

All voted in favor for reaffirming.

Distributed Identity Assurance Specification

Issues

@Tom Jones

Tom talked about the working Draft 2 on Github and led us through 6 issues. The first two issues were raised by Tom and the last 4 were raised by Colin Wallis.

• Issue #1 - Include some of concepts from OpenID Identity Assurance doc. Tom made suggestion “I suggest we pick a placeholder for the name that we can use to identify the US healthcare ecosystem until a formal name is assigned.”  Agreed to use title – US Healthcare Assurance Framework.

• Issue #2 - Lots of identifiers make tracking any transaction difficult even for architects.  Agreed to add non-normative section to explain to user how this works. Tom went through his suggestions.

• Issue #3 - Last sentence of Abstract could be clearer. Tom covered clarifying language.

• Issue # 4 - Add link for applicable IPR option for the FIRE WG.  Agreed to change link following review by Jeff.

• Issue # 5 - Add Consent Receipt (CR) to Abbreviations list. Tom added consent receipt.

• Issue # 6 - SSN last 4 digits. This was raised due to privacy/security issues.  Per Jim, the VA system uses last 4 digits. Tom added language to illustrate that the screen shot a non-normative example.  Mary discussed the issue around use of last 4 social sec digits and driver’s license noting that discussions about moving away from last 4 digits had been going on for years but there did not appear to be a universal solution at this point.