14 min readLab managers, senior technicians, and catalog administrators.

Add a new test to the catalog

Create a test definition with names, sample requirements, parameters, reference ranges, pricing, and report behavior.

Introduction

The test catalog is the foundation of the Lab Panel. Orders, samples, prices, results, reports, packages, public website pages, and patient portal behavior all depend on how each test is defined.

A good test definition prevents rework. Reception can select the correct item, collection staff know which sample to collect, technicians see the right result fields, reviewers see correct reference ranges, and patients receive a clear report.

Before adding the test

Collect the clinical and operational details before opening the form:

  • Accurate English test name; keep the Arabic catalog name for compatibility.
  • Internal code or abbreviation.
  • Category or department.
  • Sample type and container.
  • Required volume or collection instructions.
  • Turnaround time.
  • Result parameters and units.
  • Reference ranges by age, gender, or condition if needed.
  • Base price.
  • Whether the test can appear on public pages or packages.

If any of these details are missing, keep the test inactive until a senior technician or manager confirms them.

Create the test identity

Open the test catalog and create a new test. Enter the English name carefully because it is the displayed Test name throughout Kashef, including Arabic pages. Keep the Arabic name accurate for catalog compatibility and integrations, but do not expect it to replace the English name in orders, samples, results, reports, or patient-facing pages. Use the internal code if your lab uses codes on worksheets, devices, reports, or price lists.

Choose the correct category. Categories help reception search quickly, help reports group results, and help managers review catalog coverage. Avoid creating too many small categories unless your lab actually works that way.

Set the active state only when the test is ready for use. Inactive tests can remain in the catalog for preparation without appearing in order selection.

Configure sample requirements

Select the sample type, such as serum, plasma, whole blood, urine, stool, swab, or culture sample. Add container notes and collection instructions when staff need them.

Sample requirements should be clear enough that a new receptionist or collector does not need to ask a technician every time. Include fasting notes, timing notes, storage notes, minimum volume, and rejection conditions when they affect the result.

If several tests can share the same sample, configure them consistently. This helps Kashef prepare the right labels and reduces unnecessary collection.

Add result parameters

For simple tests, one result field may be enough. For panel tests, add each parameter separately with unit, display order, and reference behavior.

Use clear parameter names. The report should be readable for doctors and patients. Avoid internal shorthand unless the abbreviation is widely understood.

For numeric parameters, configure units and reference ranges. For text results, define expected values or helper notes if the technician needs guidance. For culture tests, configure organisms, antibiotic sensitivity options, and reporting structure.

Configure reference ranges

Reference ranges are one of the most sensitive parts of the catalog. A wrong range can cause normal results to appear abnormal or abnormal results to appear safe.

Review ranges by:

  • Age group.
  • Gender.
  • Unit.
  • Method or analyzer.
  • Pregnancy or special condition if your lab reports it.

Ask a senior technician or lab manager to approve reference ranges before activating the test. If you are migrating from paper or another system, compare a sample report before going live.

Add pricing

Enter the base cash price. This is the default price when no contract, insurer, or special list applies. Contract prices and discounts can be configured later, but the base price should be correct before reception uses the test.

If the test belongs to a package, add it after the standalone test is correct. Packages should not hide incomplete test definitions.

Review report behavior

Check how the test appears on the report. Confirm display order, parameter grouping, units, reference flags, comments, and whether the test should appear as a standalone section or inside a panel.

If your lab uses signatures, QR codes, or reviewer names, generate a sample report and review it before activating the test.

Activate and test

Create a practice order using the new test. Confirm the price, sample label, result entry fields, reference flags, report preview, and release behavior.

Only activate the test for live reception when the practice order looks correct from intake to report release.