Hi! I just wanted to warn people using UML linked or derived from... http://www.openehr.org/releases/1.0.2/architecture/computable/UML/uml.html ...that the old class MERGED_VERSION class still in UML files although it has been removed from the specification documents (and VERSION plus subclasses are a bit different)
The problem includes UML-generation described at http://www.openehr.org/wiki/display/dev/Experimental+generation+of+code+and+documentation+from+UML (same as tiny link http://www.openehr.org/wiki/x/OwAt) I don't know if the problem is present in the files at... http://www.openehr.org/svn/specification/TAGS/Release-1.0.2/architecture/computable/UML/MagicDraw/ ...since I have not generated diagrams from them, but the phrase MERGED_VERSION is at least present in the zipped XML file there. Best regards, Erik Sundvall erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733 P.s. A side question: It seems impossble to add attestations to IMPORTED_VERSIONs, this sounds reasonable (e.g. due to problems syncing back those attestations to other systems without creating a new original version). The question I have is if there should be a procedure for attesting things coming from other systems and how that procedure would look. Lab results (e.g. OBSERVATIONs) from an external lab could be an example - should a new local original version of the result be created and then signed as a sign of reception and reading by the receiving clinician or should other mechanisms (e.g. creating ACTION objects referring to the result OBSERVATION).
