What's New and Different

PreviousNext

Ways in which the .Net objects differ from the ActiveX objects.

(c) 2011 Hermetech International Ltd.

New In Version 3.0.1

 

•Version 3.0.1 addresses a bug in version 3.0 which would generate an error when trying to create custom HL7 segments through the Vendor Manager User Interface.

 

New In Version 3.0

 

•New function in the HL7Vendor object: HL7TableLookup.
•The MAJOR changes in version 3.0 are the changes to the internal file structure used to store the EasyHL7 Vendor definitions. This will impact the ImportVendor, ExportVendor and InstallDefaultVendors methods. See Vendor File Formats for full information on this important change.

 

New In Version 2.0

 

•New Namespace to easily identify which .Net Framework (EasyHL7MC20 for Framework 2.0, EasyHL7MC35 for the Framework 3.5) the class libraries use.
•Method Parameters and Properties are now explicitly typed. In version 1.nn for example the method HL7Vendor.GetVendorID(sVendorName, sVendorVersion). In Version 1.xx the parameters sVendorName and sVendorVersion were untyped (or rather were generic object types). In version 2.0 these 2 parameters are explicitly typed as strings, which should be good news for all of our C# programmers.
•All references to the EasyHL7 ActiveX components are removed and those methods that used them have been deprecated.
•An entirely NEW User Interfaces class (EasyHL7MC40_UI) has been implemented for creating MS Windows applications. This is particularly exciting because of some of the expanded features available with this class module including the EasyHL7RichTextbox Class. A customized subclass of the standard .Net RichTextbox control for Windows forms which has some great features and embedded HL7 reports. You can put our reports right into YOUR application!
•The former limitation of repeating fields has been removed. Now any HL7 field can repeat an unlimited number of times.