skip to main content

AbelMed Inc.

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

ABELMed EHR - EMR / PM v12

User Interface

Microsoft Windows XP, Vista, 7 and 8

Local/ASP

Local

Provided Documentation and Media Used

Each ABELMed EHR - EMR / PM v12 product comes with complete installation instructions, program change notes/release notes as well as the following electronic documentation:

  • Electronic PDF copy of ABELMed EHR - EMR / PM v12 Users Guide (a printed copy can be ordered at a cost)
  • Electronic PDF copy of ABELMed EHR - EMR / PM v12 Tutorial Guide
  • Each ABELMed EHR - EMR / PM v12 also includes an integrated context sensitive Help feature.

Other Required Environmental and Support Components

Users will derive maximum benefit from the software by taking advantage of our training and maintenance programs.

  • Hardware that meets or exceeds the recommeded specifications as detailed on our website www.ABELMed.com
  • An Internet connection is recommended to faciliate remote access to the EMR and Remote support.

Health Card Validation Support (OBEC)

ABELMed EHR - EMR / PM v12 supports Overnight Batch Eligibility Checking. This feature seamlessly integrates with ABELMed's appointment scheduler and leverages the office's existing EDT connection with the MoH.

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

Database management software (SQL Server) is required and is typically bundled with the application.

Microsoft Word is also required (1 license per physician minimum).

TrueCrypt 7 is required for disk encryption.

Remote-Scan software is required to scan from scanners connected through thin client (RDS)computers.

ABELMed utilizes features of our recommended operating systems, including handwriting recognition, as well as utilities included with ABELMed for system management. Hardware/operating system vendor(s) may recommend alternative or additional products to ease or enhance administration of the platform. Such software may include backup software, auditing software, communication software for remote support, etc.

What other software products do you advise physicians to implement?

Although no other software is required to implement or operate ABELMed EHR - EMR / PM v12, current Antivirus software is a practical necessity for any computer.

Event Log Management Suites such as those offered by Ipswitch (Formerly by Dorian Software) can automate the operating system's event log maintenance. Microsoft Office Suite would enhance some ABELMed features.

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

Microsoft Word 2013 / 2010 / 2007 and MS Access 2010 /2007 are compatible with ABELMed EHR - EMR / PM v12.

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

No.

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

ABELMed EHR - EMR / PM v12 has the following interfaces with third party software to help physicians streamline their practice: 1. Interfaces with Life Labs, Gamma Dynacare Labs and CML and MedHealth Laboratories. 2. Prosolve - an interface for Cardiology offices. We are capable of interfacing with most, if not all third party software.

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

Several out of box templates are included in our EMR Offering. Standard SOAP, annual physical, chronic disease management flowsheets e.g. Diabetes care, smoking cessation, Hamilton D depression scale, heart failure patient follow up, common encounters templates e.g. sore throat, antenatal records etc.

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

ABELMed EHR - EMR / PM v12 is currently available in English only. ABELMed has experience in developing French language applications for our dental customers. This experience can be leveraged in developing a similar version of ABELMed EHR - EMR / PM v12 in the French language.

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

ABELMed is prepared to develop patient statements/receipts for languages other than English, with assistance from the user who requests such a feature.

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

Currently, support for the ABELMed EHR - EMR / PM v12 application is in English only. However, several ABELSoft support personnel speak French and support ABELDent's French version. Our experience in supporting French-language customers puts us in a good position to extend such support to ABELMed EHR - EMR / PM v12 customers if the need arises.

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

First DataBank, Inc.

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

Updates that are made available by First DataBank are provided to clients on a monthly basis.

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

