Re: Archetype editor, CKM and v0 v1
Technically speaking, if we want to properly match any archetype in a slot, we need a regex that will match any level of versioning id. Since matched archetypes will eventually all have 3-part versions (but today might have only 1-part versions), we need to match thngs like .v0 .v1 .v0.0.1 .v3.0.2 and so on. So Diego's expression will do that. But Sebastian is correct - some of the matched archetypes could be test or research archetypes. So you need the remaining bit as well. You could in theory use: v[0-9]+(\.[0-9]+(\.[0-9]+((-rc|-alpha)(\.[0-9]+)?)?)?)? but I would say it is overkill (you only use regexes like that when you think there could be garbage version ids and you want to catch them and reject them). A reasonable balance is probably something like \.v[0-9]+.* which forces at least one digit of major version, and allows anything at all to come after, which is reasonable if we assume that no tools will create completely invalid version ids. For reference, there are some useful regexes here https://github.com/openEHR/adl-tools/blob/master/libraries/openehr/src/am/archetype/archetype_hrid.e. - thomas On 22/07/2015 15:26, Sebastian Garde wrote: My understanding was that minor version and patch version would not be part of the normal archetype id, which is what you are looking for here? Otherwise you'd need to allow -alpha etc here as well? Sebastian ___ 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 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 Co-Chair, openEHR Foundation ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 22 July 2015 at 16:37, Thomas Beale thomas.be...@oceaninformatics.com wrote: Technically speaking, if we want to properly match any archetype in a slot, we need a regex that will match any level of versioning id. Since matched archetypes will eventually all have 3-part versions (but today might have only 1-part versions), we need to match thngs like .v0 .v1 .v0.0.1 .v3.0.2 and so on. So Diego's expression will do that. But Sebastian is correct - some of the matched archetypes could be test or research archetypes. So you need the remaining bit as well. You could in theory use: v[0-9]+(\.[0-9]+(\.[0-9]+((-rc|-alpha)(\.[0-9]+)?)?)?)? but I would say it is overkill (you only use regexes like that when you think there could be garbage version ids and you want to catch them and reject them). A reasonable balance is probably something like \.v[0-9]+.* which forces at least one digit of major version, and allows anything at all to come after, which is reasonable if we assume that no tools will create completely invalid version ids. For reference, there are some useful regexes here https://github.com/openEHR/adl-tools/blob/master/libraries/openehr/src/am/archetype/archetype_hrid.e . - thomas On 22/07/2015 15:26, Sebastian Garde wrote: My understanding was that minor version and patch version would not be part of the normal archetype id, which is what you are looking for here? Otherwise you'd need to allow -alpha etc here as well? Sebastian ___ 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
Archetype editor, CKM and v0 v1
Hi All I'm having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example openEHR-EHR-OBSERVATION. blood_pressure.v1.adl When I upload the archetype to CKM, the process renames the archetype to version 0 - for example openEHR-EHR-OBSERVATION. blood_pressure.v0 (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it's a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won't exist on the CKM (so CKM can't make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.ukmailto:david.bar...@hscic.gov.uk www.hscic.gov.ukhttp://www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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
That will be the one then. Thx Ian On Wed, 22 Jul 2015 at 14:29, Diego Boscá yamp...@gmail.com wrote: Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0) El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com escribió: Thanks Diego What is the difference between the 2 ? Ian On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote: Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. 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 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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 ___ 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
Re: Archetype editor, CKM and v0 v1
Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0) El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com escribió: Thanks Diego What is the difference between the 2 ? Ian On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote: Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. 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 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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 ___ 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
Thanks Diego What is the difference between the 2 ? Ian On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote: Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. 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 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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 ___ 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 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.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
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 mailto: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 mailto: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 -- 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/ 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
Re: Archetype editor, CKM and v0 v1
Good point Sebastian, I was really thinking towards the future and the same slot constraints appearing or being redefined in templates where tighter constraints might be needed. Is that overkill? 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 22 July 2015 at 15:26, Sebastian Garde sebastian.ga...@oceaninformatics.com wrote: My understanding was that minor version and patch version would not be part of the normal archetype id, which is what you are looking for here? Otherwise you'd need to allow -alpha etc here as well? Sebastian On 22.07.2015 16:00, Ian McNicoll wrote: That will be the one then. Thx Ian On Wed, 22 Jul 2015 at 14:29, Diego Boscá yamp...@gmail.com yamp...@gmail.com wrote: Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0) El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com escribió: Thanks Diego What is the difference between the 2 ? Ian On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com wrote: Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 %2B44%20%280%29775%20209%207859 office +44 (0)1536 414994 %2B44%20%280%291536%20414994 skype: ianmcnicoll email: i...@freshehr.comi...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.orgian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ openEHR-technical
Re: Archetype editor, CKM and v0 v1
My understanding was that minor version and patch version would not be part of the normal archetype id, which is what you are looking for here? Otherwise you'd need to allow -alpha etc here as well? Sebastian On 22.07.2015 16:00, Ian McNicoll wrote: That will be the one then. Thx Ian On Wed, 22 Jul 2015 at 14:29, Diego Boscá yamp...@gmail.com mailto:yamp...@gmail.com wrote: Second one allows both the new and the old versioning (e.g. v0.0.5 vs v0) El 22/7/2015 15:12, Ian McNicoll i...@freshehr.com mailto:i...@freshehr.com escribió: Thanks Diego What is the difference between the 2 ? Ian On Wed, 22 Jul 2015 at 13:55, Diego Boscá yamp...@gmail.com mailto:yamp...@gmail.com wrote: Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com mailto:i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. Ian Dr Ian McNicoll mobile +44 (0)775 209 7859 tel:%2B44%20%280%29775%20209%207859 office +44 (0)1536 414994 tel:%2B44%20%280%291536%20414994 skype: ianmcnicoll email: i...@freshehr.com mailto:i...@freshehr.com twitter: @ianmcnicoll Co-Chair, openEHR Foundation ian.mcnic...@openehr.org mailto:ian.mcnic...@openehr.org Director, freshEHR Clinical Informatics Ltd. Director, HANDIHealth CIC Hon. Senior Research Associate, CHIME, UCL On 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk mailto:david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk mailto:david.bar...@hscic.gov.uk www.hscic.gov.uk http://www.hscic.gov.uk This message may contain confidential information. If you are not the intended
Re: Archetype editor, CKM and v0 v1
Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. 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 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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
Put v[0-9] or v[0-9](\.[0-9])* to allow multiple subversions El 22/7/2015 14:22, Ian McNicoll i...@freshehr.com escribió: Hi Dave, I recognise the problem which is a result of the transition to a much richer and better versioning mechanism. The Archetype Editor has been updated to handle the new versioning (on the openEHR Github, not released yet ) but we will need to adapt the slot fill regex to allow for .v0 archetypes, which are now the default for new, uncontrolled archetypes. The default regex for slot-fill pattern needs to be changed to allow any Version not just V1 openEHR-EHR-CLUSTER\.context_detail(-[a-zA-Z0-9_]+)*\.v1/} I am not a regex expert - If someone can guide me on how to change this to allow .v*, I can update the AE code. We will almost certainly have to edit some legacy archetype ADL as well. 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 22 July 2015 at 12:33, Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE) david.bar...@hscic.gov.uk wrote: Hi All I’m having a bit of an issue with CKM re-versioning archetypes and slots that reference Clusters. When I create a new archetype in the archetype editor (Version 2.2.905 Beta), the archetype is saved as version 1. For example “openEHR-EHR-OBSERVATION. blood_pressure.v1.adl” When I upload the archetype to CKM, the process renames the archetype to version 0 – for example “openEHR-EHR-OBSERVATION. blood_pressure.v0” (we are hosted on version 1.4.0 of the Clinical Knowledge Manager) The re-versioning becomes an issue when I use slots. In the Archetype editor I can assign a slot to a Cluster (for example), but this process creates a link to a version of the Cluster. If it’s a new Cluster, this will be version 1. When the Cluster and the archetype are uploaded to the CKM, they are both put back to version 0. However, the slot Cluster is looking for version 1 of the Cluster, which won’t exist on the CKM (so CKM can’t make the link between these 2 objects). Does anyone have a work-around, or have some advice and guidance, for this issue? Kind Regards Dave Barnet Interoperability Lead Interoperability Specifications Health Social Care Information Centre david.bar...@hscic.gov.uk www.hscic.gov.uk This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ___ 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
