Hospital@Home to the rescue

This space is designated for the participation in the COVID-19 Global Hackathon 1.0.

Content

 

Video summary

Check out the video summary (no audio):

 

Project Summary

The growing Covid-19 pandemic has recently overwhelmed healthcare systems, with case numbers outstripping the available hospital and ICU capacities, leading to chaos and despair. As the case numbers grow in the near future, this phenomenon is expected to repeat around the world. Such regional “melt-downs” of healthcare systems resemble the original situation in Wuhan, China in January 2020. Estimates show that probably 5-10% of patients infected with Covid-19 will require intensive care treatment, often for several weeks, and an overall mortality of 1-2% of the infected population, with many asymptomatic patients. While Covid-19 spreads at viral speed, and case numbers double every 3-4 days, a healthcare system melt-down will follow 2-5 months after the first cases. In such a scenario, where the number of Covid-cases exceeds the number of hospital beds, the bed itself, along with the associated healthcare provider, become the most valuable asset.

The clinical course of Covid-19 is slowly progressing for 1-2 weeks, with respiratory, or general infective symptoms, like cough, malaise, fever and headaches. Only probably <10% of patients or less eventually deteriorate to respiratory failure, often occurring 7-12d after the initial infection, and <5% progress to ARDS, shock and potential death on the basis of interstitial pneumonia and sepsis. The signs of this deterioration can be monitored by wearable monitoring, such as declining blood oxygen saturation (SpO2), faster breathing rates and heart beat. When these signs occur, does a hospitalisation may become necessary, and a reevaluation should be performed. As long as patients remain stable, isolation at home and remote monitoring could be the preferred option. 

The paramount goal in the pandemic is protection and maximizing the use of core healthcare assets, staff and beds. One important strategic consideration for this goal is the resulting need to keep Covid-19 cases out of hospitals for as long as possible. In order to properly control and distribute hospital and ICU capacities, the healthcare system needs a valve to take the pressure of the existing healthcare infrastructures. By sending diagnosed, but stable patients home in the symptomatic phase, and accurately tracking their health status through their vital signs, telemedicine can take the pressure of the pandemic. A possible extension of the system could be the monitoring and management of supplementary oxygen and potentially NIV (non-invasive ventilation), administered at home, if no other options are available. 

We want to develop a system that can take care of patients with Covid-19 pneumonia for days, isolated and safe in their home environments, while being monitored for changes in vital signs and health status. This strategy can not only save critical healthcare resources and alleviate future healthcare melt-downs, but might be able to slow the transmission and save further lives.

 

Meet the team

The content of this macro can only be viewed by users who have logged in.
The content of this macro can only be viewed by users who have logged in.
The content of this macro can only be viewed by users who have logged in.
The content of this macro can only be viewed by users who have logged in.

 

Goals

During the hackathon, we want to work out the details of the idea and develop the mobile and cloud-infrastructure, incl. analytics and dashboard. We also have a set of prototype sensors, and a Nonin Spo2-device, that can be used for a technical prototype. We would need several development resources for the technical proof-of-concept, as well UX and design expertise.

  • technical software prototyping

    • @Mohamad Atayi (Deactivated) / @Salman Rahman could u please think of the SW,

      • architectural considerations (architecture draft can be found here)

      • goals / sub-goals

      • resources needed / positions to fill

    • We should think: patient/ device data

      • to mobile app

      • to cloud

      • for continuous analysis

      • with dashboard.

    • design of monitoring and analytics in detail

    • design of dashboard, App

    • video and project presentation

  • validation of numbers, definition of inclusion / exclusion

  • operational resources planning

  • documentation, name

Goal / Sub-goal

Task

Deliverable

Team

Done by

Goal / Sub-goal

Task

Deliverable

Team

Done by

Technical prototype

 

 

 

Monday morning

  • SpO2 module

 

 

@Masoome Fazelian (Unlicensed)

 

  • Mobile/Desktop App

  • Data acquisition from Explore/SpO2 devices

  • Data transmission to the cloud

  • A python desktop application streaming biosignal data and sending them to the cloud

@Mohamad Atayi (Deactivated)

@Masoome Fazelian (Unlicensed)

Sunday 22h CET

  • Cloud arch.

  • Data ingestion

  • Data parsing

  • Data warehouse

  • Bokeh server

  • Endpoint

 

@Mohamad Atayi (Deactivated)

Sunday 22h CET

  • Analytics

  • Read the data from cloud server

  • Trigger an alarm when some data threshold is crossed

  • Depending on data metric, analysis can be long(over a period of 10-15 min) or short(15 sec)

 

@Salman Rahman

Sunday 22h CET

  • Dashboard

  • Monitor a number of patient related metrics(SpO2, Heart Rate, Respiratory Rate and maybe ECG)

  • number of days since symptom onset and number of days since diagnosed

  • generic trend of patient status

  • An overview page for all registered patients

  • authentication and encryption

 

@Salman Rahman

Sunday 22h CET

  • Data pipeline

MERGED WITH CLOUD SECTION

 

@Mohamad Atayi (Deactivated)

Sunday 22h CET

  • Prototype description

 

 

@Bernhard Rischke

 

 

Product Design

 

  • Design of whole product + visuals

@Sebastian Herberger

 

  • User stories

 

 

@Sebastian Herberger @Andreas Rudolph

 

  • Solution Details

 

  • Presentation of problem + solution

@Sebastian Herberger

Sunday 22h CET

  • Context + Operations

 

  • Demographics

  • Operation

@Sebastian Herberger

Sunday 22h CET

  • App Design

 

  • App UML

  • click dummy

…

Sunday 22h CET

  • Dashboard

first draft of dashboard items

  • Dashboard layout

  • Dashboard logic

 

 

Sunday 22h CET

  • Dashboard Design

 

  • Design Dummy

  • click dummy

  • Animation

…

 

 

 

 

 

 

Presentation

 

 

 

Monday

  • Summary

 

1 pager, sides

 

Sunday 22h CET

  • Video

 

90 Second summary

 

Sunday 22h CET

  • Website

 

name, URL, Logo

 

Sunday 22h CET

Team news

Create a blog post to share team news. It will automatically appear here once it's published.

 

Blog stream

Create a blog post to share news and announcements with your team and company.

 

Meeting 1 - 12.45h 28.03.20:

Focus on the good design, architecture and value of the proposed solution, less on technical prototyping

1.) User stories for all users in the solution

  • Prototype all user interfaces App, Dashboard

  • Which kind of interactions/ information?

    • Patients

    • Doctors

    • Provider / Operators

  • Dyssynchronous communication protocol

    • Design and Documentation

  • 2.) Technical System architecture / evaluation of tasks

    • Proof-of concept / goals-setting

    • Animation of solution / dashboard

  • 3.) General: Review of results and iteration / refinement

  • 4.) Additional statistics / information

 

 

Name and onliner suggestions:


Feel free to add

  • TelemedNet

  • Digitalhospital

  • Hospital@home

  • DDH - distributed digital hospital

  • homespit@l

  • ICU@home

  • MLab

  • MDH mobile digital hospital

  • DHP - The Digital Hospital

  • H@H - hospital at home

Tasks for Python Desktop Application

  • UI that will allow users to connect to device (web interface or something like Tkinter/Qt)

  • Data streaming to server.