RxAssist
- CATEGORYPatient companion, white-label
- PLATFORMiOS & Android, offline-first
- AIOn-device inference, no server
- BEST FORHospitals & clinical groups
A white-label patient companion app that records what happens between visits: which doses were taken, which were skipped, how the numbers moved, and what the paperwork said. All of it stays on the patient’s own phone. You ship it under your own brand, and it goes live on both stores in about six weeks.
At 11:04 AM the plan is perfect. The patient is carrying most of it in their head.
Five instructions leave the consulting room. Four of them were only ever spoken aloud, and nothing on the list records whether the patient managed to follow it.
Prescription
Printed once, then folded into a bag.
On paper
Dose & food timing
Explained once, at speed.
Spoken only
Follow-up date
“In about a month.”
Spoken only
Diet restriction
Ninety seconds on salt and sugar.
Spoken only
Lab requisition
“Before the next visit.”
Often undone
Each instruction has its own half-life. None of them are measured.
By the follow-up the plan has decayed unevenly, and none of that decay is in the record. Non-adherence tends to surface thirty to ninety days late, by which point it reads clinically as treatment failure and the next decision is usually to escalate.
The bars are illustrative. The point is that the decay is uneven and currently unmeasured.
Four things a clinician needs at the door of the follow-up.
All four are patient-side behaviour, and none of them are in your hospital system. That is why the record is kept where the behaviour actually happens, which is the same principle behind our healthcare engineering work.
Was the medicine actually taken, dose by dose, and what was the reason behind each skip?
What did the numbers do? A trend line, rather than a single value read out from memory.
What happened elsewhere? Second opinions, labs and films, gathered in one place.
Did the patient arrive prepared, with the blood test done, the fast kept and the old films in the bag?
What the patient companion app records between visits.
The patient’s half of the care plan, kept on their own phone. Doses, vitals, documents and visits are captured as they happen, so the follow-up starts from a record rather than from memory.
Doses
Taken, skipped or rescheduled. Every event is stored with the reason the patient gave for it.
Vitals
Blood pressure, glucose, SpO₂, weight and symptoms, logged over time rather than recalled at the door.
Records
Prescriptions, labs, films and bills, filed by camera and recognised on the device.
Visits
A checklist before the appointment, and a summary the patient can hand over at the door.
The assistant runs on the phone itself, with no server in the middle.
This is the smallest exposure surface we could design for: an on-device database, on-device inference, and no third-party analytics on clinical content. Where cloud sync or HIS integration is genuinely required, it is a scoped customisation with its own compliance review.
Works with no connectivity
Reminders, logging, scanning and the assistant all function offline, so patients on a weak rural signal get the whole product rather than part of it.
The record is never transmitted
The database and the inference both sit on the phone. No IndiaNIC server and no hospital server holds a patient record.
No per-query AI cost
Because inference is local, assistant usage does not scale your bill. Encrypted backup stays under the patient’s control.
Ask out loud, and the answer comes back from the record.
Your oldest patients are usually your highest-risk ones, and they are the least likely to work through an app. Someone who cannot navigate a screen can still ask Siri, and the answer is quoted from their own record rather than from the internet.
Apple Intelligence, on device
The answer is composed on the phone by the same model that powers the in-app assistant, so there is no inference server and no clinical data in transit.
Spoken, not navigated
A patient who cannot navigate an app can still ask out loud, and a carer can ask about the parent they manage. Siri quotes the record rather than giving a generic answer.
Nine shortcuts, no setup
Today’s doses, next visit, medicine stock, all medicines, latest readings, adherence, doctors and medical spending ship built in, ready for automations and the Home screen.
“What do I take this morning?”1/3
Every dose is a recorded event, including the ones that did not happen.
A skip is captured with the reason the patient gave and any reschedule that followed, so the next consultation starts from behaviour rather than from inference. Refills are flagged at seven days of cover instead of at zero.
Timeline1/4
For chronic care the trend is the diagnosis. For acute care, completion is the whole job.
The same record serves both, which is why one app covers a titration history running over eighteen months and a ten-day antibiotic course.
Chronic, where the trend is the point
Systolic pressure and fasting glucose plotted across months, annotated with what changed: a drug started, a dose titrated, a sodium restriction, a second drug added. Adherence sits on the same axis, so a flat response can be read against whether the plan was actually followed.
Acute, where finishing is the point
A ten-day course tracked day by day, with the point where symptoms resolve marked well before the course ends. A pre-visit checklist confirms the blood test was done and the fast was kept, and the visit summary is produced before the consultation rather than recalled inside it.
One person usually manages the medicines for three or four. The app is built for that person.
A parent on eleven medicines across three prescribers, a child on two short courses, and the caregiver’s own plan, which always comes last. Seventeen medicines, five prescribers, one phone. Profiles are unlimited, with no per-person licence and no separate login.
Parent, chronic
Eleven medicines across three prescribers, with overlapping mechanisms to keep track of.
Child, acute
Two medicines from one prescriber, plus short courses and immunisation records.
Self, deprioritised
Four medicines from one prescriber. The caregiver’s own plan, always seen to last.
This is what a patient actually opens.
Eighteen screens from the shipping app, not mockups. Page through them with the arrows, or swipe on a phone.
Today1/18
Localised where it actually matters, which is deeper than the menus.
Reminder copy, dose instructions, diet items and the assistant’s answers are all translated, so an elderly patient reads “after food” in the language they think in. English, Hindi and Gujarati ship as standard, and further languages are available on request.
English
Due now. Amlodipine 5 mg, after food.
हिन्दी
अभी लेनी है। एम्लोडिपिन 5 मि.ग्रा., खाने के बाद।
ગુજરાતી
હમણાં લેવાની. એમ્લોડિપિન 5 મિ.ગ્રા., જમ્યા પછી.
White-label: it ships as your app, not ours with your logo in a corner.
You get a production app, themed and submitted under your own brand, which costs considerably less than commissioning one from scratch and arrives a great deal sooner. If you would rather validate a variation first, our rapid POC track is the usual place to start.
You provide
- Brand assets, colours and tone
- Developer accounts, or we create them
- Clinical review of the default content
- A named point of contact
We deliver
- Full visual theming across icon, splash, palette and typography
- App store submission, review handling and releases
- Configured defaults for diet templates, vitals and notification copy
- Versioned updates, OS-compatibility maintenance and technical support
Built once, properly, then maintained continuously.
Live on both stores in week six. Maintenance then runs with no end date and is absorbed by us rather than by your IT team, handled by the same mobile app engineering practice that builds our client work.
- 1 week
Brand intake
- 2 weeks
Configuration
- 1 week
QA
- 1–2 weeks
Store submission
- Week 6
Live on both stores
Maintenance, absorbed
- Annual OS releases
- Store policy changes
- SDK deprecations
- Crash monitoring and fixes within SLA
Extend the app with
- HIS / EMR integration
- Cloud sync
- Appointment booking
- Teleconsult
- Analytics dashboard
What is in the box.
Everything below ships configured rather than as a backlog. RxAssist is one of several production products we deploy under a client’s brand, and the rest are on the products index. The mobile engineering team behind them takes on the customisations.
Medications
Medicines and reminders, stock and reorder, dose tracking, and prescriptions.
Vitals and symptoms
Vitals logs, a daily health log, and a single timeline.
Clinical encounters
Doctors, hospitals, visits with pre-visit checklists, and visit summaries.
Documents and bills
Documents, bills with insurance export, and scan-and-recognise intake.
Diet plan
Restricted, controlled with quantity caps, preferred and allowed, each with its clinical reason.
Platform
On-device AI assistant, encrypted backup and restore, multi-profile family management, and three languages.
The questions hospitals ask first.
Where is the patient record stored?
On the patient’s own device. RxAssist uses an on-device relational database, so there is no central patient data store operated by IndiaNIC and no copy sitting on a hospital server. Backup and restore are encrypted and stay under the patient’s control.
Does the AI assistant need an internet connection?
No. Inference runs on the phone, so the assistant answers in airplane mode. Reminders, logging and scanning work offline too, which means patients on a weak signal get the whole product. Because inference is local, assistant usage does not add a per-query cost.
How does the Siri integration work?
A patient can ask out loud, for example “what do I take this morning?” or “am I running low?”, and the answer is composed on the phone by the same on-device model that powers the in-app assistant. Nine shortcuts ship built in, with no setup required from the patient.
Can it be shipped under our own brand?
Yes. RxAssist ships as your app rather than ours with your logo added to it: full visual theming across icon, splash, palette and typography, submitted to the app stores under your developer accounts, with configured defaults for diet templates, vitals and notification copy.
How long does it take to go live?
About six weeks on both stores, covering a week of brand intake, two weeks of configuration, a week of QA and one to two weeks of store submission. Maintenance then continues with no end date, absorbed by us rather than by your IT team.
Can one person manage several patients?
Yes. Profiles are unlimited, with no per-person licence and no separate login, and one tap switches the whole app context. The app is built for the household member who manages medicines for a parent, a child and themselves from a single phone.
What languages does it support?
English, Hindi and Gujarati. Reminder copy, dose instructions, diet items and the assistant’s answers are all localised, rather than only the menus. Additional languages are available on request.
The app on a device with your clinical team, in airplane mode.
Forty-five minutes. We run RxAssist with connectivity switched off, walk your clinicians through what it records between visits, and scope what your branded version would look like.