Every audience that touches a result — the ordering physician, the employer or facility that requested the test, and the patient it belongs to — gets its own portal view, scoped to exactly what that audience needs to see. There's no separate system to license, host, or keep in sync with the LIS.
| Portal | Primary Audience | Key Actions | Access Scope |
|---|---|---|---|
| Physician Portal | Ordering physicians & clinical staff | Place orders, view results, download reports | Own patients only |
| Employer/Facility Portal | Employers, nursing homes, trucking companies | Submit requisitions, track program status, run contract reports | Own testing program only |
| Patient Portal | Individual patients | View own results, download documents | Own records only |
Scoping each portal to a single audience keeps the platform aligned with HIPAA's minimum-necessary standard by design — a physician never sees another practice's patients, and an employer never sees another employer's results, without anyone having to configure that restriction manually.
Specimens are logged into the system the moment they're collected — not later at a desk. Barcode-driven intake, chain-of-custody capture, and automated pre-registration from client-submitted orders mean front-desk and collection staff spend their time on samples, not re-keying paperwork.
| Step | Who | System Action |
|---|---|---|
| 1. Collection | Phlebotomist / field staff | Barcode label printed and applied at point of collection |
| 2. Scan-in | Front-desk or lab receiving | Barcode scanned, custody record time-stamped automatically |
| 3. Verification | System | Requisition matched against portal-submitted or pre-registered order |
| 4. Routing | System | Sample routed to correct test queue or instrument worklist |
Accessioning supports both 1D and 2D barcode formats out of the box, so labs can match whatever label stock and scanner hardware they already use without a separate integration project.
Point-of-care analyzers and reference-lab instrumentation connect directly to the platform — results flow in both directions without a technician re-typing a single value. Rules-based autoverification releases routine, in-range results automatically and reserves manual review for genuine exceptions.
| Mode | Description | Best For |
|---|---|---|
| Direct bidirectional | Orders sent to the instrument, results returned automatically | High-volume analyzers with native interface support |
| Unidirectional | Results captured automatically; orders entered manually | Older or lower-cost instruments |
| Manual bulk entry | Spreadsheet-style bulk upload for non-interfaced instruments | Legacy equipment without an electronic interface |
Autoverification rule sets are configured and validated per method before go-live, and every automatic release is logged with the rule that triggered it — so an audit can trace exactly why a result went out without manual review.
Per-sample reports and grouped/contract-level reports live side by side in the same platform, backed by real-time dashboards for turnaround time, sample volume, and pending work across every client and testing program the lab runs.
| Report | Audience | Frequency |
|---|---|---|
| Per-sample result report | Ordering physician / patient | On completion |
| Contract summary report | Employer / facility account | Daily, weekly, or monthly |
| Turnaround-time dashboard | Lab management | Real-time |
| Regulatory/EDD export | State or program reporting recipient | Per program requirement |
Scheduled report delivery can be configured per client, so a large employer account receives its weekly contract summary automatically without lab staff having to remember to generate and send it.
DOT/SAMHSA-compliant custody workflows run from collection through final disposition, paired with HIPAA safeguards and the CLIA documentation an accreditation audit expects to see — all captured as part of normal workflow, not a parallel paperwork process.
| Standard | Applies To | Platform Support |
|---|---|---|
| DOT / SAMHSA CCF | Regulated drug testing | Digital custody-and-control form workflow |
| HIPAA | All patient-related data | Role-based access, encryption, audit logging |
| CLIA | Clinical testing accuracy & documentation | Method validation and QC documentation linkage |
Every custody transfer, signature, and access event is time-stamped and retained automatically, so producing an audit trail for a specific sample or case is a lookup, not a reconstruction project.
Non-negative drug-test results route automatically to the assigned MRO for review and verification. The outcome flows back into the record before a final report is ever released, so a non-negative result never reaches a client without the required clinical review.
| Stage | Trigger | Outcome |
|---|---|---|
| Result flagged | Non-negative screening or confirmation result | Case created in MRO queue |
| Review | MRO opens case | Clinical review of result and donor history |
| Verification | MRO completes review | Verified positive, negative, or cancelled outcome recorded |
| Release | Verification recorded | Final report released to employer/client |
Routing rules can be configured per client contract, so different employer programs can be assigned to different MROs without any change to how results are generated upstream.
Client-specific pricing tiers and grouped invoicing let one lab serve employers, trucking companies, and nursing homes side by side — each with account-level reporting matched to their own contract terms, without separate billing systems for each client type.
| Client Type | Typical Billing Model | Reporting Cadence |
|---|---|---|
| Employer (drug screening) | Per-test with volume tiers | Monthly summary |
| Trucking company | Contracted flat rate per driver program | Quarterly |
| Nursing home / facility | Per-panel with facility account billing | Weekly |
Volume discount tiers apply automatically once a client crosses a contracted threshold, so pricing stays accurate without a manual adjustment at invoicing time.
A field-capable mobile experience lets phlebotomists and couriers log collection events, custody transfers, and real-time location without returning to a desktop workstation — keeping the record current the moment something happens in the field.
| Capability | Field Role | Data Captured |
|---|---|---|
| Collection logging | Phlebotomist | Time, location, sample ID, signature |
| Custody transfer | Courier | Handoff time, location, recipient signature |
| Offline capture | Any field role | Queued locally, synced on reconnect |
Offline mode matters most for rural collection routes and facility visits with unreliable connectivity — entries queue locally and sync automatically the moment a signal is available again.
Results reach the right destination automatically — fax, email, or direct EHR integration — with critical-value and STAT alerting built in, so an urgent result never waits for someone to check a queue.
| Channel | Typical Use | Confirmation |
|---|---|---|
| Direct EHR interface | Hospital-affiliated ordering physicians | Interface acknowledgment logged |
| Secure email | Independent physicians, employers | Delivery & open tracking |
| Fax | Practices without electronic interfaces | Transmission confirmation logged |
Critical values follow a defined escalation timeline — if the primary contact isn't reached within the configured window, the alert automatically escalates to a backup contact.
Configurable QC rule enforcement and reagent/control lot tracking work alongside built-in proficiency-testing program management to keep every testing site audit-ready, without a separate spreadsheet-based QC log to maintain.
| Rule Type | Purpose | Example |
|---|---|---|
| Range check | Flag results outside an expected range | 1-2s / 1-3s Westgard rules |
| Trend check | Detect gradual drift across runs | 4-1s / 10x rules |
| Lot verification | Confirm control lot is current and valid | Expired-lot block at point of use |
Standard Westgard multi-rule sets are available out of the box, and can be tuned per method once a lab has enough historical QC data to justify adjusting default thresholds.
Recurring testing programs — a periodic employer drug-screening panel, for example — are configured once and generate their expected samples automatically on schedule, without staff manually re-creating the same order every cycle.
| Program Type | Cadence | Trigger |
|---|---|---|
| Employer drug-screening panel | Random / quarterly | Auto-generated sample pre-registration |
| DOT-regulated driver testing | Random pool selection | Scheduled selection event |
| Facility environmental panel | Monthly | Calendar-based reminder & sample generation |
Employer drug-screening cadences can combine a fixed schedule with a random-selection pool in the same program, matching how most DOT-regulated testing programs are actually structured.
Standard HL7/ASTM interfaces connect the platform to large reference laboratories and hospital LIS platforms, so referred-out testing and results stay part of one continuous, traceable record instead of a disconnected side process.
| Connection | Direction | Use Case |
|---|---|---|
| Reference lab interface | Bidirectional | Send-out testing and result return |
| Hospital LIS bridge | Bidirectional | Shared patient and result records across systems |
| EHR interface | Outbound results | Direct delivery to hospital-affiliated physicians |
Every new reference lab or hospital interface goes through a documented validation and test-message process before go-live, confirming that referred-out results reconcile correctly against the originating order.