For those interested in the progress of ADL/AOM 2, I have updated the wiki pages explaining the single-file template format <https://openehr.atlassian.net/wiki/display/ADL/ADL+2+templates+as+single+artefacts>, and showing examples. This page shows some screenshots and generated OPTs <https://openehr.atlassian.net/wiki/display/ADL/ADL+2+Operational+Template>.
Single-file templates are now implemented completely in the ADL 2 Workbench and will be available in the next release, which should be in the next few weeks. (Anyone desperate for an earlier build, please check the AWB home page <http://www.openehr.org/downloads/ADLworkbench/home>regularly, there will be new interim builds every few days). The AOM has been updated to reflect these and other modelling changes; only the Archetype and Terminology packages are affected. Draft versions of the specs with these new models are available here <http://www.openehr.org/programs/specification/releases/currentbaseline#ADL2>. These documents will change in the short term as follows: * review and update explanatory text * replace UML model diagrams with tool-based diagrams In a slightly longer timespan, the specification document will be converted to a new form, probably ODF or Asciidoc. Nevertheless, the UML models and main explanatory text is a reasonably correct reflection of the AOM and ADL 2. These technical changes are the final major updates I propose to make to the formalism. There are various minor technical adjustments likely, including to: * exact details of OPT formats * annotations - we probably need to make the 'value' part of every key/value pair any AOM primitive data rather than just String * AOM may need a proper URI type; still under investigation * the descriptive meta-data may well need some final adjustments, possibly based on / related to ISO Tech Spec 13972 <http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=62416>. * some small adjustments around terminology code representation, based on CIMI / IHTSDO input. These will most likely come out of the forthcoming Specifications Program editorial process. This process is open, and comments are welcome from anyone in the community at any time (we will be establishing a dedicated Jira tracker for this purpose very shortly). So - we more or less at the end of ADL 2 development. There is of course work to do on working out migration strategies for ADL 1.4 based systems and tools, and of course much more to do on ADL 2 tooling. Interim forms of the specifications between 1.4 and 2 may be required for ISO standardisation. But the A lot of people have provided input on these specifications, and as ever we are indebted to them. Their names are recorded in the revision history sections of the specification documents (if anyone has been left out, please contact me). Input from various people in CIMI, Mayo Clinic, Intermountain Healthcare, Polytechnic University Valencia, and of course the openEHR community is much appreciated. - thomas beale -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150125/e4bb02c5/attachment.html>
