<div dir="ltr"><h3 id="markdown-header-roll-call-stats" style="margin:0px;padding:0px;color:rgb(51,51,51);font-size:18px;font-weight:normal;line-height:1.38888889;font-family:Arial,sans-serif">Roll call stats</h3><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">15/21 on the call were members</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">25 have submitted IPR - reminder - <a href="http://openid.net/intellectual-property" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">http://openid.net/intellectual-property</a>. specify the working group as “OpenID HEART"</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Listserv count up to 81</p><h3 id="markdown-header-ace-style-use-case-bashing" style="margin:20px 0px 0px;padding:0px;color:rgb(51,51,51);font-size:18px;font-weight:normal;line-height:1.38888889;font-family:Arial,sans-serif">'ACE-style' use case bashing:</h3><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Debbie attempted to super-simplify what Kathleen presented last week, into the “ACE” style. She picked the “Multiple Portals” use case to focus on, and she took out the VA specificity. Eve lightly edited it. Kathleen thinks it looks good.</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Debbie made an attempt at an Authorization Problems Summary. Some comments: Can we add something about Alice being present, or were we intending to eliminate that? On the other hand, would this be a generic scenario, and should we add specific use cases that would have their own authorization problem summaries that would get into that level of detail on their own? Justin suggests editing U2.5 by saying “…where possible, and authorize in real time where necessary.”</p><h3 id="markdown-header-technology-level-set" style="margin:20px 0px 0px;padding:0px;color:rgb(51,51,51);font-size:18px;font-weight:normal;line-height:1.38888889;font-family:Arial,sans-serif">Technology Level Set</h3><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">OpenID Connect presentation by Justin (<a href="http://www.slideshare.net/zeronine1/mit-2014-introduction-to-open-id-connect-and-oauth-2" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">http://www.slideshare.net/zeronine1/mit-2014-introduction-to-open-id-connect-and-oauth-2</a>):</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Justin picked up where he left off last week. He distinguished OAuth (chocolate) and OpenID Connect (fudge). OAuth doesn’t do any authentication-related jobs, such as identification or session persistence; this is where OIDC comes in.</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Adrian asks: What about an HIE that has no patient portal, and is in a third-party data broker role? Eve remarks that if the patient has no way to manage protected resources at that HIE, then those resources aren’t “user-managed”, but rather exchanged on a back channel with respect to that patient.</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">UMA presentation and demonstration of a taxes use case/workflow to illustrate concepts by Eve (<a href="http://openid.net/wordpress-content/uploads/2015/02/UMA-for-HEART-2015-02-09.pdf" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">http://openid.net/wordpress-content/uploads/2015/02/UMA-for-HEART-2015-02-09.pdf</a>)</p><h3 id="markdown-header-general-announcements" style="margin:20px 0px 0px;padding:0px;color:rgb(51,51,51);font-size:18px;font-weight:normal;line-height:1.38888889;font-family:Arial,sans-serif">General Announcements</h3><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">For those willing to edit the wiki, create a bitbucket account (<a href="https://bitbucket.org/" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">https://bitbucket.org</a>) if you dont have one or send info to Debbie will add Bitbucket rights, and she’ll expose the use case publicly that she was showing on the screen. People can also send email to the list to have Debbie and Eve add wiki content.</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px"><strong>We’re not meeting next week</strong>, but will pick up again on Feb 23 to work on more specific use cases, including Registration.</p><p style="margin:10px 0px 0px;padding:0px;word-wrap:break-word;color:rgb(51,51,51);font-family:Arial,sans-serif;font-size:14px;line-height:20px">Going forward - Meeting notes archived on the wiki  <a href="http://bitbucket.org/openid/heart/wiki/Home" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">http://bitbucket.org/openid/heart/wiki/Home</a> and resource links can be found - <a href="http://openid.net/wg/heart/resources/" rel="nofollow" style="color:rgb(53,114,176);text-decoration:none">http://openid.net/wg/heart/resources/</a></p></div>