<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>
<div>I appreciate your expertise and action. </div><div><br></div><div>I don't necessarily agree with some of your statements here but that is the beauty of open processes. </div><div><br></div><div>Let's strive to do all we can - together.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><span style="font-size: 15.4224px;">Aaron Seib</span><div><span style="font-size: 17.489px;">@CaptBlueButton<br></span><div dir="auto"><span style="font-size: 15.4224px;" dir="auto">(O) 301-540-9549</span></div><div dir="auto"><span style="font-size: 15.4224px;" dir="auto">(M) 301-326-6843</span></div><div dir="auto"><span style="font-size: 15.4224px;" dir="auto"><br></span></div><div dir="auto"><span style="font-size: 15.4224px;" dir="auto">"The trick to earning trust is to avoid all tricks. Including tricks on yourself."</span></div><div dir="auto"><br></div></div></div><br><br>-------- Original message --------<br>From: "Glen Marshall [SRS]" <gfm@securityrs.com> <br>Date: 2016/01/24 7:07 AM (GMT-08:00) <br>To: HEART List <openid-specs-heart@lists.openid.net> <br>Subject: [Openid-specs-heart] CHIME Launches $1M Challenge to Solve Patient ID Problem <br><br>
This is pertinent to our data-sharing use cases. There is no
current solution to accurately sharing/gathering patients' clinical
data stored among various repositories. In turn, that makes
applying access controls across all of a patient's data in those
repositories difficult. I'm happy to see Chime's challenge.<br>
<br>
However, the related problem of discovering where all of one's data
might be is computationally intractable. It is equally intractable
to gather and combine all access permissions and regulatory
restrictions on patients' data, even if there were a useful means to
do so. (Both are equivalent to the <a href="https://en.wikipedia.org/wiki/Halting_problem">halting
problem</a>.)<br>
<br>
Having a single "source of truth" repository is one direction for a
solution, as is having a single access permissions source. Keeping
them updated with new data and permissions is possible, even if
difficult in the short run.<br>
<br>
However, establishing unique URIs for each patient's data and
permissions is the same as having a universal patient identifier.
That might be subject to current Congressional funding restrictions.
<br>
<br>
<br>
<i>The College of Healthcare Information Management Executives on
Tuesday launched a $1 million National Patient ID Challenge to
develop solutions to ensure 100 percent accuracy of every
patient’s identity to reduce preventable medical errors.</i><i><br>
</i><i><br>
</i><i><a class="moz-txt-link-freetext" href="http://www.healthdatamanagement.com/news/chime-launches-1m-challenge-to-solve-patient-id-problem">http://www.healthdatamanagement.com/news/chime-launches-1m-challenge-to-solve-patient-id-problem</a></i><br>
<div class="moz-signature">-- <br>
<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>
</body></html>