X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 80F64D1CA42 for ; Wed, 28 Jul 2004 00:27:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02361-08 for ; Wed, 28 Jul 2004 03:26:54 +0000 (GMT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id A8062D1CAD4 for ; Wed, 28 Jul 2004 00:21:58 -0300 (ADT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by www.postgresql.com (Postfix) with ESMTP id 2BE38CF7C0D for ; Tue, 27 Jul 2004 22:32:44 -0300 (ADT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id i6S1TIt15638; Wed, 28 Jul 2004 10:29:18 +0900 Message-ID: <001f01c47442$4dd673a0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "Kenneth Gonsalves" , "Karsten Hilbert" , References: <1090325769.3241.27.camel@dicaprio.akademie1.de> <002801c472fc$be62af40$7201a8c0@mst1x5r347kymb> <20040726223441.T699@hermes.hilbert.loc> <04072711335024.01150@thenilgiris.com> Subject: Re: surrogate key or not? Date: Wed, 28 Jul 2004 10:29:19 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/233 X-Sequence-Number: 18485 > > One thing we ARE looking for in our records is the ability to > > find groups of patients by arbitrary criteria since one day > > I'll have to find all my patients whose father took a statine, > > whose second-born child suffered a bout of neutropenia 2 weeks > > after birth and who started being on the pill at age 14. > > Because they'll have a 3fold increased risk of lung embolus. > > Unless monitored for clotting factors every 6 months. Which I > > will have to do from now on. Get my point ? :-) > > couldnt you do something like, let them write the 'long flaky text', and at > the same time mark a certain number of key words or key phrases which could > be stored and retrieved? I was thinking along similar lines. On one hand, you need the "long flaky text" (love that expression), on the other, you want to ensure that you can locate appropriate data, and that the required details are available. By available, I mean that it was entered in the first place, and that it is retrievable. I imagine a system whereby you define keywords and attributes for them (attributes would be an episode date, or dosage, etc). The memo, is checked for keywords and the doctor prompted to supply the attributes for them. If your parsing was smart, and the memo formated a little, you could conceivably pull a lot of this out of the memo as defaults. The processing could also be done retrospectively by an intern or researcher, but I imagine it would be best to have the doctor do it at the time. Just some vague ideas anyway. This may of course be much more work than anyone wants to get into... I don't have much experience with text searching systems, but something reasonably sophisticated would probably get you there. Regards Iain