[Openid-specs-heart] Updated Use Case: Patient Authorizes Clinical Research

Scott Shorter sshorter at kimbleassociates.com
Wed Mar 9 18:54:23 UTC 2016

Hello Glen,

Looks good, but I am confused about the de-identification and re-identification process.  The diagram shows a “reidentification engine” - what’s the concept of operations for that?  Does the de-identification process include registering with one of these engines to enable re-identification?  Or is the de-identification assumed to be reversible?

Is this explained in the ISO/TS 25237 document referenced in footnote 2?  I’m not familiar with that, I will confess that most of what I know about de-identification I learned from NISTIR 8053 (http://nvlpubs.nist.gov/nistpubs/ir/2015/NIST.IR.8053.pdf).


On Mar 4, 2016, at 12:12 PM, Glen Marshall [SRS] <gfm at securityrs.com<mailto:gfm at securityrs.com>> wrote:


An updated draft for the use case is attached.  It reflects our discussions in February, excluding any tangential issues.  I appreciate your collective help in advancing this work.


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

<UseCase - Patient Authorizes Clinical Research - DRAFT - GFM 2016-03-04.pdf>_______________________________________________
Openid-specs-heart mailing list
Openid-specs-heart at lists.openid.net<mailto:Openid-specs-heart at lists.openid.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20160309/9e5e7161/attachment-0001.html>

More information about the Openid-specs-heart mailing list