<div><div dir="auto">As referenced on the <a href="http://openid.net/wg/heart">openid.net/wg/heart</a>. Addition items on resource page referenced below</div></div><div dir="auto"><br></div><div dir="auto"><h2 style="margin:11px 0px;font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;line-height:40px;color:rgb(90,90,90);font-size:32px">Additional Resources</h2><p style="margin:0px 0px 11px;color:rgb(90,90,90);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">The US Office of the National Coordinator for Health Information Technology (ONC for Health IT) lists HEART as a <a href="https://www.healthit.gov/topic/standards-technology/health-it-standards" style="color:rgb(247,140,64);text-decoration:none">Health IT Standard to Watch</a>, and sponsored a two-hour webinar/workshop on 23 April 2019. <a href="https://www.healthit.gov/sites/default/files/page/2019-05/ONCHeartWebinarCombined.pdf" style="color:rgb(247,140,64);text-decoration:none">Slides</a> and a <a href="https://www.youtube.com/watch?v=8wpYVQDvYJI&feature=youtu.be" style="color:rgb(247,140,64);text-decoration:none">recording</a> are available.</p><p style="margin:0px 0px 11px;color:rgb(90,90,90);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">The HEART Work Group co-chairs presented on Emerging Identity Standards in Healthcare at the Identiverse conference in June 2018 (<a href="http://openid.net/wordpress-content/uploads/2018/07/Emerging-Standards-in-Healthcare-Identiverse-2018-06-27-rev-2.pdf" style="color:rgb(247,140,64);text-decoration:none">slides</a>, <a href="https://www.youtube.com/watch?v=vOypRbpn004" style="color:rgb(247,140,64);text-decoration:none">video</a>).</p><p style="margin:0px 0px 11px;color:rgb(90,90,90);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">The group has written the following use cases to crystalize key needs in patient-directed health data exchange and how HEART can contribute to the solution:</p><ul style="padding:0px 5px;margin:0px 0px 11px 25px;color:rgb(90,90,90);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px"><li style="line-height:22px"><a href="http://openid.net/wordpress-content/uploads/2018/07/AliceSharesClinicalRecordsWithHerSpouse.pdf" style="color:rgb(247,140,64);text-decoration:none">Alice Shares Clinical Records With Her Spouse</a></li><li style="line-height:22px"><a href="http://openid.net/wordpress-content/uploads/2018/07/HEART-Use-Case_-Alice-and-Spouse.pdf" style="color:rgb(247,140,64);text-decoration:none">Alice Shares Health Data With Her Spouse</a></li><li style="line-height:22px"><a href="http://openid.net/wordpress-content/uploads/2018/07/HEART-Use-Case-Alice-electronically-shares-data-from-her-PHR.pdf" style="color:rgb(247,140,64);text-decoration:none">Alice Electronically Shares Data From Her PHR</a></li><li style="line-height:22px"><a href="http://openid.net/wordpress-content/uploads/2018/07/Health-IoT-use-case.pdf" style="color:rgb(247,140,64);text-decoration:none">Patient Shares Data From Her Health IoT Device to Her Clinician</a></li></ul><p style="margin:0px 0px 11px;color:rgb(90,90,90);font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:14px">Additional information can be found on our <a href="http://openid.net/wg/heart/resources/" style="color:rgb(247,140,64);text-decoration:none">Resources page</a>.</p></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 29, 2020 at 3:10 PM Tom Jones <<a href="mailto:thomasclinganjones@gmail.com">thomasclinganjones@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">please send a point to the use cases<br clear="all"><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div>Peace ..tom</div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 29, 2020 at 11:55 AM Debbie Bucci <<a href="mailto:debbucci@gmail.com" target="_blank">debbucci@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">Forwarding response to group</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Debbie Bucci</strong> <span dir="auto"><<a href="mailto:debbucci@gmail.com" target="_blank">debbucci@gmail.com</a>></span><br>Date: Wed, Apr 29, 2020 at 2:53 PM<br>Subject: Re: [Openid-specs-heart] scope of work<br>To: Tom Jones <<a href="mailto:thomasclinganjones@gmail.com" target="_blank">thomasclinganjones@gmail.com</a>><br></div><br><br><div><div dir="auto">Tom</div></div><div dir="auto"><br></div><div dir="auto">Have you spent time on the HEART WG website? We have listed a number of use cases that have yet to be resolved. Hesitant to start from scratch. I am personally interested in FAPI because of its much more secure , has production traction for read and write transactions. HEART was criticized for being too tough to implement yet the open banking regulations helped move the FAPI work along. </div><div dir="auto"><br></div><div dir="auto">A request for data has an associated token from the user in advance - existing implementation have defaulted to a broad yes/no because of the work to permit such fine grain access.</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 29, 2020 at 2:47 PM Tom Jones <<a href="mailto:thomasclinganjones@gmail.com" target="_blank">thomasclinganjones@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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.<div>There are two way to approach this:</div><div>1. find a business purpose</div><div>2. find a set of appropriate use cases with problems that need to be solved.</div><div>I would recommend #2 - lets build use cases based on needs.</div><div>I have started a potential list of use cases that could be a starting point.</div><div>I am strongly opposed to the current approach of looking at solutions (FAPI, UMA, whatever) before we understand what value we can contribute.</div><div><br></div><div>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.</div><div><br></div><div><div><div dir="ltr"><div dir="ltr"><div>Peace ..tom</div></div></div></div></div></div>
_______________________________________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br>
</blockquote></div></div>
</div></div>
_______________________________________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br>
</blockquote></div>
</blockquote></div></div>