Pathology & Diagnostic Lab Management

Key Features

`Lab Test Catalog` and `Test Panel` DocTypes where a panel expands into component analytes, each with units, specimen type, method, and turnaround target

Per-analyte `Reference Range` child table resolved by sex and age band at result-entry time, so the correct normal range is applied automatically

`Test Requisition` DocType linked to ERPNext Customer/Patient and Price List, with an `on_submit` hook that auto-creates one `Sample` per required specimen type

Code128 barcode label printing and unique accession numbers via a Frappe naming series for full specimen identification

Sample chain-of-custody state machine (`Collected → Received → In-Process → Reported`) with each transition written by audited `@frappe.whitelist()` methods

Server-side `validate` controller that flags abnormal and critical results against the resolved reference range and blocks incomplete panel verification

Two-step technologist-then-pathologist authorization enforced by a Frappe Workflow plus role-based permission rules

PDF report generation via a Jinja Print Format on your letterhead, released only after authorization

Automatic report delivery through a `scheduler_events` job that emails/SMSes a secure report link once authorized

Referral-doctor and commission tracking with per-reported-test accrual and settlement against ERPNext Journal Entries

Whitelisted REST endpoints so a phlebotomy/collection app or patient portal can push and pull status over the Frappe REST API

Role Profiles for front-desk, phlebotomist, technologist, and pathologist that scope who can order, receive, enter, and authorize

Client Scripts for fast bench data entry — keyboard-driven result grids, auto-flagging, and unit hints on the result form

Optional analyzer/HL7-to-ERPNext ingestion path that maps instrument output onto the correct sample and analyte (scoped per instrument)

Turnaround-time and pending-worklist reports (Query Reports / dashboards) so the lab can see aging samples in real time

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Diagnostic and pathology labs live and die by turnaround time and result accuracy, but ERPNext core has no laboratory information system. The stock Healthcare module gives you patients, encounters, and a basic Lab Test DocType, yet it stops well short of a real LIS: there is no barcoded specimen chain of custody, no panel-to-analyte decomposition, no per-analyte reference ranges by age and sex, no critical-value flagging, no analyzer interface, and no referral-doctor commission accounting. Labs end up gluing these gaps together with spreadsheets, WhatsApp result sharing, and manual PDF editing — which is exactly where samples get mislabeled and reports go out wrong.

ECOSIRE builds a proper Frappe application (its own app in apps/, installed on your bench, with a dedicated module and namespaced DocTypes) that layers a full LIS workflow onto ERPNext without forking core. We model a Lab Test Catalog and Test Panel structure where a panel expands into its component analytes, each analyte carrying units, method, and a Reference Range child table keyed by sex and age band so the correct normal range is resolved automatically at result-entry time. Ordering flows from a Test Requisition DocType that links to the ERPNext Customer/Patient, prices against a standard Price List, and — via a hooks.py on_submit doc event — auto-generates one Sample record per required specimen type with a printable barcode label (Code128) and a unique accession number from a Frappe naming series.

Sample tracking is a real state machine: Collected → In-Transit → Received → In-Process → Reported, with each transition written by whitelisted methods (@frappe.whitelist()) so the collection app, front-desk, and analyzer bench all move samples through the same audited path. Result entry is a controller-validated form — a server-side validate hook compares each numeric result to the resolved reference range, auto-sets the abnormal/critical flag, and blocks verification of a panel until every mandatory analyte is entered. Report generation uses a Frappe Print Format (Jinja + your letterhead) rendered to PDF and released only after a two-step technologist-then-pathologist sign-off enforced by role-based permissions and a Workflow. Delivery is automated through a scheduler event in scheduler_events that emails or SMSes patients a secure report link once the report is authorized, and referral-doctor commission is accrued per reported test into a ledger you can settle against ERPNext Journal Entries.

Because this is build-to-order, nothing is a pre-packaged download. We start from your actual test menu, referral network, and report layouts, agree the scope in writing, then build and validate the app against Frappe/ERPNext v15 and v16. You get the installable source for your version, a git repository handover, and a staging UAT before anything touches production. Typical delivery is 2–4 weeks from confirmed scope depending on catalog size, analyzer integrations, and the number of report templates.

What you get

Installable Frappe app source code built for your ERPNext version (v15 or v16), ready to `bench get-app` / `bench install-app`

