RFP # ISD 1805

idleheadedceleryMobile - Wireless

Dec 10, 2013 (3 years and 8 months ago)

194 views


COUNTY OF SAN MATEO, CALIFORNIA




REQUEST FOR PROPOSAL


CORE CLINICAL HEALTH INFORMATION SYSTEM/

INPATIENT ELECTRONIC HEALTH RECORD


RFP # ISD
1805

Proposals must be submitted to:


San Mateo County

Information Services Department

Cyndy Chin, Administr
ative Assistant

222 W. 39
th

Avenue

San Mateo, California 94403


By
2
:
00

P.M.
P
S
T

February 4
, 201
1

Page
2

of
82


This Page Intentionally Blank


Page
3

of
82


REQUEST FOR PROPOSALS

FOR

CORE CLINICAL HEALTH INFORMATION SYSTEM/

INPATIENT ELECTRONIC HEALTH RECORD


Condition of Su
bmission

This Request for Proposals (RFP) is neither a commitment nor a contract of any kind.
The County of San Mateo reserves the right to pursue any and/or all ideas generated by
this request. The costs for developing the proposals are entirely the respo
nsibility of the
proposers and shall not be reimbursed. The County reserves the right to reject any and
all proposals and/or terminate the RFP process if deemed in the best interest of the
County. The County reserves the right to waive any requirements of
this RFP when it
determines that waiving a requirement is in the best interest of the County.

Government Code Sections 6550 et. seq., the “Public Record Act,” defines a public
record as any writing containing information relating to the conduct of the pub
lic
business. The Public Record Act provides that public records shall be disclosed upon
written request, and that any citizen has a right to inspect any public record, unless the
document is exempted from disclosure.

The County of San Mateo cannot repres
ent or guarantee that any information submitted
in resp
onse to this RFP will be confidential. If the County receives a request for any
document submitted in response to this request, it will not assert any privileges that may
exist on behalf of the person
or business entity submitting the proposal. It is the
responsibility of the person or business entity submitting the proposal to assert any
applicable privileges or reasons why the document should not be produced. The
County will attempt in a timely manne
r to inform the person or business entity that
submitted a proposal of the public records request in order to permit the person or
business entity to assert any applicable privileges.














Page
4

of
82



Contents


1.

Purpose of the Request for Proposal

2.

Timeline

3.

General Conditions of Submission

4.

Proposal Contents

5.

Service Capabilities

6.

Proposal Submission

7.

Evaluation of Proposals

8.

Protest Process

9.

Contract Negotiation and Inability to Negotiate a Contract

Attachment: Sample County Contract Template, Supporting
Materials &
Contractor Declara
ti
on



APPENDICES


Appendix A1 through Appendix F are required to be submitted with the
proposal.


APPENDIX A1

TECHNICAL REQUIREMENTS RESPONSE FORM FOR
CLIENT SERVER SOLUTION


APPENDIX A2

TECHNICAL REQUIREMENTS RESPONSE FOR
M FOR A
SaaS SOLUTION

APPENDIX B

FUNCTIONALITY AND INTEGRATION RESPONSE FORM

APPENDIX C1

IMPLEMENTATION, PROJECT MANAGEMENT, TRAINING,
AND ON
-
GOING SUPPORT FOR A
CLIENT SERVER
SOLUTION

APPENDIX C2

IMPLEMENTATION, PROJECT MANAGEMENT, TRAINING,
AND ON
-
GOING

SUPPORT FOR A
SaaS

SOLUTION

APPENDIX D


PROPOSAL COST RESPONSE FORM

(Excel Spreadsheet)

APPENDIX E


SaaS/ASP SECURITY ASSESSMENT CHECKLIST

APPENDIX F


FUNCTIONAL REQUIREMENTS

(Excel Spreadsheet)


Exhibit 1

CURRENT INTERFACE LIST









Page
5

of
82






1. Purpose of the Request for Proposal


INTRODUCTION


San Mateo Medical Center (SMMC) is requesting proposals from qualified suppliers to
provide, install, implement, support and maintain a software solution for a Core Health
Clinical Information System

f
or inpatient care to achieve Meaningful Use of Certified
Electronic Health Record (EHR) Technology and manage and support the delivery of
efficient, cost
-
effective, and high quality healthcare within the organization.


We are also
query
ing
vendors who re
spond to this RFP regarding their ability

to

integrate the various existing systems outlined in this RFP


into an integrated EHR
package that will provide continuity of care for our patients across the entire enterprise.


This document provides background

on the SMMC organization, vendor selection
process, SMMC’s functional and technical requirements, and other pertinent
information.


Additional requirements of the software include:




Must be HIPAA compliant.



Must have secure web based access.



Must generat
e reports required for state and payor requirements.





Must generate letters to the referring provider/agency as well as other
notification tools to complete the transfer process.




Must facilitate compliance by SMMC of all applicable laws and regulations.



At the time of implementation, m
ust be certified under the Office of the
National Coordinator for Health IT rules for Meaningful Use.


SMMC will consider an on
-
site client server solution or a Software as a Service (SaaS)
solution.


However, the proposed

solution must be a proven base system.


SMMC is not
interested in beta systems or purchasing professional services to design and develop a
system.


The integrated solution must meet the technical, support, service, and
business requirements as defined in
this RFP.




This project will be under the direction of the SMMC Executive Leadership Group and
SMMC Information Technology Governance Committee and it will be coordinated
through the Core Clinical Health RFP Evaluation Committee.


1.2 Service Providers


The County welcomes proposals from all qualified service providers. The County may,
at its sole discretion, enter into contract with one or more qualified service providers.


1.3 Contact with County Employees


Page
6

of
82


As of the issuance date of this RFP and con
tinuing until the final date for submission of
proposals, all proposers are specifically directed not to hold meetings, conferences or
technical discussions with any County employee for purposes of responding to this
RFP except as otherwise permitted by th
is RFP. Any proposer found to be acting in
any way contrary to this directive may result in the proposer being disqualified from
entering into any contract that may result from this RFP.

Proposers should submit questions or concerns about the process as o
utlined in
Paragraph 2.1. The proposer should not otherwise ask any County employees
questions about the RFP or related issues, either orally or by written communication.



1.4 Background

San Mateo Medical Center




SMMC is a fully accredited 448 bed acut
e and long
-
term care hospital and outlying clinic
system owned and operated by the County of San Mateo. The system has grown over
the years and today provides inpatient and outpatient care to the communities within
San Mateo County in Northern California.



