Topic: Think big picture, understand terminology when implementing your EHR
HIM Connection, July 23, 2007
Want to receive articles like this one in your inbox? Subscribe to HIM Connection!
The core technical process of implementing an electronic health record (EHR) is the task of the "system build" and related testing and training. These are the most technically detailed tasks, and the ones most specific to each vendor's product. In an EHR implementation process, system build, sometimes called system configuration, refers to:
- Loading of master files and tables
- Customizing (or approving the use of vendor-supplied) screens, templates, and decision-support aids (and accompanying workflows and processes)
- Setting up technical security controls
- Developing interfaces, especially for data to feed into the clinical data repository
Testing is the process that verifies that each component of the EHR works as intended, and that all of the components work together. Integrate training into the system build and testing processes. There are many aspects of training--some of which your EHR vendor can help you with, others of which you will want to address outside the scope of the vendor offerings.
Implementation culminates in going live; however, you must also plan pre-live activities, recognize milestone achievements, gain end-user adoption, and prepare for ongoing system maintenance and enhancements well in advance. Integrate these processes into your implementation. Pre-live conversion activities--some of which start very early in implementation and others that happen at the last minute--include data preparation, chart conversion, data conversion, a go-live readiness review, a turnover rehearsal, implementation staffing, and the actual turnover.
Editor's note: This article was adapted from HCPro's book The No-Hassle Guide to EHR Implementation. For more information, click here.
Want to receive articles like this one in your inbox? Subscribe to HIM Connection!
Related Products
Most Popular
- Articles
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- Catch up on what's new with injections and infusions
- Topic: CMS, OESS post new security compliance review information, checklist
- What does case-mix index mean to you?
- Capturing all necessary codes for IUD insertion and removal can be challenging
- QA:Coding multiple initial infusions
- News and briefs: Oklahoma Osteopathic Association against residency bill change
- HIPAA Q&A: Level of encryption needed for email
- OB services: Coding inside and outside of the package
- E-mailed
-
- Q/A: Volume requirement for reporting hydration services
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- Catch up on what's new with injections and infusions
- New conflicts of interest create new challenges
- Q/A. One injection code or two?
- What does case-mix index mean to you?
- Q&A tackles coding questions about injections and infusions
- Joint Commission Center announces handoff communication solutions
- Inside best practice: Reduce patient falls with a stoplight
- Identify modifiable risk factors to prevent patient falls
- Searched