In the module that I am building to be able to enter hospital visits in to the system without having to go to each patient chart to open an encounter. I ran across an interesting fact in the program design. @stephenwaite , when the code gets the billing data from the billing table. It uses the encounter date for the date(s) of service, rather than the individual line items’ dates. When filling out the native fee sheet, there is not an associated date of service for each line item in the form even though the database supports this. The UI does not support the ability to enter different date for each line item of service as when being at a hospital on different days. The native fee sheet would require the user to input 6 encounters for each date of service at the hospital.
I ran into this when creating our module. I checked the database, each line item has the corresponding date of service at the hospital but the HCFA (pictured above) has only the encounter form date on there which will be rejected if submitted. Now, the question is how are we going to cross this bridge together? I can simply change our code to match what we are needing and go on my way and manage that change forever. But I don’t like doing that if at all possible. @stephenwaite, what would be the best way to handle this?
Hi @juggernautsei, how does the database support different dates of service?
Hi @stephenwaite, marry this screenshot of the billing table data with the HCFA form above. You can see that each line item has a different date. But on the HCFA. There is one date which is not any of these dates. The goal is to submit as many dates of service on a single HCFA as allowed.
In the code, this is applied to every line of service.
$out .= "DTP" . // Date of Service. Page 435.
"*" . "472" .
"*" . "D8" .
"*" . $claim->serviceDate() .
"~\n";
public function serviceDate()
{
return str_replace('-', '', substr($this->encounter['date'], 0, 10));
}
The encounter date is applied and not the line item date. To make this compatible with sending in up to 6 different dates of service on a single HCFA, the date from the line item would need to be used and not the encounter date. The native fee sheet stores the encounter date in the line item date field. However, that does not have to be as I have shown in the database screenshot. The user wants to take advantage of being all to have as many dates of hospital visits they are allowed to on one HCFA / 837
There is a way to do this with backwards compatibility.
Isn’t that date the date it was entered into the fee sheet?
Since the fee sheet does not actively allow a user to selected a date for that field. My assumption is that date is the day the line item was entered. However, in my quest, this would work fine because the date will be utilized by my module to complete its function the fee sheet can continue to enter what date it enters in this field since functionally it has no use I can find in the billing process.
It’s better to add a service date field to the table because that date is used for historical purposes for tracking the lifecycle of the claim.
Ok, I will add a column to the table. Thanks for the info.