SMMC employs its own physicians and is recognized as providing services which
include acute inpatient care,
l
ong
-
t
erm
c
are facility and services, Psychiatric Emergency
Service,
i
npatient
p
sychiatric services and operation of a comprehensive medical
emer
gency room. Inpatient services include medical/surgical care as well as specialized
services such as psychiatry and therapies such as recreational services for Long Term
Care patients. Although we see OB patient
s

in our clinics, SMMC does not have a
Labo
r and Delivery service. In addition, although we do serve pediatric patients, we do
not have a dedicated pediatric unit; the great majority of our inpatients are adult.


Inpatient units at the Main campus include two Medical/Surgical units totaling 62 bed
s, a
7
-
bed ICU and a 34 bed inpatient psychiatric unit. The other

345

beds are for long
-
term
care patients
, 64 beds in 2 units on the main campus and 281 beds at the Burlingame
facility; at this time one of the long
-
term care units at the main campus is c
losed
.
Proposals should include information about data for all types of beds including the long
-
term care beds, especially around documentation systems and integration of that data
within a comprehensive
patient
record.


Outpatient services include both
primary care and specialty clinics located at SMMC and
at satellite facilities throughout the county.


Further information about SMMC can be obtained at their website
:

www.sanmateomedicalcenter.org



SMMC Info
rmation Services Department



San Mateo Medical Center IT Vision


The SMMC Information Technology vision is a paperless/paper
-
lite, automated,
integrated delivery system that traverses

the continuum of care. The goal is to leverage
systems and technology

to improve patient care, physician and employee satisfaction
Page
7

of
82


and patient safety and to support effective revenue management to create a distinct
competitive advantage.


Specifically SMMC seeks to deploy Information Technology tools to:




Advance patient s
afety and quality of care



Improve coordination of care across the continuum



Enhance patient, family and staff satisfaction



Improve the delivery of timely, efficient and cost
-
effective care



Optimize “Revenue Cycle” processes



Enhance evidence
-
based clinica
l and administrative decision making



Ensure compliance with all regulatory and accreditation standards



Two key drivers will play a major role in the sequencing and timing of the deployment of
Information Technology tools/solutions to achieve these goals:




Both the clinic system and the SMMC Emergency Department (ED) are currently
using EHR technology; eClinicalWorks is being used by all primary and specialty
care clinics and Pulsecheck from Picis is the ED system.
Data from all systems
must be available
to all providers across the Health system.




The ability to meet the ARRA (Americans Recovery and Reinvestment Act)
Meaningful Use criteria in order to maximize the incentive award is critical to the
funding of this initiative and must be considered in the
planned scope and
approach of the implementation.




SMMC Information Services


Information systems and technology for SMMC is centralized in the County’s Information
Services Department (ISD), which is responsible for all systems, planning, development
and support. Business units comprising IS
D

are:




Application Services


provides a comprehensive array of services

o

Strategy

o

Solutions

o

Sourcing

o

Support




Technical Services

o

Data Center Operations

o

Operations

o

Customer Service

o

Field Support










Page
8

of
82


Technical

Environment



Technical Standards


Intel Platform


SERVER

Operating system

Windows Server 2003
-
2008/Windows Active Directory

Hardware

Intel Dual Core 3.0 GHZ


2MB cache, fiber/GBE NIC
(redundant), Integration to an EMC Clarion SAN is via fiber
connec
tivity.

Backup

CommVault and/or Tivoli Storage Manager

Server redundancy/cluster

Depends on application

Disk array

Typically RAID 5


DESKTOP/LAPTOP HARDWARE

Mid
-
level PC with 17” monitor

Dell Optiplex Ultra small form factor PC

Monitor settings

1024

x 768/ high color

Laptop

Dell models


DESKTOP/LAPTOP SOFTWARE

Operating System

Windows XP with Service Pack 2/3

Office applications

Microsoft Office 2003 Professional, SP2

Email

Novell Groupwise

Terminal emulation

Attachmate


PDF reader

Adobe Acroba
t Reader 7.0

Desktop database

Microsoft Access 2003

Internet browser

Microsoft Internet Explorer 6.0/7.0

Antivirus

McAfee

Java

Java Version 1.4.x

Encryption



Laptop

Only

Guardian Edge


PRINTERS

Laser

HP LaserJet


Group
-

Mid
-
range printer is 4250T
N

HP LaserJet


MFP is HP 4345TN

HP LaserJet


standalone is HP2105D

Impact

Not
supported

Label

Zebra with network connectivity

Network interface

HP
-

Internal

Jet Direct



Technical Standards


Proprietary Platform (Midrange)


SERVER

Operating system

A
IX , OS400, Sun Solaris

Hardware

64bit processor, connectivity to SAN a must, dual NIC,
redundant power supply. Manufacturer configuration approval
required.

Backup

Internal for OS, integration into enterprise backup required.
Page
9

of
82


SMMC ISD uses CommVault and

Tivoli Storage Manager.

Server redundancy

Depends on application

Disk array

Depends on application

Virtualization

Supported based on application


COMMUNICATION

Protocol

TCP/IP

Topology

Ethernet

Routers/ switches

Cisco

Bandwidth


network

Gigabit (s
x/lx)

Bandwidth


to the desktop

10/100 MB/ second

Backbone

Fiber optic

Cable to the desktop

Category 5e UTP with RJ45 connections



REMOTE AUTHENTICATION/SUPPORT

Cisco VPN/SSL


UPS

Must specify requirements from manufacturer. Computer room has UPS.


There are two data centers available, one at the Medical Center and the other at the County
Center in Redwood City. Both support virtualization and are connected through a robust WAN.
County clinics are networked via
the
AT&T Opteman solution.


There i
s a wireless network in place

supported by Cisco hardware
; standard is
802.1x.



2. Timeline

The following timeline will be followed for this RFP


1) Release of RFP





Mon


12
-
20
-
10


2
) Deadline for written questions



Wed



1
-
12
-
11 2PM PST

3
) A
nswers to written questions


Thurs


1
-
20
-
11

4
) Proposal Due Date




Fri




2
-
4
-
11 2PM PST

5
) Start Review of Proposals



Mon




2
-
7
-
11

6
) Recommendation to ISD Director


Fri




3
-
4
-
11

7
) Last Date to Submit Protest



Fri



3
-
18
-
11 2PM
PST

8
) Determination of Protest



Mon




3
-
28
-
11


9
)
Board

Approval





To Be Determined

1
0
) Contract Start Date



To Be Determined

Page
10

of
82


2.1 Submittal of Questions

Proposers are encouraged to submit written questions about this RFP. Questions are

to be received at the County by
2PM
, PST on
Wed
,
Jan 12
, 2011. Questions shall
reference this RFP by number and be in writing and faxed or emailed to:

