Health & public health
MedFlow
Coordinate a patient journey through real-time, role-specific queues.
- Status
- Working product
- My role
- Full-stack architecture and implementation
- Timeframe
- April - June 2026
- Core technology
- Next.js · NestJS · PostgreSQL · Prisma
01 / Context
The problem
When clinical departments operate as disconnected tools, staff lose visibility into the patient journey and handoffs become difficult to coordinate.
02 / Product
The implemented solution
MedFlow gives each authorized role a focused queue while preserving one controlled patient journey from registration to discharge.
03 / System
Architecture, in plain language
A NestJS API enforces role permissions and patient transitions over PostgreSQL. Socket.IO publishes state changes to the relevant Next.js dashboards, while transactional inventory handling protects pharmacy operations.
04 / Judgment
Important decisions
- Modeled workflow state explicitly instead of inferring it from scattered records.
- Scoped interfaces and permissions by role to reduce operational noise and inappropriate access.
- Used event-driven queue refreshes while keeping the database as the source of truth.
05 / Boundaries
Limitations and next work
This is a software workflow project, not a certified medical device or clinically validated care system. Production use would require institutional governance, security review, and regulatory assessment.
06 / Implementation
Focused technology
Next.js · NestJS · PostgreSQL · Prisma · Socket.IO · Docker