<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Erik,<br>
      <br>
      just took a look at it: that's some seriously amazing stuff!
      Editing archetypes by using Mindmaps is really a great idea.
      Thanks to all participants for making it happen! <br>
      <h3 class="r" style="font-size: 18px; font-weight: normal; margin:
        0px; padding: 0px; display: block; overflow: hidden;
        text-overflow: ellipsis; white-space: nowrap; color: rgb(34, 34,
        34); font-family: arial, sans-serif; font-style: normal;
        font-variant: normal; letter-spacing: normal; orphans: auto;
        text-align: start; text-indent: 0px; text-transform: none;
        widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
        background-color: rgb(255, 255, 255);"><br>
      </h3>
      Best,<br>
      <br>
      Birger<br>
      <br>
      <br>
      Am 22.08.2015 um 18:10 schrieb Erik Sundvall:<br>
    </div>
    <blockquote
cite="mid:CAEhPwgFazwxjdO9-Lfav1XPF505u6n_UzpVgTns=+FfzO_4exQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">And now some ADL 2.0-related news: as of yesterday
        you can explore the ADL 2.0 capable developer-pre-release of the
        openEHR web based archetype- and template-editors (templates can
        also be exported to OPT 1.4)
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Have a look at the presentation from
          Medinfo yesterday: <a moz-do-not-send="true"
            href="https://goo.gl/7Cd52R">https://goo.gl/7Cd52R</a> </div>
        <div><br>
        </div>
        <div>When the web-client source code has been moved to the right
          place, we'll post info to the lists.<br>
        </div>
        <div class="gmail_extra"><br clear="all">
          <div>
            <div class="gmail_signature">
              <div dir="ltr">
                <div>
                  <div dir="ltr">
                    <div dir="ltr">Best regards,
                      <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">Erik
                        Sundvall </div>
                      <div><font
style="color:rgb(34,34,34);font-family:arial,sans-serif;background-color:rgb(255,255,255)"
                          size="1">Ph.D. Medical Informatics. <span
                            lang="EN-US">Information Architect. Tel:
                            +46-72-524 54 55 (or 010-1036252 in Sweden)<br>
                            Region Östergötland: </span><span
                            style="color:blue" lang="EN-US"><a
                              moz-do-not-send="true"
                              href="mailto:erik.sundvall@regionostergotland.se"
                              target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:erik.sundvall@regionostergotland.se">erik.sundvall@regionostergotland.se</a></a> </span></font><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)"
                          lang="EN-US">(previously <a
                            moz-do-not-send="true" href="http://lio.se"
                            target="_blank">lio.se</a>) <a
                            moz-do-not-send="true"
                            href="http://www.regionostergotland.se/cmit/"
                            target="_blank"><a class="moz-txt-link-freetext" href="http://www.regionostergotland.se/cmit/">http://www.regionostergotland.se/cmit/</a></a> <br>
                        </span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)"
                          lang="EN-US">Linköping University:</span><font
                          size="1"> <a moz-do-not-send="true"
                            href="mailto:erik.sundvall@liu.se"
                            target="_blank">erik.sundvall@liu.se</a>, </font><span
style="color:blue;font-family:arial,sans-serif;font-size:x-small;background-color:rgb(255,255,255)"
                          lang="EN-US"><a moz-do-not-send="true"
                            href="http://www.imt.liu.se/%7Eerisu/"
                            style="color:rgb(17,85,204)" target="_blank">http://www.imt.liu.se/~erisu/</a></span></div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
          <br>
          <div class="gmail_quote">On Thu, Aug 13, 2015 at 9:30 AM, Bert
            Verhees <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:bert.verhees@rosa.nl" target="_blank">bert.verhees@rosa.nl</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <p dir="ltr">Thanks Thomas, for the clarification. Very
                useful. </p>
              <p dir="ltr">Bert</p>
              <div class="gmail_quote">Op 13 aug. 2015 06:26 schreef
                "Thomas Beale" <<a moz-do-not-send="true"
                  href="mailto:thomas.beale@oceaninformatics.com"
                  target="_blank">thomas.beale@oceaninformatics.com</a>>:<br
                  type="attribution">
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  <div>
                    <div class="h5">
                      <div bgcolor="#FFFFFF" text="#000000">
                        <div><br>
                          Dave,<br>
                          <br>
                          I'll try to answer a few. <br>
                          <br>
                          Firstly, please treat the active
                          specifications as what you find by going to
                          the home page 'Specifications' button (top
                          left), i.e. the <a moz-do-not-send="true"
