[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Establishing additional "stock" patients into the boo
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Establishing additional "stock" patients into the bootstrap e.g. for lab data |
Date: |
Fri, 29 Feb 2008 15:36:11 +0100 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
On Wed, Feb 27, 2008 at 09:06:29AM -0800, James Busser wrote:
> Presently in the data bootstrap I am aware only of Kirk, who
> demonstrates the following:
>
> - multiple names by which he is known
> - past history items (?)
yes
There is allergy data, a family history item about his
brother and two empty documents for him, too.
> 1. Other than Kirk, does the bootstrap contain any other patients and
> have they been created in order to illustrate or to support any
> functionality of which we may like people to be aware? I could add this
> to the documentation.
There is:
gnumed_v8=> SELECT firstnames, lastnames from dem.v_person_names ;
firstnames | lastnames
-----------------+-----------
Ian | Haywood
Cilla | Raby
Horst | Herb
Richard | Terry
Karsten | Hilbert
Sebastian | Hilbert
Hilmar | Berger
Leonard Horatio | McCoy
Kelley | DeForest
? | Spock
Leonard | Nimoy
Christine | Chapel
Julian | Bashir
James Tiberius | Kirk
James R. | Kirk
William | Shatner
Laborata | Testwoman
gnumed_v8=> SELECT distinct pk_patient from clin.v_pat_items;
pk_patient
------------
12
13
gnumed_v8=> SELECT firstnames, lastnames from dem.v_person_names where
pk_identity in (12,13);
firstnames | lastnames
----------------+-----------
William | Shatner
James R. | Kirk
James Tiberius | Kirk
Laborata | Testwoman
gnumed_v8=> SELECT * from clin.v_pat_items where pk_patient=13;
-[ RECORD 1 ]---+--------------------------------------------
modified_when | 2007-12-20 13:07:58.275937+01
modified_by | gm-dbo
clin_when | 2007-12-20 13:07:58.275937+01
is_modified | f
pk_patient | 13
pk_item | 15
pk_encounter | 3
pk_episode | 4
pk_health_issue |
soap_cat | p
narrative | used for anonymized import regression tests
src_table | lab_request
gnumed_v8=> SELECT * from clin.lab_request where pk_item=15;
-[ RECORD 1 ]---------+--------------------------------------------
pk_audit | 12185
row_version | 0
modified_when | 2007-12-20 13:07:58.275937+01
modified_by | gm-dbo
pk_item | 15
clin_when | 2007-12-20 13:07:58.275937+01
fk_encounter | 3
fk_episode | 4
narrative | used for anonymized import regression tests
soap_cat | p
pk | 2
fk_test_org | 3
request_id | anon: sample ID
fk_requestor |
lab_request_id |
lab_rxd_when |
results_reported_when |
request_status | pending
is_pending | t
That is pretty much all of it.
> 2. How do we best contribute patients, or other data, to the bootstrap?
That would need to be SQL statements in a file. Adding
something to the database and extracting that data with,
say, pgadminIII might work fairly easily.
Adding data with pgadmin3 and doing a data-only dump with
pg_dump will work well, too. The dump would need to be
edited but still.
> I
> am thinking that for the purposes of supporting and letting people try a
> lab test importer, it would be nice to provide patients for example
> "LABTESTS^BPATIENT", "LABTESTS^GPATIENT" who could be rigged so that the
> BC importer would successfully match some, but not others, and would
> support the demonstration of how matched data gets signed, or reassigned,
> and how unmatched data gets reconciled.
Sounds very reasonable.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346