[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] gmContact signal --> referrals
From: |
Ian Haywood |
Subject: |
Re: [Gnumed-devel] gmContact signal --> referrals |
Date: |
Fri, 4 Jun 2004 11:48:40 +1000 |
On Fri, 04 Jun 2004 11:21:26 +0000
sjtan <address@hidden> wrote:
> The org['subtype'] field is not well abstracted though, as it means
> 'department'/'branch'/'division' with an org object, but
> 'cardiologist/plumber/physiotherapy' with a person object.
The unified object needs a common specialty attribute,
so searching for "cardiology" can give us both individual cardiologists AND
cardiology group-practices, AND the cardiology department of the local hospital.
[Aside: true specialty group practice is still fairly novel here Down Under,
most specialists
run an individual practice although they may share rooms. However, it is
becoming more common,
certainly most senior registrars I've met are keen on the idea, so it's
something we are going to have
to support]
> There's
> probably a need for a ['fullname'] attribute, as it then gets the
> hospital name and department name for a sub-org, instead of just the
> department name , which might be the same for a number of hospitals (as
> an example).
Good idea
> to make it sql simple ( and not gmOrganisation dependent, and
> current phraseWheel compatible) a personOrg sql view might be better.
Using an SQL UNION construct to unite two queries on both orgs and identity in
the backend, yep,
like it already.
Ian
--
PGP public key E750652E at wwwkeys.pgp.net
9BF0 67B7 F84F F7EE 0C42 C063 28FC BC52 E750 652E
pgpsCZqNwYo_y.pgp
Description: PGP signature