Hello Thomas, Some questions about the example available at the SVN (http://www.openehr.org/svn/knowledge2/TRUNK/archetypes/openEHR_examples/ehr_extract_template/Working/Templates/ehr_extract/openEHR-EHR_EXTRACT-EXTRACT.t_basic_acute.v1.adls)
- What does the next snippet mean? use_archetype COMPOSITION[at0103, openEHR-EHR-COMPOSITION.t_clinical_info_ds.v1] allow_archetype COMPOSITION[at0103.1] closed In the first case... that's a big archetype node identifier! Is that a simplification of the includes syntax? In the second one, what does 'closed' mean? Is the same that putting the occurrences to 0..0? If I remember correctly, use_archetype and allow_archetype are equivalent in ADL 1.4. what is the difference between them? By the way, isn't 'use_archetype' deprecated in ADL 1.5 (as can be seen on page 42 of current draft)? - All content seems to be included by value now at the EXTRACT. Following current (and I suppose outdated) Extract XSD schemas (as you can see here http://prntscr.com/1tydt) everything is referenced. On the specifications I see that there is 'item' of 'Any' type. Does that mean that can be an object or a reference? - What is the difference between an EXTRACT_CHAPTER and a common FOLDER? 2011/5/5 Thomas Beale <thomas.beale at oceaninformatics.com>: > > I have updated the page > http://www.openehr.org/wiki/display/spec/openEHR+EHR+Extract on the openEHR > EHR Extract to now include a reference to a new ADL 1.5 template example for > a full Extract of a simple discharge summary (do an SVN update on your local > copy of the http://www.openehr.org/svn/knowledge2/ repository to get the new > archetypes and templates). > > This work illustrates a large, realistic structure modelled as an ADL 1.5 > template and archetypes, and the resulting structured can be seen in the > 'flat view' visualisation. Soon we will have the ADL and XML OPT > serialisation being output. > > Apart from the ADL 1.5 template-based modelling, this example might help > people understand the openEHR EHR Extract. I sometimes see, with some > amusement, web pages, posts or papers saying things like 'openEHR is a model > of an EHR, 13606 is a model of an Extract' etc. While it is true that 13606 > defines only a model of an Extract, openEHR defines a model of EHR > information, in both a form that could be used to design an EHR, and a form > that is used for Extracts. Indeed, the openEHR Extract is significantly more > flexible than the 13606 Extract (now somewhat out of date). Perhaps if there > any new version of 13606 in the future might be able to benefit from the > design used here. > > - thomas beale > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >
