Managing the Laboratory Test Catalogue and Rate Cards

Internal test codes should be stable, unique, and meaningless. Stability matters because the code appears on historical reports and in every downstream dataset. Meaninglessness matters because any encoded attribute — department, method, price band, sample type — will eventually change while the code cannot.

Alongside the internal code, tests should carry standard terminology where it exists. LOINC identifies laboratory observations and is what makes results interpretable outside the issuing laboratory; SNOMED CT covers the broader clinical concept space. For hospitals working toward ABDM participation, mapped results are what allow a report to be meaningful in a shared health record rather than being a PDF with a local label.

Display names are a separate field from the code and from the standard mapping, and they should be curated for the audience. Clinicians order by the name they were taught, patients read the name on the report, and the two need not be identical. Synonym support in the order search is what stops a clinician creating a duplicate test because they could not find the existing one.

Laboratories use these words loosely and then build systems that cannot distinguish them. A panel is a set of analytes produced together by a single method on a single specimen — the components are not separately performable in practice. A profile is a clinically grouped set of separate tests ordered together for convenience, where each component is a real test in its own right. A package is a commercial bundle with its own price, often spanning laboratory, radiology, and consultation.

The distinction determines behaviour. A profile component can be individually cancelled, rejected, or repeated; a panel component generally cannot. A package needs a price that is not the sum of its parts and needs rules for what happens when one component is not performed. Modelling all three as the same construct forces workarounds at the counter.

Reporting follows the same split. A panel reports as a block, a profile reports as its components possibly at different times, and a package reports as whatever its components are while billing as one line. Getting this right is what prevents partial-result confusion for the clinician and disputed bills for the patient.

The catalogue is where the collection instruction lives, and it is consumed at the point of draw whether or not anyone thinks of it that way. Tube type, minimum volume, whether the sample needs to be on ice, protected from light, or centrifuged and separated within a stated period — all of it belongs against the test rather than in a laminated sheet on the collection room wall.

When it lives in the catalogue, the collection worklist can be generated correctly: one tube per container type across all the tests ordered, rather than one tube per test. That single derivation reduces both the number of tubes drawn and the number of add-on draws when a required container was missed.

Referred-out tests need extra attributes: the reference laboratory, their specimen requirement, their turnaround, and the dispatch schedule. A test the hospital does not perform still needs a complete catalogue entry, and an incomplete one is why send-out samples arrive at the reference laboratory unusable.

One test has many prices. The cash rate, corporate contract rates, insurance and TPA rates, CGHS and ESIC rates, Ayushman Bharat PM-JAY package rates where applicable, camp and health-check package rates, and internal transfer rates between branches can all apply to the same catalogue entry. The system needs a rate structure that resolves the applicable price from the patient's scheme rather than requiring counter staff to know it.

Rate cards should be effective-dated in their own right, separate from the test definition. A negotiated corporate tariff revision changes prices without changing the test, and conflating the two means a price update touches clinical master data. Keeping them separate also means a rate card can be prepared and approved ahead of its effective date.

Resolution order needs to be explicit when a patient qualifies under more than one arrangement — a corporate employee with an insurance policy presenting for a package, for instance. A platform such as HealUDoc can resolve the applicable tariff from the patient's scheme and package at the point of order so the estimate the patient is given matches the bill they eventually receive.

The rule that protects the archive is that catalogue entries are versioned, never overwritten. When a reference interval changes, a method changes, or a test is renamed, a new version takes effect from a date and the previous version remains attached to the results issued under it. A result reprinted three years later should show the reference interval that applied when it was reported, not today's.

Method changes deserve particular care because they can shift results without any error occurring. Where a new method is not numerically comparable with the old one, the trend view a clinician sees is misleading unless the change is visible. Marking the method transition on the cumulative result view is a small feature that prevents a real misreading.

Retiring a test is a controlled action rather than a deletion. The entry stops being orderable from an effective date, existing orders in flight complete under the old definition, and historical data remains queryable. Deleting a test to tidy the catalogue is how a laboratory loses the ability to report on its own history.

Shared ownership without a named owner is the usual state, and it is why catalogues drift. The workable pattern is a single custodian — commonly laboratory quality or laboratory operations — with mandatory sign-off from the clinical side for anything affecting ordering, reference intervals, or reporting, and from finance for anything affecting price.

Batch changes on a published schedule beat continuous editing. A monthly release window with a reviewed change list gives collection, billing, and clinical teams a chance to see what is changing, and it creates a natural audit record. Urgent changes still need a fast path, but the fast path should be an exception with a documented reason.

Run a periodic catalogue review looking for the specific decay patterns: duplicate entries created because search failed, tests never ordered in a year, tests with no tariff on an active payer, entries missing standard code mappings, and reference intervals that have not been reviewed since go-live. Each of those has a real operational cost attached.