[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Episodes and imported path / lab data
From: |
Jim Busser |
Subject: |
[Gnumed-devel] Episodes and imported path / lab data |
Date: |
Fri, 01 Jul 2011 00:22:54 -0700 |
If (at a later stage) lab requests would originate from GNUmed, it could be
keyed with a particular episode of a health issue and the returning
test_results could inherit the same episode key.
However, do we especially want each test_result to be associated with one
particular clinical episode? For any instance of more than one problem getting
care (at the same encounter) when the tests were ordered, the test results can
easily relate to more than one problem.
A query could be managed without particular episode attachments, because the
encounter at which the test-results were imported will presumably overlap the
time period when the episode(s) were active.
I had been thinking whether to propose that every patient have created for them
(during test_results import) an episode of description
'unassociated lab data'
which can always be "closed" and simply be added-to with each import. But then
I thought "well, what does this really achieve?".
So… may column fk_episode be removed from table test_result ?
-- Jim
- [Gnumed-devel] Episodes and imported path / lab data,
Jim Busser <=