Issue (probably known) with ADL Workbench

2012-10-03 Thread Peter Gummer
pablo pazos wrote: 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+Releases And this page lead my to the old download page:

Issue (probably known) with ADL Workbench

2012-10-02 Thread pablo pazos
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

Issue (probably known) with ADL Workbench

2012-10-02 Thread pablo pazos
known) with ADL Workbench From: peter.gummer at oceaninformatics.com Date: Wed, 3 Oct 2012 10:09:50 +1000 To: openehr-technical at lists.openehr.org pablo pazos wrote: Hi Ian, Peter was right, the issue was because I've installed ADLWB v1.4.1.595 in my notebook. I downloaded the ADLWB

Issue (probably known) with ADL Workbench

2012-09-29 Thread Ian McNicoll
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

Issue (probably known) with ADL Workbench

2012-09-29 Thread Ian McNicoll
at hotmail.com To: openehr-clinical at lists.openehr.org Subject: RE: Issue (probably known) with ADL Workbench Date: Fri, 28 Sep 2012 11:43:48 -0300 CC: openehr-technical at lists.openehr.org Hi all, I've created an archetype with a DvDateTime node with a partial time constraint using

Issue (probably known) with ADL Workbench

2012-09-29 Thread Peter Gummer
Ian McNicoll wrote: Are you using the openEHR or Ocean version of the archetype editor? That would make no difference, Ian. The same ADL is generated by openEHR and Ocean Archetype Editors. I'm sure that the problem is that Pablo must be using a very old version of ADL Workbench. Peter

Issue (probably known) with ADL Workbench

2012-09-28 Thread pablo pazos
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

Issue (probably known) with ADL Workbench

2012-09-28 Thread pablo pazos
/ Twitter: http://twitter.com/ppazos From: ian.mcnic...@oceaninformatics.com 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

Issue (probably known) with ADL Workbench

2012-09-18 Thread Carlos Cavero Barca
] 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

Issue (probably known) with ADL Workbench

2012-09-18 Thread Ian McNicoll
: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

Issue (probably known) with ADL Workbench

2012-09-14 Thread Carlos Cavero Barca
[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

Issue (probably known) with ADL Workbench

2012-09-13 Thread Ian McNicoll
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