Dave,
I'll try to answer a few.
Firstly, please treat the active specifications as what you find by going to the home page 'Specifications' button (top left), i.e. the HTML specs here <http://www.openehr.org/programs/specification/releases/currentbaseline#ADL2>\.
Second point, 'ADL 1.5' was what we used for a long time as the moniker for 'next generation ADL', until we realised that we introduced breaking changes due to CIMI, OMG/AML and openEHR development work. So 'ADL / AOM 2' is the 'modern' archetype formalism.
We never released any interim version, although some people think we should, as per this page <https://openehr.atlassian.net/wiki/display/ADL/ADL+1.4+Migration+Roadmap>\.
The ADL / AOM 2 specs referred to above are not yet quite complete - there are a few more additions to the documents, and 2 very minor potential semantic changes - semantic slots and smarter annotations. I would expect these specs to be ready for release formal TRIAL in the next 4 weeks.
Why does ADL2/AOM2 exist? It addresses various limitations in ADL1.4, including lack of proper modelling for specialisation, templating, proper versioning and id rules, and proper value sets. A full list is here <https://openehr.atlassian.net/wiki/display/ADL/Evolution+from+ADL+1.4>\.
The ADL Workbench <http://www.openehr.org/downloads/ADLworkbench/home>will reliably (in most cases) convert ADL 1.4 archetypes to ADL 2 form. This transform is not trivial, so anyone who wants to do this conversion should use this tool, or the command line version.
CIMI is using only ADL/AOM 2, and CIMI will become a working group of some kind in HL7 (agreed but not finalised yet), so HL7 will potentially use ADL 2 at some point (but I assume jut the CIMI workgroup for some time).
ADL/AOM2 is the basis for the OMG Archetype Modelling Language (AML) specification, which has entered the standards track a few months ago.
On the ground in openEHR implementation space, ADL 1.4 is being used. New tools that are internally ADL 2 will / do generate ADL 1.4 OPTs to enable these systems to keep running. The ADL Workbench doesn't yet do this but will.
There is an XML Schema for ADL / AOM 2 here <https://github.com/openEHR/specifications/tree/master/ITS/AOM2/XML-schema>, also reachable from the current specifications page <http://www.openehr.org/programs/specification/releases/currentbaseline>\.
The tougher question to answer is when systems will move to ADL 2. THere are two questions: EHR systems, and tools. Tools can move faster, and are already being changed. CKM also incorporates some ADL 2 features already. EHR systems will move more slowly and carefully for obvious reasons, which is why we need ADL 1.4 OPT support in next gen tools. I would expect some vendors to eventually support ADL 1.4 and ADL2, and existing ADL 1.4 based deployments may stay on ADL 1.4.
- thomas
(attachments)
