HL7 TCC Test Code Configuration
HL7 field reference TCC fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| TCC.1 | Universal Service Identifier | Yes | No | CE | |
| TCC.2 | Test Application Identifier | Yes | No | EI | |
| TCC.3 | Specimen Source | No | No | SPS | 0070 |
| TCC.4 | Auto-Dilution Factor Default | No | No | SN | |
| TCC.5 | Rerun Dilution Factor Default | No | No | SN | |
| TCC.6 | Pre-Dilution Factor Default | No | No | SN | |
| TCC.7 | Endogenous Content of Pre-Dilution Diluent | No | No | SN | |
| TCC.8 | Inventory Limits Warning Level | No | No | NM | |
| TCC.9 | Automatic Rerun Allowed | No | No | ID | 0136 |
| TCC.10 | Automatic Repeat Allowed | No | No | ID | 0136 |
| TCC.11 | Automatic Reflex Allowed | No | No | ID | 0136 |
| TCC.12 | Equipment Dynamic Range | No | No | SN | |
| TCC.13 | Units | No | No | CE | |
| TCC.14 | Processing Type | No | No | CE | 0388 |
TCC carries test-code configuration used by analyzers and lab automation systems.
The standard describes TCC this way: The test (e.g., analyte) code configuration segment is the data necessary to maintain and transmit information concerning the test entity codes that are being used throughout the "automated system.".
Equipment and specimen-control segments are used around instruments, analyzers, containers, device commands, device status, and test configuration. They are practical plumbing for lab and automation workflows.
The main trap is treating an equipment status as if it were a clinical result, or treating a specimen/container identifier as if it were interchangeable with a patient or order identifier. Keep the layers separate.
The v2.5.1 structures show TCC in TCU_U10 - Automated equipment test code settings update. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
TCC-1 identifies the Universal Service Identifier for this equipment or specimen workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
TCC-2 identifies the Test Application Identifier for this equipment or specimen workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
TCC-3 describes specimen or container handling. This is not patient identity and not order identity; it is the physical or analyzer-side detail needed to move, test, store, or track the specimen correctly.
The generated panel links this to HL7 table 0070; many real interfaces narrow that list further, so follow the receiver's implementation guide.
TCC-4 describes specimen or container handling. This is not patient identity and not order identity; it is the physical or analyzer-side detail needed to move, test, store, or track the specimen correctly.
TCC-5 describes specimen or container handling. This is not patient identity and not order identity; it is the physical or analyzer-side detail needed to move, test, store, or track the specimen correctly.
TCC-6 describes specimen or container handling. This is not patient identity and not order identity; it is the physical or analyzer-side detail needed to move, test, store, or track the specimen correctly.
TCC-7 describes specimen or container handling. This is not patient identity and not order identity; it is the physical or analyzer-side detail needed to move, test, store, or track the specimen correctly.
TCC-8 qualifies the equipment or specimen workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
TCC-9 carries Automatic Rerun Allowed for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
TCC-10 carries Automatic Repeat Allowed for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
TCC-11 carries Automatic Reflex Allowed for this equipment or specimen workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0136; many real interfaces narrow that list further, so follow the receiver's implementation guide.
TCC-12 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
TCC-13 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
TCC-14 qualifies the equipment or specimen workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0388. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.