one continuous journey, from pregnancy to childhood.
Life-cycle first
Visits are not isolated events. Every consultation joins a continuing pregnancy or child health journey.
Multi-branch by design
One platform across the chain. Doctors work at several branches; patients follow their doctor.
Mother–child linked
A delivery creates the baby's record and links it to the mother — permanently.
Hospital-controlled data
Designed to run inside the hospital's own infrastructure. The hospital owns its patient database.
Not an appointment book.
A continuous record of a family's care.
Women & children hospitals do not treat one-off patients. They look after a woman through a pregnancy, deliver her baby, and then care for that child for years. VEHA OPD is built around that reality rather than around a calendar.
What we are building
An OPD platform for women & children hospital chains: doctor calendars, slot booking, reception check-in, doctor queue, consultation, prescription — organised around the patient's life-cycle.
Why it matters clinically
Continuity reduces repeated history-taking, catches missed follow-ups, and lets a doctor see the whole pregnancy or the child's full growth pattern in one screen.
Why it matters commercially
Follow-up care is the revenue engine of this speciality. A system that actively surfaces the next due visit protects that engine.
Why generic OPD software
is not enough here.
General hospital software treats every visit as a transaction. That model breaks down in a speciality where the same patient returns fifteen times in nine months, and then returns as two patients.
A speciality defined by repeat visits.
The clinical pathways in this speciality are unusually predictable and unusually long. That is exactly what makes software valuable — and what generic systems ignore.
The mother is the entry point
Acquiring one pregnant patient creates a decade of paediatric demand. The system should make that continuity explicit, so the hospital retains the family rather than just completing a delivery.
Missed follow-ups are the leak
A 32-week scan or an 18-month booster that quietly slips is both a clinical risk and lost revenue. Because VEHA OPD knows the expected schedule, it can surface what is due.
Chains, not single clinics
Women & children groups typically run several neighbourhood branches with consultants rotating between them — a scheduling problem generic tools handle poorly.
A young, mobile-first patient base
Expectant mothers and young parents expect to book, reschedule and read their records on a phone.
Genuine data sensitivity
Maternity and paediatric records are among the most sensitive a hospital holds — which is why hospitals resist third-party cloud custody.
The life-cycle journey is the product.
Every booking, check-in, consultation, prescription and investigation attaches to a journey. The journey — not the appointment list — is what staff and patients actually look at.
Cycles, not one flat list
A woman may have several pregnancies. Each becomes its own cycle in her journey, so a third pregnancy sits alongside — not on top of — the previous two.
Past, present and expected
Completed milestones, the current visit and the expected next steps are all visible, which makes an overdue follow-up obvious at a glance.
Built for the consulting room
The doctor opens a patient and sees journey position, last visit, allergies, current medicines and previous diagnosis before saying a word.
Where one patient record
becomes a family.
Delivery is the moment most systems lose the thread: the mother's episode closes and a brand-new, unrelated infant record begins. In VEHA OPD the link is permanent and works in both directions.
2024 pregnancy → Aarav
Current pregnancy → 28 weeks
What the doctor gains
A paediatrician sees that this child was born at 38w4d by LSCS at this hospital, birth weight 3.1 kg, mother hypothyroid — without asking. A gynaecologist sees the previous LSCS when planning this delivery.
What the parent gains
One login, one phone number, one app — Priya switches between her own pregnancy and each child's record, and books for any of them in a few taps.
Four roles, one shared record.
Each role sees the same patient through a different lens. Nothing is re-entered as work moves from the desk to the consulting room to the patient's phone.
- Branches, specialties, doctors
- Users, roles and branch access
- Doctor OPD calendars
- Appointment rules and durations
- Volume, status and waiting-time analytics
- Today's OPD workflow board
- Search patients, quick registration
- Book, reschedule, cancel, walk-in
- Mark arrival → doctor queue
- Live queue and waiting times
- My day, next patient, waiting queue
- Patient workspace with journey timeline
- History, allergies, medicines, investigations
- Consultation notes and prescription
- Follow-up plan and referral
- Family profiles — mother and children
- Book, reschedule, cancel
- Journey, records and prescriptions
- Doctor availability across branches
- Follow-up and vaccination reminders
A chain, not six
separate installations.
Doctors rotate across branches. Patients want their doctor, not a location. VEHA OPD treats the branch as a dimension of the schedule rather than a boundary around the data.
Branch-aware calendars
A doctor's week is a set of sessions, each with its own branch, day, timing and consultation duration. Dr. Ananya Rao holds Kothapet mornings all week and Attapur evenings on Tuesday and Thursday.
Same doctor, another branch
If the preferred doctor has no slot at the usual branch, the system offers her next session elsewhere in the chain — with the earliest free time shown.
Next available doctor
When the patient cannot wait, the system ranks every doctor in that specialty by earliest free slot across all branches.
From doctor calendar
to bookable slot.
Nobody types slots into the system. The admin or doctor defines a session; VEHA OPD generates the slots and keeps them consistent with what is already booked.
Booked at the desk
Choose patient → specialty → doctor → branch → date → slot → confirm. Quick registration creates a new patient and continues straight into booking.
Booked by the patient
The same flow on the phone, starting from which family member the appointment is for — with cross-branch and next-available fallbacks built in.
One board that answers
"what is happening right now?"
The front desk is the busiest role in an OPD. The reception dashboard is built so a new staff member can read the state of the entire branch in a few seconds.
Waiting room and queue
Who has arrived, which doctor they are waiting for, and how long they have been waiting — so the desk can answer the question every patient asks.
Context, not just names
Each row carries what matters here: gestational age for an expectant mother, age and vaccination status for a child, visit type and doctor.
Open a patient.
Understand them immediately.
A consultant running a 15-minute slot cannot hunt through tabs. The patient workspace front-loads the few things that change clinical decisions.
My Day
Session timing and branch, next patient, who is waiting and for how long, what is completed, and what is still to arrive.
Journey Timeline
The full life-cycle: previous pregnancies, this pregnancy's milestones, linked children — with the current visit marked in place.
Clinical Context
Pregnancy or child summary, allergies, current medicines, previous visits, investigations and the last recorded diagnosis.
One account.
The whole family.
The patient app is where continuity becomes visible to the family. A mother switches between her own pregnancy and each child without logging out or maintaining separate accounts.
Home
Greeting with live pregnancy week or child growth status, the next appointment with branch and token, and the upcoming follow-up.
Appointments
Upcoming, completed and cancelled. View, reschedule, cancel and get directions. Video consultation is visibly marked as Phase 2.
Family
Every linked profile with its own journey progress, visit count and next vaccination due. One tap switches context everywhere.
Records
Journey, visit history, prescriptions with dosage and instructions, lab reports and the doctor's written advice.
When the usual doctor is full
The app says plainly: "Available at Paramitha Attapur — tomorrow 4:00 PM", or offers to show the next available doctor in that specialty ranked by earliest slot.
Notifications that mean something
Appointment tomorrow at 10:30 AM · Aarav's MMR-2 booster is due in two weeks · your 32-week scan is recommended next week · prescription ready to view.
Enough insight to run the OPD.
Not a BI project.
Management needs a small number of numbers they will actually act on, at chain level and per branch — not a hundred charts nobody opens.
Configuration
Branches, specialties, doctors, consultation durations, OPD calendars, booking windows, check-in and no-show rules, and patient app permissions.
User administration
Add and edit users, assign role and branch access, activate or deactivate accounts. Doctor profiles carry qualification, specialty, branches and schedule.
Operational analytics
Appointments today, completed, cancelled, no shows, walk-ins and average waiting time — sliced by branch, specialty and doctor.
Phase 1 — the MVP.
Everything below is demonstrated in this prototype. It is the scope required to run a real OPD day end to end across a multi-branch chain.
Phase 2 — reach and convenience.
Phase 2 extends the platform outward to the patient's phone and wallet. None of this is implemented in the prototype; it is marked as forthcoming wherever it would appear.
Why video is not in Phase 1
Tele-consultation needs a waiting room, payment, consent and prescription delivery to be genuinely useful. Shipping it before the core OPD flow is stable creates a poor clinical experience.
Why reminders come next
Once the system knows the expected follow-up schedule — which Phase 1 establishes — reminders become the highest-return addition for both attendance and clinical outcomes.
Where continuity pays off.
A connected longitudinal record is the prerequisite for everything on this list. These are opportunities the life-cycle model unlocks — not commitments in the current scope.
The hospital owns its patient data.
Hospitals are rightly cautious about maternity and paediatric records sitting with a third-party cloud provider. VEHA OPD is designed so that concern does not become an objection.
Hospital-hosted deployment
What may sit outside
Per-hospital tenancy
Each hospital chain runs its own instance with its own branding, branches, specialties and doctors.
Reusable, not bespoke
Paramitha is the first implementation, not the architecture. Another women & children chain is a configuration exercise.
Standards-ready
ABDM/ABHA and FHIR interoperability are planned as later-phase additions on top of the same record.
Why this wins in
women & children hospitals.
1 · Life-cycle patient journey
The defining feature. No visit stands alone; every consultation extends a pregnancy or child health journey that any doctor can read in seconds.
2 · Mother–child continuity
Delivery links the mother's record to the newborn's permanently, and the family shares one patient app account.
3 · Genuine multi-branch model
Branch-aware doctor calendars, cross-branch availability and next-available-doctor fallback — built in, not bolted on.
4 · Calendar-driven slots
Define a session and duration; slots generate themselves and stay consistent with bookings, check-ins and cancellations.
5 · Reception → doctor hand-off
Check-in puts the patient in the doctor's queue instantly, with waiting time visible to both sides of the desk.
6 · Speciality-aware clinical context
Gestational age, EDD, obstetric score and risk flag for mothers; growth centiles and immunisation status for children.
7 · Patient app that earns its place
Family profiles, real availability, records and journeys — not a thin booking form.
8 · Hospital-controlled deployment
Removes the single biggest objection in the sales conversation: where does our patient data live?
9 · Reusable across chains
Paramitha is demo data. The same product configures for any women & children hospital group.