[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
EMR tree was Re: [Gnumed-devel] Notes editor 0.4.6-1 feedback and sugges
From: |
James Busser |
Subject: |
EMR tree was Re: [Gnumed-devel] Notes editor 0.4.6-1 feedback and suggestions |
Date: |
Mon, 22 Jun 2009 13:18:16 -0700 (PDT) |
Rogerio said
> > I prefer the way it is ... it is easier to scan the list of AOE to remember
> > things that to scan it to see how many times she called in from telefone
i.e. seeing little value to be shown (if we would change to):
> > > However, that'll make a list of encounters down the left:
> > > 1.1.2003: in praxis
> > > 2.1.2003: in praxis
> > > 4.1.2003: in praxis
> > > 6.1.2003: home visit
> > > 9.1.2003: in praxis
> > > 16.1.2003: in praxis
> > EXACLY !
EXACLY was Rogerio's agreement with your own hesitation on "type"
He prefers date: AOE... and I am happy to assign to "type" the lowest priority
weighting.
More than AOE though, I am attracted to potential greater utility of the
per-problem soAp. It would seem to me that when looking down a per-problem EMR
tree, when examining -- inside any one problem -- a series of dated encounters,
with the task of brain-parsing the list for the visit(s) most likely containing
what we we are looking for, my prediction would be that the visual evolution of
(any) change in that problem's own Assessment (soAp) is going to be more
granularly helpful than AOEs as the latter are abstrations, replicated across
multiple problems touched.
I would therefore vote for (suggest):
> > soAp if exists
> > > else AOE if exists
> > > else RFE if exists
> > > else type of encounter
- EMR tree was Re: [Gnumed-devel] Notes editor 0.4.6-1 feedback and suggestions,
James Busser <=