Re: Archetype editor, CKM and v0 v1
Looking at this again, AE currently provides two choices 1. Do not include specialisation, in which case the slot constraint matches the provided slot archetype name and version exactly. 2. Include specialisation where any specialisation of the provided slot archetype is allowed (but currently only the same version of the supplied slot archetype). I suggest that we leave (1) as -is to allow precise slot-fills to be defined but loosen (2) to allow any version. 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 Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 23 July 2015 at 01:06, Thomas Beale thomas.be...@oceaninformatics.com wrote: good point. Maybe a slightly more civilised version would be \.v[0-9]+(\..*)? that forces there to be one or more digits, and if there is anything else, it must start with a dot. Somewhat safer perhaps. - thomas On 22/07/2015 23:34, Peter Gummer wrote: Hi Ian, The + is redundant here, since it’s just saying that there has to be one or more digits after the ‘v’. But the next thing that it says is that you can have anything at all after those digits. So you might as well omit the +: \.v[0-9].* This says that there has to be a digit after the ‘v’, followed by anything at all. This amounts to the same, since any extra digits qualify as “anything at all”. Peter On 23 Jul 2015, at 01:55, Ian McNicoll i...@freshehr.com i...@freshehr.com wrote: Thanks Thomas, I will go with \.v[0-9]+.* which will give us a bit of flexibility and solve Dave's problem (I think!). unless anyone strongly objects, of course. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll ___ openEHR-technical mailing listopenEHR-technical@lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [image: Ocean Informatics] http://www.oceaninformatics.com/ *Thomas Beale Chief Technology Officer* +44 7792 403 613 Specification Program, *open*EHR http://www.openehr.org/ Honorary Research Fellow, UCL http://www.chime.ucl.ac.uk/ Chartered IT Professional Fellow, BCS http://www.bcs.org.uk/ Health IT blog http://wolandscat.net/category/health-informatics/ [image: View Thomas Beale's profile on LinkedIn] http://uk.linkedin.com/in/thomasbeale ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Re: Archetype editor, CKM and v0 v1
Hi Silje, Yes, that’s true, and we’ve been wanting to do new releases for a long time but it takes time, which we don’t have. There were some incompatibilities between the tools and also with old archetypes and templates. I think these have been fixed now, but I’m not sure. Somebody would need to test that the tools to make sure that they don’t introduce new problems. If we released them in an unstable state, this could cause much bigger problems. Finding time to work on this is the problem. Regards, Peter On 7 Aug 2015, at 18:07, Bakke, Silje Ljosland silje.ljosland.ba...@nasjonalikt.nomailto:silje.ljosland.ba...@nasjonalikt.no wrote: I’m assuming there’s no reaction to this because everyone is still enjoying their well-earned holidays. ☺ But this is a serious issue, which leads to only people “in the know” being able to download updated tools and create and edit archetypes and templates which conform to the newest patterns. Precisely what we’d like to avoid, isn’t it? Regards, Silje From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bakke, Silje Ljosland Sent: Tuesday, August 04, 2015 10:45 AM To: For openEHR technical discussions Subject: RE: Archetype editor, CKM and v0 v1 On a related note; the openehr.orghttp://openehr.org website still advertises Archetype Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3. Especially now after the v1 - v0 change, the newest builds should be linked from the web site. Kind regards, Silje Ljosland Bakke Information Architect, RN Coordinator, National Editorial Board for Archetypes National ICT Norway Tel. +47 40203298 Web: http://arketyper.nohttp://arketyper.no/ / Twitter: @arketyper_nohttps://twitter.com/arketyper_no From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Thursday, July 23, 2015 1:07 AM To: openehr-technical@lists.openehr.orgmailto:openehr-technical@lists.openehr.org Subject: Re: Archetype editor, CKM and v0 v1 good point. Maybe a slightly more civilised version would be \.v[0-9]+(\..*)? that forces there to be one or more digits, and if there is anything else, it must start with a dot. Somewhat safer perhaps. - thomas On 22/07/2015 23:34, Peter Gummer wrote: Hi Ian, The + is redundant here, since it’s just saying that there has to be one or more digits after the ‘v’. But the next thing that it says is that you can have anything at all after those digits. So you might as well omit the +: \.v[0-9].* This says that there has to be a digit after the ‘v’, followed by anything at all. This amounts to the same, since any extra digits qualify as “anything at all”. Peter On 23 Jul 2015, at 01:55, Ian McNicoll i...@freshehr.commailto:i...@freshehr.com wrote: Thanks Thomas, I will go with \.v[0-9]+.* which will give us a bit of flexibility and solve Dave's problem (I think!). unless anyone strongly objects, of course. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.commailto:i...@freshehr.com twitter: @ianmcnicoll ___ openEHR-technical mailing list openEHR-technical@lists.openehr.orgmailto:openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [Ocean Informatics]http://www.oceaninformatics.com/ Thomas Beale Chief Technology Officer +44 7792 403 613 Specification Program, openEHRhttp://www.openehr.org/ Honorary Research Fellow, UCLhttp://www.chime.ucl.ac.uk/ Chartered IT Professional Fellow, BCShttp://www.bcs.org.uk/ Health IT bloghttp://wolandscat.net/category/health-informatics/ [View Thomas Beale's profile on LinkedIn]http://uk.linkedin.com/in/thomasbeale ___ openEHR-technical mailing list openEHR-technical@lists.openehr.orgmailto:openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
RE: Archetype editor, CKM and v0 v1
Thanks for replying Peter! ☺ I’ve personally used newer versions of both tools than what’s currently on the website, in fact we haven’t used TD v2.6 since we got our CKM in February 2014, since it doesn’t work with Norwegian Bokmål (nb) archetypes. If you need people to do testing for a release I’d be very happy to help, and I’m sure lots of other people would too. Is there any test documentation available so testers can know what to do and where to get the test versions of the tools? Regards, Silje From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Peter Gummer Sent: Friday, August 07, 2015 10:55 AM To: For openEHR technical discussions Subject: Re: Archetype editor, CKM and v0 v1 Hi Silje, Yes, that’s true, and we’ve been wanting to do new releases for a long time but it takes time, which we don’t have. There were some incompatibilities between the tools and also with old archetypes and templates. I think these have been fixed now, but I’m not sure. Somebody would need to test that the tools to make sure that they don’t introduce new problems. If we released them in an unstable state, this could cause much bigger problems. Finding time to work on this is the problem. Regards, Peter On 7 Aug 2015, at 18:07, Bakke, Silje Ljosland silje.ljosland.ba...@nasjonalikt.nomailto:silje.ljosland.ba...@nasjonalikt.no wrote: I’m assuming there’s no reaction to this because everyone is still enjoying their well-earned holidays. ☺ But this is a serious issue, which leads to only people “in the know” being able to download updated tools and create and edit archetypes and templates which conform to the newest patterns. Precisely what we’d like to avoid, isn’t it? Regards, Silje From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bakke, Silje Ljosland Sent: Tuesday, August 04, 2015 10:45 AM To: For openEHR technical discussions Subject: RE: Archetype editor, CKM and v0 v1 On a related note; the openehr.orghttp://openehr.org website still advertises Archetype Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3. Especially now after the v1 - v0 change, the newest builds should be linked from the web site. Kind regards, Silje Ljosland Bakke Information Architect, RN Coordinator, National Editorial Board for Archetypes National ICT Norway Tel. +47 40203298 Web: http://arketyper.nohttp://arketyper.no/ / Twitter: @arketyper_nohttps://twitter.com/arketyper_no From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Thursday, July 23, 2015 1:07 AM To: openehr-technical@lists.openehr.orgmailto:openehr-technical@lists.openehr.org Subject: Re: Archetype editor, CKM and v0 v1 good point. Maybe a slightly more civilised version would be \.v[0-9]+(\..*)? that forces there to be one or more digits, and if there is anything else, it must start with a dot. Somewhat safer perhaps. - thomas On 22/07/2015 23:34, Peter Gummer wrote: Hi Ian, The + is redundant here, since it’s just saying that there has to be one or more digits after the ‘v’. But the next thing that it says is that you can have anything at all after those digits. So you might as well omit the +: \.v[0-9].* This says that there has to be a digit after the ‘v’, followed by anything at all. This amounts to the same, since any extra digits qualify as “anything at all”. Peter On 23 Jul 2015, at 01:55, Ian McNicoll i...@freshehr.commailto:i...@freshehr.com wrote: Thanks Thomas, I will go with \.v[0-9]+.* which will give us a bit of flexibility and solve Dave's problem (I think!). unless anyone strongly objects, of course. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.commailto:i...@freshehr.com twitter: @ianmcnicoll ___ openEHR-technical mailing list openEHR-technical@lists.openehr.orgmailto:openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [cid:image001.jpg@01D0D101.27A48410]http://www.oceaninformatics.com/ Thomas Beale Chief Technology Officer +44 7792 403 613 Specification Program, openEHRhttp://www.openehr.org/ Honorary Research Fellow, UCLhttp://www.chime.ucl.ac.uk/ Chartered IT Professional Fellow, BCShttp://www.bcs.org.uk/ Health IT bloghttp://wolandscat.net/category/health-informatics/ [cid:image002.png@01D0D101.27A48410]http://uk.linkedin.com/in/thomasbeale ___ openEHR-technical mailing list openEHR-technical@lists.openehr.orgmailto:openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
RE: Archetype editor, CKM and v0 v1
I'm assuming there's no reaction to this because everyone is still enjoying their well-earned holidays. :) But this is a serious issue, which leads to only people in the know being able to download updated tools and create and edit archetypes and templates which conform to the newest patterns. Precisely what we'd like to avoid, isn't it? Regards, Silje From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Bakke, Silje Ljosland Sent: Tuesday, August 04, 2015 10:45 AM To: For openEHR technical discussions Subject: RE: Archetype editor, CKM and v0 v1 On a related note; the openehr.org website still advertises Archetype Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3. Especially now after the v1 - v0 change, the newest builds should be linked from the web site. Kind regards, Silje Ljosland Bakke Information Architect, RN Coordinator, National Editorial Board for Archetypes National ICT Norway Tel. +47 40203298 Web: http://arketyper.nohttp://arketyper.no/ / Twitter: @arketyper_nohttps://twitter.com/arketyper_no From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Thomas Beale Sent: Thursday, July 23, 2015 1:07 AM To: openehr-technical@lists.openehr.orgmailto:openehr-technical@lists.openehr.org Subject: Re: Archetype editor, CKM and v0 v1 good point. Maybe a slightly more civilised version would be \.v[0-9]+(\..*)? that forces there to be one or more digits, and if there is anything else, it must start with a dot. Somewhat safer perhaps. - thomas On 22/07/2015 23:34, Peter Gummer wrote: Hi Ian, The + is redundant here, since it's just saying that there has to be one or more digits after the 'v'. But the next thing that it says is that you can have anything at all after those digits. So you might as well omit the +: \.v[0-9].* This says that there has to be a digit after the 'v', followed by anything at all. This amounts to the same, since any extra digits qualify as anything at all. Peter On 23 Jul 2015, at 01:55, Ian McNicoll i...@freshehr.commailto:i...@freshehr.com wrote: Thanks Thomas, I will go with \.v[0-9]+.* which will give us a bit of flexibility and solve Dave's problem (I think!). unless anyone strongly objects, of course. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.commailto:i...@freshehr.com twitter: @ianmcnicoll ___ openEHR-technical mailing list openEHR-technical@lists.openehr.orgmailto:openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [cid:image001.jpg@01D0D0F8.DC60C2A0]http://www.oceaninformatics.com/ Thomas Beale Chief Technology Officer +44 7792 403 613 Specification Program, openEHRhttp://www.openehr.org/ Honorary Research Fellow, UCLhttp://www.chime.ucl.ac.uk/ Chartered IT Professional Fellow, BCShttp://www.bcs.org.uk/ Health IT bloghttp://wolandscat.net/category/health-informatics/ [cid:image002.png@01D0D0F8.DC60C2A0]http://uk.linkedin.com/in/thomasbeale ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
Re: Archetype editor, CKM and v0 v1
Hi Peter I have been using the new versions of the tools in 'live' settings for some time now. I have not come across any showstopper issues. I think we are pretty well ready to go. Ian On Fri, 7 Aug 2015 at 10:54, Peter Gummer peter.gum...@oceaninformatics.com wrote: Hi Silje, Yes, that’s true, and we’ve been wanting to do new releases for a long time but it takes time, which we don’t have. There were some incompatibilities between the tools and also with old archetypes and templates. I think these have been fixed now, but I’m not sure. Somebody would need to test that the tools to make sure that they don’t introduce new problems. If we released them in an unstable state, this could cause much bigger problems. Finding time to work on this is the problem. Regards, Peter On 7 Aug 2015, at 18:07, Bakke, Silje Ljosland silje.ljosland.ba...@nasjonalikt.no wrote: I’m assuming there’s no reaction to this because everyone is still enjoying their well-earned holidays. J But this is a serious issue, which leads to only people “in the know” being able to download updated tools and create and edit archetypes and templates which conform to the newest patterns. Precisely what we’d like to avoid, isn’t it? Regards, *Silje* *From:* openEHR-technical [ mailto:openehr-technical-boun...@lists.openehr.org openehr-technical-boun...@lists.openehr.org] *On Behalf O**f *Bakke, Silje Ljosland *Sent:* Tuesday, August 04, 2015 10:45 AM *To:* For openEHR technical discussions *Subject:* RE: Archetype editor, CKM and v0 v1 On a related note; the openehr.org website still advertises Archetype Editor v2.2.905 beta from 2013, and Template Designer 2.6.1213.3. Especially now after the v1 - v0 change, the newest builds should be linked from the web site. Kind regards, *Silje Ljosland Bakke* Information Architect, RN Coordinator, National Editorial Board for Archetypes National ICT Norway Tel. +47 40203298 Web: http://arketyper.no / Twitter: @arketyper_no https://twitter.com/arketyper_no *From:* openEHR-technical [ mailto:openehr-technical-boun...@lists.openehr.org openehr-technical-boun...@lists.openehr.org] *On Behalf Of *Thomas Beale *Sent:* Thursday, July 23, 2015 1:07 AM *To:* openehr-technical@lists.openehr.org *Subject:* Re: Archetype editor, CKM and v0 v1 good point. Maybe a slightly more civilised version would be \.v[0-9]+(\..*)? that forces there to be one or more digits, and if there is anything else, it must start with a dot. Somewhat safer perhaps. - thomas On 22/07/2015 23:34, Peter Gummer wrote: Hi Ian, The + is redundant here, since it’s just saying that there has to be one or more digits after the ‘v’. But the next thing that it says is that you can have anything at all after those digits. So you might as well omit the +: \.v[0-9].* This says that there has to be a digit after the ‘v’, followed by anything at all. This amounts to the same, since any extra digits qualify as “anything at all”. Peter On 23 Jul 2015, at 01:55, Ian McNicoll i...@freshehr.com wrote: Thanks Thomas, I will go with \.v[0-9]+.* which will give us a bit of flexibility and solve Dave's problem (I think!). unless anyone strongly objects, of course. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 office +44 (0)1536 414994 skype: ianmcnicoll email: i...@freshehr.com twitter: @ianmcnicoll ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- [image: Ocean Informatics] http://www.oceaninformatics.com/ *Thomas Beale Chief Technology Officer* +44 7792 403 613 Specification Program, *open*EHR http://www.openehr.org/ Honorary Research Fellow, UCL http://www.chime.ucl.ac.uk/ Chartered IT Professional Fellow, BCS http://www.bcs.org.uk/ Health IT blog http://wolandscat.net/category/health-informatics/ [image: View Thomas Beale's profile on LinkedIn] http://uk.linkedin.com/in/thomasbeale ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
