User Tools

Site Tools


groups:healthcare:connecting_health_data_across_silos_for_diagnostics_and_treatment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
groups:healthcare:connecting_health_data_across_silos_for_diagnostics_and_treatment [2018/07/18 11:57]
Marissa Iannarone Added screenshot from Tony Hussain
groups:healthcare:connecting_health_data_across_silos_for_diagnostics_and_treatment [2018/07/24 23:53]
Marissa Iannarone added players from Tony and Jeff
Line 17: Line 17:
 The MVP use case with this functionality could be with 4 players: The MVP use case with this functionality could be with 4 players:
   * Patient   * Patient
-  * Healthcare entity A (hosptial, lab, etc)+  * Healthcare entity A (hospital, lab, etc)
   * Healthcare entity B   * Healthcare entity B
   * Researcher   * Researcher
 +
 +Addition players to be taken into consideration to encompass the full ecosystem (highlighted in graphic below):
 +
 +  * Hospitals / Health Systems / Life Science (Research org)
 +  * Health Plans
 +  * Physicians Offices
 +  * Care Coordination Network
 +  * Social / Health Services Organization
 +  * insurer/​payer
  
 If we make the assumption that both healthcare entities use the same data standards (FHIR or other), this is how the work flow could be laid out: If we make the assumption that both healthcare entities use the same data standards (FHIR or other), this is how the work flow could be laid out:
Line 55: Line 64:
   * Update order status event------>​updates lab/ procedure event   * Update order status event------>​updates lab/ procedure event
   * Scrap vehicle event------>​ deceased   * Scrap vehicle event------>​ deceased
 +
 +We've confirmed that we will be working on a open source build. Tony Little suggested looking at the Davinci project from FHIR that that provides an implementation framework for others to follow: [[http://​www.hl7.org/​about/​davinci/​index.cfm?​ref=common]]
 +
 +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. ​
  
 **Current Solution** **Current Solution**
Line 62: Line 75:
 Take a look at how UK NHS is solving this same problem: https://​www.engadget.com/​2018/​06/​29/​britain-nhs-anonymous-health-data-privitar/​ Take a look at how UK NHS is solving this same problem: https://​www.engadget.com/​2018/​06/​29/​britain-nhs-anonymous-health-data-privitar/​
  
-We will also want to work with the Hyperledger ID team to understand better what they have thought of/built alreadyOnce we have journey map completed, we can loop them in and walk through ​it with them to gain insights+We have reviewed [[https://​medicalchain.com/​en/​|Medicalchain]] (Hyperledger project) and believe that they are targeting a very similar solution to what is laid out below. After reviewing the white paper, we do see possible opportunities for a POC to be built that would support Medicalchain work in the following areas: 
 +  * AI - machine learning could be inserted into the network - Anton recommended looking at [[https://​ada.com/​|ADA]] 
 +  * Chain of custody (which appears to be a gap according to the white paper 
 +  * Researchers able to engage with patient data via the '​market place' component laid out in the white paper 
 + 
 +We are waiting to hear back from Medicalchain on the following questions ​and are hopeful that a representative will be on the 7/27 HCWG call so that we can determine whether ​it makes sense to move forward ​with the use case stated above. 
 +  * If Medicalchain has implemented their code onto the main block chain at this time?  
 +  * Where their struggles, if any, may lie in implementation of the project.(This may be a question for them directly.)
  
 _If there are systems in place today which automate the above business problem/​opportunity,​ please explain what exists._ _If there are systems in place today which automate the above business problem/​opportunity,​ please explain what exists._
Line 104: Line 124:
  
 Initial thoughts on journeys to map: 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 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 * someone is looking to manage data from a treatment protocol that requires visits/​interventions with multiple physicians
Line 110: Line 131:
 Patient Centered Data mapping provided by Tony Hussain on 7/6: {{ :​groups:​healthcare:​screen_shot_2018-07-06_at_12.17.54_pm.png?​200 |}} Patient Centered Data mapping provided by Tony Hussain on 7/6: {{ :​groups:​healthcare:​screen_shot_2018-07-06_at_12.17.54_pm.png?​200 |}}
  
 +**Other Use Cases Being Considered by Patient/​Member Subgroup**
 +[[groups:​healthcare:​donor_milk_transparency_and_traceability|Donor Milk Transparency and Traceability]]
  
groups/healthcare/connecting_health_data_across_silos_for_diagnostics_and_treatment.txt · Last modified: 2018/07/24 23:53 by Marissa Iannarone