I've skimmed the replies on this thread, and I'm inclined to think
everyone could be right. Problem is, they can't all be right at the same
time.
So.... considering the issue from a global deployment perspective I had
the folllowing idea:
* in the archetype library, we should stick to proper versioning
rules, as Diego, David and Sebastian have said, and correct the
error and issue a new v2 archetype
o => this way there are no surprises in the archetype library for
software, or people, by the time we have forgotten about this issue
o => the paths would stay the same to the various data fields, but
the units in the tilt table field would be different, and will
break anything that specifically relies on that
* but we still may need a way of making adding the correction to the
v1 version of the BP archetype, for some users, to enable their
current queries and software based on the 'v1' id to keep working.
This could be achieved by:
o creating a specialisation of the v1 archetype that adds a new
node as Sebastian proposed, or via Heath's proposal
+ => this means that the deployment has to use a new archetype
id for data production (i.e. in the CDR), but AQL queries
using the old id should continue to work, assuming the query
processor correctly finds child archetypes for a given
archetype id
o OR enable a modification in the template that has the effect of
adding the required unit or element
+ => this means that all ids stay the same in data production
and querying, but the CDR is being told a white lie, in that
what it thinks is the BP archetype is not exactly what it is
back in the CKM library
I haven't tried to analyse the details here that far, but the general
idea is to:
* a) ensure the archetype library follows the versioning and change
rules properly
* b) inject an adjusting fix either as a specialisation, or further
along in the processing chain - in a template (or even OPT....)
thoughts?
- thomas
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
