<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">To clarify the objective, we were presenting the first draft of one of the outputs of this working group.<div class=""><br class=""></div><div class="">The HEART working group exists specifically to create these technical specifications. All of the discussions on use cases are intended to drive work on these specifications. </div><div class=""><br class=""></div><div class="">Also, the group should note that the terms “patient” and “user” were imported directly from the Argonauts projects. </div><div class=""><br class=""></div><div class=""> — Justin</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 5, 2015, at 11:31 PM, Kinsley, William <<a href="mailto:BKinsley@nextgen.com" class="">BKinsley@nextgen.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class="">
<meta name="Generator" content="Microsoft Exchange Server" class="">
<!-- converted from rtf -->
<style class=""><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
<div class="">
<font face="Cambria" size="4" class=""><span style="font-size:14pt;" class="">
<div class="">This document was presented quickly during the last few minutes of our call and I am not sure what the objective was. However, it did raise some questions that could not be addressed at the time, specifically paragraph 2.1 “Permission type” raised some
questions which I broke out below: </div>
<ol style="margin:0;padding-left:54pt;" class="">
<li class="">The term “Patient” and “User” seem misleading and the purpose is not clear.</li></ol>
<ol type="a" style="margin:0;padding-left:90pt;" class="">
<li class="">A patient can have access to multiple patient records. For example, a parent who has five children at the same pediatrician would be a patient that can access multiple patient records. </li><li class="">It also sounds like we are hardcoding two specific security roles, which would seem to contradict what we are trying to support in HEART (i.e. RBAC vs ABAC). </li><li class="">There can be resource that are not related to specific patient or patients in general such as “Organization”, “HealthcareService”, “Practitioner”, etc.</li></ol>
<div class=""><font face="Calibri" size="2" class=""><span style="font-size:11pt;" class=""> </span></font></div>
<div class=""><font face="Calibri" size="2" class=""><span style="font-size:11pt;" class=""> </span></font></div>
<div class="">Bill</div>
<div class=""> </div>
<div class=""><font face="Calibri" size="2" class=""><span style="font-size:11pt;" class=""> </span></font></div>
<table width="747" style="width:448.2pt;" class="">
<colgroup class=""><col width="378" style="width:226.8pt;" class="">
<col width="369" style="width:221.4pt;" class="">
</colgroup><tbody class=""><tr class="">
<td class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""> </span></font></td>
<td class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""><img width="145" height="40" src="http://bridge.nextgen.com/Media/3140" class=""></span></font></td>
</tr>
</tbody></table>
<table width="747" style="width:448.2pt;" class="">
<colgroup class=""><col width="747" style="width:448.2pt;" class="">
</colgroup><tbody class=""><tr class="">
<td class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""><u class=""> ________________________________ </u>
<div class=""> </div>
</span></font></td>
</tr>
</tbody></table>
<table width="747" style="width:448.2pt;" class="">
<colgroup class=""><col width="538" style="width:322.8pt;" class="">
<col width="209" style="width:125.4pt;" class="">
</colgroup><tbody class=""><tr class="">
<td class=""><font face="Calibri" size="2" class=""><span style="font-size:10pt;" class="">William Kinsley , CISSP<br class="">
Enterprise Architect, Ambulatory<br class="">
<b class="">NEXTGEN HEALTHCARE<br class="">
</b>Solutions for: Ambulatory, Inpatient and Community Connectivity<br class="">
795 Horsham Road, Horsham, PA 19044<br class="">
(215) 657-7010 x21128 <br class="">
<a href="mailto:BKinsley@nextgen.com" class="">BKinsley@nextgen.com</a></span></font></td>
<td class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""><a href="http://www.oneugm.com/" class=""><img src="http://bridge.nextgen.com/Media/3181" class=""></a></span></font></td>
</tr>
</tbody></table>
<div class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""><br class="">
</span></font></div>
<table width="747" style="width:448.2pt;" class="">
<colgroup class=""><col width="747" style="width:448.2pt;" class="">
</colgroup><tbody class=""><tr class="">
<td class=""><font face="Calibri" size="2" color="#E46C0A" class=""><span style="font-size:10pt;" class="">Be ready for MU and ICD-10 in 2015. Start your EHR version 5.8 and KBM version 8.3 upgrade today. Get the resources you need at <a href="http://www.nextgen.com/upgradecentral" class=""><font color="#007CB9" class=""><b class=""><i class=""><u class="">www.nextgen.com/upgradecentral</u></i></b></font></a></span></font></td>
</tr>
</tbody></table>
<div class=""><font face="Times New Roman" size="3" class=""><span style="font-size:12pt;" class=""><br class="">
</span></font></div>
<table width="747" style="width:448.2pt;" class="">
<tbody class=""><tr class="">
<td class=""><font face="Arial" size="1" class=""><span style="font-size:7.5pt;" class="">This message, and any documents attached hereto, may contain confidential or proprietary information intended only for the use of the addressee(s) named above or may contain information that is
legally privileged. If you are not the intended addressee, or the person responsible for delivering it to the intended addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited. If you have received
this message by mistake, please immediately notify us by replying to the message and delete the original message and any copies immediately thereafter. Thank you for your cooperation.</span></font></td>
</tr>
</tbody></table>
</span></font>
</div>
_______________________________________________<br class="">Openid-specs-heart mailing list<br class=""><a href="mailto:Openid-specs-heart@lists.openid.net" class="">Openid-specs-heart@lists.openid.net</a><br class="">http://lists.openid.net/mailman/listinfo/openid-specs-heart<br class=""></div></blockquote></div><br class=""></div></body></html>