On 14/06/2013 12:12, Gerard Freriks wrote: > Dear Thomas, > > Why do we (CIMI) need a TDD? > Isn't a TDD a transformation that is used during the implementation of > a Template.
I have to admit I was surprised to see all this talk of TDD-like things in CIMI. TDS/TDD is more than just a specification, but it doesn't need to be solved in one go with the core modelling requirements - I think CIMI should stick to just the core job for now, and look at TDS/TDD later on. It already has too much work to do and no funding to do it with! > > We in CIMI -I think, we agreed- is about Clinical Information Models. > CIMS. > CIMS that can be transformed to openEHR expressions, 13606 > expressions, CDA, all expressed as constraints on there respective > Reference Models. for CIMI, I would agree with that. > > These CIM's, once transformed, are used in Templates that will be used > locally. > And only then at implementation time implementers want something in > XML. And that is the TDD. that's a reasonable way of looking at it. On the other hand, the power of the archetype/template approach is that you can generate a message content specfication straight from the template, as an XSD (i.e. what we call TDS) or for that matter, something else, e.g. JSON schema or whatever, and call that a standard. This could be done for something widely shareable such as emergency summary, basic labs, and vital signs. The TDS form will be the most easily consumable form for most vendors, so it's more than just a purely local concern. But in the end, I would say, leave all this till later in CIMI, if there is to be any hope of timely delivery of models. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/cf40f626/attachment.html>
