[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: rschedule
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] re: rschedule |
Date: |
Sat, 1 Jul 2006 10:58:52 +0200 |
User-agent: |
Mutt/1.5.11+cvs20060403 |
On Sat, Jul 01, 2006 at 01:38:42AM -0700, Jim Busser wrote:
> - extract the master Oscar id
> - pass it, via XML-RPC, to notify GNUmed that a patient has been
> selected, and cause GNUmed to test whether the patient exists and
> accordingly move to them, or to create them from the Oscar
> demographic info
...
> I think the above would be much tidier than to aim to store in
> Oscar's appointment table (or any other Oscar table) any external
> references. I believe GNUmed already has a place in its backend that
> could be borrowed to store the Oscar patient id.
Not so much "borrowed" but much rather *designed* for
precisely that sort of thing.
The tables are
dem.enum_ext_id_types
dem.lnk_identity2ext_id
(yes, they should be named "trait" instead of "ext_id")
The cIdentity business class handles such external IDs.
Our patient searcher can search on it.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346