Follow up for: [EHRbase] Storing and querying data without an standalone archetype - #34 by ian.mcnicoll

First question Where to store additional terms on ELEMENTs A. ELEMENT Values For ELEMENT values this is pretty straightforward - we can use DV_CODED_TEXT.mappings This example ( Example of openEHR term mappings · GitHub ) adds term mappings for an internal atCode to a DV_CODED_TEXT but the approach…

Bah. I thought we were discussing how to implement semantic transformations from archetypes to some other formalism :man_facepalming: I’ll need to re-read this. Thanks to everyone for their understanding during the SEC meeting but I prefer that you ask me “what the hell are you talking about?” the …

‘Term bindings’ vs. ‘term mapping directives’ Term bindings are possible to record in archetypes but are suggested mappings that you might want to apply at runtime as term_mappings or to help with integration. Arriving at ‘consensus agreed’ bindings is actually very difficult in many cases, especial…

Nah - we framed it badly!! Easy mis-understanding to make, and there is, of course, huge overlap, in that many of the challenging semantic transforms involve term mis-matches

[image] ian.mcnicoll: In a local context we almost certainly do not want to apply every binding suggestion as term_mappings. Could you give an example of where we wouldn’t please?

Simples!! I might want to use an archetype that has LOINC bindings but I don’t want LOINC mappings in patient data as >OINC is not used in my country I do use LOINC but the LOINC bindings in the archetype have never been quality assured/ published.

[image] ian.mcnicoll: I might want to use an archetype that has LOINC bindings but I don’t want LOINC mappings in patient data as >OINC is not used in my country I do use LOINC but the LOINC bindings in the archetype have never been quality assured/ published. Ad1 there not much against stor…

Big thanks for all the sum up @ian.mcnicoll !!! I think the term mappings are the way since they cover also the values as ian pointed out. We should make this a best practice (some vendors already do that). @damoca so instead of defining code, using the term mapping seems to be a better fit.

[image] ian.mcnicoll: We might be able to say that term_bindings applied (or not constrained out) at template level should be regarded as mapping_directives i.e actually force these terms to be carried additional term_mappings but I’m not sure if we this kind of constraint on bindings is possibl…

[image] SevKohler: @damoca so instead of defining code, using the term mapping seems to be a better fit. In fact, according to the specifications, defining_code should only be used if the DV_CODED_TEXT.value is exactly the rubric of the terminology code. Otherwise, DV_TEXT and mappings must b…

How to make mappings easier to query and to document in openEHR

Specifications Terminology

sebastian.iancu (Sebastian Iancu) 17 April 2024 09:28 29

For readability, I moved some AQL relevant posts to Improve AQL to simplifying the querying of terms to continue there on AQL specifics.

Topic		Replies	Views
Coding element and event names Specifications template	56	1159	4 December 2024
Storing codes of two external terminologies Terminology	37	1793	19 July 2024
Why is value not optional for DvCodedText RM	27	990	20 October 2021
LOCATABLE name with a SNOMED code Archetype Designer	18	1181	18 March 2024
[EHRbase] Storing and querying data without an standalone archetype Platform ehrbase , aql	39	932	17 April 2024
SNOMEDCT - correct representation Implementers (archive)	49	3	20 May 2017
Option to record free text as choice against DV_CODED_TEXT - do we need DV_PLAIN_TEXT ADL adl , archetype	72	2234	5 January 2023
What happens once the Pulse/Heart beat archetype is replaced? Platform archetype	48	360	2 October 2025
New ADL/AOM proposals to solve some old problems Technical (archive)	15	1	29 April 2013
DV_CODED_TEXT with open/extensible set of codes (value set) ADL archetype , terminology , modelling-patterns , template , adl	29	1542	3 April 2020

How to make mappings easier to query and to document in openEHR

Related topics