[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Inadvertent deletion of Procedure when Deleting episo
From: |
Busser, Jim |
Subject: |
Re: [Gnumed-devel] Inadvertent deletion of Procedure when Deleting episode |
Date: |
Thu, 1 Aug 2013 01:04:55 +0000 |
On 2013-07-31, at 5:48 PM, Jim Busser <address@hidden> wrote:
> Procedures are currently (1.3.7) required to be keyed to either a
>
> {Location, Episode} combination
>
> or a hospitalization.
>
> Since patients can have surgery at a hospital without a 'hospitalization'
> (without an inpatient stay) it is desirable to be able to input the hospital
> as a location, but this still then needs an episode.
>
> The problem of entering a "historical procedure" is that it is not enough to
> create the Health Issue (Past history item) which demanded the surgery, for
> example that they had been involved in a motor vehicle accident in 2009.
>
> You have to also create an episode, which defaults to "now" and "active", and
> if you then input a procedure, with its proper date from 2009, you eventually
> observe in the EMR tree this 'active' episode and which you neither really
> want and which you risk to think that you do not need, so that if you then
> delete it, since you care only to maintain in the record the historical MVA
> from 2009, you end up (without warning) deleting the Procedure as well.
>
> Can it be possible for a Procedure to attach (be keyed) to a Health issue, so
> that it does not become necessary to create a historical episode to which to
> attach a procedure? Especially since the procedure has a date.
>
> -- Jim
It appears that the procedure was not deleted, since I can still find it at the
bottom of
select * from clin.procedure ;
but the problem now is that the episode to which it is keyed
fk_episode = 397
no longer exists:
select pk from clin.episode WHERE pk = 397 ;
pk
----
(0 rows)
-- Jim