Re: openEHR draft Expression spec

predicate, but it should be ignored in implementations Option 2 is a harder to implement, because you can no longer convert from Apath to Xpath without knowledge of the model. But as Apath expressions are not new, I’m thinking some other people will have an opinion on this :) Regards, P

Re: AW: Archie version 0.1.0 released

n a perfectly redundant wheel-reinvention exercise does achieve one very useful thing: it creates a new dev team that understands the specification and model intimately, and knows how to code with it - in other words we are growing the developer community. This is very valuable. - thomas

Archie version 0.1.0 released

there will be more releases in the near future. If you want to contribute: pull requests and issue reports are very welcome! Regards, Pieter Bos Nedap Healthcare ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman

Re: Archie version 0.1.0 released

to releasing this code under a different license, but only if the resulting work can be used in non-GPL software. Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <openehr-technical-boun...@lists.openehr.org<mailto:openehr-technical-boun...@lists.openehr.org>> on behalf of

Re: Archie version 0.1.0 released

unusable for other non-GPL projects by others. I would prefer another way forward :) Regards, Pieter Bos On 18/05/16 11:10, "openEHR-technical on behalf of Diego Boscá" <openehr-technical-boun...@lists.openehr.org on behalf of yamp...@gmail.com> wrote: >Nice wok Piter! >

Re: Hand coding templates in ADL 1.4

The editing tools for adl 2 are still limited. However the template editing by hand is easier in adl 2 than the earlier template xml formats because it's the same adl with a few extra language constructs for templates. And you can convert the ckm to adl 2 quite easily. Pieter Bos Op 12 feb

Re: inheritance of archetypes

under the Apache license, so it should be usable in any kind of project you like – open source or proprietary. Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of Ian McNicoll <i...@freshehr.com> Reply-To:

Re: Question about paths to C_SINGLE_ATTRIBUTE alternatives

objects. Of course, you can write something that converts these paths from the AOM to the RM, but I don’t see why that should be necessary. Perhaps someone can explain the reasoning behind these choices? Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <openehr-technical-b

Re: Could the specs group consider making uid mandatory?

a lot of overhead. What are you trying to do that cannot be solved with a top-level UID plus a path? Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of Seref Arikan <serefari...@kurumsalteknoloji.com> Reply-To:

Re: Could the specs group consider making uid mandatory?

That sounds reasonable. I wonder how many existing systems already do this… Regards, Pieter Bos Nedap Healthcare On 13/12/16 14:24, "openEHR-technical on behalf of Ian McNicoll" <openehr-technical-boun...@lists.openehr.org on behalf of i...@freshehr.com> wrote: T

Re: SNOMEDCT - correct representation

If anyone knows an editor that does ADL2 and supports enough options to make editing by hand no longer needed, we're interested. Regards, Pieter Bos Op 16 mei 2017 om 18:23 heeft Pablo Pazos <pablo.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>> het volgende geschreve

Re: A little community coordination

Hello Pablo, This sounds like a good initiative! Maybe it could be a good idea to add some way to distinguish ADL 1.4 and ADL/AOM 2 projects. Perhaps also the different RM versions? Regards, Pieter Bos Op 19 mei 2017 om 18:30 heeft Pablo Pazos <pablo.pa...@cabolabs.com<mailto:pa

Re: A little community coordination

Submitted our response - looking forward to the responses from others. There's no 'partially open source' option :) Regards, Pieter Bos Op 21 mei 2017 om 12:16 heeft Koray Atalag <k.ata...@auckland.ac.nz<mailto:k.ata...@auckland.ac.nz>> het volgende geschreven: Hi Pablo, grea

Re: Is 'Choice' datatype available in Archetype editor an OpenEHR standard

It is explained in the ADL 2 spec here: http://openehr.org/releases/AM/latest/docs/ADL2/ADL2.html#_single_valued_attributes And the ADL 1.4 spec here: http://openehr.org/releases/AM/latest/docs/ADL1.4/ADL1.4.html#_single_valued_attributes Pieter From: openEHR-technical

Re: Extract archetypes

I agree about the case insensitivity. Archie still does this case sensitive, so I just created https://github.com/openEHR/archie/issues/8 ( Pieter On 30/11/2017, 15:23, "openEHR-technical on behalf of Thomas Beale"

Re: Extract archetypes

The test package is called “test_pkg” at least in adl2 – so underscores are supported. Pieter From: openEHR-technical on behalf of Diego Boscá Reply-To: For openEHR technical discussions

Re: Blockchain

– almost any implementation would need to be able to handle attacks where you link multiple pieces of data to the same person or party without having explicit permission to do so. Regards, Pieter Bos From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of G

Re: Aw: Re: Blockchain

public healthcare related blockchain has interesting privacy issues that will need to be solved. Regards, Pieter Bos Op 14 nov. 2017 om 16:21 heeft Bert Verhees <bert.verh...@rosa.nl<mailto:bert.verh...@rosa.nl>> het volgende geschreven: On 14-11-17 16:02, Philippe Ameline w

Re: Scenarios for change type "deleted"

You would be able to import this structure into our implementation and it would work the same way. Pieter Op 2 nov. 2017 om 17:24 heeft Pablo Pazos > het volgende geschreven: Until we have a clear criteria for commits after delete,

Re: Scenarios for change type "deleted"

I meant data using the criteria you outlined. Regards, Pieter Bos Op 2 nov. 2017 om 18:25 heeft Pablo Pazos <pablo.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>> het volgende geschreven: Hi Pieter, What structure? On Thu, Nov 2, 2017 at 2:21 PM, Pieter Bos <piete

Re: Quantities of arbitrary units in openEHR

no way to constrain it - unless the specification contains a mistake :) It is present in the BMM variants of the RM though, as a mandatory field. Regards, Pieter Bos Op 26 jan. 2018 om 08:19 heeft Bakke, Silje Ljosland <silje.ljosland.ba...@nasjonalikt.no<mailto:silje.ljosland.ba...@nasjonal

Re: Announcing Archie version 0.4

be reported at the github repository. Regards, Pieter Bos Nedap Healthcare From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of Thomas Beale <thomas.be...@openehr.org> Reply-To: For openEHR technical discussions <openehr-technical@lists.openehr.org&g

Re: Announcing Archie version 0.4

Or a Java app with rest api and a JavaScript frontend. Let the java application take care of parsing, validating, flattening, operational template creation etc and send json to your front end. Archie has built-in json serialization and deserialization support. Pieter Op 3 feb. 2018 om 12:05

Announcing Archie version 0.4

at Maven Central. See the instructions and documentation in the readme at https://github.com/openehr/archie for how to use the library. Regards, Pieter Bos Nedap Healthcare ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http

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

? Regards, Pieter Bos From: openEHR-technical <openehr-technical-boun...@lists.openehr.org> on behalf of Thomas Beale <thomas.be...@openehr.org> Reply-To: For openEHR technical discussions <openehr-technical@lists.openehr.org> Date: Friday, 26 January 2018 at 14:23 To: Openehr-

HRe: openEHR REST APIs - Release 0.9.0 / invitation for ,

lization queries among other queries like "this path exists for this archetype ID?", etc. If this is possible, we can have interoperability between archetype repos and your queries can use my repo to get specialization info, and vice-versa. Best, Pablo. On Thu, Feb 15, 2018

Re: Announcing Archie version 0.4

sa.nl> wrote: On 23-02-18 16:36, Pieter Bos wrote: > you would have to find a way to map all the inheritance in the OpenEHR model to protocol buffers. For Java I found this web-page which explains how to do it. It is about a class with one nested class https://de

Re: Announcing Archie version 0.4

. Regards, Pieter Bos Nedap Healthcare On 23/02/2018, 15:30, "openEHR-technical on behalf of Bert Verhees" <openehr-technical-boun...@lists.openehr.org on behalf of bert.verh...@rosa.nl> wrote: On 23-02-18 14:37, Pieter Bos wrote: > A small amount of JavaScript wor

Re: Announcing Archie version 0.4

A small amount of JavaScript working with Json from a backend works very well for us. You don’t always need explicit class definitions. it does require a different programming style than a more object oriented language. Regards, Pieter Bos Op 23 feb. 2018 om 14:21 heeft Bert Verhees

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: "openehr-tech

Re: Should Duration class used in AOM 1.0.2 be ISO8601_DURATION from support specs?

that supports all of the options. Regards, Pieter Bos Op 20 mrt. 2018 om 21:06 heeft Pablo Pazos <pablo.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>> het volgende geschreven: Thanks Thomas, will create the PR! Also will double check if the same happens with other types,

