rfp attachments

ATTACHMENT I: SCOPE OF SERVICES

1 Overview LSU wishes to purchase the software systems listed in Attachment V; furthermore, LSU wishes to purchase implementation services for all systems listed in Attachment V. LSU will separately procure all necessary hardware and network systems. LSU expects this EHR system to operate in two identical data centers, a primary and a secondary, and the proposer will ensure that the completely functional EHR, when fully implemented, operates acceptably in this high-availability environment. Attachment XII lists utilization statistics for each of the ten hospitals.

2 Tasks and Services Contractor will implement all software systems for the 10 LSU hospitals. Existing LSU staff will assist with the implementation. As indicated in Attachment X, Section D, proposer must recommend the LSU staff requirements for implementation of all systems and for managing such systems after implementation is complete. Contractor will provide and administer a comprehensive training plan for all LSU personnel who will use the systems that are implemented, which may follow a “train the trainer” model. As shown in Attachment XII, there are approximately 3000 physicians and 7000 support staff to be trained.

3 Deliverables Proposer will provide a preliminary implementation plan as part of this response and will update or replace this plan as needed for successful implementation. Successful proposer will provide all necessary deliverables to ensure successful implementation and operation of the proposed applications including (but not limited to) implementation documentation, meeting materials, status reports, training documentation, and system maintenance and management documentation. LSU must approve the preliminary implementation plan and any subsequent plan modifications.

4 Functional Requirements The Proposer must offer the functional components of Attachment V that are designated “Required”. Integration (as opposed to interfaces) among these core (“required”) components is important because functionality will be greatly improved; integration refers to a level of functionality such that components access the same database, share common master files and tables, were written using common tools and architecture, and are internally synchronized.

5 Technical Requirements Contractor will implement the proposed applications in accordance with the technical requirements specified in Attachment XIII.

6 Project Requirements Contractor will be responsible for successful implementation of all project tasks within defined schedule and budget limits to be defined in EHR contract negotiations. Contractor and contractor’s project personnel will report to LSU-appointed project oversight. Contractor will ensure that all functional requirements as agreed to in the BAFO are implemented in accordance with stated project implementation milestones. LSU may impose penalties or liquidated damages for missed implementation dates or late deliverables.

ATTACHMENT II: CERTIFICATION STATEMENT

The undersigned hereby acknowledges she/he has read and understands all requirements and specifications of the Request for Proposals (RFP), including attachments.

OFFICIAL CONTACT. The State requests that the Proposer designate one person to receive all documents and the method in which the documents are best delivered. Identify the Contact name and fill in the information below: (Print Clearly)

Date Official Contact Name:

A. E-mail Address:

B. Facsimile Number with area code: ( )

C. US Mail Address:

Proposer certifies that the above information is true and grants permission to the State or Agencies to contact the above named person or otherwise verify the information provided.

By its submission of this proposal and authorized signature below, Proposer certifies that:

1. The information contained in its response to this RFP is accurate;

2. Proposer complies with each of the mandatory requirements listed in the RFP and will meet or exceed the functional and technical requirements specified therein;

3. Proposer accepts the procedures, evaluation criteria, mandatory contract terms and conditions, and all other administrative requirements set forth in this RFP.

4. Proposer's quote is valid for at least 90 days from the date of proposal's signature below;

5. Proposer understands that if selected as the successful Proposer, he/she will have 45 business days from the date of delivery of final contract in which to complete contract negotiations, if any, and 15 days to execute the final contract document.

Authorized Signature:

Typed or Printed Name:

Title:

Company Name:

Address:

City: State: Zip:

SIGNATURE of Proposer's Authorized Representative DATE

ATTACHMENT III: CONSULTING SERVICES CONTRACT

The following LSU contract format will be used in contract negotiations with the successful proposer.

STATE OF LOUISIANACONTRACT

On this ____day of 20__, the State of Louisiana, the LSU System, hereinafter sometimes referred to as the "State", and [CONTRACTOR’S NAME AND LEGAL ADDRESS INCLUDING ZIP CODE], hereinafter sometimes referred to as the "Contractor", do hereby enter into a contract under the following terms and conditions.

1 SCOPE OF SERVICES

1.1 CONCISE DESCRIPTION OF SERVICES

1.2 STATEMENT OF WORK

1.2.1. INTRODUCTION

This Statement of Work defines the tasks to be performed, the required deliverables, the completion criteria, estimated completion dates, the estimated cost for each Task Schedule; and establishes the responsibilities for accomplishing these tasks.

1.2.2. GOALS AND OBJECTIVES

1.2.3. PERFORMANCE MEASURES

The performance of the contract will be measured by the State Project Manager, authorized on behalf of the State, to evaluate the contractor’s performance against the criteria in the Statement of Work and are identified as:

1.2.4. MONITORING PLAN

Lee Bairnsfather, Ph.D., Assistant Vice President for Information Technology, will monitor the services provided by the contractor and the expenditure of funds under this contract. Lee Bairnsfather, Ph.D., Assistant Vice President for Information, Technology will be primarily responsible for the day-to-day contact with the contractor and day-to-day monitoring of the contractor’s performance. The monitoring plan is the following:

1.2.5. CONTRACTOR TASKS AND RESPONSIBILITIES

1.2.6. DELIVERABLES

The Contract will be considered complete when Contractor has delivered and State has accepted all deliverables specified in the Statement of Work.

1.2.7. SUBSTITUTION OF KEY PERSONNEL

The Contractor's personnel assigned to this Contract may not be replaced without the written consent of the State. Such consent shall not be unreasonably withheld or delayed provided an equally qualified replacement is offered. In the event that any State or Contractor personnel become unavailable due to resignation, illness, or other factors, excluding assignment to project outside this contract, outside of the State's or Contractor's reasonable control, as the case may be, the State or the Contractor, shall be responsible for providing an equally qualified replacement in time to avoid delays in completing tasks.

2 ADMINISTRATIVE REQUIREMENTS

2.1 TERM OF CONTRACT

This contract shall begin on [DATE] and shall end on [DATE]. State has the right to contract for up to a total of three years with the concurrence of the Contractor and all appropriate approvals.

2.2 STATE FURNISHED RESOURCES

State shall appoint a Project Coordinator for this Contract identified in Section 1.2.4 who will provide oversight of the activities conducted hereunder. Notwithstanding the Contractor’s responsibility for management during the performance of this Contract, the assigned Project Coordinator shall be the principal point of contact on behalf of the State and will be the principal point of contact for Contractor concerning Contractor’s performance under this Contract.

