Vendor Selection Criteria

From Clinfowiki
Jump to: navigation, search

Choosing an electronic medical record (EMR) vendor is an important task, with many aspects to consider. An EMR can completely redesign a hospital's practice, but can also optimize it in ways a paper-based system could not. With over 400 EMR vendors in the market, selecting the best option could be overwhelming. After clearly defining the needs of the company, the next step is to evaluate which vendors more closely match your list of priorities.[1] Here is a list of some of the important considerations when choosing, installing, implementing and upgrading an EMR system. [2]

Core Clinical Features

In 2003, the DHHS asked the IOM to provide guidance on the basic functionalities of electronic health records systems. The committee concluded that the core functionalities should address the following areas:

  • Improvement of patient safety
  • Support delivery of effective patient care
  • Facilitate management of chronic conditions
  • Improve efficiency
  • Feasibility of implementation and
  • Integration of hospital services

In the Journal of Healthcare Information Management Kranny et. al discussed the importance of an application in the EHR which will promote continuity of care. During the selection of a vendor it is imperative for the decision committee to find out if there is an integration of inpatient, clinical and outpatient interface systems. (8) The patient's progress in house and discharge summary should be accessible by his primary care provider upon discharge. Medications that were discontinued during hospitalization should be updated in the patient's outpatient medication profile so worng medications are not refilled by the patient. IN addition, when new medications are added to the patient medication regimen it should be accessible by the primary care provider and outpatient pharmacist.

Based on these areas, the IOM committee identified eight categories of core functionalities, including: [3]

  • Health information and data
  • Results management
  • Order entry/management
  • Decision support
  • Electronic communication and connectivity
  • Patient support; administrative processes
  • Reporting and population health management

Analyzing Business(EHR) requirements

The Evaluation team or decision Team should consist of clinicl healthcare professionals including house staff, tech support professionals, administrators, and financers from all areas of the institution. Each person brings to the table a differnt perspective of usage from their daily job responsibilites. Insitution-wide involvement creates awareness and knowledge of EMRs and their benefits. AS well as, an understanding of the upcoming modifications in work flows.

  • Assemble an Evaluation Team
  • Define the Product, Material or Service
  • Define the Technical and Business Requirements
  • Define the Vendor Requirements
  • Publish a Requirements Document for Approval

