Philippe, Fist of all: My ideas about modelling and using archetype, etc is not shared by OpenEhr
I agree that the tree is important. My tree starts at Composition contaiining one of more Sections, and/or Entries. The Entry models a process of one of these: data observation, data evaluation, data planning, data ordering and data about events/actions. Each of these models deal with the full epistemology of that topic using standardised patterns/Clusters/Archetypes That what is observed is a Cluster archetype that models the datum plus its context/epistemology. What is important is the Modelling Style. In OpenEhr the nodes of the Archetype are changed. In my style, since I make use of predefined patterns I will not change the nodes but change the data in the Elements. In my style of modelling querying the leaves is that what is done. The unique path defines its meaning. In my way of modelling the collection of paths is a kind of ontology for data in healthcare records. Gerard Freriks +31 620347088 [email protected] Kattensingel 20 2801 CA Gouda the Netherlands > On 30 Mar 2018, at 17:25, Philippe Ameline <[email protected]> wrote: > > Le 30/03/2018 à 16:49, GF a écrit : >> Philippe, >> >> I understand Archetypes are discourse models and form a sentences >> A collection of sentences (Entry Archetypes) form one >> story/session/Composition and define the content of a system-interface >> connected to a database, or screen, or other service like a messaging system. >> In my terms: A Template consists of Entry Archetypes and is the content of a >> system-interface. >> The Composition, Template, the system-interface are equivalent, but need the >> story, system-interface, Template must contain the data and its full >> context/ epistemology. >> The Archetypes in my thinking are standardised patterns with which to >> construct an Entry archetype. >> >> My hierargy becomes: >> >> Ontology - Encyclopedia >> Terminology - Dictionary >> Cluster Archetype - Standardised phrases/patterns >> Entry Archetype - Clinical sentence including epistemology/context >> (collection of patterns) >> Composition - Clinical story a Template with a collection of >> sentences/Entry archetypes >> >> Queries can be for leave nodes to find in a Patient Record the datum. In >> order to interpret the datum fully and safely one must inspect the whole >> associated Entry and/or Composition, (depending on specifics) > > Gerard, > > I think that I get your point, though not being proficient enough in openEHR > details. > > In my own universe, the basic information unit (as stored on disk) is a tree. > Each node of this tree being an element from the ontology, the tree is fully > autonomous and doesn't need external interpretation material. > > For example: > > Echocardiography > Indication > .... > Findings > Mitral valve > Doppler > Mitral leak > .... > > Hence, the "basic query unit" is not for leave nodes, but rather for a path ; > for example a query for "Echocardiography/Findings/Mitral valve" would return > a sub-tree. > > But maybe you were saying this already. > > Best, > > Philippe > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
