Offline first, and multilingual from the first release
Both were promoted from optional extensions to core requirements, because in the segment this serves neither is optional.
Connectivity is intermittent, not absent
Capture never blocks on the network
A consultation completes whether or not there is a connection.
Synchronisation is background and resumable
Interrupted sync resumes; it does not restart.
Conflicts are surfaced, not silently resolved
Where two edits disagree, a human sees both.
The clinician can always tell the state
Whether a record is local or synced is visible, because uncertainty about that is what makes people keep paper.
What the clinician can always tell
Telugu, Hindi and English at release one
Localisation is specified in layers rather than as a single translation task: interface chrome, content, clinical terminology display, patient-facing output such as prescriptions, and data entry itself. A clinic that operates in Telugu needs the prescription printed in Telugu, not an English prescription in a Telugu interface.
Clinical terminology display is the layer that carries the most risk, because a translated term that drifts from its coded meaning is worse than an untranslated one. Terminology display is therefore bound to the code, not to the string.
One sentence
A clinic that cannot use the software during a power cut, in the language it practises in, will use paper
Everything else in the specification is downstream of that.
Read the platform roadmap.
What is specified, and what is next.