href="http://www.openehr.org/programs/specification/releases/currentbaseline#ADL2"
                            target="_blank">HTML specs here</a>.<br>
                          <br>
                          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. <br>
                          <br>
                          We never released any interim version,
                          although some people think we should, as <a
                            moz-do-not-send="true"
href="https://openehr.atlassian.net/wiki/display/ADL/ADL+1.4+Migration+Roadmap"
                            target="_blank">per this page</a>.<br>
                          <br>
                          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.<br>
                          <br>
                          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 <a
                            moz-do-not-send="true"
href="https://openehr.atlassian.net/wiki/display/ADL/Evolution+from+ADL+1.4"
                            target="_blank">full list is here</a>.<br>
                          <br>
                          The <a moz-do-not-send="true"
                            href="http://www.openehr.org/downloads/ADLworkbench/home"
                            target="_blank">ADL Workbench </a>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. <br>
                          <br>
                          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).
                          <br>
                          <br>
                          ADL/AOM2 is the basis for the OMG Archetype
                          Modelling Language (AML) specification, which
                          has entered the standards track a few months
                          ago.<br>
                          <br>
                          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.<br>
                          <br>
                          There is an <a moz-do-not-send="true"
href="https://github.com/openEHR/specifications/tree/master/ITS/AOM2/XML-schema"
                            target="_blank">XML Schema for ADL / AOM 2
                            here</a>, also reachable from the <a
                            moz-do-not-send="true"
