Identifies the software product that produced or contributed to the message, including vendor name, software version, product name, and installation identifier. It is an optional segment that can follow MSH in virtually any HL7 v2 message (v2.5 and later), allowing receiving systems to log the sending application's exact software version for troubleshooting, support, and audit purposes.
from zato.hl7v2.v2_9 import SFT
from zato.hl7v2.v2_9 import XON
sft = SFT()
vendor = XON(organization_name='Zato Source')
sft.software_vendor_organization = vendor
sft.software_certified_version_or_release_number = '4.1'How to construct and work with real-world SFT segments.
HL7 integration platform info
from zato.hl7v2.v2_9 import SFT
from zato.hl7v2.v2_9 import XON, DTM
sft = SFT()
sft.software_vendor_organization = XON(organization_name='Zato Source')
sft.software_certified_version_or_release_number = '3.2.1'
sft.software_product_name = 'Zato HL7v2'
sft.software_binary_id = 'BUILD-20240115'
sft.software_install_date = DTM('20240115')Electronic health record system
from zato.hl7v2.v2_9 import SFT
from zato.hl7v2.v2_9 import XON, DTM
sft = SFT()
sft.software_vendor_organization = XON(organization_name='Epic Systems')
sft.software_certified_version_or_release_number = '2024.1'
sft.software_product_name = 'Epic EHR'
sft.software_binary_id = 'BUILD-2024-001'
sft.software_install_date = DTM('20240101')Laboratory information system
from zato.hl7v2.v2_9 import SFT
from zato.hl7v2.v2_9 import XON, DTM
sft = SFT()
sft.software_vendor_organization = XON(organization_name='Lab Corp')
sft.software_certified_version_or_release_number = '5.4.2'
sft.software_product_name = 'LabIS'
sft.software_binary_id = 'BUILD-542-001'
sft.software_install_date = DTM('20231215')Step-by-step guides for working with HL7 v2 in Zato.
SFT contains software segment information including vendor, version, product name, and installation dates for application management.
SFT is typically included after MSH to identify the sending application. Multiple SFT segments can be used for multi-component systems.
Use software_certified_version_or_release_number field:
sft.software_certified_version_or_release_number = '3.2.1'SFT provides detailed software information while MSH identifies the sending application at a high level. SFT follows MSH in the message.
Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.
Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.
Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.
Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.
Complete list of fields in the SFT segment, HL7 v2.9.
| # | Python name | Datatype | Usage | Repeatable | Table |
|---|---|---|---|---|---|
| 1 | software_vendor_organization | XON | Required | No | - |
| 2 | software_certified_version_or_release_number | ST | Required | No | - |
| 3 | software_product_name | ST | Required | No | - |
| 4 | software_binary_id | ST | Required | No | - |
| 5 | software_product_information | TX | Optional | No | - |
| 6 | software_install_date | DTM | Optional | No | - |
Get started with Zato and connect your systems in minutes.