[Gnumed-devel] Developing a billing use case that depends on being passed JSON data

[Busser, Jim]

A third-party billing solution provides an API that accepts data via http(s) 
POST in a JSON data format.

I was thinking about how this might (best) be handled within, and by, GNUmed.

Preliminary considerations …

- managing third-party login credentials … any of

        prompt user for unstored values
        and/or store user values in ~/.thirdparty.pass 
        and/or store praxis values in /etc/passwd

- billing configurational information … any of

        some in config files (e.g. billing.config)
        some in praxis settings (stored in database)
        some in user preferences (stored in database)

- data definitions by which to be able to reference and pass, to the billing 
software, the {patient, provider, invoice} information … any of

        referencing existing placeholders
        referencing new placeholders
        hard-coded in config files
        hard-coded in scripts

- once the required JSON content has been assembled … any of

        keep it volatile (in working memory, only, for on-the-fly passing to 
the billing program)
        write it temporarily to disk, in a /tmp/ file
        store it in a column yet-to-be-added to bill.bill_item

??

-- Jim