On-site or remote installation and configuration on your bench, including naming series, role profiles, and report templates

Technical documentation: DocType model, hooks, whitelisted methods, scheduler events, and integration points

End-user guide plus a live training session for front-desk, bench technologists, and pathologists

UAT on a staging site with a documented test plan and a rollback plan before production cutover

Post-go-live support window for defect fixes and configuration tuning

Private git repository handover with full commit history and branch/tagging convention

Data-migration assistance for your existing test catalog, referral doctors, and price list

Who this is for

Standalone diagnostic lab owner

Runs a single-site pathology or diagnostic lab and needs an LIS-style workflow — barcoded samples, reference-range result entry, and clean PDF reports — without buying a separate LIS bolted onto ERPNext for billing.

Multi-branch lab network operations lead

Manages collection centres feeding a central processing lab. Needs sample chain of custody across in-transit hand-offs, accession numbering, and turnaround-time visibility so aging or lost samples surface before patients call.

Pathologist / lab director

Signs off results and is accountable for accuracy. Needs enforced technologist-then-pathologist authorization, automatic critical-value flagging against age/sex reference ranges, and an audit trail on every result and report.

Referral-driven lab with doctor commissions

Depends on referring physicians for volume and needs per-test commission accrual tied to reported results, with settlement that reconciles against ERPNext accounting rather than a side spreadsheet.

How Pathology & Diagnostic Lab Management Compares

Criterion	ECOSIRE	Custom Build	Competitor
Fit to your test menu	Built around your exact panels, analytes, and reference ranges	Fully bespoke but you carry the full build and spec risk	Generic catalog you bend to fit
Sample chain of custody	Barcoded accession + audited state machine transitions	Possible, but must be designed and built from zero	Rarely goes beyond a status field
Reference ranges & flagging	Age/sex-resolved ranges with auto critical-value flags	Depends entirely on your developer's effort	Often single fixed range per test
Report authorization	Enforced technologist-then-pathologist Workflow + roles	You define and build the sign-off yourself	Single-step or no enforced sign-off
Referral commissions	Per-test accrual settled via ERPNext Journal Entries	Buildable, added scope and cost	Usually absent
ERPNext v15/v16 upgrades	Namespaced app, no core fork, upgrades cleanly	Risk of core patches that break on upgrade	Varies with vendor maintenance
Delivery model	Build-to-order, 2–4 weeks, source + git handover	Months of in-house build and hiring	Instant install but generic fit
Ongoing ownership	You own the source; support window included	You own it and all maintenance burden	Vendor-locked, per-seat or subscription

Frequently Asked Questions about Pathology & Diagnostic Lab Management

Is this an existing app I can download from the Frappe marketplace?

No. This is a build-to-order ERPNext application. ECOSIRE scopes it to your actual test menu, referral network, and report layouts, then builds, installs, and supports it. There is no instant download — you receive source built for your version and installed on your bench.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The exact timeline depends on the size of your test catalog, how many report templates you need, and whether analyzer/instrument integrations are in scope. We confirm the schedule in writing before we start building.

Does it work with ERPNext v15 and v16?

Yes. We build and validate against Frappe/ERPNext v15 and v16. Because it is delivered as its own Frappe app installed on your bench rather than a core fork, it upgrades cleanly alongside ERPNext.

How do updates and support work after go-live?

Every engagement includes a post-go-live support window for defect fixes and configuration tuning. You also receive the full git repository, so your team or ours can maintain and extend the app. Longer-term support and enhancement retainers are available if you want ECOSIRE to keep evolving it.

Can it connect to our analyzers or a patient/collection app?

Yes, as scoped work. The app exposes whitelisted methods over the Frappe REST API for a collection or patient-portal app, and we can build an analyzer/HL7 ingestion path that maps instrument output onto the correct sample and analyte. Instrument integrations are priced per device during scoping.

Will it replace our ERPNext billing and accounting?

No — it complements them. Requisitions price against your standard Price List, invoicing stays in ERPNext, and referral commissions settle against ERPNext Journal Entries. The app adds the laboratory workflow that core ERPNext lacks; it does not duplicate finance.

What do we own at the end?

You own the delivered source code for your version and get a full git repository handover with commit history. There is no per-seat license lock-in on the app itself; your only ongoing cost is optional support or future enhancement work.