HIS billing is divided into three parts. Front-end (transaction entry), middle-ware (accounting package and ebilling), back-end (sql tables). Each of these parts can be further broken down as in on the front-end there is order entry, order communication, facility service item list, formilaries, order bundling, order dependency/contraindication checking and other functions. Billing middle-ware includes department budgeting, materials management, facility accounting and both reporting and interfacing to a way to get a bill to appropriate payers. The back end of all this includes the tables to hold all this data as in a facility list, department list and individual transaction items.

While each the parts of a "billing" system can be developed separately, I don't think they should be developed in isolation. I'm new to Care2x and would like to help with what I think is the greatest need. Care2x needs what I might call a formal "Master Facility Service Item List" and a system of order/transaction communication between modules. No billing system or accounting package can be implemented without these.

Is anyone already started on a initiative like this?

Will Simpson
Moscow, Idaho


------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Care2002-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/care2002-developers

Reply via email to