Universal compendium & native catalog workflow

Use the existing four-step CSV/XLSX Catalog Upload Wizard in the selected laboratory workspace. Supply a sanitized source file, source version and native dictionary. A laboratory-native orderable is what the LIS accepts; a commercial catalog item is what an authorized Program may select; a biomarker is a result concept; a panel component is a role-bearing member of an orderable. These are not interchangeable.

The draft intake contract is solia.lab.compendium.intake.v1. It retains laboratory/tenant scope, source provenance, fingerprints and explicit test or panel kind. Unknown codes, specimen, prices, kinds and clinical approvals are not inferred.

• Native order code and source display name; terminology identifiers and synonyms are dictionary suggestions only.
• Test/panel kind and explicit required, optional, conditional or reflex components; inspect full composition, not display-name overlap.
• Specimen and collection constraints, method, turnaround, performing laboratory and effective date/version. Unknown attributes remain unknown.
• Source availability including future, validation and launch plans; imported Live is source status, never Production authorization.
• Separate laboratory-native cost, contracted Program price, network price and consumer commerce price. Fees without verified scope cannot be advertised as complete totals.

file → parse → raw-header safety validation → draft preview
     → reviewer decision → canonical approved catalog (where supported)
     → independent Program authorization → explicit channel publication

Advanced optional panels/components/specimen/method/performer/fees/status attributes are held in draft-review/preview when the current canonical save cannot preserve them. Mapping away rich column names cannot bypass the raw-header gate. Future or unknown status, missing code/kind/specimen, panel composition and ambiguous aliases stay held; do not force them into a simpler row and lose metadata.

1. Keep the accepted source/version snapshot and compare deterministic scoped fingerprints before proposing changes.
2. Identical content is a stable reimport; display/provenance differences and material clinical changes must be distinguished.
3. Changed code, composition, specimen, method or effective date requires a new review and current mapping fingerprints. A missing code is never merged by name.
4. Preserve historical order/result interpretation against the reviewed snapshot; a new source file is not permission to rewrite prior clinical records.
5. When rich persistence is unavailable, keep the changed record held and obtain Core-owner persistence approval before treating it as durably accepted.

source_version: SYN-menu-v1
native_code: SYN-PANEL-A
kind: panel
component: SYN-analyte-A; role: required
component: SYN-analyte-B; role: reflex
source_status: future
review: pending
publication: none

This is a conceptual draft record, not an official vendor workbook schema or API request. It is nonorderable. Do not substitute real clinical identifiers, guess a specimen or add an invented price.