2.3 TAXES

Contractor is responsible for payment of all applicable taxes from the funds to be received under this contract. Contractor's federal tax identification number is _________________.

3 COMPENSATION AND MAXIMUM AMOUNT OF CONTRACT

3.1 PAYMENT TERMS

In consideration of the services required by this contract, State hereby agrees to pay to Contractor a maximum fee of $[TO BE INSERTED]. Payments are predicated upon successful completion and written approval by the State of the described tasks and deliverables as provided Statement of Work. Payments will be made to the Contractor after written acceptance by the State of the payment task and approval of an invoice. State will make every reasonable effort to make payments within 30 days of the approval of invoice and under a valid contract. Payment will be made only on approval of Lee Bairnsfather, Ph.D..

During the execution of tasks contained in the Statement of Work, the Contractor may submit invoices, not more frequently than monthly. The payment terms are as follows:

Such payment amounts for work performed must be based on at least equivalent services rendered, and to the extent practical, will be keyed to clearly identifiable stages of progress as reflected in written reports submitted with the invoices. Contractor will not be paid more than the maximum amount of the contract.

Ten percent (10%) of fees approved by State Project Coordinator to be paid shall be withheld as retainage pending successful completion of the contract. Upon completion of all tasks contained in the Statement of Work to the satisfaction of the State, any amounts previously withheld will be paid.

4 TERMINATION

4.1 TERMINATION FOR CAUSE

State may terminate this Contract for cause based upon the failure of Contractor to comply with the terms and/or conditions of the Contract; provided that the State shall give the Contractor written notice specifying the Contractor’s failure. If within thirty (30) days after receipt of such notice, the Contractor shall not have either corrected such failure or, in the case of failure which cannot be corrected in thirty (30) days, begun in good faith to correct said failure and thereafter proceeded diligently to complete such correction, then the State may, at its option, place the Contractor in default and the Contract shall terminate on the date specified in such notice. Failure to perform within the time specified in the solicitation will constitute default and may cause cancellation of the contract. Contractor may exercise any rights available to it under Louisiana law to terminate for cause upon the failure of the State to comply with the terms and conditions of this contract provided that the Contractor shall give the State written notice specifying the State agency’s failure and a reasonable opportunity for the state to cure the defect.

4.2 TERMINATION FOR CONVENIENCE

State may terminate the Contract at any time without penalty by giving thirty (30) days written notice to the Contractor of such termination or negotiating with the Contractor an effective date.

Contractor shall be entitled to payment for deliverables in progress, to the extent work has been performed satisfactorily.

4.3 TERMINATION FOR NON-APPROPRIATION OF FUNDS

The continuation of this contract is contingent upon the appropriation of funds by the legislature to fulfill the requirements of the contract by the legislature. If the legislature fails to appropriate sufficient monies to provide for the continuation of the contract, or if such appropriation is reduced by the veto of the Governor or by any means provided in the appropriations act of Title 39 of the Louisiana Revised Statutes of 1950 to prevent the total appropriation for the year from exceeding revenues for that year, or for any other lawful purpose, and the effect of such reduction is to provide insufficient monies for the continuation of the contract, the contract shall terminate on the date of the beginning of the first fiscal year for which funds have not been appropriated.

5 INDEMNIFICATION AND LIMITATION OF LIABILITY

Neither party shall be liable for any delay or failure in performance beyond its control resulting from acts of God or force majeure. The parties shall use reasonable efforts to eliminate or minimize the effect of such events upon performance of their respective duties under Contract.

Contractor shall be fully liable for the actions of its agents, employees, partners or subcontractors and shall fully indemnify and hold harmless the State and its Authorized Users from suits, actions, damages and costs of every name and description relating to personal injury and damage to real or personal tangible property caused by Contractor, its agents, employees, partners or subcontractors, without limitation; provided, however, that the Contractor shall not indemnify for that portion of any claim, loss or damage arising hereunder due to the negligent act or failure to act of the State. Contractor will indemnify, defend and hold the State and its Authorized Users harmless, without limitation, from and against any and all damages, expenses (including reasonable attorneys' fees), claims, judgments, liabilities and costs which may be finally assessed against the State in any action for infringement of a United States Letter Patent with respect to the Products furnished, or of any copyright, trademark, trade secret or intellectual property right, provided that the State shall give the Contractor: (i) prompt written notice of any action, claim or threat of infringement suit, or other suit, (ii) the opportunity to take over, settle or defend such action, claim or suit at Contractor's sole expense, and (iii) assistance in the defense of any such action at the expense of Contractor. Where a dispute or claim arises relative to a real or anticipated infringement, the State or its Authorized Users may require Contractor, at its sole expense, to submit such information and documentation, including formal patent attorney opinions, as the Commissioner of Administration shall require.

The Contractor shall not be obligated to indemnify that portion of a claim or dispute based upon: i) Authorized User's unauthorized modification or alteration of a Product; ii) Authorized User's use of the Product in combination with other products not furnished by Contractor; iii) Authorized User's use in other than the specified operating conditions and environment.

In addition to the foregoing, if the use of any item(s) or part(s) thereof shall be enjoined for any reason or if Contractor believes that it may be enjoined, Contractor shall have the right, at its

own expense and sole discretion as the Authorized User's exclusive remedy to take action in the following order of precedence: (i) to procure for the State the right to continue using such item(s) or part (s) thereof, as applicable; (ii) to modify the component so that it becomes non-infringing equipment of at least equal quality and performance; or (iii) to replace said item(s) or part(s) thereof, as applicable, with non-infringing components of at least equal quality and performance, or (iv) if none of the foregoing is commercially reasonable, then provide monetary compensation to the State up to the dollar amount of the Contract.

For all other claims against the Contractor where liability is not otherwise set forth in the Contract as being "without limitation", and regardless of the basis on which the claim is made, Contractor's liability for direct damages, shall be the greater of $100,000, the dollar amount of the Contract, or two (2) times the charges rendered by the Contractor under the Contract. Unless otherwise specifically enumerated herein or in the work order mutually agreed between the parties, neither party shall be liable to the other for special, indirect or consequential damages, including lost data or records (unless the Contractor is required to back-up the data or records as part of the work plan), even if the party has been advised of the possibility of such damages. Neither party shall be liable for lost profits, lost revenue or lost institutional operating savings.

