Start with the workflow
Test consent, capture, transfer, review, approval, retrieval, access, and deletion in a controlled setting.
For Clinics
Introduce consultation memory as a managed clinical workflow.
A clinic pilot needs more than a device. It needs clear ownership, patient communication, review responsibilities, support, and evidence that the workflow fits.
Clinic readiness
What a responsible deployment should define.
01
Onboarding
Participating doctors and staff receive a shared workflow for consent, recording, review, access, and escalation.
02
User management
Clinics define authorized users and keep access aligned with each person's responsibility.
03
Export and records
Export requirements will be agreed during pilot setup. Future integrations are outside the first website release.
04
Deployment support
The pilot plan should include device setup, patient communication, incident handling, feedback, and regular review.
05
Measurement
Operational fit, doctor review effort, consent clarity, and record usefulness are assessed before wider use.
Not promised at launch
Clear scope protects the pilot.
The first pilot does not include EHR integration, ABDM integration, billing, multilingual content, clinician dashboards, or autonomous clinical actions. These are future decisions, not hidden launch claims.
Expand only with evidence
Broader deployment should follow clinical, operational, security, and legal review of what the pilot actually shows.