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
