HL7 TCU_U10 (Automated Equipment Test Code Settings Update)

HL7 TCU_U10 Automated Equipment Test Code Settings Update

A snapshot of analyzer test-code configuration, not a row-by-row patch.

HL7 message structure TCU_U10 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
SFT	Software Segment	No	Yes
EQU	Equipment Detail	Yes	No
TCU_U10.TEST_CONFIGURATION	Test Configuration group	Yes	Yes
SPM	Specimen	No	No
TCC	Test Code Configuration	Yes	Yes
ROL	Role	No	No

TCU_U10 sends test code settings and parameters from automated equipment to another application, commonly a Laboratory Automation System. It is the message for communicating how the sender currently understands test codes, specimen context, dilution behavior, rerun settings, dynamic ranges, and other automation parameters.

The important word is snapshot. The receiver should understand whether this message replaces its previous parameter set for the sender, rather than treating every TCC row as an independent add or delete.

A small TCU U10 example

MSH|^~\&|ANALYZER01|CORELAB|LAS|CITYHOSP|20260723113000||TCU^U10^TCU_U10|TCU100001|P|2.5.1 EQU|ANALYZER01^Chemistry Analyzer 1^CITYHOSP|20260723113000|IDLE^Idle^HL70365|REMOTE^Remote control^L|N^Normal^HL70367 SPM|1|||SER^Serum^HL70487 TCC|GLU^Glucose^L|APPGLU01^Analyzer application^L|SER^Serum^HL70487|1|1|1|0|10|Y|Y|Y|0^to^700|mg/dL^milligram per deciliter^UCUM

What workflow it represents

The equipment or automation system is publishing its current test-code configuration. The receiver may use it to validate orders, align analyzer mappings, display instrument settings, or compare expected and actual capabilities.

This is usually a configuration-management conversation, not routine result reporting. It belongs near interface setup, analyzer changes, maintenance, and reconciliation workflows.

How to read the structure

MSH identifies the update event. Optional SFT can identify software. Required EQU identifies the equipment whose test settings are being reported.

Each TEST_CONFIGURATION group can include optional SPM when the settings are specimen-specific. Required repeating TCC rows carry the test code configuration details, including service identifier, application identifier, specimen source, dilution defaults, rerun/repeat behavior, and related analyzer settings.

Implementation traps

Do not silently merge snapshots as if they were patches. If the sender says the message represents the current parameter set, the receiver needs a careful replacement or reconciliation strategy.

Test code identity is another common trouble spot. TCC-1 and TCC-2 should make it clear whether you are talking about the LIS orderable, the instrument application, or a local mapping between the two.

If configuration changes affect routing or result interpretation, log them loudly. A quiet test-code setting mismatch can turn into a result that looks valid but was processed under the wrong assumptions.

Reference notes

HL7 v2+ describes TCU_U10 as a message for sending test-code and parameter information. It states that the message transfers the current snapshot of the sender's test parameters, replacing the receiver's previous parameter set for that context rather than selectively adding or deleting rows.