HMS Client Version 6.6.3
Release Notes
Version 1.0
Build 6 .6.3 .3091
www.healthlink.net
HMS Client Version 6.6.3 | Release Notes
Version 1.0, 30 October 2012
© HealthLink 2012. All rights reserved. No reproduction, transmission, transcription, storage in a retrieval system, or
translation into any language or by any means, electronic, mechanical, optical, chemical, manual, or otherwise, any
part of this document without express written permission of HealthLink Limited.
HealthLink, the HealthLink logo, HealthLink, HealthLink SIX, HealthLink Messaging System (HMS) are trademarks of
HealthLink, Inc. in New Zealand. All other brand names are trademarks or registered trademarks of their respective
companies.
The content in this document represents the current view of HealthLink as of the date of publication. Because
HealthLink responds continually to changing market conditions, this document should not be interpreted as a
commitment on the part of HealthLink. HealthLink cannot guarantee the accuracy of any information presented after
the date of publication.
Information in this document is subject to change without notice. For the latest documentation, visit our Web site at
http://www.healthlink.net/resources.htm
Liability Notice: Every effort has been made to ensure that the information in this document, supplied by
HealthLink Limited, is accurate and complete. However, as use and interpretation of this document is beyond the
control of HealthLink Limited, no liability, either direct or consequential, can be entertained by HealthLink Limited, its
agents, or its suppliers.
Copyright  2012 HealthLink Limited
Page 2 of 16
HMS Client Version 6.6.3 | Release Notes
Version 1.0, 30 October 2012
Document Control
Version
1.0
Last Saved
30 Oct 2012
Author
Wendy Wang
Filename
HMS 6.6.3 Release Notes v1.0.docx
Document History
Version
1.0
Date
Author
Comment
8 Oct 2012
Wendy Wang
Initial creation
Copyright  2012 HealthLink Limited
Page 3 of 16
HMS Client Version 6.6.3 | Release Notes
Version 1.0, 30 October 2012
Table of Contents
1
Overview ............................................................................................... 5
1.1
1.2
1.3
2
Document Purpose ................................................................................ 5
Background ........................................................................................... 5
Online Resources and Customer Service Centre ........................................ 5
Installation ........................................................................................... 6
2.1
Software Requirements .......................................................................... 6
2.2
2.3
Hardware Requirements for HMS 6.6.3 .................................................... 7
Upgrade Paths to HMS 6.6.3 ................................................................. 10
2.1.1
2.1.2
Software Requirements for HMS 6.6.3 Client ................................................... 6
Software Requirements for HUO .................................................................... 7
3
New Features ......................................................................................11
4
Resolved Issues ..................................................................................13
5
Known Issues......................................................................................16
Copyright  2012 HealthLink Limited
Page 4 of 16
HMS Client Version 6.6.3 | Release Notes
1
Version 1.0, 30 October 2012
Overview
1.1 Document Purpose
This document provides information for the 6.6.3 release of the HealthLink
Messaging System (HMS). This version of the document refers to build 6.6.3 of the
software.
1.2 Background
HMS is a messaging system which exchanges electronic messages between health
providers' computer systems. Using a common electronic message exchange system
means that health providers can quickly, easily and securely share information about
their patients.
HMS can be used by any health provider organisation with a capable computer
system. Many General Practices, Hospitals, Accident and Emergency Clinics and
specialist surgeries are reducing their paper workload right now thanks to HMS.
The electronic message is typically created within the provider’s clinical system and
sent to the recipient using their HealthLink EDI address. The recipient’s HealthLink
EDI account (mailbox) will store any messages addressed to their organisation. Using
HealthLink at their practice, the recipient will collect the messages and import them
into their clinical systems. The receiving clinical system will display all newly received
messages and sort them by individual recipient. The recipient can process the
message, and the information is securely stored on their clinical system.
1.3 Online Resources and Customer Service Centre
Comprehensive information about the HealthLink Messaging System can be found on
the HealthLink website: http://www.healthlink.net/resources.htm
This includes the following online resources:





