skip to main content

TELUS Health Solutions

Certified EMR Offerings

Please note: the information provided below is for research purposes only. EMR Advisor strongly suggests you use this in conjunction with other information sources (e.g. discussions with your peers), and perform a proper RFI (Request for Information) from vendor organizations you wish to consider for your CMS/EMR selection.

This section provides information about the CMS vendor.

NOTE: The information below has been provided by the CMS vendor.


Version Number

Med Access EMR v4.3

User Interface

Windows Vista, Internet Explorer 8

Local/ASP

Local

Provided Documentation and Media Used

Production documentation is available within the EMR product via online context sensitive help.

Detailed release note documentation is also provided online with every product update.

Other Required Environmental and Support Components

Other requirement components for typical medical office environments include:

  • Printer
  • Scanner
  • Health card reader

Health Card Validation Support (OBEC)

OBEC is fully supported

What other tools and utilities (e.g. Systems Management, Monitoring, Backup, Audit Logging etc.) are required to implement the EMR on the server?

All required tools and utilities are provided by Med Access in the standard solution offering including:

  • Performance and availability monitoring
  • Onsite and offsite backup and recovery
  • Comprehensive audit logging accessible by authorized end users

What other software products do you advise physicians to implement?

Antivirus software is advised for clients who choose to use Windows based workstations.

What other software products are compatible with your EMR (e.g. Office suites, accounting, research, analysis, etc.)?

Compatible browsers include:

  • Internet Explorer
  • Safari
  • Firefox
  • Chrome
  • Compatible office suites include:
  • Macintosh office suite
  • Microsoft office suite
  • Open office suite

Additional compatible software includes:

  • Dragon Dictate voice recognition software

Does your Offering support out-of-province billing? If so, please specify.

Yes

Specify third party interfaces your Offering supports (e.g. laboratories, pharmacies, hospitals, MOHLTC).

Supported third party interfaces include:

  • OLIS (Lab results)
  • HRM (Diagnostic Imaging Reports)
  • MOHLTC (Billing)
  • Gamma Dynacare (Lab results)
  • AlphaLabs (Lab results)
  • CML Healthcare (Lab results)

Provide a comprehensive list of the out-of-box forms of templates included in your EMR Offering (e.g., SOAP, Annual physical, ante-natal).

Med Access offers an extensive library of predefined WYSIWYG forms and templates (over 1,000) covering needs in 5 provinces. We are adding regionally-relevant forms and templates every day and also provide user development tools and host a user exchange.

Does your EMR operate in both official Ontario languages (e.g. screens, online help, reports)?

Med Access EMR currently supports English only.

Describe your approach to supporting patients with multiple different language needs.

Data can be recorded in the EMR in any language supported by the local operating system.

Templates and lookup lists can be configured by end users with choices based on the chosen language

Patient's preferred language can be recorded in the database for reference.

Describe your approach to supporting physicians with multiple different language needs.

Data can be recorded in the EMR in any language supported by the local operating system.

What is the name of the data supplier to support prescription writing and drug interactions?

First DataBank

What is the frequency of updates to the data provided to your clients?

Updates are provided monthly.

Describe the process for applying updates to the data (e.g. CD-ROM, remote download, etc).

Updates are remotely broadcast and installed on all client servers automatically each month.

Does your product support structured coding for problems? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • ICD9
  • SNOMED

Does your product support structured coding for interventions? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • ICD9
  • SNOMED

Does your product support structured coding for symptoms? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • ICPC

Does your product support structured coding for allergies? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • First DataBank

Does your product support structured coding for adverse reactions? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • First DataBank

Does your product support structured coding for immunizations? If so, provide the name(s) and version(s) supported.

Yes. Supported coding systems include:

  • First DataBank

Identify other coded data elements and their schemes where appropriate in the response sheets.

Other coded data elements include:

  • Lab results - LOINC

Describe the recommended hardware configuration required to run your solution for the following scenario: Single physician office; 2 support staff; 2 exam rooms. Include any assumptions that you are making.

Single Server - Dual Processor including 32GB of Ram, mirrored Hard Drives (1TB) with Raid Controller, DVD-RW Optical Drive, dual power supplies, and covered with a 3 Year NBD Onsite Warranty. The server runs Linux Centos 5.5 or higher, there is no licensing cost for the Server Operating System nor the Database Management System. As the system is accessible through a browser there is also no requirement for any client software licensing and all that is needed is an approved browser to access the EMR. There is also no requirement for a monitor, Keyboard / Mouse setup for the server as it is managed and monitored remotely.

Office Workstations:

5 Workstations - Our standard recommendation is an i5 Processor including 4GB of Ram, 250GB Hard Drive, DVD-RW Optical Drive, 19-22" Monitor, Windows 7 Pro 64Bit, 3 Year NBD Onsite Support.

Assumptions: A workstation can either be a Mac / Windows / Linux - Laptop or workstation. As long as the workstation can run one of the approved browsers, then the base operating system of the workstation can be any of the aforementioned.

Describe the recommended hardware configuration required to run your solution for the following scenario: 8 physician FHN; 4 different geographic locations (physician offices), each with 2 physicians; 3 support staff per physician office; 4 exam rooms per physician office. Include any assumptions that you are making.

