Hi Bert,
A dv_coded text can carry a single defining_code but as many code mappings
as you wish. This makes sense to me as I would always expect one code to be
regarded as the original clinical source of truth, and other mappings to be
regarded as secondary. All of these can be queried via AQL. Th
Hi All
The idea was that the code_phrase was directly entered as part of choosing the
text from the terminology.
Anywhere where coding is done as a secondary process, the code mappings allow
multiple codes.
I think this meets all the needs you have specified. Mappings allow each
terminology to
Perhaps the best solution for the time being is to add an additional diagnosis
component with the secondary terminology binding that might be used. This is
not so common and would need a BR specialization.
Beatriz
> On Mar 15, 2017, at 6:31 PM, Bert Verhees wrote:
>
> We are considering th
We are considering that Diego, the fact is that the customer wishes to code
the name -item two times. Both coding - systems are not easy to map and the
mapping cannot be calculated easily by software.
So we need two Dv_coded_text's to carry the codes, and only one value to
carry the name.
The pro
e)?
> >
> > Thanks for any help.
> >
> > Best regards
> > Bert Verhees
> >
> > ___
> > openEHR-clinical mailing list
> > openEHR-clinical@lists.openehr.org
> >
> > http://lists.openehr.org/mailman
Thanks Ian, that explains.
Best regard
Bert
Op wo 15 mrt. 2017 om 12:14 schreef Ian McNicoll :
> Hi Bert
>
> This is correct. If you were to add those constraints in a specialised
> archetype, at run-time the submitted term in the defining_code attribute
> would have to come from one of the two
What about having two sibling DV_CODED_TEXT nodes as alternatives on the
parent? (or specialize two different ones from the single parent one). That
would allow to arbitrarily define constraint binding as needed, and in data
only one would be correct one
2017-03-15 12:13 GMT+01:00 Ian McNicoll :
Hi Bert
This is correct. If you were to add those constraints in a specialised
archetype, at run-time the submitted term in the defining_code attribute
would have to come from one of the two terminologies specified.
The constraint can define multiple potential terminologies but only one
defining_
Dear readers,
I have a problem and I want to ask your advise.
The problem is that I want to
use openEHR-EHR-EVALUATION.problem_diagnosis.v1 which is in CKM.
In that archetype is the item "Problem/Diagnosis name", which is of type
DV_TEXT. We want to use it as DV_CODED_TEXT, because we want to ad
Nice job Sebastian
Many thanks
Tony
On 13 March 2017 at 13:41, Sebastian Garde <
sebastian.ga...@oceaninformatics.com> wrote:
> Dear all,
>
>
>
> We have just updated the openEHR Clinical Knowledge Manager.
>
>
>
> This CKM release adds a new Dashboard for new or not logged-in users. It
> also
10 matches
Mail list logo