> > > 2. Archetypes are not only for openEHR. We must always have in mind > > that other reference models can be used with their own life-cycle that > > could be not so fine-grained as in openEHR. For example, we are now > > creating HL7 CDA R2 archetypes but during this year it is expected CDA > > R3 to be approved. How will we differentiate archetypes of R2 from > > archetypes of R3? Once again, R2 will still be used for many years and > > updating the version number isn't enough. > > I don't know what R3 looks like, but if it is a different reference > model, then the ids would be something like > > hl7-cda3-Entry.diagnosis.v1 > > If CDA r3 on the other hand is a clean extension / superset of CDAr2, > then the 'reference model' is really just 'cda', and there is no simple > relationship between particular archetypes and particular releases of > the CDA model. > > - thomas > > So, at the end you are putting the RM version somewhere at the identifier... :-)
(btw, I don't know which will be the changes at R3) David -- David Moner Cano Grupo de Inform?tica Biom?dica - IBIME Instituto ITACA http://www.ibime.upv.es Universidad Polit?cnica de Valencia (UPV) Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta Valencia ? 46022 (Espa?a) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110407/f35a3824/attachment.html>
