Re: MediSnap - GPLv3 medical photo system - just released
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Bhaskar, K.S wrote:
> [KSB2] Yes, but that only pushes my question back one level! If
> different practices are sharing a server but isolated from each other,
> would they share a common metadata database. The picture at
> http://medisnap.sourceforge.net/installation.html shows one common
> database. Is a typical installation one that would make Practice A
> aware that Patient P is also seen by Practice B?
>
> Regards
> -- Bhaskar
you could use separate databases _or_ a common database.
Anyway, if you send different patient-numbers via GDT code 3000 from the
both systems, then the same patient (which then would have 2 different
numbers) would also get 2 separate accounts within medisnap.
A solution might be to use some kind of translation table of patient
numbers from system a to patient numbers of system b.
Be careful if both systems might use same numbers for different persons,
that could indeed put the photos of both persons into the same account.
A simple solution for this would be to prepend something like
'system-a-<patient-no>' and 'system-b-<patient-no>' so there will never
be equal identifiers.
hope this clarifys your question,
jan
- --
publictimestamp.org/ptb/PTB-10963 haval 2011-01-21 14:47:46
17B5891712A8ADE362046EDCF21895A5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAwAGBQJNOcQBAAoJEI0XMg7eH/QczPkP/1USNnhkDZelrgAX/QRRiVDQ
mu+n4PDOJGdW90GcCjZtNsC1G9TE1LjehjSynmcwT9DxtlnC92PMACZVa7ZrbhdQ
MEItpfaNJoIp7qjky+eqxbqeChwAvnxxFqy0Nwf1rGssa4gyknDtLfXdkgX1/C03
AEiFKdslfvLLiARypdpXhzRNw+GoFxemMSfYW5zAC7oF6mDnAsiGzUkSRm/kwwA2
/88iKk9M+5mYf+AvqfDaYRyeYfZDDNPgAxAWOsLbHLbunLPGCM41AyqmBB3DmKgO
zm2ntwGjfTDFbGIMoH+VJL4eg6ef+lIvPmBxB+cybP4GXTceG+oH9fFJSMhunbtC
n25pb2eSIjG4BSAlsV2KA3INTS0NiCPyIasLx1Omh+6kKXct0uoeq3aDvhxHJ9KX
TItKS2mrra9+MohPUz7lljaBWJIycosT7SBBKjMv+0dAcq6YqZLiBZ6ov3sQRaBH
InEL81PDVeOEbhhlG9Pov/pwT7UghYbYyl5EfhxuxZwaoTqdmt6lVS4e3ImEr61E
xzLchPyk7HlFqZNVv54a0LvPkaE0VovsqOdwuuZ+0K2KswX+kpYtKaht3Xph/IGP
h73usyXBj0lA5+Lr8q1SWBBhjU/SWCMTIMT6vVBoRCBRKIXnO47LHi10sfs7Fl7B
t/lnKtqnghed6DrPijlM
=3uPD
-----END PGP SIGNATURE-----
Reply to: