The statewide vision: understand a health concern, find nearby care, check benefits and connect records and appointments—all through one familiar conversation.
Connect navigation, access, financial protection and continuity of care. Give citizens a clear next step and health leaders a coordinated service model.
Help people find care, understand benefits and continue their journey in the chat they already use—without learning separate service portals.
Connect the citizen to the responsible facility, scheme desk or care team, with consent and confirmation at each handoff.
Review where citizens need help, which services are connected and where journeys stall. Use confirmed service data to set improvement priorities.
Eight connected journeys, with service-specific verification, consent and human oversight. Preview the experience below.
Help people describe a concern, understand when clinical assessment is needed and reach the right care team.
Planned · clinical reviewFind facilities using a village, PIN code or location shared with permission. Confirm services and hours with the facility.
Planned · directory connectionCheck relevant government schemes, eligibility, documents and applicable benefit amounts against verified rules and records.
Planned · scheme verificationGuide voluntary health-identity creation or retrieval through official verification, with the citizen’s consent.
Planned · ABDM connectionHelp citizens link, view and share records from participating care providers through a consent-based journey.
Planned · connected providersDiscover connected providers and slots, request a visit and receive a confirmed booking, reminders and next steps.
Planned · provider connectionExplain policy or scheme cover, network hospitals, required documents and verified claim status through connected services.
Planned · insurer / assurance connectionRaise a facility concern, follow its ticket and speak with an official. Keep accountability inside the wider care journey.
Current grievance foundationExplore the proposed care experience through prewritten examples. Each service is activated only with its required clinical review, verification and provider connection.
A citizen starts with a need. The proposed assistant guides the right service, the required verification and the next confirmed step.
Open the statewide chat or scan an activated facility code. Tell the assistant what you need in a familiar conversation.
Connect to facility information, scheme guidance, identity verification or an available care team through approved service connections.
Approve necessary access, receive the service provider's confirmation and follow the next step. A person takes over when judgement is needed.
A statewide product vision. The current foundation supports facility grievances. Additional care journeys require approved clinical content and connected services before activation.
See the service connectionsThe product vision is simple: communicate in any Indian regional language, using the format that feels natural to you.
Describe what happened in a simple message. Guided replies keep the next step clear.
Grievance foundation: English & MarathiThe voice-support vision gives people a way to explain a concern without typing a long message.
Voice intake & transcription: plannedAdd a photo to give the responsible team useful context about the facility concern.
Photos retained with the ticket historyAdditional language coverage is planned. Confirm language and voice availability when defining your rollout.
The proposed assistant guides the journey. Official services, care providers and scheme authorities verify and confirm the outcome.
Guide ABHA creation or retrieval through official verification. Link and share records from participating providers through the citizen’s permission.
The proposed flow should make the purpose, receiving provider, records and access period clear before sharing. Citizens must be able to manage their permissions.
Official health-identity and records guidance ↗Show what applies to the citizen and the treatment using the relevant authority’s verified information.
An annual coverage cap, an approved treatment package and a cash benefit are different amounts. Final entitlement and claim approval remain with the authority or insurer.
Official national health-assurance reference ↗Clear rollout scope. Facility grievances, official routing and English/Marathi text with photos are the current foundation. Symptom support, citizen facility discovery, benefit checks, ABHA, connected records, booking and insurance connections are proposed services. Activation requires the relevant approvals, verified sources and service-provider connections.
The statewide vision connects citizen journeys with responsible care teams. The existing grievance workspace provides the first layer of departmental accountability.
Grievance overviewDistrict office⌄
Use approved information for routine guidance. Route clinical questions to qualified care teams and administrative concerns to the responsible official.
Assign responsibility, track resolution deadlines and escalate unresolved cases. Alerts keep the responsible team informed as the case progresses.
The grievance foundation already scopes officials by jurisdiction. The expanded vision adds service ownership for care referrals, benefit checks and follow-up as each connection is activated.
Shape the assistant around your state’s languages, facility network, government schemes and care pathways. Give citizens one familiar entry point into the services that matter to them.
WhatsUp.HealthOne entry point. Coordinated next steps.
Configure locally. Connect priority services. Validate before scaling.
What citizens can expect, and what a statewide rollout must connect.
Citizens use a familiar WhatsApp conversation, with no separate app or service portal to learn. The proposed assistant guides the next step for each connected service.
The existing foundation supports facility grievances, ticket tracking, official handoff and the departmental workspace. The wider health assistant is the product vision: its previews do not perform medical assessments, eligibility checks, ABHA creation, record retrieval, bookings or claims.
Symptom support is planned as clinically reviewed guidance and care navigation. Diagnosis and treatment decisions belong to qualified healthcare professionals. Urgent needs should go directly to emergency care.
The proposed journey checks the relevant scheme or policy, citizen documents, covered treatment and verified benefit information. An amount is confirmed by the responsible authority or insurer. A coverage limit is not a promise of cash payment.
The vision is to guide voluntary ABHA creation or retrieval through official verification and connect records from participating providers through explicit consent. These connections are planned. ABHA connects health identity and records; scheme or insurance entitlement is checked separately.
Participating providers confirm appointment slots and bookings. The relevant scheme authority or insurer confirms cover and claim decisions. The assistant should show only verified confirmations and status from those connected services.
The current grievance foundation supports English and Marathi text, plus photos. The wider vision includes every Indian regional language, voice and images. Expanded language and voice coverage is planned and must be confirmed for the rollout.
Anonymous filing is available for grievances. Health identity, record sharing, appointments and insurance journeys require the appropriate verification and consent. Each journey must explain which details it needs and why.
For urgent medical help, contact your nearest emergency department or local emergency service directly. The website is a product preview and does not provide an emergency response or clinical assessment.
Scope a statewide assistant around priority citizen journeys, approved clinical guidance and the service connections your programme needs.
For product enquiries and implementation discussions.