CLEAR (clearstd.com), built on the eProbatio platform, runs consumer diagnostics end to end — Ship Kit, Home Kit and clinic-visit ordering, CLEAR Pass membership, kit chain of custody, a lab verify-and-release gate with director co-sign, PASS certification reporting and shareable, identifier-redacted results.
CLEAR is a consumer diagnostics platform: a patient chooses a test panel online, has a collection kit shipped home or books a visit at a partner location, and reads the result in a secure portal once the laboratory has verified and released it. Behind the consumer brand is eProbatio, the platform that connects patients and laboratories and runs the chain from checkout to result. The platform progress record describes the consolidation that produced it — marketing site, patient portal and home-kit funnel, formerly three properties with three logins, now one domain with one account, one staff console and one admin panel, operated under a business associate agreement (BAA).
Three consumer paths are documented and built. Home Kit is a four-step checkout — choose kit, shipping, payment, done — that creates the order and its shipment with no appointment; Ship Kit ships the kit and adds a partner-site blood-draw appointment; a clinic panel books a location, date and time; CLEAR Pass is a monthly membership checked out as a subscription, with a Pass and a Pass+ tier and a 'manage plan' path for existing members. From there the order is a single record a patient can follow: a shipped kit activated by barcode, a chain-of-custody timeline from shipment through receipt at the lab, and a result page with analytes, reference ranges and flags.
For laboratories and programs it is an engine with explicit gates. Manually entered results start as drafts, must be verified and released by different people, hold on critical values, and wait for a Lab Director co-sign when abnormal; direct-to-consumer (DTC) panels are authorized by physician-signed standing-order protocols stamped on each released result. One per-panel switch decides whether a result is reported to the PASS clearance database and carries the certified-partner mark, and one redaction library decides how much of the patient's identity each surface — full PDF, no-PHI summary, QR share, PASS, analytics — is allowed to show. Results do not constitute a medical diagnosis; telehealth and treatment routing exist for results that need a conversation.
Needs · To pick a test, know the price and turnaround up front, collect at home or at a nearby location, and read the result without a phone call — or share it when asked to.
Gets · Online ordering for kits and clinic visits, a shipped kit activated by barcode with its custody timeline, results with analytes, reference ranges and flags once released, a full or no-PHI document, and a revocable QR share link.
Needs · Recurring testing on a membership, a clearance that productions and agencies can trust, and a way to prove status without handing over the full report.
Gets · Pass or Pass+ subscription management, clearance status and a PASS report on the dashboard, automatic reporting of qualifying results to the PASS database, a certified-partner mark on the PDF, and one-time or continuous sharing with agencies.
Needs · To see current clearances for the performers who work with the agency, manage who at the agency can view them, and never hold more than the member chose to share.
Gets · An organization with admin and standard members, invitations with accept or decline, results shared org-wide by members, and identifier-minimized views on every shared surface.
Needs · To receive and accession kits, enter or import results, keep a second person between entry and release, hold critical values, and sign off on abnormal results as the director of record.
Gets · The lab interface for receive, accession and QC; result entry, XLSX import and API sync; the draft → verified → released gate that refuses the same person twice; a critical-value hold; the Lab Director co-sign; amend and discrepancy handling with history.
Needs · To order panels for a wellness or telehealth population under a signed protocol and receive results without building an integration from scratch.
Gets · A healthcare-provider account with API keys and API documents, physician-signed standing-order protocols that authorize DTC panels, test-order creation, and result delivery to the ordering provider.
Needs · To find a patient's order, kit, appointment or result in one place, fix what is wrong inline, answer the ticket, and know that the PASS push actually went through.
Gets · The admin panel's orders with inline editing, shipments, billing, tickets, communications, alerts and incidents; the staff console's kit and result queues; a PASS-failures tab with retry; and an audit log on every record.
| Area | Today | With Lab Services |
|---|---|---|
| Ordering | Three separate sites — marketing, portal, kit funnel — and order buttons that ended at an account page. | One domain, one account: Ship Kit, Home Kit, clinic visit or CLEAR Pass from a single checkout, with credits or a covered tier applied automatically. |
| Specimen tracking | A kit is mailed and everyone hopes; nobody can say where it is between the mailbox and the bench. | UPS label and tracking on the order, barcode activation, and custody events with actor and time that the patient and staff both see. |
| Result release | One person types a result and it goes out; a typo reaches the patient. | Draft results must be verified and released by a different person; critical values wait for acknowledgement; abnormal results wait for the Lab Director. |
| PASS reporting | Someone remembers which panels are industry panels and keys the result into a second system. | One per-panel switch: qualifying results are reported at save time, the PDF mark follows the same switch, and failed pushes queue for retry. |
| Proving a result | A screenshot of a PDF that anyone could edit, or an emailed document with the full record attached. | A time-boxed share token that resolves to an initials-only clearance card with a CLIA banner, a no-PHI summary document, and agency sharing the member controls. |
| Partner integration | Clinics order by email and chase results by phone. | Provider accounts with API keys and documents, orders placed by API, and results delivered back to the ordering provider. |
10 modules, each describing what is built today.
Test items and panels with pricing, channel and availability, plus the two flags and the signed protocols that decide what a result may become.
The canonical, auth-gated order flow documented in the consumer order processing record, reusing one proven order endpoint.
A kit is a tracked object from the moment it ships until the lab receives it, and every step is an event a patient and staff can both read.
Clinic visits scheduled from the same account as kits, against real location hours and slot capacity.
The laboratory's working surface: receive, accession, QC and result entry.
No manually entered result reaches a patient on one person's say-so.
How a CLEAR result becomes a clearance in the PASS database, as described in the PASS reporting guide and relationship map.
One redaction library with named profiles decides who is shown on each surface; what analytes print is a separate decision.
One account for everything a patient does after checkout, documented page by page in the UAT guide.
Two operations surfaces — a staff console and a full admin panel — plus accounts and keys for organizations that order on behalf of patients.
Before the rebuild there was no working order process on the consumer site. Marketing calls-to-action dead-ended at an account or pricing page, the order form posted to an endpoint that did not exist, and the only flow that actually completed an order lived in a legacy funnel outside the design system. The consumer order processing record documents the replacement: one canonical, sign-in-gated checkout that reuses the one proven order endpoint for every kit product.
A kit checkout is four steps — choose kit, shipping, payment, done. The panel list is filtered to kit-channel products, the shipping address is prefilled from the profile and saved back, and the card payment is confirmed before the order and its shipment are created, so a failed charge never leaves a half-made order. Home Kit is self-collection with no appointment; Ship Kit ships the kit and books a partner-site blood draw; a marketing page can deep-link a panel to skip selection.
CLEAR Pass is checked out as a subscription rather than an order. The page first asks the platform whether membership is configured and whether the visitor is already a member — an existing member is routed to manage their plan, and when the subscription price is not configured the page says so plainly instead of erroring. Panels covered by the member's tier carry no per-order charge, and the Pass+ tier extends coverage to additional collection sites.
A manually entered result moves through four explicit states — draft, pending verification, verified, released — and only a released result can reach a patient. The verify, release and sign-off steps each refuse the person who entered the result: the platform answers with a refusal that says a different person must act, not with a silent success. That second pair of eyes is a property of the system, not a policy memo.
Two holds sit on top of the gate. A result containing a critical value cannot be released until someone acknowledges it, and the acknowledging user and time are stored on the result; re-entering the result clears any prior acknowledgement so a changed value is looked at again. A positive or abnormal result marked for director review waits for a co-sign by the Lab Director role — until the director signs, the result is not deliverable anywhere.
The same deliverability rule is applied by the patient portal, the result document and the public QR share, so the surfaces cannot disagree about whether a result is out. A result flagged discrepant is blocked from all of them until resolved, and a released result is corrected by amendment with a reason, with prior versions kept. Results do not constitute a medical diagnosis; results that need a conversation route to a consult.
PASS — the performer-industry clearance database — is wired to the catalog through one per-panel switch, set explicitly and never guessed from a panel's name. A PASS-enabled panel's completed results are reported to the clearance database and its documents carry the certified-partner mark; home-kit, general-public and LGBTQ+ screening panels are never reported. New panels default to off, so a panel cannot be reported by accident, and the same switch feeds the reporting push, the PDF mark and the clearance footnotes — three surfaces that therefore cannot disagree.
Reporting fires when staff save a completed result — no schedule, no separate button. A result becomes a clearance when the panel is PASS-enabled, the result is completed and within thirty days, and every PASS-required item is negative; the clearance expires thirty days after the result date. The per-item required flag handles the edge case the guides call out: a positive on an item PASS does not require prints a supplemental-screening footnote on the report instead of reading as a failed clearance.
The push is fire-and-forget — it never blocks or fails the save. A failed push lands in a staff-visible failures queue where each entry can be retried, an administrator can test the connection, and editing a result re-reports it. The identifier returned by the clearance database is stored on the report record, so every clearance is traceable from the CLEAR side.
The redaction design note starts from an insight: two different questions were being conflated. Who is this patient — name, full date of birth, medical record number — is one axis; which analytes print on a given document is another. Hiding an analyte never de-identifies anyone, and stripping identifiers never hides a finding. CLEAR separates them: per-item flags decide what prints, and a single redaction library decides who is shown.
That library exposes one function and five named profiles, one per surface. FULL — the full report and the patient's own portal — shows name, full date of birth, record and accession numbers. NO_PHI, the shareable summary, shows a first name or stage name and a birth year only. SHARE, the public QR card, shows initials. PASS carries no patient identifiers beyond what the clearance database itself requires, and ANALYTICS is stricter still — it strips identifiers and the health data.
Because every surface calls the same function, 'no-PHI' — no protected health information — means one thing across the platform instead of three. A patient can hand an agency the summary or the QR card knowing exactly which identifiers travel with it, and the analyte flags feed only the analyte filter — they can never quietly change who a document identifies.
The remediation record is candid about the before-state: the collection workflow logged nothing. Steps lived in the browser as local state, so once a visit ended there was no record of who collected what, when, or with which barcode. The chain-of-custody phase replaced that with a custody event store — every step is persisted with the acting user, a timestamp and optional photo or barcode evidence, alongside required-test checks drawn from the order itself.
The steps are a fixed, seven-word vocabulary: pre-visit, arrival, collection, labeling, completion, shipped, received. For a mailed kit the record starts before the patient does — the shipment and its tracking number are created with the order, the patient activates the kit by barcode, marks collection, and the prepaid return label carries it back; tracking webhooks update the shipment as it moves, and the lab's receive step records the accession and QC status.
Because custody is rows in a database rather than recollection, it is queryable after the fact. The same events feed the staff kit chain, the admin order timeline and the patient's own kit page, so all three audiences read one shared record — and a question like 'where was this specimen between the mailbox and the bench' is answered from the stored timeline, not from anyone's memory.
The patient picks a panel, sees price and turnaround and pays — one-time by card, with wallet credits, or covered by a CLEAR Pass tier.
A kit ships with a tracked label and is activated by barcode — Ship Kit adds a partner-site blood draw — or the patient books a clinic visit; the custody record starts at shipment or arrival.
The laboratory marks the kit received, records the accession and QC status, and enters or imports the results.
A different person verifies and releases; critical values are held until acknowledged and abnormal results wait for the Lab Director's co-sign; the authorizing standing order is stamped on the result.
If the panel is PASS-enabled and the completed result qualifies, it is reported automatically and the clearance is recorded with its expiry; failures queue for retry.
The patient reads analytes in the portal, downloads the full or no-PHI document, shares a QR card, or shares with an agency; reactive results route to a consult request.
Every promise on this page maps to something the software actually enforces.
Home Kit is a four-step checkout — choose kit, shipping, payment, done — with no appointment. Ship Kit ships the kit for self-collected samples and books a partner-site blood draw in the same flow. CLEAR Pass is a monthly membership checked out as a subscription, with Pass and Pass+ tiers. Clinic panels book a location and time in the same checkout.
The laboratory. Manually entered results pass a verify-and-release gate that refuses the same person at both steps; critical values are held until acknowledged and abnormal results require a Lab Director co-sign. Results do not constitute a medical diagnosis; a result that needs a conversation routes to a telehealth consult or treatment.
PASS is the performer-industry clearance database. A result is reported only when its panel has the PASS switch on, the result is completed and within 30 days, and every required item is negative; the clearance expires 30 days after the result date. Home-kit and general panels are never reported.
Identifier redaction, not hiding analytes. A single redaction library with named profiles decides who is shown: the full document carries name, date of birth and MRN; the no-PHI summary carries a first name or stage name and birth year; the QR card carries initials only; analytics carry nothing.
By physician-signed standing-order protocols — versioned documents managed in the admin that authorize a set of DTC panels. The active protocol is stamped on each released result, so ordering authority is traceable without a per-order signature.
Yes, when the member shares them. Performers share with another performer or with an agency, one-time or continuously; agencies have admin and standard members who view results shared org-wide. Ordering organizations get provider accounts with API keys and receive results for the patients they ordered for.
Only page views are tracked, and every event passes a guard that removes name, email, date of birth, phone, address, analyte, result and diagnosis keys before it leaves the browser.
Yes, with a record. A released result is amended with a reason and the prior versions are kept, so the history of what the patient saw is never overwritten. A result flagged discrepant is blocked from every delivery surface — portal, document and QR share — until the discrepancy is resolved.
Nothing is lost and the result is unaffected. The push is fire-and-forget, so a network failure never blocks or delays the save; the failed push lands in a staff-visible failures queue where each entry can be retried individually, and an administrator can test the PASS connection before retrying. Editing a result re-reports it.
We walk through it with your data and your team — not a canned demo.
Program and billing eligibility are determined by each practice and its payers. Results and alerts do not constitute a medical diagnosis. Third-party names are trademarks of their respective owners and do not imply endorsement.
