The question is do you want physicians to be empowered at the level of
interface design or storage/logical data structure design?
John
At 05:09 PM 5/11/01, you wrote:
>On Fri, 11 May 2001, Dr Nikki Ellis wrote:
>
> > <snip>
> > >
> > > If physicians can define tables, or a functionally equivalent task, then
> > > everything else is fairly straightforward.
> >
> > <snip>
> >
> > Why tables? They suggest a need for a relational design... why not ask
> > physicians to define objects and utilise the unique power of OO design for
> > medical applications?
>
>I agree. Furthermore, I think tables are unnecessarily complex.
>How often does a "real" clinician use a "table" to collect data?
>
>No, the most popular "interface" for data collection is still the paper
>"form". In the OIO system, clinicians define "forms" that look and work
>like paper forms. To collect data, they choose a form and complete it -
>just like what they do with paper forms.
>
>Best regards,
>
>Andrew
>---
>Andrew P. Ho, M.D.
>OIO: Open Infrastructure for Outcomes
>TxOutcome.Org (hosting OIO Library #1)
>Assistant Clinical Professor
>Department of Psychiatry, Harbor-UCLA Medical Center
>University of California, Los Angeles
