On Wednesday, September 4, 2013 5:06:28 PM UTC+5:30, Luis Falcon wrote:
>
> Dear Kaushik and all 
> On 09/03/2013 06:48 AM, Kaushik S wrote: 
> > 
> >  
> > 
> > 
> I believe that you should integrate all the information of the patient 
> into the GNU Health instance (demographics, different IDs, ... ). For 
> what I see, having that extra legacy DB will create issues and extra work. 
>
> All the best, 
>
> -- 
> GNU Health : The Free Health and Hospital Information System 
> http://health.gnu.org 
> Twitter: @gnuhealth 
>



Thanks Luis. The external database has been around for many years. This 
contains the details of all permanent members in the community - their 
name, address, telephone, email, status, whether present, in future the 
contact person. 
All other databases in the community should refer to this. We have a way to 
make sure the id is unique. However, the database is something to put up 
with.  
We have a 3 line python interface that can talk to the ldap server and get 
the latest changes in personal details.   The original developer who worked 
on this, wrote an ir.cron to keep the personal details of the members 
updated. I would like to get the cron to work.     I am thinking there is 
something simple like a daemon we need to run or some other configuration 
thats missing. 
 

Reply via email to