Single server - Dual Processor including 32GB of Ram, mirrored Hard Drives (1TB) with Raid Controller, DVD-RW Optical Drive, dual power supplies, and covered with a 3Year NBD Onsite Warranty. The server runs Linux Centos 5.5 or higher, there is no licensing cost at all for the Server Operating System nor the Database Management System. As the system is accessible through a browser there is also no requirement for any client software licensing, all you need is an approved browser to access the EMR. There is also no requirement for a monitor, Keyboard / Mouse setup for the server as it is managed and monitored remotely.

We only require the server to be deployed in one of the 4 locations. The other locations would connect to the server using one of the approved browsers over an HTTPS connection. As an additional security measure we can also setup dedicated VPN tunnels for the HTTPS connection to be carried over.

Each Satellite Office would have:

8 Workstations - Our standard recommendation is an i5 Processor including 4GB of Ram, 250GB Hard Drive, DVD-RW Optical Drive, 19-22" Monitor. Windows 7 Pro 64Bit. 3 Year NBD Onsite Support.

Assumptions: A workstation can either be a Mac / Windows / Linux - Laptop or workstation. As long as the workstation can run one of the approved browsers, the base operating system of the workstation can be any of the aforementioned.

Describe the recommended hardware configuration required to run your solution for the following scenario: 10 physician FHN all located in 1 clinic (physician office); 10 support staff; 20 exam rooms. Include any assumptions that you are making.

Single server - Dual Processor including 16GB of Ram, mirrored Hard Drives (1TB) with Raid Controller, DVD-RW Optical Drive, dual power supplies, and covered with a 3 Year NBD Onsite Warranty. The server runs Linux Centos 5.5 or higher. There is no licensing cost for the Server Operating System nor the Database Management System. As the system is accessible through a browser there is also no requirement for any client software licensing. All that is needed is an approved browser to access the EMR. There is also no requirement for a monitor, Keyboard / Mouse setup for the server as it is managed and monitored remotely

Office Workstations:

40 Workstations - Our standard recommendation is an i5 Processor including 4GB of Ram, 250GB Hard Drive, DVD-RW Optical Drive, 19-22" Monitor, Windows 7 Pro 64Bit, 3 Year NBD Onsite Support.

Assumptions: A workstation can either be a Mac / Windows / Linux - Laptop or Workstation. For this size of clinic, we also offer a Sunray Thin Client option which allows for easy movement from Exam Room to Physicians office while maintaining sessions. The Thin Client options can be discussed for sites looking for a unique solution to running a larger clinic.

Describe the recommended bandwidth requirements required to run your solution for the following scenarios: Configuration 1; Configuration 2; ASP Requirements. Requirements should be broken down by upload bandwidth/user and download bandwidth/user.

As we do not require a client server interaction but just need a web browser to connect to the local server our bandwidth needs are very small. Currently we see an average user over the course of a normal working day using less then 32kbps of download bandwidth in order to operate. We recommend a business class Cable Modem or DSL equivalent connection for each site.

Configuration #1: As we only require a standard HTTP connection to allow access for either data sharing or remote offices we only require 16kbps upload and 32kbps download per user in order to serve users connecting to the local server outside of the local office.

Configuration #2: A single server in an office accepting connections from a remote office would require approximately 16 kbps of bandwidth upload and 32 kbps download per user.

Do you provide remote server management capabilities? Please list functions provided.

The server is 100% remotely manageable through the standard Med Access offering.

We provide functions such as, monitoring, maintenance, account administration, server OS Updates, Product updates, backups and replication.

Describe how system data is recovered after a system (hard drive) failure. E.g. to the point of failure, last backup, or other.

We use a Mirrored RAID System preventing any data loss if only one drive were to fail. Data loss would only occur if more than one drive failed simultaneously. In the unlikely event that the server failed there are options for point in time backups, onsite and offsite. There are options for redundant HW to be available onsite as well as per the service offering options above.

We have the ability to perform one or many of the following: Pure replication either onsite or offsite, Backup to disk either onsite or offsite, Failover to secondary server either onsite or offsite.

Do you provide tools to manage the availability of EMR systems? Describe functions.

We have the tools available to manage the availability of the EMR System. These tools are available to both actively and proactively manage the EMR System and the Local Server. It covers functions such as disk performance, CPU, load, and memory management. It can be extended to monitor internal and externel networks. In the case of a local server it also manages the services running on the system to keep the web server and database subsytems working at peak performance.

Do you provide real-time server monitoring with alerts sent to yourselves or to clients?

We have a complete monitoring program that manages many aspects of the servers health. Alerts are sent to support and the IT Team. No alerts are sent to the client through this system.

Other information about EMR offerings:

The following information is provided to assist you:

  • Approved Local EMR Configurations
    Ontario's eHealth strategy includes the use of specific configurations designed to meet Electronic Medical Record (EMR) and eHealth connectivity needs in Physician offices.
  • For more information, please call / email OntarioMD at 1-866-744-8668, emr@ontariomd.com.