gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] clin.clin_narrative unique constraint and au specific imp


From: Syan Tan
Subject: [Gnumed-devel] clin.clin_narrative unique constraint and au specific importer
Date: Mon, 20 Feb 2006 12:07:52 +0800

whilst developing an au specific importer for gnumed , the clin_narrative.unique  column constraint failed

because narrative fields was too long and overran the index buffer.  

the proposed change is to add a after update,insert for each row and a simple plsql trigger function to check

if any existing rows matching the new row but use md5(narrative) instead of narrative in the check

( sort of defeats the purpose, as it is no longer a indexing constraint, but maybe it's faster slightly).

I've got it in the sql server scripts. Ok to commit it ?

I've also got a script package for importing a commonly used emr in oz into gnumed. So far, it imports doctors, demographics,

and progress notes.  It's main disadvantages is that it uses an intermediate postgres database, which could take up

quite a lot of space,  and also it takes more time to do a 2 stage import .  The users of the old system as registered as nonlogin

users, and show up in pg_role but not in pg_user.  This isn't currently being used, as the author's names appear in the old progress notes anyway, but it sort of normalizes better if modified_by shows the original author ?

ok to commit this too ? ( into importers, or into testarea ? )

 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]