[Openid-specs-heart] Suggestion for tomorrow's HEART meeting

[Debbie Bucci]

Given we want to pick up the conversation where we left off  I would like
to suggest that we please focus the conversation on a specific use case -
Alice Enrolls with the PCP - given its fresh in our minds.  We have
primarily focused on the What but there no real specifics on the HOW.  Much
of the conversation has been on the *other* issues ... Authentication,
Identity Proofing and Trust.


   - What were the previously assumed steps/options to establish the PCP
   and the PHR  Client and RS relationships (depending on context they could
   be both - right?)
   - Sarah's latest use case did a good job of describing the PHR flow but
   I do not see the PCP interactions (perhaps this is why Eve wanted to draw
   boxes) -
   - If patients chooses a pre-registered PHR - during registration what
   does that flow look like?  Have the scopes been pre-arranged ?
   - Will the SMART scopes (
   http://docs.smarthealthit.org/authorization/scopes-and-launch-context/
   )  suffice for this use case - even if UMA in play ?
   - Are the OpenID Connect scopes required and how are they used?
   - Would the registration flow change if identity information is common
   to both PHR and PCP?
   - Does the flow change if there is UMA on PHR side only?
   - How would the flow change if UMA is on both sides?
   - Where is consent needed and how is it expressed?  What is simple
   consent?
   - Are there gaps in the current standards that would require extensions
   for this use case?
   - Seems Adrian's CFR 42 Part 2 elements could be touched upon as well.

Yes I realize this is more system design ...
If there are other suggestions to help drive the semantic profiles over the
next couple of weeks  (highly doubt we would get through this tomorrow )
please suggest.

Regards

Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20150621/4b47bb03/attachment.html>