Hi Ian, Peter was right, the issue was because I've installed ADLWB v1.4.1.595 in my notebook. I downloaded the ADLWB from here: http://wiki.oceaninformatics.com/confluence/display/TTL/ADL+Workbench+ReleasesAnd this page lead my to the old download page: http://wiki.oceaninformatics.com/confluence/display/TTL/ADL+Workbench
That last link is the first result when "adl workbench" is searched using google. Maybe that page could be updated to link the new ADLWB download page: http://www.openehr.org/svn/ref_impl_eiffel/TRUNK/apps/adl_workbench/doc/web/index.html Thanks a lot. -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos From: [email protected] Date: Sat, 29 Sep 2012 09:48:15 +0100 Subject: Re: Issue (probably known) with ADL Workbench To: openehr-technical at lists.openehr.org CC: openehr-clinical at lists.openehr.org Hi Pablo, As far as I can tell this is legal ADL. It is passing the validation on the most recent version of AWB. >From the spec.. ? for partial date/times, any part of the date/time up to the month may be missing, not just seconds and minutes as in the standard; I am sure Thomas will be along later to tell me that I am wrong :-) Ian On 28 September 2012 15:43, pablo pazos <pazospablo at hotmail.com> wrote: Hi all, I've created an archetype with a DvDateTime node with a partial time constraint using the Archetype Editor.Opening the archetype with the ADL WB I get this error message: ------------- compiling openEHR-EHR-COMPOSITION.orden_de_estudio_de_laboratorio.v1 -------------ERROR - line 84: invalid date/time constraint pattern; allowed patterns: YYYY-MM-DDTHH:MM:SS, YYYY-MM-DDTHH:MM:??, YYYY-??-??T??:??:??, YYYY-MM-DDTHH:??:XX, YYYY-MM-DDTHH:MM:XX [last cADL token = V_ISO8601_DATE_TIME_CONSTRAINT_PATTERN] (Parse failed) (ARCHETYPE_PARSER.parse_archetype) The constraint looks like this: ELEMENT[at0009] occurrences matches {0..1} matches { -- fecha esperada del resultado value matches { DV_DATE_TIME matches { value matches {yyyy-mm-ddTHH:??:??} } } } -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos From: [email protected] Date: Tue, 18 Sep 2012 10:27:23 +0100 Subject: Re: Issue (probably known) with ADL Workbench To: openehr-clinical at lists.openehr.org CC: openehr-technical at lists.openehr.org Hi Carlos, I have just uploaded the corrected openEHR-EHR-ITEM_TREE.medication.v1 archetype to CKM. Ian On 18 September 2012 09:41, Carlos Cavero Barca <carlos.cavero at atosresearch.eu> wrote: Great! Thanks Heather! I see they are slightly different than CKM ones. I will have a look at them and let?s see. Regards. Carlos. From: openehr-clinical-bounces at lists.openehr.org [mailto:openehr-clinical-bounces at lists.openehr.org] On Behalf Of Heather Leslie Sent: s?bado, 15 de septiembre de 2012 15:08 To: 'For openEHR technical discussions' Cc: For openEHR clinical discussions Subject: RE: Issue (probably known) with ADL Workbench Hi Carlos - for easy reference: ? The NEHTA Instruction - http://dcm.nehta.org.au/ckm/OKM.html#showarchetype_1013.1.838 ? The NEHTA Action - http://dcm.nehta.org.au/ckm/OKM.html#showarchetype_1013.1.876 Regards Heather -----Original Message----- From: openehr-technical-bounces at lists.openehr.org [mailto:[email protected]] On Behalf Of Carlos Cavero Barca Sent: Friday, 14 September 2012 5:26 PM To: For openEHR technical discussions Subject: RE: Issue (probably known) with ADL Workbench Thanks Ian, I will wait then, I will also have a look at the NEHTA archetypes. I will continue asking about how to include medication properly in the clinical list. Regards. Carlos. -----Original Message----- From: [email protected] [mailto:openehr-technical-bounces at lists.openehr.org] On Behalf Of Ian McNicoll Sent: jueves, 13 de septiembre de 2012 20:20 To: For openEHR technical discussions Subject: Re: Issue (probably known) with ADL Workbench Hi Carlos Welcome to openEHR. This is a known issue, not with the Workbench but with the archetype itself. This is pretty old and breaks a validation rule that was not enforced properly in the Archetype Editor in the past. I have actually fixed or worked around most of the validation errors that AWB reports but have not had time to commit the fixes to CKM yet. As soon as I have a proper web connect I will do so at least for that archetype. The problem is a bit obscure for an openEHR newbie but is related to a bit of ADL syntax that is not currently supported in the Archetype Editor but which is required if multiple constraints of the same datatype are applied to a single element. You should also be aware that our intention is to replace the current CKM medication archetype with others based on the NEHTA medication archetypes. Ian Dr Ian McNicoll Clinical modelling consultant Ocean Informatics Mobile +44 (0) 775 209 7859 Skype imcnicoll On 13 Sep 2012, at 12:00, Carlos Cavero Barca <carlos.cavero at atosresearch.eu> wrote: > > Hi all, > > I'm quite new in openEHR, testing last released version of ADL > workbench I received an error (ERROR line 87 [last cADL token = > V_C_DOMAIN_TYPE]: (VACSIT) cannot add C_DV_QUANTITY object with > rm_type_name=DV_QUANTITY to singly-valued attribute value because > attribute already has child with same RM type) when I tried to load > the openEHR-HER-ITEM_TREE.medication.v1.adl (draft version). I don't > know if this is known or unknown but just in case. > > If I remove from line 73 to line 98 (C_DV_QUANTITY multiple > references, just leaving one of them) the archetype is perfectly loaded. > The same happened with > openEHR-EHR-ITEM_TREE.medication-formulation.v1.adl. In this case the > C_DV_QUANTITY values are empty and you need to include values on them. > > Thanks and regards. > Carlos. > ------------------------------------------------------------------ > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy it. > As its integrity cannot be secured on the Internet, the Atos group > liability cannot be triggered for the message content. Although the > sender endeavours to maintain a computer virus-free network, the > sender does not warrant that this transmission is virus-free and will > not be liable for any damages resulting from any virus transmitted. > > Este mensaje y los ficheros adjuntos pueden contener informacion > confidencial destinada solamente a la(s) persona(s) mencionadas > anteriormente pueden estar protegidos por secreto profesional. > Si usted recibe este correo electronico por error, gracias por > informar inmediatamente al remitente y destruir el mensaje. > Al no estar asegurada la integridad de este mensaje sobre la red, Atos > no se hace responsable por su contenido. Su contenido no constituye > ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. > Aunque se esfuerza al maximo por mantener su red libre de virus, el > emisor no puede garantizar nada al respecto y no sera responsable de > cualesquiera danos que puedan resultar de una transmision de virus. > ------------------------------------------------------------------ > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open > ehr.org _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openeh r.org ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ _______________________________________________ openEHR-technical mailing list openEHR-technical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ _______________________________________________ openEHR-clinical mailing list openEHR-clinical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_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-clinical mailing list openEHR-clinical at lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org _______________________________________________ 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/20121002/02853110/attachment-0001.html>
