Hi Ian & Heath, thanks for the input. I was studying the different formats and the TD, now I get it ;) Work is ongoing to support OPTs on EHRServer, as the source of data definition to index data for querying. I'll wait a little to implement ADL 1.5 since I invested a lot of time on getting my infostructure to work with ADL 1.4.Maybe someone from the community wants to help on that part. Partners are always welcome!
-- Kind regards, Eng. Pablo Pazos Guti?rrez http://cabolabs.com > From: Ian.McNicoll at oceaninformatics.com > Date: Fri, 15 Nov 2013 07:30:51 +0000 > Subject: Re: Ocean's Template Designer and allowedType rules > To: openehr-technical at lists.openehr.org > CC: openehr-implementers at lists.openehr.org > > Hi Pablo, > > I just want to re-emphasise Heath's point for anyone looking to > implement openEHR template support. Your start point should be the > .opt 'Operational template' format. This is what is used by a number > of developers to generate downstream artefacts such asd code > fragments, xsd schema and GUI generation. > > The official openEHR templates will be fully based on ADL1.5, rather > than the current mix of ADL1.4 and Ocean .oet, but the eventual ADL > 1.5 .opt output will be very similar to the current .opt, so this is a > good 'junction point' for transition from ADL1.4 -> ADL 1.5 > > Ian > > On 14 November 2013 21:27, Heath Frankel > <heath.frankel at oceaninformatics.com> wrote: > > Hi Pablo, > > > > The OET format is an internal format. You should export the template as an > > OPT and you will get a AOM and RM based output. > > > > > > > > Heath > > > > > > > > From: openEHR-technical [mailto:openehr-technical-bounces at > > lists.openehr.org] > > On Behalf Of pablo pazos > > Sent: Friday, 15 November 2013 1:06 AM > > To: openeh technical; openehr implementers > > Subject: Ocean's Template Designer and allowedType rules > > > > > > > > Hi all, > > > > > > > > I'm playing with the TD v2.7.60Beta to include openEHR template support to > > CaboLabs EHRServer (http://www.youtube.com/watch?v=D-hs-Ofb8SY) > > > > > > > > I opened the Blood Pressure archetype and tryied to constraint the Any Event > > node of type EVENT to allow only POINT_EVENT, and I get this rule: > > > > > > > > <Rule path="/data[at0001]/events[at0006]"> > > > > <eventConstraint> > > > > <allowedType>PointInTime</allowedType> > > > > </eventConstraint> > > > > </Rule> > > > > > > > > Shouldn't "PointInTime" be "POINT_EVENT"? > > > > > > > > Is there any reason for the TD to not use openEHR datatype names? > > > > > > > > Where can I find all the names used to constraint allowedTypes in TD? > > > > > > > > Thanks! > > > > > > -- > > Kind regards, > > Eng. Pablo Pazos Guti?rrez > > http://cabolabs.com > > > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > > > > -- > Dr Ian McNicoll > office +44 (0)1536 414 994 > fax +44 (0)1536 516317 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian.mcnicoll at oceaninformatics.com > > Clinical Modelling Consultant, Ocean Informatics, UK > Director openEHR Foundation www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > SCIMP Working Group, NHS Scotland > BCS Primary Health Care www.phcsg.org > > _______________________________________________ > 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/20131118/63bcb9b8/attachment.html>
