HealthShare Health Connect Maintenance Release Changes (2020.1.1)

HSHC-2141: Fix possibility of endless loop in IHE DSUB Notification Broker

Category: Healthcare Interoperability

Platforms: All

Version: 2020.1.1

Description: The FilterIntendedRecipients method of HS.IHE.DSUB.NotificationBroker.Operations had an erroneous For loop that has been fixed.

HSHC-2214: SubjectLocality for IHE XUA is optional

Category: Healthcare Interoperability

Platforms: All

Version: 2020.1.1

Description: The SubjectLocality of the IHE XUA profile is now optional, which aligns with the SAML specification.

IF-1034: FHIR Server: Database names can be different than name of namespace

Category: Healthcare Interoperability

Platforms: All

Version: 2020.1.1

Description: The UpdateDatabaseResource method has been updated to allow you to create custom names for a FHIR server's globals and routines databases. They do not have to match the name of the namespace.

JGM911: Interoperability Record Map File and FTP services to be able to skip invalid records

Category: Productions

Platforms: All

Version: 2020.1.1

Description: The EnsLib.RecordMap.Service.FileService and EnsLib.RecordMap.Service.FTPService stop processing a source file if a record fails validation, for example a field is too long. A new setting is provided "Fatal Errors" which is similar to that in the batch services. In the EnsLib.RecordMap.Service.FileService and EnsLib.RecordMap.Service.FTPService processing the new FileErrors setting can be either "Any" or "ParseOnly and is as follows:

An error saving an individual Record, such as a validation error, will be treated as fatal and end the processing of the message when the setting is "Any". This is the current behaviour.

If "ParseOnly" is selected, errors when saving individual Records will not be treated as fatal, and parsing of the message will continue after logging an error log and skipping the errored record.

If AlertOnError is enabled, an alert will be sent for a save error when "ParseOnly" is selected.

The default is "Any".

The error reported if ParseOnly indicates the position in the stream for the invalid record.

JGM933: Interoperability Production Foreground option to call correct iristerm.exe on Windows

Category: Productions

Platforms: All

Version: 2020.1.1

Description: The Interoperability Production Foreground option on Windows was not calling the correct local IRIS Terminal binary from the URL. This is now corrected.

JGM936: Correct UNDEFINED for EnsLib.LDAP.Message.EntityIdentification CalculatedDN

Category: Productions

Platforms: All

Version: 2020.1.1

Description: An UNDEFINED error would be thrown when calculating distinguished name from properties of an LDAP Message class (sub class of EnsLib.LDAP.Message.EntityIdentification) when using the Base property.

This is now corrected.

The error happens when specifying Base property along with RDN (Relative Distinguished Name) but not DN and Parent properties. Message classes that are affected: EnsLib.LDAP.Message.Add, Compare, Delete, Modify and Rename

JGM937: Correct Port Authority Report Find InUse Reservations

Category: Productions

Platforms: All

Version: 2020.1.1

Description: The Port Authority task calls Ens.Setting.Report.Port::FindUsedReservations() to check whether some reserved ports are now in use. There was an error that duplicated the Reservations that were found to be In Use. This is now corrected.

To prevent this error before a patch can be applied it is possible to prevent the current post processing that causes the issue by turning off the 'viiiPostSaveProcessing' task option. This also stops the FindConflicts and FindAvailability code being run but that can be run manually with:

##class(Ens.Setting.Report.Port).FindConflicts(1)
##class(Ens.Setting.Report.Port).FindAvailability(1)

It is possible to remove multiple copies of reservations with the SQL:

Delete FROM ISC_DM.IRISInteroperabilityPorts
    WHERE document='reservation' and inbound=1 and ID NOT IN
    (
        SELECT MAX(ID) AS MaxRecordID
        FROM ISC_DM.IRISInteroperabilityPorts
        WHERE document='reservation'
        AND inbound=1
        GROUP BY server, mirror, port, interface, inbound
    )

JGM938: Expose SFTP Session RemoteCharset and LocalCharset to the Interoperability FTP adapter

Category: Productions

Platforms: All

Version: 2020.1.1

Description: The underlying SFTP classes used by the Interoperability SFTP adpaters now implement two properties for the encoding of filenames: RemoteCharset and LocalCharset.

The introduction of these properties changed the default behavior since SSH draft working group standards give filename representation in the UTF-8 character set.

The ability to set these 2 properties is now exposed in the Interoperability FTP adapters as

SFTP Server Character Set (SFTPRemoteCharset)

Character set for file names used by the remote server. Defaults to UTF8. Set to empty string for no translation on the character sets for filenames. This setting is used to set the RemoteCharset property in the %Net.SSH.Session object.

SFTP Local Character Set

Character set used by the local system for filename encoding. For Windows the default is the empty setting which will leave local filenames as Unicode For UNIX the default is to convert to UTF8 This setting is used to set the LocalCharset in the %Net.SSH.Session object

JGM940: Interoperability MQ Series Inbound and Outbound adapter to support username and password

Category: Productions

Platforms: All

Version: 2020.1.1

Description: Interoperability MQ Series Inbound and Outbound adapter to support username and password authentication as provided by the core MQ classes.

The username and password are obtained from the exposed Credentials setting.