Dear all,
I have posted a draft of a paper on how to approach a shared archetype/template formalism which will work for all stakeholders interested in producing such arctifacts. See http://www.deepthought.com.au/health/archetypes/archetype_language.doc.
Although this work is unfinished, we have decided to publish a version now, before the HL7 San Antonio meeting, so that people participating in the relevant HL7 groups might have time to read it and comment. I will not be there personally, but Sam Heard will, and hopefully there will be a slot to discuss it in templates or Structured documents.
The title uses the word "archetype" rather than "template", even though the main topic is what is currently called "templates" in HL7. This is because the terms "archetype" and "template" are both meaningful and different; the paper describes in some detail why.
Since this is an effort to define some semantics that we can all agree on, all criticism, no matter how violent, is invited...
best regards
- thomas beale