GLOL

Public-safe clinical mock flow

Private audit patterns become synthetic teaching cases.

A local raw-genotype audit can identify the kinds of questions worth teaching. Public pages should not expose the private rows. This mock flow translates private review patterns into synthetic observations, public marker families, and explicit clinical boundaries.

Private-to-public transformation

The public case is not the private genotype.

Private

Local audit

A raw MyHeritage-style CSV is reviewed locally for format, bucket distribution, and candidate teaching patterns.

Transform

Change the specimen

Personal calls are replaced with synthetic observations and public marker families before any website material is written.

Public

Mock clinical flow

The website shows how a professional review proceeds, while keeping diagnosis, identity, and personal genotype data out of scope.

Audit-informed mix

The mock set mirrors review pressure, not personal results.

Clinical reasoning flow

Every mock case follows the same interpretation discipline.

01

Observe

Record the source row as an assay observation, including marker, coordinate, and genotype representation.

02

Normalize

Convert only when build, strand, and reference/alternate orientation can be defended.

03

Route

Select the correct evidence pathway: clinical assertion, PGx guideline, trait literature, or molecular prediction.

04

Bound

State what the data can support, what remains unresolved, and what requires clinical confirmation.

Synthetic examples

Where to look, what it could mean, and what not to conclude.

Boundary of the mock flow

The page is built from private workflow needs, not public personal results. The examples are educational, synthetic, and deliberately unsuitable for diagnosis or treatment decisions.