Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added to section 5


Do we want to submit this for any conferences:

...

Status of This Document: This is an Editors' Draft Report produced by the User-Managed Access (UMA) Work Group. See the Kantara Initiative Operating Procedures for more information.

Copyright Notice: Copyright © 2021 Kantara Initiative and the persons identified as the document authors. All rights reserved. This document is subject to theKantara IPR Policy - Option Patent & Copyright: Reciprocal Royalty Free with Opt-Out to Reasonable And Non discriminatory (RAND) (HTML version).

...

** 5 How UMA is used to accomplish the story (Alec)

UMA in this use-case (ecosystem in place for this story)

...


...

Now that we're familiar with the user case, challenges with policy and UMA/HEART technology, we will show how UMA is able to help accomplish this use case. Please keep in mind, this is one possible application of UMA and the other health IT, in reality there are many way to use the technology. The ability to change to accommodate different IT systems and policy constraints is one reason why UMA and HEART are so powerful.


"As a child, Julie's mother finds her a Pediatrician - Dr Erica"

 Dr Erica's office strives to include patients, and their guardians, in their care plans.  To help achieve this goal, they have selected an Electronic Medical Record (EMR) system that supports UMA, FHIR and HEART. At this first visit, Sue is provisioned i) login credentials and ii) and link the the EMR portal - including the UMA dashboard. Dr Erica educates Sue on how she'll be able to see Julie's health information in this portal, and also how Sue will be able to view, modify and accept anytime Julie's information may be shared with other parts of the health system. As Dr Erica gathers information about Julie, she records it into the EMR record.

After the appointment, Sue logs into the portal at home and is able to see the information captured during that first visit, such as the family history, and height and weight measurements for baby Julie. As Sue and Julie continue to attend annual check-ups, more data is stored in Dr Erica's EMR about Julie. Sue is also able to launch HEART enabled applications directly from the EMR (even if she doesn't know it) to see charts that track Julie's growth and development. 

[ bow tie diagram with UMA, EMR and some HEART apps accessed by Sue? ]


"At the age of 10, Julie is diagnosed with Asthma and will visit an asthma specialist, Dr. Robert. Dr. Robert needs access to Julie's health record in order to effectively provide care. At the end of the appointment, he prescribes Julie an inhaler"

During this annual checkup, Julie and Sue both express some concerns about some shortness of breath when Julie plays with her friends. Dr Erica believe Julie may have asthma and recommends that they visit a specialist to confirm the diagnosis and 



  •  


Info

UMA in this use-case (ecosystem in place for this story)

  • PCP run the AS and a FHIR Server (as the EHR)
  • each specialist with their own system, that needs access to the EHR (does the PCP provide this client, or can the specialist bring their own client (BYOC))
    •  respecting original policy as data moves to other systems → can be in the policy section as part of the complexity

We need another section here where Julie's record is shared with Dr Robert her Asthma specialist.

  • uma async, Dr Robert access ahead of

...

info
  • time
  • we can use the bowtie diagram to have consistent diagrams with the specific event/transition layered on. Helps presents the 'technical systems' and show how Julie and others interact with them through the story. 
  • want to eschew good default policy from the org, reduce the hard decisions needed from Julie/Sue


    In the story I have Julie's Mom doing the sharing since Julie is still a child.  If that is too confusing we can adjust the story to fit.  The reason I defined it that way is so that we can describe UMA from core concepts to more advanced, but we need to start Julie as a child so that we can demonstrate the state changes subsequently.

For the first section, when our use case describes basic UMA, I think this will be a good place to explain what UMA has over oAuth and highlight the increased security.



6. (state-diagram) Julie turns 13 - control moves from Sue to Julie (Eve if she can, otherwise Nancy will)

...