oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Sergio, & all,

On Wed, 2009-03-18 at 09:04 -0300, Sergio Miranda Freire wrote:
> In relation to the termserver, as far as I could see, you implemented a term
> server to solve your immediate problem, 

I realized that I did not address this specific point in my previous
reply.


My approach was not to address an immediate need. "I think" (and I am
open to comment) that I thought this through very thoroughly.  In order
to be "future proof" we need to maintain various versions/releases of
each terminology.   In the case of the openEHR terminology that may not
be a big deal.  But when we are dealing with ICD (released every 6
months I think) then we need to have a way to maintain past versions.  I
believe that the approach that we are using with nested grok.Containers
that are named  [ICD10][RELEASE-20090101]  and then another release
comes out in July [ICD10][Release-20090701]  
This give us the ability to look up the correct code in the temporal
context.

(many other issues like this exist)

Granted; we have to get the archetype developers to be more specif in
releases because there can be significant differences.  But that is an
issue that I will address on the implementers and clinical lists.

I would enjoy hearing from Segio's perspective how he planned to handle
these issues using his approach.


Cheers,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part