Analyzer setup with partial mappings

Analyzer Types still require an operator to review and confirm mappings. A confirmed revision can contain unresolved rows: those rows are not verified or excluded, and they do not prevent the analyzer from connecting. Connection/profile readiness and review of the exact mapping revision still apply.

New shared mappings use profile LOINC defaults when the active local catalog has a unique compatible match. Repeated LOINCs require a unique profile code/alias/name hint to distinguish the candidates. Categorical answers are filled only when their labels match uniquely (ignoring case and whitespace). No vendor-specific synonyms or positive/negative equivalences are guessed. Existing saved choices are never overwritten when another analyzer is created or setup is reopened.

A catalog change affects only the relevant results

For a previously confirmed configuration, an inactive test or answer choice holds only observations that use that mapping. Other valid observations continue to ordinary review. The original value and source payload remain available for correction and retry. Restoring the catalog entry or applying a corrected, confirmed mapping recovers the saved observation in place.

The mapping editor may still show the overall configuration as needing attention; that status does not make every incoming observation invalid. The selected profile, mapping revision, recorded review and control-recognition configuration must still match. A newly saved but unconfirmed replacement does not inherit a previous revision's confirmation.

Correct and recover held results

1. Open the analyzer's results in Analyzer Results. A held row shows its original code and value; follow its Review Analyzer Type mapping link. Original test codes, values and source context are retained.
2. In Analyzer Types, select the correct local test and answer choices. Unrecognized codes and values observed in held traffic also appear in the editor. If no choices exist for a selected test, check the test selection and its catalog configuration.
3. Save and confirm the mapping. Remaining unresolved rows may stay unresolved; their incoming results will remain held.
4. From the held row's Review Analyzer Type mapping link, choose Apply mappings and retry held results to adopt the current revision for that analyzer and retry its held rows in place. The setup Verify → Continue to Connect action does the same for an analyzer being configured. Saving or confirming a shared mapping alone does not change a running analyzer's selected revision.
5. Check Analyzer Results again. Resolved rows become available for the usual review. Unresolved rows remain held. Adoption does not accept results into a patient's clinical record.

For an Awaiting specimen row, choose one of the displayed specimen types and accept it in Analyzer Results. The row stays staged if no valid specimen can be selected; a held mapping result cannot be accepted through that choice. Results received together that add new tests to an order share one specimen: choose a type every one of them can use, or they all stay staged. When their tests have no specimen type in common in the test catalog, there is nothing to choose; they stay staged until the catalog gives those tests a common specimen type.

Use Undelivered analyzer results → Retry for messages still queued in Bridge. That is separate from mapping recovery: a message already accepted by OE has a delivery receipt, and resending it intentionally does not create new work or duplicates.

Do not receive means intentionally omit that code/value from clinical staging. It is not a substitute for leaving an uncertain mapping unresolved. Previously held rows are retained if the new mapping excludes them; historical observations are not deleted.