When applying an update on the drug reference data, ABELMed mails CD-ROMs to all eligible customers. (An eligible customer is one who is using First DataBank, Inc.'s drug reference data with ABELMed EHR - EMR / PM v12.) The CD-ROM may contain a First DataBank, Inc. update only or may also include an ABELMed EHR - EMR / PM v12 update (if one is available at the time). The CD-ROM contains an installation program that the customer must execute to apply the update.

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

ABELMed EHR - EMR / PM v12 supports ICD9-CA, ICD9, ICD10, SNOMED-CT coding. Users can customize the diagnosis list as required. The system can also accommodate ICD 10 and other specialized codes that the users may require.

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

Yes, medications are coded using both the DIN and FDB ID using First DataBank, Inc.'s Drug Information Framework (v.3.0.2) and International Drug Data File™—Canada (IDDF-CA). Procedures can be coded using the OHIP Schedule of Benefit codes and/or SNOMED-CT.

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

Yes. ABELMed EHR - EMR / PM v12 allows the user to create clinical findings templates which can be coded with  ICD9-CA, ICD9, ICD10., SNOMED-CT. These templates can be used to custom build vocabularies and list findings.

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

Yes, ABELMed EHR - EMR / PM v12 supports structured coding for allergies to drugs. Drug allergies are coded using both the DIN and FDB ID found in First DataBank, Inc.'s Drug Information Framework (v.3.0.2) and International Drug Data File™—Canada (IDDF-CA).

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

Yes, ABELMed EHR - EMR / PM v12 supports structured coding for adverse reactions to drugs. Such adverse reactions are coded using both the DIN and FDB ID found in First DataBank, Inc.'s Drug Information Framework (v.3.0.2) and International Drug Data File™—Canada (IDDF-CA).

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

Yes, ABELMed EHR - EMR / PM v12 supports structured coding for immunizations. Immunizations are coded using both the DIN and FDB ID found in First DataBank, Inc.'s Drug Information Framework (v.3.0.2) and International Drug Data File™—Canada (IDDF-CA).

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

Medications are coded using both the DIN and FDB ID found in First DataBank, Inc.'s Drug Information Framework (v.3.0.2) and International Drug Data File™—Canada (IDDF-CA). In addition, ABELMed EHR - EMR / PM v12 maintains various codified lists e.g. user defined medications.

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.

Specific recommendations can vary greatly depending on user preference for computer types (desktops, notebooks, tablets etc.). Individual office workflows can affect decisions on peripherals too. This proposal is a sample that assumes fixed desktops in all offices and exam rooms, and a minimum of peripherals; more peripherals can certainly be added. In general, mobile workstations can reduce the required number of computers.

PCs in both exam rooms, reception, doctor's office.

EMR local configuration 1

  • Entry Level Server (Database/File/Printer/RDS Server - Windows Server 2012, Intel E3-1240V2 3.4 GHz, 8GB, 2 x 500GB SATA HD, 19" SVGA, 1Gbps NIC, DVD (RW), floppy, 4x RDS CALs
  • UPS 1500VA
  • 4 x Workstation - Windows 8 Pro, Core i5-2400 3.1GHz, 4GB ,120GB HD, 19" SVGA, 1Gbps NIC, DVD (RW)
  • 8 Port Switch (1Gbps)
  • Router/Firewall/VPN appliance
  • Additional UPS 600VA for communication equipment (firewall, switch etc.)
  • Card Reader
  • External modem
  • Scanner and Remote-Scan software
  • Laser Printer
  • Label Printer (USB with cable)
  • 5 x AntiVirus
  • MS Office Professional 2010/2013 (1 minimum)
  • 5 ABELMed w SQL Server 2008R2 Standard Edition RUNTIME licenses.
  • Network cabling for 5 drops if required
  • 5-9 external USB Hard disks (1 TB) or Remote Backup Service.

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.

Specific recommendations can vary greatly depending on user preference for computer types (desktops, notebooks, tablets etc.). Individual office workflows can affect decisions on peripherals too. This proposal is a sample that assumes fixed desktops in all offices and exam rooms, and a minimum of peripherals; more peripherals can certainly be added. In general, it is expected that some mobile workstations will be used and that will reduce the required number of computers.

PCs in all exam rooms, reception, doctor's office

EMR local configuration 2

  • Database/File/Printer Server - Windows Server 2012 – Intel E3-1240V2 3.4 GHz, 32GB RAM, 2x 1 TB HD, 19" SVGA, 1Gbps NIC, DVD (RW), floppy
  • Application Server - Windows Server 2012 – Intel E3-1240V2 3.4 GHz, 32GB RAM, 2x250GB HD, 19" SVGA, 1Gbps NIC, DVD (RW), floppy and modem
  • 2 X UPS 1500VA
  • 28 x Workstation - Windows 8 Pro, Core i5-2400 3.1GHz, 4GB ,120GB HD, 19" SVGA, 1Gbps NIC, DVD (RW)
  • 4 x 12 Port 1 GB Switch
  • 4 x Router/Firewall/VPN appliance
  • 4 x 600VA UPS (for Firewalls and switches)
  • 4 x Card Reader
  • External Modem
  • 4 x Scanner + 4x Remote-Scan
  • 4 x Laser Printer
  • 4 x Label Printer (USB with cable)
  • 28 x Windows 2008R2 Server CALS (client access lic.)
  • 28 x Windows 2008R2 RDS CALS (client access lic.)
  • 30 x AntiVirus
  • MS Office Professional 2010 / 2013 licenses (minimum 8 -1 per physician)
  • 30 ABELMed w SQL Server 2008R2 Standard Edition RUNTIME licenses.
  • Network cabling for 30 drops if required
  • 5-9 external USB Hard disks (1 TB) or Remote Backup Service.

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.

Specific recommendations can vary greatly depending on user preference for computer types (desktops, notebooks, tablets etc.). Individual office workflows can affect decisions on peripherals too. This proposal is a sample that assumes fixed desktops in all offices and exam rooms, and a minimum of peripherals; more peripherals can certainly be added. In general, mobile workstations can reduce the required number of computers.

PCs in each exam room, 2 at reception, each doctor's office

EMR local configuration 1

  • Database/File/Printer Server - Windows Server 2012 – Intel E3-1240V2 3.4 GHz, 32GB RAM, 4x 1TB HD, 19" SVGA, 1Gbps NIC, DVD (RW), floppy
  • Application Server - Windows 2012 Server – Intel E3-1240V2 3.4 GHz, 32GB RAM, 2x250GB HD, 19" SVGA, 1Gbps NIC, DVD (RW), floppy and modem
  • 32 x Workstation - Windows 8 Pro, Core i5-2400 3.1GHz, 4GB ,120GB HD, 19" SVGA, 1Gbps NIC, DVD (RW)
  • 2 x UPS 1500VA
  • 48 Port Switch
  • Router/Firewall/VPN appliance
  • 750 VA UPS (for Firewall and switch)
  • 2 Card Readers
  • External Modem
  • Scanner (1 minimum)
  • Laser Printer (1 minimum)
  • Label Printer (USB with cable)
  • 34 x Windows 2008R2 Server CALS (client access lic.)
  • 32 x Windows 2008R2 RDS CALS (client access lic.)
  • 34 x AntiVirus
  • MS Office Professional 2010 / 2013 licenses (minimum 10 -1 per physician)
  • 34 ABELMed w SQL Server 2008R2 Standard Edition RUNTIME licenses.
  • Network cabling for 34 drops if required
  • 5-9 external USB Hard disks (1TB) or Remote Backup Service

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

ABEL has standardized on a Remote Desktop Services approach for all configs. The average bandwidth per user is 30Kbps and when printing scanning and program operation is all considered the requirement is approximately symmetrical.

  • From the point of view of the WAN connection in a single site (config 1) the ABELMed requirements would just be for offsite use, hospital, home, cottage etc. The requirement is 30Kbps per concurrent remote user, symmetrical
  • From the point of view of the WAN connection in a multi-site (config 2) the ABELMed requirements at the main site are 30Kbps for each user at all the remote sites plus any additional concurrent remote users. At the remote sites the bandwidth required is 30Kbps for each user at that site, again approximately symmetrical when scanning printing and program use is considered.

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

Yes, ABELMed offers remote server management services. ABELMed's tools require an Internet connection. Available services include Remote monitoring, Remote backup, Windows updates, EMR updates, EMR configuration, user management, log file examination and management, backup management, security configuration, network configuration, performance investigation and optimization.

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

Normally redundant hard disks eliminate the need to restore from backups. In the event of total hard disk failure, ABELMed provides a complete system recovery process. Backups are typically scheduled to be performed automatically. The schedule is composed of both full and incremental backups. Depending on the type of failure, recovery can be to the last backup (full or incremental), or point of failure.

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

Yes, the ABELMed EHR - EMR / PM v12 solution includes tools to manage the availability of the EMR on several levels - ABELMed:

  • Recommends hardware with appropriate availability in mind, providing pre and post sales technical support to customers, hardware vendors and IT service providers. Redundant hard disks (RAID arrays), redundant power supplies, battery backups, error correcting RAM, and fully redundant servers (clusters) are all recommended where appropriate.
  • Provides tools to automatically create scheduled maintenance plans, proactively optimizing and maintaining database integrity, and sets up scheduled, frequent, backups to disk.
  • Offers real time monitoring of server and network devices allowing problems to be quickly detected and responded to, often before availability is affected.
  • Provides technical services supporting customers and hardware/IT vendors with respect to optimal configuration, security etc.

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

ABELMed can provide real time server and network monitoring priced per monitored device per month. ABELMed would normally be the default contact and will respond based on each practice's customized plan.

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.