Wow Tom! That was a fast, nice and somewhat unexpected answer, now we're just awaiting the caption text to explain the image :-)
You at least got me poking around for the archetypes, finding http://www.openehr.org/svn/knowledge2/TRUNK/archetypes/openEHR_examples/link_archetypes/ - So tooling support already does exist, AWB for viewing & validation and text editor for editing :-) (Or is there more?) - What about the target range constraints, will string matching expressions cover all likely use-cases? - This means a small modification (inherit LOCATABLE) to the LINK class in the RM to make the reference to used archetype possible to store in the EHR, right? (The "un-archetyped" LINK information storage is already supported I believe, so data entered this way would be readable in the current 1.0.2 RM, even if archetype info will not be present, is that correct?) Best regards, Erik Sundvall erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ Tel: +46-13-286733 On Wed, Oct 27, 2010 at 13:45, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > > I mean to attach a view of the AWB with the LINK archetype compiled - let's > see if that works: > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101027/dde1a952/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: moz-screenshot-32.png Type: image/png Size: 8731 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101027/dde1a952/attachment.png>
