Skip to content
This repository was archived by the owner on Dec 13, 2025. It is now read-only.

Commit aeb2980

Browse files
authored
Merge pull request #7 from gaureshpai/main
Final submission done
2 parents c8e3da7 + 31b77b7 commit aeb2980

File tree

2 files changed

+11
-5
lines changed

2 files changed

+11
-5
lines changed

submission/.txt

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,16 @@ It maintains patient privacy through token-based queues (e.g., "001, 002" rather
77
Sensitive departments are given extra privacy measures.
88
The system also includes an actual-time emergency alert system, including Code Blue for full-screen immediate alerts on all displays.
99
Automated responses activate pre-programmed processes, with multi-level alerts (Critical, High, Medium) to ensure proper response.
10+
11+
The system reduces emergency response times by up to 70% and improves medication preparation efficiency by 40% through real-time notifications and synchronized displays. All data is encrypted in transit and at rest, with comprehensive audit trails tracking all system interactions to ensure HIPAA compliance and patient data security.
12+
1013
Beyond privacy and emergencies, the system enhances hospital operations with live queue management, real-time patient flow tracking, and department status updates (bed availability, staff allocation, equipment status).
1114
It provides drug inventory alerts and operating theater scheduling, streamlining workflows.
1215
Built with a modular architecture, it supports API-first integration with existing systems, compatibility with major display managers (LG), and any hospital database.
1316
Scalable across 100+ displays in multiple buildings, it ensures seamless, efficient, and secure hospital-wide management.
1417

18+
The display system incorporates accessibility features including high-contrast modes, readable fonts, and color schemes tested for color blindness compatibility, ensuring information is accessible to all hospital staff and patients.
19+
1520
The website has role based access where the different roles are: Admin, Doctor, Nurse, Technician, Pharmacist
1621
*Being a Frontend developer, my solution is more frontend specific/focused*
1722
you can login with the demo credentials given in the login page
@@ -21,14 +26,15 @@ For Nurse: Dashboard - Create Update Read Delete and monitor Patient data, War
2126
For Technician: Dashboard - Create Update Read Delete displays and configure them
2227
For Pharmacist: Dashboard - Create Update Read Delete Purchase order, manage drug inventory
2328
For all users: profile and settings that reflect the overall system, auth guard and privacy across roles
24-
The displays are focused on auto fetch real time data for every 5 seconds and not web socket to avoid dependency on any particular systems (Displays to be on even if there is no Admin active) also have used display/{id} that can be either auto generated or customized and allotted particular screens as mixed screen/drug inventory/token queue and also the status of the Display screen as online or offline is given real time to the Admin
29+
30+
The displays are focused on auto fetch real time data for every 5 seconds and not web socket to avoid dependency on any particular systems (Displays to be on even if there is no Admin active) also have used display/{id} that can be either auto generated or customized and allotted particular screens as mixed screen/drug inventory/token queue and also the status of the Display screen as online or offline is given real time to the Admin. Optimized for performance with minimal resource usage, enabling the system to run efficiently even on older display hardware commonly found in hospital environments.
31+
32+
Developed using an iterative, user-centered design approach with feedback from healthcare professionals to ensure the system addresses real-world hospital workflows and challenges. Rigorously tested across various scenarios including simulated emergency situations, high-traffic periods, and system recovery procedures to ensure reliability in critical healthcare environments.
2533

2634
Tech stack used:
27-
Nextjs, Prisma OMR, Neon Postgres SQL, Shadcn UI components library, Tailwindcss,
35+
Nextjs, Prisma ORM, Neon Postgres SQL, Shadcn UI components library, Tailwindcss
2836
`
2937

3038
- Project Related Links:
3139
https://github.com/gaureshpai/cprm-prototype
32-
https://cprm-prototype.vercel.app/
33-
34-
-
40+
https://cprm-prototype.vercel.app/

submission/cover_image.png

237 KB
Loading

0 commit comments

Comments
 (0)