HL7 ISD Interaction Status Detail
HL7 field reference ISD 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
ISD carries interaction status detail for equipment or interface status exchanges.
The standard describes ISD this way: The interaction detail segment contains information about the status of specific interaction (e.g., processing )
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 ISD in ESU_U01 - Automated equipment status 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.
ISD-1 says what action is being taken for this segment or record: add, update, delete, cancel, clear, or another profile-defined operation. It needs to agree with the message trigger and the previous state.
ISD-2 says what action is being taken for this segment or record: add, update, delete, cancel, clear, or another profile-defined operation. It needs to agree with the message trigger and the previous state.
The generated panel links this to HL7 table 0368; many real interfaces narrow that list further, so follow the receiver's implementation guide.
ISD-3 tells the receiver the state of this equipment or specimen workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0387 or the narrower table in the local profile.