Note: This repository is a remake of the previous EHRoute server-side implementaiton, it aims to make EHRoute more performant, and cloud native. You can find the old implementation here.
| Status | Maintainability | Security | |
|---|---|---|---|
| Auth Service |  |
||
| Account Service | |
||
| Config Service | |
||
| Discovery Service | |
||
| Gateway Service | |
||
| Provider Service | |
||
| Patient Service | |
In 2018 alone, there have been 229 healthcare data breaches affecting 6.1M victims. Such data security concerns are often the main reason that providers are hesitant to share healthcare data. Sharing patient information can help providers reduce readmissions, avoid medication errors, and even decrease duplicate testing. Genetic studies, cancer/chronic disease registries, substance abuse, population health management, larger-scale analytics, epidemiology/disease tracking, and even interoperability for routine patient care in the emergency department are all potential uses for data sharing.
EHR Route is an open source Electronic Health Records (EHR) sharing and storage solution that aims to prevent the most common causes of EHRs data breaches. It closes gap between healthcare providers and patients, and ensures patients complete privacy and engagement in the process.
It utilizes Public-key cryptography (also known as asymmetric key encryption) And Blockchain Technology using Proof of authority with a single validator at its core; Public-key cryptography enables Patients maximum engagement by giving them control of choosing who uses, edits, or shares their electronic health record. While blockchain ensures and verifies data integrity.
Patients receive a public and private key-pair upon registration completion, that gets stored locally on their mobile devices using EHR Route App, whenever a provider needs to access or edit a patient’s EHR, a consent request is sent to the patient, the patient could refuse or accept, if accepted, blocks are signed by the patient and then immediately broadcasted across the network, patients public keys could also be used to verify that they signed the block [Details and UML diagrams will be added to the wiki]. If they didn’t accept the request, then no block is broadcasted.
