Re: [Gnumed-devel] need assessment from fellow clinicians

[Karsten Hilbert]

> >Any soAp item can be a diagnosis and it can be marked is_aoe.
> 
> *Only* soAp and AOE items can be a diagnosis?
Hm, well, I guess yes. We don't currently enforce that,
however, at the moment (since I don't know how to do that).

> Can a sOap row containing anisocoria or ptosis also "be" a diagnosis?
Currently, yes. Intended to be no. Perhaps debatable. IMHO no.

> Or in order to qualify (be counted) as a diagnosis, must the condition 
> first be carried into a soAp or AOE row, and coded there?
That was my intention.

> And how is "is_aoe" meant to function? It was earlier suggested that 
> not all components of SOAP need to be filled in at every encounter.
Correct.

> An encounter may therefore contain no AOE until the user creates one.
Correct. Eg. until the user marks a soAp row to be is_aoe.

> So maybe until there is an AOE the soAp is assumed to be is_aoe and the 
> field is redundant
Yes, except that we can have *several* soAp rows. Only one of
which would be is_aoe. Or we decide to always use the
heuristics to declare the ?most recent or ?shortest soAp to be
the AOE.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346