The State and Authorized User may, in addition to other remedies available to them at law or equity and upon notice to the Contractor, retain such monies from amounts due Contractor, or may proceed against the performance and payment bond, if any, as may be necessary to satisfy any claim for damages, penalties, costs and the like asserted by or against them.

6 CONTRACT CONTROVERSIES

Any claim or controversy arising out of the contract shall be resolved by the provisions of Louisiana Revised Statutes 39:1524-26.

7 FUND USE

Contractor agrees not to use contract proceeds to urge any elector to vote for or against anycandidate or proposition on an election ballot nor shall such funds be used to lobby for or against any proposition or matter having the effect of law being considered by the Louisiana Legislature or any local governing authority. This provision shall not prevent the normal dissemination of factual information relative to a proposition on any election ballot or a proposition or matter having the effect of law being considered by the Louisiana Legislature or any local governing authority.

8 ASSIGNMENT

No contractor shall assign any interest in this contract by assignment, transfer, or novation, without prior written consent of the State. This provision shall not be construed to prohibit the contractor from assigning to a bank, trust company, or other financial institution any money due or to become due from approved contracts without such prior written consent. Notice of any such assignment or transfer shall be furnished promptly to the State.

9 RIGHT TO AUDIT

The State Legislative Auditor, agency auditors, Federal auditors, and internal auditors of the Division of Administration shall have the option to audit all accounts directly pertaining to the contract for a period of five (5) years from the date of the last payment made under this contract. Records shall be made available during normal working hours for this purpose.

10 CONTRACT MODIFICATION

No amendment or variation of the terms of this contract shall be valid unless made in writing, signed by the parties and approved as required by law. No oral understanding or agreementnot incorporated in the contract is binding on any of the parties.

11 CONFIDENTIALITY OF DATA

All financial, statistical, personal, technical and other data and information relating to the State's operation which are designated confidential by the State and made available to the contractor in order to carry out this contract, or which become available to the contractor in carrying out this contract, shall be protected by the contractor from unauthorized use and disclosure through the observance of the same or more effective procedural requirements as are applicable to the State. The identification of all such confidential data and information as well as the State's procedural requirements for protection of such data and information from unauthorized use and disclosure shall be provided by the State in writing to the contractor. If the methods and procedures employed by the contractor for the protection of the contractor's data and information are deemed by the State to be adequate for the protection of the State's confidential information, such methods and procedures may be used, with the written consent of the State, to carry out the intent of this paragraph. The contractor shall not be required under the provisions of the paragraph to keep confidential any data or information which is or becomes publicly available, is already rightfully in the contractor's possession, is independently developed by the contractor outside the scope of the contract, or is rightfully obtained from third parties.

12 SUBCONTRACTORS

The Contractor may, with prior written permission from the State, enter into subcontracts with third parties for the performance of any part of the Contractor’s duties and obligations. In no event shall the existence of a subcontract operate to release or reduce the liability of the Contractor to the State and/or State Agency for any breach in the performance of the Contractor's duties.

13 COMPLIANCE WITH CIVIL RIGHTS LAWS

The contractor agrees to abide by the requirements of the following as applicable: Title VI and Title VII of the Civil Rights Act of 1964, as amended by the Equal Opportunity Act of 1972, Federal Executive Order 11246, the Federal Rehabilitation Act of 1973, as amended, the Vietnam Era Veteran’s Readjustment Assistance Act of 1974, Title IX of the Education Amendments of 1972, the Age Act of 1975, and contractor agrees to abide by the requirements of the Americans with Disabilities Act of 1990.

Contractor agrees not to discriminate in its employment practices, and will render services under this contract without regard to race, color, religion, sex, sexual orientation, national origin, veteran status, political affiliation, or disabilities. Any act of discrimination committed by Contractor, or failure to comply with these statutory obligations when applicable shall be grounds for termination of this contract.

14 INSURANCE

Insurance shall be placed with insurers with an A.M. Best’s rating of no less than A+: XV.

This rating requirement shall be waived for Worker’s Compensation coverage only.

Contractor's Insurance: The Contractor shall not commence work under this contract until he has obtained all insurance required herein. Certificates of Insurance, fully executed by officers of the Insurance Company written or countersigned by an authorized Louisiana State agency, shall be filed with the State of Louisiana for approval. The Contractor shall not allow any sub-contractor to commence work on his subcontract until all similar insurance required for the subcontractor has been obtained and approved. If so requested, the Contractor shall also submit copies of insurance policies for inspection and approval of the State of Louisiana before work is commenced. Said policies shall not hereafter be canceled, permitted to expire, or be changed without thirty (30) days' notice in advance to the State of Louisiana and consented to by the State of Louisiana in writing and the policies shall so provide.

Compensation Insurance: Before any work is commenced, the Contractor shall maintain during the life of the contract, Workers’ Compensation Insurance for all of the Contractor’s employees employed at the site of the project. In case any work is sublet, the Contractor shall require the subcontractor similarly to provide Workers’ Compensation Insurance for all the latter’s employees, unless such employees are covered by the protection afforded by the Contractor. In case any class of employees engaged in work under the contract at the site of the project is not protected under the Workers’ Compensation Statute, the Contractor shall provide for any such employees, and shall further provide or cause any and all subcontractors to provide Employer’s Liability Insurance for the protection of such employees not protected by the Workers’ Compensation Statute.

Commercial General Liability Insurance: The Contractor shall maintain during the life of the contract such Commercial General Liability Insurance which shall protect him, the State, and any subcontractor during the performance of work covered by the contract from claims or damages for personal injury, including accidental death, as well as for claims for property damages, which may arise from operations under the contract, whether such operations be by himself or by a subcontractor, or by anyone directly or indirectly employed by either or them, or in such a manner as to impose liability to the State. Such insurance shall name the State as additional insured for claims arising from or as the result of the operations of the Contractor or his subcontractors. In the absence of specific regulations, the amount of coverage shall be as follows: Commercial General Liability Insurance, including bodily injury, property damage and contractual liability, with combined single limits of $5,000,000.

Insurance Covering Special Hazards: Special hazards as determined by the State shall be covered by rider or riders in the Commercial General Liability Insurance Policy or policies herein

elsewhere required to be furnished by the Contractor, or by separate policies of insurance in the amounts as defined in any Special Conditions of the contract included therewith.

