Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

3 Use Case flows 

  • Notice and a Notification to the person
    • title; Short Description (how does it work with existing policy) 
    • Use Case Flows
  • Person using notice to control data 
    • title; Short Description  (when in consent - how to maintain, revoke renew, ) 
    • Use Case Flows
  • Person creating a Notification - control the use of data
    • title: Short Description  : how to use with law (not controller policy) 
      • person medical data on virus + phone data research into global Covid -Research - 
    • Use Case Flows


  • All of your use cases 


Healthcare Use-Cases

Dimensions of the use-cases

  • Whether there are different domains (hospitals, countries)
  • Whether data is pre-anonymised (notably for medical research)
  • Whether there is an established identity system able to authenticate and receive requests

Actors

  • The subject
  • The healthcare organisations holding EHRs
  • Requesting parties
  • Countries or jurisdictions

Use-Cases

From simplest to comprehensive

  1. Within a single domain, subject agrees to share anonymised medical data for research
  2. Across two domains, subject agrees to share anonymised medical data for research
  3. Across two domains with federated identity, subject authenticates and allows access to EHRs
  4. Across two domains over which no common identity system exists, subject agrees to share EHRs
  5. Across two different countries, and necessarily two different domains, subject agrees to share EHRs and use part of that information to comply with public notification requirements
  • No labels