Re: [Gnumed-devel] billing by GnuMed / TORCH / OSCAR

[Jim Busser]

On May 13, 2004, at 4:20 PM, Horst Herb wrote:
> On Fri, 14 May 2004 03:38, Karsten Hilbert wrote:
> > I am fine talking to the SQL Ledger schema directly
>
> Unfortunately not. In gnumed I wanted to make the schema the API 
> through the
> use of trigger functions etc. (business logic on the backend), but 
> it's not
> working out as originally intended. We still need some middleware, 
> hence the
> API would interface the middleware and not the schema directly.

Thanks for patience with this posting.

Do I correctly paraphrase the whitepaper at the URL and does it remain 
current:
http://www.gnumed.net/whitepapers/Interacting_with_the_Backend.html

> ... the service broker object gmPG will handle [connections and] a lot 
> of other complex issues such as gathering log in information
>
> ...any client action that wishes to modify the backend database MUST 
> request, from gmPG, a new separate connection which will be done under 
> the alias of the pseudo-user created for and associated with the 
> requesting user

- Would we then be wanting SQL-Ledger to call, through gmPG, to the 
"accounting related" service listed in
        http://www.gnumed.net/whitepapers/serviceslist.html

- Had work been done on an "accounting related" service, or is its 
current status only at the conceptual design stage (e.g. list 
discussion including Yudhvir's postings, plus what I have put up as a 
billing white paper)

- As SQL-Ledger is written in PERL, does that pose any problem for 
SQL-Ledger to be extended to call gmPG? If it ends up being the 
SQL-Ledger people who provide this extensibility, is it perfectly 
acceptable that it is done in PERL?

-  What about the "accounting related" service - can it be developed in 
PERL by SQL-Ledger people, or might GnuMed want (or need) to develop it 
itself, in Python?

- Is there more "middleware" that would need to be developed once gmPG 
and the "accounting related" service are covered off?

- I understand that in order to run efficiently, PostgreSQL needs to be 
configured, which AFAIK GnuMed provides, but if SQL-Ledger also needs 
to interact with PostgreSQL in order to administer SQL-Ledger's own 
accounting databases and tables, is there any potential problem of 
conflicting configuration requirements?

PS although the above hurt my brain, it will hopefully recharge in a 
day or so, putting me only temporarily in the land of Monty Python's 
"Gumbies"