> > > ------------------------------ > > Message: 2 > Date: Sun, 04 May 2008 21:40:23 +0200 > From: Bert Verhees <bert.verhees at rosa.nl> > Subject: Re: Data-entry for OpenEhr > To: For openEHR technical discussions <openehr-technical at openehr.org> > Message-ID: <481E1127.6060805 at rosa.nl> > Content-Type: text/plain; charset=ISO-8859-1 > > > > I would also like to start importing openEHR content into PatientOS in > > the new few weeks. I am less concerned with the data at this point, > > rather I would like to be able to take a template (perhaps initially > > just archetypes and I will combine them internally to be larger forms) > > import it and make then available as a data entry form (and display). > > > > I am debating whether to parse the XML generated by the Archetype Editor > > (awesome tool by the way) or leverage the java reference implementation > > to read an ADL and then import. I expect the XML would be quicker but > > more prone to break. Though at this point it is a proof of concept not > > a long term solution (which may use the TDS instead). > > I am going to use a temporary solution, to get my data into my system. > It is not that important, it is only maybe 1% percent of all the code > involved, and with no interface change at most places I can switch > easily to another more standardized solution if it comes up, or maybe a > solution a customer wants, is also possible. > > I took a short look at your system (is it yours, or from a team?), I > couldn't find any quick pointers to the architecture behind, and the > standards used. Maybe you can point me to some information. > > I am interested. > > thanks > Bert > >
The system is open source (GPL) so the team is community based and while I have been the primary contributor there are others whose contributions have been more than valuable. The archtecture is distributed with a fat client and could be described as including elements of Domain Model, MVC/ApplicationController, DTO, Gateway, Mediator, though many of the technologies help to simplify things - specifically Hibernate, JBoss using EJB 3.0, RMI. The front end is dynamically generated Swing based upon the database defined content. The database is PostgreSQL though after 1.0 we will start supporting Oracle. PatientOS XML integrates with Mirth which does the heavy lifting for HL7, X12, NCPDP, Web services etc Today (in development) you can build clinical forms with a forms wizard but there have been a few people that have expressed interest in how PatientOS could integrate with OpenEHR. So to start things off I thought I would import archetypes to generate forms but retain the archetype value path so that each data element could be mapped to a corresponding OpenEHR value. How to use that later to support AQL or OpenEHR messages is anyones guess, I will likely wait for some direction at that point from someone who needs that level of integration. I'll start with the XML generated by the Ocean Archetype Editor and let you know when those generated 'forms' can be accessed in the demo. Greg http://www.patientos.org
