I disagree with Rong.
If for example the change between the first and second version is a change
in a position value set from ?sitting?, ?standing? and ?other? to ?sitting?,
?standing?, ?lying? and ?other?. If then a query is written for the first
version of the archetype searching for all
On Tue, Jun 03, 2008 at 11:26:08PM +0200, Mikael Nystr?m wrote:
I therefore think that excluding the version information can result in a
mess.
It shouldn't, of course, be excluded by default but should
be excludable on demand. By, say, allowing regex matching
for path definitions.
Karsten
--
Hi Tim,
-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Tim Cook
Sent: Wednesday, June 04, 2008 4:49 AM
To: For openEHR technical discussions
Subject: Re: openEHR Querying specifications
Hi Tom,
Versions should be handled using the regular expression syntax of the
archetype ID, as is done in ADL to represent slot constraints and
action_arcehtype_id in ACTIVITY.
E.g. [openEHR-EHR-COMPOSITION.encounter.v1*]
BTW, using the OR operator you could have had
...
CONTAINS COMPOSITION
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080604/8eb66047/attachment.html
/openehr-technical_lists.openehr.org/attachments/20080604/270109a7/attachment.html
On Wed, Jun 04, 2008 at 12:42:56AM +0200, Mikael Nystr?m wrote:
It shouldn't, of course, be excluded by default but should
be excludable on demand. By, say, allowing regex matching
for path definitions.
To be excludable on demand is probably a good solution, but I still think
that there
On Wed, Jun 04, 2008 at 09:09:56AM +0930, Heath Frankel wrote:
Versions should be handled using the regular expression syntax of the
archetype ID, as is done in ADL to represent slot constraints and
action_arcehtype_id in ACTIVITY.
E.g. [openEHR-EHR-COMPOSITION.encounter.v1*]
Stef Verlinden wrote:
I'm not a technical person but to me it seems very cumbersome if such
'differences' could exist between 2 versions of the same archetypes.
This would mean that for every query one has to go into detail of
every version of that AT which could mean al lot of work.
To
/20080604/9103ac24/attachment.html
One thing to note: in the MedInfo 2007 page, all the links point
back to
the openEHR.org website, whereas in future conference webpages, we
will
usually upload attachments. The problem we have to tackle is that
conferences is only one way to view material; after a while you want a
http://www.patientos.org
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080604/6b18254a/attachment.html
An important part of the specfications work this year is the upgraded
archetype specification and the new template specification. These
specifications define specialised archeytpes and also openEHR templates.
The latter will now have the equivalent of the Archetype Definition
Language (ADL)
neither Liberty nor Safety. Benjamin Franklin 11 Nov
1755
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080604/4100af17/attachment.html
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080604/3255e5dd/attachment.html
-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080604/5051c0b7/attachment.asc
16 matches
Mail list logo
