[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] demographics gnumed to oscar
From: |
James Busser |
Subject: |
Re: [Gnumed-devel] demographics gnumed to oscar |
Date: |
Tue, 4 Jul 2006 03:17:13 -0700 |
On Jul 3, 2006, at 1:05 AM, Syan Tan wrote:
currently , I am using a gnumed demographic view that uses
pk_identity for the
demographic_no, which is a primary key in oscar demographic table.
I was thinking that as long oscar was initialized with a high
enough primary key start number,
it could coexist with the gnumed demographics, so there's no
messing around with oscar side
external id tables or columns for pk_identity.
Oscar (mysql's) autoincrement can be reset
mysql> ALTER TABLE tbl AUTO_INCREMENT =
Are you thinking to sync them so that the gnumed field
dem.identity.pk gets written into Oscar's demographic_no?
Otherwise, there is a demographiccust table with cust4 field,
maybe use a cust5 field for gnumed pk_identity. The simplest is to
do would be to make sure oscar demographic_no
occupy a different number range to pk_identity.
I am missing something... if you were wanting to drive demographics
from GNUmed then why could GNUmed not write its dem.identity.pk into
the Oscar demographic table? Or were you taking the view that someone
may have already been running Oscar and therefore GNUmed would have
to copy all existing Oscar demographic_no into GNUmed as an external id?
The idea eventually is to check returned appointment search
identities,
and if they do not exist in the oscar demographic table, then they
are simply inserted. This might enable
billing eventually, if someone can explain whether provider_no is
important
Could gnumed also write its dem.staff.pk into Oscar as the provider_no?
maybe a gnumed side external_id_type for oscar providers;
gnumed isn't incorporating the idea of one responsible provider per
patient yet, is it ?