Medical Billing - The Internals Of Software
We'll be covering how patient files get put into the system and how they are ultimately access by a biller and placed into a work order to be billed. While this seems like a very simple process, it is actually quite complex and requires a lot of indexing and cross-referencing.
Another thing we're going to cover is how a claim gets sent electronically. This is one of the mysteries of medical billing as this whole process is actually invisible. While you can see a patient being pulled to a page, you can't see a claim file being transmitted. How does it go? Where does all that data come from when you have so many record specifications? How does the software know to interact with your transmitting device, which is usually your modem? These and other questions will all be answered.
We will also discuss how forms are printed. How does the software know exactly where to place that patient name and address? How do you choose a form, as there are so many of them? Where does the data get pulled from when all you see in front of you is a patient name?
If you're curious as to how security is set and how the software knows to lock somebody out of a certain part of the system, we're going to cover that too. The many options that you have to security systems make this part of the system mind boggling to say the least. We'll do a detailed walk through of a DME security system and show how it works.
Wonder how your software knows how to read those automated posting files that come from Medicare with all your money tied up in them? No problem. We'll dig deep into the auto posting system so you can see exactly what is going on behind the scenes there.
What about those add-ons? How does the system know that you even have them or not? Remember, they are not part of the standard package and have to be added later. So what is actually done by the software maker to let your system know that an add-on is there?
Finally, we'll show you how the software manufacturer can tell if you have a valid copy of the software and when it's time to pay your maintenance fee on it. This gets into some really low level programming.
The above topics will all be covered in future installments. So get a box of lightly salted popcorn and enjoy the show.
We'll be covering how patient files get put into the system and how they are ultimately access by a biller and placed into a work order to be billed. While this seems like a very simple process, it is actually quite complex and requires a lot of indexing and cross-referencing.
Another thing we're going to cover is how a claim gets sent electronically. This is one of the mysteries of medical billing as this whole process is actually invisible. While you can see a patient being pulled to a page, you can't see a claim file being transmitted. How does it go? Where does all that data come from when you have so many record specifications? How does the software know to interact with your transmitting device, which is usually your modem? These and other questions will all be answered.
We will also discuss how forms are printed. How does the software know exactly where to place that patient name and address? How do you choose a form, as there are so many of them? Where does the data get pulled from when all you see in front of you is a patient name?
If you're curious as to how security is set and how the software knows to lock somebody out of a certain part of the system, we're going to cover that too. The many options that you have to security systems make this part of the system mind boggling to say the least. We'll do a detailed walk through of a DME security system and show how it works.
Wonder how your software knows how to read those automated posting files that come from Medicare with all your money tied up in them? No problem. We'll dig deep into the auto posting system so you can see exactly what is going on behind the scenes there.
What about those add-ons? How does the system know that you even have them or not? Remember, they are not part of the standard package and have to be added later. So what is actually done by the software maker to let your system know that an add-on is there?
Finally, we'll show you how the software manufacturer can tell if you have a valid copy of the software and when it's time to pay your maintenance fee on it. This gets into some really low level programming.
The above topics will all be covered in future installments. So get a box of lightly salted popcorn and enjoy the show.
<< Home