this is an eminently sensible suggestion for how to implement certain
aspects of terminology processing in an openEHR system.
- thomas
On 02/09/2016 06:28, Daniel Karlsson wrote:
Bert,
if I understand your issue correctly, I believe that some sort of
"code index" is needed in openEHR
Bert,
doing most of what you want should come in AQL, e.g. the following in a
WHERE clause is already possible.
SELECT
e/ehr_status/subject/external_ref/id/value,
diagnosis/data/items[at0002.1]/value
FROM
EHR e
CONTAINS Composition c[openEHR-EHR-COMPOSITION.problem_list.v1]
Thomas,
I agree.
In the Semantic Stack various layers are orthogonal and intersect.
The intersection between SNOMED Reference Terminologies and structures
(archetypes) is exactly at the righthand side of the ‘is’ relation.
Codes from SNOMED are ‘universals’, meaning definitions, like entries in
On 02/09/2016 04:04, Bert Verhees wrote:
On 02-09-16 11:18, Daniel Karlsson wrote:
Terminologies typically do not specify which pieces of information
are needed in a given situation.
Hi Daniel, I don't have at the moment opportunity to reply to all you
write, so excuse me for cherrypicking
4 matches
Mail list logo