Licensed and Non-Licensed Motor Vehicles: The Contractor shall maintain during the life of the contract, Automobile Liability Insurance in an amount not less than combined single limits of $1,000,000 per occurrence for bodily injury/property damage. Such insurance shall cover the use of any non-licensed motor vehicles engaged in operations within the terms of the contract on the site of the work to be performed there under, unless such coverage is included in insurance elsewhere specified.

Subcontractor’s Insurance: The Contractor shall require that any and all subcontractors, which are not protected under the Contractor’s own insurance policies, take and maintain insurance of the same nature and in the same amounts as required of the Contractor.

15 APPLICABLE LAW

This contract shall be governed by and interpreted in accordance with the laws ofthe State of Louisiana. Venue of any action brought with regard to this contract shall be in theNineteenth Judicial District Court, parish of East Baton Rouge, State of Louisiana.

16 CODE OF ETHICS

The contractor acknowledges that Chapter 15 of Title 42 of the Louisiana Revised Statutes (R.S. 42:1101 et. seq., Code of Governmental Ethics) applies to the Contracting Party in the Performance of services called for in this contract. The contractor agrees to immediately notify the state if potential violations of the Code of Governmental Ethics arise at any time during the term of this contract.

17 SEVERABILITY

If any term or condition of this Contract or the application thereof is held invalid, suchinvalidity shall not affect other terms, conditions, or applications which can be given effectwithout the invalid term, condition, or application; to this end the terms and conditions of thisContract are declared severable.

18 COMPLETE CONTRACT

This is the complete Contract between the parties with respect to the subject matter and all prior discussions and negotiations are merged into this contract. This Contract is entered into with neither party relying on any statement or representation made by the other party not embodied in this Contract and there are no other agreements or understanding changing or modifying the terms. This Contract shall become effective upon final statutory approval.

19 ORDER OF PRECEDENCE

This contract shall, to the extent possible, be construed to give effect to all of its provisions; however, where provisions are in conflict, first priority shall be given to the provisions of the

contract, excluding the Request for Proposals, its amendments and the Proposal; second priority shall be given to the provisions of the Request for Proposals and its amendments; and third priority shall be given to the provisions of the Proposal.

THUS DONE AND SIGNED on the date(s) noted below:

CONTRACTOR’S SIGNATURE STATE’S SIGNATURE

DATE DATE

ATTACHMENT IV: BACKGROUND CORPORATE INFORMATION

QUESTION RESPONSE

1. Please provide a brief history of your company, including but not limited to:

Year company was established

Ownership status (Private or Public)

Major acquisitions, mergers, and/or divestures over the last 5 years

Background of parent company and any related affiliates or subsidiaries

2. Provide the following information on your organization’s employee base. If your company is part of a larger parent corporation, provide this information for the company/division/business unit responding to this RFP.

Name of relevant division/business unit

Total number of employees

Number of development staff within the relevant division/business unit

Number of sales staff within the relevant division/business unit

Number of support staff within the relevant division/business unit

Number of administrative/other staff within the relevant division/business unit

3. Provide the following financial information for your organization. If your company is part of a larger parent corporation, provide this information for the company/division/business unit responding to this RFP.

Annual operating revenue (provide the beginning and end month of the Financial Year for your organization)

2008: $____________________

2007: $____________________

2006: $____________________

2005: $____________________

Percentage of operating revenue devoted to research and development

2008: ____________________%

2007: ____________________%

2006: ____________________%

2005: ____________________%

QUESTION RESPONSE

Percentage of operating revenue earmarked for research and development over the next 5-to-10 years

ATTACHMENT V: EHR COMPONENTS

No. Electronic Health Record Component Priority

RequiredHighly Desired

Desired

A. Patient Management/Patient Accounting Systems

1Admission/Discharge/Transfer Registration System (including bed management) x

2 Patient Tracking System x

3 Enterprise Master Patient Index x

4 Patient Accounting x

5 Physician Billing x

6 Payor Verification/Eligibility x

7 Document Imaging (Business Office and Clinical) x

8Medical Records Management (coding, abstracting, chart management, release of info.) x

9 Transcription x

10 Enterprise Patient and Resource Scheduling x

11Integrated Physician Consult Management (notification and scheduling) x

B. Clinical Information Systems

12 Computerized Physician Order Entry (CPOE) x

13 Order Entry x

14 Results Management x

15 Clinical Data Repository x

16 Clinical Decision Support x

17Device integration (monitors, pumps, POC testing – with automated data capture features) x

18 Real-time Clinical Alerts x

19 Critical Results Notification x

20 Clinical Messaging x

21 Multi-disciplinary Clinical Documentation x

22 Clinical Content x

23Clinical Trials Management (including compliance management) x

24 Patient/Consumer Portal x

25 Physician Portal x



Desired

26 Patient Acuity x

27 Medication Administration Record (with bar coding) x

C. Ancillary Systems

28Pharmacy Management (including e-prescribing, Pyxis interface) x

29 Outpatient Pharmacy x

30

Laboratory/Pathology Information Systems (general, microbiology, blood bank, anatomic pathology with PACS interface, reference lab, instrument interfaces) x

D. Enterprise Resource Management Systems

31 Materials Management (surgical, clinical) x

E. Specialty Systems

32Peri-operative System (pre-op, surgical, post-op, anesthesia) x

33 Emergency Department x

34 Cardiology Information System (with PACS interface) x

35 Oncology Information System x

36 Infection Control Reporting x

37Allied Health System (Occupational, Physical, Speech & Respiratory Therapy) x

38 Hemodynamic Monitoring x

39 NICU x

40 ICU x

41 Labor & Delivery (bedside charting, monitoring) x

F. Decision Support System or Functions

42 Outcomes Management/Performance Improvement x

43 Risk Management/Quality Assurance x

44 Case Management & Utilization Review x

45 Clinical and Financial Data Warehouse x

46 Expert analytics and reporting x

47 User reporting tools x

48 Medical Staff Credentialing x

G. Ambulatory Information Systems

49Ambulatory EMR (e-prescribing, clinical content, clinician documentation, etc.) x

50 Ambulatory clinic and practice management x



Desired

(administrative tools)

H. Technical

51 Biometrics x

52 Workflow Engine x

53 Rules Engine x

54 Interface Engine x

55 Data Dictionary x

56Communication tools (especially between clinical providers) x

57 Phone Call Management x

58 Integrated Voice Response x

59 Single Sign-on Integrated with Microsoft Active Directory x

60 High Availability x

61 Disaster Recovery x

62 Operating Software x

63System Tools (including strong user access security features) x

64HIPAA Compliance Support (auditing, security and patient confidentiality features) x

ATTACHMENT VI: COMPLIANCE CRITERIA

1. Proposers will be evaluated for compliance under the following criteria that are deemed minimum qualifications for further consideration in the EHR selection process. Proposers must be determined to be compliant with ALL of these criteria to continue in the selection process. Please indicate your positive response where indicated.

a. Proposer has achieved 2007 or 2008 Inpatient EHR Certification with the Certification Commission for Healthcare Information Technology (CCHIT) on the proposed inpatient clinical product suite, which must be owned by the Proposer.

Response:_____________

b. Proposer has achieved 2007 or 2008 Ambulatory EHR Certification with CCHIT on the proposed ambulatory clinical product suite, which may be owned by the Proposer, or offered in partnership with an ambulatory systems proposer on the condition that the Proposer will be the single contracting body with LSU for all proposed products.

Response:_____________

c. With reference to Attachment V: EHR Components, Proposer must supply 100% of the functions marked “Required” in Group A (Patient Management/Patient Accounting Systems) AND Group B (Clinical Information Systems) from its own product suite (i.e., no third party or sub-contracted systems). In Attachment XI(a), Proposer must provide the line-item cost for these components.

Response:_____________

d. Proposer has at least one current Academic Medical Center (AMC) client using inpatient clinical applications from its own product suite. Provide the name and contact information of the AMC client, the applications implemented, and the year the first application went live.

Response:

e. Proposer has at least two health system clients, each comprised of three or more hospitals, which use inpatient clinical applications from the Proposer’s product suite. For each of these client health systems, key volumes within the last three years must equal or exceed the following metrics that represent

approximately 1/3 of the 2006 LSU system volumes indicated in Table 1:Key Metrics. For documentation, Proposer must complete Table 1: Key Metrics by inserting the name and location of the client, the number of hospitals in the health system that are implemented on the Proposer solutions, the year for which data is provided, and the volumes listed (estimates are acceptable).

Table 1: Key Metrics

Key Metric Benchmark(Volumes below are 1/3 of LSU

actual)

Client 1: name, location.

Client 2: name, location.

Number of hospital sites in health system implemented on I/P clinical applications

3

Year for which volumes are provided

2006

Annual Inpatient discharges 16,000Annual Ambulatory visits excluding ED

400,000

Annual ED visits, including admits from ED

120,000

Annual Number of deliveries 1,500Number of licensed beds 700

f. Proposer must complete Table 2: Clients of Attachment VII by listing at least 3 clients .

Response:_____________ (See Attachment VII)

ATTACHMENT VII: CLIENT BASE

1. Describe your experience with implementation and support of the proposed products at academic health systems that have facilities in geographically diverse areas.

2. Describe your experience with health systems that share patient data between hospital sites and multiple ambulatory clinics. What kind of data is shared? How is it synchronized across locations?

3. Provide a representative client list of hospitals or health system clients currently using or contracted to use your PM/PA, CIS, Ambulatory EMR and related products. Provide all the information requested in Table 2 for each client site: (Add more rows as required). It is important that sufficient information is provided to allow LSU to evaluate each proposer’s experience in implementing these products in comparable environments, and to provide contacts for future reference checks and site visits. A minimum of 3 client sites is required (meaning 3 different clients, not 3 hospital sites belonging to a single client), but proposer must provide at least one client reference for every application in the proposal. Failure to provide this information will be deemed as non-responsive and will result in elimination from the selection process.

Table 2: Client Sites

Client Name and Location

Contact Name, Title, and Telephone

Number

Number Beds

Number Ambulatory Visits

and Other Relevant Statistics

Products Installed and Date Products

Went Live

Recommended for Reference

Call and/or Site Visit?

For those sites recommended as a reference call or site visit location in the last column of this table, indicate if the site is being recommended for specific products and list them.

ATTACHMENT VIII: PROPOSED APPLICATIONS

Complete Table 3: Proposed Applications below according to these instructions and attach collateral such as brochures, sample reports, etc if available. In addition, describe the means by which applications in your proposed product suite(s) are integrated to optimize data flow and work flow and minimize the need for duplicate data entry.

A – name the application(s)/module(s) that you are proposing to meet the feature or

function indicated on each line, and provide the current version number(s). B – specify when this component was first released, or is planned for General

Availability. C – state the source of the component (Internally Developed, Acquired, or via Business Partner). D – indicate which products are Core integrated components of the base system(s)

(meaning that the components access the same database, share common master files and tables, were written using common tools and architecture and are internally synchronized), and which are separate interfaced components.

E – provide by application the number of clients (not sites) that have contracted for this application, but are not yet live.

F – enter the number of contracted clients that are operational on the application, and the number of individual sites running the application across this client base (e.g., two clients that each have two hospital sites using the system would be listed as 2 / 4)

Table 3: Proposed Applications

A B C D E F

APPLICATION / FEATURE

Product name

And

current version

Date first released

as generally available

Source

(options are:

internally developed, acquired,

or business partner)

Core integrated

or interfaced component

Number of contracted clients (but

not yet live)

Number of operational

clients

/

Sites implemented

A. Patient Management/Patient Accounting Systems

Admission/Discharge/ Transfer Registration System (including bed management)

Patient Tracking System

Enterprise Master Patient Index

Patient Accounting

A B C D E F


Product name

And

current version

Date first released


Source

(options are:



Core integrated



not yet live)


clients

/

Sites implemented

Physician Billing

Payor Verification/Eligibility

Document Imaging (Business Office and Clinical)Medical Records Management (coding, abstracting, chart management, release of info.)

Transcription

Enterprise Patient and Resource SchedulingIntegrated Physician Consult Management (notification and scheduling)

B. Clinical Information Systems

Computerized Physician Order Entry (CPOE)

Order Entry

Results Management

Clinical Data Repository

Clinical Decision Support

Device integration (monitors, pumps, POC testing – with automated data capture features)

Real-time Clinical Alerts

Critical Results Notification

Clinical Messaging

Multi-disciplinary Clinical Documentation

Clinical Content

A B C D E F


Product name

And

