[Openid-specs-heart] CHIME Launches $1M Challenge to Solve Patient ID Problem

[Glen Marshall [SRS]]

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.

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 halting problem 
<https://en.wikipedia.org/wiki/Halting_problem>.)

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.

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.


/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.//
//
//http://www.healthdatamanagement.com/news/chime-launches-1m-challenge-to-solve-patient-id-problem/
-- 

*Glen F. Marshall*
Consultant
Security Risk Solutions, Inc.
698 Fishermans Bend
Mount Pleasant, SC 29464
Tel: (610) 644-2452
Mobile: (610) 613-3084
gfm at securityrs.com
www.SecurityRiskSolutions.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20160124/406e9864/attachment.html>