Appearance
Reference Laboratory Overview
The Reference Laboratory module supports B2B relationships where your lab processes specimens for client laboratories — or acts as a send-out hub for specialized testing. Manage client accounts, inbound orders, result delivery, and consolidated invoicing from /reference-lab.
Business models
mermaid
flowchart TB
subgraph Model A["You as reference lab"]
CL[Client lab] --> YOU[Your processing]
YOU --> RES[Results to client]
YOU --> INV[B2B invoice to client]
end
subgraph Model B["You send outsource"]
YOU2[Your lab] --> REF[Reference partner]
REF --> RES2[Results back]
end| Model | EaseLab focus |
|---|---|
| Inbound reference | Clients & orders, B2B invoicing |
| Outbound outsource | Outsource tests report |
This documentation emphasizes inbound reference workflows.
Module access
| Route | Screen |
|---|---|
/reference-lab | Dashboard and client list |
| Client detail | Orders and result status |
| Invoicing | Period billing to clients |
Feature may be plan-gated — verify subscription.
Key entities
| Entity | Description |
|---|---|
| Client lab | B2B customer organization |
| Order | Batch of specimens from client |
| Accession | Barcode linked to client reference ID |
| Result package | Verified results returned to client |
| B2B invoice | Periodic charges for processed tests |
Workflow summary
mermaid
flowchart LR
O[Client order received] --> ACC[Accession samples]
ACC --> PROC[Process + verify]
PROC --> DEL[Deliver results]
DEL --> BILL[Generate B2B invoice]
BILL --> PAY[Client payment]- Register or select client lab.
- Create order with client manifest (barcodes, tests).
- Accession into standard sample workflow.
- Process and verify results.
- Publish results to client portal or export.
- Bill per contract on invoicing schedule.
Client communication
| Channel | Use |
|---|---|
| Portal login | Client views order status |
| Email / API | Automated result packages |
| PDF manifest | Shipping paperwork |
| HL7 / JSON | Integration for large clients |
Align transport security with client IT requirements.
Pricing models
| Model | Configuration |
|---|---|
| Per-test list | Client-specific rate list |
| Volume tiers | Monthly brackets |
| Panel pricing | Profile bundles |
| Rush surcharge | TAT-based fees |
Map to dedicated rate lists or manual invoice lines.
Permissions
Reference lab operations typically require:
| Module | Need |
|---|---|
catalog.view | Test mapping |
samples.* | Accession |
results_entry.* | Processing |
invoices.* | B2B billing |
| Reference lab feature flag | Plan |
Define a Reference Lab Technician role without patient retail invoice rights if workflows must separate.
Separate client barcodes
Prefix client barcodes (CLIENT-A-####) to avoid collision with walk-in patients.
Reporting
| Report | Value |
|---|---|
| Outsource tests | Send-out tracking |
| Test performance | Volume by client test |
| Financial summary | B2B revenue segment |
Tag invoices with client reference for clean exports.
Quality and compliance
| Control | Practice |
|---|---|
| Chain of custody | Log specimen receipt time |
| Turnaround SLA | Per contract in CRM notes |
| Critical values | Callback to client MD, not patient |
| Proficiency | Retain QC records per accreditation |
Read-only mode
B2B order intake may be blocked in read-only mode. Existing client result retrieval should continue for relationship continuity — confirm deployment behavior.