> > Message: 1 > Date: Sat, 25 Jul 2009 01:59:36 +0930 > From: "Heath Frankel" <heath.frankel at oceaninformatics.com> > Subject: RE: Issues around UI technologies and bindings to back end > To: "'For openEHR technical discussions'" > <openehr-technical at openehr.org> > Message-ID: > <00db01ca0c7b$f05e67f0$d11b37d0$@frankel at oceaninformatics.com> > Content-Type: text/plain; charset="us-ascii" > > There is an open source ADL to XML conversion library for .NET written in > c# > located at > > http://www.openehr.org/svn/knowledge_tools_dotnet/RELEASES/BlueChina/XMLPars > er. This is used by the Archetype Editor to generate a pure XML > representation of the ADL file via the ADL_Parser so that it can create a > canonical xml representation of the archetype model for hashing purposes. > The XML displayed and files generated directly from the Archetype Editor > uses a different (legacy) mechanism and is not as reliable as that produced > by the conversion library, the result is slightly different XML output. We > just have not had enough volunteer time to replace this legacy approach > within the Archetype Editor. > > > > If anyone need assistance in using this conversion library I can provide an > NUnit test library that shows how it can be used, or you can sift through > the Archetype Editor code if you prefer VB. > > > > We actually have a publishing tool using this library that can run a batch > process against an entire Archetype file repository that can be run within > an auto-build process and committed back into svn. This is how the XML > archetypes on openEHR used to get generated prior to CKM. > > > > I am not sure if CKM supports XML output of archetypes as yet but if it is > felt that not having archetypes available in XML is holding back openEHR > adoption then I am sure this can be put on the change request list for > prioritisation. > > > > > > Regards > > > > Heath > > > > Generating XML from ADL is one piece - but what is needed is the schema definition and not the generic one that fits all archetypes but rather one that is specific to the data elements and content of each archetype.
The technical people working with Archetypes today are obviously content with working with an ADL file but IMHO the software developers of tomorrow need to spend about 1 hour evaluating archetypes, import the definitions and then demonstrate that this well thought out, well structured OpenEHR data is of more value that defining ones own data hierarchy using HL7, LOINC, SNOMED etc. XML, XSD has orders of more tooling support, ADL only has the few tools available that we know of and that affects productivity. If XML/XSD became the defacto standard I could take our administrative and billing data model and convert into 'archetypes' and quickly people could begin to review them. As the CKM clinical reviews take place and the quality and quantity of the clinical archetypes increases the content becomes more valuable. But without easy access to that content I believe it does hamper adoption. -- Gregory Caulton Principal at PatientOS Inc. personal email: caultonpos at gmail.com http://www.patientos.com corporate: (888)-NBR-1EMR || fax 857.241.3022 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20090725/3ef081b8/attachment.html>
