Hi guys, Maybe we can help.
As David and Sam know I'm working on archetypes too and for now I've created my very simplified version in an XML format that is converted back and forth in David's OpenEMed COAS server. I've gone one step further and added a front-end using the Apache Cocoon webapplication framework which is based on XML and XSL transformations. This results in a generic EHR system that we have tested with a small group of users in the CVA-domain. We also tested how generic it is, by implementing two other domains (AML patients in the hematology dept. and registration of MRSA infections) and proved to be succesful. So I have some knowledge of OpenEMed AND Archetypes and ADL and XML and XSL and a little bit of XML Schema. ;-) On the other hand: my coworker and roommate is involved in the definition of HL7v3 DMIM/RMIM and messages for various aspects of the primary care domain. These XML messages all validate against extensive XML Schema's so we had our share of schema problems. I must confess I don't follow the OpenEHR lists very closely, but this caught my attention and it's nice to see familiar names. I would very much welcome ADL expressed in XML and XML version of properly defined archetypes. I too prefer Java to keep things cross-platform. And both OpenEMed and Cocoon are written in Java, so that made the choice of programming language easy for me. Sorry for the rambling, but I'd very much like to see archetypes get beyond the theoretical state and into working, preferably open source, projects. Bye, Helma -- Helma van der Linden Medical Informatics University Maastricht The Netherlands > -----Original Message----- > From: owner-openehr-technical at openehr.org > [mailto:owner-openehr-technical at openehr.org] On Behalf Of Sam Heard > Sent: Wednesday, 09 March 2005 23:11 > To: openehr-technical at openehr.org > Subject: MCAFEE E-MAIL SCAN ALERT!~RE: ADL TO XML SCHEMA > > > Attachment file : openEHR-EHR-OBSERVATION.blood_pressure.v1.adl > Virus name: Heuristic - (Could be a new virus) > Action taken : Continued... > > Dave > > I am not familiar with Schematron. I have had a look on the web, at > some > tutorials etc - and it is available in the Oxygen editor that I use. > Generally the openEHR approach has been to apply archetypes to the > reference model in memory. This works well and is proven. > > What you are proposing, as far as I can see, might lead to a schema > for > a composition - where the schema met both the archetype constraints > and > the reference model schema. > > It will be relatively easy to test this with something like the blood > pressure archetype. At the moment I can only give you XML data that > fit > the RM schema - the archetype constraints are only expressed in our in > > memory objects. I enclose the archetype and data for your information. > > If we could spit out a schema based on a template (a composition built > > from a set of archetypes) and express the constraints in the > archetype, > this would be well received. It would mean that standard compositions, > > like a discharge summary or a laboratory report, could be expressed as > > XML schema + Schematron. > > I believe this is worth investigating. > > Cheers, Sam > > David W. Forslund wrote: > > What I would like to do is automatically translate from an ADL > description > > to a schematron description. Hopefully, this is semantically > possible. > > > > Dave > > On Tue, March 8, 2005 5:58 pm, Sam Heard said: > > > >>David W. Forslund > >> > >>Good to see you sniffing around! The key issue for us in ADL is that > >>Eiffel is not UNICODE compliant. There will be a number of Java > parsers > >>soon, and I hope a JAVA archetype editor. > >> > >>I am interested in what you can do with Schematron as well as > another > >>implementation route....keep me up to speed. > >> > >>Cheers, Sam > >> > >>>I've been looking at schematron for doing the "equivalent" of > archetype > >>>in > >>>a more general situation, particularly since there as been no ADL > parser > >>>available in Java. Schematron seems to be reasonably popular for > >>>enforcing rules for XML data structures and there is a variety of > >>>software > >>>available for using it. > >>> > >>>Dave > >>>On Tue, March 8, 2005 4:28 am, Gavin Brelstaff said: > >>> > >>> > >>>>Rahil Qamar wrote: > >>>> > >>>> > >>>> > >>>>>Hi Alfonso > >>>>> > >>>>>I can answer one of your questions for certain and am not very > sure > >>>>>about another one. > >>>>> > >>>>>Alfonso Mata wrote: > >>>>> > >>>>> > >>>>> > >>>>>>- Is it possible to obtain a XML-Schema based on 13606 from an > ADL > >>>>>>file? > >>>>>> > >>>>>> > >>>>> > >>>>>You can obtain an XML representation of the ADL Archetype from > the > >>>>>Archetype Editor but not an XML Schema. Atleast not at the > moment. > >>>>>However Im trying to write out a schema based on the UML > Archetype > >>>>>Object Model. Its not proving to be an easy task is all I can say > ! > >>>>>I've > >>>>>done one version of the schema but its far from perfect to > generate a > >>>>>sensible XML. If you are interested in doing some work on this we > could > >>>>>collaborate. > >>>> > >>>>There are some less heavy ways of doing XML rule checking that > >>>>avoid most of the irrational intricacies of the W3C Schema. > >>>>Did you ever explore > >>>>Jim Clark's RelaxNG for schema validation of XML structures, > >>>>and > >>>>Schematron for rules involving Co-occurance relationships. > >>>> > >>>>That might be a way to go. > >>>> > >>>> > >>>>-- > >>>>Gavin Brelstaff - BioMedical Area, CRS4 in Sardinia > >>>>Loc. Pixina Manna Edificio 1, > >>>>C.P. n.25, 09010 Pula (CA) Italy. > >>>>Email: gjb at crs4.it Phone:+39.070.9250.312 Fax:+39.070.9250.216 > >>>> > >>>>- > >>>>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 > >> > > > > > > > << File: openEHR-EHR-OBSERVATION.blood_pressure.v1.adl >> << File: > BloodPressure.xml >> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050309/21566a5b/attachment.html>