Re: Should Duration class used in AOM 1.0.2 be ISO8601_DURATION from support specs?

and databases, instead of defining your own. And it's already defined in the OpenEHR models, so you can start using it right away. Regards, Pieter Bos Nedap Healthcare On 21/03/2018, 12:25, "openEHR-technical on behalf of Bert Verhees" <openehr-technical-boun...@lists.openehr.

Re: Should Duration class used in AOM 1.0.2 be ISO8601_DURATION from support specs?

and standard has its own term for those concepts. Regards, Pieter Bos On 21/03/2018, 14:42, "openEHR-technical on behalf of Bert Verhees" <openehr-technical-boun...@lists.openehr.org on behalf of bert.verh...@rosa.nl> wrote: No Duration type is a ISO8601 duration, ISO8601

Re: Parsing of Archetypes/Templates

an ADL parser ready. Note that for ADL 2 as far as I know there is no official XSD released yet, so it is possible you run into compatibility problems with XML. For ADL 1.4 this is not a problem. Regards, Pieter Bos Op 12 nov. 2018 09:18 schreef Georg Fette : Hello, For a project we want

Re: Parsing of Archetypes/Templates

compatibility with existing systems, ADL 1.4 for now – I think most EHRs are 1.4 only at the moment. Regards, Pieter Bos From: openEHR-technical on behalf of Diego Boscá Reply-To: For openEHR technical discussions Date: Monday, 12 November 2018 at 13:44 To: For openEHR technical discussions Subject

Re: DV_DURATION and magnitude_status?

Not sure if this is already in the RM version you use and not sure if ADL 1.4 supports this, but can this be a DV_INTERVAL of DV_DURATION? Regards, Pieter Bos Op 24 sep. 2018 14:42 schreef "Bakke, Silje Ljosland" : Hi, I’ve got a use case where we need to represent a tim

Re: ADL specification question

are 0..*, it can be two or more of the first, two or more of the second, or at least one but possibly more of both. More options are possible. If occurrences is not defined, in this case I think it defaults to 0..*. Regards, Pieter Bos Op 29 nov. 2018 10:31 schreef Georg Fette : Hello, I have

Re: JSON for definitions-notation

. Regards, Pieter Bos Op 15 feb. 2019 20:41 schreef Thomas Beale : JSON, YAML and ODIN are all just object-dump serial formats that result from traversing an in-memory object graph, so it is a generic operation to generate them from tools (XML is more problematic due to being irregular in many

Re: Rules in archetypes - what are the requirements?

when you flatten rules to an OPT 2 template, to obtain a single artifact that can be used for many things, including rule evaluation. That is very doable right now by prepending some paths and adding some for_all statements. I’m not sure how to do that with data binding. Regards, Pieter Bos From

Re: Rules in archetypes - what are the requirements?

, this will be different for different implementations. Regards, Pieter Bos From: openEHR-technical on behalf of Thomas Beale Reply-To: For openEHR technical discussions Date: Friday, 1 February 2019 at 13:01 To: Openehr-Technical Subject: Rules in archetypes - what are the requirements? For many

Re: Rules in archetypes - what are the requirements?

From: openEHR-technical on behalf of Thomas Beale Reply-To: For openEHR technical discussions Date: Saturday, 2 February 2019 at 15:01 To: "openehr-technical@lists.openehr.org" Subject: Re: Rules in archetypes - what are the requirements? Assuming you meant to put 'id7' as the first one,

Re: Rules in archetypes - what are the requirements?

, and a defined data model to ensure interoperability. Much easier to specify and implement, although it will be harder/no longer possible to write tooling to visualize the code and harder to write tools that allow less-technical people to write code. Regards, Pieter Bos Op 2 feb. 2019 14:16

Re: Rules in archetypes - what are the requirements?

From: openEHR-technical on behalf of Thomas Beale Reply-To: For openEHR technical discussions Date: Saturday, 2 February 2019 at 20:10 To: "openehr-technical@lists.openehr.org" Subject: Re: Rules in archetypes - what are the requirements? On 02/02/2019 16:21, Pieter Bos wr

Re: data element type from the RM

which class an object is. There's no need to replace the standard mechanisms with something custom and non-standard. In other words, yes you need to know the class of a given object, but it is mapped to the mechanism best suited for the used concepts and technology. Regards, Pieter Bos Op 10