Class TbsSFT_28

Unit

BSHL7DT28

Declaration

type TbsSFT_28 = class(TbsHL7Segment)

Description

Software Segment 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. Implementers are encouraged to use message profile identifiers (as found in 2.14.9.21, "MSH-21 Message Profile Identifier (EI) 01598") to control the behavior of the receiving application rather than relying on application or version information in the SFT segment. For example, if software product A has versions 9 and 10 deployed in different Enterprise locations, the fact that they use different message types, segments, or fields should be reflected via their message profiles (see section 2B, "Conformance Using Message Profiles"). If there is an upgrade from version 10 to 10.1, this would be reflected in the SFT segment, but changes to the message contents should be reflected via a new/different conformance profile. Use Case: An external application has been customized to communicate with a centralized patient drug history system. However, due to certain, known characteristics of the external software package, the centralized system must modify its behavior in order to process transactions correctly. In one example, the external application may have multiple versions in production. As such, the centralized application will need to know the name of the Software Vendor Organization, the Software Release Number, the Software Product Name, and the Software Binary ID so that it can correctly identify the software submitting the transaction and modify its behavior appropriately. While preparing a transaction for submission to a centralized system the sending application specifies its Software Install Date and its configuration settings (Software Product Information). While processing the transaction, the centralized system encounters an error. Upon examination of the error, install date and configuration of the software that sent the message, helpdesk staff are able to determine the sending application has not been updated to reflect recent application changes. Use Case: In circumstances where a message is manipulated or modified by multiple systems, a repetition of this segment may be appended by each system.

Hierarchy

• TBSTypedObject
• TBSTypedComposite
• TBSHL7Object
• TBSHL7Segment
• TbsSFT_28

Overview

Properties

	property SoftwareVendorOrganization : TbsXON_28 read GetSoftwareVendorOrganization write SetSoftwareVendorOrganization;
	property SoftwareCertifiedVersionOrReleaseNumber : TbsST_28 read GetSoftwareCertifiedVersionOrReleaseNumber write SetSoftwareCertifiedVersionOrReleaseNumber;
	property SoftwareProductName : TbsST_28 read GetSoftwareProductName write SetSoftwareProductName;
	property SoftwareBinaryId : TbsST_28 read GetSoftwareBinaryId write SetSoftwareBinaryId;
	property SoftwareProductInformation : TbsTX_28 read GetSoftwareProductInformation write SetSoftwareProductInformation;
	property SoftwareInstallDate : TbsDTM_28 read GetSoftwareInstallDate write SetSoftwareInstallDate;

Description

Properties

	property SoftwareVendorOrganization : TbsXON_28 read GetSoftwareVendorOrganization write SetSoftwareVendorOrganization;
Software Vendor Organization, Min : 1, Max : 1

	property SoftwareCertifiedVersionOrReleaseNumber : TbsST_28 read GetSoftwareCertifiedVersionOrReleaseNumber write SetSoftwareCertifiedVersionOrReleaseNumber;
Software Certified Version Or Release Number, Min : 1, Max : 1

	property SoftwareProductName : TbsST_28 read GetSoftwareProductName write SetSoftwareProductName;
Software Product Name, Min : 1, Max : 1

	property SoftwareBinaryId : TbsST_28 read GetSoftwareBinaryId write SetSoftwareBinaryId;
Software Binary Id, Min : 1, Max : 1

	property SoftwareProductInformation : TbsTX_28 read GetSoftwareProductInformation write SetSoftwareProductInformation;
Software Product Information, Min : 0, Max : 1

	property SoftwareInstallDate : TbsDTM_28 read GetSoftwareInstallDate write SetSoftwareInstallDate;
Software Install Date, Min : 0, Max : 1