A clearer conversation starts here

See a clearer explanation of laboratory findings

Choose a fictional example to see how Atlas brings selected findings together and explains what may need follow-up. You can also change the fictional numbers and generate another example.

This demo checks selected findings and patterns from six laboratory values. It is not a complete laboratory review. Use fictional values only. Do not enter real results or use this demo for patient care.

01 / Explore a fictional example

Your starting point

Choose an example or enter fictional numbers, then select Show the example report.

Fictional example

LDL interpretation depends on how the result was obtained and whether that method is suitable. This demo uses fictional laboratory information to show how Atlas handles missing or conflicting information.

The general example represents a fasting, 58-year-old woman. The controls below change only the context for the LDL method check.

Explore the LDL method checks

Technical method and fictional assumptions

Original-2020 equation only. SYNTHETIC-NOT-A-LAB / SYNTHETIC-REVISION-1 are invented. Serum, January 1, 2026; test-only ranges 0–2000 mg/dL. These are not Northwell identities or verified laboratory evidence. This fictional profile requires age at least 18, fasting at least 8 hours, triglycerides no more than 800 mg/dL, and all other required conditions.

Fictional information about the LDL method Age used for the LDL method check (years) Fasting status used for the LDL method check Hours fasting used for the LDL method check

Type III is a lipid disorder considered by this method check. Interference means a factor that could affect the test result.

Type III lipid disorder (fictional information) Factors that may interfere with the test (fictional information)

Missing and conflicting information stays unresolved. Choosing an example does not verify a real laboratory result.

You may use the example values or enter your own fictional numbers. Do not enter real laboratory results or personal health information.

Choose an example, then show its report.

Your fictional values and selected context are sent to our demo service to create the report. Please use invented information only. Open Privacy and hosting details below to learn about processing, analytics, and retention limits.

Privacy and hosting details

The application does not intentionally save submissions or reports, set application cookies, or save report content in browser storage. Hosting providers process connection information and may retain operational or security records. You control where you save or print copies of your report.

Plausible measures page loads, valid execution starts, and completed reports. We send only the event name, our site identifier, and a fixed demo URL—no laboratory values, context, report content, campaign parameters, or referrers. This measurement adds no cookies or browser-storage identifiers.

This demo uses the ClearVeillance website’s Sites/Cloudflare routing service and the existing Render engine service. Fictional submissions and generated reports pass through Cloudflare between your browser and Render. The routing code does not log request bodies or reports and requests are not cached. Cloudflare may set security cookies and process connection and security information; the application does not create tracking cookies. Cloudflare/Sites operational-record retention and deletion periods have not been independently verified.

Usage events are sent directly from your browser to Plausible. Plausible processes technical connection data, including IP address and browser information, to produce usage statistics. Blocking analytics does not prevent use of this demo. The future-service selection is not measured. Plausible states that it does not store raw IP addresses or User-Agent strings; it derives daily visitor identifiers and stores event/session records for statistics. Those records are not a zero-retention system. The account’s analytics-history availability is governed by its subscription; provider operational-record deletion periods have not been independently verified.

Our inspected application logs contained no submitted values or report content. The current Hobby workspace retains dashboard application logs for seven days; this does not describe all provider records. Provider processing can include IP address, requested URL, browser information, timing and response status. Internal security-log, backup and deletion periods have not all been verified.

Campaign parameters are ignored by the application and are not sent to Atlas or included in report HTML, but the page URL may remain in browser history or provider records. Do not put personal information in a campaign link. Your browser, extensions and saved PDFs are outside the application’s storage controls. Use fictional information only.

DEVELOPMENTAL ALPHA ENGINE · Fictional demonstration only · Not validated for patient care, real-laboratory qualification or study execution.

02 / Read the example report

Your example report

Make the numbers more understandable.

Your example report will appear here.

For patients / Looking ahead

Explore proposed services

We’re exploring ways to help people understand laboratory reports and prepare for a clinical visit. These proposed services are not currently available.

Choose an option to read about the idea.

Which proposed service would you like to explore? VisitPrep Detailed Atlas report Both

Your choice stays on this page and is not saved or sent.

For professionals

Could this approach be useful in your work?

We’d welcome a conversation about a defined research question or a supervised pilot.

Talk with us about a research pilot →