In een bericht met de datum 21-8-2005 14:43:17 West-Europa (zomertijd), 
schrijft Thomas.Beale at OceanInformatics.biz:


> > - coding systems never will be stable.
> > - the way to handle change in OpenEHR (and CEN En13606) is via archetypes.
> 
> well, in general that's the idea. But the question at hand is about 
> coding in the reference model itself, i.e. for the structural 
> (hard-wired) attributes that have coded values - in other words, things 
> which we have specifically chosen not to archetype.There isn't much 
> mileage in archetyping the code-set of ENTRY.language, for example - we 
> don't want to open such a basic thing up to variation in archetypes. 
> Instead we want it controlled inside the reference model and openEHR 
> vocabularies. The original question of CR-150 was whether we should 
> bypass even this flexibility and simply specify that such attributes are 
> of type String (or maybe an enumerated type) and hard code them into the 
> model. In my view, this is problematic in all sorts of ways - the main 
> one is that each implementor will do this in a different, probably in 
> compatible way.


Some coding systems must remain stable. E.g. in the format of clinical 
instruments with specific clinimetric or psychometric characteristics, examples 
include Barthel, Apgar score, already to some extend archetyped. 
The answer categories and value sets here are themselves standardized. These 
must be hard coded into the archetype to enforce the compatibility. 
Here the intelligent semantic interoperability comes into vision: the 
clinical and evidence base itself enforces specific semantics (variable, 
values, 
codes) and thus requires the data be stored and exchanged in only this format. 
There is no optionality for string here, and also enumeration cannot be done on 
the fly.

See examples of not yet archetypes on www.zorginformatiemodel.nl. These 90 or 
so instruments and observation sets will become available in English (we work 
on request by request base). 
Here we will achieve no mileage in archetyping the code-set but probably 
lightyears :-) 


My 2 Eurocents.

William Goossen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050821/5d58f14f/attachment.html>

Reply via email to