> - The LinkEHR-editor does not accept OCEAN-editor constructs as > C_DV_QUANTITY, and thus, does not allow multiple constraints on a > DV_QUANTITY > > > As I explained before, LinkEHR does accept those constructs. The only > limitation is that you cannot edit them graphically (but you can do it > in ADL view) or transform them to standard structures.
Hi David, is it possible that the Expand Domain Type is only in the paid version? I don't have it in my free version. But maybe I am wrong, but I cannot check it now. I am in the wrong room/wrong computer. I will check it later. > > > > - The LinkEHR editor silently adds NodeID's on DataValues as the > archetype does not have them. > > I agree that the tool should not add those node_Ids if they did not > exist. We will take a look to this. Good thing to change. > > - The LinkEHR creates per default the line: > terminologies_available = <...> which is not accepted by the > Ocean-Editor > > > This is part of the ADL 1.4 (and 1.5) specifications: > http://www.openehr.org/releases/1.0.2/architecture/am/adl.pdf > > 8.6.2 Ontology Header Statements > The terminologies_available statement includes the identifiers of all > terminologies for which term_bindings sections have been written. > > Maybe what it is not clear at the specs is if that line have to be > added if no terminologies have been defined or only when you have at > least one. That line can be removed very easily in that case. The problem, I already said, I was not sure if it was to blame to the OCEAN or the LinkEHR editor. The problem is that the Ocean editor gives a vague error message pointing to line-number later. The problem is, if you remove it, every time you save the archetype it is added again. It should not be the purpose of arcehtype-editors to rework archetypes in text-editors. I can do that, I have seen enough archetypes. But I know many people who can't, but they also have to do it. thanks Bert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120625/276de8e7/attachment.html>
