Data governance
Define what data the system may use, where it is processed and how long it is retained.
Trust centre
The evidence behind a healthcare deployment.
Security, privacy and clinical safety are reviewed together because every production agent touches a combination of people, data, decisions and actions.
Core controls
Designed around healthcare data and operational risk.
The exact control set depends on the deployment, integrations and data involved. These are the foundations we expect every system to address.
Access control
Restrict access by role and maintain evidence of sensitive data and system access.
Encryption
Protect information in transit and at rest across the services involved in each deployment.
Deployment isolation
Separate provider environments, credentials, policies and operational data.
Auditability
Review interactions, system decisions, tool actions, policy outcomes and human overrides.
Incident readiness
Maintain clear ownership, escalation and communication for security and safety events.
Research signal
Plausible ≠ safeA confident answer can still be wrong.
WHO warns that health-related LLM responses may appear authoritative while containing serious errors, and calls for expert supervision and rigorous evaluation.
WHO · Safe and ethical AI for healthIn practice
Evidence before assurance
Iksha reviews what the agent understood, the policy it applied, the action it took and when a person overrode it.
Review framework
What we bring into diligence.
We keep claims precise. Current certifications, deployment-specific responsibilities and available evidence are confirmed during the review rather than implied by a badge.
| Area | How we address it | Review evidence |
|---|---|---|
| Healthcare privacy | Patient-data access, consent, processing, retention and disclosure are configured for the deployment context. | Data-flow documentation and deployment controls |
| Security assurance | Infrastructure, access, change and incident controls are reviewed as part of enterprise deployment. | Security brief and supporting evidence |
| India DPDP | Consent, purpose limitation, data rights and notices are reflected in product and operational design. | Data processing and consent documentation |
| Clinical safety | Permitted actions, human authority and escalation are defined for the use case before production. | Safety specification and evaluation evidence |
Shared responsibility
Trust depends on how the system is deployed.
We define responsibilities across Iksha, the healthcare provider and technology partners before launch—covering data, integrations, access, monitoring, incidents and clinical escalation.
01
Scope
Agree what the agent may access, communicate and do.
02
Evidence
Document controls, evaluations, operational ownership and known limitations.
03
Oversight
Review performance, incidents and changes throughout the deployment.
Bring security, clinical and operational teams into one review.
We will walk through the architecture, responsibilities and evidence relevant to your deployment.