1 - corporate qualifications - san joaquin county, … · web viewthe system displays a “vaccine...

1 - CORPORATE QUALIFICATIONS

1.1 - MAIN CONTACT

Name

Title

Address

Telephone Number

Fax Number

Email Address:

1.2 - COMPANY PROFILE

Name

Address (Headquarters)

Main Telephone Number

Website

of 83

Provide a description of your Company

Company Ownership- Private or Public

Parent Company Name (If Applicable)

Address

Telephone Number

Provide an organization chart of your

company and the portion responsible for

the solution

How long has the company been in

business providing the proposed products

and services?

How many total employees are dedicated

to the proposed product or solution?

List the number of employees by category Executives and Managers

Marketing / Sales

Installation

Research and Development

of 83

Application Support

Technical Support

Customer Service

Other

Those with clinical background -Physicians

-RN’s

- Other clinicians

Has your company been acquired or

merged with any other organizations in the

past three years? If so, please list each

organization and the purpose behind such

activity.

List all previous, or pending or threatening

litigation, arbitration, administrative or

other proceedings involving the Company,

any subsidiary or any joint venture

involving the Company or any subsidiary,

or any office or director (including parties,

remedies sought and nature of action.

of 83

List and description of all previous,

pending or threatened government or other

investigations involving the Company, and

subsidiary or any officer or director.

List any regulatory or compliance issues

previously or currently being addressed by

the company where there were any notices

or other correspondence concerning any

known or alleged violation of Federal,

state, or local laws, regulations,

agreements and / or commitments.

Please describe your alliances and

partnerships.

Please provide your most recently completed fiscal year financial statements and annual report.

Please provide a letter of credit equal to your proposed five-year cost that will remain in effect during the five-year contract period.

1.3 - MARKET DATA

Annual Revenue

Years in Ambulatory Market

of 83

Current health care clients using your

proposed system total?

List number of clients by categoryFederally Qualified Health Centers, Rural Health Centers,

Free Clinics, and Community Health Centers

Hospitals (count safety net/public hospitals separately)

Physician Offices

Home Care

Extended Care Facilities

Number of total sites implemented by local

implementation team.

How many de-installs has your company had in

the last 12 months and why?

1.4 - PRODUCT INFORMATION All attestations are based on the currently RELEASED version of your company’s software NOT FUTURE releases.

Product name and version

Is this product Open Source?

What year was your EHR system developed?

Indicate whether the system was internally of 83

developed or acquired from an outside source.

Is your proposed product web based or client/

server?

Size of largest installation (Provider licenses)

How often is the product upgraded?

Do you have a Users Group?

If ‘Yes’, how often does it meet?

Is the product certified by an ONC Authorized

Testing and Certification Body (ATCB)?

Version and Year(s) of Certification

Certifying Body

2 - PRICING AND CONTRACTSPlease provide a pricing proposal for software,

implementation, interfaces and hardware as

described in our profile. Separate EHR, Practice

Management, Patient Portal, etc.

How are your products priced (number of users,

patient visits, providers, per PC, etc)? Please

explain.

of 83

Is training included in your quoted price?

Please provide a copy of your standard contract

and SLA.

Please explain at what point the maintenance

contract begins and any hardware/software

warranty or install/acceptance period ends.

Do the proposed acquisition and/or ongoing

maintenance/support costs include:Future enhancements to acquired/licensed application

modules?

Operating system and related environmental software?

Interface maintenance?

Architectural changes such as migration to emerging

technologies and new methods of systems deployment?

Please describe the conditions and terms under

which enhancements/new releases are made

available to existing customers.

of 83

3 – SERVICE

3.1 - PROJECT MANAGEMENT

Indicate the specific senior executive

responsible for the proposed solution.

Provide a resume, years of experience

supporting projects like ours, and years of

experience with the company.

Indicate the number of other accounts

this person may be responsible for during

our project.

How many employees would comprise

the project team responsible for the

installation/implementation of this

project?

Describe the experience level, tenure, and

certification of your project managers,

implementation consultants, and project

team members.

Indicate the number of customer accounts

the project team may be responsible for

during our project.

Describe the resources required from the

client and also from your company

during the implementation. Indicate roles of 83

and skills required.

Are implementation staff persons used

from any 3rd party organizations?

List any approved or recommended

consulting organizations that can assist

with implementation services.

In what timeframe after contract signing

can your resources begin the project and

the implementation start?

Provide the normal length of an

implementation of the proposed solution.

Describe the implementation strategy and

conversion approach you would use to

carry out this project.

With your proposed solution are you able

to implement components or modules of

the application over time? Conversely,

can you implement the entire solution at

once? What would your organization

typically recommend?

Identify project management best

practices you previously employed in

other projects involving the proposed

solution which you would also use during

of 83

our project.

Include studies that support your

recommended approach.

Describe the change management

procedures that will be used for this

project.

Describe the approval, prioritization, and

governance procedures.

Provide a description of the decision-

making chain of command you would

propose for this project implementation

and for post-project ongoing support.

What support do you provide for process

redesign? Is this a separate engagement

or is it available as part of the

implementation?

Describe procedures for acceptance

testing.

Include a proposed work plan, with an

associated schedule to complete the work

for this project successfully.

Please detail any reliance on 3rd party

products or services.

of 83

3.2 - TRAINING/DOCUMENTATION

Describe the training needed by the client

to be successful during the

implementation.

Indicate the length and location of the

training and whether it is targeted for

implementation team or end users.

Describe the documentation (both system

and training) provided as part of the

standard installation including: Manager and user interface manuals (applications)

User operator/system administrator manuals

Hardware/OS manuals

Training manuals (initial and ongoing user self-training)

What documentation is provided with the

system? Is the documentation available in

hardcopy and electronically?

How often are documentation updates

made available to the user and in what

format (memo, revised manual, online,

CD, etc)?

Describe the types of training offered,

of 83

e.g. end user, system administrator,

installer, etc.

How often is training offered?

Please provide the duration of each class,

the location of the training, associated

costs, and recommended number of

people that should attend.

Who provides the proposed product

training?

Describe the post implementation

education services available from your

company. Include a discussion of the

types of media offered (e.g. classroom,

CBT, webinars)

Describe the training database available

in your system. Is it a mirror image of the

production files and the system’s test

database?

Describe your approach for training of

new releases and enhancements.

Describe the testing database available

for your systems? Can new software be

loaded and tested in the test database

before it is loaded into the live production of 83

system?

3.3 - SUPPORT SERVICES

Describe the ongoing support services

offered to your customers.

What are your Customer Support hours?

Please include the time zone.

Where are your Customer Support

Offices located?

Is there a charge for after hour support?

Describe the procedures customers

follow to report problems.

What are the methods of contacting the

support center?

What is the escalation process to address

an outstanding issue?

What is the location of your Field

Support Office or Field Support

Resources?

Indicate the availability of support

services after normal business hours.

Describe how updates, enhancements,

of 83

and new releases are delivered to

customers.

Indicate how software changes may be

made in order to keep up with any novel

federal and state regulatory and

compliance issues.

Describe the bug identification and

response process.

Describe the break fix process (Break fix:

refers to the situation when an application

function was working prior to a software

upgrade but fails afterwards.)

What is the frequency of software

versions and releases?

What is covered during the software

warranty period?

How long is the warranty period?

Describe how you engage the community

for input to product development.

Indicate the types of groups and how they

interact with your company.

Do you have advisory groups? Describe

their membership.

of 83

Detail how the customer can submit

product enhancement requests.

Is an Internet-based support portal

available to the customer?

Is a knowledge base available for

customers to self-service their support

questions?

Describe the process of adding and

managing users who can make support

calls or access the support portal.

Detail any support or maintenance for the

system that is provided by other

companies.

Please list the top 5 support questions you

receive from clients.

What is the range and average for system

downtime (scheduled and unscheduled)

for your clients’ systems?

4 - HIPAAWill your company sign a Business

Partner Agreement incorporating the

Business Partner and Chain of Trust

components as defined in the HIPAA of 83

regulations?

How is your organization preparing for

software changes required by the

meaningful use initiative and other

legislation?

Indicate if your product is compliant with

the following HIPAA application security

requirements: Access Controls

Audit Controls

Data Authentication

Entity Authentication (including unique user IDs, Automatic

Logoff)

Transmission Security

Integrity

of 83

5 - VENDOR INSTRUCTIONS FOR COMPLETING THE SPECIFICATIONS CHECKLIST

All vendors are required to complete all information requested in the “Vendor Profile” section.

Fill out all answers in Blue

When responding to the functional specification section, note that each functional statement’s priority is indicated in the “PRI” column which contains one of the following

values:

H = Highly Desirable

D = Desirable

An “X” under the MU (Meaningful Use) column indicates that the function is required under the Meaningful Use Final Rule.

Where the function is (or is not) provided by the system, place an “X” under one of the following columns:

“Yes, Included” = the function is available in the system and it is part of the basic system

“Yes, Additional Cost” = the function is available but it requires system customization at an additional cost

“No” = the function is not available

In addition, enter your response in the RESP (Response) column in accordance to one of the following:

5 = Completely meets requirements today. The function will be available on day 1 of ‘go live’.

4 = Partially meets requirements today

3 = Will completely meet requirements in future (specify date)

2 = Will partially meet requirements in future (specify required change and date)

1 = Can meet requirement through customization (specify price)

0 = Not planning to offer

of 83

Use the column labeled “Comments / Clarifications” to include additional information you wish to include as part of your response. This column can also be used to indicate

if a function is not currently available but will be available in a future release by indicating the version number and approximate month/year when the function will be

available (e.g. V6.1/May 2013).

of 83

6 - SPECIFICATIONS CHECKLIST

Specifications PRI MU RESP Yes, Included

Yes, Additional

CostNo Comments / Clarifications

ELECTRONIC HEALTH RECORDS

1 Meaningful Use (as defined in CMS’ Final Rule for the Medicare & Medicaid EHR Incentive Program)

1.1 The system supports the entire Meaningful Use Final Rule. Each of the specification target dates is met with ample time to allow for template modifications, data entry and report production

H X

2 General

2.1 The system supports both a total paperless function and a hybrid function (part paper, part electronic) where the contents of the electronic record can be printed for inclusion in the paper chart.

H

2.2 The system interfaces with a variety of digital and analog dictation systems (state devices). H

2.3 The system date and time stamps all entries. H

2.4 The system includes automatic translation of codes to data. For example:

2.4.1 ICD-9-CM H

2.4.2 DSM-IV D

2.4.3 CDT D

2.4.4 CPT (4 and 5) H

2.4.5 ICD-10 H

of 83


Yes, Additional


2.4.6 SNOMED CT H

2.4.7 LOINC H

2.4.8 APC H

2.4.9 NDC H

2.5 Automatic E&M coding, verification and charge pass-through to practice management are available.

2.6 The system includes support and updates for the above vocabularies. H

2.7 The system supports user defined vocabularies, and allows for updates and enhancements of such vocabularies. D

2.8 The system supports the HIPAA Standards for Electronic Transactions. H

2.9 The system supports the integration of third party coding programs. H

2.10 The system includes extensive error checking of all user input data, including, but not limited to:

2.10.1 ICD-9 (Check diagnosis against gender, age, other as necessary) D

2.10.2 ICD-9 procedure checking against diagnosis D

2.10.3 Extensive date checking for validity as well as ensuring a valid chronological order of events (dx before treatment, scheduling after birth, etc.).

D

2.11 The system includes SNOMED CT as the integrated standard nomenclature of clinical terms. H

3 Demographics / Care Management

of 83


Yes, Additional


3.1 The system supports the Continuity of Care Document (CCD) as the harmonized format for the exchange of clinical information including patient demographics, medications, problems and allergies.

H

3.2 The system identifies and maintains a single patient record for each patient. H

3.3 The system is able to accept an HL7 ADT message from another hospital information system as the source of new patient record identifiers.

H

3.4 The system supports a user verifiable record merge function. D

3.5 The system supports purging of incomplete or partial records (i.e. those created by auto population from the practice management system but for which no clinical data exists).

D

3.6 The system captures and maintains demographic information. Where appropriate, the data should be clinically relevant, reportable, and traceable over time.

H

3.7 The system creates and maintains patient-specific summary lists that are structured and coded where appropriate. D

3.8 The system has the capability of importing patient demographic data via HL7 interface from an existing Practice Management System, Patient Registration System, or any such system used for patient registration and/or scheduling. In addition to gender and date of birth, of specific interest, are the following data:

H X

3.8.1 Collect Race data with categories as specified by OMB H X Ref: http://www.iom.edu/Reports/2009/RaceEthnicityData.aspx

3.8.2 Collect Ethnic Group as defined by IOM H X Ref: http://www.iom.edu/Reports/2009/RaceEthnicityData.aspx

3.8.3 Housing Status including effective dates H

3.8.4 Migrant Farm Worker Status including effective dates H

of 83

http://www.iom.edu/Reports/2009/RaceEthnicityData.aspx

http://www.iom.edu/Reports/2009/RaceEthnicityData.aspx


Yes, Additional


3.9 The system has the capability to import/create, review, update, and hide patient demographic information as well as other non-clinical information from the patient record in both PMS and EMR.

H X

3.10 The system captures permanent patient address. H

3.11 The system captures temporary patient addresses. H

3.12 Preferred spoken language H X

3.13 Preferred written language H X

3.14 Translator needed D

4 Patient History

4.1 The system allows the capture, review, and management of medical procedural/OB/surgical, oral health, social, and family history, including the capture of pertinent positive and negative histories, and patient-reported or externally available patient clinical history (includes birth history, dietary/nutrition history, immunization history, allergy and developmental history for children and behavioral health history).

H

4.2 For each new patient, the system captures and stores risk factors. For example:

4.2.1 History of STDs or STIs H

4.2.2 Sickle cell status H

4.2.3 TB Status H

4.2.4 Tobacco use and history including number of years and packs per day (PPD) H X

of 83


Yes, Additional


4.2.5 Alcohol use, history H

4.2.6 Drug use, history H

4.2.7 Occupational Environment H

4.2.8 Living/Residential Environment H

4.3 For each new patient, the system captures and stores the following social history elements:

4.3.1 The system allows the tracking of domestic partners as well as married couples. H

4.3.2 Occupation H

4.3.3 Religious preference H

4.3.4 Socioeconomic status H

4.3.5 Education/Literacy H

4.3.6 Housing Status D

4.3.7 Disabilities D

4.4 The system has the capability to import patient health history data, including obstetrical history data, from an existing system. D

4.5 The system documents hospitalization and emergency department data including:

4.5.1 Admission and Discharge dates for all type of hospitalizations (i.e. behavioral health, substance abuse, physical rehabilitation, ER, etc.)

H

of 83


Yes, Additional


4.5.2 Chief complaint D

4.5.3 Admitting diagnosis / Other diagnoses H

4.5.4 Procedures performed H

4.5.5 Discharge summary H

4.5.6 Discharge disposition H

4.5.7 Emergency room visit and discharge date(s) H

4.6 The system documents all existing allergies, interactions, and adverse reactions such as:

4.6.1 Drug H X

4.6.2 Food H

4.6.3 Drug-food plus other (e.g. bee sting, environmental allergies) H

4.7 The system captures history of received immunizations. H

4.8 The system captures alternative and herbal medications, OTC medications, and supplements. H X

4.9 The system has the capability of linking or grouping records of other family members on file. H

4.10 The system has the capability to capture and store genograms. D

4.11 The system collects and stores family history, including, but not limited to:

4.11.1 History of chronic diseases, including date of diagnosis H

of 83


Yes, Additional


4.11.2 Disease status D

4.11.3 Family member functional status D

4.11.4 If deceased: date and cause of death D

4.12 The system presents a chronological, filterable, and comprehensive review of patient’s EHR, which may be summarized, subject to privacy and confidentiality requirements.

H

4.13 The system captures and explicitly labels patient-provided and patient-entered (and/or parent-, family member-, or guardian-provided or -entered) clinical data and supports provider authentication for inclusion in patient history.

D

5 Current Health Data, Encounters, Health Risk Appraisal

5.1 The system includes a combination of system default, provider customizable, and provider-defined and reusable templates for data capture.

H

5.2 The system obtains test results from laboratory, radiology / imaging, or other equipment or technology related procedures and other clinical documents and notes via standard HL7 interface.

H X

5.3 The system has the capability to incorporate clinical documentation from external sources. H

5.4 The system has the capability to capture and monitor patient health risk factors in a standard format. H

5.5 The system can display encounter data using a problem-oriented format. D

5.6 The system supports online completion of health surveys or other forms (portal functions). D

5.7 The system supports the capture, graphic display, and plotting of forms requiring graphic representation. D

of 83


Yes, Additional


5.8 The system has the capability of reproducing and displaying a variety of end user patient and treatment forms. D

5.9 The system has the capability to update other portions of the record with captured vital signs data. At minimum, the system collects:

5.9.1 Height H X

5.9.2 Weight H X

5.9.3 Pulse H

5.9.4 Respiratory rate H

5.9.5 Blood pressure (including multiples) H X

5.9.6 Different position blood pressures H

5.9.7 Oximetry (with FiO2 identifier) H

5.9.8 Pain H

5.9.9 BMI (calculated) H X

5.9.10 Visual Acuity (corrected / uncorrected) H

5.9.11 Audiology screening H

5.9.12 Last menstrual period H

5.10 The system incorporates one or more accepted measure of functional level, e.g. the GAF. H

of 83


Yes, Additional


5.11 The system has the capability to import/create, review, update, and amend health data (objective and subjective) regarding the patient’s current health status, including (as applicable):

5.11.1 Chief complaint H

5.11.2 Onset of symptoms H

5.11.3 Injury mechanism H

5.11.4 Physical examination findings H

5.11.5 Psychological and social assessment findings H

5.12 The system provides a flexible mechanism for retrieval of encounter information that can be organized in variety of ‘views’. For example:

5.12.1 By name (last, first; first, last; etc.) H

5.12.2 By date of birth H

5.12.3 Chronological by encounter date H

5.12.4 By diagnosis H

5.12.5 By diagnosis type H

5.12.6 By chart number H

5.12.7 By family group / linkage D

of 83


Yes, Additional


5.13 The system provides a flexible, user modifiable, search mechanism for retrieval of information captured during encounter documentation.

H

5.14 The system provides a mechanism to capture, review, or amend history of current illness. H

5.15 The system ensures dynamic documentation during the encounter complying with all standard coding rules. D

5.16 The system enables the origination, documentation, and tracking of referrals between care providers or healthcare organizations, including clinical and administrative details of the referral.

H

5.17 The system has the capability to evaluate referrals within the context of the patient’s clinical data. D

5.18 The system is capable of providing a summary of care record for each referral, when a patient is referred to another provider of care

D X

5.19 The system captures the following referral information:

5.19.1 Referral type (Reason for referral) H

5.19.2 Date H

5.19.3 Reason H

5.19.4 Referring Provider H

5.19.5 Referred to Provider H

5.19.6 Payer D

5.20 The system tracks consultations and referrals. H

of 83


Yes, Additional


5.21 The system has the capability of printing consultations / referrals forms. H

5.22 The system provides a mechanism to capture, review, track (assign a number), and print a specific consultation or specialist report

H

5.23 Describe how templates can be created for different types of specialty practices. Are they user defined? Can multiple templates be combined and used by the physician?

H

6 Children’s Health

6.1 The system displays the age of a child in appropriate units as specified by CCHIT Child Health Criteria. H See 2011 Comprehensive Child EHR Certification Criteria CHO1.01

6.2 Height (children) English/metric – Calculated percentile H

6.3 Weight (children) English/metric – Calculated percentile H X

6.4 Head circumference (children) English/metric – Calculated percentile H

6.5 Body mass index (children) English/metric – Calculated percentile H X

6.6 The system displays growth charts showing plotted values of height, weight, head circumference and BMI against age and sex normed data

H X

6.7 The system suggests appropriate drug dose in volume/dose when given a drug formulation specifying concentration and mg/mL, a patient’s weight (in lb. or kg), a dose in mg/kg and a frequency (e.g. given a 250mg/ml formulation, a 12 lb child, and planned dose of 80 mg/kg/day divided twice daily, suggests mL/dose).

H

6.8 Newborn screening results (including sickle cell status) H

of 83


Yes, Additional


6.9 Stage of sexual maturity (e.g., Tanner stages) H

6.10 Developmental Status (based on standardized screening tool) H

7 Pregnancy Care

7.1 The system accepts coded input for historical items that are asked at each pregnancy visit (could include, but not limited to key symptoms e.g. loss of fluid, fetal movement, etc.)

H

7.2 The system makes pregnancy past history available to the provider for future pregnancies and displayed separate from past medical history.

H

7.3 The system records fetal heart rate, fundal height, weight, urine analysis and blood pressure at each visit H

7.4 The system provides for a flexible configuration for dates or time since a specified event to be used for notification and alerts H

7.5 The system displays the estimated date of delivery (EDD) given the patient’s last menstrual period (LMP). The system will calculate an EDD given an ultrasound date and the estimated gestational date (EGA) given by the ultrasound. The provider may specify which of the above methods will be used to calculate the patient’s final due date. The EGA (based on the method specified by the provider) is clearly visible at each visit

H

7.6 The system will prompt the provider about care that is due at each visit based on the EGA (calculated using the specified method above.)

H

7.7 The system creates a printable view of all visits, labs, due date, ultrasound, problem list and plans which can be given to a patient for purposes of communicating with providers on a Labor and Delivery floor.

H

7.8 The system can exchange data about the current pregnancy with other hospital and/or health information exchange systems. H

of 83


Yes, Additional


8 Behavioral Health

8.1 The system shares the medication list across the entire system. H X

8.2 The system includes a single medication module shared by both the primary care and the behavioral health module H X

8.3 The system includes an integrated diagnostic module shared with the behavioral health module. H X

8.4 The system can limit the sharing of behavioral health diagnoses and medications if configured this way by the organization H

8.5 For FQHCs doing Behavioral Health in addition to primary care, the system requires/allows for a treatment plan. H

9 Encounter – Progress Notes

9.1 The system records progress notes utilizing a combination of system default, provider customizable, and provider-defined templates.

H

9.2 The system has the capability to automatically update other sections of the record with data entered in the progress note. H

9.3 The encounter - progress note template includes space for entering performed and planned procedures. It also includes: H

9.3.1 Performed/planned laboratory procedures H

9.3.2 Diagnosis H

9.3.3 Goals (provider’s and patient’s) and follow-up plans including next visit H

9.3.4 Medications prescribed H

9.3.5 Non-drug prescriptions (e.g. exercise, dietary recommendations, complementary and alternative therapies including massage)

H

of 83


Yes, Additional


9.3.6 Patient education materials are culturally and linguistically appropriate and are written at an appropriate health literacy level

H

9.3.7 Consultation/referrals H

9.3.8 Patient condition or status H

9.4 The system includes a progress note template that is problem oriented and can be linked to either a diagnosis or problem number.

D

9.5 The system has the capability of retrieving encounters by a variety of user-defined parameters. D

9.6 The system enables standard phrases to be defined/contained in tables and used as pull down menus to reduce the key entry effort.

D

9.7 The system allows for a number of different types of input methods (e.g. OCR, image capture, voice recognition, dictation/transcription services, keyboard entry.)

H

9.8 The system enables progress notes to be sorted for viewing in chronological or reverse chronological order by encounter date in relation to the active care plan.

D

9.9 The system applies security controls to progress notes to ensure that data cannot be deleted or altered except within the current session and by an authorized user.

H

9.10 The system includes a medical terminology dictionary and a spell checker within the progress notes data entry module. D

9.11 The system supports the capability to automatically collect the data elements defined by the associated clinical practice guideline or order.

H

10 Problem Lists

10.1 The system creates and maintains patient-specific problem lists. Separation of chronic and acute problems is readily evident. H X

of 83


Yes, Additional


10.2 The system provides a problem status (active, inactive) for each shown problem. H X

10.3 The system organizes applicable patient data into comprehensive problem summary lists. H

10.4 The system provides problem descriptions based on the SNOMED CT standard controlled vocabulary H

10.5 The system allows clinicians to identify and record new patient problems as well as the current status of existing problems. H

10.6 The system expands the problem summary list on demand. D

10.7 The system updates the active problem list from relevant data in the progress note with appropriate end-user confirmation. D

10.8 When capturing problem information, the system captures:

10.8.1 Diagnosis / problem date(s) H

10.8.2 Severity of illness, as appropriate. H

10.9 For each problem, the system has the capability to create, review, or amend information regarding a change on the status of a problem (e.g. the date of diagnosis).

D

10.10 The system has the capability of allowing the display of past interventions, hospitalizations, diagnostic procedures, and therapies for review at the option of the provider

H

11 Clinical Practice Guidelines (CPG)

11.1 The system includes and maintains evidence-based Clinical Practice Guidelines (CPGs) published and maintained by nationally recognized authoritative sources (e.g. U.S. Preventive Services Task Force (USPSTF) or others). The guidelines incorporate patient education and actionable alerts and reminders.

H

of 83


Yes, Additional


11.2 At minimum the system includes CPGs for the following:

12.2.1 Asthma H

12.2.2 Congestive Heart Failure H

12.2.3 Depression H

12.2.4 Diabetes H

12.2.5 Coronary Artery Disease H

12.2.6 Hyperlipidemia H

12.2.7 COPD H

12.2.8 HIV/AIDS H

12.2.9 Cervical Cancer H

12.2.10 Breast Cancer H

12.2.11 Hypertension H

11.3 The system has the capability of allowing initial authoring and revising of clinical practice guidelines. H

11.4 The system allows for import of CPG and other CDS from outside content providers (e.g. Zynx). H

11.5 The CPG module imports/creates the facility for rapid documentation of the patient’s progress along the CPG phases. H

11.6 The format utilized by the guideline for documenting is intuitive, easy to use, and user customizable. H

of 83


Yes, Additional


11.7 The CPG module utilizes pull down menus and check boxes to speed up data entry. H

11.8 The system allows reporting and analysis of any / all components included in the CPG. H

11.9 Included in each CPG, the system has the capability to create, review, and update information about:

11.9.1 The performance measures that will be used to monitor the attainment of objectives H

11.9.2 The quantitative and qualitative data to be collected H

11.9.3 Performance metrics: CPG shall allow for decision support based on standardized discrete data to be used to calculate clinical performance measures (e.g. HEDIS).

H

11.9.4 Collection means and origin of data to be evaluated H

11.10 The system allows the provider or other authorized user to override any or all parts of the guideline. The system is able to collect exceptions for NOT following the CPG.

H

12 Care Plans

12.1 The system provides administrative tools for organizations to build care plans and guidelines, for use during patient care planning and care.

H

12.2 The system is capable of providing a summary of care record for each transition of care or referral, when a patient is transitioned to another setting of care or provider of care or is referred to another provider of care.

H X

12.3 The system identifies and presents the appropriate care plans, guidelines, and/or protocols for the management of specific conditions that are patient-specific. At minimum, the system shall provide care plans for chronic diseases referenced in 7.2 above.

H

of 83


Yes, Additional


12.4 The system has the capability to import/create, review, and amend information about the desired single or multi-disciplinary long / short term goals and objectives that will be accompanied by the care plan.

H

12.5 The system has the capability to import/create, review, and amend information about the proposed set of single or multi-disciplinary care plan options that are based upon expected outcomes.

H

12.6 The system generates and automatically records in the final document, patient-specific instructions related to pre- and post-procedural and post-discharge requirements. The instructions must be simple to access.

D

12.7 The system can generate and automatically record in the final document "Time Out" was done prior to the procedure - to include

12.7.1 Correct patient identified H

12.7.2 Correct procedure confirmed H

12.7.3 Procedure and risk were explained H

12.7.4 Correct side and site confirmed H

12.7.5 Questions were answered and patient agrees to procedure H

12.7.6 Accurate consent obtained H

12.8 The system can generate and automatically record patient - specific multilingual educational instruction related to their medical condition.

H

12.9 The system has the capability to import/create, review, and amend information about:

of 83


Yes, Additional


12.9.1 The provider’s explanation and the patient or patient representative’s understanding of the recommended and/or alternative care plan options

D

12.9.2 The medical orders, which authorize the execution of the selected, care plan D

12.9.3 The collection of specimens (body fluids, tissue, etc.) from the patient to be used for diagnostic or treatment purposes D

12.9.4 The actions taken to safeguard the patient to avert the occurrence of morbidity, trauma, infection, or condition deterioration

H

12.9.5 The provider's explanation and the patient or patient representative's understanding of health proxy and DNR consent

H

13 Prevention

13.1 The system has the capability to display prevention prompts on the summary display. The prompts must be dynamic and take into account sex, age, and chronic conditions.

H

13.2 The system allows interactive prevention status documentation. At minimum:

13.2.1 Date addressed H

13.2.2 Result H

13.2.3 Reason not performed H

13.2.4 Where performed H

13.3 The system allows the preventive measures done on the visit to automatically populate the health maintenance summary template

H

13.4 The system includes user-modifiable health maintenance templates. H

of 83


Yes, Additional


13.5 The system includes a patient tracking and reminder capability (patient follow-up) updatable by the user at the time an event is set or complied with.

H

13.6 The system allows the graphing of pertinent data into flow sheets for presentation/display. H

13.7 The system includes the incorporation of immunization protocols:

13.7.1 Universal child H

13.7.2 Universal adult H

13.7.3 Specific foreign travel D

13.8 The system includes immunization forecasting and notifies the user of vaccines that are past due and of due dates for upcoming due vaccines, and is capable of documenting vaccine refusal

H

13.9 The system allows providers to order appropriate vaccines, with staff having access to those ordered on a separate computer (tablet), on which they can record specific manufacturers/lots used (drop-down lists), site of administration, and VIS publication dates/dates provided; (drop-down lists will display only vaccine lots – private vs. state – appropriate to patient’s status as private insured, Medicaid, uninsured, underinsured, etc)

H

13.10 The system displays a “Vaccine Administration Record” (informed consent) type form, which displays the above information and is electronically signed by the party responsible for granting consent and the person administering the vaccines

H

13.11 The system allows for printing an updated “shot record” (perhaps also height, weight, etc. information) at the end of each visit

H

of 83


Yes, Additional


13.12 The system updates the practice inventory of available vaccines each time one is recorded as having been administered; a report on private and public funded vaccine inventories can be displayed or printed at any time

H

13.13 The system will send and receive information from the state’s Department of Health Immunization Information System website, if one exists, including vaccine inventories, individual patient vaccine administration histories and updated demographics

H

13.14 The system is capable of reporting to VAERS to report reactions to vaccinations D

13.15 Support the ability to view all of the patient’s physicians (e.g. consulting, attending, admitting, and referring) and their role in a single “population” view.

D

13.16 Support the ability to add or remove patients from the “population” individually or by group. H

13.17 Display measurement indicators with patient name on the “population”. H

13.18 Patients can be added automatically to a “population” based on problems, diagnoses, allergies, medications, age, and/or gender. H

13.19 Provide a long-term repository for all clinical patient data with a longitudinal view of the patient’s clinical data. D

13.20 Provide the ability to “drill down” from summary to detail without paging through multiple screens. H

13.21 Support trending and graphing of result information. H

13.22 Support the ability to launch images from result view (including PACS viewer). D

13.23 Support multiple normal reference range values for individual observations. H

13.24 Highlight abnormal and critical values as defined by the customer. H

of 83


Yes, Additional


13.25 Abnormal or critical values are indicated along with reference ranges for each test. H

13.26 Ability for the physician to add comments to lab results. D

13.27 Support access to results using flexible search criteria and non-unique service names. H

13.28 Support configurable flow sheets for specialized results presentation. H

14 Patient Education

14.1 The system has the capability to create, review, update, or delete patient education materials. The materials must originate from a credible source and be maintained by the vendor as frequently as necessary.

H

14.2 The system has the capability of providing printed or electronic patient-specific education materials or resources to the patient on demand or automatically at the end of the encounter.

H X

14.3 The system is capable of providing the materials or resources indicated in 14.2, in the patient’s preferred language. At minimum, the materials must be provided in English and Spanish as applicable.

H

14.4 The system includes or the capability to develop patient instructions in English and in the patient’s preferred language for a broad range of treatments and services delivered by providers. Examples:

14.4.1 Care of wound H

14.4.2 Exercise regimen H

14.4.3 Diet guidelines H

14.4.4 Oral Health H

of 83


Yes, Additional


14.4.5 Behavioral Health H

14.5 Administration and care of medications: H

14.5.1 The system allows patient instructions to be selected from a pull down list D

14.5.2 The system allows user modifications to instructions to suit individual patient needs without altering the original content D

14.5.3 The system enables the linkage of patient instructions to care plans/care maps/ practice guidelines/orders, enabling automatic printing

D

14.6 The system allows patient instructions to be printed on demand independent of care plans/care maps/guidelines/orders. D

14.7 The system includes the facility to create a directory of information for patient support groups and to include any applicable support group information in the instructions.

D

14.8 The system is capable of listing the educational materials printed for the patient on the final document H

15 Alerts / Reminders

15.1 The system includes user customizable alert screens / messages, enabling capture of alert details, including, but not being limited to:

15.1.1 Text describing the alert H

15.1.2 Date and time of the alert H

15.1.3 The system prints the alert on demand H

15.2 The system has the capability of forwarding the alert to a specific provider(s) or other authorized users via secure electronic mail or by other means of secure electronic communications.

D

of 83


Yes, Additional


15.3 The system tracks the user’s response to an alert. Alert frequency and override reasons are reportable by user or group. H

15.4 The system allows the user to document rationale for following/not following an alert. H

15.5 Relevant Reminders/Alerts are displayed when a patient chart is opened. D

15.6 The system is capable of utilizing alerts to facilitate sending of reminders to patients per patient preference for preventive or follow up care; and to track that status of such reminders

H X

15.7 The system includes an internal “notes” function that clinicians can use to remind themselves of non-alert/reminder issues. These items should be easily removed when complete.

D

16 Orders

16.1 The system includes an electronic Order Entry module that has the capability to be interfaced with a number of key systems (lab, pharmacy, radiology) through standard, real time, HL7 bidirectional interfaces.

H X

16.2 The system captures and tracks orders based on input from specific care providers. H

16.3 The system has the capability to submit diagnostic test orders based on input from specific care providers. H

16.4 The system has the capability to print orders for manual transmission. H

16.5 The system has the capability to fax orders. When faxing orders, the system shall determine and report whether the transmission was successful (i.e. received at destination).

H

16.6 The system has the capability to require that all orders be digitally signed at the completion of each order. H

16.7 The system accepts orders from multiple locations. H

16.8 The system has the capability to assign and display an order number for active, hold, and pending orders. D

of 83


Yes, Additional


16.9 During the order entry process, the system has the capability to require the user to acknowledge an error message prior to being allowed to continue with the data entry function.

H

16.10 The system allows the user to accept, override, or cancel an order. H

16.11 The system requires the user to enter a justification for overriding, changing, or canceling an order prior to being allowed to continue.

H

16.12 The system includes the visual indication of orders in need of review. H

16.13 The system detects and displays duplicate orders issuing visual and auditory warnings, and allows the user to override the warning after entering a justification for the override.

H

16.14 The system includes the capability to:

16.14.1 Define order sets, based on provider input or system prompt, for each provider or service department. H

16.14.2 Accept order sets from a third-party content provider (e.g. Zynx Ambulatory). H

16.14.3 Contain all information specific to one order in one display screen H

16.14.4 Include a pull-down list of all order departments to enable multiple orders H

16.14.5 Include a user-configurable / customizable pull-down list of tests and services from which to place one or more orders D

16.14.6 The system allows the provider to create/modify the most commonly used orders to assist in order placement D

16.15 The system can display all order sets including components, by any of the following:

16.15.1 By procedure D

of 83


Yes, Additional


16.15.2 By provider D

16.15.3 By diagnosis D

16.15.4 By date D

16.16 The system has the capability to specify/display exploding orders. H

16.17 The system has the capability to enable selected orders to be recurring orders. H

16.18 The system includes an order inquiry mechanism to allow providers to inquire on the details of an order. H

16.19 The order inquiry function is accessible within the order entry flow before the session is terminated. H

16.20 An order, at the user’s option, displays all the detail data associated with the order, including demographics, order parameters, electronic signatures, and order status

D

16.21 The system displays order summaries on demand to allow the clinician to review/correct all orders prior to transmitting/printing the orders for processing by the receiving entity.

H

16.22 The system is capable of reporting/listing all orders which have not been completed or received H

16.23 Support all areas of the General Laboratory (i.e. Chemistry, Hematology), Microbiology, Blood Bank and Anatomic Pathology.

H

16.24 Automatically assign ICD-9CM or ICD-10 codes given the diagnosis is provided by the physicians during the ordering protocol.

H

16.25 Support for Point-of-Care testing devices. H

of 83


Yes, Additional


16.26 Provide a detailed explanation of eSignature architecture and related operational flow. What controls are in place? Does the application support a secondary password/pin entry at time of signature? Does the application support co-signatures and other types of supervisory review/approval? How does the application support and track multiple provider entries for various components of documentation? Be specific as to how eSignature supports the workflow in an academic facility with significant resident and student activity.

17 Results

17.1 The system has the capability to route, manage, and present current and historical test results to appropriate clinical personnel for review, with the ability to filter and compare results

D

17.2 The system accepts results via standard bidirectional HL7 interfaces from all standard interface compliant / capable entities or through direct data entry. Specifically – Laboratory (clinical and anatomic pathology), Radiology, and Pharmacy information systems; clinical laboratory test results are incorporated into the EHR as structured data

H X

17.3 The system includes an intuitive interface for graphing and trending lab results H

17.4 The system allows authorized users to copy selected results into a note H

17.5 When displaying results, the system, at a minimum, displays the patient name, date and time of order, date and time results were last updated, as well as any alerts identifying changes/amendments to the test or procedure, and test name to include source of results (i.e. PHR, hospital, etc.)

H

17.6 The system is capable of providing on-demand to the patient an electronic copy of their health information (including diagnostic test results, problem list, mediation lists, medication allergies)

H X

of 83


Yes, Additional


17.7 The system is capable of providing clinical summaries for patients for each office visit H X

17.8 The system has the capability to evaluate results against normal values and notify the provider. H

17.9 The system uses visual cues to highlight abnormal results. H

17.10 The system allows reporting of relevant electronic laboratory results for reportable conditions to appropriate public health authorities

D

17.11 The system is capable of exchanging key clinical information (e.g., problem list, medication list, medication allergies, diagnostic test results), among providers of care and patient authorized entities electronically

H X

17.12 The system allows the provider to signoff and comment on received lab results. H

17.13 PACS/imaging integration H

17.14 How does the system screen lab results and send parameter-based panic alerts based on user-defined criteria in the system? (e.g.: Different panic level parameters for dialysis patients vs. non-dialysis patients)

17.15 How are incorrectly posted lab results removed or revised?

18 Medication and Immunization Management

18.1 The system creates e-prescriptions or other medication/immunization orders, including herbal medications and orders for durable goods, with detail adequate for correct filling and administration. It provides information regarding compliance of medication orders with formularies.

H X

of 83


Yes, Additional


18.2 The system presents to appropriate clinicians the list of medications/immunizations that are to be administered to a patient, under what circumstances, and captures administration details.

D

18.3 The system identifies patient drug allergy, drug - drug interaction and drug – disease severity of interaction warnings (prescription, over the counter) at the point of medication ordering. Clinical Decision Support (CDS) include drug-drug, drug-allergy and drug-formulary as stated in MU Reg.

H X

18.4 The system alerts providers to potential administration errors for both adults and children, such as incorrect patient, incorrect drug, incorrect dose, incorrect route, and incorrect time in support of medication administration or pharmacy dispense/supply management and workflow.

D

18.5 The medication module includes access to the National Drug Classification (NDC) database. H

18.6 The system stores common prescriptions/immunizations for quick entry and allows users to define favorites. H

18.7 The system supports multiple drug formularies and prescribing guidelines. H X

18.8 The system provides the capability to select both the patient and the drug in an intuitive, easy to manage user interface H

18.9 The system has the capability of displaying medications/immunizations prescribed both before and after the visit, of creating and maintaining a current medication list for each patient and updating the progress note with prescription information as necessary, and verification of medications

H X

18.10 The has capability to perform medication/immunization reconciliation H X

18.11 At the provider’s option the system has the capability of selecting drugs to be prescribed from the patient’s medication list.

H

of 83


Yes, Additional


18.12 The system allows the provider the ability to document the effectiveness or ineffectiveness of a medication. H

18.13 The system stores refill and repeat prescription information. H

18.14 The system allows storage of prescription/immunization data for retrieval by any of the following:

18.14.1 Drug name H

18.14.2 Drug code number (NDC) H

18.14.3 Dosage prescribed H

18.14.4 Schedule, including formulary management H

18.14.5 Other user defined selection criteria (e.g. route of administration) D

18.15 The system provides the following drug/prescription order information:

18.15.1 Drug contraindication H

18.15.2 Active problem interactions H

18.15.3 Check that appropriate laboratory monitoring has been obtained H

18.16 The system provides extensive drug interaction information H

18.17 The system creates and maintains an active patient-specific drug allergy and adverse reaction lists and allows on demand or scheduled reporting from such lists.

H X

18.18 The system includes clinician-modifiable therapeutic guidelines. H

of 83


Yes, Additional


18.19 The system maintains a history of all prescribed medications including those prescribed elsewhere and/or by outside physicians; and OTC medications, supplements, alternative or herbal remedies as reported by the patient. The history segment contains space for appropriate comments.

H

18.20 The system fully complies with existing regulations and restrictions applicable to the prescription of dangerous or regulated drugs.

H

18.21 The system alerts providers to potential misuse of controlled substances by reference to a public health controlled substance database

D

18.22 The system provides the capability for e-prescribing to a pharmacy or organization selected pharmacy for dispensing. H X

18.23 The system allows faxing when e-prescribing is not available H

18.24 The system includes other methods of prescribing when those above are not available H

18.25 The system has the capability to capture sample medications including lot number and expiration date. H

18.26 Allows user to specify the ordering physician during order entry H

18.27 Support entry of non-formulary drug orders. H

18.28 Identifies automatically that medication is FDA approved per diagnosis. D

18.29 Handle non-standard dosing frequencies (for example, every other day, M-W-F, daily for 21 days - skip 7 days - repeat, every Monday, etc.)

H

18.30 Perform price calculation during drug inquiry. H

18.31 Manage “stop orders” and easily identify “stop orders” on screen and on Medication Summary Report. Provide a report for “stop orders”.

D

of 83


Yes, Additional


18.32 Ability to redirect orders to provider other than ordering provider and can be changed by a system administrator. H

18.33 Ability to calculate dosages based upon different weights (ideal body weight, absolute body weight, admission weight, birth weight, etc).

D

18.34 Ability to print MAR on demand. H

18.35 Enable user to document medication errors and adverse drug events. H

18.36 Support management of floor stock inventory. D

18.37 Ability to print floor stock item list for each unit. D

18.38 Provide an inventory control module that supports the process of conducting a complete physical inventory. D

18.39 Interface with the wholesaler’s electronic order entry system. D

18.40 Ability to automatically generate restock orders to the wholesaler. D

18.41 Ability to automatically update pricing and packaging information based upon data received from wholesaler. D

18.42 Provide standard drug utilization reports with various sort options. H

18.43 Support reporting and documentation required for participation in 340B Federal Drug Discount program. H

18.44 Supports multiple sample medication inventory areas. D

18.45 Print the sample medication inventory by area. D

18.46 Supports reporting of sample medication issue by provider and can stratify by patient type. D

of 83


Yes, Additional


18.47 Ability to sort orders for verification according to defined categories of order prioritization, e.g. STAT orders that need verification before regular orders.

H

18.48 The system is capable of submitting electronic data to immunization registries or Immunization Information Systems in accordance with applicable law and practice

H X

18.49 Discuss security and auditing within the Pharmacy system.

18.50 Describe the capabilities of system’s report writer and provide sample reports.

18.51 Describe the integration with pharmacy clearinghouses such as SureScripts or RxHub?

18.52 Describe the capability to configure the system’s drug interaction/clinical decision support alerts.

18.53 Describe how the prescription is automatically checked for prior adverse reactions and potential drug interactions.

18.54 Describe how the prescription is automatically checked for insurance formulary compliance?

19 Document Imaging

19.1 Supports XML, PDF, BMP and JPEG formats. H

19.2 Versioning of documents. H

19.3 Rotate images (e.g. 45, 90, 180 degrees). H

19.4 Store any/all documents that would normally be part of the paper-based patient record. H

19.5 Accept encapsulated PDF via HL7 transmission from other hospital information systems (e.g. inpatient EHR).

of 83


Yes, Additional


19.6 Includes a section for documents not produced internally by our health organization. D

19.7 Secure to the folder level medical records that are considered sensitive (e.g. behavioral health, diagnosed conditions such as HIV, or in the case of staff).

H

19.8 How do you define/support the legal EHR?

20 Confidentiality and Security

20.1 The system protects electronic health information created or maintained by the certified EHR technology through the implementation of appropriate technical capabilities (based on a risk analysis per 45 CFR 164.308 (a)(1))

H X

20.2 The system supports single-sign on technology. It also supports biometric technology for logon as well as 2-factor authentication.

H

20.3 Supports industry standard electronic signatures. H

20.4 The system controls access to and within the system at multiple levels (e.g. per user, per user role, per area, per section of the chart) through a consistent mechanism of identification and authentication of all users in accordance with the ‘Role Based Access Control’ (RBAC) standard.

H

20.5 The system verifies and enforces control to all EHR components, information and functions for end users, applications, sites, etc., to prevent unauthorized use of a resource, including the prevention or use of a resource in an unauthorized manner.

H

20.6 Non Repudiation – The system limits a user’s ability to deny (repudiate) an electronic data exchange originated, received, or authorized by that user.

D

of 83


Yes, Additional


20.7 The system secures all modes of EHR data exchange through the use of data obfuscation and destination and source authentication and other standard security methods used to ensure appropriate security and privacy considerations.

D

20.8 The system manages attestation of information including the retention of the signature of attestation (or certificate of authenticity) associated with incoming or outgoing information.

D

20.9 The system enforces the applicable jurisdiction’s patient privacy rules as they apply to various parts of the EHR through the implementation of standard security mechanisms.

D

20.10 The system establishes patient/physician data element confidentiality. D

20.11 The system incorporates audit trails of each access to specific data. H

20.12 The system incorporates an audit trail for all system transactions including look-ups of patient data. A configurable report of all accesses to a patient’s record is available on patient demand.

H

20.13 Provides automatic analysis of audit trails and unauthorized access attempts. H

20.14 The operating systems required for the product, server and related systems operated hardware are B-2 or above rated H for more information see:

http://en.academic.ru/dic.nsf/enwiki/342389520.15 Discuss your approach to data/ information security, especially

with regards to Internet technologies.20.16 Is your security consistent with the latest industry approach for

encryption and authentication?

21 Clinical Decision Support

21.1 CDS should be built using national clinical data standards (LOINC, SNOMED, CPT, ICD9, ICD10, etc). H

21.2 The system offers prompts to support the adherence to care plans, guidelines, and protocols at the point of information capture and is capable of tracking compliance to such care plans, guidelines, and protocols (rules).

H X

of 83

http://en.academic.ru/dic.nsf/enwiki/3423895


Yes, Additional


21.3 The system identifies trends that may lead to significant problems and provide prompts for consideration. D

21.4 The system supports the integration of patient and family preferences into clinical decision support at all appropriate opportunities.

D

21.5 The system includes access to medical research and literature databases such as MEDLINE, JAMA, and others without logging out of the system. The system also allows for import of evidence-based CDS content from a third-party supplier (e.g. Zynx).

H

21.6 The system utilizes health data from all sections of the chart to provide decision support to providers. H

21.7 The system triggers alerts to providers when individual documented data indicates that critical interventions may be required.

H

21.8 The system automatically triggers an alert upon documentation of a diagnoses or event that requires reporting to outside agencies or public health authority, including the local public health department, Centers for Disease Control and Prevention (CDC), state health and mental hygiene departments, and state cancer registries.

H

21.9 Restrict the ability for a clinician to subscribe/unsubscribe from a rule, unless given proper authorization per security rights. H

21.10 The system automatically triggers an alert upon documentation of patient health data for a member of an existing medical registry or disease management program.

H

21.11 The system’s alert/reminder functions are driven by appropriate multi-disciplinary clinical guidelines. H

21.12 The system incorporates preventive medicine questionnaires to be completed by clinicians and if applicable, patients, during the encounter.

D

22 Cost Measuring / Quality Improvement / Reporting

of 83


Yes, Additional


22.1 The system has built-in mechanism/access to other systems to capture cost information. D

22.2 The system generates an evaluation survey (scheduled, on-demand or randomly selected) that will record patient satisfaction.

H

22.3 The system supports real-time or retrospective trending, analysis, and reporting of clinical, operational, demographic, or other user-specified data including current and future UDS reports, HEDIS reports, custom reports.

H

See http://bphc.hrsa.gov/uds/

22.4 When producing aggregate level reports, the system has the capability to drill down to the patient level. H

22.5 The system is capable of generating lists of patients by specific conditions to use for quality improvement, reduction of disparities, research or outreach

H X

22.6 The system produces clinician productivity/workload measures including RVU H

22.7 The system has the capability to perform automatic cost analysis for courses of drug/medication treatments. D

22.8 The system provides the capability for authorized users to develop volume statistics reports on user determined data fields. H

22.9 The system has the capability to produce population-based reports or studies based on flexible, end-user modifiable criteria. H

22.10 The system has the capability of producing scheduled and on demand case mix reports. D

22.11 The system allows customized reports or studies to be performed utilizing individual and group health data from the electronic record.

H

of 83

http://bphc.hrsa.gov/uds/


Yes, Additional


22.12 The system is capable of generating clinical reports or letters for schools, camps, sports physicals, other providers, or other entities requiring such reports/letters; and is capable of maintaining such a report/letter in the patient records. The system is capable of generating ancillary billing documents for submission to outside regulatory and compliance agencies (e.g. PM160).

H

22.13 The system will provide support for third-party report writing products. H

22.14 The system supports real-time or retrospective trending, analysis, and reporting of aggregate numerator and denominator of clinical quality measures, including the CQMs of meaningful use (MU) to CMS, the States, or other regulatory entities, through means that they require (e.g., attestation, electronic submission).

H X

Ref:http://healthit.hhs.gov/portal/server.pt?open=512&objID=1325&parentname=CommunityPage&parentid=1&mode=2

23 Chronic Disease Management / Population Health

23.1 The system provides support for the management of populations of patients that share diagnoses, problems, demographic characteristics, etc.

H

23.2 The system supports disease management registries by:

23.2.1 Allowing patient tracking and follow-up based on user-defined diagnoses H

23.2.2 Integrating all patient information within the system H

23.2.3 Providing a longitudinal view of the patient medical history H

23.2.4 Providing a longitudinal view of the patient’s demographic and social history, including occupation, industry worked in, and residential address

D

23.2.5 Providing intuitive access to patient treatments and outcomes H

of 83

http://healthit.hhs.gov/portal/server.pt?open=512&objID=1325&parentname=CommunityPage&parentid=1&mode=2




Yes, Additional


23.3 The system is capable of submitting electronically syndromic surveillance data to public health agencies in accordance with applicable law and practice.

H X

23.4 The system automatically identifies all high-risk patients and notifies clinical staff for preventive care. H

23.5 The system utilizes user-authored and/or third-party developed clinical guidelines for disease and registry management. H

23.6 The system tracks / provides reminders and validates care process against clinical practice guidelines. H

23.7 The system generates follow-up letters to physicians, consultants, external sources, and patients based on a variety of parameters such as date, time since last event, etc. for the purpose of collecting health data and functional status for updating the patient’s record.

H

23.8 Print patient reminder letters or recall notices with pertinent information. H

23.9 User-configurable, automated printing of health maintenance reminder letters. H

of 83


Yes, Additional


23.10 At a minimum, the system is able to generate a variety of reports based on performance measures identified by the Physician Consortium for Performance Improvement (AMA/Consortium), the Centers for Medicare & Medicaid Services (CMS), and the National Committee for Quality Assurance (NCQA) for chronic diseases including diabetes, coronary artery disease, heart failure, behavioral health, hypertension, osteoarthritis, and asthma, as well as for prenatal care and several preventive services including immunizations, lead testing, tobacco use cessation, and problem drinking. Information on these measures can be found at: http://www.ama-assn.org/ama/pub/category/4837.html. The system follows measures approved by NQF (national quality form) and prompted by the AQA (ambulatory quality alliance) as well as those identified by the HRSA’s Health Disparities Collaborative, see http://www.healthdisparities.net/ .

H

23.11 The system links Disease Management functions to all other sections of the EHR. D

24 Consents, Authorizations, and Directives

24.1 The system allows for or provides a mechanism for patients to electronically access their health information (including lab results, problem list, medication lists, and medication allergies) within four business days of the information being available to the EP, subject to the EP’s discretion to withhold certain information.

H X

24.2 The system has the capability for a patient or responsible party (e.g., parent, guardian) to sign consent electronically. H

24.3 The system has the capability to restrict access or sharing data electronically with other systems based on consents/authorizations provided by patient or guardian subject to national or jurisdictional requirements.

H

of 83

http://www.healthdisparities.net/

http://www.ama-assn.org/ama/pub/category/4837.html


Yes, Additional


24.4 The system has the capability for the user to create and maintain consents and authorizations when required in the patient’s preferred language

H

24.5 The systems captures, maintains, and provides access to and print a copy of patient advance directives. D

25 Technical Underpinnings

25.1 Support flexible search criteria during the patient identification process: for example, partial name, Soundex, medical record number, account number, age, date of birth, sex, combinations of data. Please comment on other types of search options.

H

25.2 Support an enterprise number as well as separate, multiple medical record numbers H

25.3 Support different numbering schemes to accommodate each facility’s requirements. H

25.4 Functionality disallows occurrence of duplication medical record numbers and duplicate encounter numbers. H

25.5 Provide embedded weighted algorithm to assist with the identification of potential duplicate accounts. Please describe. H

25.6 Provide merge capability for 2 records for same person (e.g. duplicates, erroneous registration) H

25.7 Provide capability to un-merge records incorrectly linked. H

25.8 Support collection of user defined data. Please indicate limitations. H

25.9 Generate a report indicating patients with multiple medical record numbers. H

25.10 Support for receiving HL7 merge transactions (ex. A18, A30,A34, etc.). H

25.11 The system auto-populates user defined data fields with patient demographics at the time of order or request. H

of 83


Yes, Additional


25.12 The system is scalable (i.e. has the capability to support additional storage requirements without major investments in hardware other than disk space)

H

25.13 The system incorporates a consistent user interface for data entry independent of the platform. H

25.14 The system will be accessible and available to all authorized users 99.5% of the time. H

25.15 The system supports indexed document scanning. H

25.16 The system supports an immediate response time (0.5 – 1.0) seconds 90% of the time. H

25.17 The system supports an instantaneous response time (0.1 – 0.2 seconds 80% of the time. H

25.18 The system incorporates extensive, secure telecommunications capabilities that link staff and clinicians from remote locations to the central site.

H

25.19 The system supports an industry standard locking mechanism to prevent unauthorized updates. H

25.20 The system supports and implements system redundancy / fault tolerance for 100% availability. H

25.21 The system logs all transactions processing and archiving. H

25.22 The system alerts simultaneous users of each other’s presence in the same record. H

25.23 How does the EMR/EHR prevent duplicate encounters and duplicate medical records from occurring? Please describe in detail.

of 83


Yes, Additional


25.24 Provide a detailed explanation of eSignature architecture and related operational flow. What controls are in place? Does the application support a secondary password/pin entry at time of signature? Does the application support co-signatures and other types of supervisory review/approval? How does the application support and track multiple provider entries for various components of documentation? Be specific as to how eSignature supports the workflow in an academic facility with significant resident and student activity.

26 Clinical IT Data Dictionary

26.1 The system is structured to an expandable EHR through the use of user defined fields. H

26.2 Provides attributes for each data element; supports all data types. H

26.3 Supports static/dynamic data element relationship. H

26.4 The system documentation includes a list of all data elements contained within the system along with their characteristics and pertinent information (metadata) needed for use by ad-hoc report writing and/or for mapping to third party report-writing software or interfaces.

H

27 Input Mechanisms

27.1 The system supports a full range of input technologies. H

27.2 Input protocol is easy/fast, intuitive input interface. H

27.3 Support a variety of point of care and input devices, specifically:

27.3.1 Signature Capture H

of 83


Yes, Additional


27.3.2 Hand held/portable - Radio Frequency H

27.3.3 Laptop H

27.3.4 Touch Screen H

27.3.5 Pen H

27.3.6 Voice Recognition H

27.3.7 Keyboard/Mouse H

27.3.8 Mobile Devices H

27.3.9 iPad H

27.3.10 iPad App H

27.4 The system allows easy access to existing, previously captured data for information purposes or for copying data. H

27.5 The system has the ability to allow inclusion of free text as well as the capture of discrete data in accordance with site preferences and site-specific system configuration.

H

27.6 For a patient participating in a group visit, the system has the ability to create a note that is shared by all patients in the group. D

28 Ergonomic Presentation

28.1 The system places emphasis on user friendliness. H

of 83


Yes, Additional


28.2 The system incorporates a consistent presentation of information across the entire system. H

28.3 The system incorporates visual cues. H

28.4 The system provides consistent formatting to aid users in finding information. H

29 Billing

29.1 The system meets RBRVS/E&M documentation and coding guidelines. H

29.2 The system provides a bidirectional interface a variety of information systems such as practice management, laboratory, state immunization registry, etc.

H

29.3 The system provides support to the provider on E & M coding based on documentation from the current visit. H

30 System Infrastructure & Scalability 30.1 Hardware configuration operates on industry standard Intel

servers such as IBM or HP. H

30.2 Operating system environment supports, the following minimum system requirements, Microsoft Windows XP Professional and Windows 7 and Microsoft Windows 2008 Server.

H

30.3 System can be configured in a high availability mode that continues operation in the event of specific component failures. Describe system capabilities in this context.

H

30.4 Use clustering software to load balance and demonstrate quick, automatic failover across all servers, if multiple servers are required or recommended.

H

30.5 Support a web-based interface. D

30.6 Support Citrix XenApp and XenDesktop. D

of 83


Yes, Additional


30.7 Recommended hardware platform provides capability for hot swappable, mirrored/raided disk drives. H

30.8 Support the ability to conduct routine backup procedures without the users having to be off the system. H

30.9 System is based on a relational database management system. H30.10 Data elements can be viewed, printed, interfaced, updated,

reported on and/or listed as needed. H

30.11 Provide Common Reporting Tools and Analytics that are compatible with recognized, industry standard reporting tools such as Microsoft SQL Server Reporting Services, Crystal Reporting.

H

30.12 Vendor provides load testing tools and load testing as part of their implementation. D

30.13 System is scalable to accommodate additional utilization, users, transactions and/or additional local/remote sites. H

30.14 Support multiple environments including test, production, distributed, reporting, mirror and training. D

30.15 Provide a data dictionary. H30.16 Database tools are provided to allow end-user access for queries

and extraction or output of data into other file formats. H

30.17 Application and interface servers can be implemented as virtual machines under VMWare. H

30.18 Management of client/PC software is centrally managed. D30.19 Application can be monitored via common enterprise

monitoring systems. H

30.20 Application provides an alerting and monitoring utility. D

30.21 Application exposes data via Web Services. D

30.22 Support the use of industry standard interface engines. H

30.23 Interface engine runs as a system service. H

of 83


Yes, Additional


30.24 Support standard HL7 interfaces. H

30.25 Support industry standards such as DICOM and XML. H30.26 Interface with legacy systems, departmental systems, repository

systems, foreign systems, modalities and devices. D

30.27 Users can view a display of archived transactions and audit file as well as the transactions as they are being processed. D

30.28 Includes flexible table features that enable a user to build tables for the translation of data. D

30.29 Support the ability to conditionally map data and the ability to compare and group condition tests. H

30.30 Provide a custom adapter development kit such as COM or API, making it possible for a user to create utilities and applications that can communicate directly.

D

30.31 The generation of alert messages can be configured by the time of day and day of week, for each interface via user-defined peak, off-peak and scheduled downtimes.

D

30.32 Alert messages can be sent to any device including, pagers and printers as well as to other interfaces. Alerts can also be configured based on change of interface status, idle time and excessive transaction backlog.

H

30.33 Support data mapping and conditional routing. D30.34 The following data types are supported: ASCII, BLOB,

EBCDIC, hex16, hex32, printable, raw, signed binary and unsigned binary.

H

30.35 Error Monitoring provides an alert subsystem which generates alert messages that are stored and viewable online and can be routed via various mechanisms such as e-mail and pagers.

H

30.36 Include a variety of monitoring and troubleshooting tools that allow for the immediate identification and correction of any problem you may encounter. These intuitive tools are easy to access via “point and click” or “drag and drop” features.

H

of 83


Yes, Additional


30.37 A field can easily be setup such that some values are translated and others are passed through without translation. H

30.38 Templates exist for various protocol, connections types and interface ports. D

30.39 Holds message waiting to be processed in memory and writes them to disk. Each message is flagged with a status that indicates whether it has been processed and received by the destination system.

H

30.40 Provide templates that allow users to assign attributes to a particular definition then copy these attributes for other similar builds are provided.

D

30.41 Please explain how your proposed system(s) would interface/ integrate with existing clinical applications from NTT DATA, i2i Systems, Bottomline Technologies, ExitCare.

30.42 Please describe the process in which disputes over the interface between your solution and the Practice Management System application are resolved.

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

30.44 Discuss any limitations/ issues regarding your willingness or ability to interface / integrate your product with foreign automated systems.

30.45 Describe the operating system, hardware/server platform, and database, programming language that supports your proposed product.

30.46 Has any client implemented the System in a virtualized environment?

30.47 Does your solution employ a true Service Oriented Architecture (SOA)? Explain.

30.48 In the context of a true SOA, explain how your data and service modeling is done and what advantages it provides to the customer.

of 83


Yes, Additional


30.49 Describe the vendor’s approach to data integrity and redundancy.

30.50 Describe the vendor’s approach and tools for backup, recovery and SAN/NAS recommendations.

30.51 Detail the number of environments that are recommended for implementation and their purposes, ex. Test, Development, QA, Production?

30.52 Describe the process of environment management and migrating from one environment to another.

30.53 What is the source code for the application written in?30.54 What database architecture does your solution use? Please

include version.30.55 How many application releases per year does the vendor

provide?30.56 How are minor and major releases communicated and provided

to the client?30.57 Detail the printing process for the application.30.58 Provide your definition and vision of interoperability and how

you are incorporating interoperability within your solutions.30.59 Describe your method for establishing HL7 connectivity as well

as the version you support.30.60 Describe your overall design approach to developing, testing,

implementing and upgrading system interfaces.30.61 Describe how you support systems without standard interfaces.30.62 What tools does your system provide to allow monitoring and

guaranteed delivery of your interfaces?30.63 What interface engines have your existing clients used?30.64 Describe the auditing capabilities to verify the counts of records

sent or received by your system.30.65 How many levels of software releases are supported for the

proposed product? of 83


Yes, Additional


30.66 What backup schedule do you recommend?30.67 Discuss the data archiving and restoring from archive within all

applications of the software.30.68 What are the capabilities in restoring from archive?30.69 Please provide a Systems Environment Specification that

outlines the server, networking and communication requirement for your product.

30.70 Please provide a copy of your Quality Assurance Guidelines for new software releases.

31 Network Capabilities

31.1 Supports Wireless protocols such as 802.11a-b-g-n. H31.2 Critical data (security and authentication data) is passed

between various layers using at least 128 bit encryption. The browser/server communication can also be set using standard SSL based authentication.

H

31.3 Capable of using IP and the standard network protocol. H31.4 Support secure TCP/IP remote access for users (e.g., PPTP,

SSL, Kerberos, etc.). H

31.5 Required network devices can be managed from a central location. D

31.6 Support Network Load Balancing to offer higher throughput for increased user load. H

31.7 Support Layer 3 switching H

31.8 Has the solution been implemented within an MPLS Network? H

31.9 If “Yes” describe any challenges or workarounds implemented.

31.10 Please describe your LAN/WAN network requirements.

of 83


Yes, Additional


31.11 On the Wide Area Network, what is the minimum bandwidth requirement?

31.12 Describe in detail the remote access methods you currently support for your application and how you would support devices at remote locations.

31.13 What cellular protocols does the system support?

31.14 What are the throughput response time requirements?

31.15 What encryption standard does your solution utilize?

32 Security

32.1 Support Role Based Access. H

32.2 Support task-based and object-based user authorization profiles. H32.3 Provide an audit trail that can be used to identify transactions or

data accesses that have been performed by:32.3.1 Function H

32.3.2 Patient H

32.3.3 User H

32.3.4 Terminal D

32.4 Provide field level audit log reporting features. H32.5 Log all unsuccessful logons and lock out users after a certain

number of unsuccessful attempts as defined by the customer. H

32.6 Provide a “time out” feature that automatically signs off a user if a workstation has been left unattended for a user-defined time period. Application recognizes key press as evidence of application activity.

H

32.7 Supports authentication via LDAP. D

32.8 Report on access levels by patient, user, and location. H of 83


Yes, Additional


32.9 Provide functions to restrict access to specific patient records for individual users. H

32.10 Permit creation of temporary user accounts with specific expiration timeframes. D

32.11 Permit the security administrator to specify that User IDs and passwords must contain a combination of alphabetic, numeric, and special characters.

H

32.12 Permit the security administrator to specify that passwords must adhere to strong password guidelines. H

32.13 Permit the security administrator to specify a minimum password length that will be enforced by the system. H

32.14 Force a user to select a password at initial sign-on and when the password has been reset. H

32.15 Prohibit the reuse of User IDs and passwords per user based upon security administrator controllable setting. H

32.16 Support the encryption of the password file and password information. H

32.17 Permit the security administrator to set events that are considered security violations as well as provide real-time notification of any violations.

H

32.18 Proposed solution provides at least 128-bit encryption over the Internet and intranet as a standard feature (https) H

32.19 Proposed solution provides full user activity audit trail H32.20 Discuss the system’s ability to define and control user and role

profiles within and across facilities.32.21 Describe the system user name and password structure and the

ability to enforce it.32.22 Discuss the authentication process including encryption and

wireless devices.32.23 How does your system support single sign-on?32.24 Does the system provide audit logs/error logs to detect

unauthorized access or activity? of 83


Yes, Additional


32.25 Describe the system components in place that support a user/ client’s adherence to the HIPAA security regulations.

PRACTICE MANAGEMENT

33 General 33.1 Support an Enterprise Master Patient Index (EMPI) across the

continuum of care: acute care, ambulatory, physician office, SNF, home health, and ancillary services.

H

33.2 Identify potential duplicates and alerts the user of a potential duplicate during assignment of a new medical record number. H

33.3 Flag deceased patients and integrates information with registration and clinical modules. H

33.4 Able to add new patients via registration/ admission or scheduling process. H

33.5 Able to add new patients or revise demographic data for existing patients outside of registration/admission process. H

33.6 Support alternative name/alias processing. D33.7 Provide on-line inquiry and retrieval capabilities to the EMPI

history for an unlimited number of years. D

33.8 Ability to write ad-hoc reports on all EMPI data fields with a standard report writer application. H

33.9 Ability to provide real-time access to the EMPI from other, interfaced systems. Please indicate interface standards supported.

H

33.10 Support for sending HL7 merge transactions (ex. A18, A30,A34, etc.). H

33.11 Ability to audit EMPI activity. H33.12 Ability to notify all systems when new patients are added or

when demographics are updated by another system. H

33.13 On demand patient statements at time of service. D

of 83


Yes, Additional


33.14 Electronic insurance eligibility checking. H33.15 Ability to calculate anticipated patient responsibility at

scheduling. H

33.16 Automated tasks to remind physicians of missing charges and complete reconciliation features to the Practice Management System

D

34 Scheduling 34.1 Incorporate user-defined, knowledge-based scheduling

capabilities to ensure the medically appropriate sequence and timeframes to schedule selected medical services (e.g., pre-defined duration between treatment appointments, time allotted by treatment defined in physician order).

H

34.2 Identifies available appointment sequence options, e.g., treatment followed by physician visit then lab, and allows scheduler to select preferred option

H

34.3 User-defined number of appointment types/treatments provided during selected period with override capability. H

34.4 Default template with rules that prompts for appropriate data (for example, appointment duration, pre and post procedure time, set-up requirements, prerequisites).

H

34.5 User-defined rule sets for prompts based on diagnosis/testing (for example, mammogram under 25). H

34.6 Schedule patient appointments/treatments online by department, by provider, by procedure/treatment, by resource and room. D

34.7 Automatically identify next available time slot by individual provider and specialty. H

34.8 Schedule multiple patients with a single provider or multiple providers. D

34.9 Recurring clinic/therapy schedules, for example, every other week, every other weekday, and specific dates within a month. H

34.10 Schedule meeting rooms, specify room setup, specify equipment /flip charts, etc. D

of 83


Yes, Additional


34.11 On-line warning when a patient has been scheduled for multiple appointments/procedures on the same or overlapping date and time with capability to override warning message.

D

34.12 Creates alert if there is a required pre-payment for a pending appointment H

34.13 Creates alert if insurance verification required H34.14 Creates reminders regarding unresolved prior balance, required

pre-payment H

34.15 Move patients between providers, time slots, days, therapists, etc. H

34.16 “Ticker” file for follow-up requirements e.g., reminders. D

34.17 Track “no shows,” no show status and cancelled reason. H34.18 Flag patients with a history of no-shows. Print reports of no

show patients. D

34.19 Tracks cancelled appointments with a “reason for cancellation,” and print a Cancelled Appointments Report. H

34.20 Track on-call schedules with rules (for example, days off, consecutive weeks) D

34.21 Overlapping of resources for group visit and group assignments to therapist. D

34.22 Accommodate changes in appointment dates both for individual patients and for identified groups of patients (for example, reschedule an entire day's patient load) without user re-entering all patient information.

H

34.23 Copy/paste into template when moving entire schedule. D34.24 Block the same slot over many days or weeks without requiring

user to block the slot for each individual day, including non-consecutive days.

H

34.25 Offsite physician offices access the scheduling system for displaying schedules. D

of 83


Yes, Additional


34.26 Download schedules to e-mail. D34.27 Generate list of all patients scheduled from current date through

user-defined date (for example, next two weeks) and have report emailed directly to staff workstations.

D

34.28 Print appointment/facility documents, confirmation and re-schedule letters. D

34.29 Includes interface with Interactive Voice Response (IVR) software for callback to remind patients of upcoming appointments. i.e. Phone Tree

H

34.30 A unique Provider ID can have multiple site templates on same day. H

34.31 Describe how your system manages “person” data collection. Describe person management as it relates to patient, guarantor, or relative roles. Address how these roles are linked to encounters.

34.32 Provide an overview of the enterprise scheduling features, including appointment scheduling, conflict checking, rules, patient preferences, auditing, and report features. Describe the ability of the system to produce common metrics (productivity, access, continuity). Describe patient empanelment functions.

34.33 Describe any medical necessity checking features.34.34 Describe how to define appointments or activities and

associated resources. Describe how to define for each resource, where the activity can be performed and other rules regarding when the activity can be scheduled based on the specific resources’ availability.

34.35 Describe overbooking capabilities.

34.36 Describe any alerts or warnings.

34.37 Describe report writing capabilities and standard reports.

35 Billing of 83


Yes, Additional


35.1 Provide a flexible schedule for the generation of patient bills based on patient type and payer/payer health plan or medical service.

H

35.2 Provide for several customer-defined bill hold criteria by patient type and insurance type including, missing data, diagnosis. H

35.3 Continually validate that all necessary information has been entered based on payer/ payer health plan billing requirements. Provide worklists to alerts for missing information.

H

35.4 Provide for the display of detail on the account and the patient statement including: a. Source of payment (i.e.: Insurance payment, or Blue Cross payment) b. Date of service to which the payment was applied c. Contractual allowances or not-allowed amount d. Co-payment amount e. Co-insurance amount

H

35.5 Provide for UB-04 and 1500 CMS billing forms. H35.6 Support electronic billing of third-party payers with automatic

verification of transmittals, retransmission of corrected transmittals, and cancellation of prior transmittals.

H

35.6.1 Support the transmission of HL7 messages to hospital’s existing RCM product for inclusion in the GL.

35.7 What types of claims scrubbing and transport tools are available with your system?

35.8 Describe the process for handling Primary, Straddle, Interim, Zero Balance, Rebills, Serial Bills or Demand Bills?

35.9 Describe how the user maintains claim edits.

35.10 How does the system produce a point of service bill?

36 Charging 36.1 Provide an enterprise charge definition and pricing master file

for use by all facilities and locations with on-line access for query and updating.

H

of 83


Yes, Additional


36.2 Allow the entry of multiple prices for individual Charge Master File entries with an effective date for the specific price, maintaining an accessible history of price changes and dates.

H

36.3 Ability to “explode” bundled charges into individual components for revenue and statistical reporting while maintaining a single line item for billing or detailed line items.

H

36.4 What type of online editing is available when charges are entered?

36.5 Describe options for time-based charging.36.6 Describe how the system supports online and batch charge

entry.37 Reimbursement 37.1 A contract engine embedded in the system that calculates

reimbursement, adjustments, and identified underpayments in real-time without need for an interface to another system.

H

37.2 Contracting Functions37.3 Provide a contract file, which includes payer information

including addresses, contacts, expiration dates etc. H

37.4 Sophisticated criteria for grouping together like services for a reimbursement calculation H

37.5 Contract terms are grouped into contract packages that apply to specific encounters e.g. maternity, outpatient surgery, etc. H

37.6 Provide comprehensive reimbursement calculations H

37.7 Describe your contract management capabilities.37.8 What types of reimbursement calculations does your system

provide?37.9 How does your system support denial management and the

appeal process?38 Account Management

of 83


Yes, Additional


38.1 Describe the system’s ability to transparently accept an account number and a medical record number generated by another hospital information system as the main source of ADT.

H

38.2 Allow the identification of receivables based on various criteria including: patient or guarantor name or number, phonetic name search, address, phone number, driver’s license, medical record number, social security number, date of birth, etc

H

38.3 Allow the definition of institutional accounts against which charges for multiple patients can be posted. H

39 Collections 39.1 Support the operation of a Central Billing Office serving

multiple facilities and office locations with the ability to consolidate functions while maintaining separate accounting buckets.

H

39.2 Support the operation of internal and external secondary business offices for collection of receivables. This could include external collection agencies.

H

39.3 Ability to define and monitor special payment arrangements by individual account. D

39.4 Produce consolidated patient statements by guarantor showing all related patient or family accounts. H

39.5 Support automatic and on-demand generation of customer-defined collection letters based on account type and aging criteria to pull in patient and account information such as: a. Patient name (separate the name into first, last, middle initial, title) b. Encounter number c. Date of Service d. Insurance payer e. Total billed

H

39.6 Electronically accept claim denials and perform tracking and appeal processing. H

40 Payments 40.1 Support electronic remittance for Medicare, Medi-cal and

selected insurance carrier. H

of 83


Yes, Additional


40.2 Enable both online and batch posting of payment and adjustment transactions with adequate audit trail to ensure cash controls.

H

40.3 Support multiple point-of-service cashiering sites with separate cash draws, receipts, and balancing functions. H

40.4 Apply payments to an account or line item level. H

41 Reporting 41.1 Generate enterprise reports for the health system while

maintaining ability to drill down to facility, departmental information, and provider.

H

41.2 Provide the ability to store all reports, bills and statements in an integrated document imaging repository. D

41.3 Provide AR reports by a. Service/Location b. Providers c. Patient Type d. Insurance Payer/Health plan e. Insurance Type f. Type of Account g. Date of Service h. Age of Account i. Balance Range

H

41.4 Provide for generation of an A/R aging report sorted by delinquency period by specific information. H

41.5 Provide friendly report writer tool and embedded analytics. H

42 Transaction Handling 42.1 Compliant with HIPAA 1510 requirements for transactional

security H

42.2 Compliant with HIPAA 5010 requirements H

42.3 Handle HL7 batch, real time communication H

42.4 Handle EDI transaction via modem, ftp transfer H

42.5 Maintains audit logs of user access, data transferred H

PATIENT CENTERED – Patient Portal

of 83


Yes, Additional


43 Patient Scheduling

43.1 Supports self-scheduling and registration via the Web? H43.2 Supports appointment “hold” requests until the physician office

review and subsequent approval/denial. H

43.3 Integrates fully the rules and clinical content between portal and central scheduling system. H

43.4 Offers self scheduling 24/7. D

44 Electronic Payment Posting 44.1 Supports an on-line payment process, i.e. patients can pay on

their accounts electronically. H

44.2 Supports electronic patient bill payment by portal and reflects patient’s bill in main HIS or PPM patient accounting files. H

44.3 Permits scheduling of single or recurring payments. H

44.4 Supports patient posting of electronic payments:

44.4.1 From any Internet location D

44.4.2 At a Kiosk desk D

44.5 Enables patient review of payment status and history. H

44.6 Sends due date reminders and e-mail notifications to patient. H44.7 Supports Interactive Voice Response (IVR) payment for those

without Web access. Supports voice response payments accepted from patients using a telephone, not a PC.

D

44.8 Generates standard reports for auditing and settlement. H

45 Electronic Statements 45.1 Provides online presentation of patient/guarantor statements,

letters, via the health provider’s website. H

of 83


Yes, Additional


45.2 Supports flexible statement/collection letter design in an easy-to-read format. H

45.3 Notifies and directs patient to the Web site to view their statements and make payments using their credit card or bank account.

D

45.4 Supports customizable electronic statements with health system’s web content standards, logo; large, user-defined text areas; multi-color. Please address other options in Comments.

D

45.5 Provides identical image of printed paper statement. H

45.6 Integrates with electronic payment solution. H

46 Demographics 46.1 Supports care providers viewing and printing patient face

sheets.46.2 Supports patients remote update and verification of

demographics and payor information.46.3 Describe how your system supports self-scheduling by the

patient via web portal.46.4 Describe the options for custom statements and collection letter.46.5 How do electronic statements work in conjunction with

electronic payments?46.6 What is the process for patients to pay bills online?46.7 Describe how the electronic patient payment solution reduces

production and postage costs of bills, invoices, notices, and account statements.

46.8 What payment types are supported e.g. credit card, cash, bank account, paypal?

47 Patient Health Portal 47.1 Web based application providing secure anywhere/anytime

remote access to care providers and their patients. H

of 83


Yes, Additional


47.2 GUI front-end application that is user friendly and is easy to navigate. H

47.3 Secure communication between patients and care givers. H47.4 Provide secure messaging capabilities including text, email,

pager, etc. H

47.5 Ability to integrate with external healthcare providers for participating in a health information exchange environment. H

47.6 Ability to electronically view and send data to immunization and health registries. H

47.7 Ability to display data from multiple disparate systems regardless of vendor. H

47.8 Ability to display patient data as discreet data (ex. laboratory results) and images (ex. XRAY, EKG). H

47.9 Compatible with portable devices such as tablets and smart phones. H

48 Provider/Caregiver 48.1 Ability to replace multiple disparate systems view of patient

clinical data for the care provider. H

48.2 Multiple options for displaying a list of patients (i.e. single physician, group practice, covering physician). Ability to limit exposed census by individual panel, group, department/facility, enterprise.

H

48.3 Ability to electronically receive, view, and process patient requests for prescription requests and refills. H

48.4 Single sign on capabilities. D

48.5 Provide an electronic graphical view of patient clinical data. H

48.6 Electronically capture and manage the patient problem list. H48.7 Ability to electronically notify the care provider of abnormal

and/or critical values when logged in viewing results or via text, email, pager, etc.

D

of 83


Yes, Additional


48.8 Link to external websites through the portal for viewing educational or research materials. H

48.9 Ability to electronically edit and/or sign transcribed documents. D48.10 Provides care providers with a directory of all healthcare

provider information that can be used for electronic communications.

H

48.11 Secure messaging and “inbox” functionality that can be used for task assignment and communication. H

48.12 Expert rules and alerts are built into the application. D

48.13 The system can create and display a CCD/CCR. H

48.14 Patient visit checklists customizable by physician. H

49 Patient/Family Member 49.1 Educational materials and office visit notes can be sent

electronically to the patient and/or a designated family member. H

49.2 Ability for the patient or designated family member to query for lab, radiology and other diagnostic testing results. H

49.3 Ability to receive reminders from the doctor’s office about the next immunization or lab due date. H

49.4 Provide a secure portal with encryption for patients to provide SF-36 (Functional Status Survey), health risk or H&P information to providers.

H

49.5 Provides patients with a directory of healthcare providers contact information. D

49.6 Patients are able to manage their personal health record by updating information such as allergies, medication list, flu shots, etc.

H

49.7 Do you have integration to an eHealth or patient on-line solution allowing patient populations to verify their medical record, access billing status, review tests results and communicate to the physician?

D

of 83


Yes, Additional


49.8 Describe how information from a Personal Health Record (PHR) is automatically sent to a provider’s EHR.

49.9 Describe how a provider can communicate with a patient through the use of a portal, e.g. can patient education material be distributed through the portal?

49.10 Describe how security access is granted for individual physicians covering patients for situations such as within their physician group or consults.

49.11 Describe where the database will reside, the work effort involved to build it, and ongoing support of the application. Describe hosting models that are available with this solution.

of 83

1 - corporate qualifications - san joaquin county, … · web viewthe system displays a “vaccine...

Documents