How it works
One loop, from source result to released report
Every visible number comes from a versioned fixture and passes through a clinician before a member sees an interpretation.
Import
A registered synthetic fixture is imported. Only fixtures whose checksum is on the demo manifest are accepted; there is no arbitrary upload.
Validated observations
Each result is checked for a parseable decimal, a known unit, and a source-supplied reference. Problems are recorded, never guessed around.
Deterministic draft
Software prepares a draft from those observations: exact values, neutral changes, and the source laboratory's own intervals or decision limits.
Clinician review
A fictional demo clinician reads the draft next to the source observations, edits it, or requests a correction.
Exact-version approval
Approval attests one exact content hash. Any later edit invalidates that approval.
PDF verification
A real PDF is rendered from the same HTML the member will see; its bytes, page count, and text are verified and hashed.
Release
Release is a separate, explicit action and requires a verified PDF. Nothing before this point is visible to the member.
Member HTML and PDF
The member reads the released version as accessible HTML and can download the verified PDF through an authenticated route.
Corrections create a new version
A released report is never edited in place. A corrected fixture starts a new version with a visible reason and lineage; the prior one is kept as history.
Why there is no health score
Earlier concepts showed an overall “optimization” number. It was removed: no validated scoring model was supplied, and visual appeal cannot justify an implied health assessment. The demo shows workflow completion and data-coverage counts instead, both labeled as what they are. A reference interval, a clinical target, and an overall assessment are different things, and this software does not blur them.
See the sample report or read what the reviewing clinician sees.