Download Notes - Cabarrus Health Alliance

Addendum A: High-Level EHR &
Practice Management Requirements
Please answer the questions at the end of each section. Answer “yes” if the core product meets the
high-level requirement. Answer “no” if product does not meet the requirement and cannot be made to
meet the requirement. Answer “other” if the core product does not include the described functionality
but the product can be configured to meet the requirement or if an additional product can be purchased
to meet the requirement. Please use the notes section to explain or elaborate upon your response. Be
sure to include any additional products in your proposal and proposal pricing or in Addendum C – Items
not included.
Public Health Specific Functionality
Any functionality specific to public health (not for particular clinics), e.g. multiple sliding fee scales, the
ability to bill differently for the same service when it’s done under an public health program service
versus primary care, etc.
Yes ☐
No ☐
Other ☐
Notes:
Electronic Health Records for








Yes ☐
Child Health & Pediatric Primary Care
Maternal Health
Family Planning
Tuberculosis
STD treatment (including HIV)
Immunizations
Breast and Cervical Cancer Screening
Adult Health
No ☐
Other ☐
Notes:
Meaningful Use
Maintain current MU product certification, and provide the functionality to support all current
Meaningful Use required activities and reporting.
Yes ☐
Notes:
No ☐
Other ☐
Pharmacy
The ability to track inventory, to dispense medications from small in-house pharmacy and have the
dispensement appear in the patient record and be removed from inventory.
Yes ☐
No ☐
Other ☐
Notes:
Lab
For tests performed in-house, we use our current EHR lab module as the definitive record. We would
like to have more robust LIMS functionality available. Our lab performs a limited number of tests inhouse, and they process labs that we ship to the local hospital and the NC state lab. The system should
be able to send lab requisitions electronically to these reference labs and receive lab results from them.
Providers should have the ability to review and sign-off on all lab results with the EHR.
Yes ☐
No ☐
Other ☐
Notes:
Lab Interfaces
The ability of the EHR to interface with a Roche Urisys 1100 (we have two of these units) and Siemens
DCA Vantage (we have one of these units). The EHR sends data to the machine identifying the specimen
to be processed. The machine sends results back to the EHR.
Yes ☐
No ☐
Other ☐
Notes:
Electronically Signed Documents
The ability for patients and/or staff to electronically sign documents, for example: clinical consent forms.
Yes ☐
No ☐
Other ☐
Notes:
Patient Check-in / Clinic Flow
The ability to track where a patient is from check-in, to clinical stations, to check-out and report on cycle
times.
Yes ☐
No ☐
Other ☐
Notes:
Billing

The ability to bill through patient statements, multiple insurance companies, Medicaid, and
Medicare via 837 file electronic billing.



Yes ☐
The ability to post payments electronically via 835 files from all of the above payors.
The ability to send claims through a clearinghouse
The ability to have an electronic superbill
No ☐
Other ☐
Notes:
Interfaces - Current



Yes ☐
All state or federally required reporting, including HIS batch reporting. (If HIS billing is not
included in the public health functionality, please let us know. We do not bill through HIS, but
it’s nice to know we would have the option if needed. )
Document imaging. This is a very simple interface (menu or button) to find the currently
selected patient number and search for that patient’s chart in our Laserfiche document imaging
solution. We would prefer to continue to scan documents to our in-house document imaging
system. Scanning can be scripted within that system just like searches.
In-house reporting. Like document imaging, this feature passes the patient number to our inhouse reporting system.
No ☐
Other ☐
Notes:
Interfaces – Future
HIE Connection to CMC CareConnect


Yes ☐
CMC labs bi-directional (test requisitions and results).
CMC patient data exchange – ideally this would be the conduit for maternal health information
to CMC Northeast Labor & Delivery unit.
No ☐
Other ☐
Notes:
HIE connection to NC-HIE for



Yes ☐
NC State Lab bi-directional (test requisitions and results).
NC Immunization bi-directional interface.
Patient data exchange
No ☐
Other ☐
Notes:
Data Access / Data Shipping
We would prefer to maintain the production and/or reporting database or data warehouse at CHA. If
we maintain the production database, we would be responsible for our own reporting systems. If we
maintain a reporting database only, we would like our vendor to ship information daily if not real-time,
so that we maintain a complete copy of our patient data. There are two objectives.
1. While we expect that the system will have useful canned reports and that users will have access
to ad-hoc reporting functionality with the system, there will undoubtedly be situations where
our organization needs a complex report, and there is no guarantee that report will be a vendor
or user community priority.
2. In the case that we should ever terminate the relationship with the vendor, we will require a
complete copy of our patient data.
We are open to alternatives that meet the objectives above.
Yes ☐
No ☐
Other ☐
Notes:
Data Conversion
Most of the data in our current EHR is discrete and the quality is relatively high. We would like to
convert that data: patient demographic, financial/billing, and clinical to the new EHR. One example that
has already been discussed is patient histories. As clinics migrated from paper charts to electronic
records, the visit times were made very long, because nurses were manually entering patient histories.
Visit times for return patients for all clinics have decreased, now that nurses and providers are simply
reviewing medical histories.
Yes ☐
No ☐
Other ☐
Notes:
Reports
A comprehensive list will be included in the detailed requirements document.
Release of Information reports: When patients or other providers request medical records. Thus far,
these reports seem to contain more information than can be shipped in a CCD and/or electronic referral.
However, we would very much like to have a standard interface for sharing this information with other
providers.
Maternal Health report: Similar to the ROI report, this is a comprehensive Maternal Health record
formatted similarly to the paper ACOG form. We share this with the local hospital through a reporting
interface maintained by CHA IT. If we house a reporting data warehouse, we can continue to provide
this functionality. This report is also used within the clinic to provide a better view of EHR data than the
system UI.
Optional Functionality (we may consider based on price and availability)

Picture Archiving and Communication System (PACS) capability for OB ultrasound images
Yes ☐
Notes:
No ☐
Other ☐

Laboratory Information Management System (LIMS)
Yes ☐
Notes:
No ☐
Other ☐