eClinical OCR and body images support flow together with our Scan and Fax blog post. So if you aren’t finding what you need here. Check out that post. Front Desk staff at small practices just don’t know what they are missing when converting documents into electronic form but not taking advantage of OCR or Optical Character Recognition. Let’s begin with OCR. Scanning documents is one thing but the ability to lift text off the scanned image and insert into your EMR’s patient notes is another. The copy and paste functionality becomes a lot more difficult if you are using PDF with eClinicalworks. It is recommended you use TIFF because eClinicalworks was designed to work with Microsoft Office Document Imaging tool or MODI.
The eClinicalworks built-in inbox viewer called ECWDigink.exe will be sufficient for most. The viewer features are:
- Basic document viewing
- Text and Ink Notations
- Time Stamp
- Copy and Paste the OCR text into the EMR
The MODI installed update to eCW include enhanced features like:
- Better document management. ie. Delete unnecessary pages included in the fax document viewer
- Rearrange pages in the viewer
- Improved text and ink notations
- Better overall viewing experience. Windows document viewer is a poor default app for viewing documents.
MODI is a free tool that enabled editing and annotating document. Documents scanned by your organization’s scanner or faxes received by your organization’s fax server are aggregated in an inbox or scanned shared folder. These images or hopefully TIFF files are then assigned to charts and other areas of your Electronic Health Record system.
Pro Tip! – The labeling of EMR or EHR is dependent on whether the system is dedicated solely for Patient Health Information (PHI) or more. The system is called an EHR when it contain more than just PHI.
The bottom line, request your IT guy use MODI in conjunction with eClinicalworks for the most productivity out of your staff. Check it out in action…
Eclincal scanning and fax support are critical pieces in the eCW EMR architecture.
Make “MODI” Microsoft Office Document Imaging Default
c:\program files (x86)\common files\microsoft shared\MODI\12.0\mspview.exe
To change ECWDigink.exe to MODI….
The History of Microsoft Office Document Imaging and MODI Installation
By default, newer windows computer do not have MODI. It was first introduced in Office XP, and was included in Office 2003, Office 2007, and Sharepoint Designer 2007. Although it is not available in Office 2010, it is possible to install it from a previous version of Microsoft Office and use it with Office 2010 or later.
To use MODI together with Office 2010 or later, use one of the following methods:
- You can install MODI from the 2007 Office system setup if you have 2007 Office ISO or CD installed on a computer that has Office 2010 or later installed, To do this, follow these steps:
- Start the 2007 Office setup process.
- Click Customize.
- On the Installation Options tab, select Not Available for all items except for the items under Microsoft Office Document Imaging, and then click Install Now.
- Click Close.
- The better option for most is to use MODI from Sharepoint (no license required) if you don’t have a legacy copy of Office:
1. Download Sharepoint Designer 2007
2. This download does have the ability for the admin to create a customization file in the Office customization tool (OCT) to install MODI. You will need to download the main .exe; SharePointDesigner.exe, then extract the files with the command line. For example:
This will extract the setup.exe, Admin folder, etc. to \\servername\sharename
Make sure you perform this step with appropriate administrative rights.
3. From the extracted folder location, run the following command to create the customizations in the OCT:
4. Within the OCT, you would go to Set feature installations state, and make everything “not available,” except MODI, as in the screenshot here. Changing the OCT settings to hidden and locked, if you do not want users to utilize SharePoint Designer, will hide it from within the Add/Remove Programs.
5. Save the resultant .msp (file>save) file and save it in the ‘updates’ folder where you extracted the Sharepoint Designer resource files. When you double-click setup.exe the install will use this file to define its installation parameters (no need to call it from the command-line).
6.After the installation of SharePoint Designer, if you are using SharePoint document libraries, it is recommended to unregister the Name.dll for SharePoint Designer (unless you have the actual Designer component installed). Unregistering the Name.dll for SharePoint Designer will address the interaction of Office files stored on a SharePoint document library and having two different versions of Office products (Office 2010 and SharePoint Designer 2007) on the computer.
eClinical OCR and body images support summary
I will continue to build this out as I gather more information on the subject. Until then, feel free to check out my other eCW blogs. Google “Network Antics eclinicalworks”.