Hi Thilo,
See my comments inline below...
-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Thilo Schuler
Sent: Monday, June 02, 2008 11:12 PM
To: heath.frankel at oceaninformatics.com; For openEHR
part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/a8e0a160/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/5d6ab130/attachment.html
-- next part --
A non-text attachment was scrubbed...
Name: OceanInformaticsl.JPG
Type: image/jpeg
Size: 5828
Sounds good to me. I think the sub-page for the paper could be an optional
thing but the link from the conference page can either go to a sub page or
directly to the paper. The sub-page approach also assists with the
attachment limit issue (which will need to be administered by someone) and
As part of the ongoing specification work this year, we have started to
build some resource pages for the various specifications. One of them
concerns a querying solution for openEHR - see the wiki page at:
http://www.openehr.org/wiki/display/spec/openEHR+Query+Specifications
I have uploaded
part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/d583d302/attachment.html
Hi!
Using the wiki as first entry for the publications is great for speed
and update/correction capabilities.
- - - The stuff below is a non urgent suggestion for people interested
in long term persistence
of openEHR-related publications, others could stop reading here... - - -
For real
Hi Tom,
On Tue, 2008-06-03 at 16:39 +0100, Thomas Beale wrote:
I have uploaded the Ocean Informatics developed 'Archetype Query
Language' (AQL) as a candidate solution for querying archetype-based
data. As explained in the query specification home page, AQL can be
treated as a starting
:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080603/4281de30/attachment.html
Fair point. Perhaps AQL should support ranges of version numbers to
simplify the query as in many cases the query will not be affected by
a structrural change to the archetype
e.g.
FROM EHR [ehr_id/value=$ehrUid]
CONTAINS COMPOSITION [openEHR-EHR-COMPOSITION.encounter.v[BETWEEN 1.5 AND 2]
-technical at openehr.org
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/20080603/455d222f/attachment.html
11 matches
Mail list logo