Cyndy Chin, Administrative Assistant

Email: CChin@co.sanmateo.ca.us

FAX: 650
-
627
-
9160

Answers to que
stions will be distributed by fax or email no later
than
Thurs, Jan. 20
,

2011, to all who receive a copy of this RFP.




3. General Conditions of Submission

The submitted proposal shall be used to determine the proposer’s capability of
rendering the servi
ces to be provided. The failure of a proposer to fully comply with the
instructions in this RFP may eliminate its proposal from further evaluation. The County
reserves the sole right to evaluate the contents of proposals submitted in response to
this RFP
and to select one or more successful contractor(s) or none at all. The County
reserves the right to waive any requirements of this RFP when it determines that
waiving a requirement is in the best interest of the County. The proposal is to include
contact
information, including principle contacts and officers, main and local business
addresses, tax identification number, voice and fax phone numbers, and email address.
The selected
proposal

s content will be included as an exhibit in the final contract.

4.
Proposal Contents


4.1 Service Requirements


Project Application Scope and Description


The primary objective of this project is to identify an integrated clinical information system
solution from a single vendor of choice to support the delivery of inpat
ient care at SMMC.



Consideration will also be given to the comprehensive scope of applications within a
vendor’s offerings to allow SMMC to move towards a fully integrated Hospital
Information/Clinical Information (HIS/CIS) environment in the future.

Integration of the
various EHR “pieces” is critical to having a user
-
friendly solution; this is a key piece of the
proposal.



SMMC is requesting proposals for an integrated solution that supports the following specific
applications/functional areas:


Hos
pital
-
based Core Clinical Applications/Functionality

Page
11

of
82




























SMMC

s patient mix i
s broad and will require functionality that supports multiple care
delivery settings including inpatient acute and critical care for adults and children, inpatient
and outpatient surgery, long
-
term care, inpatient psychiatric care as well as support for
re
spiratory therapy, rehabilitation and pharmacy services.


SMMC is committed to selecting an information system that supports the development of
evidence based care and promotes and tracks quality outcomes. To that end
,

this RFP
contains requirements that s
upport the building of an infrastructure to support improvement
in core measures and other quality indicators, such as The Joint Commission Patient Safety
goals and IHI quality indicators.



Lastly, the goal of achieving a paperless/paper
-
lite patient char
t environment must be
supported through a complementary document management/imaging solution. It is also
SMMC

s intention to utilize the Document Management solution on an enterprise
-
wide basis
beyond the integration with patient
-
centric clinical systems.

Initially this will include the
Patient Registration and Patient Business Services (PBS) departments and expand beyond
that as opportunities arise.



Various clinical systems will remain unchanged within the SMMC organization and
integration with these mu
st be addressed to ensure a comprehensive view of a patient

s
care delivery. The clinical systems that will remain in place and require integration with your
proposed solution include (at a minimum):



Picis Emergency Department Information System (Pulsechec
k)



Siemens Novius Laboratory Information System



Siemens Radiology Information System



eClinicalWorks Ambulatory EMR



Pr潶i摥r Or摥r Entry (CPOE)

f潲 慬l 獥牶i捥c



Cli湩捡c D散esi潮 S異灯rt (CDS)



N畲獩u朠慮搠䅮捩ll慲a Cli湩捡c D潣om敮tati潮 (as獥獳浥st, 捡牥 灬慮猩



Multi摩獣s灬i湡ry Clini捡c D潣om敮tati潮 (捡牥 灲pvi摥
r猠i湣n畤i湧 MD猩



I湴敮獩v攠䍡r攠卥rvi捥猠cICU)



P敲e
-
O灥r慴楶攠獥evi捥猠D潣om敮tati潮



P桡rm慣a / M敤i捡瑩c渠n慮慧敭敮e



Inf畳u潮 C敮t敲 M慮慧em敮t (C桥m潴桥r慰y 潮ly, 湯 R慤i慴楯渠
T桥r慰y)



T敬敭etry 慮d P慴楥湴 M潮it潲oI湴n杲慴i潮

Additional Support Applic
ations/Functionality



E湴敲灲楳p D潣om敮t M慮慧em敮t Sy獴敭 (EDMS)



R数潲oing T潯ls


Possible Future Applications



R敦err慬 M慮慧em敮t Sy獴敭



Affili慴敤aP桹獩捩慮 P潲oal



P慴楥湴nP潲t慬



P敲獯湡e H敡lt栠剥捯rd


Page
12

of
82




There are several in
-
place systems that may be evaluated for replacement as part of this
proposal:



ResQ: Resource and OR scheduling



Quadra
med: Acuity



Dietary on
-
line: Food and nutrition orders are not done through Invision but through
an on
-
line program developed in
-
hous
e



Restraints: Restraint protocols are managed through an in
-
house developed
program



Siemens Pharmacy Information System
(inpatient)

SMMC would prefer to keep this
system in place; however, because CPOE and Medication Administration and
Reconciliation are very dependent upon the inpatient Pharmacy, there might be a
need to replace it.


Other systems
which will be
key to a
full patient record include Softmed in the H
ealth
I
nformation
M
anagement (HIM)

department and Achieve, used in the Long

Term care units.


The implementation will also require integration of your proposed clinical solution with the
following revenue cycle i
ncumbent solutions at SMMC (a current list of interfaced systems
and applications can be found in Exhibit 1):



eClinicalWorks

enterprise patient scheduling



Invision


Patient Management and Patient Accounting



SoftMed


HIM


In addition, the integration of o
ther EHR systems throughout the San Mateo County Health
system must be considered. The need of all providers across the Health System to share
data in order to improve patient care is great. At this time, the primary system is an Avatar
(Netsmart) EHR s
ystem currently in place in the Behavioral Health division and soon to be
implemented within Family Health.


Based on
an
accepted proposal, there may also be requirements for data conversions or
additional interfaces to/ from various existing systems. T
his will be discussed further after
proposal review.



SMMC

ASSUMPTIONS

The system will include the following components:




Production, Test and Training Environments



User Training



Integration with existing clinical systems



Planning and Volume Statistic
s

The data below represents the key clinical and business statistics for SMMC. This
information is intended to be used as a reference to assist in the completion of your
response including pricing, sizing of processor(s), main memory, disk storage, and
nec
essary subsystems/third
-
party software.

Page
13

of
82




San Mateo Medical Center Operational Data

Item

FY09
-
10

Period Ending
6/30/
10

Projected

(within 3 years)

Total Number of Beds

448

448

Number of Beds by Specialty




Medical/Surgical

62

62


ICU/CCU

7

7



Psychiatric

34

34


Long Term Care (LTC)

345

345




Number of Operating Rooms

3

4

Annual
Discharges
-
Acute Care

2795

3075

Annual Inpatient Days
-
Acute Care

12
396

13635

Average LOS
-
Acute Care

4.4

4.5

Annual
Discharges
-
Psych

826

908

A
nnual Inpatient Days
-
Psych

9746

10720

Average LOS
-
Psych

11.8

11.8

Annual
Discharges
-
LTC

479

546

Annual Inpatient Days
-
LTC

102957

113252

Average LOS
-
LTC

215

215

Annual ED Visits

35515

39066

Annual Psych Emergency Visits

3494

3843

Annual Hospital Outp
atient Visits (excluding
ED & Same Days)

238572


262429

Number of satellite clinic sites

9

9

Number of Physicians On
-
staff

150

150

Planned Concurrent Users

600

600






4.2 History/Organizational Background


The proposal should describe the following
: the proposer’s company’s history, mission,
programs, and services; administrative structure; and experience, including length of
time in providing similar services. Please include any past experience with local
government agencies. Also, describe how thi
s program will fit into your overall
organization. Attach an organizational chart of your San Francisco/Bay Area region
operation.


Page
14

of
82


Please use the format below for this information.



PROPOSER’S CORPORATE INFORMATION


1.


EXECUTIVE SUMMARY



Include an execu
tive summary which should be a one or two page summary
intended to provide the Evaluation Committee with an overview of the significant
business features of the proposal.


2.

PROPOSER EXPERIENCE/INFORMATION


The Proposer shall include in their proposal a stat
ement of relevant experience.
The Proposer should thoroughly describe, in the form of a narrative, its
experience and success as well as the experience and success of
subcontractors, if applicable in providing and/or supporting the proposed system.



In ad
dition, Proposers are required to provide the following information:


a.

Vendor Primary Contact:

1)

Name:






2)

Title:






3)

Office/Location Address:






4)

Phone Number:






5)

Fax Number:






6)

Email Address:






7)

Organization’s Internet Home Page:






b.

Please list names, title, background and tenure of the executive
leadership of your organization and/or of your Healthcare Information
System division if part of a
larger/broader organization.






c.

Identify the locations (city, state) of the following:

1)

Corporate Headquarters:






2)

Programming/Technical Support Personnel:






3)

Field Engineering:






4)

Client E
ducation Personnel:






5)

Consulting Services Personnel:






d.

Under the laws of which state the vendor is incorporated:






e.

What is the number of employees in your organization, categorized by:

1)

Total:






2)

Management/Administration:






3)

Marketing /Sales:






4)

Research and Development:






5)

Installation:






Page
15

of
82


6)

Ongoing Application Support:






7)

Customer Service/Telephone Suppo
rt:






8)

Other:






f.

Provide input on the number and type of clinical resources you have on
staff.

g.

How long has your company been in the business of Clinical Information
systems?






h.

What percentage of your co
mpany business involves Clinical Information
systems?






Please provide the following financial information for each of the last three
fiscal years (specific to your software division if part of large company):



FY 2010

FY 2009

FY 2008

A
nnual Revenue



















Net Profit



















Total Assets



















Total Debt



















% Net Revenue spent on
Research and Development




















i.

Are there any established user groups associated with your organization
or proposed product?






Please describe your organization’s
sponsorship of these groups and how your organization works with them:








j.

Provide a complete disclosure if Proposer, its subsidiaries, parent, other
corporate affiliates, or subcontractors have de
faulted in its performance
on a contract during the past five years which has led the other party to
terminate the contract. If so, identify the parties involved and the
circumstances of the default or termination.


k.

A list of any lawsuits filed against the

Proposer, its subsidiaries, parent,
other corporate affiliates, or subcontractors in the past five years and the
outcome of those law
suits. Identify the parties involved and
circumstances. Also, describe any civil or criminal litigation or
investigation p
ending.


3.

FINANCIAL STABILITY/PROPOSER FINANCIAL INFORMATION


Proposer shall submit copies of the most recent years independently audited
financial statements, as well as those for the preceding three years, if they exist.
The submission shall include th
e audit opinion, balance sheet, income statement,
retained earnings, cash flows, and notes to the financial statements. If
independently audited financial statements do not exist for the Proposer, the
Proposer shall state the reason and, instead, submit su
fficient information such
as the latest Dun and Bradstreet report to enable the Evaluation Committee to
Page
16

of
82


determine the financial stability of the Proposer. The Proposer shall supply any
additional financial information requested by SMMC ISD in a timely mann
er.


4.3 References


Please provide the following information for three references. It is important that you include
references that are similar to SMMC in terms of size, clinical services,

scope of applications and
technology environment. If possible, pr
ovide at least one reference site from the state of
California
, preferably from the San Francisco Bay Area.
SMMC will not contact any references
without your permission. Please use the format below to provide this information.


Reference #1
:

a)

Organization

Name:






b)

Organization Address:






c)

Size and Type of Facility:






d)

Name and Release Version of Application(s) Installed:






e)

Application(s) Live
-
dates:






f)

Nature of Relationship between Vendor a
nd Reference Site (i.e., partner, beta site):






g)

Individual with sufficient knowledge and experience to speak on the implementation
process, product functionality, vendor support, and documentation and training.



Name:








T
itle:








Phone number:








Contact email address:






Reference #2:

a)

Organization Name:






b)

Organization Address:






c)

Size and Type of Facility:






d)

Name and
Release Version of Application(s) Installed:






e)

Application(s) Live
-
dates:






f)

Nature of Relationship between Vendor and Reference Site (i.e., partner, beta site):






g)

Individual with sufficient knowledge an
d experience to speak on the implementation
process, product functionality, vendor support, and documentation and training.



Name:








Title:








Phone number:








Contact email address:






R
eference #3:

a)

Organization Name:






b)

Organization Address:






c)

Size and Type of Facility:






d)

Name and Release Version of Application(s) Installed:






Page
17

of
82


e)

Application(s) Live
-
dates:






f)

Nature of Relationship between Vendor and Reference Site (i.e., partner, beta site):






g)

Individual with sufficient knowledge and experience to speak on the implementation
process, product functionality, vendor support, and documenta
tion and training.



Name:








Title:








Phone number:








Contact email address:










5. Service Capabilities

5.1 The proposal should
define the scope of work and specific services being
offered in your proposal and should
include
the information listed in the sections
below
:




5.1.1
TECHNICAL REQUIREMENTS


SMMC is seeking a contractor to provide a complete solution to satisfy the technical,
functionality, and integration requirements an
d one who is capable of providing the
stated capacity and service levels as well as the training and technical support required
to maintain the system in an operational status.


The technical requirements are to be defined referencing the technical requi
rements in
Appendices A1 and A2. Proposers submitting a proposal for a client server solution
must submit Appendix A1; whereas Proposers submitting a proposal for a SaaS solution
must submit Appendix A2. Proposers submitting a proposal for both types of
solutions
must submit Appendix A1 and Appendix A2.


Proposers must submit a thorough narrative supported by references to the technical
documentation in response to questions asked in Appendix A1 or Appendix A2.




5.1.2
VENDOR PROPOSED PRODUCT INFORMA
TION


Please complete the table below regarding the proposed applications:


Applications

Supported

Functionality

(Ref Section II
-
D)

Application
Suite Name

Module
Name

Developed In
-
House,
Integrated, or
Interfaced?

Current Status

(i.e., in development, be
ta,
or generally available
w/version # )

# Live
Clients


Hospital
-
based Core Clinical Applications



Provider Order
Entry
/all order
services






Page
18

of
82


Applications



Clinical Decision
Support








Nursing and
Ancillary Clinical
Documentation
(assessment,
care plans)








Multidisciplinary
Clinical
Documentation
including
providers








Intensive Care
Services (ICU)








Perioperative
Services,
including
documentation








Infusion Center
Management








Telemetry and
Patient Monitor
Integration






Additional Suppor
t Applications



Enterprise
Document
Management
System (EDMS)








Reporting Tools






Possible Future Applications



Referral
Management
System








Affiliated
Physician Portal








Patient Portal








Personal Health
Record















Page
19

of
82





5.1.3
SY
STEM SUPPORT REQUIREMENTS


Function

Vendor Use Only


Yes

No

Comments

1)

A dedicated support team is guaranteed.









2)

Toll free telephone support is available 7 days a
week, 24 hours a day.









3)

Web
-
access support is available 7 days a week, 24
hours a day.









4)

Telephone support response times are guaranteed.
Specify the response time.









5)

For the proposed hardware, please identify the party
responsible for support.







6)

For the proposed software, please identify the party
responsible for support.







7)

Is a preferred or “p
remier” customer support status
offered?









8)

Is a warranty for the application(s) available? What is
the warranty period?










System Support
-

Addi
tional Requirements

1.

Where are your customer support offices located?






2.

What are your standard support hours? Are they based on client local time? Do you offer
extended support hours? Is there an additional charge for this and if so, what
is that
charge?






3.

Define the recommended size and skill set of the
IT staff

to support your proposed core
clinical product(s) at an organization of SMMC’s size and complexity.






4.

Assuming SMMC contracts with another party

for hardware, networking, etc., how are
lines of responsibility drawn?






5.

Describe the process for resolving client issues and problems:

a)

Discuss issue logging and tracking.






b)

Explain service request prioritization.






c)

Describe escalation procedures.






d)

Discuss status reporting.






e)

Provide average turnaround times for problem resolutions.






f)

What documentation/acknowledgement is communicated to SMMC when
a
problem/issue is communicated to the vendor?






6.

Describe your methodology for new version/releases of your software:

a)

Development.






b)

Testing.






c)

Distribution.






d)

Installation.







Page
20

of
82


e)

Notification.






7.

How often are new versions released?






8.

What is the recommended / standard timeframe for taking new releases?






9.

When a new version of your product is released, will you guaran
tee upward conversion
to the new release at no additional cost to SMMC?






10.

Can new software be applied and tested in the training system before it is applied to the
production system?






11.

Is the training database/environmen
t a mirror image of the production files and the
systems test database?






12.

Can the test/training environment be ‘refreshed’ or synchronized from the production
environment by SMMC independent of vendor participation? Please explain.

13.

How ar
e customizations


vendor and customer
-
created


accommodated in new
releases, i.e., not overwritten?






14.

How many levels of software releases are supported?






15.

Does the vendor organization support a remote hosted model for

their software? Please
describe offering.







5.1.4
IMPLEMENTATION APPROACH


1.

Please describe your typical approach to implementing the proposed core clinical
solutions at an organization of SMMC’s size and complexity.







2.

Please describe a high
-
level recommended installation sequence and timetable for the
proposed core clinical applications with the intended goal of maximizing ARRA HITECH
incentive monies through reaching Meaningful Use in a timely manner. Please include
a
description of suggested implementation phases and timing (e.g., Phase 1:
Orders/Results, Phase 2: Clinical Documentation, etc.)

3.

Provide a sample implementation work plan for the proposed applications indicating the
tasks required, the relative sequence
of tasks, the party responsible for each task, and
the approximate time required to complete each task.

4.

Describe the anticipated
vendor and SMMC personnel and/or outside resources

required/ recommended to install your proposed solutions outlined in #2 abov
e (skill level
and numbers).






5.

Discuss activities/assistance that could be provided by vendor personnel in addition to
those provided for in your work plan and implementation cost estimate and describe how
these additional services would be billed.





.

6.

Describe
your formal procedure for system acceptance, including hardware and
software.






7.

Describe your methodology for conversion of current system files, specifically:

a)

Patient demographics.






b)

Clinical documentation (discrete dat
a and transcribed reports). Please provide
input on two methods for this data:

1.

Converting discrete data/transcribed reports to your CIS.






2.

In
-
loading of a subset of paper charts via your document management
solution.






8.

For any identified automated conversions, who would be responsible for developing:

a)

Extracts from the current system?







b)

Input/edit/updates to your system?






Page
21

of
82


9.

What is your recommendation for converting existing clinical da
ta from the incumbent
Siemens Invision
system

--

to your proposed CIS as discrete data, to your proposed
document management solution, other? How have other clients addressed historical
clinical data conversions?







5.1.5
CLINICAL CONTENT


1.

Please describe your typical approach and/or options to building the clinical content
needed for order entry/CPOE to achieve standardization and patient safety (e.g., order
sets, clinical decision support, standardized documentation, etc.).







2.

Describe the types and number of order sets and alerts/reminders you provide with the
order entry module, i.e., ‘starter set’? If you provide these, please provide details.






3.

Describe your system ability for dealing with standardi
zed order sets by specific
physicians vs. diagnosis?






4.

Describe in detail the clinical content that is provided with your clinical system. Provide
numbers and types of content including order sets (if not described in #2 above), clinical
rules and alerts, care plans, etc.






5.

Describe how the clinical content is maintained in your application.






6.

Does your system support the import of 3
rd

party clinical content? If so, please describe
the process and how is

existing content impacted.






7.

List the 3
rd

party vendors that you are aligned with for providing clinical content.
Describe any additional costs for this 3
rd

party software.






8.

Describe how your system allows the ability

to aggregate data directly from the CDR for
regulatory initiatives


e.g., THE JOINT COMMISSION core measures, CMS core
measures, IHI sepsis bundle compliance, SMMC specific databases, etc.






9.

Describe your system’s ability to integrate v
arious care protocols into general
assessment, scoring, implementation and on
-
going reassessment into the EMR


i.e.,
falls, pressure ulcers, groin management, restraints, rehab protocols, moderate sedation
protocols, central line placement protocols, etc.







10.

Describe how the system assists with adherence to national patient safety goals from
THE JOINT COMMISSION or National Quality Forum guidelines


program screening,
implementation, compliance monitoring, etc.

a.

High risk medication alerts






b.

Look alike, sound alike drugs






c.

Drug concentrations






d.

IV Conscious sedation






e.

Monitoring of hospital acquired infections






f.

Patient identification






g.

Clinical al
arms






h.

Critical values






i.

Medication reconciliation






11.

Describe the system’s ability to pick up symptom or pattern recognition of symptoms of
patient’s in trouble and triggers the end
-
user?










Page
22

of
82



5.1.6
FUNCTIONALITY AND INTEGRATION REQUIREMENTS

(APPENDIX B)



Proposers must complete and submit with their proposals the functional and integration
requirements referenced in Appendix B.




5.1.7
TRAINING


Function

Vendor Use Only


Yes

No

Co
mments

1)

Documentation is available in hard copy.









2)

Documentation is available on
-
line.









3)

On
-
line documentation can be printed on demand.









4)

Documentation is available on CD or DVD









5)

Documentation manuals accurately reflect the most
current software release.









6)

Vendor
-
supplied training can be conducted on
-
site at
SMMC.









Training
-

Additional requirements

a)

Provide a summary description of the documentation provided with the system inclu
ding:

a)

System administration manuals (including use of decision and edit tables).






b)

Technical documentation (including detailed HL7 interface specs and data
schema).






c)

User reference manuals.






d)

Training m
anuals.






b)

Describe the training approach for user personnel. Outline training classes/sessions
offered, course content, approximate length of time for each session and approximate
ratio of hands
-
on practice vs. lecture.

c)

Describe any compu
ter
-
based instruction modules available for training during installation
and for on
-
going training.






d)

Describe the training provided to operations and technical support personnel.






e)

Describe the training for the report w
riter or reporting mechanism? Describe how this is
accomplished and what is the cost?






f)

Describe the training available to information systems and user department core group
personnel for product orientation in advance of system file, tab
le, profile and parameter
building.






g)

Describe any ongoing training available to customers included in the
maintenance/support arrangement at no additional cost (not including out
-
of
-
pocket
expenses).






h)

Discuss options a
vailable for training new personnel after initial implementation.






Provide a listing of all standard reports that are provided by the system (for each module) and a
sampling of each with your response.




Page
23

of
82


Additional Note:

The implementa
tion, project management, training, and ongoing support requirements
are to be defined referencing the requirements in Appendices C1 and C2. Proposers
submitting a proposal for a client server solution must submit Appendix C1; whereas
Proposers submitting

a proposal for a SaaS solution must submit Appendix C2.
Proposers submitting a proposal for both types of solutions must submit Appendix C1
and Appendix C2.


Proposers must submit a thorough narrative supported by references to the
implementation, proj
ect management, training, and ongoing support in response to
questions asked in Appendix C1 and/or Appendix C2.



5.1.8
STRATEGIC DIRECTION


This section gathers information related to the strategic direction of the vendor and defines the
contractual requ
irements of SMMC. Please answer each question completely, concisely, and
accurately.


1.

Strategic Requirements


a)

Has your company acquire
d or merged with any other organizations in the past three
years?






If so, please describe.






b)

Are you a subsidiary of or under the control of any other corporation, individual, or other
entity?






If yes, please provide entity name.






c)

Describe your corporate visio
n for how information technology will support the healthcare
environment of the future (i.e., over the complete continuum of care).






d)

Describe how workflow tools are integrated into your products and how they can be
customized by the clie
nt.






e)

Identify your product’s strengths and its areas for improvement.







f)


What are your plans to address these improvement opportunities?






g)


Describe your
organization’s

vision for providing web
-
based

applications, technologies,
or value
-
added services.






h)

Describe how your system supports the development of evidence based care and
promotes and tracks quality outcomes.

i)

How does your system support the building of an infrastructure to s
upport improvement
in core measures and other quality indicators, such at THE JOINT COMMISSION
Patient Safety goals and IHI quality indicators?






j)

What reporting capabilities are available with your system for reporting core measure
perfor
mance?






k)

Can the proposed solution support all relevant California state regulatory requirements?






l)

Describe any work you are doing with designing or developing systems to assist
healthcare organizations meet Leap Frog s
tandards.






m)

Describe the work you’ve completed or will complete to ensure that your applications will
support clients with the expanded HIPAA requirements stemming from the ARRA
HITECH Act (security and privacy focused).






n)

Please provide
examples

of operational efficiencies and process integration benefits
achieved by clients through the use of your system (attach materials, as needed).






o)

Discuss your efforts to provide interfacing to

smart


IV pumps an
d please specify those
manufacturers that you have interfaced with to date.






Page
24

of
82


p)

Describe how your system has incorporated the use of bar
-
coding, RFID and proximity
technology into the care delivery process. Do you partner with other vendors

to support
these features and/or is software internal to your product. Please provide detail
information on this focus area.






q)

Describe how your system can support a community
-
wide HIE (health information
exchange) initiative to consolid
ated patient clinical information across disparate entities,
i.e., RHIO (regional health information organization) and/or CMPI (community master
patient index).






r)

Please describe how your system handles bed management. Is this function pa
rt of your
CIS or
you’re his?

Assuming it is part of your CIS and assuming that SMMC will remain
on their Invision system for Registration/ADT, how will that affect the bed management
processes within your CIS?






s)

What constraints do you
see with the integration of a 3
rd

party laboratory system (Novius
LIS)?






t)

SMMC plans to keep their incumbent EDIS (Pulsecheck) in place initially. What data
points would you recommend for integration between your CIS and SMMC’s Pulsecheck

ED System to ensure a comprehensive clinical record for patients that span the
ED/Inpatient continuum? Have you integrated with Pulsecheck? Have you integrated
with other ED systems? What challenges have you encountered?






u)

Please outli
ne how your proposed solution supports the ARRA HITECH Meaningful Use
requirements. Include a table of the required Meaningful Use functionality (by year) and
how your proposed solution meets these requirements currently or planned. Include
both core and

menu set items in this description.



5.1.9
Contractual Information


Indicate, in the following table, your agreement to the contractual requirements identified.
Some requirements identified below relate to language included in the County

s standard
contr
act template, a copy of which is attached to this RFP. If you cannot agree to a
requirement, explicitly state such in your response and provide alternative contract language
for consideration.


Requirement

Vendor Response


Yes

No

Comments

a)

Should SMMC

co
ntract with your organization, there
are no pending litigation activities involving your
organization that could have an impact on
SMMC
.









b)

Your organization will contract guaranteed prices for
software systems that are currently under
development and not yet installed.









c)

Your organization will contract for “not to exceed”
installa
tion fees.









d)

Your organization will stipulate that the contract will be
entered into under, and governed by, the laws of
California. (See Section 15 of the County’s standard
agreement.)









e)

Your organization will stipulate that any dispute
arising under the contract will be venued in the
County of San Mateo or the United States District
Court for the Northern District of California. (See
Section 15
of the County’s standard agreement.)









Page
25

of
82


Requirement

Vendor Response


Yes

No

Comments

f)

Your organization will agree to unconditionally
guarantee all items against defects in materials,
workmanship, and performance for one year from
date of installat
ion by
SMMC
unless otherwise
specified.









g)

Proposed acquisition and ongoing maintenance or
support costs include any future enhancements or
upgrades to the application modules. If not, indicate
addition
al costs in the cost quotation.









h)

Your organization can and will comply with the
County’s non
-
discrimination policy. (See Section 11
of the County’s standard agreement.)









i)

Your organization can and will comply with the
County’s equal employment opportunity policy. (See
Section 11 of the County’s standard agreement.)









j)

Your organization can and

will comply with the
County’s policy regarding employee benefits. (See
Section 11 of the County’s standard agreement.)









k)

Your organization can and will comply with the
County’s jury duty policy. (Se
e Section 17 of the
County’s standard agreement.)









l)

Your organization can and will comply with the
County’s hold harmless language. (See Section 7 of
the County’s standard agreement.)









m)

Your organization can and will comply with the
County’s insurance requirements. (See Section 8 of
the County’s standard agreement.)









n)

Your organization is able

and commits to comply with
all other terms of the County’s standard contract. (If
not, provide an explanation for the inability to comply
with the required term(s). If no objections are stated,
County will assume the proposer is prepared to sign
the Coun
ty contract as
-
is.)






Contractual Information
-

Additional Requirements

i.


How many contracts for proposed systems have you signed in the last three years?
Please specify for each component.







ii.


How many of those clients have completed implementation of your system? (List the
applications installed for each client.)






iii.


Have any of your customers cancelled a contract in the last two years before, during, or
after an i
nstallation?






If yes, why? (Specify organization and location.)






iv.


Describe how you will commit to providing changes mandated by Federal (e.g., HIPAA,
FDA), State, Accrediting (e.g., THE JOINT COMMISSION), and standar
ds (e.g., HL7)
organizations. Are there any additional costs for these updates?






v.


Describe your approach and timing to accommodate the mandated change to HIPAA
v5010 format and ICD
-
10 diagnosis code set.






vi.


Have you

obtained ONC certification in support of ARRA HITECH requirements
(available beginning October 2009)?







vii. Please list the clients that have purchased your CORE HIS within the last two years.






Page
26

of
82








5.1.10
Appli
cation Design


Function

Vendor Response


Yes

No

Comments

a)

If the application is Windows
-
based, can your system
run under VMWare Workstation (virtualized
environment)?









b)

Is the application object orien
ted design with flexibility
to add custom fields and modification easily? Explain.









c)

Does the application provide a tool to migrate
customization to new software releases? If so,
describe.









d)

Does the application have web access capability for
view
-
only?









e)

Does the application have web access capability for
ordering, results processing, and clini
cian charting?









f)

Is the e
-
mail interface capable of notification and
routing of reports?









g)

Can the systems support the use of email distribution
l
ists?









h)

Is the e
-
mail interface part of a secure messaging
system?









i)

How is PHI encoded in email?










Application Design
-

Addi
tional Requirements

i)

What language is the application written in?







ii)

Describe the processing model used in the application, such as 2, 3, or multi
-
tier.






iii)

Describe the distribution and centralization capabilities for da
ta, application, and interface
processing across physical platforms.






iv)

Describe how capacity planning is accomplished. Include any calculations and
documents in your response.






v)

Provide a schematic showing the logical de
sign of the proposed applications that
identifies all databases and files and indicates the direction of data flow.






vi)

How are databases mirrored for failure tolerance?






vii)

Does the system support voice recognition as an in
put mechanism?






If so, please
explain how and if there are any third party products or components required.







viii)

Please provide a list of all reports, including security reports, and report libraries
that come standard wi
th the system.







5.1.11


S
ecurity


Page
27

of
82


Function

Vendor Response


Yes

No

Comments

a)

Does the application security utilize RDBMS security
roles?









b)

Can the application security utilize enterprise
directory
services for user authentication?









c)

Can SMMC enforce password standards, such as
length, expiration, and character sets in your
application?









d)

For your application, is the authentication process
encrypted?









e)

Are users able to change passwords through the
application at their own discretion?









f)

Does your product provide security controls to restrict
access by:


i

Application module









ii

On
-
line function









iii

Screen within function









iv

Data element/section of chart









v

User ID









g)

Can groups of user security be changed at one tim
e?









h)

Can security be copied from one user or group to
another then modified?









i)

Can user
-
defined security criteria be set?









j)

Is there an audit trail for security changes?









k)

Is one sign
-
on process sufficient to control access to
all authorized functions/modules?









l)

Are separate passwords required for specific screens
or modules?









m)

Can one user be signed on to multiple devices
simultaneously (i.e., using the same password)?









n)

Does the system provide use statistics by user ID?









o)

Does the system provide an audit trail that can be
used to identify transactions or data accesses that
ha
ve been performed by:




i

Input Device









ii

Function









iii

Patient/Record









iv

User Role









v

User Identity









p)

Are all transactions identified with a user ID?









q)

Does the system provide additional
security for Web
access (if available)?









r)

Does the system include options for:




i

Failed access attempts to be tracked and
reported?









ii

Specifying

the number of failed attempts allowed?









iii

Action upon maximum failed attempts?









s)

Can audit logs be archived and recalled as needed?









Page
28

of
82


Function

Vendor Response


Yes

No

Comments

t)

Does the system have a “time out” feature that
automatically signs off a user if a workstation has
been left unattended for a S
M
MC
-
defined time
period?









u)

Can
system “time out” parameters be modified by
S
M
MC

without vendor assistance?









v)

Does the system allow for controlling/removing
access for users no longer needing access?









w)

Can
S
M
MC

define a period after which an unused
sign
-
on is deactivated/disabled from the system?









x)

Can vendor support personnel access the system
without
S
M
MC
knowledge?









y)

Does the system have a function that will
automatically “log off” ALL users?









z)

Does the system support electronic signature?











Security
-

Additional Requirements

i)

Describe how the system provides for the capability to restrict access to particular records
within the system, based on user ID or specified fields (i.e., discharged facility).






ii)

How is single sign
-
on to all applications implemented?






iii)

Describe your approach to utilizing biometric and/or proximity/RFPD device solutions for
user authentication.






Do you have any of these solutions in prod
uction?






If
so, describe the environment and benefits delivered.






iv)

Please describe the ability of software to conform to SSL and describe any other
encryption capabilities of the software.







5.1.12
D
atabase

Function

Vendor Response


Yes

No

Comments

a)

Is the database schema documented and provided to
SMMC
?









b)

Does the database schema identify all databases and
files and indicate direction of data fl
ow?









c)

Is the database schema automatically updated and
re
-
distributed as new releases are made available?









d)

Do the database schema/tables have a s
tandards
convention?









e)

Is there an entity relationship model for the
application?










Database
-

Additional Requirements

i)

Is the DBMS used standard
or proprietary?






If proprietary, describe the structure
and any required support procedures.






ii)

How many database

servers and mirrors

are recommended?






Is there a
production, test/training and developm
ent environment as delivered, etc.?






Page
29

of
82


iii)

Describe a plan and tools used to inspect, report on, and repair the database(s).






iv)

Describe your database mirroring.






How is the “correct” copy known?






v)

Describe database backup plans.






vi)

What different levels of database support does your company provide?






vii)

How do you package your database installs and upgrades for your application?






Is
the up
grade/install configurable to different database environments (i.e., schema name,
database names, table space names…)?







5.1.13
Data Dictionaries and File Design

a)

Does your system have "master files" where universal information can be en
tered
once and accessed by other applications (e.g., patient demographic information)?






Does this apply to all applications proposed?






b)

Are any files updated in a batch mode?







If so, please indicate w
hich files, the
frequency in which these files are updated and the length of time necessary for
batch updates to be performed.






Can the online functions be active while
batch updates are done?






c)

Can all data elements be

viewed, printed, interfaced, updated, reported on and/or
listed as needed? Identify any that cannot.






d)

Does the
system allow the user to restrict printing and display of confidential data
elements if flagged in the data dictionary?







5.1.14
Data Access and Storage

a)

Describe database storage model used by application, such as relational, network,
or hierarchical.






How will this affect the report writing capabilities of the
system?






b)

D
escribe the use of SAN (Block Level) and/or NAS (File Level) protocols associated
with the proposed solution.






What SAN/NAS storage vendors and products
are certified to work with your system?







c)

Describe the recommend
ed storage solution, hierarchy, sizing/capacity, speed, etc.






d)

Does the proposed system include:

i)

User
-
defined menus






ii)

User
-
defined screens/start
-
pages






iii)

User
-
defined fields






iv)

User
-
defi
ned function keys






v)

User
-
customizable patient summary screens (data from demographics, allergies,
documentation, orders, flowsheets, results, etc.)






e)

Are required fields SMMC
-
definable?







f)

How is data i
ntegrity maintained?






What tools are used?







5.1.15


I
nterfaces


Function

Vendor Response


Yes

No

Comments

a)

Do you support the use of interface engines? If yes,
comment on which engine(s) are supported.









Page
30

of
82


Function

Vendor Response


Yes

No

Comments

b)

Are all system interfaces HL7 compliant?









c)

Do you provide detailed interface specifications?









d)

Do you make tec
hnical staff available to answer
questions and assist in data mapping with other
vendors?









e)

Does the vendor support controlled user access to
monitor the interfaces and to stop/start the
interfaces?









f)

Is there an interface error log on the system and can
client personnel access it?









g)

Does the system attempt to re
-
send transactions in
the event o
f a failure?









Interface
-

Additional Requirements

1.

Describe your overall design approach to developing, testing, implementing and
upgrading system interfaces to third party systems.






2.

Provide a list of the interfaces that have been developed/implemented for your CIS.
Include type of interface and vendor/system interfaced to/from.






3.

Provide a list of the medical device (telemetry monitors, EKGs, ventilators, etc.) inte
rfaces
that you have developed/implemented for your CIS.






4.

Please discuss how you have taken steps towards interoperability in support of the
Continuity of Care Document (CCD) and Continuity or Care Record (CCR) core data sets.
Please ind
icate if you have implemented the CCD or CCR XML schema with any clients
and if so, to what other clinical software systems.






5.

SMMC’s specific interface requirements include the following, please describe your ability
to interface to each

and include pricing in the Systems Costs section (Section 8.0). We
have listed the minimum various types of transactions and systems involved below.

a.

ADT (bi
-
directional)

i.

Inbound to CIS and Document Management from Invision

ii.

Outbound from CIS and Document
Mgmt to Invision (to avoid data
discrepancie
s; may not be required if patient demographic data cannot be
edited in the CIS and Document Mgmt system)

b.

Orders/Results (bi
-
directional including order status/results and inquiry) If
proposing these systems

i.

Orde
rs Outbound from CIS to Novius Lab and Siemens RIS

ii.

Orders & Order Status/Results Inbound to CIS from Novius Lab, Siemens
RIS

c.

Charges (uni
-
directional)

i.

Hospital
-
based Charges Outbound from CIS to Invision

ii.

Professional Charges Outbound from CIS to Invision

d.

T
ranscription (uni
-
directional)

i.

Transcription Inbound to CIS and/or EDMS from Webmedx

e.

Pulsecheck EDIS Integration Requirements

i.

Medication Orders Inbound to CIS Pharmacy module from Pulsecheck

Page
31

of
82


ii.

Comprehensive clinical data from Pulsecheck EDIS to CIS (supporti
ng CCD
standards):

a.

Height/weight, allergies/reactions, advanced directive, clinical
history, reason for visit, problem list, ED documentation, medications
(home and administered while in ED) and time of meds
administration in the ED to the CIS eMAR.

iii.

Order
processing for ED orders. Currently done from Pulsecheck to Invision
and then to Lab and Rad. If proposal includes a different solution, please