The correct artefact to use for this purpose is the operational template originally developed by Ocean.
If you look at the Marand ehrscape API dev.ehrscape.com you will see how it used The Ocean, code24, Privantis, Infinnity , ADOC. Cabolabs and Nousco backends all use this format. Ian On Tue, 14 Apr 2015 at 12:32, Dmitry Baranov <baranovda at yandex.ru> wrote: > Hi Ian, > I'm trying to implement a EHR module that uses Oracle XML DB as a storage > for clinical records in form of clinical document. A template defines the > structure of such document (consultation note, evaluation note, operation > note and so on), and EHR module produces a document that match particular > template. So I just need an XML-schema-based template definition format but > can't decide which one is more suitable. > Got your links, thank you. > > > > .oet is an internal Ocean format used by the Template Designer. > > As far as I know this is the current version > > > https://github.com/openEHR/java-libs/blob/master/oet-parser/src/main/xsd/CompositionTemplate.xsd > > The key template schema which you should probably be investigating is > the Operational > > Template .opt (which is generated by the Template Designer). > > > https://github.com/openEHR/java-libs/blob/master/oet-parser/src/main/xsd/Template.xsd > > It depends on what are you trying to do. Can you tell us more about your > project? > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150414/5f382a29/attachment.html>
