Menu
▾
▴
#46 Patient Statments - Needs Client side and Multi-OS Support
The current custon/statements.php.inc is unix server-side only and must be hand edited to be useful. The follow changes are in progress at mi-squared.com
First pass:
1. Modify the overall process to support Multi-OS (like backup.php)
2. Modify the overall process to be client centric as a optional configuration. That is; the results of the processing run are available on screen, printable and as down loadable text files.
Second Pass:
3. Add the ability to create and use templates as in the Letter application
4. Add the ability to create nicely formated printable statements in PDF, HTML-CSS and down loaded as delimited text records per some of the existing reports
5. Add archiving of date stamped statement output on the server (like the claims edi directory)
6. Add a patient note indicating that a statement was produced on ‘date’ and the basic balance represented there.
-Tony
Forgot to add that it will get the return address from the facility marked as the billing location. Remit to, if different will need some thought, perhaps the address book? -tony
The attached patch is the first pass support. It adds configurable temp dir and print commands and a new feature to let the user download the resulting text file locally to be handled anyway they see fit.
Next up... reading the return address and clinic location address from the facilities table.
-Tony
Bill or Tony?,
The goal is to have your patches be directly commitable so we can give you commit access to our cvs. So gonna be more strict on your patches.
Please re-submit patch following below tenets for internationalization (xl function calls):
For coding new xl functions:
1) No trailing or leading whitespace. (so would do trailing space outside call like this xl('Demographics').' ';)
2) No variables. (so if variables, need to separate xl('hey').' '.$name.' '.xl('this is cool');)
For previously coded xl functions:
1) To be safe, just leave them be (the above rules do not apply). This is because some situations warranted placing variables within the function.
For further reading on the xl function the bottom of the Internationalization manual in the configuration section in the wiki goes over the xl function. Especially important to understand the concept of the second parameter (echo flag).
Also, for the globals variables, just pretend you are in the development tip (the temp dir is already set), especially in regards to the print command (are there os specific commandline print commands, if so could use the current OS specific section in globals to set the most likely commands for each).
-brady
I have attached an updated patch for dev tip. Still want to add lookup of billing facility, etc , but this will do it for the now. I included the entire statements.inc.php as it's nearly a complete replacement.
I guess I put in the patch area this form a has not attachment option.
Dang, it's getting late, or I'm going blind. File is attached now.
I have attached a final revision of the statements patch enhancement and will commit it tomorrow after I take a deep breath :-)
--Tony
Statements have MutiOS printing and download option
Brady - please check to make sure I did this commit correctly and assign this ticket back to me, since there is more to it than I have committed so far.
Checking in custom/statement.inc.php;
/cvsroot/openemr/openemr/custom/statement.inc.php,v <-- statement.inc.php
new revision: 1.5; previous revision: 1.4
done
Checking in interface/globals.php;
/cvsroot/openemr/openemr/interface/globals.php,v <-- globals.php
new revision: 1.111; previous revision: 1.110
done
Checking in interface/billing/sl_eob_search.php;
/cvsroot/openemr/openemr/interface/billing/sl_eob_search.php,v <-- sl_eob_search.php
new revision: 1.32; previous revision: 1.31
--Tony
Tony - the commit was correct. happy almost new year. -brady