[Openid-specs-heart] V2 of Profiling UMA for FHIR slides

[Adrian Gropper]

Use Case 1 - HIE across state lines

   - Alice's motivation: She lives in NJ, has doctors in both NY and NJ.
   Wants them all to see everything.
   - Provider's motivation: Wants to have the same HIE experience even if
   Alice's doctor is in another state.
   - Scope: Everything R/W

Use Case 2 - Referral

   - Alice's motivation: Doesn't want to have to fill in a paper clipboard
   when she visits new provider
   - Provider's motivation: Wants accurate medications, allergies, current
   problems, insurance, and contact info. Wants to avoid front-office data
   entry work.
   - Scope: Medications, allergies, current problems, insurance, and
   contact info R

Use Case 3 - Healthcare Proxy

   - Alice's motivation: Wants her adult son healthcare proxy 200 miles
   away to see the result of every provider encounter.
   - Provider's motivation: Wants to avoid having to call healthcare proxy
   after every encounter.
   - Scope: Everything R

Use Case 4 - Mental Health Visit

   - Alice's motivation: Wants to keep her mental health encounter away
   from all other providers.
   - Provider's motivation: Wants to be able to say to Alice: "Speak
   freely, this encounter will not be shared."
   - Scope: Everything except items entered in date range R/W

Use case 5 - Compare out-of-pocket cost for a prescription

   - Alice's motivation: She wants to know her out of pocket cost, choose a
   pharmacy, and tell her provider where to send the prescription.
   - Provider's motivation: Knows the drug or x-ray is expensive. Wants to
   help the patient but doesn't want to be called to move the prescription to
   another pharmacy or imaging facility.
   - Scope: One Medication or Order just added or most recent. R

Adrian

On Tue, Nov 1, 2016 at 12:00 PM, Eve Maler <eve.maler at forgerock.com> wrote:

> As discussed on the call, the exercise is to figure out *Alice's
> motivation for sharing* the various data sets (FHIR resources in scope)
> vs. *the provider's motivation for wanting access* to them.
>
> The ones listed on the slides aren't necessarily the ones Nancy et al.
> listed on the call/in email, so please don't take the slides versions as
> gospel!
>
> Please identify the specific use cases/scenarios you have in mind. By
> drilling down on this, we can get an idea of the interplay among the FHIR
> API design, the UMA resource set boundaries and scopes as Alice may want to
> experience them, and the API calls as the provider's client applications
> may want/need to make them. I believe this will have a big impact on how we
> can/will profile.
>
>
> *Eve Maler*ForgeRock Office of the CTO | VP Innovation & Emerging
> Technology
> Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl
> *The ForgeRock Identity Summit* is coming to
> <http://summits.forgerock.com/> *Paris in November!*
>
> _______________________________________________
> Openid-specs-heart mailing list
> Openid-specs-heart at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-heart
>
>


-- 

Adrian Gropper MD

PROTECT YOUR FUTURE - RESTORE Health Privacy!
HELP us fight for the right to control personal health data.
DONATE: http://patientprivacyrights.org/donate-2/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-heart/attachments/20161102/3aa0b5a3/attachment.html>