Clear answers. Clear boundaries.

CareSaathi is the patient-facing continuity experience and service brand. ACIS—the Adaptive Continuity Intelligence System—is the governed execution, evidence, routing and audit system designed beneath it.

No. ACIS supports execution, education, evidence and coordination. It does not independently diagnose, prescribe, change medicines or override approved clinical advice.

No. It can structure scheduled checks, capture patient-reported information and route configured signals. It does not imply continuous clinician observation or guaranteed real-time response.

No. In an emergency or with severe or worsening symptoms, contact the treating team or local emergency services immediately. After-hours coverage requires an explicit approved programme policy.

The patient journey is WhatsApp-first. Coordination, case management, governance, summaries, delivery operations and clinical review can use other configured surfaces.

Depending on the programme, it can combine meals, medicine reminders, movement, hydration, symptom checks, vitals, proof, due laboratory work, OPD follow-up, safety wording and one immediate priority.

The designed workflow can account for late meals, poor intake, travel, fasting, outside food, symptoms and household availability while preserving already-delivered guidance and protected clinical instructions. Availability depends on the implemented programme.

No. Documented medicine context can constrain diet, timing, hydration or movement guidance, but ACIS does not start, stop, substitute or change medication doses.

Missing information remains missing. The intended safety behavior is clarification, review-first, hold, block or escalation—not confident invention.

AI may assist with patient-friendly wording, bounded classification, clarifying questions and evidence-backed summaries. It must not diagnose, prescribe, invent evidence, reassure emergencies or bypass governance and audit controls.

They describe a development architecture for twelve condition-specific longitudinal bundles sharing one governed execution spine. They are not twelve identical templates, and they are not all represented as production-ready.

Eligible medicine, comorbidity, nutrition, recovery, day-mode and safety contexts can constrain permitted actions. Emergency safety, doctor advice, discharge restrictions and medicine obligations take priority over defaults and convenience.

Evidence-backed workflows include patient-level operational context, unified proof and escalation case management, assignment, acknowledgement, resolution, closure, lifecycle history and message-state visibility. Exact release and deployment status must be confirmed.

Yes. A bounded pilot can start with one cohort and workflow, provided clinical authority, ownership, service coverage, escalation boundaries and learning measures are explicit.

Subject to clinical suitability, geography, credentialing, scheduling and contracted scope, programmes may coordinate nursing, physiotherapy, counselling or therapy, and aesthetic-care therapy.

No. Intended advantages include stronger continuity, structured evidence and clearer ownership. Claims about readmissions, complications, adherence or biomarkers require prospective evidence.

Patient information is intended to be processed according to applicable consent, access-control, privacy and healthcare-governance requirements, with role-based visibility limited to required care and operations.

No. Conditions, languages, roles, staffing, integrations, service availability, response expectations and clinical approval are deployment-specific.