> > > Message: 1 > Date: Fri, 02 May 2008 00:37:36 +0200 > From: Bert Verhees <bert.verhees at rosa.nl> > Subject: Re: Data-entry for OpenEhr > To: heath.frankel at oceaninformatics.com, For openEHR technical > discussions <openehr-technical at openehr.org> > Message-ID: <481A4630.5020207 at rosa.nl> > Content-Type: text/plain; charset=us-ascii > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > Ocean is also developing the idea of a Template Data Schema, which will > be > > published as a draft on openEHR in the coming months. This does provide > a > > specific XML schema for a template (or combined collect of archetypes) > where > > the XML element names come from the archetype element names, but there > is > > That is fine, but I can't wait for that now. I really have to finish my > work on this in short time. > When the TDS will be released, I will study it and probably implement it > then. > Now I will go on with my schema, which, by the way, works with generated > XML-files too > > Thanks, for your reply, and I hope TDS will be released to public soon. > > Bert
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). thanks! Greg http://www.patientos.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080502/32322dff/attachment.html>
