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