EMR software

  • Health Information & Data Management (Demographics, Problem list [CC, Conditions, Acute/Chronic, Worsening/Resolving, Injuries, Present Illness] with ICD-9 or ICD-10 numbering, Procedures, Diagnoses, Medications, Allergies, Family medical history, Consultations, Signs & Symptoms and Vitals, Progress Notes and Discharge Summaries, Appointments/Admissions/Visits, Advance Directives, Clinical Reminders [Immunizations, Screenings, Risks])
    • EHR that allows for the creation and maintenance of patient specific problem lists that are dated and organized by diagnosis, problem, and problem type and associates encounters, orders, medications and notes to one or more problems. Once a problem is resolved, the EHR provides an automated algorithm that closes that problem.
  • Is the Software configuration flexible to customize for future needs.
  • Is this EMR system compatible with any other systems such as adverse drug reaction system, case based reasoning system and rule based reasoning systems
  • Result Management (lab, imaging, other diagnostic measurements, pictures, multimedia)
    • Review and search results easily by sorting test types, test time, test administers, test results and so on
    • Choose one or several test types, such as HGB, and/or WBC, and/or blood sugar and chart on their results for showing trends.
  • The proposed EMR software should bring minimal to no new limitations to the institution. Selectors must be certain that the EMR system meets all required operational tasks.
  • How much customization to the EMR can the vendor offer to meet the institution’s needs? Will there be a surplus of unusable or insufficient components to the EMR?
  • Ensure that the EMR software is tested prior to finalizing the vendor contract.
  • Proposed EHR should allow for expandability to mobile devices, mobile medical applications and upcoming mobile technology.
  • Does the EHR have integrated practice management to avoid having to interface with a 3rd part practice management system?[4]
  • Does the software provide a tool for workflow mapping/charting?
  • Can the software be easily configured/adapted to changing workflows?
  • Does the EHR provide on-screen flags to indicate patient visit status?
  • Does the EHR allow customization of work flows by the provider, clinician, or other health care professional?
  • Does the EHR documentation method support error checking for vital sign data entry?
  • Does the EHR/EMR system allow multiple terminals (physician, nurses' station, X-ray, labs, etc.) to log in to the same patient's record simultaneously? Certain systems only allow one terminal to access a patient record at a time - they must log out before any other terminal can access patient EHR/EMR. (For example, if a nurse forgets to log out at their station, the lab cannot access that patient's record.)

Privacy and Security

  • Does the system provide roadmaps for adherence to organizational policies (such as HIPAA)?
  • The system shall allow an authorized administrator to enable or disable auditing for events or groups of related events to properly collect evidence of compliance with implementation-specific policies. Note: In response to a HIPAA-mandated risk analysis and management, there will be a variety of implementation- specific organizational policies and operational limits.[1]
  • Internet Connectivity and Redundancy Contract - There are three main types of connections for clinical data connections: business class digital subscriber line (DSL), business class cable, and T1 connection. Redundant back up systems and procedures to ensure your data will be backed up in multiple locations and securely stored off-site.
  • Will the system allow staff administrators to create and manage users and user security profiles?
  • The system restore functionality shall result in a fully operational and secure state. This state shall include the restoration of the application data, security credentials, and log/audit files to their previous state. [1]
  • If the system includes hardware, the system shall include documentation that covers the expected physical environment necessary for proper secure and reliable operation of the system including: electrical, HVAC, sterilization, and work area.
  • How well does the EMR work with antivirus, antispyware and other security software?
  • What is the vendor’s history with cyber attacks? [5]
  • Does the system allow for off-site access to files/data and how does the technology protect against external breech or diversion of patient information?

CPOE

  • Computerized Physician Order Entry (CPOE), e-Prescribing
  • Computerized Physician Order Entry system that integrates and provides for two-way communication with the Pharmacy, Laboratory, Registration systems, and that allows for scanning and downloading of health information as needed. The EHR system should have a completely understood interface and provide for interoperability with all current and future systems and between clinics and providers.
  • CPOE will generally allow for the organization to specify a default dose for a medication order. [6].
  • The CPOE team will need to review what happens when non-formulary items are entered. The workflow for non-formulary items will also need to be determined. [6].
  • The EHR should have the capabilities to interface with the various labs the hospital or physician uses to order and receive patient lab work automatically.
  • Does the EHR have a referral management system so that within large organizations, specialty and primary care departments can easily communication with each other and have similar information on a patient that is using both offices to treat their illness?[7].

Clinical decision support (CDS)

  • Earlier Clinical Decision Support (CDS) Tools
  • Historical Challenges of Clinical Decision Support (CDS) Tools
  • Benefits of Various types of Clinical Decision Support(CDS) Tools
  • Decision Support (Drug Interaction, Drug information and other Prescription Supports, Clinical Guidelines [Plans & Protocols] and disease information, Diagnosis and differential diagnosis Support, Risk Assessments, Clinical Checklists, Medical References, etc)
  • Formulary Database Support
  • Electronic Communication (Provider-Provider & Patient-Provider Direct Communication, Health Data Exchange, Interface to Medical Devices, Notifications, Clinical Documentation such as Nursing Notes)
  • Patient Administration (ADT [Admit, Transfer, Discharge], Reservation & Scheduling, Billing, Waiting List Management, Records of Patient Activity, Master Patient Index across the Healthcare Organization)
  • Querying & Reporting (Research & Analysis, Statistics [Vital Statistics, National Statistics], External Accountability Reporting)
  • Telecare, Telehealth, and Telemedicine functionality. Home Monitoring device input/linking.
  • Patient Portal for online personal health record access
  • Clinical policies and procedures guidelines
  • Produce visit summary and complete medical record printout and data export on demand for patient use.
  • Electronic Health Record (EHR) systems should be capable of accommodating multiple users working concurrently within the system and within the same patient file or document [2]. EHR systems should also be capable of protecting the integrity of data in the system so that no data loss occurs when multiple users are working concurrently with the same patient file or document [2].
    • Provide direct decision support explanation link to evidence based knowledge (through such as "infobutton",etc) about needed test information, such as purpose and methods of conducting that test, normal range of that test, clinical indications when abnormal results occurred and suggestions what to do, etc.
    • Provide abnormal alerts to providers and/or patients through various ways, such as online display, cell phone text messages, etc if the patients/doctors register for this service.
  • The organization will need to strike a balance between displaying so many alerts that it causes clinical care to slow. [6].
  • Does the EHR have an aspect of the CPOE that can manage patient protocols and treatment plans? [7].
  • Does the software have “Clinical/Business Intelligence” capability based on local clinic medical trends, e.g. if there is above normal upper respiratory infection clinic visits, perhaps a flu season is imminent and may warrant stocking of flu vaccine in the clinic?

Data storage and retrieval

  • EHR systems should be capable of capturing, storing, indexing, retrieving and displaying externally created documents [2]. Indexing of captured documents should include not only patient identifiers and descriptive information, but also date/time stamps and document type [2].
  • EHR systems should be capable of retaining all system data until such data is archived or intentionally purged from the system [2].
  • The system should load patient records in a timely manner to not interrupt workflow.
  • This system should present chronological data of patients like medicine history, progress of diseases.
  • Also, system provides gene information or drug allergies of patients to avoid ADE.
  • System should be compatible with old system to reduce re-entry time.
  • System should update regularly.
  • system should be able to have Patient prescription plan eligibility, prescription product formulary and external medication history.
  • System should be able to have insurance retrieval capabilities (i.e. insurance firms, sum insured, premium dues, etc.).[11]
  • Capability to integrate with other products such as practice management software, billing systems and public health interfaces.

Other Clinical Functionality

  • Does the system promote delivery of safe care?
  • The system shall require documentation of the audit support functionality in the vendor provided user guides and other support documentation, including how to identify and retrospectively reconstruct all data elements in the audit log including date, time. [1]
  • Can the system identify the chronic disease management subgroups?
  • Is the EHR scalable to different medical specialties and practice demographics (i.e., Neurology vs. Cardiology, small satellite practice vs. intensive care unit)
  • Can the system support future clinical models (i.e., Medical Home)?
  • Does the EHR system support accurate, consistent and effective clinical documentation by appropriately balancing data auto-population, structured data entry, and unrestricted physician entry of natural-language narrative?
  • Does the EMR have the capability to display data over time graphically, such as growth charts?
  • The system shall provide the ability to query for a patient by more than one form of identification
  • Can it integrate with external knowledge sources such as links to journal references or other knowledge base systems (such as John Hopkins Guidelines System) to provide more academic information and update on particular patient problem?
  • Does the EHR store the identity of the user and associate the ID with the additions or changes made to the system?
  • Can the EHR system be used to capture clinical trial data? How the clinical trial specific data is managed?
  • Does the EHR system have the ability to import and export data (interact) in a standard format to EHR systems from other vendors?
  • In outpatient departments, does the EHR have a patient-to-physician email and/or web access abilities for the outpatient department to communicate directly with the patient in case more information is needed or the office needs the patient to take some action?[7].
  • Does the vendor’s product provide the key functionality needed to achieve the organization vision?
  • Does the EHR provide outcomes data in terms of key metrics (cost savings, medication error reduction, disease management) in line with the vision of the organization?
  • How does the system import data from personal health devices?
  • Can patient data be directly imported from patient portals or personal health records?
  • Does the vendor provide an EHR system that can be integrated with and is interoperable with other systems?
  • Can the vendor provide an EHR system with standard terminology that is cross platform with other EHR systems?
  • Does the vendor provide safe log in for patients and clients?
  • Does the EMR could provide appropriate information on screen without cramming too much information?
  • If the EMR/EHR system allows users to access through mobile devices (through the web or an app), is the mobile version similar to the computer-based version? Is it user-friendly? Will mobile access require additional training, or will user feel comfortable with it after training on the computer-based version?
  • What type of system is built into the EHR for clinicians, staff and any other users to provide feedback?
  • Does the EMR/EHR integrate with off the shelf software currently in use? (i.e. Microsoft products, adobe, etc.) and will new software/upgrades need to be purchased to enable inter-operability?

Continuity of Care: Outpatient vs Inpatient EMR

If there is no communication between the ambulatory (outpatient) and the inpatient (hospital admissions) EMR services, the clinical information does not get accurately or completely transmitted between transitions of care. This need for continuity of care must be addressed by the EMR vendors by looking at the integration between their outpatient and inpatient clinical systems. The level of integration can be-

  1. at the user interface level (for example, separate inpatient and outpatient applications, minimal data sharing with separate databases, viewable in same shell)
  2. at the database level (such as having two separate applications and one database, with the ability to manually transfer data between applications)
  3. at the workflow level (with one application and one database, with data displays in the context of care setting and full accommodation for workflow)

A discharge note writer is needed to generate a transition of care document (discharge summary) so that the patient can be handed off from one setting of care to another. According to JCAHO (Joint Commission) medication reconciliation must be done at every transition of care. There is very little literature that addresses the direct financial ROI for an ambulatory EMR, as opposed to the inpatient arena, where more evidence exists.[8]

Nursing Functionality

  1. Supporting eMAR: supporting real-time electronic medication administration record and bar code medication administration technology [Link to reference]
  2. Supporting bedside automation in medication delivery: Support data interface and real-time monitoring of smart pumps and home infusion pumps [Link to reference]
  3. Ease of use of Nursing flow sheets: Rows in the EHR to be filled by nurses for consistent patient care processes.[9]
  4. Ease of access and usability of EHR for nursing administration and clinical documentation for nurses. [10]
  5. Clinical decision support and risk assessment tools for issues related to nurse care delivery, such as falls, medication delivery, skin ulcers etc. [11]

Pharmacy operation

Formulary management

  1. Data repository for formulary information, maintain real time update of medication information with national drug information database
  2. Support periodic update of formulary, restricted formulary, and nonformulary medications
  3. Cross reference patient’s insurance formulary list to allow for generic medications to be selected when e-prescribing.

Drug dispense and delivery

  1. Support outpatient pharmacy operation functionality:
    1. Maintain outpatient prescription data
    2. Management of prescription fill, refill and dispense activities
    3. Support billing protocols with governmental and private insurance
  2. Support inpatient pharmacy operation functionality
    1. Maintain inpatient medication ordering data
    2. Real-time monitoring of IV and oral medication compounding and delivery
    3. Support real-time data interface with automatic dispensing cabinet

Research Functionality

  • Does the vendor bid include the product's ability to be used as a tool for research. If "no", is an add-on solution for research capability needed and will it entail extra cost. [12]
  • Does the EMR have informed consent alerts and documentation systems for clinical research?
  • If the proposed installation site is a research hospital, what are the research capabilities of the EMR?
  • How is research achieved?
  • How are reports produced?
  • How is data exported from the production system?
  • Which database is used for reporting? For research? Vendor or other?
  • Does the vendor provide natural language processing for entry data or document?
  • Support for research billing including research orders (6)
  • Does the EHR system provide data mining capabilities to support clinical research?
    • Are there limits on the fields that researchers can use?
    • How difficult is it to interface with the database?
    • Does the EMR have smart search abilities to search through physician notes for specific keywords while extracting research data.
    • Does the vendor assist in research endeavors, or is it left up to the institution?
  • Does the EMR have the flexibility to capture documents necessary for specific clinical trials like adverse events, enrollments, and etc? [9]
  • If research involves use of pathological/histological samples, does the EMR system tie into the laboratory management systems and database to allow for retrieval and processing of samples?
  • Does the EMR system provide functionality to identify clinical related concepts?
  • Does the EMR provide the flexibility to normalize the clinical concepts found in the document?
  • Does the EMR provide the assistance to automatically generate the de-identified document for research purpose?
  • Does EMR system provide functionality to implement study-screening parameter into patients’ registration, scheduling, medication lists, diagnostic codes (ICD) and clinical notes? [13]
  • Does EMR system provide functionality to contact potential candidates and notify the patient’s providers of potential study eligibility? [13]
  • Does EMR system provide capability to systematically captured study specific data and electronically exports deidentified study data to clinical trial electronic data capture system? [13]
  • Vendor's ability to support research is especially important for large academic hospitals. In academic settings, research productivity is evaluated on publication and funding. To assess the ability of each vendor’s EMR to support research, the same two criteria for assessing productivity can be used— 1) publications that were the result of or 2) funded research made possible through EMR use or data analysis from the EMR’s data warehouse. [14] To assess this one can follow Mt. Sinai's example in selecting a vendor as follows:
  1. After a rigorous investigation of vendor statements and industry statements, a standardized questionnaire was used to consistently ask about items specific to the site contacted. Sites suggested by vendors, as well as community listservs, were contacted; the user community was engaged.
  2. Literature search:
    • PubMed was used to search MEDLINE covering the fields of medicine, nursing, dentistry, veterinary medicine, the health care system, and the preclinical sciences.
    • Also queried was CRISP (Computer Retrieval of Information on Scientific Projects), a searchable database of federally-funded biomedical research projects.

Meaningful use gap analysis

  • The ONC’s Regional Extension Centers (RECs), located in every region of the country, serve as a support and resource center to assist providers in EHR implementation and HealthIT needs. As trusted advisors, RECs “bridge the technology gap” by helping providers navigate the EHR adoption process from vendor selection and workflow analysis to implementation and meaningful use. [15]
  • Does the system meet all Meaningful Use objectives?
  • Does the system provide relevant reports for data for compliance with meaningful use of the EHR.[11]
  • Does the EHR vendor provide any guarantees regarding the ability of a practice to meet meaningful use requirements? (http://www.americanehr.com/Home.aspx)
  • Does the vendor support data documentation and capture of future government mandated measures such as Meaningful Use, ACO measures, CMS measures for Patient Quality, population health etc?
  • Does the EMR system provide any option to store Genetic information of the patient and at the same time, this genetic information should be easily accesible for research.
  • Make sure the vendor's product is able to document the meaningful use [2]
  • Is the EMR CCHIT Certified?
  • Is there a way for the organization to monitor the usage of EMR components?
  • Will the EMR user potentially qualify for the American Recovery Health and Reinvestment Act or Health Information Technology for Economic & Clinical Health Act funding opportunities?
  • Be certain that the organization has a way to transfer pertinent data from the current EMR to proposed EMR. Create a plan that is not only financially safe, but also allows the organization enough time for implementation.
  • Does the vendor provide training and resources specific to Meaningful Use compliance?
  • Does the vendor provide any consulting services to assist with workflow modifications and attestation for Meaningful Use?
  • Is the EHR capable and certified to send PQRS (Physician Quality Reporting System) data to CMS to fully meet the requirements of meaningful use?
  • Does the EHR implement the CDS to improve performance on high priority health conditions?[11]
            • Will the EHR help the hospital to meet the following requirement of Meaningful Use:
  • Use CPOE for medication, laboratory, radiology ordering by licensed professionals
  • Automatically track medications from order to administration using assistive technologies such as bar coding in conjunction with an electronic medication administration record (eMAR)
  • Generate and transmit permissible prescriptions electronically (eRX)
  • Protect electronic health information created or maintained by the CEHRT through the implementation of appropriate technical capabilities.
  • Implement drug-drug, drug-allergy checking.
  • Maintain up-to-date problem/diagnosis list.
  • E-Prescribing
  • Maintain active medication list and medication allergy list
  • Record demographics: Gender, Race, Date of Birth, Ethnicity, Preferred Language
  • Record and chart changes in vital signs: Height, Weight, Blood Pressure, Calculate and Display, BMI, Plot and display growth charts for children 2-20 years, including BMI
  • Generate lists of patients by specific conditions to use for quality improvement, reduction of disparities, research, or outreach.This requirement (from Meaningful Use, Stage 2) requires the EHR to allow patient lists to be created within the EHR using specified criteria so that patients can be sorted by specific conditions. [16]
  • The EHR system must be able to generate Summary of Care documents when the patient transitions to another level of care [16]
  • The EHR must be able to provide a function that allows patients to view, download, and transmit data regarding their hospital admission. Usually this is known as a patient portal. [16]

[16]

Patient quality improvement

  • Link to patient education materials database or service and the ability to load practice specific documents for patient handouts. Must be able to access and print these from visit encounter interface.
  • Does EHR system provide better integration among providers by improved information sharing, viewable and up-to-date medication and allergy lists and order entry at point of care or off-site ?
  • Will the EHR system provide standardization of data, order sets, and care plans helping to implement common treatment of patients using evidence-based medicine ?
  • Does EHR system provide access to experts for rural health care providers by sharing best practices and allowing for specialized care through telemedicine ?
  • Can EHR system manipulate and provide feedback on population management trended data and treatment and outcome studies for more convenient, faster, and simpler disease management?
  • Can the system pull from clinical documentation for billing, quality reporting and patient safety reporting?
  • How does the vendor use certified EHR technology in ways that can be measured significantly in quality and in quantity?
  • Will the system support utilization review with the Milliman and Interqual clinical criteria for Quality Management and discharge planning.
  • Does EMR system provide capability to aggregates data on the impact of specific evidence based/cost effectiveness intervention as compared to current population in management practice?

Public Health research

  • Does the vendor support the ability to send de-identified bio-surveillance data to population health agencies to support epidemiologic research?
  • Does the vendor have the ability to send patient specific public health disease report(s) to a disease registry, as a part of a Public Health Information Network (PHIN)?
  • Does the vendor have the ability to report on Quality Improvement, such as infection control measures (i.e., Hospital Acquired Infection rates) or patient safety measures?
  • Does the vendor have the ability to report to the State, CDC Registry and external sources

IT and Technical Requirements

  • For already existing software functionality, does the vendor employ reliable and trustworthy software like an open-source MySQL or Apache server? Or do they develop their own system, or do we have to license a proprietary one (extra cost)?
  • How the vendor estimates the total amount of users and licenses needed? Will they be concurrent user licenses or asynchronic?
  • Will technical support remain active even if the Hospital is running a non-upgraded system? For how long?
  • Does the system use DICOM standards for the transmission of image data?
  • Does the system provide an imaging database or allow customized program attachments of imaging needs of specific departments in the hospital?
  • What are the hardware requirements? [1]
  • How frequently does the vendor provide patch upgrades for the product?
  • Do the upgrades come with a fee?
  • Is the vendor’s application (system) platform independent?
  • Is the system using standards such as Snomed, ICD 10; HL7 Version 2 or 3; HL7 infobutton…)
  • How does the system handle multiple logins of the same user at different locations/instances?
  • How does the system handle user inactivity? (auto-logout, discarding\saving changes, draft creation)
  • Is the software capable of using biometric data for rapid login by providers who are mobile between patients/sites?
  • How does the system lend itself to automated back-ups? Does the vendor provide IT support team to implement specific back-up plans that will work with the hospital's IT team?
  • Can the system allow login remotely – off site transcription or home or other clinic?
  • Does the system provide the ability to identify all users who have accessed an individual's chart over a given time period, including date and time of access?
  • Does the vendor offer a Software as a Service (SaaS) solution, also know as an Application Service Provider (ASP), or a client-server solution?
  • With existing systems, how tightly integrated will the new EHR system be and what prep work is required to make the integration possible?
  • Does the system have modules for automatic update of knowledge sets at regular intervals, more like automatic update of antivirus definitions?
  • How often does the software need to be upgraded? [1]
  • Does the software allow generation of customized reports such that desired information can be extracted periodically for performance improvement projects or performance monitoring.
  • Does the vendor utilize the desired technology?
  • Is remote access available for mobile devices?
    • Is this web-access or a dedicated app?
    • In what way is this mobile access limited? Does it have access to all functionality?
    • What devices can access the mobile apps? (e.g. iPad, iPhone, Android, etc.)
  • Is remote access cross platform? The use of open standards (e.g. HTML5, XML) allows users on any platform, including smartphones and tablets, to have equivocal access to the system.
  • Does the system support web-based working environment?
  • Does the system provide extension package or software for IT engineers or users?
  • Does the system comply with HIMMS standard?
  • Can the system be installed on Windows or IOS operating systems?
  • How does the system’s IT infrastructure requirement align with the institution’s current infrastructure and the institution’s infrastructure five-year strategic road map?
  • What hardware technology (Server) does the database support? And does the supported hardware provide built-in high availability?
  • Does the system’s application (not database) support virtual environments? Will it run on a virtual server?
  • Is your ticketing system capable of interfacing with [name of ITSM software utilized by your institution]?
  • Negotiate the terms and prices of the interface system: to/from PM system, scanner, fax machine, laboratory, health information exchange partners such as hospitals, ambulatory surgical centers, radiology, ePrescribing.
  • Can the system be hosted and supported remotely by the vendor?
  • How scalable is the IT infrastructure? Is there a peak limit on the number of concurrent users utilizing the system? (this comes in handy during mergers & acquisitions in which you may exponentially increase in size of user base)
  • Does the system support dictation function?
  • Does the system support speech recognition?
  • What are the data back up options available in case of natural calamity?

Legacy systems

  • How does the vendor compare in KLAS rankings of similar systems and applications?
  • How will legacy patient record data be integrated into the new system?
  • Does the vendor provide services to convert and transfer data from legacy systems into the new system, and if so, what is the cost?[17]
  • How does a legacy Practice Management System integrate with the EHR system? Is there a list of successful PM vendor integrations? MikeField 20:47, 29 January 2010 (CST)
  • Make sure the vendors give accurate information for the Request for Proposal. So the stakeholders can make informed decisions on the comparison of vendors.

-Zoker 9/17/2011

  • What is the legacy Practice Management System conversion process for legacy data import into the EHR system? Time/cost and loose-ends? What reference clients are there for particular legacy PM systems? MikeField 20:47, 29 January 2010 (CST)
  • Does the vendor have a List of Lessons Learned from previous implementations?
  • Does the vendor have a legal license to essential code sets, such as the AMA Current Procedural Terminology (CPT®) file? Will the vendor maintain this license annually as part of your service or maintenance agreement?American Medical Association
  • How does the vendor manage diagnosis documentation and coding? Does the system require specific coding terminology or does it allow provider synonyms for coding terms? How is that updated and maintained?
  • Does the vendor offer a “test environment” in which upgrades are loaded to allow you time to test and learn their functionality without affecting your live system? American Medical Association
  • What is the vendor's rate for on time & under budget implementations?
  • Are other consulting firms certified to implent the vendor's product? If so will the vendor provide system updates and customer service if system issues (not related to implementation) arise?
  • Check whether the vendors EMR products are CCHIT certified (http://www.cchit.org/products/cchit)
  • What services does the EHR vendor offers for post-implementation optimization of the system with respect to training and system customization? (http://www.americanehr.com/Home.aspx)
  • What is the company policy regarding data ownership for the ASP EHR?
  • The EHR product should be certified for the standards and certification criteria issued by the Office of the National Coordinator for Health Information Technology (ONC-HIT)? How many criteria does it satisfy?

Troubleshooting

  • Immediate trouble shooting ability.
  • Regular connect with customers about their problems
  • The system shall include documentation that describes the patch (hot-fix) handling process the vendor will use for EHR, operating system and underlying tools (e.g. a specific web site for notification of new patches, an approved patch list, special instructions for installation, and post-installation test).[1]
  • The system shall include documented procedures for product installation, start-up and/or connection.[1]
  • What options does the EMR have for upfront abstraction and scanning? Are these costs included in the purchase of the EMR?
  • Can the vendor support the organization desired implementation strategy?
  • How can the EHR technology be useful for electronic exchange of clinical health information among providers and patient authorized entities? (http://en.wikipedia.org/wiki/Electronic_health_record#Quality)
  • Is implementation of the new EHR system going to be in stages or at once based on the size and complexity of the purchasing institution?

EHR Disaster Recovery

Either internal hardware problems or external sources (especially in EHR systems that store data in the cloud) may cause unexpected EHR system failures. The EHR may be unavailable for a few hours or for a week or more. Disaster recovery must always be considered when selecting a vendor to ensure that data is secure in these emergency situations. Questions to consider include:

  • Does the EHR use internal hosting or an ASP model? [18]
  • Is the EHR system adherent to the HIPAA Security Rule and provides both a contingency plan and secure data back-up reserves in case of system failure?
  • Has the EHR provided users with a detailed disaster plan during implementation of the EHR that includes how to cope with unexpected system failure?
  • Has the EHR provided training packets and educational materials for end users to study to prepare for unscheduled downtime of the EHR?
  • Will the EHR notify users immediately when system failure occurs and provide information about the breadth of the failure and the time anticipated before the EHR will be restored?
  • What happens when small private EHR vendors go out of business for any reason? Will you have a backup of the source code when that happens? Are we able to access that source code for our use?
  • Is off-site back-up and recovery supported in the event of a natural disaster or other catastrophic event?
  • Is training available for catastrophic event recovery?
  • What safeguards does the software have to warn users/administrator of an impending major failure?
  • Does the software monitor the hardware that it runs on?
  • Is there a technical relationship between the EHR/EMR vendor and hardware vendors?
Some of the criteria I will like to see in an EHR system in the event that it crashes or during downtime*****

1. What backup system does it have in place during such an event so that patient care continues without reverting to a paper system?

2. How is data updated into the system when it is back up and running again?

3. Where is the data stored so that in the event of a catastrophic crash historical data is not lost?

Health information exchange, connectivity, and standards

  • Does it meet the following connectivity standards: HL7, HL7 CDA, CCR, HL7 CCD, ELINCS and Vendor software specifications? [19]
  • How flexible is there connection framework? Can it negotiate multiple standards?
  • How quickly can you build and implement an interface within the interface engine?
  • Can our facility support the space needed for the installation and implementation of an EHR?
  • Make sure wireless connection is accessible in all parts of the hospital is your facility is planning to use portable devices (tablets, computers on wheels, etc.) to access the system.

Implementation

  • Implementation Project Manager – A project manager is necessary to bring vendor experience and guidance to the implementation process and should hand off the implementation to your internal team within 12 to 15 months.
  • Will the vendor be readily available to conduct training for all shift and service line?
  • Service Agreement - A service agreement identifies what the EMR vendor will do to maintain the software, including software maintenance, technical support, and upgrades.
  • IT Support Agreement - Hardware installations are your responsibility, not the EHR vendor. However, if you do not have onsite IT support, request an estimate for the following:
    • Installation charges for electrical requirements, cable and phone connections for the system
    • Monthly fees to provide access to patient data on a remote server
    • Networking design and administration charges related to the set-up and service of client's network
    • Hardware onsite installation and maintenance
    • Third-party software maintenance for products not provided by the vendor
    • Correcting errors that result from changes you or a third-party made to the software. This applies primarily to client-server agreements
    • Backup capabilities. This applies primarily to client-server agreements.
  • Terms and Conditions - Irrespective of the contract length, ask about penalties for withdrawing your data. Any vendor interested in preserving its reputation will provide you with data in a common format able to be transitioned to another system, but there is a withdrawal fee. [13]
  • How long is does it take for a typical install, troubleshooting and go-live of the EHR?

Configuration

  • Does the vendor factor the number of users as part of their implementation cost?
  • Does the vendor provide their own hardware or use a third-party company for their hardware needs? Based on the practice size and niche, is a well-established vendor with all software and hardware in-house preferable?
  • If you have an existing system, what kind of difficulties will the vendor encounter? Will it be possible to transfer existing data to the new system?
  • In calculating the Total Cost of Ownership (TCO), the break out costs should include who pays for the additional costs due to delays in implementation, especially those due to the Vendor. In fairness, the Vendor's rate for successful, on-time and under-budget implementation should be discussed as well.

•Does the TCO include lifecycle costs that include milestone payment scheduling to back up promises made by EHR implementation? [8]

  • Does the system minimize or ease the data input, so that doctors spend more time with their patient?
  • Does the vendor qualify under the organization acquisition policies?
  • How will current policies and procedures change once implementation takes place?
  • Is there a dedicated support team?
  • If implementation of the system fails, what steps is the EHR willing to take to make it successful?
  • Will the license cost for updated versions of the EHR be borne solely by the purchasing institution or will there be cost sharing between the institution and the vendor for updates?
  • How often the possibility of system break out?
  • Does the fee include pre-training and post-training?
  • How long and including of the warranty of infrastructure and system? Do we pay for accident damage for system or hardware?
  • What system configurations are available? How does the vendor involve the client in the configuration of the system?

Training of users

  • How many hours of initial training is provided for administrators? For users?
  • When is the initial training provided, during or after implementation?
  • How large a virtual environment will be required to provide training for staff, and how much time should be allocated.
  • What are the time requirements to train the trainers?
  • Is the initial training included in the costs of the tool?
  • If additional training is required post-implementation, how is it priced – lump sum or hourly rate?
  • How many hours of post-implementation support is included?* Will the vendor provide technical training to the IT Department of the purchasing institution to handle minor non-critical hardware problems?
  • How long is the training that is required for each subgroup to fully implement the system?
  • What are the training requirements for the vendor? For the clinic/hospital?
  • What is the vendor's track record for successfully training a new system for your clinic/hospital size?
  • What training manuals, user guides, on-line training assets, and any other training materials will be made available to the clinic/hospital?
  • What training mechanisms are used by the EHR Vendor? (http://www.americanehr.com/Home.aspx)
  • Does the vendor provides training instructors at beginning?
  • Are the training staff familiar with both the technical aspects of the product and the clinical needs of the department of interest? (i.e. subject matter specialist, clinical informatic specialist)
  • Does the vendor has well-organized and reliable training courses?
  • Training Contract - Training should be included in the licensing and service agreement, but some vendors provide separate online and onsite training contracts.
  • Does the EHR vendor provide a test version of EHR product for training and quality assurance (QA) purposes as well as the full production environment that is installed in the clinic? (The test version is a segmented area where users can make changes to templates or forms without it affecting the live environment) (http://www.americanehr.com/Home.aspx)
  • Are training materials provided by the vendor or is the organization responsible for producing in-house? If the training material will be developed in-house, does the vendor stipulate specific training requirements (i.e. classroom-based vs. web-based, mandatory competency examinations)?
  • What kind of on-going training and support will be provided after implementation? Is the cost of post-implementation training and support clearly specified?
  • If there are major updates to the system, will the vendor provide ample support and training for the users? And how much will this additional training cost?
  • Does the EHR/EMR vendor offer the option to have their staff available to be present at the hospital/clinic/facility during training and then "go-live" implementation? This would allow the EHR/EMR staff to offer hands-on support for any obstacles that come up during training and "go live" implementation.


* Spell out pricing before selecting and Electronic Medical Record (EMR/Electronic Health Record (EHR) system such as hardware, software, maintenance, upgrade costs, lab and pharmacies interfaces, customized quality reports, expenditure to connect to health information exchange (HIE)Bold text== Future relationships: vendor partnership ==

  • Talk to vendor's existing customers, making sure to also contact some vendor customers independently, as the vendors tend to only provide contacts to their most satisfied customers.
  • Research available EMR systems and vendors: determine if your jurisdiction has a "pre-approved" vendor list; develop checklists & questionnaires to assist with product comparison; and prepare a Request for Proposals (RFP).
  • Composing the RFP can be a daunting task. AHIMA has created a guidelines for a template that may be used to write the RFP. The guidelines are extensive and include several particular components that must be included. It can be found at: http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_047959.hcsp?dDocName=bok1_047959 [20]
  • An important consideration is whether the vendor or any of its industry partners have done an analysis of processes in healthcare
  • Ensure there will be well-laid out contractual agreement regards the 'source code' that will satisfy/cover necessary conditions: "When does the company get the 'source code?, How does the company get the source code?"
  • If there are workflow changes within the organization, after the product is implemented, is the product flexible enough to allow for changes without major outages or disruptions to daily activity?
  • What are the vendors’ contingency plans if technical glitches occur, post implementation?
  • Is technical support offered by the vendor 24 hours per day/ 7 days a week?
  • In the event of need for support from the vendor, what is the approximate response time to calls that vendor the projects?
  • What is the cost of providing this technical support per hour?
  • What size, in terms of employees, is the EHR vendor? Do they have the staff to fully address the support needs of their current client base and, can they accommodate the added support load of your institution?
  • In terms of clinical decision support, how often are drug list and drug interaction list updated? Once updated, how long will it take for the changes to be accessible by the end users?
  • When code sets and medical vocabularies, ontologies, etc. are updated, how long after will the tool be updated?
  • In "EMR Vendor Selection" on Health Technology Review.com (http://www.healthtechnologyreview.com/emr-vendor-selection.php) it states an old adage in the Software industry that consumers will buy a product based on features, but will leave the vendor based on a lack of support. Therefore, it is important to check references for the vendor related to post-implementation technical support satisfaction.
  • Aside from providing source code in the event the company undergoes changes, how and when can the organization acquire the "raw" data?
  • Will the source code be placed in escrow so that the system could be maintained and modified by internal IT staff in the event that the vendor ceases operation.
  • Does the vendor have local support personnel or will all issues be handled by a distant team?
  • What is an average time for installing and testing upgrades to the system? If an upgrade is missed or skipped, does the subsequent upgrade(s) have all prior changes included or just the current fix or feature for that version?
  • Is there going to be a vendor-institution confidentiality agreement or can the vendor share institutional information and dealings with other establishments?

* Does the vendor's produce meet our needs and goals for our practice? Carryout a test drive of our specific needs with the vendor's product and provide the vendor with patient and office scenarios or mock trial that they may use to customize their produce demonstration.Bold text=== Upgrades ===

  • Does the vendor share the organization's vision for the EHR?
  • Does the product provided by the vendor has all the key functions needed to fulfill the vision of the organization?
  • Is the vendor utilizing the desired technology?
  • Compare retail broker workstation alternatives, including proprietary and third party packages, based on user requirements and technology/operational considerations. Project included EMR development and response evaluation
  • Does the vendor plan to offer interoperability options in the event of a nationally implemented CIS?
  • Upon the termination of a license or agreement, is there an orderly process for you to extract your data? This is applicable if you access the vendor’s software within an application service provider (ASP) model.American Medical Association
  • Ability to have HIE compatibility
  • Improved billing accuracy and charge capture
  • Electronic replacement for traditional reportable disease notifications to health departments, may become part of biosurveillance in the future.[1]
  • Is it possible to virtualize or sandbox the system to test updates? This functionality would allow site specific testing of new features and systems with less risk of corruption of the current system. It would also allow testing of new features functionality and allow easy rollback if features end up being unwanted.
  • Does the system allow outreach/growth to affiliates as a "subset" of the existing clinical provider group? Does that outreach include full or limited functionality? How does that data interface with the existing clinical record?
  • How does the system scale? Is the vendor able to provide support and functionality as a practice grows or can they provide functionality to a small, regional branch?
  • Provision of EHR systems that support the capture of public health data from Clinical Information Systems.
  • Does the system can combine with EHR in long term health care area as a reminder of senior people?
  • Ensure that your vendor will be around when you need help. While specific vendor qualifications vary, generally information to be considered in the vendor vetting process, besides functional and technical details, includes vendor reputation, staff experience and qualifications, and financial solvency. (Chao, C., & Goldbort, J. (2012). Lessons Learned from Implementation of a Perinatal Documentation System. JOGNN: Journal Of Obstetric, Gynecologic & Neonatal Nursing, 41(5), 599-608. doi:10.1111/j.1552-6909.2012.01378.x)
  • Does the vendor allow discrete data capture and easy reporting of critical data that needs to be submitted for reimbursement by the national and state policies on healthcare?
  • Is the vendor at the forefront of research in healthcare and does the software offer clinical dashboards and predictive models for easy tracking and analysis of patient data and efficient decision making by clinicians.
  • Does the vendor require hiring of outside consultants for training?

Contracts

Contracts are as much a business tool as they are a purchasing agreement. [21]

  • Project Payments
  • Contract Terms [1]
  • All costs, current and future, associated with the implementation

Details of the total cost incurred by the institution also called total cost of ownership (TCO) is an important consideration in the selection process. It helps to predict the longevity of the program. The request for proposal to vendors should include a request for information about vendor license and implementation costs. Vendors should deliniate the assumptions made when preparing the TCO so the decision committee is able to verify that they are parallel to the goals and objectives of the insitutions. If the same assumptions are encorporated in all request for proposals one can better compare the applications.(8) Institutions must also consider the intangible return on their investments such as reduced adverse events, decreased hospital stay, accurate and timely billing and improved management of supplies.

  • Does the vendor have any hidden fees?
  • Time commitment from vendor with regard to implementation and training
  • Penalties for delays in implementation
  • Code escrow - be sure code will be available if vendor goes out of business
  • Indemnification and hold harmless clauses
  • Confidentiality and nondisclosure agreements
  • Warranties and disclaimers
  • Limits on liability
  • Dispute resolution
  • Termination and wind down
  • Intellectual property disputes
  • IT support agreement
  • Training Contract
  • Applied area contract
  • User and vender liability
  • Disputation judgment
  • Attorney of vender and clients
  • User License - The person who has access to data using a user ID and password. Pricing structures vary according to the definition of user.
  • Consider variation of user licenses according to the needs: one price per MD, tiered price (MD, nurse or administrator), site license (25+ providers in the same facility), and enterprise license (multiple users in multiple departments). [22]
  • Interface - The EHR vendor's contract includes the cost of interfaces. These include interfaces such as those with your scanner or fax machine; and more complex interfaces such
  • Hardware Contract - Review the EHR vendor's hardware quote, but research may lower costs. Check the vendor's website for hardware specifications the vendor supports. Hardware includes servers, high-speed scanners, computers, handhelds, computer on wheels (COW), wall mounts, etc. Hardware installation to a wholesaler means assembling the server and software to make it work at their location prior to delivering it to you. It usually does NOT mean the installation at your location, a difference that will create a significant budget surprise. Clarify the term "installation" with any hardware wholesaler before making the purchase.
  • Third Party Software Contracts – Software includes encryption, speech-recognition, password management, Microsoft™ suite, anti-virus, golden image, bar-coding or webcams.
  • Business Associate Agreement - To be HIPAA-compliant you will need a business associate agreement with the vendor, and must ensure the vendor meets HIPAA security and privacy requirements.[23]

Check Vendor References

  • Each vendor being considered should provide minimal of three (3) references, to include a) physician users, b) IT person, and c) senior manager of the facility or practice.
  • Vendor provided references may be considered 'happy customers' with biased viewpoints.
  • Check several references on your own, outside of the provided references from the proposed vendor.
  • The chosen reference should be of a comparable size and structure
  • Have a prepared list of questions to ask.
  • Compare vendor satisfaction with current customers.
  • Ask supplied list of references how they acquired the EHR system, eg did they purchase the system or was it provided by the vendor?
  • Ask each reference to rate the vendor on a scale from 1 (very dissatisfied/strongly disagree) to 5 (very satisfied/strongly agree) for each criterion
  • Each vendor reference should provide reference on background information such as version of system currently being used, duration using current system, length of implementation, number of interfaces practice currently installed and estimated time to install, training provided on-site or remote.
  • Each vendor reference should provide reference on current system overview such as system reliability, satisfaction with vendor, and overall satisfaction with system.
  • Research references the vendor did not mention, visit facility to get an unbiased viewpoint
  • Must use list serves, internet searches and networking to identify other users to interview to get more objective viewpoint.
  • All interviewers should utilize the same questionnaire approved by the project manager or steering team.
  • Notes must be recorded by each interviewer for each customer interviewed.
  • These notes should be made part of the overall evaluation process, ideally kept by the project manager [7].
  • Is the vendor currently involved in or have a history of any litigation with customers?
  • Does the vendor have a track record?
  • Has the vendor been in business for long?
  • Perform site visits to similar organizations that are currently implementing the vendor’s product and ask plenty of questions to all end users (physicians, administrative staff, nurses, etc.)

[24] [25]

Site Visits

Conducting site visits at other institutions that have already implemented the vendor’s system may provide additional and practical insight. Below is a list of criteria that should be observed on site visits. The following are criteria established by MetaStar and can be found at: https://www.metastar.com/web/professional/docs/DOQ-IT/Vendor/Tools/SiteVisitingTips.doc [26]


  • Bring a diversity of positions from your committee.
    • At minimum bring a physician, IT specialist, and senior management person.
  • Observe during actual patient encounters.
  • Observe other departments such as billing and labs using the vendor.
  • Choose a site to visit based on your own research rather than one provided by the vendor.

Transparency

EHR vendors may enter contracts with confidentiality or non-disclosure terms that can prevent transparency. Examples include:

  • Disclosures required by law or regulation, sometimes with an obligation to give the other party advance notice and the opportunity to oppose the disclosure or seek confidential treatment.
  • Disclosure of information that has been independently developed by the disclosing party
  • Disclosure of information that is available to the general public or has been provided separately to the disclosing party without violation of an agreement.
  • Are there any hidden fees associated with training, support, consultant costs?

The definition of confidential information may be broad and could restrict your ability to share access to the EHR technology developer’s software in order to compare different EHR technology developer systems, provide access to researchers, or even address possible patient safety concerns. You should review the confidentiality and non-disclosure language carefully to make certain it does not inhibit your ability to conduct activities you value. [27]

Misc considerations

  • It is not uncommon for developers or implementers to impose lock-in features in order to protect their IP rights. How mature is the support community for the particular vendor and is there a marketplace for support and services to their product or is support limited to their own team?
  • A multidisciplinary team, usually a subset of the decision team consisting of a physician, IT personnel and a senior management must conduct a site visit to one of the vendor customer sites and vendor headquarters. Informal discussions at this level were quite informative as they bridged the gap between theory and practice for actual software implementation and usage.
  • An unstructured “drive-by” demonstration of the system must be arranged for, wherein the vendors conduct product demos, demonstrate product futures and distribute promotional materials for a majority of the employees to get the feel of the new systems. It facilitates building a comfort level and relationship with the vendor and the product offered.
  • Can the company demonstrate tangible ways that use of the product can increase hospital revenue? If yes, can you validate this/these claims?
  • Is the vendor willing to contract to go "at risk" for any part(s) of the contract?
  • What other services does the company offer (especially useful for rural or small hospitals or practices)? e.g. consultants to do special projects, data transmission/claims, billing
  • Can the record be accessed at home by clinicians and patients, or do they have to be on-site at the facility?
  • Is the vendor capable of adapting to emerging technology such as open source programming, cloud computing, "tablet" PCs/Macs, demand for smartphones (e.g. iPhone), and Web 2.0 technology?
  • Is the vendor capable of integrating its system with a personal health record and allowing more patient control?
  • Can the company provide return on investment analysis?
  • Vendors may not be chosen if the current managers have been convicted of or have had a civil judgment for the following: fraud, antitrust violations, embezzlement, theft, etc.
  • Reduced pharmaceutical costs derived from having information available at the time it is needed
  • How can this EHR be an asset for the solo practitioner who sees this technology primarily as a financial drain?
  • How much extra financial cost will it be to train outpatient clinics that are a subset of the system?
  • Does the vender return loss money if their system can not complete established goal in scheduled time?
  • Can the company provide a multi-background consult team from doctors, nurses, IT engineer, to attorney?
  • Does the vendor qualify the organization's acquisition policies? Is the vendor CCHIT certified?
  • Certification can be verified at the Certified Health IT Product List (CHPL) [28]
  • Is the vendor active in national EMR leadership task forces, such as the Electronic Health Records Vendors Association [29]
  • Will the vendor be supporting the organization's desired implementation strategy?
  • Check the track record of vendor for operations and maintenance support?
  • Will the vendor sell or monetize of our clinical data for research or any other purposes?
  • Is Application Support provided by on-shore resources?
  • Clarify the roles, responsibilities and costs for data migration if desired. [2]
  • Does the Vendor demonstrate financial and management stability?
  • Does the vendor have experience with implementing the product in a similar type of organizations? How many?
  • Conduct a site visit [2]
  • Ensure that the site is similar to you - similar number of beds, acuity, rural/urban setting
  • Flexibility that allows for significant changes in product or order lines. Thus, this enables for businesses to modify orders, if necessary, without having to face a penalty from the vendor. Not always do things go as planned and if any modifications are needed, there should not be any consequences that inhibit this from occurring.
  • The ability to provide all the products/services required and/or the complete solution. This in turn can provide the whole picture in allowing for the consumer more transparency in terms of being able to distinguish between the products/services that a particular vendor is offering. As a result, this can save time and money in terms of a consumer being able to choose a certain business that can provide everything that is needed instead of wasting time and effort in purchasing products/services from individual vendors that have a small selection available.
  • The ability to have a consistent supply of products or services readily available for the business to purchase at all times. There is always a need for products and services to be provided on a regular basis; thus a business does not want to have a vendor that has supply issues. If a vendor is not reliable, then it can affect the business’s ability to in turn supply and provide for its customers, which can have a dramatic effect on the reputation and finances of the business.
  • Does vendor volunteering disclose adverse events or near misses data involving vendor’s EMR system to potential buyers? Are there protocol designed to notify federally designated patient safety organizations of IT related adverse events or near misses? [30]
  • Does the EHR have the ability to link payments and incentive rewards to the implementation of milestones and performance goals, as well as conduct data queries for support of quality improvement? [31]

Dr. Sittig's Overview of EMR Vendor Selection

  1. Make The Plan
    1. Identify Decision makers
  2. Set Goals
    1. Make a Checklist of what should the EMR accomplish
    2. Map your Workflow
    3. Do a thorough Scan of your environment
  3. Prioritize needs
    1. Make EHR Functionality Checklist
  4. Develop a Request For Proposal (RFP)
  5. Select RFP recipients
    1. For example up to 5 vendors
  6. Narrow the field
    1. EHR Evaluation Form
  7. EHR Vendor Demonstrations
  8. Narrow the field
    1. For example up to 3 vendors
    2. Ask additional questions to vendors
  9. Check references
    1. Examples: consulting KLAS, Gartner etc
  10. Rank the vendors
    1. Functionality vs cost vs vendor characteristics
    2. Vendor selection tools
  11. Site visits
  12. Select a finalist (between the last 2 competitors)
  13. Verify Commitment
    1. Determine approval of selection committees and discuss choice will all the key stakeholders.
    2. If possible repeat the Demo to all the staffs
    3. For uncovered concerns, verify all the references and repeat verification steps if necessary
  14. Formal Contract Negotiation
    1. Ask vendors to spell out all the current as well as the future costs including the vendor time commitments for training and implementation
    2. Ask vendor to put source code in escrow just in case Vendor go out of business
    3. Before signing the software contracts,make sure you have familiar attorney to review
  15. Follow all the above process
    1. Know that the process takes time and do not rush because the end result can be expensive.
    2. Follow the process without skipping any steps.

EHR Evaluation Resources

Select/upgrade to a certified electronic health record vendor Retrieved from http://www.healthit.gov/providers-professionals/ehr-implementation-steps/step-3-select-or-upgrade-certified-ehr

text==References (old, to edit) ==
  1. RI Regional Extension Center. 2011. Vendor members and applicants. Retrieved from http://www.docehrtalk.org/selecting-ehr/for-vendors
  2. The Certification Commission for Healthcare Information Technology (CCHIT). CCHIT Certified 2011 Ambulatory EHR Certification Criteria. May 17, 2011. Available at: https://www.cchit.org/documents/18/158304/CCHIT+Certified+2011+Ambulatory+EHR+Criteria.pdf.
  3. http://mhcc.dhmh.maryland.gov/hit/ehr/Documents/sp.mhcc.maryland.gov/ehr/cmsdemo/februarycmsehrdemonstrationarticle.pdf
  4. McDowell SW, Wahl R, Michelson J. Herding Cats: The Challenges of EMR Vendor Selection. Journal of Healthcare Information Management. 2003; 17(3):17.
  5. Weber, M. (January 2008). "Selecting an EHR, Now What????" wwww.healthconsultingstrategies.com
  6. Eastaugh, S. R. (2013). Electronic Health Records Lifecycle Cost. J Health Care Finance, 39(4), 36-43.
  7. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC2361387/
  8. Finding an EHR vendor: Mistakes are costly, and questions about confidentiality linger. (2011). Alcoholism & Drug Abuse Weekly, 23(42), 1-4.
  9. Jain, V. (2010). Evaluating EHR systems. Health Management Technology, 31(8), 22-24
  10. Hoyt, R. (2014). Health Informatics: Practical Guide for Healthcare and Information Technology Professionals. Informatics Education

References

  1. Selecting the right EMR vendor. http://www.himss.org/files/HIMSSorg/content/files/selectingemr_flyer2.pdf
  2. 2.0 2.1 2.2 2.3 What factors should I consider when selecting a vendor? http://www.healthit.gov/providers-professionals/faqs/what-factors-should-i-consider-when-selecting-vendor
  3. Johnson 2006: Selecting an electronic medical record system for the physician practice. http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_035390.hcsp?dDocName=bok1_035390g
  4. http://www.himss.org/files/HIMSSorg/content/files/Code%2093_15%20questions%20to%20ask%20before%20signing%20an%20EMR-EHR%20agreement_AMA.pdf
  5. MIT Geospactial Data Center: Protecting EMR Data (1 of 2) http://cybersecurity.mit.edu/2012/11/protecting-emr-data-1-of-2/
  6. 6.0 6.1 6.2 HIMSS Computerized Provider Order Entry (CPOE) Wiki. https://himsscpoewiki.pbworks.com/w/page/26349065/Clinical%20Content
  7. 7.0 7.1 7.2 Kansas Department of Health and Environment 2008: Selecting an EHR, Now What??? http://krhis.kdhe.state.ks.us/olrh/Notices.nsf/bf25ab0f47ba5dd785256499006b15a4/720f6f7bfa876f0a862573c600595a2f/$FILE/EHR%20System%20Selection%20Process.pdf
  8. Using an evidence-based approach for system selection at a large academic medical center: lessons learned in selecting an ambulatory EMR at Mount Sinai Hospital. http://www.ncbi.nlm.nih.gov/pubmed/16669592
  9. Carayon, P. Cartmill, R. Blosky, M. Brown, R. Hackenberg, M. Hoonakker, P. Hundt, A. Norfolk, E. Wetterneck, T. Walker, J. (2011).ICU nurses’ acceptance of electronic health records. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3197984/pdf/amiajnl-2010-000018.pdf
  10. Raasikh, . What the others haven't told you: lessons learned to avoid disputes and risks in EHR implementation.http://go.galegroup.com.ezproxyhost.library.tmc.edu/ps/i.do?action=interpret&id=GALE%7CA365889941&v=2.1&u=txshracd2509&it=r&p=HRCA&sw=w&authCount=1
  11. Dowding,D. Turley, M. and Garrido, T. (2012). The impact of an electronic health record on nurse sensitive patient outcomes: an interrupted time series analysis. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3384108/pdf/amiajnl-2011-000504.pdf
  12. Kannry J 2006: Using an Evidence-based Approach for System Selection at a Large Academic Medical Center: Lessons Learned in Selecting an Ambulatory EMR at Mount Sinai Hospital. http://www.ncbi.nlm.nih.gov/pubmed/16669592
  13. 13.0 13.1 13.2 Integrating Electronic Health Records and Clinical Trials http://www.esi-bethesda.com/ncrrworkshops/clinicalresearch/pdf/MichaelKahnPaper.pdf .
  14. Using an evidence-based approach for system selection at a large academic medical center: lessons learned in selecting an ambulatory EMR at Mount Sinai Hospital. http://www.ncbi.nlm.nih.gov/pubmed/16669592
  15. Regional Extension Centers (RECs) http://www.healthit.gov/providers-professionals/regional-extension-centers-recs
  16. 16.0 16.1 16.2 16.3 http://www.healthit.gov/sites/default/files/meaningfulusetablesseries2_110112.pdf
  17. http://www.himss.org/files/HIMSSorg/content/files/Code%2093_15%20questions%20to%20ask%20before%20signing%20an%20EMR-EHR%20agreement_AMA.pdf
  18. EHR and Disaster Recovery. http://www.himss.org/News/NewsDetail.aspx?ItemNumber=6469
  19. What is Your EHR Connectivity Strategy? http://www.corepointhealth.com/sites/default/files/whitepapers/emr-connectivity-strategy-healthcare-interoperability.pdf
  20. AHIMA http://library.ahima.org/xpedio/groups/public/documents/ahima/bok1_047959.hcsp?dDocName=bok1_047959
  21. Carolyn Hartley - signing an EHR contract http://physiciansehr.org/signing-an-ehr-contract-25-tips-to-control-costs.aspx
  22. Signing an EHR contract. Tips to control costs. http://physiciansehr.org/signing-an-ehr-contract-25-tips-to-control-costs.aspx
  23. http://www.himss.org/files/HIMSSorg/content/files/Code%2093_15%20questions%20to%20ask%20before%20signing%20an%20EMR-EHR%20agreement_AMA.pdf
  24. http://www.himss.org/files/HIMSSorg/content/files/Code%2093_15%20questions%20to%20ask%20before%20signing%20an%20EMR-EHR%20agreement_AMA.pdf
  25. Selecting An EHR, Now What????. ftp://ftp.hrsa.gov/ruralhealth/jan082008tacall.pdf
  26. MetaStar https://www.metastar.com/web/professional/docs/DOQ-IT/Vendor/Tools/SiteVisitingTips.doc
  27. EHR Contracts: Key Contract Terms for Users to Understand. http://www.healthit.gov/sites/default/files/ehr_contracting_terms_final_508_compliant.pdf
  28. Certified Health IT Product List (CHPL) list of EMRs. http://oncchpl.force.com/ehrcert
  29. HIMSS Electronic Health Record Association http://www.himssehra.org/ASP/index.asp
  30. Better Patient Safety is Goal of Confidential EHR Error Reports http://www.amednews.com/article/20130724/profession/130729986/8/ .
  31. 31.0 31.1 Health Resources and Services Administration http://www.hrsa.gov/healthit/toolbox/healthitimplementation/implementationtopics/selectcertifiedehr/selectacertifiedehr_7.html
  32. The National Learning Consortium Vendor Evaluation Matrix Tool. http://www.healthit.gov/providers-professionals/implementation-resources/vendor-evaluation-matrix-tool
  33. http://www.himss.org/files/HIMSSorg/content/files/Code%2093_15%20questions%20to%20ask%20before%20signing%20an%20EMR-EHR%20agreement_AMA.pdf