gfrer wrote: XFORMS perhaps? > http://www.w3.org/TR/xforms/ > > Gerard
What about Relaxatron? http://www.xml.com/pub/a/2004/02/11/relaxtron.html Unlike W3C schema it makes it simplifies the process of defining constraints on structured documents. The RelaxNG bit does the rules about document section, subsection, data type, etc, while the Schematron bit does the fancy stuff like data ranges, units and co-occurance relations [e.g. if the patient is male then don't allow the pregnancy section, etc] I've been contemplating, on and off, how it might be compiled down into web page GUIs. The basic idea would be to serve and maintain the EHR as a single XML document and apply stylesheets (CSS/XSL) at the client [e.g. using Mozilla or IE6] to make it interactive or not as the case may be. In effect any GUI interaction on the client - through FORM variables etc - would be editing the XML document locally. Eventually the client uploads back to the server where the 'exact-same' RelaxNG-Schematron rules would be used as a check to validate it or not. If the GUI is implemented properly- it would always validate. As far as I can see this will need more than mere stylesheets on the client - it will need scripting (Javascript urgh!). In particular, if the FORM is going to assist the user make choice then some how the selection of choices needs to accompany the arrival of the XML EHR. I.e. the population of drop-down menus is not part of the patient's record it is part of the assistance-to-the-medic and IMHO would be the stuff that 'clinical visual components' [See Thomas Beale above] are made of. Just my eurocents worth :-) \Gavin Gavin Brelstaff - BioMedical Area, CRS4 in Sardinia Loc. Pixina Manna Edificio 1, C.P. n.25, 09010 Pula (CA) Italy. - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
