Home

Healthcare

Keep patient identifiers out of AI chat and control clinical tool calls.

UK-first AI governance for healthcare teams: local checks for patient identifiers before Send, plus a separate MCP gateway for agent access to configured clinical tools.

Start a team pilot →

The problem

Patient information can enter AI systems through everyday chat prompts and through automated tool calls. Healthcare teams need practical controls and reviewable evidence that support their UK GDPR, Data Protection Act and confidentiality obligations.

Two separate products

People at Send

Sovara Browser

  • - A Health preset for NHS numbers, medical-record numbers, patient identifiers and date-of-birth markers.
  • - Local policy evaluation before Send, with email and phone redaction rules in the preset.
  • - Metadata-only connected audit events; the current Browser client does not upload prompt text or snippets.
Explore Sovara Browser →

Agents at the tool

Sovara Gateway

  • - Verified JWT identity and policy for configured agent-to-MCP tool calls.
  • - Per-tool identity rules, required roles and scopes, raw argument patterns, time windows and rate limits.
  • - Masked audit copies and optional JSON-response DLP inside your own Azure or self-hosted environment.
Explore Sovara Gateway →

One-page sector brief

Healthcare AI governance one-page brief

A concise overview of Sovara Browser controls for healthcare teams. It covers the Browser product specifically and is designed to share with security, compliance and operational stakeholders.

View the one-page brief →

PDF · 1 page

Consistent evidence, separate stores

Browser: review the decision, rule, site and managed user identifier without collecting the message body.

Gateway: review which agent called which configured MCP tool, the policy outcome and masked evidence.

Sovara provides controls and evidence; it does not by itself make an organisation compliant or certify a clinical workflow.

Start with one team and one workflow.

We will scope the surface, policy, evidence and success criteria before rollout. Browser and Gateway can be piloted together, but they remain separate workstreams and products.

Start a team pilot →