Patient registry and risk banding
Enrol once by mobile number. Every condition the patient lives with sits on the same record, with a risk band that updates as readings arrive.
Chronic care platform
Chronic illness does not happen
in visits.
It happens in between.
Chronia holds one continuous record per patient — across every condition, every clinic, every year. Not a stack of separate visits.
Readings, consultations and prescriptions on a single line — the way chronic care is actually lived.
Why a separate platform
A hospital system records visits. Chronic care needs the line between them.
Episodic systems
Each visit is a new record. The patient explains their history again. Nothing watches the gap between appointments.
Continuous care
One record that runs for years. Readings arrive between visits. The system notices when they stop arriving.
One spine, every condition
The platform does not know what a disease is. The condition pack does.
Around 80% of chronic care is the same work whatever the diagnosis. That shared spine is built once. What differs per condition is configuration — so a new disease is a form to fill in, not a project to quote.
Built once, shared by every condition
- Patient registry and enrolment
- Longitudinal record and timeline
- Care plan engine
- Reading capture: app, SMS, USSD, WhatsApp
- Teleconsultation and e-prescription
- Lab orders and results
- Follow-up, recall and alerts
- Analytics and reporting
Defined per condition pack
- Which parameters are tracked
- Target and watch ranges
- How often each is reviewed
- Red-flag rules and escalation
- Patient education content
- Clinician who signed the pack off
DM2Type 2 Diabetes
HTNHypertension
CKDChronic Kidney Disease
SCDSickle Cell Disease
ASTHAsthma
COPDCOPD
EPILEpilepsy
THYRThyroid Disorder
CVDCardiovascular Disease
ONCFCancer Follow-up
HIVHIV Chronic Care
TBTuberculosis Treatment
OBESObesity / Metabolic
MHChronic Mental Health
Fourteen packs ship ready. Your clinical team approves the thresholds — the approving clinician and date are recorded against each pack.
What is inside
The whole cycle, in one place
Care plans with real targets
Targets, review dates and red-flag thresholds drawn from the condition pack, adjustable per patient by the treating doctor.
Readings from any phone
Blood pressure, sugar, weight and symptoms arrive by app, SMS, USSD or WhatsApp. Every route writes to the same record.
Teleconsultation
Video, audio or chat, with audio fallback where bandwidth is thin. Consent captured before, notes written during, prescription issued at the end.
E-prescriptions and refills
Repeat prescriptions with validity and refill counts, dispensing records, and reminders when a refill falls due.
Labs on the same timeline
Order, result and trend in one view. HbA1c, creatinine and eGFR plot against the target line rather than sitting in a PDF.
Follow-up and recall
Worklists for missed readings, missed appointments and overdue reviews. The people who quietly disappear are the ones this finds.
Population analytics
Control rates, cohort views, defaulter counts and outcome trends by region, facility and condition.
How a patient moves through it
Five steps, then it repeats for years
-
01
Enrol
Registered by mobile number at a clinic, a camp or over the phone. Consent recorded in the patient’s own language.
-
02
Assess
Conditions added, baseline readings taken, care plan generated from the condition pack.
-
03
Monitor
Readings arrive between visits. Out-of-range values raise an alert to the care team, not just a note in a file.
-
04
Consult
Teleconsultation when a review falls due or an alert demands it. Prescription issued on the same screen.
-
05
Review
Targets checked, plan adjusted, next review scheduled. The cycle restarts with the whole history intact.
Who uses it
Three levels of access, cleanly separated
Level 1
Platform administration
Caresoft
Client provisioning, condition pack library, language packs, global settings, full audit trail across every deployment.
Level 2
Client administration and care team
Your organisation
Every setting for your deployment: facilities, staff and roles, condition packs, thresholds, message templates, reports. Doctors, nurses and agents work under it.
Level 3
Patient application
End users
Their record, their readings, their prescriptions, their appointments — on the app, or by SMS and USSD if they have no smartphone.
Built for a regulated deployment
The questions your compliance team will ask, answered before they ask
Data residency is a setting
Each client runs on its own database with a configurable data region, so production can sit in your country where local law requires it.
Consent is a record, not a checkbox
Type, version, language and channel are stored per patient, with the grant and revocation timestamps.
Every action is logged
Who did what, to which record, from which address, at what time — queryable, exportable, immutable.
Language is not an afterthought
No text is hard-coded. English is the default and French is one click away. Further languages are packs, not projects.
Caresoft Systems holds CMMI Level 5, ISO 27001 and PCI DSS, and serves over 1,000 hospitals across India and 12 countries.
Questions
Asked and answered
What is Chronia?
Chronia is a chronic disease management platform that keeps one continuous record per patient across every condition, clinic and consultation.
Chronia is a chronic disease management platform built by Caresoft Systems. Unlike a hospital information system, which records separate visits, Chronia keeps one continuous record per patient over years, covering every chronic condition they live with. It combines a patient registry, care plans, remote vital capture, teleconsultation, e-prescriptions, lab results and follow-up in a single system.
Which chronic diseases does Chronia cover?
Chronia is condition-agnostic. Any chronic condition can be configured as a condition pack, and fourteen packs ship ready to use.
Chronia does not hard-code diseases. Every condition is defined as a condition pack containing the parameters tracked, target ranges, review frequency, red-flag rules and patient education. Fourteen packs ship ready to use, including type 2 diabetes, hypertension, chronic kidney disease, sickle cell disease, asthma, COPD, epilepsy, thyroid disorder, cardiovascular disease, cancer follow-up, HIV, tuberculosis, obesity and chronic mental health. New conditions are added as configuration, not as new code.
Does Chronia include teleconsultation?
Yes. Video, audio and chat consultations run inside the platform and end in an e-prescription on the same screen.
Yes. Chronia includes scheduled and on-demand teleconsultation over video, audio or chat, with an audio fallback for low-bandwidth areas. Consent is captured before the session, clinical notes are written during it, and the doctor issues the e-prescription from the same screen, so nothing is re-keyed afterwards.
Where is patient data stored?
Data location is configurable per client. Production deployments can be hosted in the client country to meet local data protection rules.
Chronia stores each client on its own database with a configurable data region. During a pilot the platform may run on Caresoft infrastructure, and for production the deployment can be moved to the client country or a region of their choice. This matters where health data is a sensitive category and cross-border transfer is restricted, as it is in Senegal under Law 2008-12.
Which languages does Chronia support?
English and French ship by default, and further languages are added as language packs without code changes.
Chronia runs on a full internationalisation layer. English is the default interface language and French can be selected by any user at any time. No text is hard-coded, so further languages, including local languages for patient messaging, are added as language packs.
How do patients send their readings if they do not have a smartphone?
Readings can be sent by SMS, USSD or WhatsApp as well as the patient app.
Patient participation does not depend on owning a smartphone. Chronia accepts blood pressure, blood sugar, weight and symptom entries through the patient app, SMS, USSD and WhatsApp, and every route writes to the same record. Patients marked as voice-first receive spoken prompts instead of text.
Can Chronia work at national scale?
Yes. It is built multi-tenant with region partitioning, queue-based messaging and read replicas for national patient volumes.
Chronia is designed for national deployment rather than single-facility use. Patient data is partitioned by tenant and region, outbound messaging runs through queue workers rather than the web request, reporting reads from replicas, and the application layer scales horizontally behind a load balancer.
Who approves the clinical rules?
The client clinical team authors and signs off every condition pack before it goes live.
Caresoft builds and maintains the engine. Target ranges, review intervals and red-flag thresholds inside each condition pack are authored and approved by the client clinical team, and the approving clinician and approval date are recorded against the pack.
Next step
Tell us what you are trying to run
Send the shape of your programme — conditions, patient numbers, who delivers care — and we will come back with a walkthrough built around it.