Hi Thomas Thanks for the response.
Thomas Beale wrote: > Depends on what you want to do ;-) Well we're looking at authoring openEHR Archetypes to seve as a standard form for representing clinical data for capture through templates (not the HL7 ones!). With people often confusing the openEHR approach with the CEN13606 work (and using them almost interchangeably), I wanted to make sure we're not going off on a tangent. > In the near future, the automatic bidirectional transformation for > openEHR/CEN will be completed (when CEN works out what data types it > is using). This will mean openEHR tools will be able to generate CEN > structures automatically. It may be worth looking at the openEHR EHR > Extract specification as well. This is not yet finished, but will > offer significantly more power than the CEN Extract, while containing > a CEN-like mode to act as a wrapper for CEN-encoded information. Ive downloaded the EHR Extract document. Just wanted to know exactly what this document will be beneficial for - are the Extracts to be used for sending relevant parts of the EHR data (or perhaps model) based on the user query? Does the document prescribe the format in which the extracts will be returned to the user or do they prescribe the query syntax or is it just a logical representation of how the Extracts relate to the EHR Information Model? >> In particular, is it important to know the CEN13606 archetypes if >> working with openEHR archetypes. At a logical level what are the >> differences between the two? >> > > others may know better, but at the moment I don't know of any CEN > archetypes. Thats a useful piece of info. Ill look for more responses on this issue then. >> Another topic area that alludes my understanding is a clear >> parallel/possible relationship of HL7 Templates and the use of >> 'templates' in openEHR archetypes (the later concept I am very clear >> about.. its the HL7 view of templates Im not sure of). It'll just >> help in my understanding of hl7 templates w.r.t. archetypes, as >> parallels are often drawn between the two. >> > > We would like to know that as well ;-) What I know at this stage is > that an HL7 template is a specialised XML-schema of a base XML-schema > such as the CDA schema. There is no distinction in HL7 that I know of > between what we call archetypes and templates in openEHR. At the best, > you would have to say that an HL7 template is like an openEHR template > that is built like an archetype, i.e. no re-use of anything, just a > single giant archetype built for the particular purpose at hand (which > would normally make us call it a template...)... And I thought only I was confused :). But I think your view of what the HL7 templates are is the closest Ive got to receiving a clear explanation ! I had a guy show me how the Templates can be extracted from the CDA models .. at the end I was even more confused ! .. Ill revisit the hl7 templates work with this new understanding. Thanks a lot Rahil > > - thomas beale > > > -- Rahil Qamar Ph.D. Student Medical Informatics Group Room 2.43 Kilburn Building University of Manchester Work number: +44 (0) 161 275 6151 Email: qamarr at cs.manchester.ac.uk Website: http://www.rahilqamar.com/
