0 comments on “Go Direct!”

Go Direct!

DSM recently acquired the necessary infrastructure and connections to accommodate direct Medicare transmissions via high bandwidth connection.  In addition DSM has received 5010 Approval from both   Palmetto and Cahaba for direct transmissions.   Transmitting claims through this new infrastructure eliminates the typical 3-day wait to get claims to Medicare through one of the large clearinghouses improving the turn-around time from claim transmission to payment.  This in effect makes DSM your clearinghouse and removes one level of complexity as DSM provides the claim build and posting software as well as the transmission infrastructure.   Only a few customers can take advantage of this direct connection at the moment but soon all customers will have this option.

0 comments on “***IMPORTANT JH Transition Information***”

***IMPORTANT JH Transition Information***

On May 16, 2012 Novitas will mail letters requesting that each group/billing provider complete a new CMS-588 EFT Authorization Agreement. The revised CMS-588 should be sent in to Novitas no later than 30 days prior to August 13, 2012. Provider action is required to avoid payment delays.

Click here to see the “JH Implementation Alert”.

0 comments on “AR/LA/MS On Board With Our New MAC!”

AR/LA/MS On Board With Our New MAC!

In the midst of all the EDI updates, transitioning to our new Part A/B MAC is right around the corner. Novitas, formerly known as Highmark , will begin this transition with AR/LA/MS Part A in August. DSM is asking all the right questions and informational updates will be posted here. We will help you “weed” through the overwhelming “blast” of information and highlight points of interest for our providers. Stay tuned for these and other updates…

Click here for more information about the JH Implementation.

0 comments on “Moving Right Along!”

Moving Right Along!

DSM has been busy this summer bringing up EMR interfaces and installing our new insurance programs in customer hospitals. 

EMR

DSM now has four different EMR solutions in seven different hospitals up and running.  All are interfaced to our billing system and were up and running by the July 3 deadline.   We have numerous hospitals in our customer base that have contracts signed and will be making the move on bringing up EMR’s in the next six months.  DSM is also in talks with several new hospitals for a tightly integrated solution with our preferred EMR partner, Razor Insights.

Insurance

The insurance system has steadily been installed in customer hospitals and it also has numerous enhancments in it. A new front-end edit system allows for a much larger number of edits and automatic claim modifications to occur before the scrub is done.  We have also worked with our scrubbing partner to add customer specific edits to occur in the scrubbing process.    The dashboard now includes dollar amounts and number of claims in the bar and pie charts.  The 5010 X12 formatting programs are ready and testing for the January implementation is under way.  Of course, our new insurance system was designed for 5010 compliance from the ground up which made the 5010 formatting a piece of cake.

Mississippi Health Department Discharge Reporting

DSM has installed a new upgraded server for the Health Discharge Reporting System which will accommodate the lab result reporting system that the Health Dept is bring online as well as future systems like electronic surveillance.  DSM has also collaborated to come up with improved reconciliation procedures for the discharge health reporting.

New Servers

Several customers have recently upgraded their servers with the latest Power7 servers from IBM.  The machines are speed demons and make our new web based applications like insurance and time and attendance really whistle.  The difference is truly unbelievable.  The new servers have many great features that we like.  The LAN console for example allows our support personnel to do functions requiring the console remotely.  This allows most of the migration to the new system to be done remotely.  IBM PTFs and operating system changes can be done without a technician being on site.  The machine has many capabilities to make them even more highly available, like RAID-6 which allows for two drives to be damaged and the system will continue running.

Development

DSM is partnering with a third party group for new program development to refresh our entire product line.  Work has already begun with the design and integration of registration screens with our EMR partner, Razor Insights.

Medical Necessity

We now have medical necessity available through our new insurance system as a web service, eliminating the need to have a subscription.   This system is transaction oriented rather than fixed price, meaning you can pay as you go at the same rate as insurance claims and only for the medical necessity checks that are performed.  This is a vast cost improvement over partner solutions with fixed annual fees.

Certifications

DSM recently completed new certification requirements for IBM with both sales and technical certifications being completed for the new Power 7 systems.  The new Power7 systems have been really moving at IBM, providing some of the highest sales volumes of these systems seen in recent years.

