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 <[email protected]> wrote: > > 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 would always need an > external tool to create the OPT2 from the ADL repository that you want to > use, instead of an EHR that generates the OPT2s from the source archetypes > itself. Of course, you could just use the ADL workbench or the Archie > adlchecker command-line utility to do it for you, but I’m not sure if it’s a > nice thing to do. > > Also if you only use OPT2, you might want to do queries such as ‘retrieve all > information that is stored in an EHR that has been derived from archetype > with id X, including archetypes specializing from X’ (not just operational > template X). An example: retrieve all reports, or all care plans, regardless > of the used template. To do that, you probably need a specialization section > in the OPT2, which according to the specs should have been removed, and you > also need to create operational templates for archetypes that you never use > to directly create compositions from. Or the tool querying the EHR must be > fully aware of the full archetype specialization tree and use that to create > a query with all specializing archetypes included in the query. > > So, is it intended that the REST API only works with operational templates, > and never archetypes? > > Regards, > > Pieter Bos > > From: openEHR-technical <[email protected]> on > behalf of Thomas Beale <[email protected]> > Reply-To: For openEHR technical discussions > <[email protected]> > Date: Friday, 26 January 2018 at 14:23 > To: Openehr-Technical <[email protected]> > Subject: openEHR REST APIs - Release 0.9.0 / invitation for comments > > > The REST API Team (Bostjan Lah, Erik Sundvall, Sebastian Iancu, Heath > Frankel, Pablo Pazos, and others on the > SEC<https://www.openehr.org/programs/specification/editorialcommittee> and > elsewhere) have made a 0.9.0 Release of the ITS (Implementation Technology > Specifications) component, in order to make a pre-1.0.0 release of the REST > APIs available for wider comment. > > The key point about this current release is that it is meant to be a 'core > basics' foundation of APIs to build on, and some services like CDS, and more > sophisticated querying (e.g. that Erik Sundvall has published in the past) > will be added over time. > > NOTE THAT IN THE 0.9.0 RELEASE, BREAKING CHANGES ARE POSSIBLE. > > You can see the ITS Release 0.9.0 link > here<https://www.openehr.org/programs/specification/latestreleases>, while > the links you see on the specs 'working baseline' > page<https://www.openehr.org/programs/specification/workingbaseline> are the > result of 0.9.0 plus any modifications made due to feedback. The .apib files > are here in > Github<https://github.com/openEHR/specifications-ITS/tree/master/REST_API> > (see mainly the includes directory). > > We are aiming to release 1.0.0 at the end of February, at which point the > formal process kicks in. > > Since we are in Release 0.9.0, the formal PR/CR process is not needed, and > you can comment here. However, if you want to raise a PR you can, in which > case, please set the Component and Affects Version fields appropriately: > > [cid:[email protected]] > > - thomas beale > -- > Thomas Beale > Principal, Ars Semantica<http://www.arssemantica.com> > Consultant, ABD Team, 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/> > <image001.png>_______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
