I'm thinking he's talking about the openEHR Archetype Model document,
which would specify the structure of an archetype, and how it constrains
instances of the openEHR reference model. If that's the case, Gavin, this
document is still a work in progress, which is why it's not on the web. The
DSTC archetype editor generates archetypes that conform to the GEHR archetype
model, which is an older version. I hope this helps.

-zar

--
Zar Zar Tun
Titanium Project [ http://titanium.dstc.edu.au ]
DSTC Pty Ltd
**** DSTC is the Australian W3C Office ****

On Wed, 25 Sep 2002, Andrew Goodchild wrote:

>
> Hi Gavin,
>
> I am not entire sure what you mean by an archetype rule. Are there any
> examples of these kinds of "rules" which you envisage the archetype
> encoding and your XUL UI checking?
>
> -Andrew
>
> p.s. We tried going down the path you are working on at the moment, but we
> ended up wanting to support other browsers as well.  We finally ended up
> building a java program which uses a bundle of archetype definition to
> generate a Form for one or more archetypes (with embeded javascript to
> check some basic constraints) and a servlet which interpreted the form
> output and generted the raw XML (note this feature is not in the current
> archetype editor).  The whole process is quite complicated and I am
> impressed that you have managed to wrap your head around it.
>
>
>
> On Tue, 24 Sep 2002, Gavin Brelstaff wrote:
>
> > Hello all - I'm new to the list, pls b kind!
> >
> > My research group here in Italy is looking to combine an openEHR
> > archetype-based design with XUL/Mozilla/XML technology to produce
> > a prototype electronic patient record system accessible via web clients
> > of a certain degree of sophistication.
> >
> > We've been happily designing archetypes using the DSTC Archetype
> > Editor and we've been able to "compile" it's output into XUL front-ends
> > in an automated scheme that involves customised stylesheet amongst other
> > things.
> >
> > How do we generate "archetype rules" to provide constraints
> > internally within archetypes.
> > We would like to use such rules to constrain data at it's point of
> > entry on the client.  We already generate handler code (in Javascript)
> > to ensure the data-type and range constraints are valid.
> >
> > I can find no mention of any "archetype rules" in the openEHR
> > Reference Model nor in the "Design Principles" document.
> > In fact, all I can now find is the example of an
> > invariant on page 25 of Thomas Beale's "Archetypes" report
> > (I've the version issued 21 /Aug/01).
> >
> > Am I missing something obvious or have "archetype rules" been
> > omitted, delayed from consideration?  If so why?
> >
> >
> > I do hope you can help.
> >
> >
> > --
> > Gavin Brelstaff - BioMedical Area, CRS4 in Sardinia
> > VI Strada Ovest, Z.I. Macchiareddu, C.P.94, 09010 Uta (CA) Italy
> > Email: g j b @crs4.it
> > Phone:+39.070.2796.312 Fax:+39.070.2796.216
> > -
> > If you have any questions about using this list,
> > please send a message to d.lloyd at openehr.org
> >
>
>   _-_|\    Andrew Goodchild
>  /     *   DSTC Pty Ltd
>  \_.-._/   Brisbane, Australia
>       v    http://staff.dstc.edu.au/andrewg/
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>

-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org

Reply via email to