DatamedFT™ and DatamedRcv™ Applications should be installed by a user with Administrative privileges on the host computer. While no files are added to system folders, registry entries are added to initiate theDatamedFT™ and Accessory programs which run as system level services at computer startup. Administrative access at installation ensures proper privilege is applied.

When installing DatamedFT™ for ECG acquisition over a local or enterprise network, ensure that proper privilege and security is enabled for all transmitting and receiving devices to inbound and outbound network shares defined for both the DatamedFT™ system and host ECG Management System.

If DatamedFT™ is writing output files across the network to a separate ECG Management system, ensure that the DatamedFT™ service is enabled as a user with appropriate privilege to write to the destination folder. This can either be a domain account or a duplicated local account. The default setting for a new service is to run as the local system account, which does not have network access.

In larger domain controlled networks with the DatamedFT™ application centrally located, well-intended security across subnets can create unintended results for remote networked acquisition devices.

Mapped drive letters should not be used when defining destination network shares for the Datamed™ applications. Mapped drives are not accessible to applications running as services. As a matter of practice, UNC style network paths should be used for all network mapping.

Hardware Security Keys or HASP keys, commonly known as “dongles” are required to be installed into any USB port on the computer on which the DatamedFT™ or DatamedRcv™ applications are to be installed. Installing the HASP key is easy, but often over complicated. On Windows based machines, NO drivers need to be installed as long as the computer has Internet access. Drivers are automatically downloaded from the Microsoft Update site. If the computer does NOT have Internet access, then drivers are available on the installation CDs, on the HASP Page on this website. The HASP key is enabled when the red LED lights.

The DatamedRcv™ DRCV01 Module also requires a hardware security key or HASP. If the DatamedRcv™ DRCV01 is an add-on to an existing DatamedFT™ setup, the HASP key must be updated with theDatamedRcv™ DRCV01 license. Instructions for updating the HASP key are available in the DatamedRcv™ DRCV01 Module Users Manual or on the HASP Page on this website. If the DatamedRcv™ DRCV01 Module is installed on a separate machine than the DatamedFT™ host, a separate HASP key is required and must be installed prior to setting up the DatamedRcv™ DRCV01 application. If the machine has an Internet connection, just plug the HASP key into any available USB port and drivers will be downloaded from Microsoft.

All Datamed® applications makes entries to the operating system’s application event log for informational, advisory and critical events. If problems occur in these applications, consult the Applications Event log under Administrative Tools. Beyond the information in the log entry, within each event log’s description is a web based URL link to the DATAMED.COM web site that provides additional information on the event, it’s critical, cause and possible resolutions if applicable.