Modeling generic concepts, considerations for querying

Ian McNicoll ian.mcnicoll at gmail.com
Tue Sep 26 05:40:11 EDT 2017


Hi due to

We developed a UK oriented termsrt as the LOINC based list used by HL7 CDA
was too US oriented but the principle is identical. We will probably apply
the term to composition name/value which allows mappings rather than the
templateid. Both are available to AQL

Ian


On 26 Sep 2017 at 10:24, <Diego Boscá <yampeku at gmail.com>> wrote:

I agree with Ian that we should probably use a real 'coded' approach? I
believe HL7 uses Loinc for that. Spanish MoH has also proposed snomed terms
for each entry in the national archetypes. Maybe we can explore something
like this before trying to create our own pseudoterminology

2017-09-26 11:10 GMT+02:00 Ian McNicoll <ian.mcnicoll at gmail.com>:

> Hi Heather
>
> That is pretty well my approach too. I think we will start yo see more
> formal coding of composition names to be able to accurately identify the
> content. In the UK we have developed a document name SNOMED subset for this
> purpose and will also use this for ihe xds metadata.
>
> Ian
>
> On 26 Sep 2017 at 09:58, <Heather Leslie
> <heather.leslie at oceanhealthsystems.com>> wrote:
>
> Hi Pablo,
>
>
>
> The modeller’s dilemma!
>
>
>
> If you make clinical synopsis more specific then how many variations will
> there be in the end? We will end up with zillions of variations of all the
> generic archetypes which will be an absolute governance nightmare.
>
>
>
> I would prefer to see the queryable filter made at the template level –
> even as simply as using the COMPOSITION.encounter inside a ‘Psychotherapy
> consultation’ template. Use that template within all of the Psychotherapy
> consults for that app consistently.
>
>
>
> Then query for the EVALUATION.clinical_synopsis across all templates that
> contain the COMPOSITION.encounter which has specifically been renamed to
> ‘Psychotherapy consultation’.
>
>
>
> Regards
>
>
>
> Heather
>
>
>
> *From:* openEHR-clinical [mailto:openehr-clinical-
> bounces at lists.openehr.org] *On Behalf Of *Pablo Pazos
> *Sent:* Tuesday, 26 September 2017 11:52 AM
> *To:* For openEHR clinical discussions <openehr-clinical at lists.openehr.org
> >
> *Subject:* Modeling generic concepts, considerations for querying
>
>
>
> Hi all,
>
>
>
> I'm working with the clinical synopsis archetype, using it to model very
> open psychotherapy notes. The difference of that archetype from, for
> instance, blood pressure, triage, problem/diagnosis, is these archetypes
> are more or less very specific concepts, while synopsis might be used in
> many contexts, by different specialties, to save different kinds of data.
> The synopsis itself is a very generic concept.
>
>
>
> Considering querying for a synopsis, I think queries should consider the
> context, not only the archetype id. For instance if I want the
> psychotherapy notes instead of other kinds of clinical synopsis, some extra
> data should be given in the query.
>
>
>
> I can see two ways of doing this, with more 1. specific archetypes or 2.
> using templates to filter the query results. 1. means the synopsis
> archetype might  be specialized to synopsis-psychotherapy, so queries can
> use that new archetype id. 2. at the template level using the synopsis
> archetype, and the template is for psychotherapy. This implies the template
> id should be used on the query as context/filter.
>
>
>
> What alternative do clinical modelers see as more correct?
>
>
>
> I like specializing archetypes because we can keep queries simple, but we
> might end up with a lot of archetypes. Using templates makes queries more
> complex, but we don't need more archetypes for specializations.
>
>
>
> Thanks!
>
>
>
> PS: please let me know if this doesn't make sense :)
>
>
> --
>
> Ing. Pablo Pazos Gutiérrez
> e: pablo.pazos at cabolabs.com
> p: +598 99 043 145 <+598%2099%20043%20145>
> skype: cabolabs
>
> <http://cabolabs.com/>
> http://www.cabolabs.com
> https://cloudehrserver.com
> Subscribe to our newsletter <http://eepurl.com/b_w_tj>
>
>
> _______________________________________________ openEHR-clinical mailing
> list openEHR-clinical at lists.openehr.org http://lists.openehr.org/
> mailman/listinfo/openehr-clinical_lists.openehr.org
>
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-
> clinical_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]
<https://htmlsig.com/t/000001BZTWS7>

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
<+34%20627%2001%2050%2023>
www.veratech.es

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.
_______________________________________________ openEHR-clinical mailing
list openEHR-clinical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20170926/488a675a/attachment-0002.html>


More information about the openEHR-clinical mailing list