How many in this community, in the past, were on this mailing-list for
their school or university.?
For me, I don't care, homework or other work. We are all learning and
work in the school of life.
See the very interesting discussion he/she initiated.
On 28-08-15 07:54, Seref Arikan wrote:
Sorry, but I have to ask: are you doing a homework?
This sounds like an accusation (the Sorry, I have to ask-part). Then I
don't understand the point.
How many in this community, in the past, were on this mailing-list for
their school or university.?
On 27-08-15 19:54, Thomas Beale wrote:
I would suggest that CIMI has been simiplified to the point of not
being directly usable as an RM by openEHR or 13606 - most of the
needed context information is gone in CIMI, and it doesn't distinguish
any kind of 'Entry' or clinical statement.
Are you
If no one else is volunteering, I can do it over a month or so. I am
really quite busy and under time-pressure at this moment
Bert
On 28-08-15 13:00, Ian McNicoll wrote:
Edwin has been around here for a while.
I think the suggestion of creating a wiki page based on this
discussion (and
Edwin has been around here for a while.
I think the suggestion of creating a wiki page based on this discussion
(and updating Erik's StackOverflow page) is worthwhile. It is question that
is commonly asked and a single summary would be helpful.
Any volunteers?
Ian
Dr Ian McNicoll
mobile +44
Hi Bert,
On 28/08/2015 16:32, Bert Verhees wrote:
On 27-08-15 19:54, Thomas Beale wrote:
I would suggest that CIMI has been simiplified to the point of not
being directly usable as an RM by openEHR or 13606 - most of the
needed context information is gone in CIMI, and it doesn't
distinguish
I agree it is a balancing act in how far the semantics should be in the
RM or in the archetypes.
Both ways have their pro and contra.
Thanks for explaining it
Bert
On 28-08-15 19:17, Thomas Beale wrote:
Hi Bert,
On 28/08/2015 16:32, Bert Verhees wrote:
On 27-08-15 19:54, Thomas Beale
On 26/08/2015 13:08, Bert Verhees wrote:
On 26-08-15 14:03, Diego Boscá wrote:
I agree with most of the points, but I'm curious why you say that 13606
does not support AQL (and in any case wouldn't be AQL does not support
13606?)
Yes, that is a good question, I did not know that AQL was
On 26/08/2015 16:46, Erik Sundvall wrote:
Hi!
Where can one find proposals/diagrams describing the refreshed RM
(reference model) in the new 13606 revision? Will 13606 keep using the
old data types or harmonize more with CIMI or OpenEHR?
Is there now consensus/majority regarding using
openEHR has an EHR Extract specification
http://www.openehr.org/releases/RM/latest/ehr_extract.htmlas well,
which is more flexible than the 13606 one e.g. it can include
information from more than one patient, and accommodates both openEHR
and non-openEHR content.
- thomas
On 26/08/2015
Sorry, but I have to ask: are you doing a homework?
On Friday, 28 August 2015, 王海生 edwin_ue...@163.com wrote:
could we just add a page on openEHR website to illustrate these points
thx
--
王海生
15901958021
在 2015-08-28 01:54:58，Thomas Beale thomas.be...@oceaninformatics.com
On 28/08/2015 10:03, 王海生 wrote:
could we just add a page on openEHR website to illustrate these points
thx
if you search on the wiki
https://openehr.atlassian.net/wiki/dosearchsite.action?queryString=13606,
with either '13606' or 'CIMI' you will find a lot of material.
- thomas
Like the Ocean Archetype editor. It only supports the OpenEhr RM only. That
is understandable and no problem. The market will fill in that gap.
Op 27 aug. 2015 01:49 schreef Heath Frankel
heath.fran...@oceaninformatics.com:
Technical, the original grammar for AQL was bound to openEHR RM
Presumably the outline syntax, SELECT, CONTAINS etc is generalisable?
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Director, freshEHR Clinical
All of it is very, very generalizable :)
On Thu, Aug 27, 2015 at 9:43 AM, Ian McNicoll i...@freshehr.com wrote:
Presumably the outline syntax, SELECT, CONTAINS etc is generalisable?
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email:
By the way feel free to add some of the
onsdag 26 augusti 2015 skrev Erik Sundvall erik.sundv...@liu.se:
Hi!
Where can one find proposals/diagrams describing the refreshed RM
(reference model) in the new 13606 revision? Will 13606 keep using the
old data types or harmonize more with CIMI or
Hi!
Where can one find proposals/diagrams describing the refreshed RM
(reference model) in the new 13606 revision? Will 13606 keep using the
old data types or harmonize more with CIMI or OpenEHR?
Is there now consensus/majority regarding using ADL/AOM 2.0 for 13606? If
so, great!
When it comes
Oh, that got sent too early, sorry. I meant to say:
Feel free to add some of these descriptions to the stack overflow question:
http://stackoverflow.com/questions/32010122/are-the-hl7-fhir-hl7-cda-cimi-openehr-and-iso13606-approaches-aiming-to-solve
Two people thought the question was bad enough
On 26-08-15 16:33, Kalra, Dipak wrote:
The specification of archetypes is very mature, and during the
revision we expect to upgrade to the latest AOM (which is 2.0). This
part of the standard will also remain focused on a logical
representation supporting archetype interchange.
Thanks Dipak,
Hi,
I would say that the main difference is that 13606 is for data communication
and openEHR is for EHR architecture, both based on archerypes.
For detailed differences just look at both information models, you will see
that 13606 IM is much simple.
About the specs, 13606 has 5
Well, technically, it is not part of the openEHR scope either. Happy to be
corrected :)
On Wed, Aug 26, 2015 at 1:09 PM, Ian McNicoll i...@freshehr.com wrote:
Hi Diego,
I was not aware of any 13606 implementations that support AQL , although I
am sure there is some sort of path-based
Hi Bert,
I would leave it with: AQL is an archetype bound query language, and every
system which is build on archetypes is able to implement AQL.
That is fair enough but we were asked to characterise the differences
between 13606 and openEHR and I am comfortable that the actual and formal
Hi Diego,
I was not aware of any 13606 implementations that support AQL , although I
am sure there is some sort of path-based querying. AFAIK AQL is not part of
the 13606 scope.
Happy to be corrected.
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
On 26-08-15 14:03, Diego Boscá wrote:
I agree with most of the points, but I'm curious why you say that 13606
does not support AQL (and in any case wouldn't be AQL does not support
13606?)
Yes, that is a good question, I did not know that AQL was considered to
be OpenEHR specific.
In my opinion
On 26-08-15 14:23, Ian McNicoll wrote:
but am not aware of any non-openEHR
implementations
Is there a Xhosa implementation of 13606 or OpenEHR?
Does that mean OpenEHR or 13606 are not able to support Xhosa?
I would leave it with: AQL is an archetype bound query language, and
every system
See my earlier response. I think that is probably as official as you can
expect for now!!
13606 and openEHR share some aspects of their design, there are many formal
and informal links between the two communities e.g. Thomas Berale and I are
both invited experts to the 13606 group, and there are
On 26-08-15 14:44, Ian McNicoll wrote:
That is fair enough but we were asked to characterise the differences
between 13606 and openEHR and I am comfortable that the actual and formal
adoption of AQL is one of those differences.
If you see it from the formal point of specifications, you are
Dear Pablo,
According to the scope statement: the 13606 is for the creation of the
EHR-EXtract for communication between IT-systems
and
for the definition of the Information Viewpoint in Interfaces with system
services.
Gerard
Gerard Freriks
+31 620347088
gf...@luna.nl mailto:gf...@luna.nl
I agree with most of the points, but I'm curious why you say that 13606
does not support AQL (and in any case wouldn't be AQL does not support
13606?)
2015-08-26 12:32 GMT+02:00 Ian McNicoll i...@freshehr.com:
This might help a little
It is definitely on the openEHR Specifications Roadmap. That was a clear
decision at the Oslo meeting a year ago. There are at least 3
implementations that I know of and more back-end vendors are intending to
implement but I know what you mean 'technically';)
I agree that AQL is RM agnostic but
I'd agree with Ian here.
While both could possibly support AQL, the difference I see is in
intent, scope and actual implementation.
As Gerard says, 13606's main aim is to communicate between IT-systems
and for this, AQL may not be quite as fundamental as it is to openEHR.
Sebastian
On
Dear Gerard, IMO communication includes the interfaces, I didn't excluded
them :D
--
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com
Subject: Re: difference and relationship between openEHR and EN13606
From: gf...@luna.nl
Date: Wed, 26 Aug 2015 14:03:18 +0200
To: openehr-technical
Dear All,
This is an interesting discussion, and I would like to stress the
complementarity of the two.
openEHR is, as others have said, an important consolidator of the
state-of-the-art in best practices for the design of an electronic health
record architecture, repositories and the
On 26-08-15 14:57, Sebastian Garde wrote:
AQL may not be quite as fundamental as it is to openEHR.
How about filtering messages?
Messaging is a process, in the cloud it will become very important, it
will become more then two system interchanging information.
It doesn't matter were your
Maybe this would help:
http://search.informit.com.au/documentSummary;dn=950616334398351;res=IELHEA
On Wed, Aug 26, 2015 at 10:14 AM, 王海生 edwin_ue...@163.com wrote:
dear all ,
how could i explain to someone difference and relationship between
openEHR and EN13606
thx
--
王海生
This might help a little
http://www.slideshare.net/atalagk/implementation-and-use-of-iso-en-13606-and-openehr
Similarities:
Both use archetypes and ADL and two-level information modelling.
Both share the EHR, FOLDERS,COMPOSITIONS, ENTRY, ELEMENT classes.
Some archetype tools can work with both
Hi,
I must repeat the scope of 13606 verbatim once more.
It is NOT only for messaging but also for Interfaces
Gerard Freriks
+31 620347088
gf...@luna.nl mailto:gf...@luna.nl
Scope
This standard is for the communication of part or all of the electronic health
record (EHR) of a single
Hi Gerard,
Agreed - I was using messaging loosely - 'interfacing between systems' is
better.
Ian
Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Technical, the original grammar for AQL was bound to openEHR RM classes,
composition, version, observation, etc. theoretically it could be generalised
to be a RM agnostic and should be the goal of the current AQL specification
work if it hasn't already been done in the antlr grammar.
Regards
Hi,
Next week we will meet in Brussels and discuss the proposals, discussion papers
by the various working parties.
I think that the RM and data types will be simplified.
leaving semantics to be dealt with at the archetype level using standardised
archetype patterns.
(participations,
Thanks Dipak,
A very clear and helpful statement of current and future intent. I too
agree that we should not focus negatively on the differences and that they
are mutually reinforcing but people do ask and it's important that we are
clear that while 13606 and openEHR share a number of tools,
Dear Ian,
Thanks also for your helpful reflections. I agree that once the standard is
close to final we should perform and publish a detailed comparison and cross
mapping between the reference models, as an aid to system implementers and tool
makers.
With best wishes,
Dipak Kalra
On 26 Aug
We are in agreement, then. :-)
Gerard Freriks
+31 620347088
gf...@luna.nl mailto:gf...@luna.nl
On 26 aug. 2015, at 17:06, Ian McNicoll i...@freshehr.com wrote:
Hi Gerard,
Agreed - I was using messaging loosely - 'interfacing between systems' is
better.
Ian
Dr Ian McNicoll
Gutiérrez
http://cabolabs.com http://cabolabs.com/es/home http://twitter.com/ppazos
Subject: Re: difference and relationship between openEHR and EN13606
From: gf...@luna.nl mailto:gf...@luna.nl
Date: Wed, 26 Aug 2015 14:03:18 +0200
To: openehr-technical@lists.openehr.org
mailto:openehr-technical
44 matches
Mail list logo
