Re: Strange behavior in Template designer 2.8.94 Beta

It's AOM2.x inside, but deals with ADL 1.4 and .oet files externally. It's now more or less BMM-driven I think. But also they made some compromises to make sure all the ADL 1.4 and .oet stuff works the way it did. Archie is completely ADL/AOM2 of course. It may be that in the future they

MEDINFO 2019, Lyon, France.

Dear openEHR colleagues, In the next year, MEDINFO 2019 will be in Lyon, France, from 26th to 30th August, 2019. The application for paper/poster/workshop/tutorial deadline is Nov 12. This is important, ONLY less than TWO MONTH left for the deadline. I already launched wiki page for MEDINFO 2019.

Re: Strange behavior in Template designer 2.8.94 Beta

Has that been changed? Last time I checked and asked Marand it was ADL 1.4 only. Or is it AOM 2.x but ADL 1.4? Regards, Pieter Bos From: openEHR-technical on behalf of Thomas Beale Reply-To: For openEHR technical discussions Date: Monday, 20 August 2018 at 13:04 To:

Re: Strange behavior in Template designer 2.8.94 Beta

Okay, interesting! It would have made things easier for us 5 or 10 years ago to have had a looser interpretation of the ‘unique path rule’. Perhaps it was a case of erring on the side of caution, since it's always easier to relax a rule that turns out to have been too strict rather than

Re: Strange behavior in Template designer 2.8.94 Beta

The new tool is AOM 2.x inside, but I have to admit I have not investigated how this particular problem is resolved in it. - thomas On 20/08/2018 11:42, Peter Gummer wrote: Hi Hildi, On 20 Aug 2018, at 19:13, Hildegard McNicoll > wrote: Incidentally, the new web

Re: Strange behavior in Template designer 2.8.94 Beta

Hi Peter It's probably best to defer the exact answer to others, but my understanding is that the 'unique path rule' was interpreted too tightly in Template Designer, rather than this being a strict limitation in ADL 1.4. Certainly there is no need to migrate to ADL 2.0 with ADL Designer, it

Re: Strange behavior in Template designer 2.8.94 Beta

Hi Hildi, > On 20 Aug 2018, at 19:13, Hildegard McNicoll wrote: > > Incidentally, the new web based ADL Designer tool developed by Marand doesn't > have this problem anymore. As far as I know it is very close to being > released now. I’m curious — from a purely academic perspective, now,

Re: AQL on specific list of compositions

that would be possible if we modify the meaning of the CONTAINS operator to mean contains-by-value (like ENTRYs inside a COMPOSITION) /or /contains-by-reference, which is the FOLDERs case - as you have long argued ;) Not hard technically as far as I can see - but it does mean a

Re: AQL on specific list of compositions

On Mon, Aug 20, 2018 at 10:04:45AM +0100, Thomas Beale wrote: > Some of these Contsys definitions are problematic: > > ENCOUNTER > > > > But there is an encounter when the HcP interacts with the EHR without a > > Patient (Virtually) present. > > that would certainly be a subversion of the

Re: AQL on specific list of compositions

You're (unintentionally) circling back to discussions re AQL in the last SEC meeting in Slovenia (I was sitting in remotely) What you're asking for can be accomplished in a number of ways at the AQL level, all of which would require changes to AQL specs and implementations. I'm always happy to

Re: AQL on specific list of compositions

Yup but AQL is so cool for this kind of thing :) I still want to do Select c FROM EHR Contains folder x contains composition c since logically folder x contains compositions. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com

Re: AQL on specific list of compositions

@Gerard - I have always assumed that Contsys 'Health Issue' equates to problem. https://github.com/openehr-clinical/shn-contsys Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR

Re: Strange behavior in Template designer 2.8.94 Beta

Hi Dileep In your particular example I would leave the archetype unchanged, but instead rename the Issue name to say 'complaint description'. That way you can keep the multiple recurrence of the archetype, but have your preferred name in the data as the left hand side of the name/value pair. You

Re: AQL on specific list of compositions

Well if you have access to a Folder, you don't need to do an AQL query, you can just retrieve the Folder structure and recurse through it, picking up direct refs to VERSIONED_COMPOSITIONs. Creating Folders from the data on the other hand requires writing some queries that look for admissions

Re: AQL on specific list of compositions

Thanks Thomas, What are your thoughts on the AQL example I foolishly guessed at :( and that Seref quite correctly rejected!! How would/should we do... Select all compositions referenced by Folder x. How else might we meet Dileep's use-case with AQL? Dr Ian McNicoll mobile +44 (0)775 209 7859

Re: AQL on specific list of compositions

Some of these Contsys definitions are problematic: On 20/08/2018 09:13, GF wrote: Hi Karsten, ISO System of Concepts for Continuity of Care (ContSys) defines all kinds of concepts related to care and its documentation. It would be. a good thing to harmonise terms we use. More info via:

Re: AQL on specific list of compositions

This is how I understand it as well, just in the interests of avoiding confusion, so a Folder solution as described above is for episodes of care, within an institution, or something that functions like an institution, and where there is internal continuity of care, e.g. an integrated area or

Re: AQL on specific list of compositions

On 18/08/2018 07:56, Bert Verhees wrote: I cannot imagine how a folder structure can get lost except by data corruption. In that case anything is lost anyway and a rollback from a backup is needed. It's a thought experiment, not a serious proposition about a real system. But it partially

Re: AQL on specific list of compositions

Hello Gerard, > ISO System of Concepts for Continuity of Care (ContSys) defines all kinds of > concepts related to care and its documentation. I (GNUmed, that is) agree with the definitions you refer to. I was answering to Ian's input: > As Dileep has indicated he probably would use folders

Re: AQL on specific list of compositions

Hi Karsten, ISO System of Concepts for Continuity of Care (ContSys) defines all kinds of concepts related to care and its documentation. It would be. a good thing to harmonise terms we use. More info via: https://contsys.org ContSys is NOT a Data model but a way to define