Amela
For confidentiality, company names, service names and system images have been replaced with pseudonyms and mocks.
Healthcare Network Operator — Platform Build Story

Care & prescription procedures —all on one phone. A platform that delivers it.

MediOrder is an end-to-end medical ordering platform connecting patients, clinics and pharmacies — completing clinic booking, digital intake, e-prescriptions and pharmacy integration in a single mobile app. A 5-app integrated solution built from React Native patient apps V1+V2, a clinic web CMS and a NestJS backend.

“Half a day lost per visit · paper intake forms · manual clinic operations · the burden of returning to the pharmacy” ─ the story of launching a brand-new platform, built in-house from scratch in 16 months, that satisfies all four axes a medical ordering system requires.

Integrated apps
5 Features
API + 2 RN + CMS + LP
Stakeholders
3 Role integration
Patient · Clinic · Pharmacy
Flow
End-to-end
Booking → Intake → Prescription → Pickup
Supported platforms
iOS / Android
React Native V1+V2 migration complete
01
CLIENT
About the client

The “healthcare network operator,” driving medical digitization.

The healthcare network operator is a B2B2C business running a medical network that links clinics, pharmacies and patients. The care journey burned time across many steps — “phone booking → waiting at the hospital → paper prescription → waiting again at the pharmacy” — while clinics, still paper-based, struggled to improve operational efficiency.

Aiming to “complete everything from booking to prescription pickup on a single phone,” we built the medical ordering platform in-house. We run five integrated applications: patient-facing React Native apps (V1+V2), a clinic-facing web CMS and a NestJS backend.

Integrated apps
5 (API+2 RN+CMS+LP)
Stakeholders covered
3 (Patient / Clinic / Pharmacy)
Flow
E2E Booking → Prescription → Pickup
BUSINESS FLOW
01
STEP
Clinic booking
Select a doctor and time to book online
02
STEP
Digital intake
Answer intake on your phone before the visit
03
STEP
Consultation + prescription
Issue e-prescriptions (QR / API)
04
STEP
Pharmacy pickup
Pharmacy selection · Delivery / In-store pickup
02
CHALLENGE
Design challenges to solve

Four structural requirements demanded of the platform.

None of these are questions of tech choice — they are business requirements tied directly to the care experience, clinic efficiency, prescription integration and data consistency.

① Leave the patient experience as phone + paper + waiting, and half-day visits persist

Keep booking, intake and prescriptions on paper, andHalf a day per visit becomes a permanent burden.

② Rely on paper ledgers for clinic operations, and partnership growth stalls

If booking management stays phone + ledger,the more clinic partnerships, the more operational load explodes .

③ Keep prescriptions on paper, and a return trip to the pharmacy stays mandatory

Carrying paper prescriptions around meanswaiting again at the pharmacy is unavoidable.

④ Leave the RN app on an old version, and it hits a maintenance ceiling

Keep running on the old React Native (V1), andlatest-OS support and new features become difficult.

03
ARCHITECTURE
The architecture we built together

Turning medical ordering into an “unstoppable platform” across four domains.

We built the healthcare network operator's medical ordering platform entirely in-house, from the ground up. On a shared NestJS + TypeORM + MySQL backend, we integrated patient-facing React Native apps V1+V2, a clinic-facing web CMS, and a landing page. Three stakeholders — patients, clinics and pharmacies — connect through a single database.

Domain ①
Patient App
Challenge
Leave the patient experience as phone + paper, and half-day visits persist.
Solution
Simultaneous iOS / Android development with React Native
After the V1 release, V2 migrated to the latest RN CLI. Push notifications + deep links complete the booking flow.
Domain ②
Clinic CMS
Challenge
Rely on paper ledgers for clinic operations, and partnership growth stalls.
Solution
Centralized booking, intake and prescriptions in a TypeScript SPA
Clinic reception and doctors check booking status in real time on the same screen — prescription issuance in one click.
Domain ③
Prescription integration
Challenge
Keep prescriptions on paper, and a return trip to the pharmacy stays mandatory.
Solution
Send e-prescriptions directly to the pharmacy via QR + API
Patients pre-select a pharmacy; the pharmacy app confirms receipt instantly; choose delivery or in-store pickup.
Domain ④
Unified API
Challenge
Build a separate DB per app, and data consistency is lost.
Solution
Unified into one platform with NestJS + TypeORM + MySQL
Five apps reference the same database, with JWT auth separating permissions across three stakeholders.
TECH STACK
Mobile
React Native (V1+V2)N Push notifications
Backend
NestJS TypeORM JWT Redis
Infra · CMS
MySQL 8 TypeScript CMS Docker PM2
04
IMPACT
The value the platform creates

The healthcare network operator's “care experience” accelerates.

This platform continuously delivers business outcomes — shorter visit times, clinic operational efficiency, prescription digitization and three-party integration — not just technical metrics.

① A platform that drastically cuts visit time

Booking · intake · prescription · pickup, all on a phone. The half-day care experience is dramatically shortened.

② A design that makes clinic partnerships scalable

Moving from paper ledgers to the CMS lowers the operational load when onboarding new clinics, making network expansion easier.

③ A setup that eliminates return trips to the pharmacy

Send e-prescriptions directly to the pharmacy. Delivery options can fully eliminate a return trip to the store.

④ A design that lets you focus on feature expansion

With a unified API and migration to the latest RN (V1→V2), new features can ship to all three stakeholders at once.

05
DEMO
Three scenarios

Experience the healthcare network operator's solution through a working demo.