Thanks for all the responses
I guess I see "problem" as a high level construct, decided by an
expert clinician as a way of "coding" the client's various ongoing,
significant issues in a way that is relevant to management. It could
be a formal diagnosis like Diabetes or a less structured problem like
"smoker". I am not sure how this could be coded in a consistent way -
the definition of a problem can be quite subjective and in general it
is the task of a sophisticated clinician. Short term issues like
"Upper respiratory tract infection" or even "abscess" would not
normally be defined as problems in my practice.
I agree with Marcus on the understanding - I have struggled with the
whole concept of OpenEHR for a long time as a sophisticated clinician
and perhaps somewhat less sophisticated IT enthusiast. I see it as a
data modelling system accessible to clinicians to allow computable
models - which in turn will allow decision support.
But I think the "problem" concept ids an important one
Perhaps we should relax a bit - allow the clinician to create
problems at their discretion which are not necessarily connected to
other elements of the record. This is effectively how it works now.
R
----- Original Message -----
From: "For openEHR clinical discussions"
To:
Cc:
Sent:Thu, 27 Jun 2019 17:05:35 -0300
Subject:Re: Problem orientation in OpenEHR
In a slightly roundabout way, Links from Problem-SOAP Compositiions
to Entries committed at other times is essentially the equivalent of
tagging, and indeed the UI could easily be built to make it look
exactly like tagging, by presenting a list of existing SOAP note
problem names, and the 'tag this under problem X' action would create
the relevant Link.
Literal tagging causes some issues in versioned, medico-legal EHRs,
because you are updating the link target, not the logical link source,
when there is nothing changing in the target.
it seems to me we should think a bit more about (?semi-)persistent
SOAP Compositions, and maybe a related micro-service to make it easy
to do logical tagging that actually does the correct linking...
- thomas
On 27/06/2019 16:33, Marcus Baw wrote:
If I wanted to solve POMR in a simple way without repetition, I'd
use Tagging You'd tag anything relevant to the Problem with that
problem's Tag, you index by Tags too, in a background job Then when
searching by Problem you get all entries Tagged as relevant M
On Thu, 27 Jun 2019 at 19:32, Gunnar Klein wrote:
I do agree pomr has an important role in primary care and I like the
proposal of Thomas to manage it in openEHR. I am not sure why pomr
never took on in hospitals. Larry Weeds idea was not restricted to
primary care.
Gunnar Klein, GP an professor of health informatics
Links:
------
[1] mailto:[email protected]
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
