Avoiding the headaches and high costs of consolidating healthcare data.
Many entities operate in the space serviced by the ANSI X12 HIPAA EDI transaction set.
Common documents are:
- Benefit Enrollment and Maintenance (834)
- Claim Payment Advice (835)
- Professional and Institutional Claims (837 P, 837 I)
- Various status inquiry documents (270, 271, 276, 277)
Here are four easy ways to mitigate the costly risks associated with HIPAA PHI Data.
If you handle healthcare data, you’re most likely very intimate with HIPAA and the Privacy Rule. If not (or not enough), you’re vulnerable to costly penalties ranging from $100 to $50,000 per year, and could face jail time (depending on the severity of the breach).
These penalties can be avoided with some simple steps, but let’s start with the basics.
Are you being required to send out (214) Shipment Statuses of your trucks?
Let 1 EDI Source help you with your Shipment information. We can display your Load Tender (204) in our PartnerXchange EDI system. It will provide you with specific information pertaining to the shipment, when to be picked up, and the date and time to respond by.
Does your Retail Trading Partner require your business to be EDI Compliant?
Let 1 EDI Source help you, it’s as easy as clicking a button. With EDI/PX™ you will be able to easily become EDI compliant.
With EDI/PX all you will have to do is sign on to the website, and you will have everything you need at your fingertips. Your Purchase Orders (850) will be displayed on the webpage for you to print or view. It can display various information such as: PO Number, PO Date, Ship to name and address, Date to be shipped. It will also contain detailed information about the parts being ordered: Part Number, Quantity, Price, UOM, and Description of the goods.
1 EDI Source, a leading provider of electronic data interchange (EDI) software and Software-as-a-Service solutions, provides Ad-Hoc Reporting for EDI
Ad-Hoc Reporting software, EDI/HQ™, combined with the company’s previously released advanced mapping designer and engine, is the latest in a series of upcoming enhancements to help businesses of all sizes do more with their EDI data. The new ad-hoc reporting enhancement allows users to build a nearly unlimited number of reports from EDI data, transaction history and trading partner configuration information housed in the EDI software. With EDI/HQ SmartFilters, businesses can restrict the report contents by trading partner, transaction type, date created, etc., providing a truly custom reporting experience. Read More
Trading Partner decides they don’t want to transmit the 997 Functional Acknowledgments to you…
…they want to save some money on their VAN costs, thinking that the 997 is a waste of time.
There is so much more to a 997 than you might think….as it is called a “Functional” Acknowledgement. So what are its’ functions? The 997 Functional Acknowledgment EDI transaction, a necessary piece of the EDI process, informs recipients that an EDI transaction has been received. This is important when you send out 810 Invoices to get paid and you want to make sure your customer has received them in a timely manner!
Many systems commonly reconcile the incoming and outgoing 997, verify that acknowledgement reporting has occurred inside a window of time (usually 24 hours), and confirm that all EDI transactions were accepted. Read More