Reference Ranges

Governed reference, critical, reportable, and linearity range profiles — tied to test identity, source, method, demographics, and effective dates, and customer-approved before they affect clinical behavior.

What It Does

Every analyzer reports a result against a reference range, but the range that is correct for one source, method, and patient population is not correct for another. Reference Ranges is the governed registry that stores customer-approved range profiles with full context, so the right range is used for the right patient, specimen, and method.

Each profile records four families of bounds, each independently optional:

A profile is tied to a test identity and carries source, specimen, fluid, collection source, method, module, and unit context, plus demographic bounds (sex and age in days) and an effective date window. Parsed OBX-7 text from messages remains available as trace evidence, but only governed profiles are used for clinical decisions.

Review-gated by default. Each profile carries a validation status — draft, approved, or retired — plus an evidence record. Approved profiles appear in verification notes as evidence, but they do not change result disposition until governed critical/reportable/linearity behavior is validation-gated and product-reviewed.

Context and Demographics

Reference ranges vary by patient population. A profile can be scoped by sex (female, male, unknown, or any) and by age range in days, so pediatric and adult ranges can coexist for the same test. The material and method context — specimen, fluid, collection source, method, module, and unit — is recorded alongside each profile so a range is only selected when the observed context agrees.

Numeric bounds are validated at write time: the high bound must not fall below the low bound, and an effective end date must follow the start date.

Import and Review

Ranges are created, edited, imported, and exported through the Sources > Reference Ranges surface. Bulk CSV import uses a template and requires reviewed rows before they are committed. Create, update, and delete actions write an audit record before changing range state, and fail closed if audit logging is unavailable. Approve and retire actions are evidence-gated, so a draft cannot be approved while it lacks validation evidence or has a conflict in the same context.

When two enabled profiles share the same test identity and context but define different bounds, Vorian Connect surfaces that conflict as a review signal rather than silently choosing a winner.

Where It Fits

Technical Details

Last updated: August 16, 2026