Case study · Healthcare platform
Slashcure
One platform for Pakistan's patients, doctors and hospitals.
A lifetime health record that patients carry on a QR code, connected to verified doctors and live hospital pages. Groflex designed, built and shipped the whole platform, and kept it growing week after week.
02The idea
It started with the patient.
Slashcure began as a health record: a patient's history, organised once, kept for life and carried on a QR code.
As it proved itself, the brief grew. Doctors got verified public profiles. Hospitals got live OPD pages. The record became the core that connects them all.
Start with the patient. Everything else connects to that.
03The challenge
Sensitive data. Live information.
A health platform holds the most private data a person has, and it also has to answer the most practical question in healthcare: can I see this doctor today?
The hard part wasn't the features. It was this: how do you make information this sensitive, and this live, something people can trust?
Private vs findable
Medical records have to stay locked. Doctors and hospitals have to be easy to find. Same platform.
Live vs reliable
“Is the doctor in today?” changes by the hour. A wrong answer sends a patient on a wasted trip.
Many roles, one truth
Patients, doctors, receptionists and admins look at the same schedule. It can never disagree with itself.
04How it grew
It grew with the client.
Slashcure was never specified once and handed over. Each phase went live, met real doctors and patients, and shaped the next. Twelve weeks, 194 commits, one product that kept getting bigger.
- JunePhase 01
Health record
A lifetime patient record, a QR Health ID and consent-based doctor access.
- JulyPhase 02
Slashcure
The rebrand, verified doctor profiles, multi-clinic schedules and medico-legal certificates.
- Early AugPhase 03
Public handles
Every doctor at slashcure.com/their-name, with branded QR posters for the clinic wall.
- Mid AugPhase 04
Hospital portal
Live OPD status, departments, staff accounts and an Ask Receptionist line.
- Late AugPhase 05
Doctor portal
“I’m in clinic”, announcements, articles, reviews and analytics.
05Privacy
Private by default. Shared by consent.
We designed access around the patient. Nothing opens without their say, and nothing opens without a record of who looked.
A doctor opens a record
- ScanThe patient’s QR
- RequestAsk for full access
- ApprovePatient shares a one-time code
- Time-boxedAccess expires on its own
- LoggedEvery view is recorded
An emergency
- ScanThe emergency QR
- IdentifyName and role
- ReasonWhy they need it
- EssentialsOnly the emergency summary
- LoggedAccess is recorded
- 01
Locked by default
The database refuses every request from a browser. All data goes through one server that checks who is asking.
- 02
The patient holds the key
Full access needs the patient’s one-time code, expires on its own and can be revoked instantly.
- 03
Built for PDPB
Consent capture, data minimisation, immutable access logs and a PDF export of everything held, hosted in the nearest region.
06Product
Real screens. Live product.
The public side of slashcure.com, where patients find doctors and hospitals today. Doctor photos are blurred for privacy.
Finding a doctor
Live · for patients
Finding a hospital
Live · hospital portal
07The details
The details are the product.
Trust is built in small decisions nobody notices until they go wrong. A few we made along the way.
- 01
A zero that doesn’t lie
Metrics we can’t count yet say “Not tracked yet”. A confident 0 would tell a doctor nobody wants them.
- 02
QR codes that outlive a holiday
A doctor’s leave poster is a different sheet, never a different code. What’s printed on the wall keeps working.
- 03
Presence that can’t go stale
“I’m in clinic” expires the moment it’s read after the sitting ends, not when a background job gets round to it.
- 04
Old links never die
Rename a handle and the old one forwards, so a printed code never lands on a different doctor.
- 05
Reviews one side can’t erase
A doctor can ask to hide a review. Only an admin can approve it.
- 06
One schedule, one answer
Every screen reads a doctor’s status from the same function, so a patient and a receptionist never see two different Tuesdays.
08Engineering
One gateway to the data.
Groflex built the whole platform: four portals, the consent engine, QR and PDF generation, and the release pipeline.
The browser never talks to the database. Every request goes through one server that checks who is asking, so a bug in a page can't become a leak.
- Lines of code
- 44k
- Routes
- 335
- Automated tests
- 240
- Weeks, 194 commits
- 12
09In their words
“Everything was built properly, exactly as discussed. We kept making changes along the way, and every one was handled without a single issue. Way better than the competitors.”
10Groflex
We build products people trust.
Slashcure needed more than a website. It needed a team that could handle medical data carefully, keep up with a vision that kept growing, and keep shipping without breaking what was already live. That's the work we do.
What we did
- Product strategy
- UX/UI design
- Full-stack development
- Security & compliance
- Deployment & releases
Handled by Slashcure
- Brand & logo
- Doctor & hospital onboarding
- Marketing & growth