[Top][All Lists]

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

[Gnumed-devel] Idea... cloning patients to facilitate GNUmed demo

From: Jim Busser
Subject: [Gnumed-devel] Idea... cloning patients to facilitate GNUmed demo
Date: Thu, 09 Jul 2009 09:14:01 -0700

I think it could be useful to be able to demonstrate the evolution in a patient's record.

The idea is that the patient would start with a few past history items and one or two unattributed episodes but over time would have a more complex record but despite its complexity GNUmed will allow the fullness to be in the EMR tree while keeping it manageable in the problem list.

Exists there a method for the entirety of a single patient's record (but only that *single* patient's record) to be "dumped" from the database? Would that be useful to add to options in EMR > Export. ?

Relatedly, is there a method of then reimporting that patient? Presumably (hopefully) postgres would throw an exception on account of duplication of the patient unique ID unless the import method would assign a new patient ID, and preserve this across the related records being imported across the other tables. All other primary keys, despite that they had been dumped with these records, would all be replaced by newly-assigned (by the db) pks.

I would propose to name the original patient "one", clone them into "two", add to their EMR, export "two", reimport and rename as "three" and add to their EMR... you get the picture.

If it is work to create an import method to support the above, this same method could permit an exchange of patients between two praxes using the same db version of GNUmed. :-)

reply via email to

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