HL7 ECD Equipment Command
HL7 field reference ECD 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
ECD sends an equipment command to an instrument, analyzer, or automation component.
The standard describes ECD this way: The equipment command segment contains the information required to notify the receiving component what is to happen.
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 ECD in EAC_U07 - Automated equipment command and EAR_U08 - Automated equipment response. 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.
ECD-1 identifies the Reference Command 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.
ECD-2 carries Remote Control Command 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 0368; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ECD-3 carries Response Required 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.
ECD-4 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
ECD-5 carries Parameters 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.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.