-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: 837P service location details are not created when service facility and billing facility differ #7213
Comments
hi @juggernautsei , can't reproduce on master, what version are you testing? |
v7.0.2. I reported it because in the codebase it is the same code. I know that in master things can be fixed that has not made it git. I changed this line per the screenshot that I sent.
I posted this issue hoping this has been fixed already. I did search for this issue. You tell me. |
So, why is the code on github wrong? Pull down the release code and it is wrong. |
hi @juggernautsei , check out this line, https://github.com/openemr/openemr/blob/master/src/Billing/X125010837P.php#L990 it's not very good logic and needs to be improved in master when you get a chance, thank you it should be something like
|
Thanks @stephenwaite |
Describe the bug
When creating an encounter with a service facility and a different billing facility. The service facility is not being saved. The facility column in the database is filled with the billing facility number. This causes the incorrect billing.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Facility to be filled with the service facility number.
Client configuration
The text was updated successfully, but these errors were encountered: