Hello!
Here at Magma Soft we are moving slowly forward with adapting FreePM
to the (weird) Nicaraguan Health Insurance System.
We are sorry, that our contract with the clinic we are working for is
breaking, but we hope to find other "Empresas M�dicas" interested in
the product.
In the following weeks we will publish our "Version" of FreePM on the
Magma Soft's Web-Site:
http://www.magma.com.ni
Together with the manual in Spanish we are preparing for it.
Our needs are more on the administrative and less on the medical side.
Also, we are using the older Version of FreePM, have made a lot of
fixes and addons, so we are surely heavily incompatible by now with
the real FreePM :(
Especially the "localization" we make is a simply copy and translate
process, as at the time of starting there was no localization
procedure established.
Hopefully, our work will at least serve as example.
Now to more details:
Database speed:
---- Only read if you need a background for the following part -------
We have a special requisite in Nicaragua, that requires to register
"afiliation" of a pacient to a Clinic. Any assured person is
afiliated to an "Empresa M�dica Previsional", where she/he gets
atended. There are also "Beneficiarios", which are children up to 6
Years and the Husband. The afiliation is a one year contract that is
firstly taken up by the Clinics Insurance Clercs, which reports
weekly (via a DBF-File, and some printouts) to the Public Insurance
Institute (INSS) in the capital. INSS gives a modified DBF-File back,
where some people may be deleted (asigned to another Clinic) or some
other may be asigned (from another Clinic).
----- Here comes the programming problem ------------
So we need to make a query to the database, listing all Patients
asured by INSS and afiliated to our Clinic *without* the children and
the husband.
So I am doing something (ugly like this):
---------
loop over all EMR's in all emr-Folders
where "relation_to_assured==Self"
loop over all Patient-accounts
if you find the Patient-account with the same Code as the EMR
Extract the wanted data from the Guarantee-property-sheet
endloop
endloop
---------
The last step is a cold-blooded guess, as a person can have various
Guarantee's and we should check which is the one coinciding with the
person itself.
---------
This double loop maybe is innecesary and can be programmed in other
way, but I don't know how to lookup the Patient-account folder
directly.
it looks something like:
<dtml-with emr>
<dtml-in ...EMR's>
<dtml-let [extract "-code" from the id and asign it]>
<dtml-with URL[2] - go up to levels>
<dtml-with accounting>
<dtml-with patients>
<dtml-in ...PA's>
<dtml-if PA-code == EMR-code>
<dtml-let [remember secuence-item in rec_id]>
<dtml-with rec_id>
<dtml-in ...Guarantor>
<dtml-with sequence-item
do what has to be done here to
extract the data and format it
nicely
</dtml-with>
</dtml-in>
</dtml-with>
</dtml-let>
</dtml-if>
</dtml-in>
..... you see why I don't like this?
Anyway, the way it is programmed actually it takes about 10 to 25
minutes to yield a list of all Afiliated Patients, on a Database with
only about 200 Patient records and 140 Afiliated.
Imagine if we manage 2000 Patients!
If there is no smarter (and veeery faster) way to get this information
out of Zope, I will lose faith in Object Oriented Databases.
By the way, it's a big handicap for us, to have to duplicate the
Guarantee's information about 3 to 6 times every time we create the
EMR / PA for a Beneficiario (families are big here :).
--------------------------------------
At last, on our way through FreePM we found out, that we could not
create some "printouts", because the "stripogram" module could not be
found, especially in the prescription module.
We use Debian Gnu/Linux, and this tiny program is not included.
I have the impresion, that you substitute it in other areas with
labreport, but you'll know better.
Maybe the dependency on stripogram could be completely eliminated, or
it should be stated in the installations Guides and eventually be
included in your installation packs.
----------------------------
Until today I read the Mail on the new Beta Release. I agree with
data and code separation practice (although it hurts me badly at my
site). The need to export/import updates yet made me think about a
way to completly separate the code from the patient data, so you can
syncronize code on diferent client's sites, without affecting the
stored data.
--------------------------
Best Regards,
Jorge-Le�n
_______________________________________________
FreePM Support List
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freepm-discuss
