Inspiration

  1. Unavailability of organised and proper medical records.
  2. Interoperability of medical data not possible.
  3. Absence of patient medical history leads to compromise in diagnosis.
  4. Too much headache for patient to maintain and carry their health records.
  5. Data on paper is more vulnerable to damage/loss.
  6. Data security is compromised.

What it does

Establish an ecosystem of connected healthcare systems in the network that will improve continuity of care, deliver better quality of care. Exchange Patient Care Information between members of network for better treatment management, while ensuring patients’ privacy and confidentiality. Leverage tiered approach of care delivery. Features:

  1. The main focus of the Elixir is to help provide a framework for facilities to digitize patient medical records and enable sharing these records across the care spectrum.
  2. The application allows doctors registered with multiple facilities to record medical information specific to each facility.
  3. Digitization: Ability to digitize patient medical records with the help of a user friendly and minimalistic web interface.
  4. Mobility: Web browser based access to the application enabling mobility for doctors.
  5. Ownership: Consent based creation of medical ID, complete ownership of health records.
  6. Medical History: Ability to have a longitudinal view of individual health records

How I built it.

I used FReMP architecture to build it. FReMP stands for Flask, ReactJS, MongoDB and Python. Flask and Python enable developers to develop scalable applications, capable of handling huge volume of data. React facilitates the development of a modern user interface on the client side.

Challenges I ran into

Major Challenges

  1. Making present application architecture flexible enough to easily accomodate future updates like - integrate with other applications, introduce new features and updating health guidelines like FHIR compliance, etc.
  2. Ensuring security of medical records via authentication services.
  3. Designing database for patients and health-officials.

Accomplishments that I'm proud of

  1. Elixir runs as a distributed application with client-side hosted on Firebase and the server deployed on Heroku which interact via REST API calls. In this way it can be easily integrated with other applications by modifying the API calls, without changing the present client and server side code.
  2. Presently, the application employs JWT authentication for security and further layers of multi-factor and OTP based authentication can be introduced using Firebase.
  3. A schema-based approach is followed with MongoDB which ensures its inherent flexibility while having a well-structured database which can be modified as per standardized medical norms.

What's next for Elixir (Integrated Public Health Repository)

  1. We are planning to develop this as a beta version, which is already in place.
  2. Also the typescript+ Nextjs + GraphQL version of elixir is under progress and the update will be available soon.
  3. We plan to put this interface for open source development like that of OpenEMR where everyone can contribute and it would also lead towards democratization of both developers and consumers.
  4. In additon to being an ecosystem for safe sharing of medical information we would like to use this as a medical practise management solution.
Share this project:

Updates