Get documents about "Printable Daily Routine Schedules - Excel
Description
Printable Daily Routine Schedules document sample
Document Sample
PMS Functionality
Functionality Vendor's ability to meet requirement
HIPPA compliant/ready
User defined alerts
Set reminders
Master appointment schedule is easy to modify
Support centralized and decentralized scheduling
Ability to schedule one year in advance
Ability to export the reason code for visit into the EMR daily schedule screen
Schedule can be viewed on PDA
Complete audit trail for changes/cancellations
Waitlist is supported
Event chaining of multiple events with configurable wait times supported
Unlimited over-booking with permission
Ability to tracks no shows
Patient information can be viewed within the appointment view such as past
due balance, # of referrals, insurances.
Notes are categorized by type
Eligibility, referral and claim status can be handled in real-time
Capture image of drivers license and insurance card
Capture a picture of patient
Letters and forms are generated using MS Word, Adobe Acrobat, Google
Documents, etc.
Vendor provides task management capabilities
System maintains multiple fee schedules
System supports electronic claims submission
System supports electronic remittance
Posting functionality
System automatically shifts encounter balances from primary insurance to
secondary, tertiary and patient responsibility
Create and receive 837 – HCFA 1500
Create and receive 835 – electronic remittance advice
Ability to upload most recent medicare fee schedule
Accounts Receivable Reports included in the system and are exportable to
excel
Proposed Pricing
[insert vendor name]
Software - license, Time ASP subs. ASP hosting Client Server Support Support
Metric Quantity Extended Price
subscription, hosting fee Period unit price unit price unit price (1st year) (post year 1)
Provider EHR license(s)
Provider PMS license(s)
discount for
combined EHR and PMS
Mid-level EHR license(s)
PMS license(s)
Mid-level discount for
combined EHR and PMS
Part-time EHR license(s)
PMS license(s)
Part-time discount for
combined EHR and PMS
Practice EHR license(s)
Practice PMS license(s)
Part-time discount for
combined EHR and PMS
Total software fees $ -
One-time implementation Time Support/Fee Support/Fee
Metric Quantity Unit Price Extended Price
fees Period (1st year) (post year 1)
Fee for additional modules -
Software
installation/configuration -
Data migration -
Template design/development -
Forms design/development -
Knowledge or clinical content
development -
Dictation install/configuration -
On-site training -
Remote training -
Vendor-site training -
Scanning (one year of
records) -
Scanning (additional years of
records) -
Daily fee for technical services
(implementation, network, etc) -
Daily fee for project
management -
Daily fee for on-site trainer -
Daily fee for product specialist -
Daily fee for billing specialist -
Daily fee for other (specify) -
Total implementation fees $ -
2
Proposed Pricing
[insert vendor name]
Time Support/Fee Support/Fee
Interface fees Metric Period Quantity Unit Price (1st year) (post year 1) Extended Price
Commercial lab/rad -
Hospital lab/rad -
SHIN-NY compliant CCD -
Transcription -
Practice management system
Other
Total Interface fees $ -
Other software and service Time Support/Fee Support/Fee
fees Metric Period Quantity Unit Price (1st year) (post year 1) Extended Price
Clearinghouse -
Surescripts/RxHub -
Document
Management/Scanning -
Template and Form Builder -
Dictation -
Decision support systems -
Patient Education -
Diagnosis Database ICD-9 -
Procedure Database CPT 4 -
Drug Database -
Formulary Updates -
Drug Utilization Review -
Optical Character Recognition
Software (OCR) -
Viewing Software (Adobe,
etc.) -
Reporting/Report Writer
(Crystal, other)
Forms Libraries
Fax Software
Claims Submission Support
(CCI, LMRP)
Medical Manager
Docutrack
Docutrack
Total other software and
service fees $ -
3
Proposed Pricing
[insert vendor name]
Time Support/Fee Support/Fee
Hardware fees Metric Period Quantity Unit Price (1st year) (post year 1) Extended Price
Server -
Desktop -
Laptop -
Tablet -
PDA -
Router -
Wireless nodes -
Scanners -
Printers -
Total hardware fees $ -
4
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
1.1 Provide comprehensive benefit EHR will have ability to conduct
eligibility (health plan, Medicaid,
Medicare, etc.) information, to
eligibility checking for all
commercial health plans and R R V1
include managed care Medicaid from within the
1.2 Appropriate clinical staff should The system shall allow
document and/or update
patient identifying and financial
appropriate clinical staff to
document and/or update R V1
information, and verify patient identifying and financial
1.3 Appropriate clinical staff can The system can print out
print out medication and
diagnosis list and other
medical summary including
medication and diagnosis list. R V1
applicable information for
2.1 Clinical staff can document EHR will have the ability to
patient medication history
electronically from patient.
perform basic clinical
documentation, including R V1
Clinician shall confirm previous medication history. Current,
2.2 The system shall allow the EHR will have the ability to
clinician to update the
management plan. Clinician
perform basic clinical
documentation. The system R R V1
shall confirm previous shall be able to document a
2.3 Specialist can document EHR will have the ability to
consult note, recommendations
and clearance.
perform basic clinical
documentation features. The R V1
system can document a consult
2.4 Appropriate clinical staff can EHR will have the ability to
document Chief Complaint, VS,
new history, MD visits, problem
perform basic clinical
documentation features. R R V1
list, med list electronically from Appropriate clinical staff can
2.5 Clinical staffs are able to The system will allow
document detailed
HPI/ROS/FH/Medical
appropriate clinical staff to
electronically record detailed R V1
Hx/Surgical Hx/Social Hx and history of present illness (HPI),
2.6 Appropriate clinical staffs are The system supports clinical
able to document, review and
update patient problems,
list items for problems,
medications, medication R V1
medications, medication reconciliation, allergies/ADR,
2.7 The system shall allow the The system shall have patient
education of the patient and
referral to other patient
education material available
within the application either R V1
educators (e.g., dietitian, from the application itself or
2.8 The system shall allow the The system shall have basic
complete physical assessment,
including all necessary
template documentation
functionality for standardized R V1
examinations based on the documentation with consistent
3.11 The system shall have the The system shall allow export
capability to receive and store
measure information, including
of standardized patient level
data to support the third party R V1
general measure information, calculation of quality measures,
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
3.12 As appropriate, pseudonymize As appropriate, pseudonymize
or de-identify the patient-level
data which are being readied
or de-identify patient-level data
prior to transmission to the R V1
for transmission. HIE.
4.2 The EHR is able to retrieve The EHR is able to retrieve
(manual or automatic)
aggregate clinical data to
(manual or automatic)
aggregate clinical data to R R V1
review. System may have the review. The system shall have
5.1 Quality measurement. The The system will allow additional
system shall allow for frequent
updates to the list of required
required data elements to be
added to the system based on R V1
data elements and numerator / enhancements to measures.
5.2 The system shall populate the The system shall populate the
EHR so that when a patient
history of smoking is
EHR so that when a patient
history of smoking is R V1
documented, the indicator to documented, the indicator to
5.3 The system shall facilitate The system shall support
prevention, wellness, disease
management and other health
clinical decision support which
will alert a provider to identify R R V1
education through a clinical prevention services needed,
5.4 The system shall facilitate The system shall support
prevention, wellness, disease
management and other health
clinical decision support which
will alert a provider to identify R R V1
education through a clinical prevention services needed,
5.6 The EHR shall (if required The system is able to provide
under certification) include
alerts and reminders about
alerts and reminders based on
predefined clinical guidelines. R R V1
routine processes of care for The system shall have DSS
5.7 The system shall have decision The system shall have decision
support capabilities. support capabilities and alerts
that identify the reason for the R V1
alert, relevant trigger data,
5.8 The system shall have the The system shall support alerts
capability for clinical decision
alerts/messages.
and reminders about Health
Maintenance and Disease R R V1
Management triggers. The
5.14 The system shall provide a The system shall provide a
prompt to alert staff to
diagnosis of diabetes,
prompt to alert staff to
diagnosis of diabetes, R V1
standardized lab order set is standardized lab order set is
5.15 The system shall have a CDS The system shall have a CDS
that informs the provider of
best practices in smoking
that informs the provider of
best practices in a disease and R V1
cessation and highlights life habit and highlights relevant
5.16 Appropriate clinical staffs are The system can capture vital
able to document, review and
update patient problems,
signs data including T, P, R,
BP, Ht, Wt, BMI, (head circ- R V1
medications, medication peds) which is available for
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
5.19 The provider initiates a The system shall allow for a
discussion with the patient
about changing a life habits
reminder to be set based on
the provider initiating a R V1
(i.e. smoking, alcohol, etc.). discussion of life habits to
5.21 The system shall allow the Education provided to patient,
education of the patient and
referral to other patient
and referral given to patient,
shall be documented in a R V1
educators (e.g., dietitian, standardized manner with
6.1 The system shall have decision EHR has standardized drug
support capabilities. database (ex: FDB, Multum)
with allergy dictionary. Drug R V1
codes from the dictionary will
6.2 Technology allows cardiologist EHR has Rx decision support
to determine if prescription
drug is on formulary of patient’s
for drug-drug interactions and
allergy checking and has R R R V1
insurance plan. Formulary mandatory alerting for drug-
6.3 The system shall have decision The system shall have decision
support capabilities around
medication alerts. The system
support capabilities and
structured fields to drive alerts R R V1
shall be capable of allowing ED (allergies, current medications).
6.4 System allows cardiologist to ePrescribing function within
send prescription to pharmacy
electronically or to print for
EHR, documents and stores
physician and patient info, SIG, R R R V1
patient. substitutes and can
6.5 Technology allows user to EHR system is certified for
determine if prescription drug is
on formulary of patient’s
RxHub and makes available to
the end-user ALL payer R V1
insurance plan. Formulary eligibility information and
7.2 Clinician shall confirm previous If electronic ordering is not live,
medications and prescribe any
potential new medications or
system can create customized
order forms for efax to relevant R R V1
make dose changes. Clinician facility.
7.3 Clinician shall confirm previous Clinician shall confirm previous
medications and prescribe any
potential new medications or
medications and prescribe any
potential new medications or R R R V1
make dose changes. Clinician make dose changes. Clinician
8.2 The system shall have the The system shall have the
capability for the provider to
manually select/deselect a
capability for the provider to
manually select/deselect a R V1
patient as part of a panel of patient as part of a panel of
8.3 The system shall have the The EHR shall have the ability
capability to receive and store
measure information either
to store discrete values that will
be used to compute quality R V1
documented from within the measures.
9.1 The system shall send the lab Lab results are populated
request electronically. Lab
results are populated
(imported) electronically into
the EHR with flags for R V1
electronically into the EHR with abnormal results.
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
9.2 The system shall send the lab The EHR must accept
request electronically. Lab
results are populated
electronically delivered lab
results. R V1
electronically into the EHR with
9.3 The system shall send the lab The EHR must accept LOINC-
request electronically. Lab
results are populated
mapped electronic lab results if
available from the source lab. R V1
electronically into the EHR with
9.4 The ordering physician shall Functional Requirement The
have the capability to
electronically receive the
system shall accept radiology
results and reports R V1
ordered radiology report so electronically from imaging
9.5 The system shall send the lab The system will set a reminder
request electronically. Lab
results are populated
for recommended time frame
for next lab test. R V1
electronically into the EHR with
10.1 In the event that a RHIO The system must permit a
becomes aware of any actual
or suspected privacy and/or
person with administrative
access to log into the system R R R V1
security breach, either through to investigate a potential
10.2 In the event of a privacy and/or They system must allow an
security breach, the RHIO shall
mitigate (or cause the
administrator to terminate all
users' access to a specific R R R V1*
applicable Participant to patient's data, or discontinue a
10.3 Each RHIO shall maintain audit The system must be able to
logs that document all access
of health information through
determine when an "access"
has occurred and log that R R R V1*
the RHIO and include at a event, in order to take
10.4 The audit logs maintained by The system must assure that
RHIOs pursuant to these
policies and procedures shall
all audit logs maintained are
immutable (cannot be changed R R R V1*
be immutable. EHR systems or modified).
10.5 The audit logs maintained by The system must retain audits
RHIOs pursuant to these
policies and procedures shall
for 6 years.
R R R V1*
be maintained for a period of at
10.6 Each RHIO shall 1) establish The system should have
categories of Authorized Users
2) Define the purposes for
administrative controls and
access privilege controls R R R V1*
which Authorized Users within aligned with categories of
10.7 Each Authorized User shall be The system should have the
assigned a unique user name
and password to access
ability to create unique user IDs
and passwords R R R V1*
information through a
10.8 Authorized Users shall be The system shall prompt user
required to change their
passwords at least every 90
to change his/her password
after 90 days, track past R R R V1*
calendar days and shall be passwords used, and prohibit
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
10.9 Access to the RHIO of an The system shall lock out a
Authorized User for whom
access has been denied
user who has been denied
access X number of times; to R R R V1*
multiple times (e.g., due to use be determined by the RHIO
10.10 Session of an Authorized User The system should have a
shall automatically terminate
after a specified period of
configurable inactivity timer,
after which time period, a User R R R V1*
inactivity will be logged off the system.
10.11 There are two levels of The system needs to track and
Consent - Level 1 and Level 2 record 2 levels of consent. The
system must be able to R R R V1*
transmit the consent status for
10.12 NY law permits minors to System must record and store
obtain certain types of health
services based on their own
Minor Consent for Minor
Consent Information. System R R R V1*
consent without the consent or must tag Minor Consent
10.13 When a minor turns 18, the The EHR system must
RHIO may no longer facilitate
the exchange of the minor's
generate an alert or reminder
to obtain a new consent for R R R V1*
information unless the minor minors who have turned 18.
10.14 Level 1 Consent form must System must record and store
contain: description of intended
uses, what information being
structured data elements for all
data required in Level 1 R R R V1*
exchanged with specific Standardized Consent Form as
10.15 Level 2 Consent form must System must record and store
contain: Level 1 items plus
specific entities from which
structured data elements for all
data required in Level 2 R R R V1*
information will be obtained and Standardized Consent Form as
3.1 The provider shall receive EHR will capture and export
through their IT system a
complete and accurate
data elements required for
defined medication R R V2
medication history from reconciliation. Ambulatory EHR
3.2 Appropriate clinical staff is able EHR will both capture and NA
to document Chief
Complaint/RFV and initial HPI
export data elements required
for defined medication R R V2
in EHR. Clinical staff is able to reconciliation. The system is
3.3 The system shall allow the EHR will export required clinical
physician to put their notes in a
format that can be shared with
data elements in a standard
format as determined by the R R R V2
other physicians and the host RHIO and/or SHIN-NY.
3.4 The system shall allow the EHR will allow VS, H&P, office
physician to put his notes in a
format that can be shared with
notes, and referrals to be
exported and imported for data R R R V2
other physicians. The EHR sharing in standard format
3.5 A patient logs into their PHR If as a result of a message NA
and notices that certain data is
incorrect. The patient will send
received from another system
(i.e. PHR), a modification is R V2
a message to the source made to the EHR, the system
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
3.6 The system shall have the The EHR system shall have the NA
ability to confirm the
appointment and/or send the
ability to acknowledge an
electronic scheduling request in R V2
pre-visit questionnaire. a format determined by the
3.7 The system shall have the The EHR system will have the NA
ability to confirm the
appointment and/or send the
ability to send a scheduling
confirmation to the requesting R V2
pre-visit questionnaire. system/user in a format
3.8 A patient sends an electronic The EHR system will have the NA
request to the EHR, requesting
an appointment. The practice,
ability to attach a file or link with
a scheduling confirmation. R V2
via the EHR sends an
3.9 A provider modifies a patient The EHR system shall allow
record as part of a visit. The
data is then transmitted to the
real time electronic notification
of clinical services i.e., R V2
HIE to note changes, and additions, changes, deletions
3.10 The HIE shall accept updates The EHR is able to export
from the EHR and may route
them to the PHR.
either batch or real-time
updated patient data and route R V2
to the appropriate system with
3.13 The system allows export of The system allows export of NA
numerator counts and numerator counts and
denominator counts to support denominator counts to support R V2
third party display of quality a third party display of quality
4.1 The physician shall receive The EHR shall import alerts NA
email alerts/messages
directing her/him to a Care
from the HIE as per standards
determined by the RHIO. R V2
Consideration regarding one of
4.3 As a clinician looks for The system (EHR) has the
information on a patient, they
have the option to import the
ability to import discrete clinical
data from an HIE. The system R R V2
clinical information from the will accept the electronic
4.4 A patient logs into their PHR The source NA
and notices that certain data is system/practice/entity can
incorrect. The patient will send receive data request from the R V2
a message to the source PHR to modify data.
4.5 If an external system has The system shall allow import NA
calculated quality measures,
then the provider should be
of quality measure results.
R V2
able to view the quality
4.6 A provider receives an alert The EHR system shall facilitate NA
from an external system (PHR, an easy way to link to RHIO
HIE) with a link attached. The web services to receive alerts. R V2
provider is able to follow the
4.7 The patient shall be able to The system should provide
request an appointment with a access to a scheduling system
physician through the PHR. or allow the patient to initiate a R V2
request to a practice to
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
4.8 The system shall create a The system supports secure NA
means for physicians to
securely communicate with
messaging. The system allows
secure electronic R R V2
other providers for the benefit communication between the
4.9 The clinician has the option to The clinician can trigger which
import the clinical information
from HIE or view only. The
data gets imported into an EHR
from an HIE. The system can R R V2
providers shall have the option import the medication record,
4.10 Medication history shall be EHR will have ability to import
incorporated directly into the
EMR (automatically loaded)
medication history information
from an HIE. It is strongly R V2
and/or staged through an HIE. encouraged that EHRs
5.5 A provider in the ED sees a The system shall transmit an NA
patient with a chronic illness.
The Hospital system shall allow
"alert" to care management
program or to internal care R V2
for ED information to be manager (would apply to other
5.9 The system shall notify the The system shall notify the NA
provider that a patient may
qualify for a measure
provider that a patient may
qualify for a measure R V2
population. This notification population. This notification
5.10 The system shall be able to The system shall be able to NA
collect non-compliance / refusal
/ lack of completion data,
collect non-compliance / refusal
/ lack of completion data, R V2
where available. where available for specific
5.11 The system shall identify pt as The system shall identify NA
having a history of diabetes
with multiple ED visits, the
patients as having a history of
a chronic illness or disease and R V2
recent ED visit generates a flag that they have had multiple
5.12 The system shall capture in a The system shall capture in a NA
discrete field that is easily
retrievable or based on text
discrete field that is easily
retrievable or based on text R V2
mining that the appropriate and mining that the appropriate
5.13 The provider and the patient The system shall capture in a
have a discussion about
smoking cessation and
discrete field that is easily
retrievable based on text R V2
provider recommends smoking mining that smoking cessation
5.17 The system facilitates the The system facilitates the NA
review of which patients are
compliant with follow-up
review of which patients are
compliant with follow-up R V2
examinations. examinations.
5.18 The system shall allow the The system shall suggest type NA
education of the patient and
referral to other patient
of referral needed (e.g., to
dietitian, diabetes educator, R V2
educators (e.g., dietitian, nutritionist, counselor, etc.)
5.20 The system shall link the The system shall link with an NA
system with the appointment
scheduling feature that has a
appointment scheduling feature
that has a reminder and R V2
reminder and tracking function tracking function to call/follow-
Functional Requirements
To view entire cell contents, highlight the cell and double-click
[insert vendor name]
Requirement # Published V1.0 Clinical Published V1.0 Functional MMM CNY QUAL Version Vendor Flag* Vendor's ability to meet requirement Vendor Comments
Requirement Requirement
7.1 The system must capture and The system must capture and
track the referral and track that
the appointment was kept,
track the referral and track that
the appointment was kept, R V2 NA
results reviewed and sent to results reviewed and sent to
7.4 Clinician shall confirm previous When electronic ordering is NA
medications and prescribe any
potential new medications or
enabled the system can
generate relevant requisition R R V2
make dose changes. Clinician numbers, registration numbers,
8.1 The system shall have the The system shall have the
capability to automatically
identify patients who meet
capability to automatically
identify patients who meet R V2
denominator requirements of denominator requirements of
* There were some requirements that every vendor not could meet as of November 1, 2008. Requirements were assigned a flag depending upon the number of vendors that were able to meet this requirement; the grid below
explains how these flags were assigned:
All responding vendors were able to meet this requirement
Most responding vendors were able to meet this requirement
Few responding vendors are were able to meet this requirement
Related docs
