User Tools

Site Tools


This is an old revision of the document!

Section 1 - Problem Statement

To link longitudinal user data identified across silos to help inform diagnostics and treatment - giving the individual ownership of their electronic medical records and health data.

While aggregated healthcare data can be a powerful tool for informing algorithms for patient diagnostics and treatment, Currently data are across various silos in Electronic Medical Records (EMR), laboratories, etc., residing with various stakeholders that form a center of trust around the individual. We need a way to connect these data across silos for a specific individual in a de-identified manner, while keeping the individual at the center of all data flow and access.

When thinking of this individual-owned health data record, we have identified 2 major use cases to explore (each of these with endless user journey and “sub use cases”: * Clinical trials * Sharing data across healthcare entities

  • Emergency room visit - how can an individual bring any relevant data with you to an emergency visit
  • Acute incident that requires both in-network and out-network provider visits/interventions

From here we need to deconstruct these use cases to make the work more actionable (we can't boil the ocean) - journey mapping seems like a logical next step - identifying the steps that a user would take along the way to get the expected results - then at each step of the way we can dig into the challenge areas below.

Areas that we'll need to dig into for each “sub use case” include: * Interoperability * Provenance * Data standards * Data rights * Flow of consent and data

Initial thoughts on journeys to map: * someone signs up to engage in our platform in order to manage data from and engage in a clinical trail * someone is looking to manage data from a treatment protocol that requires visits/interventions with multiple physicians * Opt-in for laboratory sample results to be leveraged to inform patient treatment protocols or diagnosis

_Please explain the business problem or opportunity in business terms without technical jargon, and without mention of a distributed ledger._

Current Solution - has been highlighted, but doesn't address data standardization and GitHub repo is here:

We will also want to work with the Hyperledger ID team to understand better what they have thought of/built already. Once we have a journey map completed, we can loop them in and walk through it with them to gain insights.

_If there are systems in place today which automate the above business problem/opportunity, please explain what exists._

Why Distributed Ledger Technology?

_Please explain how distributed ledger technology would improve the current solutions (if they exist) or enable new solutions which were previously unavailable. The goal here is to ensure we do not have a solution looking for problems, but problems where solutions would become possible or significantly improved by using distributed ledger technology._


_Use this section to give details that support the value of pursuing these user stories using distributed ledger technology. Some examples of information that might be included here are applicable market segments, workloads, user bases, etc. and any associated data._

Section 2 - User Stories and Requirements

_Please explain this use case using actors and interactions and assuming the ideal distributed ledger technology exists. You can tell one or more user stories if they are inter-related. Please list requirements per user story. It would be useful to explain where the use of the distributed ledger begins. For example, in a use case for prescription drugs, it would be valuable to ensure: * The manufacturer has sourced the correct ingredients * The manufacturer has combined the ingredients correctly * The manufacturer has tested the finished product and recorded the results for later audit * The finished goods are tracked to ensure the end user received exactly what the manufacturer shipped However, these could all be different use cases addressed with different solutions. So, it's important to explain where the problem starts and where distributed ledger technology would help._

Section 3 - Requirements Not Related to User Stories

_It is useful to specify requirements that should be considered but may not be apparent through the user story and usage examples. This information will help the developers be aware of any additional known constraints that need to be met for adoption of the newly implemented features/functionality. Precise specifications of the requirements make a developer's job much easier, so when in doubt, consult a technical expert. Example of the requirements not obvious thru user stories: performance, hardware, connectivity, privacy etc._

Section 4 - External References and Glossary

_Please use this section to add references for standards or well-defined mechanisms. In particular, if any of your requirements specifically call for the implementation of a standard or protocol or other well-defined mechanism, use this section to list them. Additionally, if your use case needs non-standard consensus mechanisms or cryptographic tools, please include technical material here, or references to technical material (i.e. a link to an eprint paper with security proofs). Remember, the burden of proof for security or consensus of non-standard mechanisms will be placed upon the proposer rather than the evaluator of the proposal, so be verbose here if necessary. It is highly suggested that you define any terms, abbreviations that are not commonly used in order to ensure that your user story is understood properly._

_Provide a list of acronyms, their expansions, and what they actually mean in general language here. Define any terms that are specific to your problem domain. If there are devices, appliances, or software stacks that you expect to interact with Hyperledger, list them here._

groups/healthcare/connecting_health_data_across_silos_for_diagnostics_and_treatment.1531833621.txt.gz · Last modified: 2018/07/17 13:20 by Marissa Iannarone