EKLIS.CLIENT REPORT
03 · WORKFLOW

The core loop the product must own

From the physician's order to a paid claim: eight stages, one immutable audit trail, and a verification engine that releases routine work automatically.

01 02 03 04 05 06 07 08 Order Collect Accession Route Analyze Verify Report Bill portal · HL7 · DTC eligibility check phlebotomy ZPL barcode labels scan → unique ID 2-identifier match worklists · aliquot send-outs ASTM / HL7 instrument run auto-verify 80–90% delta · QC gate PDF · portal · ORU fax · corrected ver. CPT claim → clearing- house · denials
The requisition-to-reimbursement pipeline. Every stage writes to the immutable audit log; the highlighted Verify stage is where auto-verification releases 80–90% of routine chemistry untouched — the single biggest ROI lever an LIS has (CLSI AUTO10/AUTO15).

Stage by stage

StageWhat happensBuilt-in safeguards
1 · OrderPortal, manual, HL7, or DTC order entry against the LOINC-coded test compendiumEligibility + medical-necessity checks at order time; STAT priority captured
2 · CollectPhlebotomy with barcode label printing (ZPL / PDF)Two-identifier patient verification at collection
3 · AccessionScan to check in; unique accession ID assignedOrder/specimen match verified; < 5 s per specimen; mismatch warnings are blocking
4 · RouteDepartment / instrument worklists, aliquoting, send-outsSTAT elevation everywhere; bounded reflex chains
5 · AnalyzeInstrument runs file results via ASTM / HL7Durable message log; results file only into open orders
6 · VerifyAuto-verification rules or technologist reviewQC gating, range & delta checks, instrument flags; rule-set version stamped on every auto-release
7 · ReportPDF (cumulative / corrected), portal, HL7 results out, faxReleased results immutable; corrections issue a labeled new version
8 · BillCPT-coded billable events to the clearinghouse adapterDenial tracking and analytics close the loop

Specimen lifecycle

ordered collected in-transit received accessioned in-process preliminary final rejected reason logged · client notified hemolyzed · QNS · mislabeled… corrected new version · original retained stored retention ≥ 2 yr (CLIA) disposed
Specimen lifecycle state machine, enforced server-side. Out-of-order transitions are rejected. A final result is immutable — corrections create a linked new version and both stay visible (CLIA §493.1291). Rejection is a first-class state with reason codes and client notification, not a deletion.

Verification & quality machinery

result received (ASTM/HL7) QC in control? Westgard rules no Hold run — QC worklist corrective action documented yes Flags clean? hemolysis · icterus · lipemia no yes In auto-verify range? per-analyte limits no yes Technologist worklist manual review · repeat · dilute reflex add-on per rule chain release or reject with reason every action attributed + audited Delta check pass? vs. prior result no — possible mislabel yes AUTO-RELEASE report + portal + ORU · rule-set version stamped critical value Critical notification workflow closed loop: who notified · when · read-back
Every result walks this path (CLSI AUTO10/AUTO15). Passing all gates auto-releases without human touch; any failure lands on the technologist worklist with full attribution. Critical values can never auto-release silently — they always enter the documented closed-loop notification workflow CAP inspectors ask for.

Quality control

Control-lot management, Levey-Jennings charts, and Westgard multirules (1-3s, 2-2s, R-4s, 4-1s, 10x). QC failure blocks result release for the affected run and requires documented corrective action.

Delta checks

Every result is compared to the patient's prior value against per-analyte absolute and percentage limits — the classic catch for mislabeled specimens.

Critical values

Panic results trigger a closed-loop notification workflow that records who was notified, when, by whom, and the read-back — the documentation CAP and Joint Commission expect.