MedEasy
An open source healthcare management system.
- Why ?
- How it works
- Available services
- Get started
- Want to contribute
- Troubleshooting
- each service should work independantly from others
- each service owns its data : data are never shared by two services.
- services can be updated independantly from one an other.
- HATEAOS all the way !
- services must be storage agnostic meaning they should never rely on storage specific features.
- Clone this repo
- Install Nuke tool globally. this tool is used to perform various tasks (migrations, running tests, etc.).
- Install Tye tool locally.
Why ?
Why not ?
How it works
MedEasy works as a set of independant services that operates together.
Design principles
Available services
Proxy
ReverseProxy handles all incoming requests and hides the remaining services from the public network.
It handles compression, caching, authentication, authorization on the behalf of all other services.
Agenda API
Agenda API handles appointments and attendees.
Documents API
Documents API handles file storage/retrieval.
Identity API
Identity API handles accounts that can be used to log into the
application. Relies heavily on JWT
Measures API
Measures API handles all sorts of physiological measures :
Patients API
Patients API handles patients primary data (name, date of birth, etc.)
Get started
You should be good to go !
Run nuke --help to see all available options
Want to contribute ?
You can start contributing by looking at good first issues
on the issue tracker.
Make sure you've read the contribution guidelines
Troubleshooting
If you find an issue you can submit a pull request (PRs are welcome 😀 !!) or open an issue.