0 comments on “Clinton Tornado Close Call”

Clinton Tornado Close Call

Many thanks to all those who called concerned about us here at the Clinton offices when today’s tornado hit.  The photo on the left was taken by someone at Mississippi College and of course DSM offices are nearby, but our offices received no damage.  DSM’s network admin, Tracy Reynolds spotted a tornado briefly, we are not sure if it was the same one.   It was certainly a scare. DSM employees were glued to the windows expecting a tornado, we are certainly glad that this one went east of us.  Our thoughts are with the people who were injured.

0 comments on “Our Silent Solution to Reporting Health Data”

Our Silent Solution to Reporting Health Data

I was looking on the web for information on electronic health reporting and found this 2007 report prepared by the National Association of Health Data Organizations.  The report  preceded the law that mandated health data reporting in Mississippi and laid out options that Mississippi used in planning it’s health data reporting systems.  I found it very interesting that under the heading of “Hospital Burden” the report quotes a study that cites “upfront costs” and some very high reporting costs, from “$10 per record to $132 per record”.  As DSM is providing it’s solution to it’s customers for only $100 per month for all records in a month and there were no up front costs, I think we hit a home run.  Not to mention all the monitoring and behind the scenes processing we do. It’s actually an elegant solution:

 DSM personnel monitor the automated processes with the following screen:

 Each individual transmission for a hospital can be pulled up with the following screen:

 If a an error is encountered, which is very rare indeed, a DSM representative contacts the hospital which can access the error by using the option below:

And any errors will appear on the following screen, however, you may notice the message “No records have been selected.”  

That’s because the system rarely has any errors.  Not only do we receive an email if there are errors, we receive emails from the Health Dept. which have totals of records received and we reconcile those numbers.    All of these activities occur without the intervention of your personnel. 

The same infrastructure was applied very similarly in the BCBS daily census reporting, which also runs behind the scenes in a very quiet and unobtrusive way, allowing hospital personnel to concentrate on other tasks.  The MSHDS solution we provided is just another way that DSM continues to provide quality results with affordable efficiency.

0 comments on “Windows 7 – Client Access vs Windows 7, The Sequel”

Windows 7 – Client Access vs Windows 7, The Sequel

On my last two posts, I discussed enabling the Windows 7 Administrator account and the problems associated with installing and using Client Access on Windows 7.  This post will show you the steps to take to configure Client Access for every user on a Windows 7 PC.

While changing these files, we’ll use the snap-to-edge feature of the Windows 7 Aero Desktop.  This will allow you to see two windows at the same time much like an FTP screen.  First Go to the Control Panel and click on Folder Options.  Go to the View tab and under the Advanced Settings area click the radio button next to the “Show Hidden Files” entry and then Click the OK button.

Assuming you’re logged on as the Administrator:

  1. Click on the Start Menu and click the Computer link (on the right side of the menu).
  2. Double click on the C: drive and go to Program Files/IBM/Client Access/Emulator/Private.
  3. Click the title bar and drag the window right until the cursor touches the right edge of the screen. (It should resize and fill half the screen)
  4. Click on the Start Menu and click the Computer link.
  5. Double click on the C: drive and go to Users/Administrator/AppData/Roaming/IBM/Client Access/Emulator/Private.
  6. Click the title bar and drag the window left until the cursor touches the left edge of the screen.
  7. In the left window, with the Ctrl key pressed, click the AS400 file and the newly created workstation file. This should highlight both files.
  8. Right click on one of the files and choose Copy.  In the right window, right click and choose Paste. Replace any file that requires it.
  9. In the right window, right click the workstation icon and choose Open With, then choose Notepad.  (Remember to uncheck the “always use the selected program to open this kind of file” check box)
  10. Find the “defaultkeyboard” entry and enter this line: “DefaultKeyboard=C:Program FilesIBMClient AccessEmulatorprivateAS400.KMP” without the quotes.

On the left side, click the back button until you’re at the C: drive.  Double click the Users folder and then the Public folder.  Double click the Desktop folder.  In the right screen, right click the workstation icon you created and drag and drop it into into the left screen and into the UsersPublicDesktop folder.  When asked, choose to make it a shortcut icon.  This will put the workstation on everyone’s desktop.

