<div dir="ltr">I actually think we're coming close to a happy medium (or something) with what Nancy is proposing, with the sentiment that others are expressing in the thread, and with candidate text that's appearing in our spec drafts now.<div><br></div><div>Let us assume for a moment that tags (applied by an RS) that obscure what information is "behind" them (such as "this is highly sensitive" without revealing the categories considered sensitive, or "PSY" without spelling out "Psychiatry Related") could receive UX assistance. The cool thing about the ability for a resource owner to control sharing is that such scopes are just <i>made available</i> for Alice's use over at the AS. There's a separation of concerns; the RS can mark the resources during registration, but Alice still gets to control access based on the markings if she feels like it.<br><div><br></div><div>And note that we've made a bit of progress since Nancy and I first discussed the topic and put together the initial proposal wording, which flagged potential technical issues. Justin was able to translate our WG discussions into some text, which I recommend we look at specifically to see if we want to change it. I, for one, think it's technically viable.</div><div><br></div><div><b>First:</b> OAuth+FHIR Sec 3 and Sec 4: <a href="http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-fhir-oauth2.xml#rfc.section.3">http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-fhir-oauth2.xml#rfc.section.3</a></div><div><br></div><div>Specifically, see the listings of <font face="monospace, monospace">conf/N</font> and so on, and also "Additional confidentiality and sensitivity scopes can be defined by [[ IANA or other registry process ]]."</div></div><div><br></div><div>This section defines five <b>specific</b> OAuth scopes (with a sixth in the next section), and an <b>extension</b> mechanism by which any additional set of scopes can be used from an external specification. (The mechanism is to be determined...) Does it look like this would work for OAuth?</div><div><br></div><div><b>Second:</b> UMA+FHIR Sec 2.2: <a href="http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-fhir-uma.xml#rfc.section.2.2">http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?modeAsFormat=html/ascii&url=https://bitbucket.org/openid/heart/raw/master/openid-heart-fhir-uma.xml#rfc.section.2.2</a></div><div><br></div><div>Specifically, this language: "Additionally, the resource MAY use any of the scopes defined in [HEART.OAuth2.FHIR] regarding confidentiality, sensitivity, or emergency (break the glass)."<br></div><div><br></div><div>This section enables usage of scopes in UMA of any of the cross-cutting OAuth scopes defined in (or through) Sections 3 and 4 in the OAuth+FHIR spec. Does it look like this would work for UMA?</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" 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"><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 +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl</p></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Sun, Mar 26, 2017 at 5:02 PM, Debbie Bucci <span dir="ltr"><<a href="mailto:debbucci@gmail.com" target="_blank">debbucci@gmail.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><div><div><div>We are trying to finish up the final semantic profile.<br></div>HEART profiles does not deal with UI issues<br></div>Nor would it define how to technical information is tagged. <br><br></div>That said, if a resource server is able to tag information - perhaps the AS should be aware. <br><br></div><div>I thought John originally suggested we should start focus on the confidentiality code as a start - and I think that is what Nancy is suggesting - with a bit more context.<br><br></div><div>Terminology may not be perfect and cover all use cases but certainly there is a use case or two that we could give examples for. The two that Nancy suggest - seem general enough for a good start. Odds are that patient would understand and could express the level of data (confidentiality code) to release.<br><br>ETH – Substance Abuse<br><br>PSY – Psychiatry Related <br><br>I have to keep reminding myself that This dance would ONLY occur if the RS relayed to the AS it will support it. <br></div><div><br></div><span style="color:rgb(31,73,125)"></span><span style="color:rgb(31,56,100)"></span><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="m_-2862754954992421015gmail-HOEnZb"><div class="m_-2862754954992421015gmail-h5"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="m_-2862754954992421015gmail-m_-1616606062922701620m_6680531488399435593WordSection1"><div><div><div><div><div><div><table class="m_-2862754954992421015gmail-m_-1616606062922701620m_6680531488399435593MsoNormalTable" style="border-collapse:collapse" cellspacing="0" cellpadding="0" border="0"><tbody><tr style="height:1pt"><td colspan="2" style="width:256.7pt;padding:0in 5.75pt;height:1pt" width="428" valign="top"><br></td></tr><tr style="height:1pt"><td style="width:1.45in;padding:0in 5.75pt;height:1pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt;height:1pt" width="254" valign="top"><br></td></tr><tr style="height:1pt"><td style="width:1.45in;padding:0in 5.75pt;height:1pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt;height:1pt" width="254" valign="top"><br></td></tr><tr style="height:1pt"><td style="width:1.45in;padding:0in 5.75pt;height:1pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt;height:1pt" width="254" valign="top"><br></td></tr><tr style="height:1pt"><td style="width:1.45in;padding:0in 5.75pt;height:1pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt;height:1pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td colspan="2" style="width:256.7pt;padding:0in 5.75pt" width="428" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td style="width:1.45in;padding:0in 5.75pt" width="174" valign="top"><br></td><td style="width:152.3pt;padding:0in 5.75pt" width="254" valign="top"><br></td></tr><tr><td colspan="2" style="width:256.7pt;padding:0in 5.75pt" width="428" valign="bottom"><br></td></tr></tbody></table></div></div></div></div></div></div></div></div></blockquote></div></div></div></div>
</blockquote></div></div></div>
<br>______________________________<wbr>_________________<br>
Openid-specs-heart mailing list<br>
<a href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.<wbr>openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" rel="noreferrer" target="_blank">http://lists.openid.net/<wbr>mailman/listinfo/openid-specs-<wbr>heart</a><br>
<br></blockquote></div><br></div>