This project aims to help hospitals digitalize their in-patient departments. In-patient department refers to the department of a hospital that handles patients who are being treated post-operation or are scheduled for a procedure.
- Built it primarily because I saw many doctors in my town still relying on paper logs and struggling with managing patients.
Checkout more screenshots here
- Manage multiple hospital buildings/branches.
- Supports 3 roles with varying priviliges: Operator, Manager, Admin.
- Restrict operator access to specific branches.
- Deactivate a user account.
- Create/view/modify building structure via web interface.
- Allows hard reset of the whole system and soft reset per branch.
- Backup branch structure (wards, beds) into a json file
- Restore system from a backup file.
- Manage admissions in a branch - admission time, discharge time, patient info, doctor name, comments and more.
- Helps manage credit and transactions - In rural India many patients arrive at the hospital without any form payment method and the doctors are expected to give them a temporary loan without any collateral - because it might be an emergency. This is primarily a paper based log kept on the back of an envelope – consequently it's poorly managed and prone to discrepancies at the time of discharge.
- The system logs each and every change to admission and transaction data.
- Transaction data is never deleted, it is only updated before logging, so no operator/manager/admin can make a false modification, since change/deletion is logged. Unless the system is soft reset by the admin.
- Doesn't allow discharging an admission if the ledger is not settled.
- Allows operators to use the application on a per branch basis. Switching to another branch means that all branch specific interface would be applicable only to that branch/building.
- Supports dark mode in the entire interface.
(what I learned during the 2 months building it)
- Why doesn't buildings.destroy_all work, but buildings.all.destory_all works (HABTM nested associations in Rails are read only)/
- Rails has inbuilt support for user models having password, just add has_secure_password call in the User model.
- how cookies work in Rails 6. Updated an existing answer on Stackoverflow too.
- what is JWT and when to use it. Read multiple blogs on where to store it, best practices etc.
- Best practices for structuring controllers and services.
- Catching errors raised in services directly at the controller and converting them to JSON.
- Having a single json handler allows consistent JSON response.
- querying on nested conditionally joined tables using ActiveRecord.
- Clearly understood the use for belongs_to has_many and other association constructs,
- Understood what the API only mode for rails is meant for and what middleware to additionally enable for a different frontend.
- Stick to figaro for env management, no point in implementing that yourself. It's okay to use other gems/libraries!
- Typescript should be avoided if the project needs to be done quickly and you are the only developer.
- Implemented route based authorisation for the first time.
- Used to directly use axios request object before this project, now I make custom hooks for get and post, way more clean code.
- Vercel has implemented swr (stale while revalidate) RFC as a hook called useSWR, which is awesome way to fetch data from an external api (though discovered that a bit late).
- How to SSR when a page is behind authentication (with cookies).
- SSR is not the preferred way for such projects, unless we want SEO, so that web crawlers can crawl our pages.
- Nextjs 10: router.push() takes two arguments and for dynamic routes we must provide the 2nd arg (as) to ensure that the page is not unmounted and remounted - spent a solid time on this foolishness.
- Difference between _app and _document files in nextjs.
- How to implement dark mode toggle using CSS variables.
- apply dark background to body and not a containing div of full 100vw,100vh. Because if browser is allowed to scroll past the end, there would be a white background(body color) making it unpleasant.
- Improved CSS knowledge vastly, learnt about BEM. But the project was near deadline by then.
- Learnt figma to create UI designs.
- For my clients' usecase, the application needed to be deployed on premises instead of cloud, hence the process is trivial.
I am open sourcing the application for anyone to use, especially if you find a doctor with a similar problem.
The code has room for improvement (evaded some typescript errors with any - bad practice). Please feel free to submit a PR. Thanks!