Terminology bindings ... again
yampeku at gmail.com
Mon Mar 12 04:44:35 EDT 2018
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).
Same can be achieved with Snomed BTW, Spanish Snomed Extension includes
codes for the Compositions, Sections and Entries defined in the national
2018-03-12 9:12 GMT+01:00 Birger Haarbrandt <birger.haarbrandt at plri.de>:
> Hi Gerard,
> 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.
> *Birger Haarbrandt, M. Sc. Peter L. Reichertz Institut for Medical
> Informatics (PLRI) Technical University Braunschweig and Hannover Medical
> School Software Architect HiGHmed Project *
> Tel: +49 176 640 94 640 <+49%20176%2064094640>, Fax: +49 531/391-9502
> birger.haarbrandt at plri.de
> Am 12.03.2018 um 08:51 schrieb GF:
> CIMI made the decision to use LOINC for the ‘question' part of the
> And SNOMED for the ‘answer’ part.
> Leading to: Question = Answer, or something coded in LOINC is something
> coded in SNOMED.
> Nodes in an archetype coded in LOINC and data coded in SNOMED.
> Gerard Freriks
> +31 620347088
> gfrer at luna.nl
> Kattensingel 20
> 2801 CA Gouda
> the Netherlands
> On 12 Mar 2018, at 01:38, Pablo Pazos <pablo.pazos at cabolabs.com> wrote:
> 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.
> 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.
> 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 (https://loinc.org/collaboration/snomed-international/). IMO we
> should focus on SNOMED.
> openEHR-clinical mailing listopenEHR-clinical at lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
[image: VeraTech for Health SL] <https://htmlsig.com/t/000001C268PZ>
[image: Twitter] <https://htmlsig.com/t/000001C47QQH> [image: LinkedIn]
<https://htmlsig.com/t/000001C4DPJG> [image: Maps]
Diego Boscá Tomás / Senior developer
diebosto at veratech.es
yampeku at gmail.com
VeraTech for Health SL
+34 961071863 <+34%20961%2007%2018%2063> / +34 627015023
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 veratech at veratech.es.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openEHR-clinical