HL7 SID Substance Identifier
HL7 field reference SID 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
SID identifies a substance or specimen-related item in analyzer and lab automation workflows.
The standard describes SID this way: The Substance Identifier segment contains data necessary to identify the substance (e.g., reagents) used in the production of analytical test results. The combination of these fields must uniquely identify the substance, i.e., depending on the manufacturer all or some fields are required (this is the reason the optionality is 'C' (conditional)). If the analysis requires multiple substances, this segment is repeated for each substance. The segment(s) should be attached to the TCD segment. Another purpose of this segment is to transfer the control manufacturer, lot, etc., information for control specimens. In this case the SID segment should be attached to the SAC segment describing the container with the control specimen.
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 SID in OUL_R21 - OUL - Unsolicited laboratory observation, OUL_R22 - OUL - Unsolicited Specimen Oriented Observation message, OUL_R23 - OUL - Unsolicited Specimen Container Oriented Observation message, and OUL_R24 - OUL - Unsolicited Order Oriented Observation message. 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.
SID-1 identifies the Application / Method 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.
SID-2 identifies the Substance Lot Number 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.
SID-3 identifies the Substance Container 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.
SID-4 identifies the Substance Manufacturer 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.
The generated panel links this to HL7 table 0385; many real interfaces narrow that list further, so follow the receiver's implementation guide.