<div dir="ltr">Hi Eve,<div><br></div><div>It would seem that we would indeed have this figured out. But reality is that we never quite talk about it so bluntly, mostly because classifying healthcare data is so very hard. Further the various ways that would be logical don't fall nicely upon the logical ways that data can be segmented. That is the way that people would like to segment their data is according to how sensitive it is; yet this doesn't align with FHIR resources, or departments, or function, etc... Plus data changes sensitivity based on current medical knowledge (HIV was very sensitive a few years ago, today it tends to trend closer to normal data).</div><div><br></div><div>So the best I have to offer is the _confidentiality classifications we have in the security-tags: It is a scale that centers around Normal - that group of data that everyone agrees is the typical healthcare data (mathematically normal). Think of it as a risk scale of 6 different risk quantum. All data MUST have one of these values assigned to it.</div><div> <a href="http://hl7-fhir.github.io/v3/ConfidentialityClassification/vs.html">http://hl7-fhir.github.io/v3/ConfidentialityClassification/vs.html</a></div><div><br></div><div>so U, L, M, N, R, V --- definitions are on the page above.<br></div><div><br></div><div>Is this a good solution? NO! but it does exist today.</div><div><br></div><div>More on my blog article</div><div> <a href="https://healthcaresecprivacy.blogspot.com/2015/07/how-to-set-confidentialitycode.html">https://healthcaresecprivacy.blogspot.com/2015/07/how-to-set-confidentialitycode.html</a></div><div>or </div><div> <a href="https://healthcaresecprivacy.blogspot.com/2016/01/fhir-oauth-scope.html">https://healthcaresecprivacy.blogspot.com/2016/01/fhir-oauth-scope.html</a></div><div><br></div><div>John</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">John Moehrke<br>Principal Engineering Architect: Standards - Interoperability, Privacy, and Security<br>CyberPrivacy – Enabling authorized communications while respecting Privacy<br>M +1 920-564-2067<br><a href="mailto:JohnMoehrke@gmail.com" target="_blank">JohnMoehrke@gmail.com</a><br><a href="https://www.linkedin.com/in/johnmoehrke" target="_blank">https://www.linkedin.com/in/johnmoehrke</a><br><a href="https://healthcaresecprivacy.blogspot.com" target="_blank">https://healthcaresecprivacy.blogspot.com</a><br>"Quis custodiet ipsos custodes?" ("Who watches the watchers?")</div></div></div>
<br><div class="gmail_quote">On Sun, Jun 26, 2016 at 11:18 AM, Eve Maler <span dir="ltr"><<a href="mailto:eve.maler@forgerock.com" target="_blank">eve.maler@forgerock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>This message is intended to give shape to our profiling efforts. I apologize in advance if I "step in it" due to my lack of HL7 or FHIR knowledge. :-)</div><div><br></div>Given our <a href="https://bitbucket.org/openid/heart/wiki/Alice_Shares_with_Physicians_and_Others_UMA_FHIR" target="_blank">first sharing scenario</a> (in the latest use case) of providing basic data before a first visit, are there various subsets or supersets of such data, e.g., in different jurisdictions, that Alice would be expected to provide, or one obvious and universally understood data set? I'm guessing that payment data is one subset of data that doesn't apply in some jurisdictions, whereas quite a lot of "medically related data" would generally be considered desirable to share if available.<div><br></div><div>What I'm going for here is: If you could have a system of "keywords" representing virtual clipboard-type data sets and how you want them shared, what's the smallest arrangement of keywords that would do the trick?</div><div><br></div><div>By (very rough) analogy, look at how <a href="http://openid.net/specs/openid-connect-core-1_0.html#ScopeClaims" target="_blank">OpenID Connect standardizes client requests for claims using scope values</a>. It rolls up multiple identity claims under single scope names, so that "openid" gives the client full access at the UserInfo endpoint, "profile" gets access to 14 specific claims, "email" gets access to two claims, etc.</div><div><br></div><div>UMA gives us two dimensions to play with, so it could be like this:</div><div><br></div><div>Potential resource sets to access (I'm totally making this up! for all I know, HL7 figured this out 10 years ago and it doesn't look anything like this...):</div><div><ul><li>BasicVirtualClipboardData<br></li><li>FinancialVirtualClipboardData (or a unique version per jurisdiction?)</li><li>AllVirtualClipboardData (an aggregation of the two of them)</li></ul><div>Potential scopes of action across them (same for each one? it doesn't have to be that way, and other resource sets might have deidentified-read options or something...):</div></div><div><ul><li>read</li><li>write</li></ul></div><div>Note that the scope work already begun in our OAuth FHIR profile, coming from the SMART on FHIR work, gives us ideas for things like a "read" verb and a "write" verb, but for right now, we can think outside the box if that's the right thing to do.</div><span class="HOEnZb"><font color="#888888"><div><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">
<p><b>Eve Maler<br></b>ForgeRock Office of the CTO | VP Innovation & Emerging Technology<br>Cell <a href="tel:%2B1%20425.345.6756" value="+14253456756" target="_blank">+1 425.345.6756</a> | Skype: xmlgrrl | Twitter: @xmlgrrl<br><b>ForgeRock Summits and UnSummits</b> <a href="http://summits.forgerock.com/" target="_blank">are coming to</a> <b>Sydney, London, and Paris!</b></p></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div></font></span></div>
<br>_______________________________________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br>
<br></blockquote></div><br></div>