href="http://www.openehr.org/programs/specification/releases/currentbaseline"
                            target="_blank">current specifications page</a>.<br>
                          <br>
                          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.<br>
                          <br>
                          - thomas<br>
                          <br>
                          On 12/08/2015 04:32, Barnet David (HEALTH AND
                          SOCIAL CARE INFORMATION CENTRE) wrote:<br>
                        </div>
                        <blockquote type="cite">
                          <div>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">All</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Hope

                                everyone is well.</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">I
                                have a few questions on ADL versions</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Is

                                there a general view as to when
                                archetypes will be created in an ADL
                                version other than version 1.4?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">I’ve

                                sampled CKMs from various countries
                                & found all archetypes (that I
                                sampled) were in the ADL 1.4 format.</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Some

                                questions:</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Is

                                anyone planning to use anything other
                                than ADL 1.4 in the near future?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">How

                                will CKMs cope with multiple ADL
                                versions in a single CKM?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">When

                                will tools be available to create
                                archetypes in 1.5 and 2.0?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">How

                                will the export format change from ADL
                                1.4 to 1.5 and 2.0?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Will

                                I be able to import an archetype in 1.5
                                or 2.0 into my CKM?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Is

                                there an XML schema available for 1.5
                                and 2.0?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">When

                                do we expect archetypes in 1.5 & 2.0
                                to be the norm?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">What’s

                                the driver to move to archetypes created
                                to DL version 1.5 or 2.0?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Are

                                all the answers in the published
                                document <a moz-do-not-send="true"
                                  href="http://www.openehr.org/releases/trunk/architecture/am/adl2.pdf"
                                  target="_blank">http://www.openehr.org/releases/trunk/architecture/am/adl2.pdf</a>
                                ?</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif"">Regards</span></p>
                            <p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Dave

                                Barnet<br>
                                Health and Social Care Information
                                Centre</span></p>
                            <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">NHS

                                England, UK</span></p>
                          </div>
                        </blockquote>
                        <br>
                        <br>
                        <div>-- <br>
                          <table style="text-align:left" border="0"
                            cellpadding="2" cellspacing="2">
                            <tbody>
                              <tr>
                                <td> <a moz-do-not-send="true"
                                    href="http://www.oceaninformatics.com"
                                    target="_blank"><img alt="Ocean
                                      Informatics"
                                      src="cid:part16.05000201.06080808@plri.de"
                                      height="50" width="111"></a></td>
                                <td> <font size="-1" face="Helvetica,
                                    Arial, sans-serif"> <b>Thomas Beale<br>
                                      Chief Technology Officer</b> </font>
                                  <font size="-2" face="Helvetica,
                                    Arial, sans-serif"> <br>
                                    <a moz-do-not-send="true"
                                      href="tel:%2B44%207792%20403%20613"
                                      value="+447792403613"
                                      target="_blank">+44 7792 403 613</a>
                                  </font> </td>
                                <td> <font size="-2" face="Helvetica,
                                    Arial, sans-serif"> Specification
                                    Program, <a moz-do-not-send="true"
                                      href="http://www.openehr.org/"
                                      target="_blank"><i>open</i>EHR</a>
                                    <br>
                                    Honorary Research Fellow, <a
                                      moz-do-not-send="true"
                                      href="http://www.chime.ucl.ac.uk/"
                                      target="_blank">UCL</a> <br>
                                    Chartered IT Professional Fellow, <a
                                      moz-do-not-send="true"
                                      href="http://www.bcs.org.uk/"
                                      target="_blank">BCS</a> <br>
                                    <a moz-do-not-send="true"
                                      href="http://wolandscat.net/category/health-informatics/"
                                      target="_blank">Health IT blog</a>
                                  </font> </td>
                                <td> <a moz-do-not-send="true"
                                    href="https://uk.linkedin.com/pub/thomas-beale/0/217/68a"
                                    target="_blank"> <img
                                      src="cid:part23.09000007.03020705@plri.de"
                                      alt="View Thomas Beale's profile
                                      on LinkedIn" border="0"
                                      height="15" width="80"></a> </td>
                              </tr>
                            </tbody>
                          </table>
                        </div>
                      </div>
                      <br>
                    </div>
                  </div>
                  _______________________________________________<br>
                  openEHR-technical mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:openEHR-technical@lists.openehr.org"
                    target="_blank">openEHR-technical@lists.openehr.org</a><br>
                  <a moz-do-not-send="true"
href="http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org"
                    rel="noreferrer" target="_blank">http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org</a><br>
                </blockquote>
              </div>
              <br>
              _______________________________________________<br>
              openEHR-technical mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:openEHR-technical@lists.openehr.org">openEHR-technical@lists.openehr.org</a><br>
              <a moz-do-not-send="true"
href="http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org"
                rel="noreferrer" target="_blank">http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org</a><br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
openEHR-technical mailing list
<a class="moz-txt-link-abbreviated" href="mailto:openEHR-technical@lists.openehr.org">openEHR-technical@lists.openehr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org">http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org</a></pre>
    </blockquote>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <b>Birger Haarbrandt, M.Sc.</b><br>
      <p>Peter L. Reichertz Institut für Medizinische Informatik<br>
        Technische Universität Braunschweig und<br>
        Medizinische Hochschule Hannover<br>
        Mühlenpfordtstraße 23<br>
        D-38106 Braunschweig<br>
      </p>
      <p>
        T +49 (0)531 391-2129<br>
        F +49 (0)531 391-9502<br>
        <a class="moz-txt-link-abbreviated" href="mailto:birger.haarbrandt@plri.de">birger.haarbrandt@plri.de</a><br>
        <a class="moz-txt-link-freetext" href="http://www.plri.de">http://www.plri.de</a>
      </p>
    </div>
  </body>
</html>