Horst,

I agree with you completely. To think that the whole of medicine can be "standardised" 
is  to set forth on a never ending, increasingly frustrating quest. There are too many 
areas. In a sense let us start with the end user and tell them to collect data, and 
let them collect data in a way which makes it easy to build communicating portals for 
sharing information in a flexible way. Let the programmers worry about getting them to 
communicate rather than trying to tell them HOW they should communicate.

regards

Nandalal

----- Original Message -----
From: Horst Herb <[EMAIL PROTECTED]>
Date: Wed, 24 Dec 2003 14:14:43 +1100
To: [EMAIL PROTECTED]
Subject: Re: hub, spoke, new Esperanto for healthcare, was Re: form-to-form 
translator, was Re: Solving the data type   problem, was: ODB vs. RDMBS was: OIO-0.9.1 
released

> On Wed, 24 Dec 2003 12:32, Andrew Ho wrote:
> > 3) My proposal is to build hubs from the bottom-up - based on OIO forms
> >    that are in-use. Analagous to building a dictionary - opposite from
> >    building an "universal" language. Let's learn something from
> >    the failure of Esperanto,
> 
> A MAJOR point, and I see this failure happening all over again and again, be 
> it in the domain of coding (where countless professionals have been mucking 
> around for decades in the quest for the ultimate coding system instead of 
> settling for a thesaurus like growing dictionary of terms) or in the domain 
> of health record architectures
> 
> I'd wish we would settle for small independent modules all communicating via 
> *simple* protocols (like XML-RPC via HTTPS or Jabber), using self-growing 
> terminology dictionaries.
> 
> I don't believe we need a monolithic architecture. All we need is well defined 
> APIs to extract and submit data.
> 
> I don't believe these APIs need to be consistent/synchronized/monolithic:
> - there is no reason why demographic information should be dealt with in the 
> same way as for example vaccination records or a cardiovascular examination 
> or drug interactions.
> 
> If our systems get too complicated, we will never get there. With all due 
> respect, the ADL of OpenEHR looks to me like a further complication rather 
> than simplification for example - yet another mini language where I believe 
> that using existent versatile markups (like YAML) could have the achieved the 
> same goal with less steep learning curve and the benefit of human 
> readability.
> 
> Horst
> 

-- 
______________________________________________
Check out the latest SMS services @ http://www.linuxmail.org 
This allows you to send and receive SMS through your mailbox.


Powered by Outblaze

Reply via email to