There are a bunch of AQL examples at
https://github.com/RippleOSI/Ripple-openEHR/tree/master/docs/bindings/Current%20Ripple%20Headings
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Director, freshEHR C
Yes that works. It is also common to use the name/value attribute of the
Composition root to identify a specific composition.
Normally the name/value attribute of a templated Composition defaults to
the underlying Composition archetype croot concept name e.g 'Bericht' but
it can be renamed at templ
Hi Ian,
Sorry, I did not mean specifically imaging data.
What I meant was that all our templates are based on the archetype
openEHR-EHR-COMPOSITION.report.v1.
My question therefore was, if the only possibility to retrieve all data
for a specific template type is by querying with something you de
We are still working on Imaging but the current presumption is that we
would use a generic Imaging Result archetype
https://openehr.org/ckm/archetypes/1013.1.1494
which contains Examination result name and modality elements which we would
query on to find 'Echocardiography' data. The exact use of
Ah, I understand.
I just made the test to use the json_instance_generator of the CoboLabs
openEHR Toolkit by creating an instance of one of my templates. The
template name only appears in the archetype_details. The whole rest
looks like a standard instance of the archetype the template is base
Hi Georg,
You don't find the templates as such, you find compositions committed
against those templates definitions. Templates are just definitions of how
to aggregate archetypes to meet a specific use-case. It is the composition
instance that is committed and queried against. The data within that
Thanks for the answers.
Is a template apart from being a container which aggregates archetypes,
a semi-definition or a derivation of an archetype ? The .oet template
definitions always state a derivation from a an existing archetype
(archetype_id="openEHR-EHR-COMPOSITION.report.v1"), and the t
7 matches
Mail list logo