current version

Date first released


Source

(options are:



Core integrated



not yet live)


clients

/

Sites implemented

Clinical Trials Management (including compliance management)

Patient/Consumer Portal

Physician Portal

Patient Acuity

Medication Administration Record (with bar coding)

C. Ancillary Systems

Pharmacy Management (including e-prescribing, Pyxis interface)

Outpatient Pharmacy

Laboratory/Pathology Information Systems (general, microbiology, blood bank, anatomic pathology with PACS interface, reference lab, instrument interfaces)

D. Enterprise Resource Management Systems

Materials Management (surgical, clinical)

E. Specialty Systems

Emergency Department

Peri-operative System (pre-op, surgical, post-op, anesthesia)Cardiology Information System (with PACS interface)

Hemodynamic Monitoring

Oncology Information System

Infection Control Reporting

A B C D E F


Product name

And

current version

Date first released


Source

(options are:



Core integrated



not yet live)


clients

/

Sites implemented

Allied Health System (Occupational, Physical, Speech & Respiratory Therapy)

NICU

ICU

Labor & Delivery (bedside charting, monitoring)

F. Decision Support System or Functions

Outcomes Management/Performance ImprovementRisk Management/Quality AssuranceCase Management & Utilization ReviewClinical and Financial Data WarehouseExpert analytics and reporting

User reporting tools

Medical Staff Credentialing

G. Ambulatory Information Systems

Ambulatory EMR (e-prescribing, clinical content, clinician documentation, etc.)Ambulatory clinic and practice management (administrative tools)

H. Technical

Biometrics

Workflow Engine

Rules Engine

Interface Engine

A B C D E F


Product name

And

current version

Date first released


Source

(options are:



Core integrated



not yet live)


clients

/

Sites implemented

Data Dictionary

Communication tools (especially between clinical providers)

Phone Call Management

Integrated Voice Response

Single Sign-on Integrated with Microsoft Active Directory

High Availability

Disaster Recovery

Operating Software

System Tools (including strong user access security features)HIPAA Compliance Support (auditing, security and patient confidentiality features)

OTHER APPLICATIONS

Please list any other applications that may be of interest to LSU

ATTACHMENT IX: APPLICATION INTERFACE EXPERIENCE

1. Describe your experience with interfacing your applications to the applications that are currently in place at LSU or that will be in place at LSU in the near future as listed in Table 4: Application Interface Experience. Add lines as needed to describe different types of interfaces that your organization has created to the LSU applications listed.

2. What is your interface development methodology? Please provide specific detail on your proposed solution for integrating or interfacing retained LSU applications to the application portfolio that you are proposing.

3. Is entry or modification of data in any part of the proposed application suite instantly reflected and available in all other parts of the proposed application suite, implying “true” integration of data? If not, explain why.

Table 4: Application Interface Experience

LSU System VendorNumber of interfaces completed

Outline description of data being interfaced

Batch or continuous?

One-way or Bi-directional?

Data exchange format (HL7, Flat file, DICOM etc.)

PMPA/Administrative ADT system Siemens Master patient index/Enterprise Access Directory (EAD)

Siemens, Initiate

Clinical and Financial Data Warehouse (DSS)

Siemens

HDX Payor Verification Siemens Medicaid Eligibility Siemens Administrative Document Imaging

Siemens, LaserFiche

Medical Staff Credentialing

Cactus/ iPrivileges, MDStaff

Clinical Trials Management

MCAnalyze

Coding (3M) 3M Medical Records Management

Softmed

Report Distribution VPS, RAS






Physician Billing

GE/IDX FlowCast, AllScripts, Medisoft

Release of Information SourceCorp Transcription

Transcription Clinic Summary Notes

Various (Spheris, Softmed, Dictaphone)

Transcription Histories and Physicals

Various (Spheris, Softmed, Dictaphone, Scribedoc, Iridium)

Transcription Discharge, Death, Transfer Summaries

Various (Spheris, Iridium, Dictaphone etc.)

Transcription Consult Reports


Transcription Operative Reports


Transcription Lab/Pathology Reports

Misys

Transcription Outside Lab Reports

Vendor

Transcription Cardiology Staff

Transcription Radiology

Various (RadTalk, SpeechQ, Neurostar)

Scheduling Outpatient scheduling system

Siemens

Nurse Scheduling System

ANSOS






Surgery Scheduling System

ORSOS

Electronic Health Record

Computerized physican order entry system

Siemens (Shreveport only)

e-Prescribing system None

Clinical data repository

CLIQ (internally developed), Siemens LCR

Residency Training EMR iMed

Results management system

CLIQ (internally developed), Siemens NetAccess

Medication administration system

Siemens MAK(Shreveport only), Intellidot

Departmental

Emergency department information/tracking system

Doctor’s Choice (Shreveport only), Emergisoft, CMR

Cardiology Information system

Cardiology PACSMuse (Shreveport only)

Oncology Information system

Eclipsys SCM (Shreveport only)

Infection Control Reporting System

Respond. AICE

Radiology Information system w/mammo

GE

Picture archiving and communication system

GE

Inpatient pharmacy system

McKesson, Siemens






Outpatient pharmacy system

McKesson, Siemens, QS1

Pharmacy Dispensing system

Pyxis, MedSelect

Laboratory / Pathology information systems

Misys,

NICU System Neodata

Lab Tracker HIV LabsGround Zero, Careware

L&D Bedside Charting System

OBIX (CSSI), Spacelabs

Mammography Management

GE

Point of Care Testing RALS

Indigent Pharmacy QS1, MDCares/Prisim

Coumadin Tracking CoumaCare

Ultrasound PACS

GE Ultrasound PACS (Shreveport and Conway)

Fetal Monitor

OBIX (Shreveport and Conway)

ATTACHMENT X: ADDITIONAL PRODUCT INFORMATION

SECTION A: PATIENT MANAGEMENT/PATIENT ACCOUNTING (PM/PA)

1. This question intentionally left blank.

2. Provide information about the utilization of the following features in your PM/PA applications if applicable. How do these features contribute to optimization of revenue cycle and patient management processes?

Workflow Engine

Rules Engine

Notes features

3. Describe Enterprise Master Person Index functionality including coordination of multiple identification numbers from external systems.

4. Describe enterprise patient scheduling that coordinates multiple resources across multiple settings, with system alerts that are available to notify the scheduler of special circumstances (i.e., need for authorization for service).

5. Is real-time insurance eligibility verification integrated with the registration application? How does this communication occur?

6. What claim scrubbing and editing tools and features are available to assist in the generation of accurate claims?

7. Describe how your company meets the billing requirements for the following specialized areas. If your company has not developed a software product that addresses one or more of these areas, please note any proposer partnerships that you have developed to meet these needs.

Clinic (Ambulatory) Billing

Outreach Services (such as reference labs)

Home Health

Medical Transportation

8. Describe any remote chart analysis and/or remote chart completion functionality.

SECTION B: CLINICAL

9. Does the system support the use of standardized assessment tools and meets Nursing Information and Data Set Evaluation Center (NIDSEC) Standards and Scoring Guidelines?

10. Describe options available in configuration of nursing documentation templates and workflows.

11. Describe your Orders module and its ability to support standard order sets.

12. Describe the integration of your system among the CPOE, Pharmacy and on-line MAR components.

13. Do you offer a wireless, bedside, barcode based medication administration verification system?

14. Describe how critical care documentation integrates with the base clinical information system (CIS).

15. Does the system have a surgery scheduling module? Does it have a surgery patient tracking module? If not, have you worked to interface with any surgical systems proposers?

16. Describe what the CIS system provides for reports – patient specific, diagnosis specific, unit specific, discipline specific, including infection control, aggregate reports. Provide sample reports.

17. Describe available interactive clinical decision support capabilities of your system whereby orders can be assessed against a knowledge-based rules engine that references drug interactions, clinical protocols, relevant lab results, and research and educational databases. Describe the methods by which clinicians are notified of adverse alerts and events.

18. Describe your system for reporting critical results.

SECTION C: TECHNICAL

19. Describe the overall technical environment. Include diagrams of the environment. Is this a client/server system? If yes, is this 3-tier or n-tier system?

20. What is the language or software used for developing the system for both client and server components?

21. What database systems are supported?

22. Do you support a web-based or thin-client architecture for full application functionality delivery? Describe.

23. Describe your user interface and any tools available to the customer to aid screen and form redesign.

24. Identify any configuration features that require proposer intervention to complete, other than one-off custom requests that require special programming to build (e.g., new screen design, configuration of new payer contract terms).

25. Describe the data conversion process involved with migrating patient information form current LSU systems to your system.

26. For interfaces and EDI, what standard formats do you adhere to and state current versions of these formats?

27. How would your system assist LSU in becoming compliant with HIPAA regulations, particularly related to Privacy and Security?

28. Describe your web strategy. What are your future plans in this area?

29. What features or contingencies are included in the system for protection and rapid recovery of data such as redundant servers, disk mirroring etc.?

30. Do you offer both in-house and ASP/remote hosting options?

31. Describe future development plans for your products.

SECTION D: IMPLEMENTATION AND SUPPORT

32. Describe your implementation strategy and the resources that will be provided by your organization.

33. Indicate whether your organization will provide the following as part of your implementation process:

Workflow analysis and process change requirements

Operational analysis

Development of performance improvement targets

34. Please describe the recommended LSU staff requirements necessary to install and operate the product(s) across the LSU systems of hospitals and clinics (in addition to the resources you are proposing for implementation). Complete Table 5 below as part of your response. If the time and staff commitment for an ASP/remote hosted implementation is different, provide that information in a separate table.

Table 5: LSU Implementation Staffing Requirements

LSU Staff category Skill set summaryFTEs required for

implementation activities

FTEs required for ongoing activities

Project Director

Project Manager

Database Administrators

Clinical Staff

Administrative Staff

Training and End User Support

Clinical Application Analysts

Others (please specify_____)

Operations (hardware and systems)

35. Please describe the ongoing system and customer support offered to your clients.

36. Do you support a web-based or thin-client architecture for full application functionality delivery? Describe.

37. Describe your user interface and any tools available to the customer to aid screen and form redesign.

38. Identify any configuration features that require proposer intervention to complete, other than one-off custom requests that require special programming to build (e.g., new screen design, configuration of new payer contract terms).

39. Describe the data conversion process involved with migrating patient information form current LSU systems to your system.

40. For interfaces and EDI, what standard formats do you adhere to and state current versions of these formats?

41. How would your system assist LSU in becoming compliant with HIPAA regulations, particularly related to Privacy and Security?

42. Describe your web strategy. What are your future plans in this area?

43. What features or contingencies are included in the system for protection and rapid recovery of data such as redundant servers, disk mirroring etc.?

44. Do you offer both in-house and ASP/remote hosting options?

45. Describe future development plans for your products.

ATTACHMENT XI: COST PROPOSAL

Provide a cost proposal for the products listed in your response using the multi-tabbed spreadsheets in Attachment XI(a): Cost Proposal. To the degree possible, please provide separate pricing for each application requested. Be sure to indicate all costs associated with each application including the implementation and training cost per application, any related subscription services, etc. Detail your assumptions for each option and each cost item.

Please use the Microsoft Excel spreadsheets as the format for your cost proposal to facilitate accurate normalization and analysis of your response. Proposer must submit the cost proposal in this standard format IN ADDITION TO filling out these sheets. Although printed and electronic formats of the RFP response are required, do not convert the Excel sheets to Adobe Acrobat when submitting the electronic version.

As indicated in Section 6.3, LSU will only consider total cost of required components and services as shown on Attachment V in determining the RFP Total Cost Score for Proposer. However, LSU may also be interested in considering (a) cost proposals for BOTH remote-hosted or ASP solutions; (b) Catalog Pricing proposal for all products. Such additional information may be provided in a Microsoft Excel spreadsheet.

ATTACHMENT XII: UTILIZATION FOR FY2007-08

LSU Profile

Earl K Long Med. Ctr.(EKL)

Med. Ctr. LA New Orleans (MCL)

Bogalusa Med. Ctr.(BMC)

Lallie Kemp Reg. Med. Ctr.(LAK)

Huey P. Long Med. Ctr (HPL)

Inpatient discharges - Annual 7,345 11,985 2,552 989 2,665Outpatient Visits - Annual 162,285 147,216 92,380 79,462 58,410ER Visits (Annual) - includes Admits from ER 43,716 52,915 28,320 26,158 38,503Number of Deliveries 745 907 0 0 186Total # of Beds - Licensed 161 714 90 25 137Total # of Beds - Staffed 135 211 51 17 60# of patient monitoring devices 106 226 42 30 70

Number of physicians on staff (LJC - staff, visiting docs, CRNAs, PA, NP, LSU, Ochsner) 424 944 103 74 138Number of clinical system concurrent users 650 500 250 175 100Number of clinical system workstations 700 600 300 200 312Total number of Pharmacy Orders last year 127,356 284,484 66,216 184,895 61,638Pharmacy Retail prescriptions QS1 139,501 38,462 12,022 13,825 103,345Total number of Radiology Orders last year 63,826 155,900 35,100 31,732 41,931Total number of Laboratory Orders last year 666,491 192,686 277,520 184,750 629,544Number of beds for the following Inpatient areas: Medical 25 48 17 12Surgical (med and surg cmbnd for EAC, EKL, HPL) 71 54 3 3 13ICU 10 10 8 4 4CCU 0OB/GYN (LAK in surgical) 13 10 5Nursery 24 6 0 8NICU 15 14 0 0Pediatrics (HPL in surgical) 0 1 10Detox 5 Psychiatric 16Number of beds for the following outpatient areas: Dialysis 12 4 2 1 Oncology/Cancer Center 0 0 11 Endoscopy 1 8 2 1 Cardiology 0 2 0 1 Oral Surgery ACC Infusion Area Women and Children's

Number of hospital based clinics 7 37 15 30 48

LSU ProfileW. O. Moss

University Med. Ctr.

L.J. Chabert

E A Conway

Shreveport Med. Ctr. Total

Reg. Med. Ctr. (WOM)

(UMC)Med. Ctr.(LJC)

(EAC) (SHV)

Inpatient discharges - Annual 1,400 5,712 5,643 6466 19,649 33,005Outpatient Visits - Annual 77,516 164,437 170,749 108,692 425,125 946,519ER Visits (Annual) - includes Admits from ER 24,767 45,075 42,400 34,069 54,195 200,506Number of Deliveries 0 361 520 1077 1,282 3,240Total # of Beds - Licensed 74 150 156 247 436 1,063Total # of Beds - Staffed 31 110 95 158 386 780# of patient monitoring devices 25 112 57 85 175

Number of physicians on staff (LJC - staff, visiting docs, CRNAs, PA, NP, LSU, Ochsner) 110 703 220 88 464 1,585Number of clinical system concurrent users 75 50 300 234 1,500 2,159Number of clinical system workstations 175 280 300 312 2,500 3,567Total number of Pharmacy Orders last year 30,792 155,712 118,485 167,074 792,000 1,264,063Pharmacy Retail prescriptions QS1 47,902 22,570 28,213 98,685Total number of Radiology Orders last year 30,230 72,298 74,380 51,266 171,931 400,105Total number of Laboratory Orders last year 173,774 494,451 1,169,787 359,600 1,503,036 3,700,648Number of beds for the following Inpatient areas: Medical 30 28 34 140 Surgical (med and surg cmbnd for EAC, EKL, HPL) 16 12 34 118 128 ICU 6 8 8 16 40 CCU 27 0 OB/GYN (LAK in surgical) 0 13 17 75 41 Nursery 0 5 26 44 25 NICU 0 5 6 13 40 Pediatrics (HPL in surgical) 2 10 0 11 33 Detox 13 Psychiatric 20 20 24 Number of beds for the following outpatient areas: Dialysis 0 0 0 0 5 Oncology/Cancer Center 0 8 0 11 15 Endoscopy 15 2 0 3 4 Cardiology 0 7 0 0 4

Oral Surgery 7 with monitors

ACC Infusion Area 8 with monitors

Women and Children's 5 with monitors

Number of hospital based clinics 30 24 25 46

22 sites with 48 total clinics (including specialties)

ATTACHMENT XIII: TECHNICAL ENVIRONMENT

Hardware and Data Centers: Except for hardware requiring FDA certification, LSU will independently procure all hardware in accordance with vendor specifications. Any system that requires FDA certification and for which hardware cannot be independently procured by LSU must be identified. LSU will also procure maintenance for hardware. All software applications must be implemented and supported on LSU-provided hardware that matches the software vendor’s specifications. LSU will provide an opportunity for review and comment on hardware specifications. LSU requires hardware and software be specified for identical dual data center, high availability operating model. One data center will be designated primary and the other secondary. The timing process for switching between data centers (failover and restoration) for scheduled and unscheduled switchovers must be described. Methods describing how the two data centers can be used to reduce downtime related to software (vendor and OS) and hardware upgrades must be described. LSU prefers to use blade servers housed in APC “In-line racks.”

Software Maintenance: LSU requires software maintenance for 24x364 support, including problem categories and guaranteed response time by category. LSU also requires customer advocacy options, including statistics regarding the number of other sites the customer advocate supports for each maintenance option. Finally, LSU requires problem escalation procedures.

Software Environment: Except for database servers, LSU desires to operate all servers to be virtualized using VMWare ESX. LSU prefers Microsoft SQL servers and possesses client licenses through a Campus License Agreement. Other technology may be considered, but all license costs must be included. LSU requires that the Windows OS environment can be kept patch current using Microsoft WSUS and SMS/SCCM without the prior approval of the vendor. Any software that cannot be kept patch current in this manner must be identified and a plan to respond to high-priority security threats in a timely manner must be provided.

Security: LSU requires a security model that natively integrates with Microsoft Active Directory. All authentications and user groups will be specified through Microsoft Active Directory. The application may layer in additional application specific security. LSU prefers that users are only able to access the data through the application and not through the database. The security model should use row

level security. The application should provide the ability to delete user accounts and reissue user ID’s at a later date. LSU requires that the application provides an automatic logoff due to inactivity and that the auditing functions adhere to HIPAA standards. The application security should provide a separation of duties between System Administrators and Security Administrators and restrict security related functions from all users including System Administrators.

Network: LSU will provide a 10GB/s backbone between the data centers. The 10 LSU hospitals will connect to the network at speeds from 100Mb/s to 10Gb/s. LSU will be responsible for providing network redundancy between the two data centers.

Data Storage and Retention: The architecture for document retention, data tiering (i.e., movement of seldom used data to less expensive, lower performing storage media), and backup/restore processes must be described.

rfp attachments

Documents

successful proposer

successful implementation

lsu staff requirements

lsu system

deliverables proposer

implementation documentation

implementation services

lsu personnel