Tynixa Workspace
Case intakeDraft-onlyHuman review required

Start a case or run a safe report check

Use synthetic/de-identified content to run readiness, PHI precheck, eligibility, and review package creation. Doctor and patient roles receive safe explanations and questions, not final diagnosis.

Back to DashboardOpen Review Package Demo

Guided intake — what to do next

Step 1: Choose a synthetic or de-identified file below. Selecting a file does not upload it to the server.

  1. Choose a file in the File input below. Verify that the filename and preview appear.
  2. Run checks using Classify file, PHI precheck, Eligibility and Run check. The result will appear below with feedback.
  3. Choose your next path: Create review-ready package for a safe demo, or for a governed upload sign in to an authorized workspace, confirm the appropriate attestation, then use the separate PDF or VCF upload button.
  4. Continue review using the Case Detail / Review Package link shown after a successful server operation. Human review is always required before clinical release.

Ready to select a file. Nothing has been uploaded to the server yet.

Case details

1. Enter or upload2. Run checks3. Create package
Run precheck before creating a review package.

Upload PDF / VCF

Select a local PDF, VCF, TXT, JSON, or CSV. The demo reads safe preview text in-browser where possible and sends synthetic/de-identified precheck metadata to existing APIs.

File
No file selected
Type
—
Size
—

After selecting a file, run check. Do not upload PHI in this demo.

Governed PDF report intake · P197

Upload a synthetic or de-identified PDF report into the existing governed case/vault path. Embedded PDF text is extracted and passed to the existing P197 report interpretation engine. OCR is not claimed; image-only PDFs remain stored but require a separate extraction/review step.

Choose a .pdf file above, then sign in with an authorized workspace account.

Saved reference-VCF case · governed upload

This is a separate, authenticated nonclinical reference workflow within the existing intake page. Use only an explicitly public reference or fully invented synthetic VCF containing eight site-only columns. No sample IDs, genotype columns, personal VCF, reports or phenotype notes. Your workspace session determines access; selecting a role above does not grant access.

This public-reference declaration is not independently verified. Clinical upload remains unavailable through this workflow.

Choose a .vcf file above, then sign in with a workspace-authorized account.

G3 · Public source evidence for the saved reference case

Only a saved public or invented synthetic VCF with up to two single-base sites is eligible for this limited source check. NCBI RefSeq verifies the genomic reference allele; exact matching NCBI ClinVar records, if any, are external source claims and NOT a diagnosis, ACMG classification, gene assignment or clinical sign-off.

This evidence view reuses your signed-in authorized workspace and existing saved case. It does not transfer patient data or use an AI agent. An absent ClinVar exact match is reported as absent; no result will be invented.

Open an existing saved G2 case to inspect the G3 public source ledger.

G3 · Source-bound five-agent execution audit

This view displays execution metadata for the five real synthetic-only agent roles already approved for this saved case. Unreviewed model text is withheld; it is NOT scientific source evidence, ACMG classification, diagnosis, clinical recommendation, or human sign-off.

A signed-in workspace account and existing synthetic case are required.

Operational journey status

This is a projection of existing intake/upload/review states. It does not create a second workflow state store.

Current state

Not started

Start with PHI precheck or a governed upload.

Next action

Start intake

No corrective action required yet.

Human review remains required. Qualified signoff and clinical release are not inferred from this status.

Result

Run check to see readiness, PHI status, missing evidence, safety boundaries, and next actions.

Advanced technical audit JSON
No technical result yet.

Case intake and readiness check

What this page does

Upload or paste synthetic/de-identified genomic input and check whether it is ready for review.

Who should use it

Lab users and demo users preparing a VCF, PDF-like summary, text report, or case description for review.

What you get

Input type classification, PHI precheck, readiness score, missing fields, and recommended next step.

What is not allowed

No final diagnosis. Do not submit PHI or patient identifiers in the demo. Intake does not finalize diagnosis or classification.

Example in practice

A synthetic BRCA1 VCF passes PHI precheck, receives a readiness score, and moves to review package creation.

Next step

If eligible, create a review-ready package or send the case to reviewer workflow.

Case intake value moments

The intake workflow turns raw synthetic/de-identified input into a clear readiness decision before review-package creation.

Readiness Score

The user sees whether the case has enough structure to continue.

Basis: readiness-score API

PHI Safety Check

The demo confirms that the input is synthetic/de-identified before processing.

Basis: PHI precheck API

Missing Inputs

Missing fields and recommended next steps are shown before package generation.

Basis: eligibility and missing-input checks

Safety: These value moments are event-based and review-context-only. They do not claim autonomous diagnosis, final ACMG classification, treatment decisions, clinical performance approval, regulatory approval, unsupervised clinical automation, same-visit final clinical decisions, or clinical release without qualified human sign-off.