HL7 SFT Software Segment
HL7 field reference SFT 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
SFT identifies the software product and version involved in producing or handling the message.
The standard describes SFT this way: This segment provides additional information about the software product(s) used as a Sending Application. The primary purpose of this segment is for diagnostic use. There may be additional uses per site-specific agreements.
SFT identifies the software that created or handled a message. It is especially useful when several engines, versions, or vendor components can send the same message type.
Most receivers do not route solely from SFT, but it is very helpful for support, audit, and finding the exact product build that generated a malformed message.
The v2.5.1 structures show SFT in ACK - General acknowledgment message, ADR_A19 - Patient query, ADT_A01 - Admit/visit notification, and ADT_A02 - Transfer a patient, and 186 other message structures. 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.
SFT-1 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.
SFT-2 identifies the Software Certified Version or Release Number for this message audit trail. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
SFT-3 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.
SFT-4 identifies the Software Binary ID for this message audit trail. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
SFT-5 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.
SFT-6 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.