Difference between revisions of "Vendor Selection Criteria"

Revision as of 04:49, 20 September 2010 (view source) Jjortiz1863 (Talk | contribs) (→‎Acquisition and Implementation Cost (25%)) ← Older edit		Latest revision as of 04:57, 3 October 2015 (view source) RoniMV (Talk | contribs) (→‎Vendor assessment plan)
(711 intermediate revisions by more than 100 users not shown)
Line 1:		Line 1:
−	== Example Vendor Evaluation Criteria ==	+	Choosing an [[EMR|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 [[Removing Paper|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.<ref name="Selecting a vendor">Selecting the right EMR vendor. http://www.himss.org/files/HIMSSorg/content/files/selectingemr_flyer2.pdf </ref>
−		+
−	=== Demonstrate Clinical Functionality (25%) ===	+	Here is a list of some of the important considerations when choosing, installing, implementing and upgrading an EMR system. <ref name="factors selecting vendor">What factors should I consider when selecting a vendor? http://www.healthit.gov/providers-professionals/faqs/what-factors-should-i-consider-when-selecting-vendor </ref>
−	* How do EMR software implement HIPAA Privacy and Security Compliance and other regulatory requirements and Local laws.	+
−	* How does EMR software have customer support. Do they have a local workforce, a testing plan,  prioritization of issues	+
−	* Do they have multiple note creation options like template, macros, dictation, voice recognition, hand writing recognition.	+
−	* Does EMR software enable a user to maintain up-to-date problem list? For e.g.: Does it enable a user to electronically record, modify, and retrieve a patient's problem list for longitudinal care (i.e. over multiple visits with the same provider and using the problem list vocabulary standards.) in accordance with certification criteria defined by the ONC’s Interim Final Rule?	+
−	* Does EMR software enable a user to electronically record, modify, and retrieve a patient's active medication list as well as medication history for longitudinal care (i.e. over multiple visits with the same provider and using the medication list vocabulary standards.) in accordance certification criteria defined by the ONC’s Interim Final Rule?	+
−	* If EMR software provides CPOE Functionality then does it enable a user to electronically record, store, retrieve, and manage, at a minimum, the order types like 1) Medications 2) Laboratory, 3) Radiology and Imaging and 4) Provider referrals according to certification criteria defined by the ONC’s Interim Final Rule.	+
−	* Will the system support utilization review with the Milliman and Interqual clinical criteria for Quality Management and discharge planning.	+
−	* Will it support the Clinical pathways for the  Physicians and the Residents for standardization of care processes?	+
−	* Will it have the direct export options of the collected data to the State and Federal Health Departments and for other research sites?	+
−	* How well is the vendor able to demonstrate the clinical functionality required by [your organization]?	+
−	* Is the software flexible enough to meet our current needs and allow for future changes?	+
−	* Specifically how does the system support many 24/7 functions, like medication administration changes in an environment that does not have 24/7 pharmacy or CPOE users on site?	+
−	* Can a demonstration of the software successfully handle a scenario you have prepared?	+
−	* Does the software have functions of supporting clinical decisions?	+
−	* Does the software have functions of assisting nurses in documentations?	+
−	* Is the vendor able to create interfaces for physicians' office EMRs to allow viewing and sharing of clinical, financial (insurance) and other data?	+
−	* Does it have the capability to provide advanced reporting and analytics?	+
−	* What is the ease of use for front-line workers?  Does the user interface modern and able to adapt to different role-based requirements?	+
−	* How easily and quickly can the embedded clinical decision support be modified when new published guidelines or evidence-based medicine studies are published? Will they be responsible for these updates (and at what cost) or will that be our responsibility?	+
−	* Is the vendor software compliant with the Certification Commission of Healthcare Information Technology (CCHIT) criteria?	+
−	* Can the company categorize users according to their characteristic and provide user-centered usability design? Old physicians usually have vision problem and do not like to use keyboard.	+
−	* Can the company provide different levels of decision support based on user working experience? For resident, attending physician, the decision support should be different.	+
−	* What capabilities does the application provide for patients with psychiatric, psychological, or severe behavioral disorders?	+
−	* If your organization's mission includes clinical research, does the software include decision support and data query functions to support research?	+
−	* Can the medical records be easily transferred to another clinic with patient approval?	+
−	* With what other HIT software systems have you established successful interfaces? (organization may use a variety of systems for BCMA, clinical documentation, laboratory data, business functions that need to have data interchange)	+
−	* What capability does the application demonstrate to produce information for patient education?	+
−	* Does the system provide capability for patient portals (web access)?	+
−	* What wireless functions has the system supported?	+
−	* Does the system satisfy security requirements (access control and logging)?	+
−	* Does the system provide configurable workflow options?	+
−	* Does the system provide integration options with other service providers’ systems (hospitals, insurance companies, labs, …)	+
−	* Does the system provide any linkage between clinical notes and structured medical vocabularies?	+
−	* Joan Breuer, Ph.D. 01/27/2010 17:19 The Vendor product must have vocabulary standards such as SNOMED, NDC, LOINC, WHO Drug Dictionary, MeSH, CPT, DRG, and UMLS.	+
−	* Can the EHR vendor provide a standardized system for the market? And at the same time, can they customize the EHR for different clients and requirements?	+
−	* How “personalizable” is the system for individual users to eliminate screen clutter and focus their electronic work process.	+
−	* Is the EHR system Health Level Seven (HL7) ready?	+
−	* Does the EHR vendor have a procedure to integrate other record/data (e.g. personal health record, public health disease surveillance data) into the system?	+
−	*Functionality Matching: Vendor with best functional match. All product selection exercises should start with determining your organization's specific needs.	+
−	* Joan Breuer, Ph.D. 01/27/2010 17:20 There needs to be a plan so In-house developers can work with the Vendor such that all algorithms are carried out seamlessly.	+
−	* Is the system’s data entry interface intuitive for new users?	+
−	* Can the system pull from clinical documentation for billing and patient safety reporting?	+
−	* Does the system have meet specific specialty practice needs of users?	+
−	* How granular is user access to information?  Is the user access hierarchy flexible to accomodate HIPPA standards?	+
−	* Has this software shown to decreased adverse drug reactions when implemented in other facilities?	+
−	* Does the EMR have different modules for different specialties in our healthcare facility?	+
−	* Are these modules “home-grown” at your company or have they been acquired from different companies as your EMR has grown?	+
−	* Are the module structures set or can they be used as a template which can be modified to suit or healthcare facilities needs?	+
−	* Ask all staff who evaluate the system for their assessment of the strengths and weakness of the system as they perceive that the system would apply to the practice.	+
−	* Does the software meet the JCAHO standards?	+
−	* What makes this vendor software better than others?	+
−	* Does the ASP (remote hosting) model provide local caching of active sessions in the event the network connection is lost briefly? If so, what functionality is guaranteed during the network outage?  [[User:MikeField|MikeField]] 20:43, 29 January 2010 (CST)	+
−	* Does the EHR system support disease/domain specific profiles that accommodate the level of data needed to support specialty groups such as mental health, oncology and iridology?	+
−	* Does the vendor offer a Document Imaging component as part of their solution to allow incorporation of paper records that contain previous patient histories?	+
−	* How does the software handle continuity of care as patients transfer from inpatient to outpatient, from one department to another or even between providers? Does the system provide for the writing of discharge notes that list diagnoses, medications and other instructions?	+
−	* Is the system easily configurable to allow customized structured data for efficient coding and revenue capture? Clinical data should not be restricted to some arbitrary minimum.	+
−	* Does the system handle clinical reminders (i.e: immunization, drug monitoring, dosage) ?	+
−	* Does your system handle live pharmacy stock when e-prescribing?	+
−	* The user interace includes interoperability with PACS systems?	+
−	* Are there tools for manually triggering simple alerts/messages between clinicians for situations that may not yet trigger CDS alerts?	+
−	* Does the vendor’s application support external access by physicians, and if so is it part of the system or a user addition?	+
−	* Does the vendor offer any data conversion services? At what cost? How long will it take to transfer the data? [http://www.ama-assn.org American Medical Association]	+
−	* Can the system indicate normal and abnormal lab results when a patient's lab data are reviewed?	+
−	* Can the system display patients' lab data in flowsheets or graphical form to compare results and see trends?	+
−	* Can the system document medication administration?	+
−	* Does the system support the standards identified and recommended by the Health Information Technology Standards Panel in the latest version of its HITSPTP13 document?	+
−	* Does the system support two-factor authentication in alignment with NIST 800-63 Level 3 Authentication?	+
−	* If the system provides access to PHI using a web browser via HTML over HTTP, does the system provide data encryption capability via SSL?	+
−	* Does the system provide the ability to display the patient's allergy list, including the date of entry? (CCHIT certified 2011 Ambulatory EHR criteria # FN 05.12)	+
−	* Does the system provide the ability to display CCD (Continuity of Care Documents) and file them in the EHR, where the summary document must include information on - patient demographics, medication list, and medication allergy list? (CCHIT certified 2011 Ambulatory EHR criteria # IO-AM 10.10)	+
−	=== Acquisition and Implementation Cost (25%) ===	+	==EHR Vendor Selection==
−	* What is the total financial investment required to acquire and fully implement the proposed solution?  Break out costs for the following and detail any time or resource constraints for each item.  If additional resources or time are required, what are the additional costs per unit?	+	===Preliminary selection criteria for EHR vendors===
−	** Application	+
−	** Per-user licenses (and tier pricing, if offered)	+
−	** Database (if treated as a separate item)	+
−	***Data integration from legacy systems	+
−	** Application documentation	+
−	** Annual maintenance agreement	+
−	** Training	+
−	*** End-user	+
−	*** System administrators	+
−	*** In-house developers	+
−	*** Re-current training	+
−	** Professional services:	+
−	*** Project management	+
−	*** Software development or customizations	+
−	*** Technical support	+
−	* What is the estimated time that it will take for the investment of the vendor to pay for itself based on projected savings?	+
−	* Does the system allows to track and detail log audits and transactions made by users?	+
−	* Does the system have the functionality to generate customizable reports given a determinate frequency?	+
−	* What is the cost for upgrading when new releases are available?	+
−	* What is the projected timeline for upgrades? What training support is included if any, and what is covered by the service fees?	+
−	* Upon go-live, business imperatives will define a timeframe within which workflows and processes are to to be run in parallel, until agreed upon metrics/milestones are achieved and the system is signed off into full production: which system is more flexible, less complex, and least disruptive in terms of workflow and process change/adjustments?	+
−	* Implementation costs associated with organizational changes to clinician, administrative, etc. processes should be considered in calculating ROI.	+
−	* At what point are implemenation costs (and other factors) considered too extreme and a GO/NO decision is given serious consideration?	+
−	* All implementation risks must be calculated for "impact and probability" and rank accordingly when analyzing EHR solutions.	+
−	* Does the vendor provide functionality to track ROI? If not what reports can be produced that could help track usage?	+
−	=== Hardware Platform and Technical Requirements (20%) ===	+	According to McDowell, et.al (2003), the primary and vital step for choosing vendors is to narrow your selection from over 400 to as few as 4 vendors based on the following key requirements. <ref name="McDowell"> McDowell, et.al. (2003). Journal of Healthcare Information Management. Herding Cats: The Challenges of EMR Vendor Selection. http://www.providersedge.com/ehdocs/ehr_articles/Herding_Cats-Challenges_of_EMR_Vendor_Selection.pdf.</ref>
−	* Which vendor uses less proprietary systems and has partnerships with established industry players? Are they certified developers for the platform they are using? Is the vendor's system and devleopment lifecycle management aligned with their respective industry partners?	+	*Is the EHR up-to-date with technology?
−	*Compared 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	+
−	* Identify all hardware and system software that would be required to support an implementation of our scope and scale.	+
−	* How well is the vendor able to meet our technical requirements ?	+
−	* How flexible is the vendor to change requirements and what are the cost?	+
−	* How hard is to implement new modules within the system?	+
−	* How well is the vendor able to create and maintain interfaces to our existing systems?	+
−	* How well is the vendor able to migrate our data from actual system to the new, if it is neccesary?	+
−	* Is the vendors's software created with the most adequate developing technology? Platform? Language? Databases?	+
−	* Will we do periodic updates, or will the vendor do this as part of the contract? How often are they released?	+
−	* Do we plan on-site or remote hosting for the system?	+
−	* If we plan to utilize remote hosting, how safe, sound, and accessible are these data?	+
−	* Is the hardware user friendly in all departments? (i.e. nursing, pharmacy, pulmonary,..etc.)	+
−	* Will the vendor provide a mock system for testing?	+
−	* What is the responding duration of each entry and information extraction? Is there any delay?	+
−	* How the data structure for storing data? Is it expandable? Is it easy to be extracted for future analysis?	+
−	* How often does the system need to be updated or serviced?	+
−	* As the technology is changing and the hospital decides to upgrade their hardware, will your system be able to handles these changes or will we have to buy a new program?	+
−	* What language is the vendor's systems software coded in?	+
−	* Scaling:	+
−	** To how many patients has the system been scaled?	+
−	** To how many users has the system been scaled?	+
−	** Has the system been scaled to the size of the evaluating institution?	+
−	** What are the hardware/software licensing implications of growth?	+
−	* Is it necessary to buy (possibly expensive) hardware from the vendor, or can we just install their software on our standard desktop computers (at least for the clients)?	+
−	* 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 upgrade system? For how long?	+
−	* Does the system use DICOM standards for the transmission of image data?	+
−	* How frequently does the vendor provide patch upgrades for the product?	+
−	*Is the system using standards such as Snomed, ICD 10; HL7 Version 2 or 3; HL7 infobutton…)	+
−	* If this is a hosted solution, how many computing facilities does the vendor have capable of hosting the application and where are they located?  What are the vendors' security and disaster recovery plans?	+
−	* How do you handle redundancy for clinical records, like off-site backups and such?	+
−	* For Mobile EMR implementations, how do you handle communication to remote wireless clients? security interfaces? types of devices and minimum requirements?	+
−	* Is the database program one likely to be waning in use and are personnel available at my site with adequate skills/knowledge to provide support post implementation?	+
−	* What database and programming tools (such as instrumented code) are in place for quick problem resolution?	+
−	* If software licenses are sold per physician or user, how are part-time physicians, physician assistants and/or advanced nurse practitioners calculated? [http://www.ama-assn.org American Medical Association]	+
−	=== Implementability (15%) ===	+	*Are the core clinical components fully integrated in the EHR?
−	* How does the vendor compare in KLAS rankings of similar systems and applications?	+	*Are the applications available for inpatient, ambulatory, and outreach settings?
−	* How much time, effort, and resources will be required to successfully implement?	+
−	* What is the vendors track record for successfully implementing its system in similar settings?	+
−	* Do the vendors provide detailed plan for implementation, training and quality control?	+
−	* Will the vendor supply on site support when we "go-live" and how long will they be available?	+
−	* How responsive is the vendor to emergencies?  Do they have a quick and accurate response to support issues?	+
−	* Do they have a backup or alternative plan if the system or partial of the system is not working? The situation could be out of energy or computer virus attack.	+
−	* 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?	+
−	* Will the implementation require a consulting "team" and how much will this cost?	+
−	* Is the vendor sufficiently well known that most health care consulting firms have familiarity with the system?	+
−	* How will legacy patient record data be integrated into the new system?	+
−	* Is the vendor's system compliant with the Health Insurance Portability and Accountability Act (HIPAA)?	+
−	* Is the vendor's system compliant with the Patient Safety and Quality Improvement Act (PSQIA) Patient Safety Rule?	+
−	* How is the evaluation procedure for the approval of the ongoing stages of implementation? How objective will be the defined how  to proceed with the approval and payment?	+
−	* Is the vendor's system compliant with ISO standards for EHRs?	+
−	* Does the system have a proper data recovery plan in case of an crash or any other unexpected event? Can the system be restored without any data loss? Does the vendor have a proper disaster recovery plan?	+
−	* How does a legacy Practice Management System integrate with the EHR system? Is there a list of successful PM vendor integrations?  [[User:MikeField|MikeField]] 20:47, 29 January 2010 (CST)	+
−	* 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?  [[User:MikeField|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?[http://www.ama-assn.org American Medical Association]	+
−	* 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? [http://www.ama-assn.org 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?	+
−	=== Vendor Partnership and On-going viability (10%) ===	+	*Does the vendor have a proven record of financial stability and management reliability?
−	* Please provide audited financial statements for the last five years, including Balance Sheet, Income Statement, and Statement of Cash Flows, as well as any accompanying footnotes.	+
−	* Provide a list of customers who have implemented the systems and applications that you are recommending to us.	+
−	*Create a list of vendor selection criteria, and evaluate the vendors and software: review responses to the RFP; schedule demonstrations; check references; and, use proven tools/templates for assessing and consistently comparing vendors.	+
−	*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).	+	*Does the vendor have a well-established familiarity with large healthcare providers like academic medical centers and tertiary care hospitals?
−	* What type of long-term relationship do we think we can expect from the vendor?	+	*Does the vendor offer an "exit strategy" if they, for unknown reasons, are unable to continue to support your system
−	* How stable vs risky is the company?	+	--- Example will they allow you access to the source code---
−	** Request that the software source code be put in escrow with specific provisions established under which it could be accessed.	+
−	** How long has the company been in business?	+
−	** How large is the company?	+
−	*** How much money did they bring in last quarter? year? 3-years?	+
−	*** How much is the Vendor company revenue in $M?	+
−	*** How much is the vendor company net income in $M?	+
−	*** How much are the total assets and liabilities of the company?	+
−	*** What is the growth strategy of the company?	+
−	*** Are they a private or a public company?	+
−	*** How many employees?	+
−	* How many contracts have they should to Health Care Systems like yours?	+
−	** Can you contact and/or visit a few representative samples?	+
−	* How many new contracts have they signed in the past year?	+
−	* How many uninstall's have been done the last year?	+
−	* Does word of mouth support that the company believes in service after the sale?	+
−	* Joan Breuer, Ph.D. 01/27/2010 17:22 The  HCF needs formal documentation from other HCFs who have used this Vendor’s product signed by the other HCFs’ CEOs, prepared by an attorney.  Note: “Word of mouth” does not stand up in court, especially when we are talking about millions of dollars.	+
−	* What is the vendor's cost per year after implementation?	+
−	* How the vendor provides technical support? On site or remote? Package or individual project based?	+
−	* What provisions exist in the contract for termination and/or penalties if the application does not perform as specified or if the vendor fails to provide any services that are agreed to?	+
−	** Ensure that all application specifications that can be measured or quantified are incorporated into the contract.	+
−	** Ensure that all services verbally offered by the vendor are incorporated into the contract.	+
−	** Does the vendor have service level agreements (SLAs) with appropriate penalties for technical support of the application?	+
−	** Does the system’s implementation plan consider proper risks evaluation and mitigation strategies?	+
−	*An important consideration is whether the vendor or any of its industry partners have done an analysis of processes in healthcare	+
−	* In a HIPAA complaint product, one should consider the feasibility of implementing future mandates. The cost should be considered in terms of both money and time.	+
−	* Obtain references of current customers that are similar in size, have similar patient population, and have similar required functionality needs to your practice and evaluate the ease of implementation, current satisfaction, and costs.	+	===Assess EHR Requirements===
		+	Before diving into specific attributes needed for an EHR system, the general requirements of the EHR must be decided. General requirement decisions may be needed for the following:<ref name = HRSA HIT Vendor Select>How to Select a Certified EHR. http://www.hrsa.gov/healthit/toolbox/healthitimplementation/implementationtopics/selectcertifiedehr/selectacertifiedehr_7.html</ref>
−	* What kind of service level agreements are offered by the vendor and what is their track record for maintaining those SLAs?	+	*Will the EHR be open source or off-the shelf commercial software?
		+	*What EHR functions are needed, such as patient demographic and care management data on patient visits?
		+	*What kind of clinical decision support and reports are critical, important, and desired but not essential?
		+	*What type of consents, authorizations, and directives are needed?
		+	*What interfaces are required to exchange health information with other providers, laboratories, pharmacies, patients, and government disease registries?
		+	*What type and scope of training is expected?
		+	**What levels of training will be needed?
		+	**How many people need to be trained by the vendor?
		+	*What availability for assistance will be necessary?
		+	**How much will be needed for how long?
−	=== Future Vision (5%) ===	+	'''Vendor Assessment'''
−	* Does the vendor have a meaningful Product Lifecycle that defines major and minor releases, their associated costs, and delivery (push or pull) methods?	+	Vendor assessment should be performed systematically in order to meet the goals of the given institution: <ref name= “Chin”> Chin, B. J., & Sakuda, C. M. (2012). Transforming and Improving Health Care through Meaningful Use of Health Information Technology. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3347738/.</ref>
−	* What is the vendor's five-year strategic plan?	+
−	* What percentage of revenue is being re-invested into R&D?	+
−	* How does the company capture/communicate client concerns for re-engineering? i.e. Is this a learning company?	+
−	* What "game changers" are on the drawing board?  Are these related to one of our organization's core goals?	+
−	* Compared 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	+
−	* Lifespan and Staying Power: One should consider the track record of the vendor and viability as a company to sustain the ups and downs of the industry. One sub-criteria in this category often used is how long the vendor has been around.	+
−	* Does the vendor plan to offer interoperability options in the event of a nationally implemented CIS?	+
−	*What is the plan to support smart phone applications to enhance interoperability and custom accessibility of EHR data while maintaining security? (DROID, IPHONE)	+
−	* 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.[http://www.ama-assn.org American Medical Association]	+
−	=== Extra Credit (optional) ===	+	*Determine which EHR vendors are available in the locality.
		+	*Compile a pre-screen questionnaire and survey for local vendors.
		+	*Evaluate request for proposal (RFP) documents and provide vendors with details of any state-specific requirements.
		+	*Assemble a list of pre-qualified vendors based on survey response and RFP.
		+	*Provide a comprehensive request for information document to pre-qualified vendors.
−	* 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?	+	'''Steps to conducting an EHR Assessment'''
−	* 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.	+	*What is your facilities need for an EHR?
−	* 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.	+	*What are your goals for the EHR?
−	* Can the company demonstrate tangible ways that use of the product can increase hospital revenue? If yes, can you validate this/these claims?	+	*What could be the deal breakers
−	* Is the vendor willing to contract to go "at risk" for any part(s) of the contract?	+	*Start narrowing the field on the EHR selection <ref name = HealthIT>http://www.healthit.gov/providers-professionals/faqs/how-do-i-select-vendor</ref>
−	* 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?	+	=== Decide what paths and vendors you need to obtain your EHR===
−	* 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?	+	*Create a checklist with functionalities that your selected EHR must have, is good to have, and must avoid.
−	* Is the vendor capable of integrating it's system with a personal health record and allowing more patient control?	+	*Conduct wide screen to map EHRs that meet all or most of your anticipated functionalities and rank them from high to low.
−	* Can the company provide return on investment analysis?	+	*Request advice from organizations that you know or have collaboration about the process of acquiring and implementing EHRs or find potential organizations that you can collaborate with. <ref name=" HRSA"> HRSA. (n.d.). Organizations Safety Net Providers Can Collaborate With. Retrieved September 24, 2015, from http://www.hrsa.gov/healthit/toolbox/healthitimplementation/implementationtopics/collaborate/collaborate_3.html. </ref>
−	* Does the system have e-prescribing functionality?	+	*Contact or work with your local Health IT offices and regional extension centers for further information and advice.
−	* 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...	+
−	[[Category:EMR]]	+	===  Check out possible vendors through current users ===
−	* How can this EHR be an asset for the solo practitioner who sees this technology primarily as a financial drain?  [[User:MikeField|MikeField]] 20:54, 29 January 2010 (CST)	+	*Find EHR using organizations in your local area or collaborators for their experience and comments.
		+	*Ask questions related to EHRs’ core functionality and relevant information, including but not limited to timeline, cost, impact on interruption of productivity, vendor additional charges or hidden charges, evaluation about return on investment, feedback from clinicians, staff, or other users. <ref name=" HRSA"> </ref>
		+
		+	=== Interview certified EHR vendors ===
		+	*Select 4-5 top ranked certified EHR vendors based on your investigation through your previous screening and inquires.
		+	*Set up phone interview for asking questions as suggested by HRSA website. <ref name=" HRSA"> </ref> For example, type of organization (for-profit or not-for-profit), history or duration in EHR business, other users in local area, costs for different phases and upgrades, and supports.
		+
		+	=== Arrange for vendor demonstrations ===
		+	*Select 2-3 best candidates from previous selection for onsite demonstrations.
		+	*Set up an environment that can mimic a real situation for using selected EHRs in your organization that can test how well each EHR can meet the needs of your organization.
		+	*Test each EHR if it can integrate with other providers or data systems such as public health interface, billing system, drug post market surveillance, CDSSs, and CPOE.
		+	*Cybersecurity protection function.
		+	*Quality control and report function.
		+	*Electronic reporting capability.
		+
		+	===Common Vendor Selection Mistakes===
		+
		+	*Not Enough/Too Much Time
		+	*Not Enough Research
		+	*RFP is a Surprise / Poor Quality / Scoring Unclear
		+	*No Plan for Demos
		+	*Insufficient Due Diligence
		+	*Insufficient Education and Buy-In
		+	*No Rules of Engagement
		+	*Fool Me Once…
		+	*Entering Negotiations Alone, Naked, and Cold<ref name="Miller 2010">Miller,D. Best Practices in Software Vendor Selection http://www.slideshare.net/advantiv/cfakepathbest-practices-in-vendor-selection-advantiv </ref>
		+
		+	=== EMR Selection Tips From A CCRC ===
		+
		+	Retirement community service providers are generally not considered a priority when the government is considering the purchasing and use of electronic medical record (EMR) systems.  While acknowledging the benefits that a new EMR system can bring to their facility, the Jewish Association on Aging (JAA) would like to point out four main challenges it faced with the implementation of the government mandated EMR.
		+	But first they mentioned the positive: the benefits.  These benefits included improved reliability of data, improved workflow, and increased quality of life (QOL) for their residents.  The JAA is a non-profit continuing care retirement community (CCRC).  The impact of the required, updated EMR systems can pose a greater threat to the existence of these non-profit, smaller patient care entities.
		+	This facility would like to share four main challenges which it encounters while trying to update to the new government regulations for EMR regulations.
		+	# The first of these challenges was the large burden of financial funding.  In order for the JAA to overcome this they first informed their board of directors about what the upcoming mandated changes encompassed, and they stressed the positive benefits of the new EMR implementation. With the support of their board of directors, and grants from local foundations, they were able to meet the first challenge.
		+	# The second challenge was to ensure adequate information technology (IT) support for their project.  In order to do this, the JAA hired an IT project manager and an EMR nurse clinician to help develop their specific EMR infrastructure.
		+	# The JAA realized they had to upgrade the CCRC's hardware and networking system.  This was the third challenge they faced in order to implement the demands of a new EMR system.
		+	# The fourth challenge was actually selecting the appropriate system to meet their specific needs as a CCRC.  In order to do this, the JAA utilized an EMR selection tool by the Leading Age Center for Aging Services Technologies (CAST).  This was reported as a major influence in helping them select the appropriate EMR system to meet their specific needs.  They also contracted an outside consulting company to aid in the selection process.
		+
		+	Once the JAA had narrowed their choices down to two possible software candidates, they used a five year total cost of ownership (TCO) to make their final decision.  The consulting company was able to present a comprehensive image of what the TCO would entail.  With this process, the JAA was able to choose the HealthMEDX EMR system.  They found HealthMEDX to have evidence of a proven and successful implementation record for their EMR system.<ref name="Bowers 2015"> Bowers, Lois A.(2015). Secrets to EMR selection: a CCRC shares implementation and selection tips. Long-Term Living; 64(2): 34-37. http://ca3cx5qj7w.search.serialssolutions.com/?ctx_ver=Z39.88-2004&ctx_enc=info%3Aofi%2Fenc%3AUTF-8&rfr_id=info:sid/summon.serialssolutions.com&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Secrets+to+EMR+success%3A+a+CCRC+shares+implementation+and+selection+tips&rft.jtitle=Long-Term+Living&rft.au=Bowers%2C+Lois+A&rft.date=2015-03-01&rft.pub=Vendome+Group+LLC&rft.issn=1940-9958&rft.eissn=2168-4561&rft.volume=64&rft.issue=2&rft.spage=34&rft.externalDBID=IOF&rft.externalDocID=410137947&paramdict=en-US</ref>
		+
		+	== Planning and Implementation Approach==
		+	[[Vendor Selection Criteria: Planning and Implementation Approach]]
		+
		+	== Planning and Implementation Approach==
		+	[[Vendor Selection Criteria: Planning and Implementation Approach]]
		+
		+	== Core clinical features ==
		+	[[Vendor Selection Criteria: Core clinical features]]
		+
		+	There are 8 "Core Clinical Functions" That EHRs should have. With these core features the EHR should be usable in any (NON-specialized) clinic
		+
		+	1. Health information and data
		+
		+	2. Results management
		+
		+	3. Orders management
		+
		+	4. Decision support
		+
		+	5. Electronic communications and connectivity
		+
		+	6. Patient support
		+
		+	7. Administrative processes
		+
		+	8. Reporting and population health management  <ref name= "core">http://www.mmafoundation.org/portals/mmaf/HIT_Toolkit/Printpages/select3.pdf</ref>
		+
		+	== Personal Health Records ==
		+
		+	'''Personal Health Records''' is a vendor selection criteria important for patients in order to have access to personal information through [[Electronic Health Records|(EHR)]]. [[Personal health records |(PHR)]] is an electronic system designed and integrated into the EHR system for patients to maintain and manage their own health information.
		+	* PHR will improve health care cost
		+	* PHR will improve quality and efficiency
		+	* With standalone PHRs, patients fill in the information from their own records and memories, and the information is stored on patients' computers or the Internet.
		+	* Tethered or connected PHRs are linked to a specific health care organization's EHR system or to a health plan's information system. The patient accesses the information through a secure portal and for instance will able to track their lab results from the past years. <ref name= "hit">http://www.healthit.gov/providers-professionals/patient-participation</ref>
		+
		+	According to Phillips, et al (2015 ) '''Strategic Suggestions for PHR''' are to fully integrate EHR and PHR and "improve patient and population health". <ref name= "family medicine and phi">A family medicine health technology strategy for achieving the Triple Aim for US health care,http://www-ncbi-nlm-nih-gov.ezproxyhost.library.tmc.edu/pubmed/2638212, Phillips, R. L., Bazemore, A. W., & DeVoe, J. E. (2015). </ref>
		+	* A shared primary care health IT center will be necessary for control, privacy and security.
		+	* Meaningful primary care quality measures and capacity to assess/report them.
		+	* Increased primary care technology research: to advance and constantly improve health care to patients.
		+	* A national family medicine registry, every patient should have a primary care provider.
		+	* Enhancement of family physicians' technology leadership
		+	* Championing patient-centered technology functionality. Phillips, et al (2015) <ref name= "family medicine and phi"></ref>
		+
		+	== IT and technical requirements ==
		+	[[Vendor Selection Criteria: IT and technical requirements]]
		+
		+	== Usability ==
		+	[[Vendor Selection Criteria: Usability]]
		+
		+	Previous studies demonstrated how usability measurements can be applied to the evaluation of EHR systems; however, most of these studies were conducted post implementation. If significant problems have been discovered with usability, at this point in the system development
		+	life cycle it is usually too late to make any major modifications to the EHR system. Therefore, it is important to consider the usability criteria in early stages of the EHR implementation, and particularly during the process of vendor and product selection.  <ref name="Saiku"> I. Saiku. Including usability in the procurement process of healthcare IT Systems. <http://www.soberit.hut.fi/T-121/shared/thesis/di-Inkeri-Saiku.pdf</ref>
		+
		+	== Interoperability ==
		+	[[Vendor Selection Criteria:  Interoperability]]
		+
		+
		+
		+	== Future relationship with vendor ==
		+	[[Vendor Selection Criteria: Future relationship with vendor]]
		+
		+	Purchasing an EMR is a long-term decision with many hidden costs to consider.
		+
		+	== Certification and meaningful use ==
		+	[[Vendor Selection Criteria: Certification and meaningful use]]
		+
		+	Selecting an EMR is like buying a house where it needs thorough inspection/evaluation and making sure that every component is functional and meeting all the related requirements prior to approval and signing of contract. One must be able to confirm whether an EHR system is HIE certified or not.<ref name="EHR/HIE Interoperability Workgroup">EHR/HIE: Interoperability http://interopwg.org/certification.html/</ref> In addition, meaningful use should be assessed.<ref name="HIT.gov">Meaningful Use Definition and Objectives http://www.healthit.gov/providers-professionals/meaningful-use-definition-objectives</ref>
		+
		+	==Why need vendor certification==
		+	#certification assures certain level of quality of EHR.
		+	#provides sustainability and support by vendor.
		+	# CCHIT <ref name="CCHIT">CCHIT website.http://www.cchit.org </ref>-Certification Commission for Healthcare Information Technology is one of the well known certification process in the market now.
		+	#The goals of CCHIT mentioned by Handel et. al are
		+	*Lower the risks of investment in new EHR
		+	*Assure compatibility of EHRs
		+	*With improved quality, providing incentives for EHR adoption.
		+	*Protect patient privacy
		+
		+	== Vendor assessment ==
		+	[[Vendor Selection Criteria: Vendor assessment]]
		+
		+	Most vendors typically fall into one of the three categories:
		+
		+	# Vendors that develop their own software organically on a single source code, one database, single instance.
		+	# Vendors that may operate under one name, but offer several acquired products, including some custom programs.
		+	# Vendors that have been acquired/sold/merged as a means to stay more competitive.
		+
		+	The first category of vendor is less likely to run into major market conflicts to keep its software modern and compliant with regulations. Vendors that operate on a single source code have far less difficultly staying current and/or responding to rapid changes in the market and mandated IT standards.<ref>Types of vendors http://www.greenwayhealth.com/wp-content/uploads/2013/03/Replacing_an_EHR-Coker_Greenway_white_paper.pdf</ref> However, selection of a vendor also depends on the size of the organization, and the list of services they need. A larger health care organization might need more services, hence the vendor they select must offer multiple products.
		+
		+
		+
		+	Goals
		+
		+	The setting of goals is a critical component of the assessment of EHRs.  It is suggested that the goals should be according to the following format
		+
		+	Specific – Achieving the goal would make a difference for our patients and our organization.
		+
		+	Measurable – We can quantify the current level and the target goal.
		+
		+	Attainable – Although the goal may be a stretch, we can achieve it.
		+
		+	Relevant – The goal is worth the effort.
		+
		+	Time bound – There are deadlines and opportunities to celebrate success
		+
		+	These are referred to as the "SMART" Goals <ref>SMART http://www.healthit.gov/providers-professionals/faqs/what-types-goals-should-i-set-during-readiness-assessment-process</ref>
		+
		+	===Vendor assessment plan===
		+	When vendors have been short listed, the following type of analysis should be included in the assessment process.  Each vendor should be assessed in a structured process with a ranking of 1-7 for each vendor and criteria:
		+	*Functionality Analysis - clinical criteria, workflow processes and outcomes functionality are some of the features that could be the focus
		+	*CPR attributes assessment - the vendor's claims of their product's ability to fulfill the computer based patient record attributes and sub-attributes could cross-references and used to contractually bind the vendor to deliver the actual functionality
		+	*Technology assessment - stakeholders from the IT architecture department should rank the vendor and product against their list of technical criteria
		+	*Cost of ownership - while it may to difficult to assess across vendors for this, initial cost can be divided into capital and operating cost to make this more possible
		+	*vendor comparison analysis - structure cross vendor comparison analysis should be conducted by the decision team
		+	* Risk Analysis - the specific risk should be objectively analyzed
		+
		+	The selection team should assess the vendors with ranking against the various criteria as this ensures the team focus on objective analysis of each of the vendors.<ref name ="Herding Cats"> Herding Cats: The Challenges of EMR Vendor Selection http://www.providersedge.com/ehdocs/ehr_articles/Herding_Cats -Challenges_of_EMR_Vendor_Selection.pdf</ref>
		+
		+	== Go live support ==
		+	[[Vendor Selection Criteria: Go live support]]
		+
		+	== Evaluation post implementation ==
		+	[[Vendor Selection Criteria: Evaluation post implementation]]
		+
		+	== References ==
		+	<references/>

---

Latest revision as of 04:57, 3 October 2015

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]

EHR Vendor Selection

Preliminary selection criteria for EHR vendors

According to McDowell, et.al (2003), the primary and vital step for choosing vendors is to narrow your selection from over 400 to as few as 4 vendors based on the following key requirements. ^[3]

• Is the EHR up-to-date with technology?

• Are the core clinical components fully integrated in the EHR?

• Are the applications available for inpatient, ambulatory, and outreach settings?

• Does the vendor have a proven record of financial stability and management reliability?

• Does the vendor have a well-established familiarity with large healthcare providers like academic medical centers and tertiary care hospitals?

• Does the vendor offer an "exit strategy" if they, for unknown reasons, are unable to continue to support your system

   --- Example will they allow you access to the source code---

Assess EHR Requirements

Before diving into specific attributes needed for an EHR system, the general requirements of the EHR must be decided. General requirement decisions may be needed for the following:^[4]

• Will the EHR be open source or off-the shelf commercial software?
• What EHR functions are needed, such as patient demographic and care management data on patient visits?
• What kind of clinical decision support and reports are critical, important, and desired but not essential?
• What type of consents, authorizations, and directives are needed?
• What interfaces are required to exchange health information with other providers, laboratories, pharmacies, patients, and government disease registries?
• What type and scope of training is expected?
  • What levels of training will be needed?
  • How many people need to be trained by the vendor?
• What availability for assistance will be necessary?
  • How much will be needed for how long?

Vendor Assessment

Vendor assessment should be performed systematically in order to meet the goals of the given institution: ^[5]

• Determine which EHR vendors are available in the locality.
• Compile a pre-screen questionnaire and survey for local vendors.
• Evaluate request for proposal (RFP) documents and provide vendors with details of any state-specific requirements.
• Assemble a list of pre-qualified vendors based on survey response and RFP.
• Provide a comprehensive request for information document to pre-qualified vendors.

Steps to conducting an EHR Assessment

• What is your facilities need for an EHR?
• What are your goals for the EHR?
• What could be the deal breakers
• Start narrowing the field on the EHR selection ^[6]

Decide what paths and vendors you need to obtain your EHR

• Create a checklist with functionalities that your selected EHR must have, is good to have, and must avoid.
• Conduct wide screen to map EHRs that meet all or most of your anticipated functionalities and rank them from high to low.
• Request advice from organizations that you know or have collaboration about the process of acquiring and implementing EHRs or find potential organizations that you can collaborate with. ^[7]
• Contact or work with your local Health IT offices and regional extension centers for further information and advice.

Check out possible vendors through current users

• Find EHR using organizations in your local area or collaborators for their experience and comments.
• Ask questions related to EHRs’ core functionality and relevant information, including but not limited to timeline, cost, impact on interruption of productivity, vendor additional charges or hidden charges, evaluation about return on investment, feedback from clinicians, staff, or other users. ^[7]

Interview certified EHR vendors

• Select 4-5 top ranked certified EHR vendors based on your investigation through your previous screening and inquires.
• Set up phone interview for asking questions as suggested by HRSA website. ^[7] For example, type of organization (for-profit or not-for-profit), history or duration in EHR business, other users in local area, costs for different phases and upgrades, and supports.

Arrange for vendor demonstrations

• Select 2-3 best candidates from previous selection for onsite demonstrations.
• Set up an environment that can mimic a real situation for using selected EHRs in your organization that can test how well each EHR can meet the needs of your organization.
• Test each EHR if it can integrate with other providers or data systems such as public health interface, billing system, drug post market surveillance, CDSSs, and CPOE.
• Cybersecurity protection function.
• Quality control and report function.
• Electronic reporting capability.

Common Vendor Selection Mistakes

• Not Enough/Too Much Time
• Not Enough Research
• RFP is a Surprise / Poor Quality / Scoring Unclear
• No Plan for Demos
• Insufficient Due Diligence
• Insufficient Education and Buy-In
• No Rules of Engagement
• Fool Me Once…
• Entering Negotiations Alone, Naked, and Cold^[8]

EMR Selection Tips From A CCRC

Retirement community service providers are generally not considered a priority when the government is considering the purchasing and use of electronic medical record (EMR) systems. While acknowledging the benefits that a new EMR system can bring to their facility, the Jewish Association on Aging (JAA) would like to point out four main challenges it faced with the implementation of the government mandated EMR. But first they mentioned the positive: the benefits. These benefits included improved reliability of data, improved workflow, and increased quality of life (QOL) for their residents. The JAA is a non-profit continuing care retirement community (CCRC). The impact of the required, updated EMR systems can pose a greater threat to the existence of these non-profit, smaller patient care entities. This facility would like to share four main challenges which it encounters while trying to update to the new government regulations for EMR regulations.

1. The first of these challenges was the large burden of financial funding. In order for the JAA to overcome this they first informed their board of directors about what the upcoming mandated changes encompassed, and they stressed the positive benefits of the new EMR implementation. With the support of their board of directors, and grants from local foundations, they were able to meet the first challenge.
2. The second challenge was to ensure adequate information technology (IT) support for their project. In order to do this, the JAA hired an IT project manager and an EMR nurse clinician to help develop their specific EMR infrastructure.
3. The JAA realized they had to upgrade the CCRC's hardware and networking system. This was the third challenge they faced in order to implement the demands of a new EMR system.
4. The fourth challenge was actually selecting the appropriate system to meet their specific needs as a CCRC. In order to do this, the JAA utilized an EMR selection tool by the Leading Age Center for Aging Services Technologies (CAST). This was reported as a major influence in helping them select the appropriate EMR system to meet their specific needs. They also contracted an outside consulting company to aid in the selection process.

Once the JAA had narrowed their choices down to two possible software candidates, they used a five year total cost of ownership (TCO) to make their final decision. The consulting company was able to present a comprehensive image of what the TCO would entail. With this process, the JAA was able to choose the HealthMEDX EMR system. They found HealthMEDX to have evidence of a proven and successful implementation record for their EMR system.^[9]

Planning and Implementation Approach

Vendor Selection Criteria: Planning and Implementation Approach

Planning and Implementation Approach

Vendor Selection Criteria: Planning and Implementation Approach

Core clinical features

Vendor Selection Criteria: Core clinical features

There are 8 "Core Clinical Functions" That EHRs should have. With these core features the EHR should be usable in any (NON-specialized) clinic

1. Health information and data

2. Results management

3. Orders management

4. Decision support

5. Electronic communications and connectivity

6. Patient support

7. Administrative processes

8. Reporting and population health management ^[10]

Personal Health Records

Personal Health Records is a vendor selection criteria important for patients in order to have access to personal information through (EHR). (PHR) is an electronic system designed and integrated into the EHR system for patients to maintain and manage their own health information.

• PHR will improve health care cost
• PHR will improve quality and efficiency
• With standalone PHRs, patients fill in the information from their own records and memories, and the information is stored on patients' computers or the Internet.
• Tethered or connected PHRs are linked to a specific health care organization's EHR system or to a health plan's information system. The patient accesses the information through a secure portal and for instance will able to track their lab results from the past years. ^[11]

According to Phillips, et al (2015 ) Strategic Suggestions for PHR are to fully integrate EHR and PHR and "improve patient and population health". ^[12]

• A shared primary care health IT center will be necessary for control, privacy and security.
• Meaningful primary care quality measures and capacity to assess/report them.
• Increased primary care technology research: to advance and constantly improve health care to patients.
• A national family medicine registry, every patient should have a primary care provider.
• Enhancement of family physicians' technology leadership
• Championing patient-centered technology functionality. Phillips, et al (2015) ^[12]

IT and technical requirements

Vendor Selection Criteria: IT and technical requirements

Usability

Vendor Selection Criteria: Usability

Previous studies demonstrated how usability measurements can be applied to the evaluation of EHR systems; however, most of these studies were conducted post implementation. If significant problems have been discovered with usability, at this point in the system development life cycle it is usually too late to make any major modifications to the EHR system. Therefore, it is important to consider the usability criteria in early stages of the EHR implementation, and particularly during the process of vendor and product selection. ^[13]

Interoperability

Vendor Selection Criteria: Interoperability

Future relationship with vendor

Vendor Selection Criteria: Future relationship with vendor

Purchasing an EMR is a long-term decision with many hidden costs to consider.

Certification and meaningful use

Vendor Selection Criteria: Certification and meaningful use

Selecting an EMR is like buying a house where it needs thorough inspection/evaluation and making sure that every component is functional and meeting all the related requirements prior to approval and signing of contract. One must be able to confirm whether an EHR system is HIE certified or not.^[14] In addition, meaningful use should be assessed.^[15]

Why need vendor certification

1. certification assures certain level of quality of EHR.
2. provides sustainability and support by vendor.
3. CCHIT ^[16]-Certification Commission for Healthcare Information Technology is one of the well known certification process in the market now.
4. The goals of CCHIT mentioned by Handel et. al are

• Lower the risks of investment in new EHR
• Assure compatibility of EHRs
• With improved quality, providing incentives for EHR adoption.
• Protect patient privacy

Vendor assessment

Vendor Selection Criteria: Vendor assessment

Most vendors typically fall into one of the three categories:

1. Vendors that develop their own software organically on a single source code, one database, single instance.
2. Vendors that may operate under one name, but offer several acquired products, including some custom programs.
3. Vendors that have been acquired/sold/merged as a means to stay more competitive.

The first category of vendor is less likely to run into major market conflicts to keep its software modern and compliant with regulations. Vendors that operate on a single source code have far less difficultly staying current and/or responding to rapid changes in the market and mandated IT standards.^[17] However, selection of a vendor also depends on the size of the organization, and the list of services they need. A larger health care organization might need more services, hence the vendor they select must offer multiple products.

Goals

The setting of goals is a critical component of the assessment of EHRs. It is suggested that the goals should be according to the following format

Specific – Achieving the goal would make a difference for our patients and our organization.

Measurable – We can quantify the current level and the target goal.

Attainable – Although the goal may be a stretch, we can achieve it.

Relevant – The goal is worth the effort.

Time bound – There are deadlines and opportunities to celebrate success

These are referred to as the "SMART" Goals ^[18]

Vendor assessment plan

When vendors have been short listed, the following type of analysis should be included in the assessment process. Each vendor should be assessed in a structured process with a ranking of 1-7 for each vendor and criteria:

• Functionality Analysis - clinical criteria, workflow processes and outcomes functionality are some of the features that could be the focus
• CPR attributes assessment - the vendor's claims of their product's ability to fulfill the computer based patient record attributes and sub-attributes could cross-references and used to contractually bind the vendor to deliver the actual functionality
• Technology assessment - stakeholders from the IT architecture department should rank the vendor and product against their list of technical criteria
• Cost of ownership - while it may to difficult to assess across vendors for this, initial cost can be divided into capital and operating cost to make this more possible
• vendor comparison analysis - structure cross vendor comparison analysis should be conducted by the decision team
• Risk Analysis - the specific risk should be objectively analyzed

The selection team should assess the vendors with ranking against the various criteria as this ensures the team focus on objective analysis of each of the vendors.^[19]

Go live support

Vendor Selection Criteria: Go live support

Evaluation post implementation

Vendor Selection Criteria: Evaluation post implementation

References

1. ↑ Selecting the right EMR vendor. http://www.himss.org/files/HIMSSorg/content/files/selectingemr_flyer2.pdf
2. ↑ 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. ↑ McDowell, et.al. (2003). Journal of Healthcare Information Management. Herding Cats: The Challenges of EMR Vendor Selection. http://www.providersedge.com/ehdocs/ehr_articles/Herding_Cats-Challenges_of_EMR_Vendor_Selection.pdf.
4. ↑ How to Select a Certified EHR. http://www.hrsa.gov/healthit/toolbox/healthitimplementation/implementationtopics/selectcertifiedehr/selectacertifiedehr_7.html
5. ↑ Chin, B. J., & Sakuda, C. M. (2012). Transforming and Improving Health Care through Meaningful Use of Health Information Technology. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3347738/.
6. ↑ http://www.healthit.gov/providers-professionals/faqs/how-do-i-select-vendor
7. ↑ ^{7.0 7.1 7.2} HRSA. (n.d.). Organizations Safety Net Providers Can Collaborate With. Retrieved September 24, 2015, from http://www.hrsa.gov/healthit/toolbox/healthitimplementation/implementationtopics/collaborate/collaborate_3.html.
8. ↑ Miller,D. Best Practices in Software Vendor Selection http://www.slideshare.net/advantiv/cfakepathbest-practices-in-vendor-selection-advantiv
9. ↑ Bowers, Lois A.(2015). Secrets to EMR selection: a CCRC shares implementation and selection tips. Long-Term Living; 64(2): 34-37. http://ca3cx5qj7w.search.serialssolutions.com/?ctx_ver=Z39.88-2004&ctx_enc=info%3Aofi%2Fenc%3AUTF-8&rfr_id=info:sid/summon.serialssolutions.com&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Secrets+to+EMR+success%3A+a+CCRC+shares+implementation+and+selection+tips&rft.jtitle=Long-Term+Living&rft.au=Bowers%2C+Lois+A&rft.date=2015-03-01&rft.pub=Vendome+Group+LLC&rft.issn=1940-9958&rft.eissn=2168-4561&rft.volume=64&rft.issue=2&rft.spage=34&rft.externalDBID=IOF&rft.externalDocID=410137947&paramdict=en-US
10. ↑ http://www.mmafoundation.org/portals/mmaf/HIT_Toolkit/Printpages/select3.pdf
11. ↑ http://www.healthit.gov/providers-professionals/patient-participation
12. ↑ ^{12.0 12.1} A family medicine health technology strategy for achieving the Triple Aim for US health care,http://www-ncbi-nlm-nih-gov.ezproxyhost.library.tmc.edu/pubmed/2638212, Phillips, R. L., Bazemore, A. W., & DeVoe, J. E. (2015).
13. ↑ I. Saiku. Including usability in the procurement process of healthcare IT Systems. <http://www.soberit.hut.fi/T-121/shared/thesis/di-Inkeri-Saiku.pdf
14. ↑ EHR/HIE: Interoperability http://interopwg.org/certification.html/
15. ↑ Meaningful Use Definition and Objectives http://www.healthit.gov/providers-professionals/meaningful-use-definition-objectives
16. ↑ CCHIT website.http://www.cchit.org
17. ↑ Types of vendors http://www.greenwayhealth.com/wp-content/uploads/2013/03/Replacing_an_EHR-Coker_Greenway_white_paper.pdf
18. ↑ SMART http://www.healthit.gov/providers-professionals/faqs/what-types-goals-should-i-set-during-readiness-assessment-process
19. ↑ Herding Cats: The Challenges of EMR Vendor Selection http://www.providersedge.com/ehdocs/ehr_articles/Herding_Cats -Challenges_of_EMR_Vendor_Selection.pdf