Re: SV: [Troll] Terminology bindings ... again

2018-03-24 Thread Jussara Macedo Rötzsch
Heather,

As  you know Brazil has chosen to adopt SNOMED CT on a business case basis,
trying to create clinical models that make the better use of structures and
meaning.
Therefore my research group has dedicated to study detailed clinical models
and to deepen our knowledge of Snomed CT. We agree with GF that we have
four ways to do it and that depends  on the use cases.  As Mikael said
there’s no fix boundary between when you use pre or post coordinatinated
expressions, although context to me naturally is easier to be represented
in the structure ( templates).
TO leverage our knowledge os Snomed CT everyone in our team has taken the
Snomed CT Foundation Course. I think that many assumptions made here are
explained there.
BRAZIL has just joined Snomed CT International. We intend to propose  a
creation of a Worlgroup   focussed on DCMs, for the openEHR community, as
Thomas tried to do years ago.
I will be In London for the next Business meeting, and gladly would have a
meeting with others with the same objective.
Jussara Rötzsch

Em sáb, 24 de mar de 2018 às 04:42, Heather Leslie <
heather.les...@atomicainformatics.com> escreveu:

> Totally agreed, Silje. I think preordination for anatomical location is
> invaluable, but it’s the only use case that I have identified as one we
> absolutely can’t do without.
>
>
>
> But I would love the opportunity to really investigate this properly, and
> with others who understand SNOMED better than I. That will help with the
> boundary issue/semantically grey area.
>
>
>
> I’d prefer that we could use and reuse simpler, really high quality value
> sets from in multiple archetypes for different contexts eg a list of
> diagnoses in the Problem/diagnosis archetype as well as the Family History
> archetype. The archetype context is invaluable here. And the terminology
> community focussing on high value terms that would provide great impact.
>
>
>
> Regards
>
>
>
> Heather
>
>
>
>
>
> *From:* openEHR-technical  *On
> Behalf Of *Bakke, Silje Ljosland
> *Sent:* Friday, 23 March 2018 8:35 PM
>
>
> *To:* For openEHR technical discussions <
> openehr-technical@lists.openehr.org>
>
> *Subject:* RE: SV: [Troll] Terminology bindings ... again
>
>
>
> I read Thomas’ reply with great interest, and I generally agree that with
> a well thought out information model, the very detailed precoordinated
> expressions are redundant. At the same time I understand Mikael’s point of
> view too. BUT, what I’m often met with is that because these precoordinated
> expressions exist (like for example “lying blood pressure” and “sitting
> blood pressure”), we should use them INSTEAD OF using our clever
> information models (that we do have) for recording new data.
>
>
>
> In my opinion this is wrong because it doesn’t take into account that
> healthcare is unpredictable, and this makes recording more difficult for
> the clinician. How many different variations would you have to select from?
> Take the made up example “sitting systolic blood pressure with a medium
> cuff on the left upper arm”; this will be a lot of possible permutations,
> especially if you take into account all the different permutations where
> one or more variable isn’t relevant.
>
>
>
> So while I don’t think the existence of these precoordinated terms in
> itself is a problem, it’s a potential problem that people get a bit
> overzealous with them.
>
>
>
> Regards,
>
> *Silje*
>
>
>
> *From:* openEHR-technical  *On
> Behalf Of *Mikael Nyström
> *Sent:* Friday, March 23, 2018 10:06 AM
> *To:* For openEHR technical discussions <
> openehr-technical@lists.openehr.org>
> *Subject:* SV: SV: [Troll] Terminology bindings ... again
>
>
>
> Hi tom,
>
>
>
> I can agree with you that if SNOMED CT was created when all patients in
> the world already had all information in their health record recorded using
> cleverly built and structured information models (like archetypes,
> templates and similar), but that is not the case. Instead SNOMED CT also
> tries to help healthcare organizations to do something better also with
> their already recorded health record information, because that information
> to a large extent still belongs to living patients.
>
>
>
> It would be interesting to have your opinion about why it is a real
> problem with the “extra” pre-coordinated concepts in SNOMED CT in general
> and not only for the use case of creating archetypes or what would be
> nicest in theory.
>
>
>
>  Regards
>
>  Mikael
>
>
>
>
>
> *Från:* openEHR-technical [
> mailto:openehr-technical-boun...@lists.openehr.org
> ] *För *Thomas Beale
> *Skickat:* den 23 mars 2018 01:06
> *Till:* openehr-technical@lists.openehr.org
> *Ämne:* Re: SV: [Troll] Terminology bindings ... again
>
>
>
> I have made some attempts to study the problem in the past, not recently,
> so I don't know how much the content has changed in the last 5 years. Two
> points come to mind:
>
>
>
> 1. the problem of a profusion of pre

Re: Setting thresholds

2018-02-28 Thread Jussara Macedo Rötzsch
Hi
Ranges  aren’t actually part   of the Information model, they are rules for
decision support, and therefore belong to the Application level, like a gdl
based CDS
Jussara


Em qua, 28 de fev de 2018 às 09:01, Seref Arikan <
serefari...@kurumsalteknoloji.com> escreveu:

> This sounds like something you should handle at the application level
> rather than modeling level to me.
>
> On Wed, Feb 28, 2018 at 11:48 AM, Jan-Marc Verlinden <
> jan-m...@medrecord.io> wrote:
>
>> We are developing a completely openEHR based Personal Health Environment
>> (PHR). For this we would like to show measured data in a graph containing
>> "good" or "bad". Mostly one would see some traffic light system, our
>> approach is different but comes to the same principle.
>>
>> So for this we need to set thresholds that also could be changed
>> afterwards. In the most common BP archetype (and Template) no thresholds
>> are defined, so at what level would we do that?
>> --
>>
>> Regards, Jan-Marc
>> Mobile: +31 6 53785650 <+31%206%2053785650>
>> www.medrecord.io
>>
>> ___
>> openEHR-technical mailing list
>> openEHR-technical@lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

--
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Re: Templates for application form development

2018-02-20 Thread Jussara Macedo Rötzsch
Could we have access to that Pablo?
Regards
Jussara Rotzsch

Em dom, 18 de fev de 2018 às 15:58, Pablo Pazos 
escreveu:

> I have a pdf spec in Spanish, this was a university project to have
> platform independent GUI definitions based on opts, while creating
> technology specific GUI generators for data entry and display. I mentioned
> this a while ago on the lists but catched not much attention.
>
> Need to do a little translation work :)
>
>
> On Feb 18, 2018 7:51 AM, "Thomas Beale"  wrote:
>
>
>
> On 17/02/2018 20:11, Pablo Pazos wrote:
>
>> I think SET has a lot of applications, including result sets.
>> Of course that should interior from LOCATABLE to be archetypable.
>>
>> I'm not sure on the types associated with the UI. I have a specification
>> for UITenplates that includes some of that, I can share it :)
>>
>>
> I think any existing UI/template specification / app modelling would be
> useful to share - possibly on the wiki - let me know if you need a page
> there.
>
> My aim would be to get closer to an IDE application building tool for
> clinical people to at least build a POC application that works, something
> like Balsamiq but with real data connections built in. Marand's EhrExplorer
> does some of this, and it would also be useful to extract some of the
> semantics of that tool into a standard specification to support this kind
> of thing.
>
> - thomas
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

--
___
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org