Sahtek
A role-aware prescription platform connecting doctors, patients, and pharmacists through one accountable flow.
- Role
- Product architecture, backend engineering, data modeling, and full-stack implementation.
- Stack
- NestJS / TypeScript / TypeORM / MySQL / Docker
Overview
Healthcare coordination, designed as a system—not a collection of screens.
A role-aware prescription platform connecting doctors, patients, and pharmacists through one accountable flow.
The constraint shaped the system.
Prescription handoffs cross multiple actors, each with different permissions, context, and operational needs. The product needed a trustworthy flow without making routine actions feel heavy.
Responsibilities made explicit.
A domain-led backend models prescriptions as a controlled lifecycle. Role-specific surfaces expose only the actions each participant needs, while identification and history make the handoff traceable.
Workflow
One prescription, three accountable roles.
The workflow keeps prescription state understandable as responsibility moves from medical authoring to patient access and pharmacy verification.
- 01Doctor
- 02Prescription
- 03Patient
- 04Pharmacist
- QR / CIN access
- Medication history
- Pharmacy availability
- Dispense state
Engineering
Boundaries before screens.
- 01
Role boundaries
Doctor, patient, and pharmacist experiences expose the actions each actor needs while keeping permissions explicit.
- 02
Prescription lifecycle
Creation, retrieval, verification, and dispensing are treated as controlled state transitions rather than disconnected actions.
- 03
Domain data
NestJS, TypeORM, and MySQL support prescription records, medication information, and retrievable history.
- 04
Consistent delivery
Docker packages the application environment so the system can be run and inspected consistently.
System scope
- 01Doctor, patient & pharmacist roles
- 02Electronic prescriptions
- 03QR identification
- 04Medication history
- 05Pharmacy availability
- 06Multilingual workflows
- 07Analytics-ready data
- NestJS
- TypeScript
- TypeORM
- MySQL
- Docker
Engineering takeaway
The strongest healthcare UX starts with clear domain boundaries and conservative access—not visual complexity.