Perficient Healtchare Solutions Blog

Subscribe via Email

Subscribe to RSS feed

Perficient Healthcare Business Solutions

Perficient Healthcare on Twitter

avatar

Deborah O'Rear

Posts by this author:

avatar

Choosing a Clearinghouse/VAN

by on April 9th, 2012

Choosing your clearinghouse or VAN is a very important step, especially if you are in healthcare.  In healthcare you need to make sure they are HIPAA compliant, which means they will be able to handle all the mandated transaction sets.  Other industries have different requirements.  Whichever clearinghouse you choose, you need to make sure they can handle all the transaction sets you might want to utilize.

When shopping for your clearinghouse or VAN, make a check list of your requirements.  Here are a few of the most common questions you’ll want to address in creating your list:

  1. What transaction sets can they handle?  In healthcare, some of the transaction sets would be 834, 837, 835, 270/271, 276/277, etc.
  2. What is the problem resolution process?  Who do you contact?  How is the issue resolved?  If there is a programming change how long does it take for the change to be effective?
  3. How is data transmitted?  Is this done via web connection, SFTP, FTP, etc?
  4. How often is data transmitted?  Is data transmitted real time, batch, once daily, etc?
  5. What is the cost per transaction set?  Is the charge per ISA, transaction set, or bytes?
  6. What is the initial set up fee?
  7. What is the contract period?
  8. What additional expenses are required?  Do you need additional hardware, software, programming, etc. to trade data with the clearinghouse?

It is a good idea to have at least 2 different proposals put together.  Best case and acceptable scenarios, with justification for each.  This will give management a good idea of why you are proposing a particular clearinghouse/VAN.

Once you have gathered all the information you can put together the proposed budget for this implementation.

Whether this is an implementation of its own or part of a larger implementation, keep in mind to get all affected parties involved.  This will help eliminate issues further down the road.

Are there any additional questions you would consider for your requirements list?

avatar

Shopping for an EDI software package

by on March 12th, 2012

This is a very important step in the implementation of EDI.  This step informs several of your other decisions; hardware, additional software, staffing, etc.  Your previously identified data needs will also help to determine your software package.

When shopping for your EDI software package, make a check list of your requirements. Here are a few of the most common questions you’ll want to address in creating your list:

  1. Is it flexible?  If your data needs to be changed, how easily changes can be made to the software will be critical.
  2. Will you need additional hardware?  Your current hardware may not have the memory, storage, or speed required by the data needs and software package.
  3. Will you need additional software and/or programming?  Is the software flexible enough to integrate with your current system or is additional software required and/or do you need additional programming to integrate the data to/from your system?
  4. Will additional staff be required?  Do you already have staffing necessary for the programming of the software?
  5. Will additional training be required?  Chances are, if you are implementing a new software package then training will be required.  If so, what is the cost?
  6. Will it require on site personnel from the software company for installation?  If yes, is this cost part of the software purchase or is it an additional cost.
  7. What is the total cost of the software package?  Often this is a major factor on what software package you decide to purchase.

Once you have determined which software package will work best for your company you can put together the proposed budget of total cost including software, hardware, staffing, training, etc.  This will give you a good picture of what the total cost will be for implementation.

It is a good idea to have at least 2 different proposals put together: best case and acceptable scenarios, with justification for each.  This will give management a good idea of why you are proposing the purchase of a particular scenario.

What other tips would you follow when shopping for an EDI solution? 

avatar

Creating your EDI mapping layout

by on February 15th, 2012

In the previous blog we discussed the importance of knowing your data and business requirement needs. This is one place where that becomes important. If you already know your needs it makes it much easier to start your data mapping.

First you should contact your trading partner. They should have some type of functional specs which state what they expect to send to you or receive from you  or these are specs they will request from you.

Let’s begin with the layout of the transaction set for outbound data. I have found that the best way to start is to take the segments of the transaction set and put them in an Excel spreadsheet, keeping in mind to maintain the segment looping structures. Once you have the segments in your document you can then flesh them out further by putting in the individual data elements and sub-elements for that segment. As you are doing this it would be a good idea to mark each data element as to whether or not they are required, optional or situational. This will help you determine what needs to be present when creating the final product.

Now that you have the transaction set laid out in an editable format you can start marking those fields that fit the identified business needs. You can now use this document to cross reference to your trading partners’ specs as well. Keep in mind that if the data element states it is a required field you must have it populated with data.

Once this layout is complete it is time to start cross mapping to your database. Chances are you will be mapping to numerous tables based on the database layouts where each business unit utilizes their particular data, etc. These should all be reflected in your document and you should be working with your database administrator to make sure everything is being placed into or pulled from the proper table and field as well as whether or not any additional fields will need to be added to the database tables.

Now that you have your document complete you should review once again with the vested parties to make sure everything is as expected. This is a good time to identify any additional requirements or changes that need to be made before you start the actual mapping process.

You are now ready to start working with the mappers to create the transaction set.

avatar

Were you ready for HIPAA 5010?

by on January 16th, 2012

Hopefully everyone answered ‘yes’ and you had a smooth transition.  In this blog we will discuss some of the items we need to keep in mind when either transitioning or implementing EDI.

Whether you are getting ready to transition to a new standard or initiating EDI for the first time, remember the most important thing is to KNOW YOUR DATA NEEDS!

Knowing what data you expect to send and receive is one of the most important items you can establish.

First, review the standard for the transaction set(s) you want to use (some of the transaction sets used for healthcare are 835, 834 837, 270/271, etc).  Whether this is for Healthcare, Automotive, or any other standard, this is very important.  This will give you an idea of what data is available and what you can plan to accommodate.  Remember, just because it is in the standard does not mean you need that piece of data.

Once you have reviewed the standards, you need to get everyone involved: business users, a data mapper, a database administrator, trading partners and anyone else who might have a vested interest.  It might surprise you as to what data they will actually need and utilize.  Whether the data is used in the data warehouse or for reports it is important to identify your business needs.  Also, try to plan for future business requirements.  Just because you don’t use that piece of data right now doesn’t mean you might not need it as standards evolve.  You can start with a “wish list” and pare it down from there.  Keep in mind that just because you want to receive a particular piece of data, your translation software may not currently be set up to capture, your trading partner may not be able to accommodate, or your clearinghouse may not have that set up in their maps.  We all would like to have everything, but it is not always practical.

If you are converting to a new standard this is the chance to change things.  Just because it has always been done that way is no reason to continue – that may not be the best practice.  This gives you a chance to make things better and perhaps correct things that were not working right before.  If you are initiating a new transaction set, this is the perfect opportunity to grab the data you need and get everything set up right the first time.  This is where it is important to get the users involved.  As the person doing the research you may not think a piece of data is important, but to them it may be very necessary.

When you have identified all your data needs you are ready to move on to the next step – mapping the fields in the standards to your database.  We will talk about that in our next blog.

Have you initiated EDI? What data issues did you face? How did you overcome them?