[Openid-specs-heart] Please VOTE before Election Day: What’s hindering adoption of HEART?

[Adrian Gropper]

Debbie,

It would be really valuable to HEART if you could share the list of
possible votes with VA, CMS, and All of Us and try to answer from their
perspective as data holders and public servants.

For example, All of Us has an official policy of sharing data with the
patients that contribute. Patients are being asked to volunteer. Setting a
good example for patient-directed exchange could make a difference on
whether Patient Privacy Rights and other patient groups promote All of Us
or not.

Where is the federal health architecture with respect to HEART?

Adrian

On Wed, Nov 1, 2017 at 9:54 AM Debbie Bucci <debbucci at gmail.com> wrote:

> I doubt the dstu version makes any difference when it comes to securing
> API.  Much of early FHIR work is in trusted environments.  Where is there
> major exchange happening today?
>
>  I would like to think the work has influenced other areas.
>
> UMA 2.0 is more directly OAUTH like in it flow.
>
> Current SMART profiles have been updated to reference jwt and support
> dynamic client discovery
>
> EHRs realize they need to know who is making the request and some cases
> are implementing OIDC connect
>
> And most importantly ...there is a growing need/desire to look past the
> provider to provider to patient mediated exchange
>
> If folks could just get past stating it too hard-complicated ( because
> well ...its multiple standards/protocols) and take the time to digest ,
> react to what's there ...if that in some way influences what is actually
> implemented in the long run ...its been worth the time energy/ resources
> spent.
>
>
> --

Adrian Gropper MD

PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
DONATE: https://patientprivacyrights.org/donate-3/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20171101/53b1b2e2/attachment.html>