<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
In today's call I asked a question regarding the persistence of
end-user identification credentials. Some of the ones being
discussed, e.g., driver's license, credit card, e-mail address,
etc., have a significant likelihood of changing between patient
visits. End-users are also likely to fail to remember what
credentials were used previously.<br>
<br>
Given this, should HEART have a constraint on the persistence of
end-user credentials?<br>
<br>
There may be similar issues with client systems maintaining current
credentials. <br>
<div class="moz-signature">
<p><b>Glen F. Marshall</b><br>
Consultant<br>
Security Risk Solutions, Inc.<br>
698 Fishermans Bend<br>
Mount Pleasant, SC 29464<br>
Tel: (610) 644-2452<br>
Mobile: (610) 613-3084<br>
<a class="moz-txt-link-abbreviated" href="mailto:gfm@securityrs.com">gfm@securityrs.com</a><br>
<a class="moz-txt-link-abbreviated" href="http://www.SecurityRiskSolutions.com">www.SecurityRiskSolutions.com</a></p>
</div>
<div class="moz-cite-prefix">On 6/28/15 08:42, Debbie Bucci wrote:<br>
</div>
<blockquote
cite="mid:CAG6zQ1Ygjom3Bbvf34891Q+VZEG57NqHot5=9SmLhsQG1VFygQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div dir="ltr">
<div><b style="font-size:13px"><span
style="font-family:Times;font-size:10pt"><br>
When: 1 PM PST/4 PM EST</span></b>
<p class="MsoNormal" style="font-size:13px"><b><span
style="font-family:Times;font-size:10pt">Where:
Gotomeeting – </span></b><span
style="font-family:Times;font-size:10pt"><a
moz-do-not-send="true"
href="https://global.gotomeeting.com/join/785234357"
target="_blank"><span style="color:blue">https://global.gotomeeting.com/join/785234357</span></a></span></p>
<p class="MsoNormal" style="font-size:13px"><span
style="font-family:Times;font-size:10pt"><b>US phone
number</b>: <a moz-do-not-send="true"
href="tel:%2B1%20%28619%29%20550-0003"
value="+16195500003" target="_blank"><font
color="#0066cc">+1 (619) 550-0003</font></a>. Access
Code 785-234-357</span></p>
<p class="MsoNormal" style="font-size:13px"><b> </b><br>
</p>
<p class="MsoNormal" style="font-size:13px"><b><br>
</b></p>
<p class="MsoNormal" style="font-size:13px"><b>Agenda :</b></p>
<ul style="font-size:13px">
<li style="margin-left:15px">Roll call </li>
<li style="margin-left:15px"> PHR or Patient Portal
(client) to PCP or Patient portal (protected resource)
Introduction</li>
<li style="margin-left:15px">AOB</li>
</ul>
<p><br>
</p>
<p>For tomorrow's call, I would like us to focus on the
following assumption/fact: The PHR is already recognized
by the PCP prior to the patient's engagement. <br>
</p>
<p>What are the sequence flows, scopes and policy decisions
that need be prearranged/agreed upon to support the
following during the patient registration process:<br>
</p>
<ul>
<li>Update the patient portal from her PHR.</li>
<li>Update her PHR from the patient portal</li>
<li>Sync the patient portal with her PHR.</li>
</ul>
<p> <br>
</p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openid-specs-heart mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.openid.net</a>
<a class="moz-txt-link-freetext" href="http://lists.openid.net/mailman/listinfo/openid-specs-heart">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a>
</pre>
</blockquote>
<br>
</body>
</html>