Service Level Agreement

Version 8.6

1.0 Agreement Overview

This Agreement represents a Service Level Agreement (“SLA” or “Agreement”) between Bridge Patient Portal (“Company”) and its customer (“Client”) for the provisioning of IT services required to support and sustain the Patient Portal software.

This Agreement remains valid until superseded by a revised agreement mutually endorsed by the stakeholders.


2.0 Goals & Objectives

The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Client by the COMPANY.

The objectives of this Agreement are to:

  • Provide clear reference to service ownership, accountability, roles and/or responsibilities
  • Present a clear, concise and measurable description of service provision to the Client
  • Match perceptions of expected service provision with actual service support & delivery


3.0 Service Agreement

The following detailed service parameters are the responsibility of the COMPANY in the ongoing support of this Agreement.


3.1 Service Scope

The following Services are included in this Agreement:

  • Manned telephone support
  • Monitored email support
  • Support desk / ticket system
  • Remote assistance using Remote Desktop

The following issues are covered by this Agreement;

Troubleshooting server outages and hosting-related errors and resuming service from server outage*

* COMPANY will provide reasonable amount of support to attempt to identify and resolve any server-related issues or outages. Reasonable amount of support is defined as up to two (2) hours of support (per server outage) to address the issue. Service Provider reserves the right to bill Client at the hourly rate listed in “Exhibit A” if the work to restore the server outage or resolve the issue exceeds reasonable amount of support time.


3.2 CLIENT Requirements

CLIENT responsibilities and/or requirements in support of this Agreement include:

  • Payment for all support and maintenance costs according to the Client’s contracted hourly rate
  • Reasonable availability of Client representative(s) when resolving a service related incident or request


3.3 COMPANY Requirements

COMPANY responsibilities and/or requirements in support of this Agreement include:

  • Meeting response times associated with service related incidents
  • Appropriate notification to Client for all scheduled maintenance
  • Best effort in diagnosis and repair of incident(s) including critical decision making in emergency situations


3.4 Service Assumptions

Assumptions related to in-scope services and/or components include:

Changes to services will be communicated and documented


3.5 Exceptions

Client shall not receive any credit under the SLA in connection with any failure or deficiency of website or email availability caused by or associated with:

A. Circumstances beyond COMPANY’s reasonable control, including, without limitation, acts of any governmental body, war, insurrection, sabotage, armed conflict, embargo, fire, flood, strike or other labor disturbance, interruption of or delay in transportation, unavailability of or interruption or delay in telecommunications or third party services, virus attacks or hackers, failure of third party software (including, without limitation, e-commerce software, payment gateways, chat, statistics or free scripts) or inability to obtain raw materials, supplies, or power used in or equipment needed for provision of this SLA;

B. Scheduled maintenance and emergency maintenance and upgrades (Note: Every effort will be made to keep downtime to a minimum during maintenance periods and, when possible, COMPANY will notify Client in advance of the expected downtime. Client will not be billed hourly for these maintenance periods, but these maintenance periods are not eligible for SLA credits);

C. DNS issues outside the direct control of COMPANY;

D. Client’s acts or omissions (including acts or omissions of others engaged or authorized by the Client), including, without limitation, custom scripting or coding (e.g., CGI, Perl, HTML, ASP, etc), any negligence, willful misconduct, or use of the Services in breach of this Agreement;

E. DNS (Domain Name Server) Propagation;

F. Outages elsewhere on the Internet that hinder access to your account. COMPANY is not responsible for browser or DNS caching that may make your site appear inaccessible when others can still access it. COMPANY will guarantee only those areas considered under the control of COMPANY.

G. Issues with email Client configuration or performance


4.0 Service Management

Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.


4.1 Service Availability

  • Regular business hours are considered to be from 9.00 am until 5.00 pm Eastern Standard
  • Time, Monday to Friday, except Federal U.S. Holidays and observances as defined by the U.S. Government.
  • Telephone support: will be conducted during business hours. Direct contact information will be provided for telephone support outside of business hours. However, no action will be guaranteed until the next working day.
  • Email support and Support Desk: will be monitored during business hours. Any email received outside office hours will be collected, and best efforts will be made to respond to client’s request. However, no action will be guaranteed until the next working day.


4.2 Emergency Situation

  • Any work performed or calls handled outside regular business hours will be considered an emergency and billed accordingly. Bill rate, unless otherwise contracted incurs an surcharge of 50%.
  • Services that are in need of an immediate resolution, including but not limited to server failure, software failure, e-PHI risk, that are not related to an existing project or approved work/change order, may be completed without Client’s approval.
  • Client will be provided with an emergency email address and phone number, which will be forwarded to multiple parties in COMPANY’s organization.

Client will be promptly notified In the event of this situation, and the COMPANY will make the best effort to identify such circumstances in order to ensure the best possible service.


4.3 Service Requests

In support of services outlined in this Agreement, the COMPANY will respond to service related incidents and/or requests submitted by the Client within the following time frames:

Classification Description Response Time*
Critical Critical Business Impact-Problem or issue that renders your Patient Portal unusable (ie: offline) < 6 hours (during business hours)
< 8 hours (during non-business hours)
High Significant Business Impact-Problem or issue that DOES impact the operation of your Patient Portal or email but DOES NOT render it unusable (i.e. slow server response time). < 24 hours (during business hours)
< 48 hours (non business hours)
Low Minimal Business Impact-Problem or issue that DOES NOT impact the operation of your Patient Portal or email (i.e. maintenance requests). < 72 hours (during business hours)


Remote assistance will be provided in-line with the above timescales dependent on the priority of the support request.

COMPANY guarantees 99% uptime (average over a 1 year period) for systems under their direct control, protecting the system from downtime as a result of poor server configuration or poor application performance. As server is not being hosted in COMPANY’s network, COMPANY cannot be held responsible for downtime as a result of network outages, hardware failure and other issues outside of COMPANY’s control. COMPANY expects remote access to be maintained and direct contact to individuals physically present at the server hosting company.

* COMPANY will make every effort to respond to all service requests in a timely manner.


5.0 Customer Requesting Reimbursement

If there is a server outage or other problem that causes Client’s Patient Portal to go offline due to a problem not excluded in the Exclusions section of this agreement Company shall apply a credit of 2% of the monthly bill (SaaS license fees only) for each 30 minutes of downtime beyond the guaranteed uptime up to a maximum 100% of their monthly bill.

Such credits shall be applied automatically by COMPANY, provided that Client may also make a request by sending an e-mail message to COMPANY. Credits for confirmed unavailability will be applied within two billing cycles after receipt of the Client’s credit request. Credits are not refundable and can be used only towards future billing charges.

(Visited 150 times, 1 visits today)