Labs arrive as scans
Faxed, image-only PDFs with a different layout from every lab. Nothing searchable, nothing comparable, nothing that trends.
For longevity, functional & concierge practices
Every lab, every wearable, every protocol — one panel.
Health data arrives broken: scanned PDFs, half a dozen device apps, and protocols written down in prose. OnePanel pulls it into a single longitudinal record — so your practice sees the whole picture, and your patients see something they actually want to open.
Patient access is by invitation from your practice.
Comprehensive panel
- Testosterone, total742ng/dL264–916+64Optimal
- ApoB118mg/dL< 90+11Out of range
- hs-CRP2.8mg/L< 1.0+1.9Out of range
- Ferritin412ng/mL30–400+38Borderline
- HbA1c5.4%4.0–5.6−0.1In range
Extracted from a scanned PDF · every value links back to its source page
The problem
The data exists. It just doesn't sit anywhere useful.
Nothing here is a tooling gap. It is four separate systems that were never designed to meet.
Wearables stay in their own apps
Continuous glucose in one app, sleep in another, body composition on a scale that talks to neither.
Protocols live in a chart note
Peptides, HRT, IV and ozone get written down in prose, so nobody can see what actually moved after a patient started.
Every visit opens with data entry
The most valuable hour of the week begins with twenty minutes of hunting through portals.
What it unifies
Four streams, one timeline.
Each arrives its own way. All of them end up on the same axis, which is the entire point.
Labs
Upload a PDF and the panel comes back read, categorised and ready to review. Or enter results by hand. Or let the practice add them from HQ. Every value stays editable, with a full history of who changed what.
Wearables & devices
Sleep, recovery, heart-rate variability, continuous glucose, body composition — pulled in on a schedule and lined up against the bloodwork on the same timeline.
Nutrition & training
What someone eats and how they train is context for every marker on the panel. Logged simply, and shown beside the results rather than in a separate app.
Protocols
Peptides, hormone therapy, IV, ozone and anything else the practice runs — recorded as dated courses, not prose. So a protocol start date can be drawn straight onto the chart.
For patients
The first one they actually open.
Most platforms in this category are built for the clinician and hand the patient a portal as an afterthought. That is backwards: the person with the most at stake in the data is the one least likely to log in twice.
The patient side of OnePanel is deliberately the simplest thing we build. One screen, plain language, and an answer to the only question anyone opens a lab result to ask.
- One screen that answers "am I okay?" before it answers anything else.
- Every marker in plain language, with what changed since last time.
- Optimal ranges, not just the lab's "not sick" range.
- A direct line to the practice, in the same place as the results.
For practices · hq.onepanel.health
A practitioner HQ, not a second inbox.
Invite patients, add results however you actually work, review every extraction, and answer questions where they were asked.
Add results any way you work
Upload a scanned panel for a patient, key in a single marker, or correct an extraction. All three land in the same record.
Nothing publishes unreviewed
Extracted values arrive as pending and stay off the patient's charts until a human confirms them, however confident the model was.
See what your protocols did
Protocol courses are drawn onto the trend, so the question "did this work" has a picture instead of an anecdote.
Answer in context
Patient messages arrive attached to the result that prompted them, so there is no hunting for what they mean.
Security & data
Built for clinical data from the first commit.
OnePanel is not HIPAA-certified today and does not claim to be. What it is, is architected so that becoming compliant is a hosting decision rather than a rewrite — which is the part that is expensive to add later.
One data layer, on purpose
Every read and write of health data goes through a single interface rather than pages touching the database. That is what lets the store move to HIPAA-eligible hosting under a BAA without rewriting the product.
Separate identities
Patients and practice staff sign in through structurally separate systems. A staff session can never resolve to a patient session, or the reverse.
An audit log you cannot skip
The log is append-only and written inside the data layer itself, so every access is recorded whether or not the calling code remembered to.
No PHI where it leaks
No health values in logs, in URLs, or in query strings. Results are identified by record, never by value.
Next step
See it against your own panels.
The fastest way to judge OnePanel is to hand it a lab report you already have and see what comes back. Bring a scanned one — those are the hard case, and the one everything else falls over on.