<div dir="ltr"><div>Thank you Eve!! I hope we can reach consensus on something like the format you present.<br><br>Narratives are much easier to understand when they begin with a clear statement of the problem. Shouldn't use cases be asked to clearly state the problem they are trying to solve right up front? <br><br></div><div>This particular use-case seems to be trying to solve some or all of three problems: federated sign-in, eliminating the registration clipboard hassle, and updating a PHR with encounter results. All of these can be solved by OAuth alone.<br><br></div><div>If the problem is to begin HEART with a patient-centricity as the problem, then this particular use-case distorts the discussion by presuming Alice wants a PHR and diminishes the patient-centered benefits of UMA as a health information exchange technology.<br><br></div><div>I've tried to clarify these fundamental issues in my comments on the document and hope we can resolve this before we move on to semantic profiling and scopes.<br></div><div><br></div>Adrian<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 1, 2015 at 3:32 PM, Id Coach <span dir="ltr"><<a href="mailto:coach@digitalidcoach.com" target="_blank">coach@digitalidcoach.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Thanks Eve,<br>
<br>
This is wonderful. I questioned/commented on things only a newbie is
likely to ask/care about. <br>
<br>
It's also a useful template for other use cases. To your point about
explaining oAuth and other template terms, you're using a new
language and a new ecosystem to many, so I encourage those template
terms to be explained over and over again as needed and as
appropriate.<br>
<br>
It will be helpful to me to illustrate or diagram this process. I'll
take a crack at that in the next few days (I hope).<br>
<br>
judi<div><div class="h5"><br>
<br>
<div>On 8/1/15 11:20 AM, Eve Maler wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Completing my action item, you'll find our
(well-worn :-) use case document <a href="https://docs.google.com/document/d/1IvbdWerdvMuA1dQ-KQvVKqIBrAas7FoenNVUtgpqYrw/edit?usp=sharing" target="_blank">here</a>.
Following is my proposal. If we like what I've done here, I
recommend that we:
<div>
<div>
<ul>
<li>Edit the doc title to match the use case title I've
supplied (just below the horizontal line).</li>
</ul>
<ul>
<li>Resolve all the comments above my title (fear not,
they're all accounted for in the comments I've inserted)
and delete all the text above that point (I've retained
all our existing text above the line, just in case).</li>
</ul>
<ul>
<li>Resolve all the comments I've inserted -- as quickly
as possible! We don't have to take up call time to do
the minor ones, if people take the initiative to review
them offline and supply their feedback as responses to
this note. Note that, in this new template, I have
avoided the use of the comment mechanism for anything
that should be a permanent part of the document.</li>
</ul>
<ul>
<li>Ask people to write their other use cases in GDoc
using this style.</li>
</ul>
<ul>
<li>Obviously, if you have suggestions on how to improve
the template, weigh in! If you want to make invasive
suggestions, contact me and we can do a collaborative
editing session together.</li>
</ul>
<div>I'm extremely glad I finally did this exercise, because
it caused me to understand more of what we need to
consider profiling and more of the "health SME" point of
view. And, to be honest (perhaps forestalling a comment
from Justin ;-), I don't feel that it was wasteful to go
to this degree of mapping to the technologies because it
flushed out some mismatches that really didn't make sense
to me all this time. I now feel we can go straight to the
heart (ahem) of the profiling matter with as many future
use cases as we want, and in fact, we can begin profiling
and write more use cases in parallel.<br>
</div>
</div>
<div><br>
</div>
<div>Thanks to you all for letting me "get my OCD on".</div>
<div>
<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>
Join our <a href="http://forgerock.org/openuma/" target="_blank">ForgeRock.org OpenUMA</a>
community!</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Openid-specs-heart mailing list
<a href="mailto:Openid-specs-heart@lists.openid.net" target="_blank">Openid-specs-heart@lists.openid.net</a>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a>
</pre>
</blockquote>
<br>
</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><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br><div dir="ltr">Adrian Gropper MD<span style="font-size:11pt"></span><br><br><span style="font-family:"Arial",sans-serif;color:#1f497d">RESTORE Health Privacy!</span><span style="font-family:"Arial",sans-serif;color:#1f497d"><br>HELP us fight for the right to control personal health data.</span><span style="font-family:"Arial",sans-serif;color:#1f497d"></span><span style="font-family:"Arial",sans-serif;color:#1f497d"><br>DONATE:
<a href="http://patientprivacyrights.org/donate-2/" target="_blank"><span style="color:#0563c1">http://patientprivacyrights.org/donate-2/</span></a></span><span style="color:#1f497d"></span>
</div></div></div></div></div></div>
</div>