In the EHRServer we use that approach, template ids have a version number and language: https://github.com/ppazos/cabolabs-ehrserver/wiki/Template-Management-(from-EHRServer-v1.3)
But that is not related to querying. On Sat, Sep 1, 2018 at 2:21 PM Ian McNicoll <i...@freshehr.com> wrote: > We have informally started to add major version number to our template > names. Our assumption is that major and minor changes to any component, > which are not constrained out, should bubble-up to the template. e.g if we > switched from blood_pressure.v1 to blood_pressure.v2 that would require a > template major change. OTOH if we went from blood_pressure.v1.1 -> 1.2 but > none of the 1.2 changes impacted the template we would not change the > template minor version. > > Not sure if that is fully thought through but it follows the spirit of the > archetype id scheme, I think. > > 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 Sat, 1 Sep 2018 at 18:12, Pablo Pazos <pablo.pa...@cabolabs.com> wrote: > >> In the EHRServer the implementation of queries allow to express a >> specific version of an archetype a.b.v1 or all versions a.b.* >> >> We don't use filters based on templates yet. >> >> Not sure how that is implemented in AQL but maybe there is a matches >> operation that can match a regex for any archetype version. >> >> On Sat, Sep 1, 2018 at 2:03 PM Thomas Beale <thomas.be...@openehr.org> >> wrote: >> >>> Dileep, >>> >>> the Archetype Identification specification >>> <https://www.openehr.org/releases/AM/latest/Identification.html> may >>> provide some answers. It undoubtedly needs further development in this area. >>> >>> - thomas >>> >>> On 01/09/2018 15:04, Dileep V S wrote: >>> >>> Hi, >>> >>> As an EHR solution evolves, the templates also tend to evolve to an >>> acceptable level, especially since the archetypes themselves are evolving. >>> However, all the data recorded using different versions of the OPT should >>> remain consistently and easily query-able with out the AQL becoming overly >>> complex and difficult to manage. >>> >>> So is there any best practices in versioning the templates as they >>> evolve so that the incremental evolution does not break the AQLs. The >>> question is do we use the OPT filename(visually identifiable), Name filed >>> in template properties or any of the fields in authorship metadata for >>> indicating the template version? >>> >>> Secondly, is there any template best practices document? >>> >>> >>> >>> -- >>> Thomas Beale >>> Principal, Ars Semantica <http://www.arssemantica.com> >>> Consultant, ABD Project, Intermountain Healthcare >>> <https://intermountainhealthcare.org/> >>> Management Board, Specifications Program Lead, openEHR Foundation >>> <http://www.openehr.org> >>> Chartered IT Professional Fellow, BCS, British Computer Society >>> <http://www.bcs.org/category/6044> >>> Health IT blog <http://wolandscat.net/> | Culture blog >>> <http://wolandsothercat.net/> | The Objective Stance >>> <https://theobjectivestance.net/> >>> _______________________________________________ >>> openEHR-technical mailing list >>> openEHR-technical@lists.openehr.org >>> >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>> >> >> >> -- >> *Ing. Pablo Pazos Gutiérrez* >> pablo.pa...@cabolabs.com >> +598 99 043 145 >> skype: cabolabs >> Subscribe to our newsletter <http://eepurl.com/b_w_tj> >> <https://cabolabs.com/> >> http://www.cabolabs.com >> https://cloudehrserver.com >> >> _______________________________________________ >> 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 > -- *Ing. Pablo Pazos Gutiérrez* pablo.pa...@cabolabs.com +598 99 043 145 skype: cabolabs Subscribe to our newsletter <http://eepurl.com/b_w_tj> <https://cabolabs.com/> http://www.cabolabs.com https://cloudehrserver.com
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