Using these steps, you’ll be able to install Client Access, move and configure the workstation file to the IBM folder that everyone has access to, and then create a shortcut on everyone’s desktop.  All your coworkers will look at you with envy!  They’ll want to be you!  If you get too lost while trying to accomplish these instructions, call me and I’ll get you straightened out.

0 comments on “Windows 7 – Client Access vs Windows 7”

Windows 7 – Client Access vs Windows 7

I started using Windows 7 not long after it came out.  It didn’t take me long to realize that it is easier to use than Windows XP and more stable that Windows “Linux is Better” (also known as Windows Vista).  I had a concern that there might be problems with the vast array of software that our customers use.  That turns out not to be the case….almost…

Windows 7 is a little quirky when it comes to allowing users to access some programs.  This is very evident when it comes to Client Access.  You install Client Access the same way you did in Windows XP.  The fun begins when you start configuring it.

If you haven’t read my other Windows 7 article about setting up the Administrator account now would be a good time to do so…go ahead…I’ll wait.  If you can’t find it, look in the Networking/PC Support Category on the right.

Assuming that you’ve enabled and logged onto the Administrator account, let’s proceed.  To configure Client Access, click on the Start Menu and then All Programs.  Click on the IBM iSeries folder, then the Emulator folder, and then the “Start or Configure Session” icon.  Configure the session and save it.  For instructions on configuring the Client Access sessions, email me at treynolds@dsmhospital.com and I’ll send you a cheat sheet that will walk you through the steps.

If you launch Client Access (and it’s configured correctly) then you should be able to log on to the server.  It’s all fun and games until you change user accounts, then you’ll get so many error messages that you’ll probably start apologizing for things you didn’t even do! (I personally confessed to the Chicago fire, but after I calmed down I realized that was a bit nutty.  I have since recanted.)

You see, the saved Client Access configuration is NOT placed in the Program Files/IBM/Emulator/Private folder like it is in Windows XP.  Instead it’s saved in the App Data folder of the installing user account.  In this case, the Administrator’s App Data folder.  Since other users would not normally have access to this folder, access error messages will appear if another user tries to use Client Access.

To solve this problem, you’ll need to move and edit a few files.  I’ll talk about this on the next post titled “Windows 7 – Client Access vs Windows 7, The Sequel.”

0 comments on “Windows 7 – Administering the Administrator”

Windows 7 – Administering the Administrator

As people cling to Windows XP like it was the last donut in a room full of policemen, Windows 7 is quickly becoming more noticeable. Like every other version of Windows, Windows 7 is an improvement over it’s previous flavors. It’s not without its quirkiness, however, and one of the most notable is the configuration of the local Administrator account!

Though it was not so important in XP, major installations (Client Access, anti-virus, etc.) should be installed using the Administrator account. Win7 takes the role of Administrator seriously. So seriously, in fact, that the Administrator account is not even enabled by default. When you start to configure a new Win7 PC, a good place to start is by enabling the Administrator account.

To enable it, simply log on to the first user account you create. Click on the start menu, click on All Programs, and then click on the Accessories folder. Right click on the Command Prompt icon and choose “Run as administrator.” At the prompt, type in the command “net user administrator /active:yes” without the quotes. Hit the enter key and you should get a message stating that the operation was successful. Remember to open the command prompt by right clicking and running as the administrator. This is important because simply opening the command prompt and running this command will lead to error messages and possible balding, though the latter is still unconfirmed.

The Administrator account does not have a password when you enable it so log off the current user and you’ll see the Administrator icon on the Welcome screen. Click it and, after the desktop loads (which might take a little longer the first time) click the Start Menu and go to the Control Panel. The default view for the control panel is supposed to be user friendly, but, like swimming with lead flippers, I find it a bit cumbersome.

Near the upper right corner you’ll see a link labeled “View by.” Click on the word “Category” and choose “Large Icons” from the drop down menu. Scroll down to the bottom of the screen and you’ll see an entry for user accounts…so….click it. In the middle of the window there will be several links for different tasks. Choose the link that enables you to create a password and follow the on-screen prompts. When you’re done, close everything out and you’re ready to use the Administrator account.