On 05/05/2011 13:42, David Moner wrote: > > > 2011/5/5 Thomas Beale <thomas.beale at oceaninformatics.com > <mailto:thomas.beale at oceaninformatics.com>> > > >> - What is the difference between an EXTRACT_CHAPTER and a common FOLDER? >> > > Chapters of type EXTRACT_CHAPTER are used to explicitly organise > top-level chunks of content in the Extract; the meaning of each > chapter is archetype/template-defined. EXTRACT_FOLDERs are there > to represent FOLDER or similar structures from the source system, > i.e. to preserve such structures in the Extract. So > EXTRACT_CHAPTER is an artefact of an Extract, FOLDER is (usually) > an artefact of data being extracted. I think 13606 mixes these > functions up in one FOLDER class, which makes it difficult to say > what a Folder actually is in a 13606 Extract. > > - thomas > > > > As in other cases, the 13606 approach uses a more generic way to get > the same results without the need of defining specific classes or data > structures. At this specific case, there is an attribute at all > RECORD_COMPONENTs that is "synthesised". Its definition is: "This > attribute value must be TRUE if this RECORD_COMPONENT has been created > in order to comply with this standard , but this point in the EHR > hierarchy has no corresponding node in the EHR from which it was > extracted."
I am actually the person responsible for this attribute (I proposed it at a CEN meeting in Rome in about 2004, if I remember correctly). The intention of this attribute is to indicate if container structures, e.g. Cluster, Entry, Composition objects in the Extract had to be synthesised completely new rather than generated from source data, due to the source data being very simple, e.g. a flat list or so. In openEHR it was originally an attribute, but became a value of the coded attribute AUDIT_DETAILS.change_type (it is openEHR code 252). But that is not the same thing as EXTRACT_CHAPTER - the latter is an organising structure within an Extract, regardless of what the content is - it is what allows demographic entities to be grouped in one place, and clinical information on a per patient basis to be grouped under chapters, one for each patient. This allows for very flexible data structuring, e.g. large numbers of lab results for hundreds of patients in an Extract. The Folder is a possible artefact of the content. Since Folders are optional, there is no question of them needing to be 'synthesised' to comply with the standard. So I can't think how synthesised=True on any optional container object, Folder included, could meaningfully be interpreted. - thomas* * -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110505/e2aa4518/attachment.html>
