Skip to main content

Customer Experience and Design

Determining EDI hardware needs

It is very important to make sure you determine your hardware requirements if you are implementing EDI for the first time, changing your EDI software or your EDI data needs.

If you have already met your needs then you’re ahead of the game. If not, then once again make sure you get all key stakeholders involved to make the determination as to what your expected needs now and in the near future may be. Always try to plan for the future and not just your immediate needs. One of the first things you should do is a requirements gathering. You might want to consider doing a JAD (Joint Application Design) session. Some of the questions you might need to address are:

  1. Do you have all the processing power needed?
  2. Will your system accommodate the new software?
  3. Will your system accommodate the new data needs?
  4. Do you have the communications setup needed?

These are just some of the issues that need to be addressed. Everything depends on your processing requirements and needs.

After the requirements have been compiled, have another meeting with the key stakeholders to review. This will help to clarify any ambiguities. Once everyone has agreed to the requirements you can determine what, if anything, you will need to buy. You can then put together your RFP to send out to vendors.

The time spent on the front end gathering detailed requirements helps to eliminate unnecessary delays and affects system quality.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Deborah O'Rear, Sr. Technical Consultant

Deborah O’Rear is a business-focused, outcomes-driven consultant with more than 15 years of healthcare industry experience. She has a vast depth of EDI and BSA knowledge to support healthcare clients. Deborah is well versed in articulating, clarifying, and writing business requirements, establishing implementation strategies, QA, user stories, and testing.

More from this Author

Follow Us