Reference native catalog, clinical mapping and specimen review

Everything below describes engineering source contracts and isolated test evidence (disposable PostgreSQL, loopback PostgREST, test-signed tokens). Where a behavior is described as "designed", it exists in source and isolated tests only — not as a joined, persisted canonical R1 workflow. This is not an availability, certification or publication announcement.

Read each laboratory’s authorized native orderables through its own canonical catalog path. Preserve source/destination native codes, laboratory identity, orderable kind, dictionary revision, provenance and fingerprints. A sender cannot rewrite the performer’s catalog. Imported Live or future launch-ready status is editorial evidence only.

1. Identify a single orderable versus a panel; list every required, optional, conditional and reflex component with its role.
2. Record specimen, method, units, container, volume, preparation, handling, collection modes, supported regions and turnaround evidence.
3. Tie the mapping to current Program diagnostic, source/destination orderable and catalog mapping references.
4. Compare the complete nonempty component multiset and constraints, not shared analytes.
5. Submit an independent reviewer decision at a named review and authority version; retain source and destination fingerprints.
6. Invalidate the decision on any dictionary, composition, method, specimen, unit or version change.

LOINC can describe an analyte or panel and UCUM can describe units; neither supplies missing native code or a clinical substitution decision. Do not invent LOINC, UCUM or vendor fields where a source dictionary lacks them. No silent unit conversion or output-unit discrimination resolves ambiguous source codes.

NON_EXECUTABLE synthetic comparison
A panel: required X, optional Y; serum; method M; unit U
B panel: required X, required Y; serum; method M; unit U
Decision: structural mismatch (Y role differs), HOLD
Shared display name / LOINC / X overlap does not authorize substitution

The reference mapping requirements contract names specimen, method, container, volume.amount/unit, preparation, handling, turnaround, collection and regions. Missing governed requirements refuse. Protocol and additional advanced compendium attributes require approved provenance and persistence; this contract does not establish a new persisted field for every imported column.

• Rich optional fields that the existing catalog writer cannot safely persist stay draft/held; do not strip them to make a row importable.
• Future-only, withdrawn, empty-panel, alias-ambiguous or structurally incompatible rows are not orderable.
• Clinical reviewer identity, review status/version and effective period are separate from commercialScopeRef and clinicalScopeRef.
• Transport temperature/stability and TAT need source evidence and approved handling policy; no courier capability is inferred.

• Sender: its own source dictionary and, only while fully source-approved, granted destination code/specimen/menu and its own contracted terms.
• Performer: its own native catalog and native cost; no other sender’s private terms exposed through general reads.
• Unrelated buyer: no private mapping or price; independently published safe network discovery remains separate.
• Blocked sender row: safe refusal identifiers only, never source/destination code, specimen, mapping versions, price or result/webhook scopes.

Test changed component roles, missing optional/reflex members, specimen/method/unit mismatch, stale fingerprints, withdrawn tests, invalid effective dates, incorrect region and cross-laboratory grants. A passing solia.clinical.equivalence.v1 source comparison is not installed reviewer authority; staged bindings are draft-only and all reference execution remains unavailable.