▶ About

Built for teams who can’t bring a translator for every person.

▶ The mission

The intended field workflow lets a health worker download a reviewed language pack and screening module while there is still Wi-Fi, then conduct the encounter offline on the phone. The current device-test build supports an English conversation and review path; two-way English-to-Fijian translation remains under human verification.

The problem it solves is a scaling one. A team can grow its health workers faster than it can grow qualified interpreters, and interpreter headcount doesn’t scale with team size the way a downloaded language pack could. Viridis is being developed to reduce the “one interpreter per person” bottleneck while keeping clinician review and safe manual fallbacks in the workflow.

It’s scoped on purpose, not stretched thin across everything at once: the current synthetic preview focuses on a tuberculosis workflow in English. Standard Fijian is a planned reviewed pack, not a current clinical capability.

▶ The boundary

Where the boundary sits

Viridis is a communication and record-keeping aid, not a diagnostic tool.

  • Viridis never diagnoses, recommends treatment, or gives clinical guidance.
  • The Review Portal never receives patient data. Consented device-test encounter details stay encrypted on the phone unless an authorised user exports them.

Read the full safety boundary ↓

▶ Safety

Where Viridis draws the line.

Viridis is built to back up a health worker in the field, not to replace clinical judgment. These are the boundaries it doesn’t cross.

▶ In practice

What Viridis will never do

  • Viridis never diagnoses, recommends treatment, or gives clinical guidance. It's a communication and screening aid, not a diagnostic tool.
  • No language content may be labelled verified or released for clinical use without qualified human review. Current preview content remains synthetic and unapproved.
  • Viridis doesn't create or become the official record of a clinical encounter.
  • Patient details recorded with consent remain in the encrypted device database and are never sent to this website or Review Portal.

These boundaries cover the device workflow. Reviewer and staff personal data in this separate portal is covered under Privacy below.

Development status

Viridis is under active development and has not been clinically validated. Nothing shown here should be treated as verified or production-ready.

▶ Privacy

What we collect, and why.

This website and Review Portal do not receive patient records. The device-test app’s consented local encounter data is a separate system described in the safety boundary. This section covers the personal data belonging to people who review content for this project: names, email addresses, professional context, written comments, and voice recordings.

▶ In detail

What we collect and why

Account information
Name, email, and organisation, used to invite you, verify who submitted a review, and let project staff contact you about your work.
Review responses
Ratings, corrections, and comments, the content you were invited to provide, retained as review evidence.
Voice recordings
Only when a review explicitly requests one, and only after a separate consent step, distinct from this general policy.
Administrative audit records
A bounded log of account and content actions, used for accountability. It never contains passwords, session tokens, full response text, or audio file contents.

▶ The specifics

Voice recordings

A recording is only ever requested with a separate, explicit consent step, shown before recording starts, that explains why it's needed and how it's handled. A recording can be accessed only by project staff carrying out that specific review, and is never made public. It can inform corrections to the reviewed language content itself, never a patient-facing clinical decision. Retention periods are still being finalised before this is used with real reviewer content; once a response containing a recording is submitted, it becomes part of the project's review evidence, and a deletion request goes through a project administrator rather than an automatic self-service action.

Who can access it

Project administrators and the staff carrying out the review a submission belongs to. A reviewer can only see their own submissions, never anyone else's, and nothing here is ever made public. Viridis includes no advertising, behavioural tracking, or third-party analytics.

Your requests

To request access to, correction of, or deletion of your personal data, contact a project administrator through your existing project channel, or use the contact details below.

▶ Get in touch

Contact

A dedicated contact address will be published here once one is confirmed.