Hi! At Karolinska we are a bit confused about how to format/use some things in different forms of the FLAT/SimSDT format. We are testing at least three CDR products that are supposed to support it and at least two (non-openEHR-based) systems that try to use it correctly for exporting/converting for…

Is this the way both EHRbase and Better platform behaves?

First day back from a short vacation for me, I will try to take some time this afternoon and see if I can test a bit more to be sure. One thing I have now noticed is that it seems from Better’s Archetype Designer we are now receiving a node_id (this at0002 and at0001) on these when we export (both …

[image] erik.sundvall: [image] pablo: do you see any advantages on using FLAT and similar formats for openEHR data exchange vs. using the official canonical JSON format No, not between two openEHR-compliant systems. Template-specific formats can become a maintenance nightmare outside narr…

Hi, without going into all the details, just my 2 cents from the EHRbase perspective (which the developers can further elaborate on). Regarding the use of WebTemplate and FLAT: I very much disagree with the statement that using FLAT is as difficult as using the RM directly. Our experience is tha…

Thanks Josuha, There is/was something odd around the way that Web templates are handling context, which coincided, I think, with Archetype Designer adding these (I think redundant) atCodes on category and context. @Eeik - I’ll look at your examples but I don’t think this is related to or affected …

[image] stefanspiska: Yes this is due to Composition Archetypes are generated with atcode in EventContext Thanks Stefan. That does exactly explain what has been happening. Those redundant codes were only being added to new compositions created in AD, which then appeared in the .opt and were …

[image] pablo: They still need to understand what they are doing, what those paths mean, learn how to transform those paths back and forth to a RM instance, etc. That’s not really true Pablo - the CDR handles transforming the short paths to and from the RM instance, nor doe tey have to unders…

[image] ian.mcnicoll: I wonder if it is worth documenting our ‘findings’ and solutions in a separate thread/channel/wiki. The top post in this thread is a “wiki-post” so many active users (but not recently registered ones) should be able to edit it, I’ll add a “findings” heading where we all…

[image] ian.mcnicoll: [image] pablo: They still need to understand what they are doing, what those paths mean, learn how to transform those paths back and forth to a RM instance, etc. That’s not really true Pablo - the CDR handles transforming the short paths to and from the RM instance, …

The good, the bad and the "Wat?" of current simplified FLAT/SimSDT openEHR exchange format

Specifications ITS

stefanspiska (Stefanspiska) 12 April 2023 14:43 13

Yes this is due to Composition Archetypes are generated with atcode in EventContext

So you need to remove this wrong atcode.

Topic		Replies	Views
Coding element and event names Specifications template	56	1159	4 December 2024
Polishing node identifier (at-codes) use cases. Technical (archive)	73	5	27 September 2013
Missing rule in AOM 1.4 for non-unique sibling nodeIds Specifications	42	968	8 April 2024
AOM: how do you differentiate between sibling C_OBJECT if both are ARCHETYPE_ROOT and have the same archetype_id? ADL	36	806	5 October 2022
Modelling pattern - imaging examination - what do you think? Clinical modelling-patterns	40	1134	11 June 2022
Choice between data element and SLOT? Clinical archetype	41	2077	8 March 2021
Is using EVENT in archetypes an inconsistent way of modeling "any event"? ADL adl , archetype , aom	29	1042	5 October 2022
Named element - and occurences Archetype Designer	71	1570	29 January 2023
Agreeing on optional user interface hints in templates Specifications ux , forms	53	2638	29 April 2026
Dynamic archetype in slot based on preconditions Clinical archetype , template	40	844	28 August 2025

The good, the bad and the "Wat?" of current simplified FLAT/SimSDT openEHR exchange format

Related topics