There are now some useful links to get to any openEHR terminology group
on the specifications home page
<https://specifications.openehr.org>(scroll down) in one click.
- thomas
___
openEHR-technical mailing list
openEHR-technical@lists.opene
Hmm, interesting idea.
H
-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Peter Gummer
Sent: Wednesday, 10 June 2009 5:50 PM
To: For openEHR technical discussions
Subject: Re: Archetyping links
Rong
discussions'
Subject: RE: Archetyping links
Hi Grahame,
No, I don't think, not directly anyway. The URIs are based on paths which
obviously utilise the archetype and node IDs from Archetypes, but each
implementation of a particular archetyped concept may be in a different
location within
of slot too, but whereas a slot has
aggregation semantics (i.e. the data in the slot is owned by the
containing archetype), a link is just an association. So maybe links
could use the same regular expression patterns that slots use.
- Peter
maybe links
could use the same regular expression patterns that slots use.
- Peter
___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
Hi Rong,
Ocean certainly has runtime support for LINKs. The Ocean Archetype Editor
used to (and perhaps it is still there) have an initial implementation of
constraining LINKs but it became unclear if this was viable, useful or
appropriate. We tend to now think it is a template constrain
, 2009 9:55 AM
To: 'For openEHR technical discussions'
Subject: RE: Archetyping links
Hi Rong,
Ocean certainly has runtime support for LINKs. The Ocean Archetype Editor
used to (and perhaps it is still there) have an initial implementation of
constraining LINKs but it became unclear
to
only allow linkage to instances conforming a specific set of archetypes
(e.g. allowing linkage only to Diagnosis-archetype instances for links
with complication of meaning.) Is it allowed to use a regexp
constraint on the DV_EHR_URI and include the archetype id? Is it
guaranteed that the archetype id
Sorry, forgot the final question: Is this (see preceding email)
implemented in openEHR-based systems?
Regards again,
Daniel
--
Daniel Karlsson, PhD.
Department of Biomedical Engineering/Medical informatics
Link?pings universitet
SE-58185 Link?ping
Sweden
Tel. 013-227573, Mobil: 070-8350109,
or other
artefact) If the order is an openEHR extract it carries the URL with it.
To work efficiently we will need the threads to be easy to follow - this
will mean that the local EHR server will have to know which links point to
which transactions from other transactions - this is an indexing problem
10 matches
Mail list logo
