Tests catalog

Why the Tests catalog matters

The Tests catalog is the foundation for order creation, sample labels, reference ranges, result entry, report layout, public website browsing, pricing, packages, and lab-to-lab work. A test that is configured carefully can move from reception to final report with very little manual correction. A test that is configured loosely creates repeated problems for reception, technicians, reviewers, and patients.

Use this page when you need to create a new test, update a test name or code, configure sample and processing requirements, define reference behavior, or attach reusable preparation requirements.

General settings

The first section defines the identity of the test. The Code Name must be unique because it is used in formulas, result logic, search, and operational references. Use stable lab codes such as CBC, ALT, FBS, or TSH instead of changing marketing names.

Keep the English name accurate because Kashef displays laboratory test names in English across order entry, samples, results, reports, invoices, worksheets, partner pages, and patient-facing pages. Arabic interface labels and instructions still follow the selected language, but a Test name is never replaced with name_ar. The Arabic name remains available for catalog compatibility and integrations. Historical orders use the captured English snapshot when available, then a legacy English name, code, or Unnamed Test when necessary. The category controls where the test appears in browsing and reporting lists. The test type decides whether the record is a single test or a profile that includes other tests.

Turnaround time sets the expected completion window in hours. Available for Ordering controls whether reception can add the test to new orders.

Profiles and included tests

When the test type is profile, the Profile Composition section requires at least one active single test and lets you drag components into their clinical display order. Use profiles for groups that should be ordered together, such as a lipid profile or liver profile.

Do not duplicate the same single test inside a profile. Do not create a profile when a package is more appropriate. A profile is clinical composition; a package is commercial bundling and pricing.

Sample settings

Sample Settings define which sample and tube combinations can be used. Each tube row includes the sample type, tube or container, and the mL volume the test consumes. The first row is the primary combination used by automatic planning; additional rows are accepted alternatives. These values affect sample creation, barcode preparation, and tube planning.

Use sample types that already exist whenever possible. If you create a new sample type inline, give it a clear name because it will appear in the Sample Log and barcode workflows.

Processing settings

Processing settings now focus on decisions that are not already owned by Sample Settings:

• Processing Workflow: choose In-house when the test is performed inside your laboratory, or Partner Lab when it must go to one approved processing partner. Partner processing requires an active partner account that is enabled as a processing destination.
• Sample Retention After Completion (Days): define how long physical material must be kept after results are submitted or the sample is rejected. When one sample contains several tests, Kashef uses the longest configured period to calculate its EOL. Leave this blank only when retention is managed outside the automatic EOL workflow.
• Collection & Stability: enter the collection amount and display unit used in order guidance, then select the transport temperature and validated stability window in hours. The mL volume consumed by planning remains in Sample Settings, so staff do not have to maintain it twice.
• Preparation & Sample Use: choose one main preparation workflow, add a short controlled detail when needed, and record fasting in hours. Mark a dedicated sample only when sharing is prohibited. Allow aliquots only when the procedure permits them, then mark Requires Aliquot when separation is mandatory.

Write both patient and collector instructions in English and Arabic. Patient instructions should explain what the patient must do before collection. Collector instructions should cover identity checks, collection, labeling, mixing or clotting, temperature, transport, and processing. These catalog-controlled instructions appear during order readiness and sample creation and are captured on the planned sample so later staff use the rules that applied when it was created.

Kashef keeps the primary specimen, container, and consumed volume synchronized from the first Sample Settings row when the test is saved. Catalog JSON export and import preserve these structured collection rules by sample code and container name, making the configuration portable without carrying branch-specific database identifiers.

Reference and interpretation setup

The reference unit is the default unit used for result interpretation. Reference ranges and advanced interpretation rules use this setup to evaluate results during entry and review.

Interpretation rules are evaluated in order. Use them to add comments when a result matches a configured condition. Keep comments clinically clear and avoid generic text that does not help the reviewer or patient.

Calculated formulas

Calculated Formula Settings derive a numeric result from other test results or the patient's age or sex-at-birth encoding. Enable the calculation, declare the produced result unit, write the expression, and map every uppercase variable to one same-laboratory test or supported demographic source. For test dependencies, declare the unit the formula expects. That contract must match the dependency's configured result/reference unit, and the produced unit must match this test's reference ranges.

Kashef validates formula syntax, unknown variables, duplicate mappings, cross-laboratory references, unit mismatches, self-dependencies, and indirect calculation cycles before saving an active definition. Every material change creates a numbered immutable version; unchanged saves do not. Results retain the exact version and definition hash used for traceability. Disabling calculation returns the test to direct entry but preserves earlier definitions and versions. If a required dependency is not ordered or has no numeric result, no calculated result is saved.

Use the formula sandbox with sample values before live use. Supported functions are min(), max(), pow(), abs(), and round(). Enable accountable override only when laboratory policy allows authorized staff to replace an automatic value; the result retains override metadata for review.

Requirements

The Test Requirements section attaches reusable instructions such as fasting, medication, sample timing, or preparation notes. These requirements appear during order creation so reception can mark them met, unmet, or overridden with a reason.

Use reusable requirements instead of typing preparation instructions repeatedly into order notes.

Before making a test active

Before turning a test on for ordering, confirm code, names, category, type, turnaround time, sample tube, processing rules, reference unit, reference ranges, pricing, requirements, and report behavior. Then create a test order in a safe environment or with a controlled workflow and verify sample creation, result entry, and report output.