[Openid-specs-heart] Draft HEART Meeting Notes 2016-11-14

[Sarah Squire]

Attending:

Debbie Bucci

Adrian Gropper

Cait Ryan

Celestin Bitjonck

Dale Moberg

Edmund Jay

Glen Marshall

Hope Morgan

Jim Kragh

Justin Richer

Kenneth Salyards

Luis Maas

Nancy Lush

Sarah Squire

Debbie:

We’re going to base the profile on conditions, medication list, and
allergies. Looking at these separately, we need to think about separate
elements - each resource set will have a unique id. We need to talk about
what a resource type would be, and whether there are additional scopes we
need to profile.

Adrian:

I don’t know how we do anything without use cases.

Nancy:

Maybe we should frame what we already have, and then see if it fits the use
case.

Debbie:

Fair enough. So different resource types have different scopes associated
with them. Do we have an example of a resource type?

Sarah:

So keep in mind that when we’re talking about resources, we’re not just
talking about pieces of data, we’re talking about APIs, so the concepts of
read and write may not be meaningful for an API that does cryptographic
signing, or generates consent receipts for example.

Glen:

Right, you’re dealing with resources and verbs. The nature and purpose of
data sharing are going to be different for sharing with a provider vs a
payer.

Nancy:

There should be a separate section for purpose.

Sarah:

But purpose would have to be under scope, that’s the only way that UMA has
to express purpose.

Adrian:

Does UMA have resource sets?

Justin:

The UMA working group is discussing a change to the terminology, but the
concept of resource sets is still there.

Nancy:

Could we give a couple examples of resource sets?

Debbie:

Medications, Allergies, All

Are we agreeing that purpose is a useful scope?

Nancy:

I think it’s an important thing to have in UMA

Does UMA have scopes outside of read and write?

Justin:

UMA defines read and write, but any implementation can add additional scopes

Sarah:

We can add additional scopes if we feel they would be helpful to the HEART
profile

Justin:

ALL seems like it would be a helpful scope

Debbie:

Do we need more than read/write?

Justin:

SMART hasn’t used anything else yet.

Debbie:

What claims would be helpful to define?

Luis:

Covered entities

Adrian:

EMT/ER

Glen:

That could be a purpose too.

Sarah Squire
Engage Identity
http://engageidentity.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161114/782a4d7c/attachment.html>