Swasth: Annual Wellness Visit preparation agent

Swasth prepares Annual Wellness Visit work for staff review. It assembles candidate review queues from data an organization already holds and has authorized, shows why each record appears and which inputs are missing, and routes incomplete or conflicting records to an exception queue. People decide who is contacted and when. Swasth does not perform the visit, determine Medicare coverage, or produce billing evidence.

A deployment reads authorized patient identity, scheduling, visit-history, contact-preference and task-status data through whichever access route your organization approves, which may be APIs, governed feeds, a data warehouse, or an existing integration layer. Every queue row carries its source, timestamp and inclusion reason so a reviewer can see why it is there. Field definitions, matching rules and refresh expectations are agreed with your team before implementation.

No. Swasth is EHR-agnostic and runs as a cloud-hosted service over the access route your organization approves. EHR-agnostic does not mean integration-free: each deployment still needs field mapping, patient matching, validation, access controls, failure handling, and an explicit read-only or write-back model. Synodha claims no endorsement by Epic or by any other EHR vendor.

Require a named owner for every queue, role-based access, visible provenance and timestamps, approved communication channels, an explicit human approval point before any outreach leaves the organization, an exception queue for uncertain matches, audit events, and a documented downtime procedure. Eligibility verification, outreach approval and clinical work stay with accountable people.