fix: broken links in README
This commit is contained in:
parent
90c98e03b3
commit
1f9518f575
1 changed files with 12 additions and 12 deletions
24
README.md
24
README.md
|
@ -3,8 +3,8 @@
|
||||||
This repository contains the software, research data and final thesis I worked on
|
This repository contains the software, research data and final thesis I worked on
|
||||||
as part of my Computer Science degree at TU Braunschweig.
|
as part of my Computer Science degree at TU Braunschweig.
|
||||||
|
|
||||||
My research examined the current state of research in mobile patient deterioration monitoring,
|
Over the course of three months, my research examined the current state of research in mobile patient deterioration monitoring,
|
||||||
and introduced a novel software system, which acts as an early warning system for high-risk patients
|
and introduced and evaluated a novel software system, which acts as an early warning system for high-risk patients
|
||||||
outside of direct medical supervision by utilising smart medical sensors in combination with
|
outside of direct medical supervision by utilising smart medical sensors in combination with
|
||||||
automated early warning score calculations.
|
automated early warning score calculations.
|
||||||
Following the conception and development of the software, the system underwent a usability trial
|
Following the conception and development of the software, the system underwent a usability trial
|
||||||
|
@ -26,7 +26,7 @@ To calculate an early warning score, or MEWS specifically, several vital paramet
|
||||||
scored individually. The individual scores are then added together to produce the final MEWS, which gives a clear
|
scored individually. The individual scores are then added together to produce the final MEWS, which gives a clear
|
||||||
indication of the patient's risk of deterioration. The following table shows the vital parameters and scoring for MEWS:
|
indication of the patient's risk of deterioration. The following table shows the vital parameters and scoring for MEWS:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Using tradtitional, expensive and immobile vitals monitoring devices, early warning scores are well established and widely used.
|
Using tradtitional, expensive and immobile vitals monitoring devices, early warning scores are well established and widely used.
|
||||||
But what about at home or on the go? With recent advances in smart medical sensor technologies, predicting patient
|
But what about at home or on the go? With recent advances in smart medical sensor technologies, predicting patient
|
||||||
|
@ -46,11 +46,11 @@ patients are asked to visit the web-UI, followed by recording their vital parame
|
||||||
|
|
||||||
These devices are shown the following picture:
|
These devices are shown the following picture:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Some UI screenshots of this process are shown here:
|
Some UI screenshots of this process are shown here:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Following the successful measurement using all three devices, Medwings retrieves the recorded vitals data from the Withings API,
|
Following the successful measurement using all three devices, Medwings retrieves the recorded vitals data from the Withings API,
|
||||||
processes it, calculating the patient's MEWS, and stores the results. The patient user is given feedback through the UI and, should
|
processes it, calculating the patient's MEWS, and stores the results. The patient user is given feedback through the UI and, should
|
||||||
|
@ -63,20 +63,20 @@ notifications. It communicates with the Withings Health Data Cloud via the RESTf
|
||||||
requests and to link Withings user accounts to Medwings. The dedicated Gotify Server used by Medwings is also controlled via
|
requests and to link Withings user accounts to Medwings. The dedicated Gotify Server used by Medwings is also controlled via
|
||||||
its own REST API.
|
its own REST API.
|
||||||
|
|
||||||
The Medwings application is split itself into the following modules, each handling a specific responsibility:
|
The Medwings application itself is split into the following modules, each handling a specific responsibility:
|
||||||
|
|
||||||
- [core](/app/core/): globally shared files and application-wide configuration
|
- [core](./app/core/): globally shared files and application-wide configuration
|
||||||
- [authentication](/app/authentication/): Medwings user and login/logout management
|
- [authentication](./app/authentication/): Medwings user and login/logout management
|
||||||
- [medwings](/app/medwings/): everything related to vitals data processing, storage and MEWS calculation
|
- [medwings](./app/medwings/): everything related to vitals data processing, storage and MEWS calculation
|
||||||
- [gotify](/app/gotify/): interfaces to the notification server
|
- [gotify](./app/gotify/): interfaces to the notification server
|
||||||
- [withings](/app/withings/): interfaces to the Withings API
|
- [withings](./app/withings/): interfaces to the Withings API
|
||||||
|
|
||||||
You can read more about each module and its functionality in each section mentioned above.
|
You can read more about each module and its functionality in each section mentioned above.
|
||||||
|
|
||||||
#### Further Reading
|
#### Further Reading
|
||||||
|
|
||||||
For more details about Medwings, its architecture, the development process and the in-depth evaluation and usability
|
For more details about Medwings, its architecture, the development process and the in-depth evaluation and usability
|
||||||
study of the system, you can read the [complete paper here](/docs/thesis/thesis.pdf).
|
study of the system, you can read the [complete paper here](./docs/thesis/thesis.pdf).
|
||||||
|
|
||||||
# Development Guide
|
# Development Guide
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue