Skip to content

Darshpreet2000/LibreHealth-Essential-Care-For-Every-Baby

Repository files navigation

LibreHealth Essential Care For Every Baby

A Newborn Baby Care Support App

Goal

An Android/IOS application to provide clinical decision-support for nurses and doctors delivering essential newborn care interventions during the first day of life. This application provides knowledge, skills, and competencies to nurses and doctors in low/middle-income settings so that they can provide life-saving care to newborns from birth through 24 hours postnatal. App uses DHIS2 as backend & can be setup for any hospital/organization

Features

  • Ability to track multiple babies at a time

  • Time-stamping births to generate an essential newborn care clock for each baby being tracked in the app

  • Automated classification of babies health status, based on results from observations and assessments that are conducted during the first 2 hours after birth

  • Automated advice on management of babies, based on their classification; Reminders/alerts to provide recommended essential newborn care interventions

  • If particular interventions are not delivered on time, or at all, capture of information regarding why this essential newborn care was late, or missed

This project is developed using Flutter, it supports Android & IOS with single codebase

Link to documentation

Link for User & developer documentation of this App

https://librehealth.gitlab.io/incubating-projects/mhbs/lh-mhbs-eceb/

Maintainers and Developers

Screenshots

Login Screen Home Screen List of Babies Screen
Sort By Feature Profile Screen Risk Assessments
Monitoring Alerts Drawer Doctor Schedule Screen
Settings Screen Home Screen Drawer
List of Babies Doctor Schedule Screen Settings Screen
Stage 1 Stage 2 Register
Normal Problem Danger
Discharge Notification About Screen

Contributions Best Practices

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.

  • Single commit per pull request
  • Reference the issue numbers in the commit message. Follow the pattern Fixes #<issue number> <commit message>
  • Follow uniform design practices. The design language must be consistent throughout the app.
  • The pull request will not get merged until and unless the commits are squashed. In case there are multiple commits on the PR, the commit author needs to squash them and not the maintainers cherrypicking and merging squashes.
  • If the PR is related to any front end change, please attach relevant screenshots in the pull request description.
  • Before you join development, please set up the project on your local machine, run it and go through the application completely. Press on any button you can find and see where it leads to. Explore.
  • If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to start working on it.

Branch Policy

We have the following branches

  • development All development goes on in this branch. If you're contributing, you are supposed to make a merge request to development. PRs to development branch must pass a build check and a unit-test check on Gitlab pipeline.

  • master This contains shipped code. After significant features/bugfixes are accumulated on development, we make a version update and make a release.

License

This project is licensed under the Mozilla Public License 2.0 with Healthcare Disclaimer. a copy of this license can be found in LICENSE.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages