Professional Documents
Culture Documents
1 PM/EMR General
Requirements
1.1 Data & Information
Management
1.1.1 Highly desirable that data is
maintained in a structured format
ensuring a minimum of text-
based data.
1.1.2 Highly desirable that required
data be highlighted in some
manner.
1.1.3 Highly desirable that existing
clinically relevant data not be
overwritten when updating.
Corrections should be marked as
such.
1.1.12 Wildcard
searches/searches on partial
data (e.g. DoB = July, 2004)
1.1.13 Highly desirable that user be
able to save/re-use searches.
1.1.14 Highly desirable that a patient
identification search be available
including search options of
name, PHN, chart #, phone #
and/or postal code
automatic translation of
diagnostic coding to billing as
required for compliance to MSP
claims submission, encounter
reporting.
1.4 Security
1.4.1 Highly desirable that suppliers
declare whether or not system is
completely compliant with latest
FOIPPA standards.
1.4.2 All reasonable means should be
used to protect data from
unauthorized access, disclosure
or modification. Explain your
security
architecture/components.
- Identification of household
groups
- Patient status (e.g.
deceased)
3.4.6 Quick/copy (“clone”)
demographic information where
appropriate (e.g. for family
members)
3.5 Scheduling, Appointment
Booking, Arrival and Check-in
Recap (OPTIONAL)
3.5.1 Use the space below to describe
the features of the application
that you feel are noteworthy in
meeting the criteria.
4 Billing Requirements
4.1 Teleplan
4.1.1 Highly desirable that Billing
software be MSP Teleplan
compliant
State your compliance status
and the actual (or planned) date
of compliance for each of:
Pre-loaded PHCO
population-based funding patient
list ("patient register"). Patient list
will be supplied by the clinic, or
by MoHP/S, Primary Health Care
branch on behalf of the clinic.
4.1.6
Availability of complete
ICD9 and ICD10 code lists
through the billing software (not
just 3 and 4 character codes)
4.1.7 Preloaded MSP Fee Schedule at
the time of implementation.
4.1.8
Updates to the MSP Fee
Schedule and related MoH P/S
billing related reference tables be
made electronically through
Teleplan.
4.1.9
Diagnostic codes recorded in the
EMR automatically
transferred/translated to MSP
ICD9 billing codes for submission
and processing through Teleplan.
4.1.10
5 EMR Requirements
5.1 General Requirements
Highly desirable that the EMR:
5.1.1
Support the capture,
display and reporting of clinically
significant data in a multi-
disciplinary setting including but
not limited to physicians, nurses
and nurse practitioners, and
dieticians.
5.1.2
7 Reporting
7.1.1 Describe in general terms how
reports are produced and stored
by the system (i.e. exported to
Word, proprietary report viewer)
Provide a list of standard report
templates that are provided with
the system including but not
limited to:
7.1.2.1 Activity reports,
7.1.2.2 PHCO population-based
detail and summary reports,
7.1.2.3 PHCO access reports,
7.1.2.4 Chronic disease
management reports by
diagnosis, and
7.1.2.5 PHCO access reports.
7.1.2.6 Also include whether the
reports are tabular, periodic (e.g.
monthly, YTD, etc.), ad-hoc,
OLAP, KPIs, etc.
7.1.3 Describe tools available for
developing customized user-
defined reports. This might
include a proprietary report
writer, or a third-party tool such
as Crystal Reports.
http://healthnet.hnet.bc.ca/hds/approved_standards/sd99-01_hnt_health_registry_std.
http://www.healthservices.gov.bc.ca/cdm/index.html
9.8 Connectivity
9.8.1 Highly desirable that the
proposed solution support
comma delimited, file import and
export formats.
9.8.2 Highly desirable that the
proposed solution support
integrated connectivity among
health providers.
9.8.3 Describe connectivity standards
available with the solution such
as ODBC, SQL, SSL, 128-bit
encryption, etc.
9.8.4 Describe any messaging
standards available with the
solution, such as XML, HL7,
SMTP, etc.
Describe the current and/or
planned EMR connectivity to
(include if they are to be met by
configuration or programmatic
changes):
10 Future Capacity
10.1.1 Highly desirable that suppliers
develop familiarity with emerging
provincial and national standards
to ensure the timely
implementation of approved
standards in the EMR, for
example,
Electronic Medical
Summary (BC),
Electronic Signatures
(federal),
Electronic Prescription O/E
(federal),
Canada Health Infoway
architecture blueprint.
10.1.2 Use the space below to describe
your approach to maintaining
currency with approved and/or
mandatory standards indicating
when additional fees may be
incurred.
12 Services
12.1 Section Not Applicable
12.2 ASP or Local Installations
12.2.1 State your software operating
environment (local and/or ASP)
and describe your available
environments.
12.3
Software Installation Services
12.3.1 Describe the installation services
provided indicating whether
installation is performed locally
or remotely and any related
costs.
13 Support
13.1 Software Support
13.1.1 Highly desirable that the
suppliers provide a written
statement of their policies and
procedures regarding software
support for operational clients as
an appendix to the RFP
response. Support policies
should clearly:
Severity Level 5=
Enhancement/Upgrade request:
Response = 1 day to log request;
Target Resolution = Next
quarterly release
13.2
Master File and Tables Support
13.2.1 List all available master
files/tables and describe update
processes and schedules for
master files and code tables, and
the processes for converting
from one diagnostic code to
another, including but not limited
to:
Multi-disciplinary
Diagnostic Codes (e.g. ICD9,
ICD10-CA, ICPC, CSA body
codes for WCB reporting, etc.)
Pharmacare Formulary
MSP Fee Schedule, WCB
fee items, etc.
13.2.2 State the users ability to
customize and/or create user
preferred subsets.
13.2.3 Provide examples of on-line
context sensitive help, and an
example chapter of user guides
and operating manuals as an
appendix to your RFP response.
Excellent
Good
Acceptable
Marginally Acceptable
Weak Response
Unacceptable