Archive for: Automation
QTSO releases MDS 3.0 submission helpful hints
The QIES Technical Support Office (QTSO) recently released a document containing helpful hints to ensure correct MDS 3.0 submission. The document outlines the steps required to submit an MDS 3.0 file, verify its submission status, and obtain a Final Validation report. The document also lists some of the most common severe errors that providers are seeing in processing MDS 3.0 files. These errors are as follows:
- 1001 Invalid Zip file format (no generated FVR)
- 1002 Empty Zip file (no generated FVR)
- 1004 Invalid XML file format (record not on generated FVR)
- 1008 Missing or invalid State Code (record not on generated FVR)
- 1009 Missing or invalid Transaction Type code (record not on generated FVR)
- 1010 Missing or invalid Provider Type Code (record not on generated FVR)
- 3693a Invalid Fac_ID (record not on generated FVR)
To read the QTSO’s document of MDS 3.0 submission tips, visit our Resources page.
Senate Finance Committee passes healthcare reform bill
On October 13, the Senate Finance Committee, which spent the past two weeks discussing 130 amendments, approved its healthcare reform bill by a vote of 14-9. It is one of five pieces of legislation seriously being considered on Capitol Hill and is the only plan that excludes a public option, according to CNN.
The bill is expected to cost $829 billion over the next ten years and is partially financed by about $400 billion in spending cuts, including significant Medicare reductions. Democratic leaders in the House and Senate will begin drafting a single piece of legislation out of the five existing proposals. Republicans refuse to endorse a public option plan, which they argue would eventually lead to a government-run healthcare system. Senator Olympia Snowe of Maine was the only Republican committee member to support the bill, which was initially drafted by Chairman Max Baucus, D-MT.
Ask Diane: What if I need a new automation vendor for MDS 3.0?
Q: My automation vendor just contacted me and told me the company will not be going forward with producing new software for the MDS 3.0. What should I do?
Diane: The first thing you should do is make sure your entire administrative team knows your current software vendor will not be transitioning to the MDS 3.0 and that you will need to search for a new vendor.
Another thing you should do immediately is determine your budget for new software and other related items you might need, like new hardware.
Searching for a vendor is a complex process, but here are a few guidelines to keep in mind as you get started:
- Don’t restrict your search to only one or two vendors—look at a broad spectrum of vendors.
- Evaluate whether vendors you are considering can keep up with frequent changes. We know there will be some glitches when we transition to a new system, so choose a vendor who can handle changes.
- Check vendors’ references and make sure to visit facilities that use a certain vendor’s software to see how it actually works. Ask about how long the vendor takes to respond to client problems.
Also, evaluating whether a certain kind of software will work for your facility is a critical part of the vendor selection process. I’ll post more tips about what to look for in a software products in upcoming MDSCentral posts.
Ask Diane: What should I ask my vendor?
Q: Our facility will need to update our software when we transition to the MDS 3.0. What questions should we ask our vendor now?
Diane: It’s important to start a dialogue now with your automation vendor. You can work with your vendor to create a better product.
Sit down with your team and make a wish list for your software. Be aware that when you ask your vendor for a process improvement, the price of your software is likely to increase.
When you talk to your vendor, you should ask:
• Is your vendor aware the MDS will be updated? Is your vendor planning to meet the deadline?
• How much will updates cost?
• What process improvements is your vendor willing to make?
• How much will improvements cost?







