NEGOTIATING HEALTH IT CONTRACTS
|
|
- Candace McBride
- 7 years ago
- Views:
Transcription
1 NEGOTIATING HEALTH IT CONTRACTS Physicians and Hospitals Law Institute, Las Vegas, NV, February 2015 American Health Lawyers Association Dawn R. Crumel 1 Shipman & Goodwin LLP Washington, DC Introduction When negotiating health IT agreements physician organizations and hospitals ( Provider(s) ) often find vendors unwilling to negotiate material terms that have financial, operational and regulatory impact on the Provider. While the Request for Proposal (RFP) process may slow down the contracting process, it provides Providers a boost in bargaining position and results in having vendors agreeing to contractual terms prior to being awarded a contract. In addition, a Provider may consider negotiating with more than one vendor at the same time, so that the Provider is not wedded to a particular vendor if negotiations are not as desired despite the RFP process. This paper/outline is intended to address key aspects Providers should consider in negotiating Health IT agreements. The corresponding paper, Critical Requirements for Creating a RFP for HIT Systems, from Jeffrey Daigrepont of the Coker Group addresses the RFP process and using leverage to negotiate better Health IT contracts. Roadmap Prior to purchasing any additional health IT software, a Provider should have a health IT roadmap. A roadmap enables the Provider to look at its long term goals for functionality and see how each solution interconnects. It is advisable for the Provider to evaluate how each solution the Provider currently has works and interfaces with other solutions the Provider has. Any additional solutions should be compatible with the current solutions and help the Provider achieve its IT functionality goals in the roadmap. This consideration is especially important when considering issues of interoperability as discussed herein. Definitions Critical aspects of the Health IT contract turn on the definitions. The Provider should indicate upfront and in writing that the responses to the RFP will be included in the definitions in the 1 The views expressed herein are solely of the author, and should not be attributed to any current or former employer or client. This outline may be used, in whole or in part, in other presentations and articles by the author. The author would like to acknowledge the assistance from Cherie Pardue and Bill Roberts in preparing this paper. 1
2 contract and that the vendor may not make changes after the negotiations to the RFP responses. Issues such as the extent of the license, what the documentation is, when the agreement starts and what warranties include depend on key elements in the definitions. It is critical to include the IT professionals of the Provider in the contract discussions to ensure the descriptions are detailed enough. Key elements to include within the definitions are network components, updates, enhancements, new releases, technical and functional specifications, interfaces, and customizations. The Provider should ensure there is substantial detail in the documentation description as most aspects of functionality and performance will hinge on the specification of the documentation. In addition, some contracts do not clearly define the products and services the vendor will provide, raising the possibility that the vendor later will charge the Provider additional fees for services thought to be included in the original price. Many contracts carefully limit the exact services the vendor will provide including maintenance services. A health IT contract with many maintenance exclusions will result in the Provider incurring additional costs down the road when it needs services that are outside the scope of the definition. Vendors make their bread and butter in the maintenance provisions of health IT contracts. To avoid additional costs outside the basic service fees, the defined services to be provided should be clearly understood and not have unreasonable limitations within the definition. Defining User can be a critical aspect of a health IT contract. Vendors may price contracts on the basis of the number of authorized users or the number of concurrent users. User generally is defined as a specific individual, rather than defined as interchangeable among different people. The Provider will need to pay additional fees to allow any additional individuals access to the data. Another limitation in the definition of User is a particular geographic location. The contract should expressly allow for use in all locations with language addressing expansion or changes in the Provider s location. To illustrate the importance of defining User as broadly as possible, the following sample user license shows how costs pivot on the definition of User: for permitted users to use the software only for customer s (and all permitted users) internal business purposes related to operating the facilities (i) the software may be installed only on equipment located at the facilities (except for back up); (ii) the software may be used only at the facilities (except for back up) and (iii) the software is limited to the number of users identified. Fees The Provider should understand the different sources of vendor fees and negotiate to predetermine those fees in the contract based upon contracted rates rather than market rates the vendor charges at the time of service. Types of fees include: 2
3 Licensing Fees - The Provider pays this fee in order to utilize the vendor s software. Equipment Fees- Providers should account for any additional costs for installation on hardware or third party costs in operating equipment. Maintenance Fees - The vendor charges fees to maintain the software and equipment to the specifications. The contract should define the level of service. This fee should specify any fees associated with the vendor s upgrades to new versions of the software. Professional Services Fees - The Provider pays the vendor in exchange for consulting services and similar professional services. These fees should be contracted rather than market rates. Implementation Service Fees - The vendor charges the Provider for services to set up the software, including data conversion, software loading, equipment installation, software testing, services set-up and training. The level of training should be specified including the length of time training will be provided, whether the training will be onsite or at the vendor s location, the costs of travel for the vendor s trainers or the Provider s staff, and the cost of any additional training. The cost of implementation is often unexpectedly high due to lack of transparency. Interface Fees - The vendor charges for developing interfaces to other health IT systems. Additional Features - Providers should clarify which services and features a base quote includes and any additional subscription or other fees. The vendor will want to allow for increased fees at a later date. It is advisable to limit any increase in fees by the amount and frequency. For instance, the amount of any such increase will not exceed 3% or the percentage annual increase in the Consumer Price Index, and fees may not increase more than annually after the fifth anniversary of the go - live date. Licensing The license provides for the quantity of the service to be provided. It often is quantified by the number of users. It is important to the Provider to ensure as broad of a license as possible. Otherwise, the risk is that there can be payment of significant additional license fees, that the provider is liable for financial penalties for violating the license agreement, and that the license may be terminated for breach. The Provider should ensure the scope of the license covers: all potential users, each computer housing the software and the geographical location. The vendor is unlikely to allow for unlimited users; however, there needs to be allowance for a broad number of users such as affiliates who would use the software in conjunction with the Provider. It is better not to define the scope of users with a specific list of entities owned by the Provider. The definition should include any entity owed or operated so that entities formed at a later date fall under the license. Additional important considerations regarding the license include: The right to utilize in the event of a merger or acquisition; 3
4 The term of the license: fixed, annual, perpetual? Is there a single upfront payment or are there license fees as long as the license remains in effect? Is any third-party software included in the system that may require a sub-license? Negotiate the right to get approval for modifications through the vendor. If the Provider modifies without permission indemnification protection may be lost. Ensure right to have a copy for training, implementation testing and backup of data. The contract should guarantee back up service, as well as training on how to access the stored data in such case as the need arises. The vendor is likely to audit the license use of the software. The purpose of the audit is to determine if there are more users than permitted by the license. If the vendor finds more users, then the provider may owe additional fees. The provider should negotiate the parameters of the audit which can be resource intensive but also to ensure the audit is not overly broad. It is important for the Provider to limit the audit to the scope of the license and to negotiate that all costs associated with audit are covered by the vendor. Another consideration is that there be sufficient time and notice for the audit, and that it be conducted in a manner than does not disrupt the business of Provider. Acceptance Testing It is critical to use acceptance testing to determine whether the vendor provided the agreed upon product. Acceptance testing provisions include the acceptance criteria and the testing process. Providers should not agree to general acceptance testing. Acceptance testing criteria include the product definition, documentation, the functional and performance expectations, and warranties. The testing process should detail the triggers for different levels of testing, when parties report deficiencies and the correction of deficiencies and retesting. Certain payment commitments should be withheld until acceptance testing is final, the first productive use or a period after the go-live date. To illustrate, sample acceptance language is the following: Customer will have the right to test any software delivered by Vendor hereunder to ensue that it performs in all material respects in accordance with the applicable documentation. Such testing will commence on the software delivery date and will end days after the go live date as may be adjusted as provided herein (Testing Period). Prior to the expiration of the Testing Period, Customer may provide Vendor with a reasonably detailed written report identifying any material nonconformance in the performance of the software from the documentation. In such event, the Testing Period will continue and Vendor has days to correct the material nonconformities submitted. Once the software corrections have been delivered to the Customer, Customer has days to test. If Vendor is unable to correct the material nonconformities within _ days, written notification and explanation must be submitted to Customer along with a commercially practicable resolution timeline. Both parties will cooperate in good faith to resolve any issues 4
5 and seek mutual agreement on corrected software delivery timeframe. However, if mutual agreement cannot be reached, Customer has the right to invoke software quality warranties. Payment Milestones, Uptime Guarantees, Warranties Often parties negotiate payment milestones, uptime guarantees and warranties into agreements. Payment milestones allow payments to link to a vendor s performance obligations rather than calendar dates. These milestones should be coordinated with detailed acceptance testing criteria. For instance, 20 percent of the contract price may be paid upon execution, 20 percent upon delivery, 40 percent upon completion of installation, and the remaining 20 percent upon final acceptance or 45 days after go-live. Payment milestones give Providers a better negotiating position than payment at execution or within 45 days after execution, for example. If the vendor pays the full amount due within the first 90 days after execution but implementation has been delayed, the vendor will have less incentive to resolve diligently the implementation issues. Providers should negotiate uptime guarantees from the vendor. Vendors frequently warrant that the software will be up a certain percentage of time and performing pursuant to the documentation. In the event, there is downtime above a certain percentage of time, then the vendor provides the customer with credit for future services. What parties may not realize until implementation is that there may not be a meeting of the minds for process for recording downtime. The software may be up and running, except one segment of the software is not working. To correct the one malfunction of the singular segment of the software, the whole system may need to go into downtime. The vendor may not count this as downtime as the software can be up and running and is only down to correct a specific issue. Warranties are likely to be limited in a vendor form agreement. In negotiating a more extended warranty Providers should address system compliance with functional and performance specifications, compatibility of components, viruses and disabling devices, prevention of unauthorized access or usage of system, and availability of support and maintenance. Warranties are only as good as the documentation definition. The more detailed the documentation description there is the less likely there is to be a dispute over the extent of the warranty. Enhancements, Support and Maintenance Like most technology health IT rapidly changes. It is important for Providers to secure enhancements and updates in an included price in the contract. Moreover, the cost of implementing enhancements and updates is very costly and often over looked in the contract process. Often a Provider does not have the resources to pay for all of the updates. To counter the cost of enhancement implementation costs, Providers may want to negotiate free labor to future upgrades or negotiate the cost of maintenance down in exchange for enhancement implementation fees. 5
6 Support and maintenance are critical implementation factors. The contract should address and clearly define the hours and days support is available and what types of assistance are available. The contract should also address the consequences if the vendor does not meet the support requirements. Maintenance may add significant additional costs to the vendor contract, including for new software releases, new functional capabilities, and other product upgrades or enhancements. It is important that the contract specify what is included in the maintenance agreement and how the maintenance costs are calculated. Interoperability Generally, Interoperability means allowing for information exchange among HIT systems. Specifically, the HIMSS Board of Directors approved the definition of interoperability as In healthcare, interoperability is the ability of different information technology systems and software applications to communicate, exchange data, and use the information that has been exchanged. Data exchange schema and standards should permit data to be shared across vendor. Interoperability means the ability of health information systems to work together within and across organizational boundaries in order to advance the health status of, and the effective delivery of healthcare for, individuals and communities. 2 HIMSS further describes three levels of interoperability as follows: 1. Foundational interoperability allows data exchange from one information technology system to be received by another and does not require the ability for the receiving information technology system to interpret the data. 2. Structural interoperability is an intermediate level that defines the structure or format of data exchange (i.e., the message format standards) where there is uniform movement of health data from one system to another such that the clinical or operational purpose and meaning of the data is preserved and unaltered. Structural interoperability defines the syntax of the data exchange. It ensures that data exchanges between information technology systems can be interpreted at the data field level. 3. Semantic interoperability provides interoperability at the highest level, which is the ability of two or more systems or elements to exchange information and to use the information that has been exchanged. Semantic interoperability takes advantage of 2 standards/what is interoperability 6
7 both the structuring of the data exchange and the codification of the data including vocabulary so that the receiving information technology systems can interpret the data. This level of interoperability supports the electronic exchange of health-related financial data, patient-created wellness data, and patient summary information among caregivers and other authorized parties. This level of interoperability is possible via potentially disparate electronic health record (EHR) systems, business-related information systems, medical devices, mobile technologies, and other systems to improve wellness, as well as the quality, safety, cost-effectiveness, and access to healthcare delivery. 3 Interoperability is not easily achievable. Previously, most products were built around the standard of HL7, and Providers could purchase software solutions from multiple vendors to meet multiple needs without as much concern as to whether the solutions would be interoperable. Vendors moved to create market dominance by creating solutions with very specific platform standards that may not be compatible with those of other vendors. Even with federal standardization requirements such as meaningful use the expense to create interfaces and the lack of clinical standards for data have made interoperability less than easily obtainable. Some larger health systems have moved to single source solutions where there is only one system. For instance, all products are from Cerner or Epic. As such health system affiliates it requires the affiliate provider to utilize the same system or it declines to affiliate to affiliate with such provider. A health system has to have enough market dominance to require a particular health IT platform for affiliates as the expense of losing critical strategic partners can be very high when there is a need for clinical integration. In the event a Provider cannot move to a single source solution due to the expense of its existing long term health IT contracts and lack of market dominance, it should consider solutions such as Commonwealth Health Alliance. Commonwell Health Alliance, with members such as Cerner, athenahealth, McKesson and Allscripts, develops and offers services that are embedded natively in vendors own software to enhance interoperability across vendor lines. Therefore, the different solutions are programmed to interface with one another. Notably, Epic is not a member of this alliance though. In addition, Providers, who cannot single source, are looking to build a platform across solutions on their own. This process can be very resource intensive and time-consuming. However, the Provider s IT employees and consultant may best understand the particular needs in building a specific platform. 3 standards/what is interoperability 7
8 In negotiations with vendors there needs to be particular attention to the standards the vendor utilizes. Lack of full understanding of the facets of a vendor s standards has caused implementation issues down the road after the parties sign the contract. Part of the issue may be that the salesperson may not have the technical knowledge to describe accurately the vendor s standard. It is important to engage the Provider s IT staff and consultants with the vendor s IT staff and consultants as the Provider considers purchasing the solution and before the contracting phase. Additional considerations in addressing interoperability before a contract is executed are: Conducting an internal review of the standards on which the Provider s solutions currently operate. Consider state requirements for HIE. The speed in which data needs to be obtained. Patient engagement - Each solution has its own patient portal so that patients are interfacing with multiple portals. Vendors should commit to assisting Providers to ensure interfaces between the portals to enhance rather than complicate the patient experience. Interfaces Interfaces allow disparate technology and systems to communicate with each other. They are integral to successful implementation and interoperability. It is essential that the vendor provide interfaces to Providers for pre-existing systems to interact. The labor costs associated with interfaces can be expensive. Providers should negotiate reduced or pre-determined costs. Data The reason to have the health IT system is for the Provider to access and rely on the data. Often vendors will not be held responsible for any clinical decisions based upon the data. Ensuring the accuracy of the data is critical to the Provider. The contract may provide for certain testing of the data to ensure it is accurate, however, the Provider may not have the resources for consistent testing. The Provider may consider requiring the vendor to agree to a self-audit, as discussed herein, in the RFP. The contract should give full ownership of all data to the Provider and state that all data will be returned to the Provider if the contract is terminated for any reason. The Provider should be particularly careful about third party contractors retaining data. An additional consideration with data is being able to utilize the data to ensure the safety and quality of care. Clinicians are critical to the discussion of data needs in the contract as they best understand their needs. Providers need to engage their clinicians to ensure a good understanding for the data needs so the patient care can be enhanced. Moreover, with clinically integrated 8
9 networks Providers not only need to show data integration but also must show that Providers are still delivering at least the same level of care. Liability and Indemnification The limitation of liability clause is often highly negotiated. Often vendors try to limit liability to the fees paid for the particular portion of the software causing the issue or fees paid within a year or a low flat dollar amount such as $100,000. The Provider needs to consider if there is a claim how much damages may be before it agrees to limit narrowly the liability. It is advisable to opt for a broad limitation of liability such as all fees paid pursuant to the agreement. Certain causes of liability should be excluded from the limitation of liability including: breach of confidentiality and privacy; intellectual property infringement; and vendor s breach resulting in the Provider s failure to achieve meaningful use in a timely manner. Often vendor form agreements solely offer indemnification for infringement. The contract should contain much broader indemnification provisions. The indemnification should protect the Provider from at least the following: vendor s breach of its obligations; HIPAA and privacy/confidentiality violations by the vendor and third-party claims for bodily harm, injury, or death caused by the vendor s personnel or software. The vendors are most likely to impose indemnification obligations on Providers. Regardless of the cause of the fault vendors may require providers to indemnify them for any third-party claims brought against the vendor as a result of the vendor-provider relationship. For instance, the vendor may hold the Provider responsible for all clinical decisions made even if the Provider relied on faulty data provided by the vendor. Self-Audit Many Providers are unable to audit the vendors with which they contract due to lack of expertise or lack of financial or personnel resources. Other Providers may be unwilling to audit a vendor due to concerns with accepting vendor policies and procedures which may in fact be insufficient or which the Provider may later want to challenge. As a result, health care providers are increasingly turning to a vendor assessment and self-audit protocol, through which the vendor submits information to the Provider regarding its policies, procedures and safeguards relevant to the transaction or engagement. In some instances, the Provider may have a question and answer assessment form that the vendor is asked to complete. The RFP process allows the Provider leverage to have the vendor agree to audit itself. The issues a Provider may seek to have addressed during the self-audit include: Personnel screening - are background checks performed on new hires? Are current personnel checked for exclusions from federal or state health care programs? 9
10 Subcontractor screening - does the vendor screen subcontractors it engages to perform services related to the proposed contract? What does the screening entail? (e.g. experience, qualifications, data security, exclusions) Training - Are vendor s employees and staff trained on applicable compliance issues, such as the privacy and security of health information? If yes, how often is training provided? Information Privacy and Security - what privacy and security measures and safeguards does the vendor employ? (e.g. password protection, malware protection, encryption) What are the vendor s policies for the return or destruction of sensitive information? What are the vendor s breach notification and response policies? Compliance History - has the vendor been the subject of any compliance-related investigations (e.g. data breach)? What was the outcome of such investigation? If an adverse finding resulted, what steps has the vendor taken to prevent such violation from occurring in the future? A Provider may also ask the vendor to self-certify to the information provided during the selfaudit and the results of the self-audit. When adopting a vendor self-audit program, a Provider should consider the following: Assign business persons with contracting authority to request vendors complete the selfaudit. Identify individuals to review the vendor self-audit reports to determine if any risks may prevent the engagement of the vendor from moving forward Train relevant business persons on the self-audit tool and information requests to enable them to interface with vendors and potential vendors and answer questions Termination The reason a Provider enters a health IT contract is to utilize data in a format that can be utilized easily by the Provider. When a Provider exits a health IT contract or it finds the vendor is no longer providing the service, it needs to ensure that it will be able to keep that data in a format that can be utilized easily by the Provider. The time to ensure that the data can be transferred in a format that is useful for the Provider is before the parties execute the contract. Issues to ensure are o Where the data will be; o What type of format; and o How data can be transferred. The contract should require that the vendor assist with the transfer of the data for at least 12 months. When the data is transferred there can be an issue with the data staying in the same format in which it was stored and that it can continue to be utilized after transfer. The Provider should ensure it understands any changes in format. 10
11 However, the vendor may not be in business at the time of transfer. Therefore, the Provider should ensure that it can utilize the data in the format that is market standard or in a format otherwise usable by the Provider. The vendor should allow for a one time transfer in the event of termination of its business. To further protect against issues at the time of termination, the Provider should ensure the contract allows for and that it periodically back up copies of the data on its own onsite server, if available. Costs for transfer of data should be negotiated up front so that the vendor cannot tack on additional charges at the end. Ideally there would be no additional fees. If there is a fee it should be at set or contracted rate. Conclusion While the world of health IT contracting is very much vendor driven, Providers can leverage negotiating power through the use of an RFP and through dual negotiations with vendors. Getting the IT staff involved in the road mapping of solutions and in the details of the standards and documentation early is another key to successful health IT contracting. 11
AHLA. V. Betting on the RFP Process to Create Winning Health IT Contracts. Dawn R. Crumel Shipman & Goodwin Washington, DC
AHLA V. Betting on the RFP Process to Create Winning Health IT Contracts Dawn R. Crumel Shipman & Goodwin Washington, DC Jeffery Daigrepont Senior Vice President Coker Group Alpharetta, GA Physicians and
More informationNegotiating EHR Acquisition Contracts
Negotiating EHR Acquisition Contracts Key Strategies, Terms and Conditions Louisa Barash, Esq. & Jane Eckels, Esq. The Art and Skill of Negotiations Painful Contract Negotiations Take too long Are too
More informationEHR Buyer Beware: Issues to Consider When Contracting with EHR Vendors
Health Information Technology Practice Management Services EHR Buyer Beware: Issues to Consider When Contracting with EHR Vendors INTRODUCTION Electronic health record (EHR) contracts typically are vendor-favorable.
More informationEvolving Issues for Healthcare IT Contracting
Evolving Issues for Healthcare IT Contracting By: Alan L. Friel This client advisory is based in part on an article appearing in FierceHealthIT. The emergence of mega-suite vendors, more use of the cloud,
More informationTO: Chief Executive Officers of National Banks, Federal Branches and Data-Processing Centers, Department and Division Heads, and Examining Personnel
AL 2000 12 O OCC ADVISORY LETTER Comptroller of the Currency Administrator of National Banks Subject: Risk Management of Outsourcing Technology Services TO: Chief Executive Officers of National Banks,
More informationRisk Management of Outsourced Technology Services. November 28, 2000
Risk Management of Outsourced Technology Services November 28, 2000 Purpose and Background This statement focuses on the risk management process of identifying, measuring, monitoring, and controlling the
More informationChecklist for a Watertight Cloud Computing Contract
Checklist for a Watertight Cloud Computing Contract Companies of all industries are recognizing the need and benefit of moving some if not all of their IT infrastructure to a Cloud whether public or private.
More informationHow To Understand A Software License Agreement
SOFTWARE LICENSE AGREEMENTS A PRACTICAL GUIDE By Bradley J. Freedman SOFTWARE LICENSE AGREEMENTS A PRACTICAL GUIDE By Bradley J. Freedman Table of Contents Introduction...1 The Software License...2 Software
More information15 questions to ask before signing an electronic medical record or electronic health record agreement
15 questions to ask before signing an electronic medical record or electronic health record agreement Many definitions exist for electronic medical record (EMR) and electronic health record (EHR). Although
More informationService Schedule for CLOUD SERVICES
Service Schedule for CLOUD SERVICES This Service Schedule is effective for Cloud Services provided on or after 1 September 2013. Terms and Conditions applicable to Cloud Services provided prior to this
More informationSERVICE TERMS AND CONDITIONS
SERVICE TERMS AND CONDITIONS Last Updated: April 19th, 2016 These Service Terms and Conditions ( Terms ) are a legal agreement between you ( Customer or you ) and Planday, Inc., a Delaware corporation
More informationGENERAL TERMS AND CONDITIONS FOR SAP CLOUD SERVICES ( GTC )
GENERAL TERMS AND CONDITIONS FOR SAP CLOUD SERVICES ( GTC ) 1. DEFINITIONS Commonly used capitalized terms are defined in the Glossary at the end of the document. 2. USAGE RIGHTS AND RESTRICTIONS 2.1 Grant
More informationHSHS BUSINESS ASSOCIATE AGREEMENT BACKGROUND AND RECITALS
HSHS BUSINESS ASSOCIATE AGREEMENT This HIPAA Business Associate Agreement, ( Agreement ) is entered into on the date(s) set forth below by and between Hospital Sisters Health System on its own behalf and
More informationBUSINESS ASSOCIATE AGREEMENT
BUSINESS ASSOCIATE AGREEMENT This Business Associate Agreement ( Agreement ) is effective as of, 2013, and is by and between SOUTHWEST DEVELOPMENTAL SERVICES, INC. ( Covered Entity ) and ( Business Associate
More informationCloud Computing: Legal Risks and Best Practices
Cloud Computing: Legal Risks and Best Practices A Bennett Jones Presentation Toronto, Ontario Lisa Abe-Oldenburg, Partner Bennett Jones LLP November 7, 2012 Introduction Security and Data Privacy Recent
More informationWebsite Hosting Agreement
Website Hosting Agreement 6 oak grove avenue This Hosting Contract governs your purchase and use, in any manner, of all Web site hosting services, including the Shared Hosting Services, (collectively,
More informationSaaS Terms & Conditions
SaaS Terms & Conditions These SaaS Terms and Conditions ( SaaS Terms ) are part of the Serraview Services Agreement ( Agreement ) which governs Client s (also referred to herein as you or your ) use of
More informationCOMPUTER SOFTWARE AS A SERVICE LICENSE AGREEMENT
COMPUTER SOFTWARE AS A SERVICE LICENSE AGREEMENT This Agreement is binding on the individual and the company, or other organization or entity, on whose behalf such individual accepts this Agreement, that
More information2012 Winston & Strawn LLP
2012 Winston & Strawn LLP Top 5 Negotiation Points for Software, SaaS, and Outsourcing Agreements Brought to you by Winston & Strawn s Advertising, Marketing, and Entertainment Law Group 2012 Winston &
More informationPROVO CITY UTILITIES NET METERING LICENSE AGREEMENT
PROVO CITY UTILITIES NET METERING LICENSE AGREEMENT Customer-Owned Electric Generating Systems of 25kW or Less This NET METERING LICENSE AGREEMENT ( Agreement ) is between ( Customer ) and Provo City -
More informationDisclaimer: Template Business Associate Agreement (45 C.F.R. 164.308)
HIPAA Business Associate Agreement Sample Notice Disclaimer: Template Business Associate Agreement (45 C.F.R. 164.308) The information provided in this document does not constitute, and is no substitute
More informationSPECIAL TERMS AND CONDITIONS FOR INFORMATION TECHNOLOGY
SPECIAL TERMS AND CONDITIONS FOR INFORMATION TECHNOLOGY A. ACCEPTANCE: The College shall commence Acceptance testing within five (5) days, or within such other period as agreed upon. Acceptance testing
More informationContracting Guidelines with EHR Vendors
Contracting Guidelines with EHR Vendors In general, if a contract is presented to your group from a software company, it will be written from the perspective of the software company. You can request language
More informationSalesPro CRM SUBSCRIPTION AGREEMENT & TERMS USE
SalesPro CRM SUBSCRIPTION AGREEMENT & TERMS USE Page 1 of 5 Preamble This CRM SaaS Subscription Agreement (this Agreement ) is by and between SalesPro CRM. ( SalesPro ) and the Client specified on the
More informationThe Art of the Deal: Negotiating a Winning EHR Contract
The Art of the Deal: Negotiating a Winning EHR Contract Rural Hospital Information Technology Conference October 20, 2010 Austin, Texas Diana J.P. McKenzie Partner and Chair, Information Technology & Outsourcing
More informationAdvanced HIT Contracting Issues
Advanced HIT Contracting Issues AHLA: Current HIT Challenges Baltimore Steven J. Fox, Esq. Post & Schell, PC March 28, 2014 (rev d 3/31/14) SESSION DESCRIPTION This session will describe some of the advanced
More informationHIT/EHR Vendor Contracting Checklist
HIT/EHR Vendor Contracting Checklist Dear Members: You are likely coming to the end of an intense process of vetting one or more electronic health record (EHR) products and related vendor proposals. As
More informationUser Agreement. Terms of Use
User Agreement This page contains the User Agreement ("Agreement") between you and Connecticut Radio Information System, Inc. ("CRIS"), the nonprofit radio reading service. The term "Site" as it is used
More informationData Sharing Agreements: Principles for Electronic Medical Records/Electronic Health Records
CMA POLICY Data Sharing Agreements: Principles for Electronic Medical Records/Electronic Health Records I. INTRODUCTION This document is intended to provide some interim guidance with respect to the main
More informationPARTICIPATION AGREEMENT For ELECTRONIC HEALTH RECORD TECHNICAL ASSISTANCE
PARTICIPATION AGREEMENT For ELECTRONIC HEALTH RECORD TECHNICAL ASSISTANCE THIS AGREEMENT, effective, 2011, is between ( Provider Organization ), on behalf of itself and its participating providers ( Providers
More informationCalifornia Solar Initiative (CSI) Program 2007 Reservation Request Form and Program Contract [follows the second page Reservation Request form]
California Solar Initiative (CSI) Program 2007 Reservation Request Form and Program Contract [follows the second page Reservation Request form] CSI CONTRACT TERMS AND CONDITIONS This California Solar Initiative
More informationWEBSITE MAINTENANCE & SUPPORT SUBSCRIPTION AGREEMENT
WEBSITE MAINTENANCE & SUPPORT SUBSCRIPTION AGREEMENT This Website Support and Maintenance Subscription Agreement ( Agreement ) is made by and between Goose Dog Designs (the Developer ) and the aforementioned
More informationTerms of Service. Permitted uses You may use the Services for your own internal business purposes only in accordance with these Terms.
Terms of Service Description of services Through its network of Web properties, Nintex UK Ltd and its global affiliates ( Nintex or We ) provides a variety of resources, including but not limited to hosted
More informationNegotiating the Software License: Eight Tips for the Licensee
Negotiating the Software License: Eight Tips for the Licensee Brian B. Gilbert 1 A software failure can hamstring your client's business. Be sure to build the solutions into the licensing agreement. WITH
More informationAPPENDIX I: STANDARD FORM BUSINESS ASSOCIATE CONTRACT AND DATA USE AGREEMENT (2012 Version)
APPENDIX I: STANDARD FORM BUSINESS ASSOCIATE CONTRACT AND DATA USE AGREEMENT (2012 Version) THIS AGREEMENT is entered into and made effective the day of, 2012 (the Effective Date ), by and between (a)
More informationService Schedule for BT Business Lite Web Hosting and Business Email Lite powered by Microsoft Office 365
1. SERVICE DESCRIPTION 1.1 The Service enables the Customer to: set up a web site(s); create a sub-domain name associated with the web site; create email addresses. 1.2 The email element of the Service
More informationMobile App Developer Agreements
Mobile App Developer Agreements By Alan L. Friel Many companies that have had disputes with developers have been surprised to discover that the agreements signed, often without input from legal, failed
More informationManaged IT Services Terms & Conditions. I. Overview. Definitions
I. Overview Managed IT Services Terms & Conditions This Agreement states the terms and conditions by which Azul Services (heretofore known as Provider ) will deliver, and Customer (heretofore known as
More informationSTATE OF NEVADA DEPARTMENT OF HEALTH AND HUMAN SERVICES BUSINESS ASSOCIATE ADDENDUM
STATE OF NEVADA DEPARTMENT OF HEALTH AND HUMAN SERVICES BUSINESS ASSOCIATE ADDENDUM BETWEEN The Division of Health Care Financing and Policy Herein after referred to as the Covered Entity and (Enter Business
More informationIf a Client and a Freelancer enter an independent contractor relationship, then this Freelancer Agreement ( Freelancer Agreement ) will apply.
Freelancer Agreement If a Client and a Freelancer enter an independent contractor relationship, then this Freelancer Agreement ( Freelancer Agreement ) will apply. This Agreement is effective as of March
More informationProvider Web Portal Registration Form
Provider Web Portal Registration Form Thank you for your interest in registering for the Maryland Physicians Care provider web portal. Maryland Physicians Care is committed to protecting the privacy of
More informationCOMPREHENSIVE REMOTE ACCESS AGREEMENT FOR PRIVATE MEDICAL PRACTICES OR NURSING HOMES
COMPREHENSIVE REMOTE ACCESS AGREEMENT FOR PRIVATE MEDICAL PRACTICES OR NURSING HOMES THIS COMPREHENSIVE REMOTE ACCESS AGREEMENT ("Agreement") between MAIN LINE HEALTH, INC. ("MLH") in its own capacity
More informationReference Table of Special Terms & Conditions for IT Contracts
Reference Table of Special Terms & Conditions for IT Contracts Definitions Term & Termination Software License Transition of Services Contract Kick- Off Meeting Contract Closeout License Grant License
More informationHOSTING SERVICES ADDENDUM TO MASTER SOFTWARE LICENCE AGREEMENT
HOSTING SERVICES ADDENDUM TO MASTER SOFTWARE LICENCE AGREEMENT Last Updated: 10 June 2015 This Hosting Services Addendum to the Master Software Licence Agreement ( Addendum ) will only apply to the extent
More informationFramework Terms and Conditions
Introduction Framework Terms and Conditions These Framework Terms and Conditions form part of the contract to allow one or more Purchasing Agencies to purchase outcome-focussed services from the Provider.
More informationPreferred Professional Insurance Company Subcontractor Business Associate Agreement
Preferred Professional Insurance Company Subcontractor Business Associate Agreement THIS SUBCONTRACTOR BUSINESS ASSOCIATE AGREEMENT ( Agreement ) amends and is made a part of all Services Agreements (as
More informationInfinedi HIPAA Business Associate Agreement RECITALS SAMPLE
Infinedi HIPAA Business Associate Agreement This Business Associate Agreement ( Agreement ) is entered into this day of, 20 between ( Company ) and Infinedi, LLC, a Limited Liability Corporation, ( Contractor
More informationPaychex Accounting Online Terms of Use
Paychex Accounting Online Terms of Use Paychex recommends that Client read the Terms of Use prior to using the Paychex Accounting Online Software ( Software ). If Client does not accept and agree with
More informationColumbia University Service Provider Agreement
Columbia University Agreement Agreement ( Agreement ) dated as of, 20 (the Effective Date ) between The Trustees of Columbia University in the City of New York ( Columbia ) and ( Service Provider ). 1.
More informationELLIPTICS, LTD. TERMS OF SERVICE. For Elliptics branded products: Webcrossing Core, Webcrossing Community, Webcrossing Neighbors 1.
ELLIPTICS, LTD. TERMS OF SERVICE For Elliptics branded products: Webcrossing Core, Webcrossing Community, Webcrossing Neighbors By using Elliptics products, software, services and hosted websites (referred
More informationSOFTWARE AS A SERVICE AGREEMENT
SOFTWARE AS A SERVICE AGREEMENT IMPORTANT READ THIS SOFTWARE AS A SERVICE AGREEMENT (THIS AGREEMENT ) CAREFULLY. THIS AGREEMENT IS RELATED TO AND DEEMED INCORPORATED INTO THE ACCOMPANYING ORDERING DOCUMENT
More informationSecureWatch PLUS Service Description and Agreement
SecureWatch PLUS Service Description and Agreement This SecureWatch PLUS Service Description and Agreement ( Agreement ) is made effective as of the Effective Date (defined below) by and between Corero
More informationWeb Site Hosting Service Agreement
Web Site Hosting Service Agreement Updated April, 2015 The following agreement is between Softext Publishing Inc. ( SOFTEXT ) of 954 1st Ave West, Owen Sound ON, Canada and You ( Client ). WHEREAS, SOFTEXT
More informationTerms and Conditions for Purchase Orders for Recycling Materials
Terms and Conditions for Purchase Orders for Recycling Materials This Agreement is made by and between AEROJET-GENERAL CORPORATION, an Ohio corporation with a place of business at Rancho Cordova, California
More informationTerms and Conditions
Terms and Conditions 1. TCD Software as a Service Terms and Conditions (the "Terms and Conditions") cover the relationship between The Cambridge Don ("TCD") and users (hereinafter referred to as the "Client")
More informationHIPAA BUSINESS ASSOCIATE AGREEMENT
HIPAA BUSINESS ASSOCIATE AGREEMENT This HIPAA Business Associate Agreement ("BA AGREEMENT") supplements and is made a part of any and all agreements entered into by and between The Regents of the University
More informationBUSINESS ASSOCIATE AGREEMENT
BUSINESS ASSOCIATE AGREEMENT The parties to this ( Agreement ) are, a _New York_ corporation ( Business Associate ) and ( Client ) you, as a user of our on-line health record system (the "System"). BY
More informationCloud Agreements: Ensuring a Sunny Forecast July 28, 2011
Cloud Agreements: Ensuring a Sunny Forecast July 28, 2011 February 11, 2014 Presented by: Robert Bethea, AOL Tom Knox, Morrison & Foerster Todd Tabor, HP Software 2014 Morrison & Foerster LLP All Rights
More informationContracting Guidelines with EHR Vendors
Doctors Office Quality - Information Technology (DOQ-IT) Project Contracting Guidelines with EHR Vendors In general, if a contract is presented to your group from a software company, it will be written
More informationCloud Agreements: Do s, Don ts, and Cautions
Cloud Agreements: Do s, Don ts, and Cautions 4 th Annual Grand Rapids IT Symposium June 11, 2015 Nate Steed & Ken Coleman 2015 Warner Norcross & Judd LLP. All rights reserved. WNJ.com Disclaimer 2015 Warner
More informationService Schedule for Business Email Lite powered by Microsoft Office 365
Service Schedule for Business Email Lite powered by Microsoft Office 365 1. SERVICE DESCRIPTION Service Overview 1.1 The Service is a hosted messaging service that delivers the capabilities of Microsoft
More informationHow To Indemnify An Ehr Technology Developer
EHR Contracts: Key Contract Terms for Users to Understand June 25, 2013 Prepared for: The Office of the National Coordinator for Health Information Technology Washington, DC Prepared by: Westat An Employee-Owned
More informationAnnex 1. Contract Checklist for Cloud-Based Genomic Research Version 1.0, 21 July 2015
Annex 1. Contract Checklist for Cloud-Based Genomic Research Version 1.0, 21 July 2015 The following comprises a checklist of areas that genomic research organizations or consortia (collectively referred
More informationKaiser Permanente Affiliate Link Provider Web Site Application
Kaiser Foundation Health Plan of Colorado Kaiser Permanente Affiliate Link Provider Web Site Application FOR PROVIDERS CONTRACTED WITH KAISER IN THE COLORADO REGION ONLY Page 1 of 7 Kaiser Permanente Affiliate
More informationIsaac Willett April 5, 2011
Current Options for EHR Implementation: Cloud or No Cloud? Regina Sharrow Isaac Willett April 5, 2011 Introduction Health Information Technology for Economic and Clinical Health Act ( HITECH (HITECH Act
More informationBUSINESS ASSOCIATE AGREEMENT
BUSINESS ASSOCIATE AGREEMENT This Business Associate Agreement ( Agreement ) by and between (hereinafter known as Covered Entity ) and Office Ally, LLC. (hereinafter known as Business Associate ), and
More informationHow To Deal With Cloud Computing
A LEGAL GUIDE TO CLOUD COMPUTING INTRODUCTION Many companies are considering implementation of cloud computing services to decrease IT costs while providing the flexibility to scale usage on demand. The
More informationBuckeye Brainiacs Support Terms of Service
Buckeye Brainiacs Support Terms of Service 1. ACKNOWLEDGEMENT AND ACCEPTANCE OF TERMS OF SERVICE The Brainiacs Terms of Service ( Service Terms ) are available to you ( Customer ) at our website www.buckeyecableystem.com
More informationWe suggest you retain a copy of these End User Terms of Use for your records.
END USER TERMS OF USE The use of Incident Response Technologies Inc. s ("IRT") Software is offered to you upon your acceptance of these End User Terms of Use. By using IRT s software (the Software ), you
More informationDAIMLER GROUP NORTH AMERICAN COMPANIES
DAIMLER GROUP NORTH AMERICAN COMPANIES General Purchasing Conditions for IT Part H Individual Software Development, Maintenance and Customization 1 Subject Matter / Scope of Performance 1.1 General The
More informationMerchant Gateway Services Agreement
Merchant Gateway Services Agreement This Merchant Gateway Services Agreement ( Agreement ) is made as of, 20 ( Effective Date ), by and between American POS Alliance, LLC ( Reseller ) and the merchant
More informationBUSINESS ASSOCIATE AGREEMENT
BUSINESS ASSOCIATE AGREEMENT This HIPAA Business Associate Agreement ( BA Agreement ) amends, supplements, and is made a part of the Agreement ( Agreement ) entered with Client ( CLIENT ) and International
More informationNEWBURGH ENLARGED CITY SCHOOL DISTRIST NEWBURGH, NEW YORK REQUEST FOR PROPOSAL ARCHITECTURE SERVICES 2015 2016
NEWBURGH ENLARGED CITY SCHOOL DISTRIST NEWBURGH, NEW YORK REQUEST FOR PROPOSAL ARCHITECTURE SERVICES 2015 2016 Notice is hereby given that the Board of Education of the Newburgh Enlarged City School District,
More informationA How-To Guide for Updating HIPAA Policies & Procedures to Align with ARRA Health Care Provider Edition Version 1
A How-To Guide for Updating HIPAA Policies & Procedures to Align with ARRA Health Care Provider Edition Version 1 Policy and Procedure Templates Reflects modifications published in the Federal Register
More informationVirtual Private Server Services Specific Terms and Conditions
Virtual Private Server Services Specific Terms and Conditions These Specific Terms and Conditions and ROOT General Terms and Conditions shall be interpreted and applied together as a single instrument
More informationJOHN DEERE DIFFERENTIAL CORRECTION SOFTWARE LICENSE AGREEMENT
JOHN DEERE DIFFERENTIAL CORRECTION SOFTWARE LICENSE AGREEMENT IMPORTANT -- READ CAREFULLY. THIS IS A LEGAL CONTRACT BETWEEN YOU AND JOHN DEERE SHARED SERVICES, INC., A CORPORATION HAVING A PRINCIPAL ADDRESS
More informationBUSINESS ASSOCIATE AGREEMENT
BUSINESS ASSOCIATE AGREEMENT Express Scripts, Inc. and one or more of its subsidiaries ( ESI ), and Sponsor or one of its affiliates ( Sponsor ), are parties to an agreement ( PBM Agreement ) whereby ESI
More informationSpecific Terms and Conditions of LINE Services for Business Partners: LINE Business Connect
Specific Terms and Conditions of LINE Services for Business Partners: LINE Business Connect Article 1 (Purpose) These Specific Terms and Condition of LINE Services for Business Partners: LINE Business
More informationDue Diligence Request List: IP and IT
PLC Intellectual Property & Technology An intellectual property (IP) and information technology (IT) due diligence request list for use in connection with an M&A transaction. This request list is designed
More informationHIPAA BUSINESS ASSOCIATE AGREEMENT
HIPAA BUSINESS ASSOCIATE AGREEMENT This HIPAA Business Associate Agreement and is made between BEST Life and Health Insurance Company ( BEST Life ) and ( Business Associate ). RECITALS WHEREAS, the U.S.
More informationCloud Computing Contracts Top Issues for Healthcare Providers
Cloud Computing Contracts Top Issues for Healthcare Providers North Carolina Bar Association Health Law Section Annual Meeting NC Bar Center Cary, North Carolina April 23, 2015 Presenters Kathryn Brucks,
More informationORACLE PARTNERNETWORK EMBEDDED SOFTWARE LICENSE DISTRIBUTION AGREEMENT
ORACLE PARTNERNETWORK EMBEDDED SOFTWARE LICENSE DISTRIBUTION AGREEMENT This Embedded Software License Distribution Agreement ( agreement ) includes the terms and definitions set out below and any orders
More informationBNSync User License Agreement
BNSync User License Agreement This Agreement ("Agreement") contains the complete terms and conditions that apply to your installation and use of BNSync, a proprietary software product that is owned and
More informationHotel Meeting Contracts Navigating Legal Issues for Successful and Profitable Meetings
Hotel Meeting Contracts Navigating Legal Issues for Successful and Profitable Meetings Presented By Jeffrey S. Tenenbaum, Esq., Venable LLP Kristalyn J. Loson, Esq., Venable LLP Topics for Today 1. General
More informationGUIDANCE FOR MANAGING THIRD-PARTY RISK
GUIDANCE FOR MANAGING THIRD-PARTY RISK Introduction An institution s board of directors and senior management are ultimately responsible for managing activities conducted through third-party relationships,
More informationContract Terms for Services provided to Clients
2015-01-01 Contract Terms for Services provided to Clients 1. Definitions 1.1 This contract is authored by ProjectCompanion AB (org nr 556861-6493), further referred to as ProjectCompanion. 1.2 This contract
More information1. In this Contract, except where the contrary intention is expressed, the following definitions are used:
Model clauses on the ownership of intellectual property rights in developed software for use by Commonwealth agencies subject to the Financial Management and Accountability Act 1997 in information and
More informationInternet Services Terms and Conditions
Internet Services Terms and Conditions 1. These terms and conditions These General Terms and Conditions apply to you if you are a business or residential telecommunications customer of Telnet Telecommunication
More informationTERMS AND CONDITIONS OF BANK INDEPENDENT BILL PAY
TERMS AND CONDITIONS OF BANK INDEPENDENT BILL PAY This Bill Pay Agreement outlines the terms and conditions of use of the Bank Independent Bill Pay Service. In this Bill Pay Agreement, Bank means Bank
More informationProvider secure web portal & Member Care Information portal Registration Form
Provider secure web portal & Member Care Information portal Registration Form Thank you for your interest in registering for the Aetna Better Health Provider Secure Web Portal and the Aetna Better Health
More informationDATA SECURITY AGREEMENT. Addendum # to Contract #
DATA SECURITY AGREEMENT Addendum # to Contract # This Data Security Agreement (Agreement) is incorporated in and attached to that certain Agreement titled/numbered and dated (Contract) by and between the
More informationWEBSITE HOSTING SERVICES AGREEMENT. Effective Date: 1/1/2015
WEBSITE HOSTING SERVICES AGREEMENT Effective Date: 1/1/2015 1) Scope of Services. Company will provide Client a shared or dedicated virtual machine, an Internet address for storage and access to Content,
More informationAutomatic Recurring Payment Application
Automatic Recurring Payment Application Schedule your payment to be automatically charged to your credit card. Just complete and sign this form to get started! Here s How Recurring Payments Work: You authorize
More informationInteractive Brokers Hong Kong Agreement for Advisors Providing Services to Interactive Brokers Clients
Interactive Brokers Hong Kong Agreement for Advisors Providing Services to Interactive Brokers Clients This Agreement is entered into between Interactive Brokers Hong Kong Ltd ("IB") and the undersigned
More informationSAMPLE RETURN POLICY
DISCLAIMER The sample documents below are provided for general information purposes only. Your use of any of these sample documents is at your own risk, and you should not use any of these sample documents
More informationH.W. Wilson General Database License Agreement
The H.W. Wilson Company 950 University Avenue Bronx, NY 10452 Telephone 718 588 8400 800 367 6770 Fax 718 590 1617 www.hwwilson.com New York Dublin H.W. Wilson General Database License Agreement 1.0 The
More informationLOGGING SUBCONTRACT. Recital
LOGGING SUBCONTRACT This Logging Contract (this Contract ) is entered as of the day of, 200, by and between ("Contractor") and ("Subcontractor") as follows: Recital The owners of certain timber growing
More informationIICLE ONLINE SUBSCRIPTIONS TERMS AND CONDITIONS
IICLE ONLINE SUBSCRIPTIONS TERMS AND CONDITIONS IICLE Online Library, IICLE Online CLE, and IICLE Online All Access subscriptions are accepted and approved with the understanding that the Subscriber has
More informationYa-YaOnline Platform ( Service ).
SOFTWARE AS A SERVICE AGREEMENT FOR THE USE OF: Ya-YaOnline Platform ( Service ). NOW IT IS HEREBY AGREED by and between the parties hereto as follows:- Definitions "Agreement" means this Agreement and
More information