I cannot compliment the team enough for the wonderful work that has been
done, so again, good job, very promising.
Bert
On 21-08-15 17:37, Thomas Beale wrote:
I am finalising the ADL/AOM2 specifications, mainly updating text, and
incorporating content from older separate documents. It's not
Thanks Thomas, for the clarification. Very useful.
Bert
Op 13 aug. 2015 06:26 schreef Thomas Beale
thomas.be...@oceaninformatics.com:
Dave,
I'll try to answer a few.
Firstly, please treat the active specifications as what you find by going
to the home page 'Specifications' button (top
-syntax-files.
Seeing at what you have, it is already very useful, with string-colors,
and that kind of basic things. In good open source tradition, call it
version 0.0.1, meaning: it is a good start, also invitation to do
something with it.
Bert
- thomas
On 24/06/2015 17:49, Bert Verhees wrote
Very good Thomas, I often use vim for quick repair in terminal, I hope you
get it distributed with vim, as some other programming languages, like C,
are supported default.
Regards
Bert
Op 23 jun. 2015 18:46 schreef Thomas Beale
thomas.be...@oceaninformatics.com:
I have uploaded new vim syntax
Very nice, Pablo, thanks for sharing
Bert
On 29-05-15 01:46, pablo pazos wrote:
Dear friends,
I'm happy to share with you that our openEHR EHRServer is on the
cloud: http://cabolabs-ehrserver.rhcloud.com/ehr-0.1/
This is a pre-beta version, with no security. Anyone can play with it.
Some
On 15-04-15 23:11, Thomas Beale wrote:
On 15/04/2015 17:28, Bert Verhees wrote:
On 15-04-15 17:19, Dmitry Baranov wrote:
Sorry Bert ) I had to explain that Oracle 11 is a business
requirement, not a hardware limitation.
Just do it, and then it should run fine, although you have to
change
On 16-04-15 09:06, Dmitry Baranov wrote:
Hi Bert,
I give up. The problem appears in 12c as well.
And people agree that it is an Oracle bug.
https://community.oracle.com/message/13008017
You should always follow the standard in your analyses, before you
declare one product buggy and another
On 16-04-15 09:29, Thomas Beale wrote:
e still need some kind of schema for XML docs/ messages, but I would
not even think of making any persistence be based on XML, especially
not XML schema. Probably Relax NG would have been the better one for
messages etc.
Keep XML at the boundaries,
On 16-04-15 10:42, Dmitry Baranov wrote:
I regret that I cannot post the XML Schema and XML-instances I use, because
they are not of my IP. But they are structured in another way, more
dedicated to efficiency.
XML schema is intellectual property, I agree, but why might you or somebody
else
On 16-04-15 11:13, Thomas Beale wrote:
Indeed, it would be a great thing. The reason it doesn't exist so far,
is that to be useful we need synthesised data sets that have some
realistic statistical spread of values. Since we are talking at
multiple levels - not just vital signs
On 15-04-15 15:47, Dmitry Baranov wrote:
Hi everyone,
According Bert experience
(https://www.linkedin.com/groups/Choice-OpenEHR-persistence-layer-144276.S.208531138),
one must not try to adopt OpenEHR model to relational storage since almost
all popular database engines able to process
On 15-04-15 17:19, Dmitry Baranov wrote:
Sorry Bert ) I had to explain that Oracle 11 is a business requirement, not a
hardware limitation.
Just do it, and then it should run fine, although you have to change the
XML-Schemas (a bit) before registering them to Oracle. I already
explained to
Hi,
I wonder what a use-case might be for the ordered keyword in
CMultiAttribute.
It complicates software, and seems useless because elements in a list
can be queried/sorted in any order in the result, as well be queried as
a single element.
Shouldn't it therefore not be in the AOM, but be
Although the the stock market-information is a data-object, it is
generated by a service, and because Rest is (mis)used to communicate
with services the service must be seen as the addressed resource.
If the service is out of order, or the address to the service is
misspelled a 404 would be in
Op maandag 19 januari 2015 heeft Peter Gummer
peter.gummer at oceaninformatics.com het volgende geschreven:
Bert Verhees wrote:
The point for me is separation of transport layer and application
layer, and each domain has its own errorhandling.
Hi Bert,
HTTP is not a transport layer
you ever been sick? No? That is a 404 error.
But on the other hand, that is how the big guys do it.
Bert
Op maandag 19 januari 2015 heeft Bert Verhees bert.verhees at rosa.nl het
volgende geschreven:
Ok, you are right, but http is a very generic application layer, not to
designed to serve
I just had some extra information.
A query with no result would have status 200, for example,
/parties/John+Doe.
When an identified resource is queried, and there is no result, than the
404 will be applicable, for example /party/123456
Op maandag 19 januari 2015 heeft Bert Verhees bert.verhees
Verhees escribi?:
I checked on how the large companies like Google, Amazon, PayPal,
github do it.
They all have a hybrid solution. They all use an own error schema was
verbal terms, sometimes hierarchical, and they all map their errors
to the http numerical status schema.
This means
On 19-01-15 12:06, Gerard Freriks (priv?) wrote:
Niet een slecht advies: Kijken bij FHIR van HL7
I will check that
GF
Gerard Freriks
+31 620347088
gfrer at luna.nl mailto:gfrer at luna.nl
On 19 jan. 2015, at 11:29, Diego Bosc? yampeku at gmail.com
mailto:yampeku at gmail.com wrote:
On 19-01-15 11:31, Birger Haarbrandt wrote:
The medrecord openEHR server is also based on REST and worth looking
at. There was a lot to learn from for me as the API is pretty neat.
I will check that too, thanks for the links
Bert
-- next part --
An HTML attachment was
Thanks Ralph
;-)
On 19-01-15 13:10, Ralph van Etten wrote:
Hi,
On 01/19/2015 11:31 AM, Birger Haarbrandt wrote:
The medrecord openEHR server is also based on REST and worth looking at.
There was a lot to learn from for me as the API is pretty neat.
Thanks. We do our best to make the
--
*From: *Bert Verhees
*Date: *Sat, Jan 17, 2015 8:35 PM
*To: *openehr-technical at lists.openehr.org
javascript:_e(%7B%7D,'cvml','openehr-technical at lists.openehr.org');;
*Subject:*Re: CRUD Restlet
.
There are good reasons for trying to reuse a few standardized status codes
in HTTP if you
https://developers.google.com/drive/web/handle-errors
This is exactly my point, 404 is for handling errors, someone not being
in a hospital-register is not an error. To check if someone is, and he
isn't, that is not necessarily an error.
It may even be a good thing, that someone never has
, I have posted this question to several forums
because I think this is important, and maybe I find support for my way
of thinking.
Bert
El 18/1/2015 11:21, Bert Verhees bert.verhees at rosa.nl
mailto:bert.verhees at rosa.nl escribi?:
https://developers.google.com/drive/web/handle
On 18-01-15 11:49, Erik Sundvall wrote:
Why do you see the status 404 as an evil error status but 200 as some
totally other kind of status?
Restlet has implemented 404 as an evil error: it means: if it cannot
route your URL, it returns 404.
So a client application has no useful information
For information:
See therecommendations by Ethan Cerami: Specialties: Cancer genomics,
bioinformatics, scientific computing, software engineering, project
management.
https://www.linkedin.com/in/ecerami
http://www.oreilly.com/pub/au/806
Read:
:)
Sent from my LG Mobile
-- Original message--
*From: *Bert Verhees
*Date: *Sun, Jan 18, 2015 9:46 AM
*To: *openehr-technical at lists.openehr.org
mailto:openehr-technical at lists.openehr.org;
*Subject:*Re: CRUD Restlet
For information:
See therecommendations by Ethan
-- Original message--
*From: *Bert Verhees
*Date: *Sun, Jan 18, 2015 9:46 AM
*To: *openehr-technical at lists.openehr.org;
*Subject:*Re: CRUD Restlet
For information:
See the recommendations by Ethan Cerami: Specialties: Cancer genomics,
bioinformatics, scientific computing, software
.
Sent from my LG Mobile
-- Original message--
*From: *Bert Verhees
*Date: *Fri, Jan 16, 2015 8:18 PM
*To: *For openEHR technical discussions;
*Subject:*CRUD Restlet
I was looking at EHRScape, I should have posted this question
On 17-01-15 12:00, Diego Bosc? wrote:
Probably 405 'method not allowed' or just return a generic 400 'bad
request'. In either case you know it is your client fault.
Wikipedia is a good start for most common codes. You can see you can
cover a lot of use cases just with the codes on that page.
On 17-01-15 11:56, Karsten Hilbert wrote:
What would be the error code for when the client attempts to
call a non-existing service on the server ?
Sorry that I come back to this once more. Karsten almost gave a good
example, I want to explain my cause on a better but similar example.
The same
.
As far as I know, there are already few openEHR-REST-apis out there,
all behaving in a similar if not identical way in what regards
returned status codes.
Sebastian
On 1/17/2015 6:20 PM, Bert Verhees wrote:
On 17-01-15 11:56, Karsten Hilbert wrote:
What would be the error code for when
.
There are good reasons for trying to reuse a few standardized status
codes in HTTP if you can (see Fieldings dissertation etc.) but the
codes are extensible if you really need to invent your own status code.
That is true, but Restlet already uses 404 for a method not found, or
an URL
already running again, stupid networks
Depending on how your XML is constructed, it is very easy to convert AQL to
XQuery, or ADL-path to XPath.
Bert
Op dinsdag 16 december 2014 heeft pablo pazos pazospablo at hotmail.com het
volgende geschreven:
Just curious :)
I'm adding version control features to EHRServer (
On 31-10-14 09:21, Thomas Beale wrote:
I know, that's why I asked if it is feasible to incorporate this or
at least something similar in the transitional 1.4+ since it seems a
very important characteristic.
yes, undoubtedly. I will start a wiki page to try and tease out
changes to
On 31-10-14 10:32, Gerard Freriks wrote:
Use case: to define an ?ad-hoc? list of codes that might apply and
from which one can be choosen without the need to use the terminology
service?
Exactly, many times there are only a few codes needed in an
archetype/dataset and the need to have a
On 25-10-14 13:58, Thomas Beale wrote:
On 24/10/2014 19:17, Bert Verhees wrote:
OpenEHR is not a standard, it is a formal specification.
http://www.iso.org/iso/home/standards.htm
ISO, What is a standard:
A standard is a document that provides requirements, specifications,
guidelines
of the board on the website, I think.
You can email them and ask. I hope you tell us what they tell you. Maybe it
is just money. There ain't no such thing as a free lunch.
Good luck
Bert Verhees.
Pablo Pazos
www.CaboLabs.com
-- Original message--
*From: *Bert Verhees
*Date: *Fri, Oct 24
standard because that definition fits what openEHR is.
Anyway, we are not discussing definitions but a much broader subject:
the board being silent in front on community efforts that need them.
Pablo Pazos
www.CaboLabs.com
-- Original message--
*From: *Bert Verhees
*Date: *Fri
On 25-10-14 02:54, Shinji KOBAYASHI wrote:
To Bert,
Thank you for proof-reading. English is too difficult for me,
Japanese. My understanding is openEHR specs are oriented to base of
the standards. Could you let me know the better phrase?
Only strong men can admit their weaknesses. So this is a
On 25-10-14 05:21, pablo pazos wrote:
Bottom line, I just see a gap between the foundation and the
community, and that gap gets bigger because of language and
geografical differences. That's why I created the openEHR course in
spanish and the ES community. My proposal is just a help me
On 25-10-14 13:58, Thomas Beale wrote:
On 24/10/2014 19:17, Bert Verhees wrote:
OpenEHR is not a standard, it is a formal specification.
http://www.iso.org/iso/home/standards.htm
ISO, What is a standard:
A standard is a document that provides requirements, specifications,
guidelines
On 07-10-14 22:57, Seref Arikan wrote:
Knuth, Donald E. Structured Programming with go to Statements. /ACM
Computing Surveys (CSUR)/ 6.4 (1974): 261-301.
Did you see the date?
Programming has changed a bit since then
-- next part --
An HTML attachment was scrubbed...
On 03-10-14 18:36, Thomas Beale wrote:
On 03/10/2014 16:40, Ian McNicoll wrote:
When this published v1 archetype needs to go back into review it gets
labelled as
org.openehr::openEHR-EHR-OBSERVATION.lab_test.v1.0.1-unstable+build.e34dgtj67856
or using the uid -
%2Egmp_144276
Best regards
Bert Verhees
On 01-10-14 17:02, Bakke, Silje Ljosland wrote:
Hi everyone,
In light of the recent re-licensing of FHIR
http://www.healthintersections.com.au/?p=2248 using the Creative
Commons CC0 Public Domain Dedication as well as the discussion about
licensing
For information the link to the LinkedEhr discussion, I hope it works
Of course, this should be: LinkedIN ;-)
(sorry David)
Best regards
Bert Verhees
On 01-10-14 17:02, Bakke, Silje Ljosland wrote:
Hi everyone,
In light of the recent re-licensing of FHIR
http
It didn't work on Linux, though the opening screen was confusing. It
wouldn't work, it said, but still it invited to fill in my name. I did, and
it didn't work.
Just for fun, I looked at the supported platforms, first the 128 versions
of Windows, and in the end was Macintosh. I never heard about
On 17-09-14 01:25, Diego Bosc? wrote:
Not sure if this is referring to the same lync, but maybe it is worth trying
http://its.uiowa.edu/support/article/4049
http://uits.arizona.edu/uaconnect/lync/linux
I try to remember for the next time
2014-09-17 1:20 GMT+02:00 Bert Verhees bert.verhees
On 05-09-14 19:06, pablo pazos wrote:
Hi! Thanks for your answers.
It is a little tricky but from Thomas comments, I think that the
system is not a technical term, but is more related to an
organizational term. For example, if I use the same system / service
to hold EHRs from 2 different
On 16-05-14 03:55, pablo pazos wrote:
I mentioned the phases, several times, in my previous messages :)
Maybe Thomas can break that up into more phases.
On 16-05-14 09:16, Thomas Beale wrote:
I think Pablo has summarised some useful things:
* validate based on OPTs - this is a must; it's
On 16-05-14 12:54, Thomas Beale wrote:
OPT = Operational Template - it's the fully compiled version of a
template. See the Template Designer
http://www.openehr.org/downloads/modellingtools for this - it
generates them. Or else you can just do a fully flattened template in
the ADL 1.5
Thanks
I will study it
Bert
On 16-05-14 19:37, Thomas Beale wrote:
Interest in ADL AOM 1.5 is growing daily now.
In order to enable visitors new and old to more easily find the ADL
and AOM pages on the openEHR wiki, I have moved them to a new ADL
space
On 14-05-14 12:20, Timothy W. Cook wrote:
Precisely. This is why I said before that it is an implementation
level issue. Especially in openEHR or anywhere that you are using a
DSL and there are not a existing tools to choose from that have been
tested across thousands of use cases.
I
On 14-05-14 14:04, Timothy W. Cook wrote:
It is an illustration of how varied the approaches can be based on the
implementation situation.
I tried googling it, of course. I always try to find an answer by
myself, before discussing it on a mailinglist.
I got 6 million hits to the question you
Can someone please comment on this. Repairing may not be that hard
Thanks
Bert Verhees
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20140321/9cbb42a9/attachment.html
under attention.
Thanks for clarifying this.
Bert
On 02/19/2014 06:00 AM, Peter Gummer wrote:
Bert Verhees bert.verhees at rosa.nl wrote:
Maybe this discussion has been on this list before December 2012, I must
have missed it.
Hi Bert,
There was a long discussion 18 months earlier than
On 02/19/2014 10:34 AM, Ian McNicoll wrote:
The
preferred solution was namespacing use reverse-urls but you and others
argued for more definitive unique identification via OID/UIDs.
I agree
Bert
On 02/19/2014 10:34 AM, Ian McNicoll wrote:
The
preferred solution was namespacing use reverse-urls but you and others
argued for more definitive unique identification via OID/UIDs.
Ooops, send to quickly
I am not anymore so sure if it need to be UIDs. I think now, one year
later, that
On 02/18/2014 01:36 PM, Ian McNicoll wrote:
As I understand it, the idea of the ENTRY sub-classes was to remove
some of this variability in the top-level patterns and strike some
sort of balance between your two contradictory wishes.
I don't think so.
It is the wish, I know, of all working on
On 02/18/2014 03:52 PM, Sebastian Garde wrote:
On 18.02.2014 14:56, Bert Verhees wrote:
For example, in the OpenEHR, the idea was that CKM would serve the
world with archetypes, and there would be no need of a strong
archetypeId-system, because, all archetypes ever to be taken
seriously
Sorry I misunderstood you.
Bert
Op dinsdag 18 februari 2014 heeft Sebastian Garde
sebastian.garde at oceaninformatics.com het volgende geschreven:
On 18.02.2014 16:48, Bert Verhees wrote:
On 02/18/2014 03:52 PM, Sebastian Garde wrote:
On 18.02.2014 14:56, Bert Verhees wrote
I have read the PPT from Thomas which is linked in
http://www.openehr.org/wiki/display/CIMI/CIMI+Entry-in-Entry+Modelling+Pattern
I have some remarks on that. My two cents:
The proposal is written from the point of view of OpenEHR.
Although, I cannot comment on medical content, only from the
Ralph van Etten schreef op 6-2-2014 9:45:
At the moment only the functionality required for our use cases is
implemented. For instance, OpenEHR allows archetype slots with
wildcards. This is something we do not need for our usecases and
therefore we have not implemented it yet. There are many
of constraints.
Thanks
;)
Bert
2014-02-06 Bert Verhees bert.verhees at rosa.nl
mailto:bert.verhees at rosa.nl:
Diego Bosc? schreef op 6-2-2014 9:52:
Regarding consistency checks, we have been able to generate
schematron rules from the archetypes to check constraints stated
requirements?
Best regards
Bert Verhees
Ralph van Etten schreef op 5-2-2014 20:34:
On 02/04/14 17:33, Birger Haarbrandt wrote:
Hi Birger,
Erik's approach
was to develop a proprietary XML Schema to wrap compositions and
contained entries. Obviously, this might work in a native XML database
like
Hi Thomas, best wishes to you too, and all other readers.
ADL is a generic modeling language, one should not stick to the OpenEHR
RM while defining it.
it looks like a good idea to reflect the structure of an archetype in
the idCodes, like this:
definition[at]
list[at.1]
The dwarf sitting on the shoulder of a giant, moves forward faster, but
sees things the giant cannot see.
They cooperate.
http://upload.wikimedia.org/wikipedia/commons/4/4a/Library_of_Congress%2C_Rosenwald_4%2C_Bl._5r.jpg
On 11/28/2013 02:24 PM, Ingram, David wrote:
Dear Bert,
On behalf of
On 11/28/2013 02:43 PM, pablo pazos wrote:
One is, the most important, but not in our hands, make the AOM
important, create RM's above the AOM, use it for other purposes than
OpenEHR only. The more the AOM is used, the less developers will
complain about complexity.
IMO end system
On 11/22/2013 08:07 PM, Thomas Beale wrote:
I spent a bit of time trawling back through that last discussion on
C_OBJECT.node_id (the property that carries at-codes) and whether it
should be mandatory or optional, and also whether empty is valid.
Currently it is mandatory, and can't be
Reflections on Pablo and Leo, both recognizing the complexity of the RM
and looking for ways how to deal with it.
On 11/28/2013 04:30 AM, pablo pazos wrote:
Hi Leo,
I think simplifying openEHR is not a good strategy. The problem is
that most programmers are not implementing against openEHR
Op zondag 24 november 2013 schreef Colin Sutton (
Colin.Sutton at ctc.usyd.edu.au):
i.e. don't use indexes - especially where they contradict the meaning:
* How can you have two 'first' names?
* Family names come first in some asian languages.
Hi Colin, the discussion is about syntax, not
Thomas, thanks for your effort, it is very interesting, but now I am not
able to respond more to it. I'll come back to this in a few days.
Bert
Op vrijdag 22 november 2013 schreef Thomas Beale (
thomas.beale at oceaninformatics.com):
I spent a bit of time trawling back through that last
Op donderdag 21 november 2013 schreef Thomas Beale (
thomas.beale at oceaninformatics.com):
On 21/11/2013 18:35, Leo Simons wrote:
(: from all the items, take the first one, then take all the ones with
node id at0009 :)
/*[1][@archetype_node_id=at0009]
(: from all the items,
On 11/22/2013 10:44 AM, Thomas Beale wrote:
as ADL short hand for
cluster[@archetype_node_id='at0009']/items[@archetype_node_id='at0008',
@sibling_id='2']
I am not sure about this, sibling_id is the array-index, when I
understand. What happens in case a dataset changes, for example an
me thinking about it.
Thanks,
Bert
On 11/19/2013 10:23 PM, Thomas Beale wrote:
On 19/11/2013 20:08, Bert Verhees wrote:
Hi Alessandro,
I think you propose this?
/items[at0008,1]/value/value = Mark
/items[at0009,2]/value/value = Rutte
Either this or Bert's original (if it's legal Xpath
in a hurry.
Maybe not following xPath-like path-notation is a better idea?
I will reply later to the other mails regarding this
Thank you all very much
Bert
On 11/19/2013 10:23 PM, Thomas Beale wrote:
On 19/11/2013 20:08, Bert Verhees wrote:
Hi Alessandro,
I think you propose this?
/items
On 11/20/2013 09:53 AM, Diego Bosc? wrote:
/cluster[@archetype_id='openEHR-EHR-CLUSTER.bert.v1']/items[@archetype_node_id='at0008']/value[1]/value=Jan
/cluster[@archetype_id='openEHR-EHR-CLUSTER.bert.v1']/items[@archetype_node_id='at0008']/value[2]/value=Peter
, for
compatibility reasons.
Thanks for your helping, and if some one wants to discuss it further, I
am still open for that.
It would be a good thing if the OpenEHR community would reconsider the
ways paths are treated
regards
Bert Verhees
-- next part --
An HTML attachment
]/value/value = Peter
/items[at0009][1]/value/value = Balkenende
/items[at0008][1]/value/value = Jan
/items[at0008][2]/value/value = Peter
/items[at0009][3]/value/value = Balkenende
Or would another solution be better?
Thanks in advance for suggestions.
Kind regards
Bert Verhees
Hi Alessandro,
I think you propose this?
/items[at0008,1]/value/value = Mark
/items[at0009,2]/value/value = Rutte
regards
Bert Verhees
Alessandro Torrisi schreef op 19-11-2013 20:19:
i would say
/items[at0008,1]/value/value = Mark
/items[at0008,2]/value/value = Rutte
Alessandro
back to
this when more people can get involved (which will be fairly soon).
thanks
- thomas
On 26/09/2013 11:21, Bert Verhees wrote:
In my system it is not useful to preload archetypes, because,
archetypes are only parsed once in my system.
That is when they are saved in the system
Op 25-9-2013 22:47, Thomas Beale schreef:
On 25/09/2013 00:53, Bert Verhees wrote:
sure - if you have a separate property to store the archetype id, it
is empty in 95% of all object instances, and also you need a class
invariant to prevent it being filled at the same time
In my system it is not useful to preload archetypes, because,
archetypes are only parsed once in my system.
That is when they are saved in the system. They are parsed in order
to create a RNG/Schematron definition.
ok, so the downstream form of an archetype you are using is a
Op 24-9-2013 19:54, Thomas Beale schreef:
On 24/09/2013 00:10, Bert Verhees wrote:
For that reason I believe specifications should very carefully
specify things. I'll give a very simple example. The openEHR
specifications routinely specify which properties of a class are
mandatory
:
se.acode.openehr.parser.ParseException: Encountered / / at line
186, column 57.
Was expecting:
} ...
Thanks very much
Bert Verhees
On 09/23/2013 01:29 PM, Diego Bosc? wrote:
It should work, it is valid ADL
It works, I was using an older adl.jj, I updated it, and now it seems to
work.
Sorry for the trouble
Bert
2013/9/23 Bert Verhees bert.verhees at rosa.nl
mailto:bert.verhees at rosa.nl
I have a question about
Op 20-9-2013 17:01, Thomas Beale schreef:
it's simpler than you think - we made that property mandatory so that
programmers would never get a null exception.
Must have been along time ago, nowerdays, programmers have no problem
handling a null property.
I wonder what the idea behind stuffing
On 09/05/2013 09:38 AM, Diego Bosc? wrote:
II would say that you just have to attach the remaining path from
target node to the use_node path, so I would say first option is the
right one
That seems to me the most logical too.
Thanks, Diego!
Bert
2013/9/5 Bert Verhees bert.verhees
, if not overwritten by the
use_node, the nodeId in the targetpath.
Thank you very much
Bert
2013/9/5 Bert Verhees bert.verhees at rosa.nl mailto:bert.verhees at
rosa.nl
On 09/05/2013 09:38 AM, Diego Bosc? wrote:
II would say that you just have to attach the remaining path from
target node
LinkEHR writes an archetypenode id in a use_node, the Java ADL-parser
regards this as erroneous, although it is permitted in the AOM, where
there is an nodeId in the ArchetypeInternalRef constructor.
The repair in adl.jj was, however simply to do. I tested it with all
available testfiles, and
I have received a few archetypes created with the LinkEHR editor.
In there is a dateTime pattern like this:
time existence matches {1..1} matches {-??-??T??:??:??}
I wonder if it is a legal pattern according to the specifications. I
must say that it is an EN13606 archetype.
If it is legal,
On 09/02/2013 03:17 PM, Diego Bosc? wrote:
I think we changed this somewhere in the past. Now we only allow date
as -mm-dd or -??-?? and times as hh:mm:ss, hh:mm:?? or
hh:mm:XX (as we haven't been able to find use cases for the all
question marks dateTime).
Having said that,
Op 02-09-13 16:54, Thomas Beale schreef:
you might want to consider posting these issues on the Java list,
you'll probably get more answers there... not everyone bothers to read
all messages on this list if they are busy
Thanks Thomas, I forgot there was a Java-list. There hasn't been much
On 09/01/2013 02:54 AM, Peter Gummer wrote:
Bert Verhees bert.verhees at rosa.nl wrote:
The items in ontology are very limited, only text and description. I must
agree that this is not much, especially if you want the at-nodes being
explained by code systems.
But on the other hand
:
1. Re: openEHR-technical Digest, Vol 18, Issue 38 (Bert Verhees)
2. RE: Polishing node identifier (at-codes) use cases. (pablo pazos)
3. Re: Polishing node identifier (at-codes) use cases. (Thomas Beale)
4. Re: Polishing node identifier (at-codes) use cases. (Thomas Beale
the list at
openehr-technical-owner at lists.openehr.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of openEHR-technical digest...
Today's Topics:
1. Re: openEHR-technical Digest, Vol 18, Issue 50 (Bert Verhees
to) the archetypes.
Jan
On 29 aug. 2013, at 21:53, Bert Verhees bert.verhees at
rosa.nljavascript:;
wrote:
On 08/29/2013 09:00 PM, Talmon (CRISP) wrote:
Bert
Archetypes were conceived to support SEMANTIC INTEROPERABILITY. The
13606 is a communication standard, but of course you can also use
On 08/30/2013 12:26 AM, Thomas Beale wrote:
On 29/08/2013 20:53, Bert Verhees wrote:
I think, it has to also some connection with the idea of one world
wide archetype-repository. But we found out in discussion, this will
never happen. So now, in the new ADL-standard, 1.5
My two cents,
A nodeID only has to be unique inside an archetype, because an archetype
with a specific archetypeId is considered unique.
The path to a data-item contains the nodeId and the archetypeID, and
together they form a unique combinations. (most of the cases the paths
contains more
401 - 500 of 842 matches
Mail list logo
