[Openid-specs-heart] Draft HEART Meeting Notes 2016-11-28
Sarah Squire
sarah at engageidentity.com
Mon Nov 28 21:59:59 UTC 2016
Light notes this week since we mostly walked through the use case that Eve
and Nancy have been working on which will be sent out to the list shortly.
Attending:
Debbie Bucci
Adrian Gropper
Celestin Bitjonck
Edmund Jay
Eve Maler
Glen Marshall
Jim Kragh
Jin Wen
Luis Maas
Nancy Lush
Sarah Squire
Scott Shorter
Thomas Sullivan
Walter Kirk
Eve:
We’ve been winnowing down the resources we think people should focus on. We
want to help people think with the lens of UMA. We might want to profile
what normal people would say in natural English. So “medicines I take”
might be friendlier than “current medications”
Adrian:
So we’re saying that our goal is that two RSs would describe the same words
to describe a resource?
Eve:
We should decide whether or not to standardize that.
Glen:
Well, this might not be as straightforward as you might think to map these
to FHIR resources.
Adrian:
Is it allowed for a server to list the FHIR resource itself? Rather than
the friendly name?
Eve:
So we need to decide whether we want friendly names at all, and then
whether we want to suggest or require them. We have a use case for
proactive Alice sharing including notifications.
Nancy:
Is it okay to notify the client what Alice’s patient ID is? If the FHIR
interface knows it and sends it over the wire, then the client should be
able to know it and send it over the wire.
Adrian:
Why do we need a patient ID?
Eve:
All we really need is the resource endpoint, we don’t need Alice’s patient
ID. You can notify Dr. Erica with knowledge of that endpoint. We probably
want the client to pass all the trust elevation tests before it can see the
URL with a patient ID in it. We don’t want a patient id in the clear.
Nancy:
We really tried to make this as simple as possible.
Eve:
We’re trying to replicate what Google has already done with document
sharing in a loosely coupled protocol.
Sarah Squire
Engage Identity
http://engageidentity.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161128/fbc2bc8b/attachment.html>
More information about the Openid-specs-heart
mailing list