If you're the CEO of a healthcare system or hospital using MEDITECH to qualify for Meaningful Use Stage 2 and you qualified for use of CPOE for Stage 1 in 2011 at 33%, and your physicians are still utilizing CPOE at 33%, here's the storm headed your way.
To qualify for the ARRA CPOE Stage 2 metric for 2012, you need 60% of orders by physicians in 2012 to be entered electronically to qualify. As you'll see... this window is closing fast.
In May, your physicians need to begin placing 75% of their orders electronically for the rest of the year to make the grade of 60% for the whole year.
In June, your physicians & providers need to be placing 80% of their orders electronically to average out to 60% for 2012.
After June, there isn't much hope of qualifying for the ARRA money this year. Even in an ideal world, how many physicians are going to be utilizing CPOE above 80%? Not many, the time to act is right now!
Meditech's ARRA Report Documentation says: "In order for queries to be properly maintained and available for reporting in all instances, you must enter Yes in the Save Query History field. This allows a query to appear on reports in Patient Care System and retains a history for edits and undos for reporting purposes. Please be aware, entering Yes in this field also allows recall of previous responses to this query when entering documentation for a patient."
Today, I'd like to turn the camera on you dear reader, and give you the opportunity to share your hard won, real world experience with our readers.
Anyone have a real world experience with Query History they'd like featured here?
- Send your story, positive or negative.
- Include any relevant examples (minus PHI that's patient information).
- Whether or not you'd like to share your name and health system name and a photo (headshot) unless you'd like to remain anonymous.
Fax your story to: 509-624-3862
or
Secure email: http://tools.comstock-software.com/Vendors/SendSecureFile.aspx
When including Client Server data on a 6.x report, it is not possible as of 03/22/2012 to suppress the Database Prompt as depicted below. In the future that might change, 6.x is evolving rapidly. Here's the MEDITECH dialogue on the subject.
(QUESTION to MEDITECH) - Mar 21, 2012: When a report in Report Designer accesses a CS Module such as ABS, is there a way to suppress the prompt at run time?
(MEDITECH RESPONDS) - Mar 22, 2012: At this time there is no functionality to suppress that message from printing. It is needed in order to establish the link over to CS.
I can hear you now. Wait a minute: this didn't work like this in Magic or Client Server. Don't you have that funny feeling, I know I do, you're going to be saying that again & again!
In 6.x MAT Meditech Report Designer patch PP whatever we're at now, the current standard report defaults to the Select Screen staying open after you've selected and printed your report. Very nice in some instances, but as a default option? Maybe not!
Management, Analysts & Report Writers: your users are going to want this changed. Why wait for them to request it?
Here's what to do: for every custom Report Designer report, go to the General Tab, and answer Yes to the Close Screen After Printing.
Staples, I can hear you now!
To quickly combine multiple files, place the files you want to combine in a new folder.
Open a command prompt: click your Start button 
, click Run 
, type cmd. Use the CD (Change Directory) command to navigate to the folder where your files are stored.
Use the DIR command to create a file with a list of the text files in this folder: dir *.txt >Dir.txt. Close your command prompt, by clicking on the X as shown: 
.
Using a text editor, copy the file names from Dir.txt into a new text file.
Save the new file as CombineFiles.bat in your directory with the other files.
Using copy /b combine all file names in a + delimited list onto the first line of the CombineFiles.bat file. After your list of files, type a space and then the name for your new large file which will contain the contents of the other files.
Example 1: copy /b Data-File-0.txt+Data-File-1.txt+Data-File-2.txt+Data-File-3.txt+Data-File-4.txt+Data-File-5.txt+Data-File-6.txt+Data-File-7.txt+Data-File-8.txt+Data-File-9.txt+Data-File-10.txt+Data-File-11.txt New-Large-File.txt This will combine the files in the exact order you've expressed in your + delimited list.
Example 2: If file order doesn't matter, copy /b *.txt New-Large-File.txt will copy all files into the new file.
Save and close CombineFiles.bat. Run CombineFiles.bat by going back to your folder with the files and clicking on CombineFiles.bat. Running this file is known as executing a batch file.
When the batch file completes (this can take a while if your files are large), your command prompt will close by itself. Go back to your folder to find your new file containing the contents of the other files, if you’ve followed the naming convention above, the file will be named: New-Large-File.txt.
There: we’ve successfully combined 10 flat data files into 1 large data file, just like that.
To set your default printer (just like you can in Microsoft Windows): next time you print, check out the MEDITECH 5.6 Print Preferences button to the right of your screen.
Since my work usually involves loading vendor databases, data marts and warehouses, my default should be Download. Maybe your default will be the printer at your desk.
If the extract runs at the same speed all of the time, use
binary troubleshooting to
divide & conquer the performance issues inherent in the code. Assuming the extract can be run faster when restarted, rule out
slowness, 1 aspect at a time:
- Can the extract be scheduled to start at another time and run quicker? Example: 2:00 a.m. instead of 12:00 a.m. If so ... start time could be the cause.
- Reboot the machine where the extract is running. If ... extract run time does not improve, the state of the server was not the issue.
- Run the extract from another machine. If run time improves, look at re-installing MEDITECH client on the original machine. If performance does not improve, then try re-imaging the client machine.
When I use a systematic method, to locate the cause of my problem, I usually don't get very far in the troubleshooting process. Often I'll get to somewhere around steps 6 - 9 and spot the trouble.
That's because
Binary Troubleshooting is a method used to solve problems.
To start: imagine your problem as a system. Divide the system into 2 equal areas & implement tests to prove the problem is not in 1 of the 2 areas.
Continue: divide the remaining piece of the system where the problem is now proven to exist, into 2 more pieces. Implement tests to isolate the cause of the problem to just 1 of the remaining pieces. Rinse & repeat.
Stop: when you find the cause of the problem. If your problem were to consist of over 1 million possibilities, it would only take you 20 steps: to find the root cause of the problem.
This divide & conquer process comes in handy, especially when working on projects in unfamiliar terrain.
The previous article did not include an actual link to the MEDITECH White Paper.
Thank you HP for noticing!