NON-PRODUCTIONSYNTHETIC DATA ONLYNOT FOR PATIENT USE
EvidenceAssure

Identity and evidence assurance

Know who is in front of you. Keep nothing you don't need.

EvidenceAssure gives a clinic one calm journey for identity and parental-responsibility evidence: one secure link for each person, a human decision every time, a signed certificate at the end — and source documents deleted, with proof.

Take the guided tour
  • 1 secure link per person
  • 0 automated decisions
  • 100% synthetic data here

How it works

Four steps, one link, no loose ends

  1. Step 1

    One secure link

    Reception creates a case from the clinic's own reference. Each person receives a single expiring link, and sees only their own steps.

  2. Step 2

    Identity and evidence

    A specialist identity verifier checks who they are. Documents go straight into temporary encrypted storage. Extraction pre-fills the identity reviewer's fields.

  3. Step 3

    Human review

    Deterministic checks mark the case green, amber or red. A trained reviewer confirms, corrects, requests one more document or escalates.

  4. Step 4

    Signed certificate, evidence deleted

    A hashed, signed certificate states the outcome. Source evidence is deleted, and the deletion is independently verified.

What makes it safe

Safeguards you can see working

Each of these is observable in the guided tour, not a line in a brochure.

  • Human review is mandatory

    No certificate is issued without a named reviewer's decision and written rationale.

  • Decision support never decides

    Green, amber and red direct attention. A red case cannot be confirmed without a senior reviewer.

  • Adolescent confidentiality

    A young person's private note reaches reviewers only. It is never shown to the guardian, reception, or any connected system.

  • Per-object encrypted, temporary evidence

    Every document has its own key, lives outside backups, and exists only until the decision.

  • Verified deletion

    Deletion is checked independently. A failure is visible to an administrator until it is resolved.

  • Tamper-evident audit chain

    Every view, decision and deletion is hashed into a chain. Changing history breaks it, visibly.

  • Signed and hashed certificates

    Anyone holding a certificate can verify its digest and signature without learning anything about the person.

  • Role enforcement in the API

    The service withholds what a role may not see. The interface cannot leak what it never received.

  • Synthetic-only environments

    Outside production, real documents are blocked and every person, document and certificate is visibly fictional.

Architecture

Small surface, clear boundaries

The browser only ever talks to the web application. Evidence lives in its own encrypted store for as long as a decision takes, and no longer.

EvidenceAssure architectureParticipants and clinic staff use the web application, which talks only to the Core API. The Core API uses an identity provider, a temporary encrypted evidence store, and a certificate and audit service. A vendor-neutral integration API and signed webhooks connect to your clinic system, carrying outcomes only.EVIDENCEASSURE CORE · WORKS STANDALONE/v1Outcomes onlyParticipantsOne secure link eachPhone or computerClinic staffReception, reviewers,administrators, auditorWeb applicationSame-origin proxyStrict content policyNothing cachedCore APIRoles, tenant boundariesCase engine and rulesSupport, never decisionsIdentity providerDemonstration provider hereResult only: no imagesTemporary evidence storeEncrypted per objectDeleted, then verifiedCertificates and auditSigned, hashed PDFsTamper-evident hash chainIntegration API v1Vendor-neutral, versionedSigned webhooksYour clinic systemOpens cases, reads status,collects certificatesNo raw evidence, extracted text,rationale or confidential notesever cross the integration boundary.
Core is complete on its own. The integration API is optional and vendor-neutral: it carries case status and the signed certificate, never evidence.

Works standalone, connects to anything

Your clinic system stays in charge of the record

EvidenceAssure is complete on its own: staff can run every case from this application. When you are ready, a small, versioned, vendor-neutral API lets your clinic system open a case, follow its status and collect the signed certificate.

  • Bearer keys per connected system, idempotent writes
  • Signed webhooks: case.status_changed, certificate.ready
  • Never returns documents, images, extracted text, rationale or confidential notes
POST
/v1/integration/cases:openCreate or open the case for a clinic reference. Idempotent.
GET
/v1/integration/cases/{reference}Status and outcome in careful, defensible language.
GET
/v1/integration/certificates/{reference}Certificate metadata, hash and signature.
GET
/v1/integration/certificates/{reference}/downloadThe signed PDF.
POST
…/export-acknowledgementsTell Core where the certificate was filed.

Guided tour

Choose a scenario and step inside

Each scenario switches you to the right demo identity and opens a seeded case with prompts you can hide. Explore freely afterwards: the identity switcher is always at the top of the application.

Training Academy

Competence you can evidence

Role-specific exercises run in a private sandbox for each trainee. Actions are scored, feedback is immediate, and a supervisor signs off with an exportable completion record.

Reception learning path

  • Create the correct adult or family case
  • Use the clinic's reference, never a name
  • Respond to an expired link

Reviewer learning path

  • Confirm a consistent case with rationale
  • Spot a name mismatch, request proportionately
  • Recognise a safeguarding trigger

Administrator learning path

  • Respond to a failed evidence deletion
  • Verify rather than assume
  • Read audit evidence without raw data

Environments

The same build everywhere, with different keys

Every environment has its own database, storage, secrets and visible banner. Production data is never copied anywhere else.

Environment model
EnvironmentPurposeData and providersAudience
DevelopmentCoding and automated testsGenerated fixtures and local fakesDevelopers
ShowcaseGuided demonstration for decision-makersCurated synthetic cases, simulated identity providerInvited stakeholders
TrainingStaff practice and competence evidencePer-trainee synthetic cases, simulated messagesClinic staff and trainers
UATValidate a release candidateControlled synthetic test scriptsProduct owners and clinic testers
ProductionThe real operational serviceLive providers, approved clinic configurationAuthorised clinic users and patients