sunsetsystems wrote on Wednesday, June 17, 2009:
This is to let y’all know that I am modifying the Fee Sheet and other modules to support specification of service provider by service line. The “main” provider at the encounter level will still be there, and will serve as the default where a provider is not specified at the line level.
I don’t think this will cause any headaches, but if you have any questions or concerns just ask.
sunsetsystems wrote on Thursday, June 18, 2009:
I am starting on these changes. Here is the tentative list of modules that I’m working on:
custom/import_medics.php
interface/forms/fee_sheet/new.php
interface/forms/CAMOS/content_parser.php
interface/patient_file/pos_checkout.php
interface/billing/sl_receipts_report.php
interface/billing/billing_report.php
interface/billing/sl_eob_invoice.php
library/report.inc
library/coding.inc.php
library/Claim.class.php
library/gen_hcfa_1500.inc.php
library/gen_x12_837.inc.php
library/sl_eob.inc.php
sl_convert.php
sql/3_0_1-to-3_0_2_upgrade.sql
sql/database.sql
tmccormi wrote on Friday, June 19, 2009:
Rod,
No need to work on custom/import_medics as that is very specific to me and I have rewritten it extensively already and we are about to rewrite it again to make it fully automatic without user intervention.
Now as to the rest… what does "working on them mean?" do you have a specific list of enhancements you have planned? Nearly All of those are programs that we have made changes to for our customers here. It would be good to know what you are planning so we can coordinate specs and effort.
–Tony
tmccormi wrote on Friday, June 19, 2009:
I think I read that out of context … if what you are doing to those modules is “service provider by service line” then cool. Still don’t need the import_medics changes though.
–Tony
sunsetsystems wrote on Monday, June 22, 2009:
Right, this is only about service provider by service line.
Should I delete import_medics.php from the repository, or do you want it updated with your current version?
tmccormi wrote on Monday, June 22, 2009:
It’s too custom to be useful to anyone else. You can remove it. Some day I’ll make a generic example out of it for importing complete medical records via XML. It has some value for that and I have derived a number of other import modules from it.
–Tony
sunsetsystems wrote on Tuesday, June 23, 2009:
These changes are now checked in. They pass the “smoke test” but extensive testing is not yet done. I’d be interested to hear from anyone who wants to try it out and see if their claims come out OK!