SEALISON FOR HEALTHCARE · PATIENT-FACING AI

AI explained a diagnosis.
Can you prove what it said?

In healthcare, “almost correct” is not enough.

The problem is not just what the AI system computed. It is what the patient, member, or operator actually saw — and you may need to prove that later.

▲ Try it yourselfVerify a proof →

REALITY CHECK

When the patient disputes the AI.

PATIENT SAYS

Your AI told me I was eligible for this treatment.

YOUR SYSTEM SAYS

Our records show a different interpretation.

This is no longer a customer support issue. It’s a medico-legal question.

WHAT TEAMS RELY ON TODAY

None of these hold up in a medical dispute.

EHR system logs

Audit trail exists but entries remain editable by privileged users. No cryptographic guarantee.

Portal message history

Can be retroactively changed. No independent timestamp. No tamper-evidence.

Screenshots from patients

Not reliable evidence in medical litigation. Trivially modified. No cryptographic anchor.

When a patient or their lawyer asks for proof of what was shown — “we have logs” is the beginning of a problem, not an answer.

WITH SEALISON

Each interaction is sealed as a verifiable record.

01

Hash

The exact AI output is hashed with SHA-256 at the moment it's produced.

02

Seal

The hash is sealed in a signed, append-only chain. Ed25519 signatures. Any change is cryptographically detectable.

03

Keep

The original content stays with you. SEALISON does not store what your AI said — only the proof.

04

Verify

Later, you (or anyone) can reproduce the interaction and verify it matches. Public CLI verifier planned for stronger independent verification.

EU AI ACT · HEALTHCARE = HIGH RISK

Some healthcare AI use cases may fall under high-risk obligations, especially where patient-facing outputs, eligibility, triage, reimbursement, or medical-device-adjacent workflows are involved. Sealison provides cryptographic evidence that can support auditability and traceability reviews.

EU AI Act obligations for healthcare AI systems:

  • Annex IIISome healthcare AI use cases are explicitly addressed in EU AI Act Annex III, where applicable.
  • Article 12Article 12 requires high-risk AI systems to support automatic event logging and traceability appropriate to their intended purpose. Sealison can provide cryptographic evidence for selected AI outputs and events that need independent verification.
  • Article 14human oversight records, including what the human reviewer saw at decision time.

Sealison does not determine whether an AI system is high-risk and does not provide legal compliance certification. It provides cryptographic evidence that can support auditability and compliance demonstrations.

Not “screenshots in the chart.” Cryptographic evidence.

WHERE THIS APPLIES

Any patient-facing AI interaction.

Eligibility explanations

AI tells patients what treatments or benefits they qualify for. Later disputed by insurers or patients.

Coverage & reimbursement

AI explains what will or won’t be paid. Medico-legal consequences when disputed.

Clinical-adjacent recommendations

AI suggests next steps, specialist referrals, lifestyle changes. Must be auditable.

Patient-facing treatment options

AI presents options, explains risks. Patients challenge what they were told.

WHAT CHANGES

From “we believe” to “we can prove”.

BEFORE

We believe the AI said this.

EHR logs. Hopefully intact. Medico-legally contestable.

AFTER

We can prove the AI said this.

Cryptographic proof. Verifiable by any third party. Independently verifiable.

TRY IT NOW

See a real proof.

Generate one from scratch, or verify one we already published. Takes 30 seconds.

▲ Try it yourselfVerify a proof →See a live example →

Get in touch

Working with AI systems that talk to customers? We can show you how SEALISON fits in. 10 minutes. You test it yourself.

Request a pilot

Or email us directly at [email protected]

Logs are claims.
Proof is verifiable.

HomeVerifyRetailFintechHealthcareDocsAPIQuickstart
LegalPrivacyCookies
SealisonProof, not logs.