Table of Contents
HORAS is an open source Hospital Information System. It was created for helping hospital as an assistant to run business easily, help to make business or medical decisions by datas, faster department integity, universal business core.
Here's why:
- Humanity. Helping hospital faster to save lives
- Minimize unnecessary expense leakage in order to maximize health services
- A kind of expensive paid application that makes it difficult for small scale hospitals to run faster
Built using these awesome frameworks
- Nodejs
- npm@9.5.1
- @nestjs/cli@9.2.0
- jest@29.4.3
## Project Structure
HORAS contains 2 main project directory (server and app). You need to run npm start/serve on each folder to run it.
API default run on port 3000. You can access Open API at <hostname>:3000/api
API service is inside server folder (NestJS environtment, monorepo mode)
- Create .env file from .env.example format and adjust with your local setting (environtment folder)
- Run api service
Watch Mode
npm run start
And module target (see package.json)npm run start:dev
npm run start:dev:core
- Run front end
npm run serve
Below is an example of how you can instruct your audience on installing and setting up your app. This template doesn't rely on any external dependencies or services.
- Clone the repo
git clone https://github.com/theycantrevealus/horas.git
- Enter your config in
.env - Install NPM packages (for each folder api and app)
npm install
- Application Design
- Discussion and Evaluation
- Documentation
- Code strategy
- Add "components" document to easily copy & paste sections of the readme
- Documentation Adjustment
- Multi-language Support
- English
- Indonesia
See the open issues for a full list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated (God Bless Your Kind Heart).
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Make sure to write properly test and run it on locally to keep commits clean on remote repository
This project using following format as committing message. If any suggestion of type, feel free to suggest it. For now we are not using git lint yet, but soon
✨ feat: Add a new feature to the codebase (MINOR in semantic versioning).
🔧 fix: Fix a bug (equivalent to a PATCH in Semantic Versioning).
📑 docs: Documentation changes.
👑 style: Code style change (semicolon, indentation...).
👓 refactor: Refactor code without changing public API.
🚀 perf: Update code performances.
🔎 test: Add test to an existing feature.
📦 chore: Update something without impacting the user (ex: bump a dependency in package.json).
Distributed under the APACHE 2.0 License. See LICENSE.txt for more information.
Hendry Tanaka - @takashitanaka_ - theycantrevealus@gmail.com
Project Link: documentation and paper
Use this space to list resources you find helpful and would like to give credit to. I've included a few of my favorites to kick things off!
- Choose an Open Source License
- GitHub Emoji Cheat Sheet
- Malven's Flexbox Cheatsheet
- Malven's Grid Cheatsheet
- Img Shields
- GitHub Pages
- Font Awesome
- React Icons