<div dir="ltr"><div>Without knowing the internal decision process, I would say that has something to do with the fact that HL7 guys in CIMI already used Loinc for describing document and section codes in CDA (not being uncommon that they just define new Loinc codes to new kinds of documents and sections).<br></div>Same can be achieved with Snomed BTW, Spanish Snomed Extension includes codes for the Compositions, Sections and Entries defined in the national archetypes<br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-03-12 9:12 GMT+01:00 Birger Haarbrandt <span dir="ltr"><<a href="mailto:birger.haarbrandt@plri.de" target="_blank">birger.haarbrandt@plri.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_-8445010536263564367moz-cite-prefix">Hi Gerard,<br>
      <br>
      are you able to provide more information on the reasoning that led
      to this decision? Maybe links to documents or any other insights?
      This would be quite interesting for our acitivities in Germany.<br>
      <br>
      Best,<span class="HOEnZb"><font color="#888888"><br>
      <br>
      -- <br>
      <b>Birger Haarbrandt, M. Sc. <br>
        Peter L. Reichertz Institut for Medical Informatics (PLRI) <br>
        Technical University Braunschweig and Hannover Medical School <br>
        Software Architect HiGHmed Project </b><br>
      Tel: <a href="tel:+49%20176%2064094640" value="+4917664094640" target="_blank">+49 176 640 94 640</a>, Fax: <a href="tel:+49%20531%203919502" value="+495313919502" target="_blank">+49 531/391-9502</a> <br>
      <a class="m_-8445010536263564367moz-txt-link-abbreviated" href="mailto:birger.haarbrandt@plri.de" target="_blank">birger.haarbrandt@plri.de</a> <br>
      <a class="m_-8445010536263564367moz-txt-link-abbreviated" href="http://www.plri.de" target="_blank">www.plri.de</a></font></span><div><div class="h5"><br>
      <br>
      <br>
      <br>
      Am 12.03.2018 um 08:51 schrieb GF:<br>
    </div></div></div>
    <blockquote type="cite"><div><div class="h5">
      
      CIMI made the decision to use LOINC for the ‘question' part of the
      statement.
      <div>And SNOMED for the ‘answer’ part.</div>
      <div>Leading to: Question = Answer, or something coded in
        LOINC is something coded in SNOMED.</div>
      <div>Nodes in an archetype coded in LOINC and data coded
        in SNOMED.<br>
        <div>
          <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><br>
              Gerard   Freriks</div>
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">+31
              620347088<br>
                <a href="mailto:gfrer@luna.nl" target="_blank">gfrer@luna.nl</a></div>
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><br>
            </div>
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">Kattensingel
               20</div>
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">2801 CA
              Gouda</div>
            <div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word">the
              Netherlands</div>
          </div>
        </div>
        <div><br>
          <blockquote type="cite">
            <div>On 12 Mar 2018, at 01:38, Pablo Pazos <<a href="mailto:pablo.pazos@cabolabs.com" target="_blank">pablo.pazos@cabolabs.com</a>>
              wrote:</div>
            <br class="m_-8445010536263564367Apple-interchange-newline">
            <div>
              <div style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
                <div>Now that I have more experience with
                  SNOMED expressions, I like the idea of doing the
                  binding with an expression, also I think an expression
                  includes the single code binding, if that is correct
                  there is no need of defining a different notation for
                  single code binding, just use a simple expression
                  formed by one specific concept code. Also the
                  expression being something processable and very
                  versatile, we can express complex concepts with a few
                  codes, which will help on adding knowledge to the
                  archetype and serve to a better and simpler CDS.<br>
                  <br>
                </div>
                About the metadata, there should be expressed against
                which SNOMED release this expression was created. We
                can't be sure only with min version. I should be
                responsibility of the user to check if the expression
                works on a different version/release of SNOMED. Another
                metadata is if the version is a local extension, some
                countries have their own extensions.<br>
                <br>
              </div>
              <span style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I don't know if we need to
                support other terminologies (technically) and if doing
                that is useful (strategically). Terminology services can
                do SNOMED to ICD, and ICD is not clinical relevant.
                LOINC is useful, but there is a SNOMED-LOINC
                collaboration, so we might expect an official mapping in
                the future (</span><a href="https://loinc.org/collaboration/snomed-international/" style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://loinc.org/<wbr>collaboration/snomed-<wbr>international/</a><span style="font-family:Helvetica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">). IMO we should focus on
                SNOMED.</span></div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="m_-8445010536263564367mimeAttachmentHeader"></fieldset>
      <br>
      </div></div><span class=""><pre>______________________________<wbr>_________________
openEHR-clinical mailing list
<a class="m_-8445010536263564367moz-txt-link-abbreviated" href="mailto:openEHR-clinical@lists.openehr.org" target="_blank">openEHR-clinical@lists.<wbr>openehr.org</a>
<a class="m_-8445010536263564367moz-txt-link-freetext" href="http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org" target="_blank">http://lists.openehr.org/<wbr>mailman/listinfo/openehr-<wbr>clinical_lists.openehr.org</a></pre>
    </span></blockquote>
    <p><br>
    </p>
    <div class="m_-8445010536263564367moz-signature"><br>
    </div>
  </div>

<br>______________________________<wbr>_________________<br>
openEHR-clinical mailing list<br>
<a href="mailto:openEHR-clinical@lists.openehr.org">openEHR-clinical@lists.<wbr>openehr.org</a><br>
<a href="http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org" rel="noreferrer" target="_blank">http://lists.openehr.org/<wbr>mailman/listinfo/openehr-<wbr>clinical_lists.openehr.org</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="margin-bottom:10px;margin-right:10px;font-family:Helvetica,Arial,sans-serif;font-size:12px;line-height:14px"><a href="https://htmlsig.com/t/000001C268PZ" style="text-decoration:none" target="_blank"><img src="https://htmlsigs.s3.amazonaws.com/logos/files/000/669/711/landscape/VeraTech-Horizontal.png" alt="VeraTech for Health SL" height="48" border="0" width="160"></a></p><p style="font-size:0px;line-height:0;font-family:Helvetica,Arial,sans-serif"><a href="https://htmlsig.com/t/000001C47QQH" style="text-decoration:none;display:inline" target="_blank"><img src="https://s3.amazonaws.com/htmlsig-assets/grey/twitter.png" alt="Twitter" style="margin-bottom:2px;border:none;display:inline" height="16" width="16"> </a><span style="white-space:nowrap;display:inline"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2"> </span><a href="https://htmlsig.com/t/000001C4DPJG" style="text-decoration:none;display:inline" target="_blank"><img src="https://s3.amazonaws.com/htmlsig-assets/grey/linkedin.png" alt="LinkedIn" style="margin-bottom:2px;border:none;display:inline" height="16" width="16"> </a><span style="white-space:nowrap;display:inline"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2"> </span><a href="https://htmlsig.com/t/000001BZTWS7" style="display:inline;text-decoration:none" target="_blank"><img src="https://s3.amazonaws.com/htmlsig-assets/grey/maps.png" alt="Maps" style="margin-bottom:2px;border:none;display:inline" height="16" width="16"> </a><span style="white-space:nowrap;display:inline"><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="2"></span></p><img src="https://s3.amazonaws.com/htmlsig-assets/spacer.gif" width="10"><div><p style="font-family:Helvetica,Arial,sans-serif;font-size:12px;line-height:14px;color:rgb(33,33,33);margin-bottom:10px"><span style="font-weight:bold;display:inline">Diego Boscá Tomás</span> <span style="display:inline">/</span> Senior developer<span style="display:inline"></span><span style="display:inline"><br></span><a href="mailto:diebosto@veratech.es" style="color:rgb(190,72,30);text-decoration:none;display:inline" target="_blank">diebosto@veratech.es<span></span></a><br><a href="mailto:yampeku@gmail.com" style="color:rgb(190,72,30);text-decoration:none;display:inline" target="_blank">yampeku@gmail.com</a><span></span></p><p style="font-family:Helvetica,Arial,sans-serif;font-size:12px;line-height:14px;margin-bottom:10px"><span style="font-weight:bold;color:rgb(33,33,33);display:inline">VeraTech for Health SL</span> <span style="display:inline"><br></span><span style="color:rgb(33,33,33);display:inline"><a href="tel:+34%20961%2007%2018%2063" value="+34961071863" target="_blank">+34 961071863</a> / <a href="tel:+34%20627%2001%2050%2023" value="+34627015023" target="_blank">+34 627015023</a> </span><span style="color:rgb(33,33,33)"></span><span style="display:inline"><br></span><span style="color:rgb(33,33,33)"></span><span></span><span style="color:rgb(33,33,33)"></span><span></span><a href="http://www.veratech.es/" style="color:rgb(190,72,30);text-decoration:none;display:inline" target="_blank">www.veratech.es</a></p></div><p style="font-family:Helvetica,Arial,sans-serif;color:rgb(33,33,33);font-size:9px;line-height:12px;margin-top:10px">Su
 dirección de correo electrónico junto a sus datos personales forman 
parte de un fichero titularidad de VeraTech for Health SL (CIF 
B98309511) cuya finalidad es la de mantener el contacto con usted. 
Conforme a La Ley Orgánica 15/1999, usted puede ejercitar sus derechos 
de acceso, rectificación, cancelación y, en su caso oposición, enviando 
una solicitud por escrito a <a href="mailto:veratech@veratech.es" target="_blank">veratech@veratech.es</a>.</p></div></div></div></div>
</div>