[Openid-specs-heart] scope of work

[Tom Jones]

First - i fundamentally agree with Justin's request that HEART needs to
find a purpose that aligns with the needs of the market - His assertion was
more of the type that HEART got no tracktion the last time around.
There are two way to approach this:
1. find a business purpose
2. find a set of appropriate use cases with problems that need to be solved.
I would recommend #2 - lets build use cases based on needs.
I have started a potential list of use cases that could be a starting point.
I am strongly opposed to the current approach of looking at
solutions (FAPI, UMA, whatever) before we understand what value we can
contribute.

wrt Justin's proposal on TXAUTH to HEART - i note one missing element -
specifically  how does the requesting site tell the sending site what data
they want in a manner that permits the user to accept or request the
request. I do not believe that a list of FHIR data elements is something
that the user could evaluate. If we want to put the user in control, we
must provide the user a choice that they can understand. I can share the
Kantara doc on patient choice if that is desired. TXAuth does not currently
do that, but could be adapted to do it.

Peace ..tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20200429/d0fa6e44/attachment.html>