Attendees:

Debbie Bucci

Abbie Barbir

Adrian Gropper

William Kinsley

Glen Marshall

Justin Richer

Sarah Squire

Michael Magrath

Jim Kragh

Josh Mandel

Chad Evans

Corey Spears

Edmund Jay

Jeremy Maxwell

Andrew Hughes

Eve Maler

Notes:

Alice Enrolls at PCP Use Case

Justin’s comment was intended to convey that Alice should be able to login with whatever digital identity she chooses. We don’t want Alice to have to create multiple usernames and passwords.

Is federated identity core to the HEART project? The ability to use federated identities is core to HEART, but they are not required.

Identity proofing policies are out of scope for the HEART project

Leveraging common identity attributes is a core part of the problem statement for this use case.

Are we using OIDC in this use case? Yes, we are.

The data exchange in this use case is patient-mediated, so identity matching is necessary.

We have now finalized this use case.

New Use Cases

We would like the next use case to involve UMA, and we would like to be able to influence and harmonize with the FHIR API. What is it that we must profile vs what FHIR must profile?

We want to bias toward wide ecosystems.

Adrian will elaborate on his use cases and we can discuss next week.

Adrian added: Great notes. One flaw:

"The data exchange in this use case is patient-mediated, so identity matching is necessary."

should be is NOT necessary.

Adrian

Sarah added: Quite right! Thanks for catching that, Adrian!

Jeremy added: Wait, I’m confused. I know we called identity matching out of scope, which I agree with, but what did I miss that it’s unnecessary? Even though Alice is mediating the exchange, the provider still needs to know which Alice in the EHR, right?

Justin Richer added: Right, but they do it during the initial binding of alice’s identity and access tokens to the record. They don’t take in a bunch of attributes from Alice’s IdP and say, “oh, well, let’s go find some Alice that might fit this”. As long as they have the right record up during the binding, then that same record can be pulled up by its local identifier. At that point, the system doesn’t even care that Alice is Alice, they just know that account X has access to record Y because of a specific (and auditable) action.

Jeremy added: To parrot what I heard…identity matching happens at binding time not exchange time, therefore matching is not necessary to the exchange use case. Am I tracking?

Justin added: Correct, and at the time of binding there’s a lot more context available to make sure the matching is done correctly. The rest of the system flows from that match being made.