Download of the installer for HMS 6.6.3
HMS 6.6.3 Installation and User Guide
Integration Guides for Clinical Software Applications
Directory of EDI Accounts
Remote Support Service
HMS 6.6.3 Licensing information is provided as part of the HealthLink Service
Agreement (http://www.healthlink.net/support.htm).
Additional support is available through HealthLink’s Customer Service Centre via free
phone (1800 125 036 in Australia; 0800 288 887 in New Zealand) or email
helpdesk@healthlink.net.
Copyright  2012 HealthLink Limited
Page 5 of 16
HMS Client Version 6.6.3 | Release Notes
2
Version 1.0, 30 October 2012
Installation
You can download the software installer from the HealthLink website
(http://www.healthlink.net/software.htm) or request an installation CD from
HealthLink Customer Service Centre. The installer can be used for new installations
of the HMS Client as well as for upgrading existing HMS Client installations to the
6.6.3 release.
For detailed installation instructions, please refer to the HMS 6.6.3 Installation and
User Guide (see the Online Resources and Customer Service Centre section of these
Release Notes).
2.1 Software Requirements
HMS 6.6.3 consists of two main applications, HMS 6.6.3 Client and HealthLink User
Online (HUO). Their supported software environments are described in the following
subsections.
2.1.1
Software Requirements for HMS 6.6.3 Client
Table 1 provides an overview of the software environments supported by the HMS
6.6.3 Client. The HMS 6.6.3 requires a software environment consisting of one of the
listed supported operating systems and a compatible runtime environment.
Operating System
Windows
XP,
2003 Server,
Vista (32 and 64 bit),
2008 Server (32 and 64 bit),
7 (32 and 64 bit),
2008 R2 Server,
8 (32 and 64 bit),
2012 Server
MacOS1
Runtime Environment
Java
2
10.6,10.7,10.8
1.6.0
Table 1: Software Requirements for HMS 6.6.3 Client
1
The HMS 6.6.3 Client features Quantum Synchronous Messaging, HealthLink Online (online forms) and HMS web
service interface are not supported for MacOS.
2
On non-MacOS machines, the HMS 6.6.3 Client installs its own copy of the Java Runtime Environment. This Java
Runtime Environment can only be used by the HMS 6.6.3 Client itself and does not interfere with any existing Java
installations (i.e. it neither uses nor modifies them). On MacOS machines, the HMS 6.6.3 Client relies on the
operating system’s automatic distribution mechanism to use the latest patch level of JRE 1.6.0.
Copyright  2012 HealthLink Limited
Page 6 of 16
HMS Client Version 6.6.3 | Release Notes
2.1.2
Version 1.0, 30 October 2012
Software Requirements for HUO
Table 2 provides an overview of the software environments supported by the
HealthLink User Online (HUO) application. HUO requires a software environment
consisting of one of the listed supported operating systems and a compatible web
browser.
Operating System
Windows
XP,
2003 Server,
Vista (32 and 64 bit),
2008 Server (32 and 64 bit),
7 (32 and 64 bit),
2008 R2 Server,
8 (32 and 64 bit),
2012 Server
Web Browser
Internet Explorer
6.x, 7.x, 8.x3, 9.x
Firefox
3.x
Table 2: Software Requirements for HUO
2.2 Hardware Requirements for HMS 6.6.3
The HMS Client provides two major areas of functionality:
1. Transfer of standard messages (e.g. Referrals) via a file drop interface. This
requires just the HMS client next to the EMR server.
2. HealthLink quantum web component services which include:
 Provision of web-services integration for message exchange with the EMR
 The online forms service which enables online form access to a web
browser (probably embedded in an EMR program).
Table 1 and Table 1provide an overview of the hardware requirements for running
the HMS 6.6.3 Client.
3
IE8 will be automatically set into IE7 compatibility mode. No user intervention required.
Copyright  2012 HealthLink Limited
Page 7 of 16
HMS Client Version 6.6.3 | Release Notes
Standard Messaging
(MINIMUM)
Standard
Messaging (RECOMMENDED)
Standard Messaging + Web
Services and/or
online Forms (MINIMUM)
Standard Messaging + Web
Services and/or online Forms
(RECOMMENDED)
Practitioner's
Workstation for rendering of
online Forms in Browser
(MINIMUM)
Practitioner's
Workstation for rendering of
online Forms in Browser
(MINIMUM)
Version 1.0, 30 October 2012
CPU
Intel Pentium IV 1.3GHz CPU
Memory
1 GB RAM
Disk
1 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 2 Mbit/s
downstream and 512 KBit/s upstream
CPU
Intel Core 2GHz CPU
Memory
2 GB RAM
Disk
2 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 2 Mbit/s
downstream and 512 KBit/s upstream
CPU
Intel 2GHz CPU
Memory
2 GB RAM
Disk
2 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 5 MBit/s
downstream and 1 MBit/s upstream
CPU
Intel Core 2 Duo 3GHz
Memory
2 GB RAM
Disk
5 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 5 MBit/s
downstream and 1 MBit/s upstream
CPU
Intel 2 GHz CPU
Memory
2 GB RAM
Resolution
1280*1024
Browser
Internet Explorer 6
CPU
Intel Dual Core 3GHz
Memory
3 GB RAM
Resolution
1680*1050
Browser
Internet Explorer 8
Table 3: Hardware Requirements for HMS 6.6.3 Client on Windows
Copyright  2012 HealthLink Limited
Page 8 of 16
HMS Client Version 6.6.3 | Release Notes
Standard Messaging
(MINIMUM)
Standard
Messaging (RECOMMENDED)
Version 1.0, 30 October 2012
CPU
G5 1.6GHz or Intel 1.6GHz CPU
Memory
1 GB RAM
Disk
1 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 2 Mbit/s
downstream and 512 KBit/s upstream
CPU
G5 2GHz or Intel 2GHz CPU
Memory
1 GB RAM
Disk
1 GB Harddisk (available for HMS)
Resolution
1024*768
Network
Network card for broadband access (wireless or
LAN)
Broadband internet access (at least 2 Mbit/s
downstream and 512 KBit/s upstream
Table 4: Hardware Requirements for HMS 6.6.3 Client on Mac OSX
Copyright  2012 HealthLink Limited
Page 9 of 16
HMS Client Version 6.6.3 | Release Notes
Version 1.0, 30 October 2012
2.3 Upgrade Paths to HMS 6.6.3
The supported upgrade paths are listed in Table 5.
Before uninstalling your existing installation of the HMS Client, please ensure that
your system is meeting the software requirements of the HMS 6.6.3 Client (see
section 2.1.1 for details).
Previous
HMS
Version
Upgrade
Type
Windows
Mac OS
6.5.1
Manual
Please uninstall your existing HMS version and subsequently install HMS
6.6.3 as a new installation.
Please contact the HealthLink Customer Service Centre for assistance.
Remote
Not supported
6.5.2 to
6.5.3
Manual
Manual upgrades using the HMS 6.6.3 installer are supported.
Remote
Can be performed on request or
automatically
6.5.5
Manual
Manual upgrades using the HMS 6.6.3 installer are supported.
Remote
Can be performed on request or
automatically.
Manual
Manual upgrades using the HMS 6.6.3 installer are supported.
Remote
Can be performed on request or automatically.
6.5.6 to
6.6.2
Not supported
Not supported
Table 5: Supported Upgrade Paths
Copyright  2012 HealthLink Limited
Page 10 of 16
HMS Client Version 6.6.3 | Release Notes
3
Version 1.0, 30 October 2012
New Features
The following table provides an overview of the main feature set improvements
introduced with HMS 6.6.3.
1
Feature Description
JIRA
Issue ID
Support Australia Standard ATS 5822-2010 E-health Secure Message
Delivery (SMD) and TR 5823-2010 Endpoint Location Service (ELS)
HMS-1076
The HMS Client now can send and receive messages from Australia Standard SMD web
services with internal or external ELS web service lookup.
2
3
4
HMS-1083
New Australia NEHTA HL7v2 MDM message type
HMS-1099
The HMS Client now can deliver HL7 CDA document wrapped in HL7v2 MDM message
using SMD web services or HealthLink Secure Messaging. MDM message can either be
delivered in its own folder “MDM01AU” or shared with “LAB2” folder. By default
installation, MDM message is configured to use shared “LAB2” folder. This can be
changed to use its own folder “MDM01AU” from the HMS Advanced Options after the
installation.
HMS-1090
Canadian Installation
HMS-1039
Previously, the HMS Client Installer only supports New Zealand and Australia
installation. To install HMS client in Canada, it has to be installed as New Zealand
installation and also an automatic update is sent out to migrate the sites to the
Canadian installation. Now the HMS Client installer supports Canadian installation and
HealthDocs e-MS Message type is included in the default setup.
HMS-1013
Forms Director Supporting form submission as HMS message
HMS-375
HMS-1091
Forms are now able to be submitted asynchronously from Forms Director to HMS
Message Exchange Web service as HMS message.
5
Support unbalanced HMS Web Service
HMS-1144
Previously, to enable HMS Message Exchange Web Service in HMS Client for a
message type, the EMR/PMS integration for both the incoming and outgoing message
needs to be through web service interface. Now it is possible to configure only one
way (e.g. outgoing message) to be through web service interface and the other way
(e.g. incoming) to be through file based interface.
6
Add Authentication to HMS Web Service
HMS-1145
Previously, to send a message from HMS Web Service, it requires the sender’s
HealthLink EDI account to be configured as service auto logon account with
connection password from the HMS Advanced Option. Now the authentication login
information can be embedded in HTTP header as part of HMS Web Service HTTP SOAP
request.
7
Remotely Enforced Certificate Reissuing
HMS-1025
Previously, certificate used for message encryption or signing is only get automatically
reissued when it is about to expire (28 days before expiry date). Now certificate can
be reissued on demand trigged remotely from the HealthLink Global Profile Server
(GPS).
8
Remotely Trigged HMS Client Service restart
HMS-1114
When HMS Client is running on NT Service mode, the NT Service restart can now be
trigged remotely from the HealthLink Global Profile Server (GPS).
Copyright  2012 HealthLink Limited
Page 11 of 16
HMS Client Version 6.6.3 | Release Notes
9
Version 1.0, 30 October 2012
Feature Description
JIRA
Issue ID
Generation of Negative Acknowledgement for invalid outgoing Generic XML
Messages
HMS-1020
In the past, HMS supports negative acknowledgement generation for invalid outgoing
HL7 and HealthDocs messages, and any invalid incoming structured messages
including HL7, HealthDocs, FlatFile and Generic XML messages (e.g. HealthDocs e-MS
Message and DIABETIES2). Now the negative acknowledgement generation has been
extended for invalid outgoing Generic XML messages as well.
The negative acknowledgement messages can only be generated if the message
header information for the original message could be parsed successfully.
Consequently, for messages containing a malformed message header or messages
that could not be accessed (e.g. because of exceeded file size limitations or insufficient
access permissions by the HMS Client), no negative acknowledgement message is
generated. Note that this constraint is only limited to the generation of negative
acknowledgements and does not apply to the remaining error handling mechanisms.
10
Filename extension enhancement
HMS-1123
Some EMR software e.g. MD3 is relying on message filename extension for its
incoming message processing. But messages from some interchange e.g. SMD/SMX
clouds may not have filename and its extension information. Previously HMs Client will
deliver these messages in the incoming folder with a derived filename of
“(<sender>)<timestamp>” without an extension. Now a special configuration can be
added to the User settings of HMS Client to indicate the incoming and outgoing
filename extension e.g. “.hl7” if the filename extension is missing, so messages can be
processed by EMR software. This special setting is not included in the default
installation and can be automatically deployed to the sites on request.
11
Filename length restriction enhancement
HMS-1081
To prevent message successfully sending but then failing to download due to the fact
that the file path length exceeds the operating system limit or some EMR software
may not be able to open file with too long file name like notepad++ does, HMS Client
restricts any message with filename length greater than 80 to be sent. There is an
ongoing demand for increasing this length limit as the operating systems may increase
its path/filename length limit already or in the future.
Now the filename length and the full file path (including filename) length limits are
configurable from HMS Client. These new settings are not available for modification
from the default installation. To prevent messages from being blocked from receiving
due to a message with over length filename in the HMS Messaging Server for existing
HMS Clients, these two new settings are still using existing limit values i.e. 80 for
filename and 255 for full file path. When all the existing HMS Clients are upgraded to
version 6.6.3 and above, HealthLink will send out an update automatically to readjust
these two settings.
Copyright  2012 HealthLink Limited
Page 12 of 16
HMS Client Version 6.6.3 | Release Notes
4
Version 1.0, 30 October 2012
Resolved Issues
The following table provides an overview of the most important issue resolutions.
1
Issue Description
JIRA
Issue ID
Memory Leak in HealthLink System Tray Icon under Windows XP
HMS-1031
The memory usage of the HealthLink System Tray is slowly but steadily climbing
when running HMS Client on Windows XP platform.
Now HealthLink System Tray application has been modified to use standard java6
system tray library. ‘Memory Usage’ does not seem to increase indefinitely in
Windows Task Manager, and the heap size usage reported from HMS java process is
stable as well. However ‘VM Size’ shown in Windows Task Manager still continues to
grow over time.
2
Advanced Options closes itself when going to “Configuration>User
Settings”
HMS-970
HMS-1063
When running Advanced Options on Windows 7 with visual themes enabled,
sometimes Advanced Options closes itself when attempting to go to “Configuration>User Settings”.
This issue has been addressed In this release.
3
Remove Upward OS Restriction from HMS Installer
HMS-986
The Installer of HMS Client will now no longer reject installation on any operating
system which version is above its explicitly supported range of versions. Instead, a
warning message is displayed to user when trying to install the HMS Client on the
operating system which is currently unsupported.
4
HealthLink System Tray Icon not showing after remote Silent Mode
upgrade
HMS-927
When running HMS Client as NT Service mode, the HealthLink System Tray Icon is
not showing after remote silent mode upgrade under windows XP, 2003 server,
Vista 64 bits and 2008 server 64 bits platforms.
HMS-983
HMS-980
The Silent Mode Installer has been modified to fix this issue in this release.
5
Negative Acknowledgement generation failure for some HL7 messages
When an originating HL7 messages contains an invalid field which is a sub
component of a composite HL7 filed e.g.
“OBR/SpecimenSource/SpecimenSourceNameOrCode/Identifier”, HMS Client will fail
to create corresponding negative acknowledgement and just simply move the
message into the rejected folder.
HMS-1110
This issue has been rectified in this release
6
Zombie Connection Detection
HMS-1151
In the previous releases, HMS Client may hang forever on a zombie connection
made to the HMS Messaging Server when trying to send or receive message during
a network outage.
A zombie connection timeout setting has been introduced in this release to rectify
this issue.
Copyright  2012 HealthLink Limited
Page 13 of 16
HMS Client Version 6.6.3 | Release Notes
7
Version 1.0, 30 October 2012
Issue Description
JIRA
Issue ID
HMS Client connection failure when checking settings update
HMS-1148
HMS Client will check and update its settings from the HMS Profile server before
attempting a scheduled or manually triggered messaging session for message
delivery. If for some reason, the HMS Profile server is not available, HMS Client will
stop to make the messaging session for message delivery.
Now, HMs Client will continue the messaging session even if the HMS Profile Server
is not available.
8
Show warning message when there is no user logged on under interactive
mode
HMS-1152
In the previous releases, when a user manually launches HMS Client Application and
leaves the HMS Client screen unattended, the main screen of HMS Client displays
message with “starting HMS <version> in unattended mode... done” after one
minute login timeout. This makes user think there is no issue with login.
Now instead of displaying message with “starting HMS <version> in unattended
mode... done” after login timeout, warning messages in red colour with “starting
HMS <version> in unattended mode... done” and “Login was not successful, please
login.” are displayed.
9
Restoring “Security Backup” from HMS Advanced Option comes up with an
error
HMS-1170
When clicks “Restore” button from “HMS Advanced Option>Configuration>Global
Settings>Security Backup”, an error message is popped up with “Unable to restore
security backup: ...” after choosing the backup copy to restore.
This issue has now been rectified in this release.
10
“Save As Default” and “Reset Default” functions freeze “Message Types”
list box from HMS Advanced Option
HMS-1160
This issue has now been rectified in this release.
11
Australia HL7v2 RSD message validation change: HL7 table 0203 new
value ‘SN’
HMS-1157
A new value ‘SN” is now added to Australia HL7 v2 RSD validation table 0203 that
applies to PID-3.5 PatientIdentifierList/TypeCode field to support Medicare Safetynet
card numbers in PID-3.5 field.
12
Australia HL7v2 LAB Acknowledgement with ‘AUSNATA’ in MSH-4.3
'UniversalIDType' or MSH-6.3 'UniversalIDType' is rejected by HMS Client
HMS-1185
HMS Client rejects Australia HL7v2 LAB2 acknowledgement which has value
‘AUSNATA’ in MSH-4.3 'UniversalIDType' or MSH-6.3 'UniversalIDType'. ‘AUSNATA’ is
a valid value for 'UniversalIDType' in Australia. This bug only exists in HMS
6.6.2.2522 (R4) and above.
This issue has now been rectified in this release.
Copyright  2012 HealthLink Limited
Page 14 of 16
HMS Client Version 6.6.3 | Release Notes
13
Version 1.0, 30 October 2012
Issue Description
JIRA
Issue ID
Australian HL7v2.3 LAB Message with OBR-3 field more than 75
characters long is rejected by HMS Client
HMS-1196
Australian Lab2.3 Messages with OBR-3 field more than 75 characters long is failing
message validation in HMS clients.
Australian HL7 2.3.1 message specification for Pathology Orders and Results (AS
4700.2-2004 ImplementationofHealthLevelSeven-HL7-Version2.3.1Pathologyordersandresults) has extended the character length for OBR-2 (placer
order number) and OBR-3 (Filler order number) to 250. The subsequent AU
Standard AS 4700.2-2007 has also extended ORC-2 (placer order number) ORC-3
(Filler Order number) and ORC-4 (Placer Group Number) to 250.
This issue will not affect Australian HL7v2.4 LAB Message.
Now the following fields have all been updated to the same field length of 250
characters in this release:
OBR-2, OBR-3, ORC-2, ORC-3 and ORC-4.
14
UniversalIDs Not Supported in Negative Acknowledgement for Generic
XML Messages
HMS-1022
The generation of negative acknowledgement for generic XML messages fails if the
sending or receiving facility fields of the original message contains the optional
UniversalId and/or UniversalIdType components.
This issue has now been rectified in this release.
15
The file path separator changed from “\” to “/” for additional EDI
Account(s) in HMS interface file “hms_config.xml”
HMS-1149
When adding a second EDI to HMS installation from HMS Advanced Options, the file
path separator changed from "\" to "/" for the second EDI in HMS interface file
"hms_config.xml". This may cause issue for some EMR software when it tries to
read HMS interface file e.g. Genesis currently can't load the second EDI from HMS
interface file.
Now the file path separator will always be obtained from the operation system which
HMS Advanced Option is running on. E.g. “\” for Windows and “/” for Mac OSX.
16
HMS interface file “hms_config.xml” sometimes may corrupt when
uploading the configuration setting change(s) to HMS backend server
HMS-1203
This bug was only reported for HMS Client which is running on Mac OSX platforms.
This prevents the EMR software e.g. Genesis and Medical Director from using the
interface file ‘hms_config.xml” for automatically message delivery integration and
may also affects HealthLink Online Forms deployment in the future.
This issue has now been rectified in this release.
Copyright  2012 HealthLink Limited
Page 15 of 16
HMS Client Version 6.6.3 | Release Notes
5
1
Version 1.0, 30 October 2012
Known Issues
Issue Description
JIRA Issue
ID
HMS 6.6.3 does not support Mac OSX version 10.5 and below
HMS-1139
HMS 6.6.3 can only be installed and running on Mac OSX which supports java 6. Mac
OSX 10.5 and below does not support java 6 and therefore it is not supported by this
release.
64-bit Intel Mac OSX 10.5 supports java 6, but this has not been tested in this
release.
2
Requires manual java installation on Mac OSX version 10.7 and above
HMS-1066
On Mac OSX 10.7, Java is not installed by default as part of OS installation. So
during HMS Client installation, user is prompted to install java. This also happens
when launching HMS applications e.g. HMS Client and Advanced Options after the
Mac OSX is upgraded to 10.7 with an already installed HMS Client.
3
Latest Windows OSs Reporting Issue
HMS-1132
HMS 6.6.3 reports Windows 7 as “Windows Vista (6.1)”, Windows 8 as “Windows
Vista (6.2)” and Windows Server 2012 as “Windows Server 2008 (6.2)” in its
configuration file “system.profile”. This is caused by the version of java 6 bundled
with HMS 6.6.3 client (i.e. JRE6_06) which does not recognise the latest Windows
platforms.
4
HMS Advanced Options Log File Printer does not print
HMS-1181
Opens HMS Advanced Options>Utilities>Log File Printer, select one of the log files,
click ‘print’ button, nothing is print from the printer after checking the printer setting.
5
HMS Advanced Options File menu ‘Save All’ does not save details
HMS-1179
If running HMS Advanced Options with “HealthLink” menu enabled (i.e. with
internal.jar deployed), "Save" or "Save All" sometimes does not save change(s) if
“Profile File Editor” is opened with conjunction of other menus.
“Profile File Editor” under “HealthLink” menu is not designed to synchronise the
setting changes with other menus, So user should always try to avoid to open
“Profile File Editor” if want to make change(s) from other Advanced Option menus.
This behaviour exists in all the versions of HMS Advanced Options.
6
HMS Advanced Options “Logs” setting does not refresh properly after
“Save All” menu is clicked
HMS-1140
Opens HMS Advanced Options, changes some setting(s) and navigates to “Global
Settings>Logs” tab, select one of the log type e.g. “debug log”, then goes to File
menu “Save All”. After saving, the values of log settings i.e. "Log file", "Log
Direction" and "Log Backups" always use the values for “event log” type and does
not match with the values for the current selected log type. The workaround is to
reselect other log type, it will then display properly.
Copyright  2012 HealthLink Limited
Page 16 of 16