AQL Parser

2018-02-15 Thread Georg Fette
Hello, What is the best (comfortable, easiest to use, most often used, most interoperable, etc.) implementation of an AQL parser currently available ? After some googleling I found a Git repository of JacSoyYo. Alternatively I could cut the parser from the EtherCIS-Server. Currently I am only in

Re: openEHR REST APIs - Release 0.9.0 / invitation for comments

2018-02-15 Thread Georg Fette
Hello, I have some questions on the explicit definition on how the result rows are returned in the query API: 1. In the example at https://www.openehr.org/releases/ITS/Release-0.9.0/docs/query.html#header-resultset-example there is one result row with one fact for each of the columns that were

Re: openEHR REST APIs - Release 0.9.0 / invitation for comments

2018-02-15 Thread Seref Arikan
Hi Georg, Please see comments inline On Thu, Feb 15, 2018 at 9:43 AM, Georg Fette wrote: > Hello, > I have some questions on the explicit definition on how the result rows > are returned in the query API: > 1. In the example at https://www.openehr.org/releas > es/ITS/Release-0.9.0/docs/query.htm

Archetype pattern

2018-02-15 Thread Bert Verhees
An interesting wiki from Heather Leslie https://openehr.atlassian.net/wiki/spaces/healthmod/pages/90507705/Archetype+Design+Patterns She concludes that pattern are necessary, I agree with that, and she also concludes that clinicians are better modelers then technicians. Well, that depends, of

RE: Archetype pattern

2018-02-15 Thread Anastasiou A .
Hello Bert I think that this is an interesting topic from a number of aspects. Can I please ask what do you mean by "clinicians create archetypes with unpredictable paths"? Can you provide one or two examples? Also about the "something, that is: PATTERN", David Hay has written an excellent boo

Re: openEHR REST APIs - Release 0.9.0 / invitation for comments

2018-02-15 Thread Pieter Bos
I noticed the recent version of the REST api only works with templates, and not archetypes. As our EHR is ADL 2 only, this has some interesting consequences. Of course, you can upload just the operational templates and probably create a fully functional EHR, but if you work with ADL 2, you wou

Re: Archetype pattern

2018-02-15 Thread Thomas Beale
Indeed, patterns are conceptually what is needed - many of us have thought so for a long time. The real question is what lies behind a pattern? Consider the OBS/EVAL/INSTR/ACTION set of classes in the RM - they are a formal representation of a pattern (each containing some micro-patterns), that

RE: Archetype pattern

2018-02-15 Thread Heather Leslie
Hi Bert, Unfortunately pattern by itself won't result in good archetypes. Mind you, I think the RM classes are brilliant and they have been the cornerstone for our modelling experience. In fact I suspect that the lack of these classes is a large part of the reason why other modelling paradigms

Re: openEHR REST APIs - Release 0.9.0 / invitation for comments

2018-02-15 Thread BoĊĦtjan Lah
Hi, We can add definition endpoint for archetypes as well, no problem. Actually we had it in the previous version, so I'll just add it back. Best regards, Bostjan > On 15 Feb 2018, at 17:09, Pieter Bos wrote: > > I noticed the recent version of the REST api only works with templates, and >