On the question of OPT2, it's fully defined from the point of view of
ADL2, which is to say that if you run the 'flatten' operation on an ADL2
source template, it generates something for you, which can be serialised
in ADL2, ODIN, JSON, YAML and XML (the ADL WB does this, and I didn't
check, but I assume Archie replicates these).
However... there is the question of post-processing the flattened output
('Raw OPT' in the diag below) to do things like choosing/reducing
languages, possibly removing annotations, reducing terminology bindings,
potentially replacing inline at- and ac-codes with their binding values
(i.e. concept or value-set refs from actual terminologies).
opt tool chain
See here in the OPT2 spec
<https://specifications.openehr.org/releases/AM/latest/OPT2.html#_types_of_opt>.
These post-processing stages are what need further specification.
The AOM2 XSD is here
<https://github.com/openEHR/specifications-ITS-XML/tree/master/components/AM/latest>,
which I think is the one I wrote some years ago, possibly amended by
others since. I doubt if this has undergone sufficient rigorous testing
to be considered entirely reliable yet.
With respect to preserving lineage in templates, this was contemplated
in the Archetype Identification spec
<https://specifications.openehr.org/releases/AM/latest/Identification.html#_supporting_archetype_based_querying>,
but not integrated into any other specification at this stage.
- thomas
On 12/02/2019 19:47, Seref Arikan wrote:
Thank you. Please see inline
On Tue, Feb 12, 2019 at 7:02 PM Pieter Bos <pieter....@nedap.com
<mailto:pieter....@nedap.com>> wrote:
I mean OPT2, which is according to the ooenehr specifications a
flattened archetype with extra operations performed on it, such as
including and flattening all archetype roots in the same tree,
including their terminologies,and replacing all use_node with a
copy of the tree to be used. Very useful. Can be expressed in ADL.
I did not realise that opt2 was fully defined. I thought it was
ongoing work. I'll have to go and check it now :)
Archie does not support the 1.4 xml OPT format.
Thanks for the clarification.
Note that xml bindings are in place for the AOM, but I wouldn't
use them for interoperability because they were written before an
official xsd has been published - I'm actually not sure if an
official AOM 2 xsd currently exists.
Could you please clarify which official XSD you're referring to? AOM2?
Note that there is also the concept of a template, which is also
an archetype, but is different from an operational template -
templates are authored, opts are generated, often generated from a
template.
Hmm. I guess this means opts lose some information regarding their
lineage.
Regards,
thanks a lot for the detailed response.
_______________________________________________
openEHR-implementers mailing list
openEHR-implementers@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-implementers_lists.openehr.org
