Now you are getting into archetypes and templates. Templates are used to a) choose archetypes to be composed to make larger structures from smaller re-usable pieces b) to remove those data points not needed in the larger structure, i.e. for the use case at hand (could be most data points and c) to further constrain remaining data points to e.g. mandatory, or reduced terminology subsets etc. A template in ADL 1.5 (forthcoming specification) is just a specialised archetype, and the new generation of tooling will be able to treat it as such. A new release of the ADL Workbench will appear in the next week or so, demonstrating ADL 1.5 archetypes and templates.
There is of course a remaining wider discussion about 'standards' and what they can possibly mean, and how we can improve them. regards - thomas On 27/06/2010 13:14, William E Hammond wrote: > I generally agree. However, I thin k it depends on the higest level to > which the archetype is defined. Some are carrying architypes to a complete > collection of data for a disease encounter, any encounter and a medical > record. Obviously some data elements would appear in more than one > archetype. I view archetypes as more for data collection and some data > presentations rather than an architectural model for the EHR, although in > some cases I would keep the data bundled. In any case, navigation of the > database is the issue. > > I have left my emeritus status and returned to full time at Duke. I am the > Director of the Center for HEalth Informatics which involves both teaching > a informatics research. My time with HL7 will probably be limited. My > focus will be more on standards for the clinical commun ity. > > W. Ed Hammond, Ph.D. > Director, Duke Center for Health Informatics
