[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Better-structured narrative output
From: |
Busser, Jim |
Subject: |
[Gnumed-devel] Better-structured narrative output |
Date: |
Wed, 30 Nov 2011 09:27:26 +0000 |
Is there any agreement that the following would be suitable?
- organize the output by encounter
- encounters sanely ordered by clin.encounter.started
- within each encounter the order could be sanely
s
Encounter and AOE information
Episode information (just description, not status / summary, dx
certainty)
S rows
O rows
A rows
P rows
' ' rows
- the date column need only show the start date (and optionally time) of the
encounter
- within the encounter, rows within each of {S,O,A,P} could have their original
sequence preserved by ordering by pk, even despite that a correction could have
been made (this is ok because the correction time can be shown in parens at the
end of the narrative output)
- before sorting by pk, can sort by {S,O,A,P} be achieved by
CASE WHEN soap_cat = 'S' THEN 1
WHEN soap_cat = 'O' THEN 2
WHEN soap_cat = 'A' THEN 3
WHEN soap_cat = 'P' THEN 4
ELSE 5
END
??
Lastly, with respect to the column
clin_when
which *has* meaning when purposely 'dating' something which might be entered
after-the-fact, such as in
clin.health_issue (past history item)
clin.family_history
clin.hospital_stay
clin.procedure
clin.substance_intake
clin.vaccination
clin.allergy (I need to come back to this at a later time)
should AFAICT *not* affect the sort order of *notes*, they should only inform
the sort order among *lists* where the clinical chronology among
back-referenced items of {past history, family history, procedures etc} becomes
of interest.
- [Gnumed-devel] Better-structured narrative output,
Busser, Jim <=