Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Diego Boscá
I have quite a few generated archetypes. Not clinically valid (or clinically validated at least) but they should be simple and varied enough to test. Or we could just try to generate a full cycle (I could open a CKM archetype, save it and give it back to you to test it). 2013/8/27 Thomas Beale

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
Hi Thomas, thanks for your attention. I experienced the problems with the Ocean Archetype Editor and The LinkEhr editor when used in the same work-environment, for example, which causes archetypes to be opened in both editors. It is not difficult to reproduce the errors and inconviences. The

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Peter Gummer
Bert Verhees bert.verhees at rosa.nl wrote: The issue is that both, Ocean and LinkEhr, do not recognize their responsibility and do not see a need to change this. Hi Bert, Glad you've brought this up again, but the problem won't get fixed unless you report it. Can you report the problem at

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread pablo pazos
-technical_lists.openehr.org/attachments/20130828/75c6767e/attachment.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 02:34 AM, Peter Gummer wrote: Bert Verhees bert.verhees at rosa.nl wrote: The issue is that both, Ocean and LinkEhr, do not recognize their responsibility and do not see a need to change this. Hi Bert, Glad you've brought this up again, Can you report the problem at

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Peter Gummer
Bert Verhees bert.verhees at rosa.nl wrote: Or leave it and do nothing with it, like this has been done for years now. The market maybe will correct you. Nothing has been done about it, Bert, because no one has ever logged it as an issue. If any one out there actually does care about this,

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 08:27 AM, Peter Gummer wrote: Bert Verhees bert.verhees at rosa.nl wrote: Or leave it and do nothing with it, like this has been done for years now. The market maybe will correct you. Nothing has been done about it, Bert, because no one has ever logged it as an issue. If

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 08:42 AM, Bert Verhees wrote: maybe even send a box of chocolates then. From Brussels, of course.

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Thomas Beale
Bert, all these tools are free, built and maintained by their originators at their own cost. So you might be sending yourself the chocolates... - thomas

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 08:54 AM, Thomas Beale wrote: Bert, all these tools are free, built and maintained by their originators at their own cost. So you might be sending yourself the chocolates... There ain't no such thing as a free lunch Bert

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread David Moner
://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/a5af394a/attachment.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 08:55 AM, Bert Verhees wrote: On 08/28/2013 08:54 AM, Thomas Beale wrote: Bert, all these tools are free, built and maintained by their originators at their own cost. So you might be sending yourself the chocolates... There ain't no such thing as a free lunch Some of the

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Thomas Beale
: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/52af4bf5/attachment-0001.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Peter Gummer
Bert Verhees bert.verhees at rosa.nl wrote: They could be grateful accept the help I offered until now and profit from it, they can also do nothing with it. It is their choice. I fully respect that. But saying that the tool isn't better because I (me, as a person) refuse to walk through

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread David Moner
-- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/c3a581e6/attachment.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Diego Boscá
2013/8/28 Bert Verhees bert.verhees at rosa.nl: On 08/28/2013 08:55 AM, Bert Verhees wrote: On 08/28/2013 08:54 AM, Thomas Beale wrote: Bert, all these tools are free, built and maintained by their originators at their own cost. So you might be sending yourself the chocolates... There

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 11:25 AM, Diego Bosc? wrote: BTW, I don't know how much does a university researcher gets paid in the Netherlands, but I can assure you that is not that well paid in Spain ;D It depends on your qualifications, but it must be enough so one can live from it. A dead researcher is of

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Bert Verhees
On 08/28/2013 10:33 AM, Peter Gummer wrote: Look forward to getting that problem report when you get a chance. It should only take you a couple of minutes I think you are right. I do it, next chance as I happen to work with it. Bert

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Thomas Beale
. What is to prevent that? - thomas -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/6610f406/attachment-0001.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread Gerard Freriks
... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/1595399d/attachment.html

openEHR-technical Digest, Vol 18, Issue 37

2013-08-28 Thread William Goossen
was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/1595399d/attachment-0001.html -- Subject: Digest Footer ___ openEHR-technical mailing list openEHR

openEHR-technical Digest, Vol 18, Issue 37

2013-08-28 Thread Sam Heard
part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/1595399d/attachment-0001.html -- Subject: Digest Footer ___ openEHR

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread pablo pazos
-technical_lists.openehr.org/attachments/20130828/b1f51ef3/attachment-0001.html

Polishing node identifier (at-codes) use cases.

2013-08-28 Thread pablo pazos
part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130828/a2999dd1/attachment-0001.html