Coordinate with HEART working group at OpenID Foundation, so we don’t compete.
Two focus activities/solutions
In particular look at the information that is created in a High Assurance ID Token that would address the needs of both the TEFCA requirement for high-assurance as well as the needs for self-sovereign identifiers.
In particular focus on how the patient can know that any given web site can be trusted with their protected health information (PHI). A good approach might be to enable the Entity Statement of the OpenID federation specification.
From the user perspective dynamic registration of HIPAA compliant web sites should not be allowed as a web site either has a current certificate or it does not,
Adopt a paradigm shift to documents that are problem oriented rather than solution oriented. For example the FAPI specifications of the OpenID foundation is oriented to solutions for financial payments from users.
Focus only on new specifications that feature the goals of the Cares Act, such as giving the Patient Choice in how their information is accessed,
Third task is more housekeeping
Bring up a GitHub repository and deprecate the bitbucket repository.
Proposes a liaison between the two committees.
Vote to allow Tom to serve as liaison to HEART. Unanimously passed.
Their next meeting is March 23. Jim will attend as well.
Former user (Deleted) will send document to team with comments Wed, agreement by Thursday. Sal will work on it with her. Then Sal can present to board.
Salvatore D'Agostino to present funding proposal at next board meeting, March 23. Jim will attend