Patient and service workflows
The approved project overview covers patient records, laboratory and radiology transactions, and Konsulta settings.
Healthcare / App case study
USM Hospital System
A collaborative hospital operations system connecting patient records, laboratory and radiology transactions, pharmacy inventory and dispensing, Konsulta settings, reports, and staff-specific dashboards.
Collaborative OJT prototype
- Laravel
- PHP
- Vue
- Tailwind
Private repository
01 / Overview
What it’s built for.
Connect hospital operations through staff-specific workflows while keeping patient records, service transactions, and inventory work organized.
Who it serves
Hospital administrators, doctors, nurses, pharmacists, laboratory and radiology staff, and receptionists.
02 / Features
Inside the app.
Pharmacy operations
The approved scope includes inventory and dispensing workflows.
Staff dashboards and reports
Distinct staff workflows support the roles described in the portfolio’s existing project summary.
03 / Workflow
From task to outcome.
Staff access the dashboard relevant to their role.
Work through the patient, service, or pharmacy module relevant to the task.
Review records and reports within the approved prototype scope.
04 / Technical layers
How the pieces work.
Vue · Tailwind
The approved portfolio stack identifies Vue and Tailwind for the interface.
Laravel · PHP
The approved stack identifies Laravel and PHP for hospital-operation workflows.
Private implementation
The public overview describes patient records and role-specific workflows. Database and authorization internals are not published here.
05 / Limitations
What to keep in mind.
- This page uses only the project description and assets already approved for the portfolio; the repository is private.
- The work is presented as a prototype and learning project, without a claim of production adoption.
- No patient records, private source code, or confidential hospital information is displayed.
06 / Evidence
Follow the source.
This repository is private. This case study uses the portfolio’s approved project summary and assets; private code and implementation details are not published here.