Hi Heath, sorry for the delay, a new project came up :)
I'm available to discuss this offline and really want to help on this topic.
In the meantime, I've tested some stuff here, simplified my previous proposed
protocol to only one operation: commit(UID ehrId, ListVersion versions)
This
Hi Pablo,
I think we have an excellent opportunity here to take this offline with Erik
to work up a combined logical service specification and RESTful technical
service specification as a candidate for the openEHR service model.
It looks like you?re looking for a Virtual EHR Service. The
Hi Pablo,
You need to understand that some of the RM classes are functional object
rather than data objects and hence are not currently considered
serializable, VERSION_OBJECT, EHR and perhaps CONTRIBUTION are examples of
these. There is no specific statement about this in the specifications,
Hi Pablo,
You need to understand that some of the RM classes are functional object
rather than data objects and hence are not currently considered
serializable, VERSION_OBJECT, EHR and perhaps CONTRIBUTION are examples of
these. There is no specific statement about this in the specifications, and
Hi Erik,
I notice that you have provided a schema for VERSIONED_OBJECT which doesn?t
align with the RM class and overlaps with the X_VERSIONED_OBJECT already
defined in the extract.xsd. I think we should leave VERSIONED_OBJECT as not
serializable and use the X_VERSIONED_OBJECT class as the
Hi Heath, thanks for your comments, you mentioned really important issues.
From: heath.fran...@oceaninformatics.com
To: openehr-technical at lists.openehr.org
Subject: RE: Understanding how to commit contributions to an EHR Server with
XML
Date: Tue, 9 Oct 2012 10:41:12 +1030
Hi Pablo,You
On 06/10/2012 16:13, pablo pazos wrote:
Hi all,
I found there is no CONTRIBUTION XSD defined on the openEHR XDS, and
if it exists, I can't commit CONTRIBUTIONs using only one XML message,
because CONTRIBUTION references (using OBJECT_REF) the VERSIONs I need
to commit, but each VERSION
On Mon, Oct 8, 2012 at 9:50 AM, Thomas Beale
thomas.beale at oceaninformatics.com wrote:
to enable this, a small piece of extra XSD would be needed, to define a
contribution as a single XML artefact. This doesn't currently exist,
Except as an experiment at:
On 08/10/2012 09:02, Erik Sundvall wrote:
On Mon, Oct 8, 2012 at 9:50 AM, Thomas Beale
thomas.beale at oceaninformatics.com
mailto:thomas.beale at oceaninformatics.com wrote:
to enable this, a small piece of extra XSD would be needed, to
define a contribution as a single XML
Hi!
A CONTRIBUTION points to the IDs of it's contained VERSIONED_OBJECTs and
the VERSIONED_OBJECTs at the same time points to their
related CONTRIBUTION, thus it is probably easiest to finalize them in the
same transaction in most systems if they are stored/retrieved as separate
objects. (You
Hi all,
I found there is no CONTRIBUTION XSD defined on the openEHR XDS, and if it
exists, I can't commit CONTRIBUTIONs using only one XML message, because
CONTRIBUTION references (using OBJECT_REF) the VERSIONs I need to commit, but
each VERSION also references (by OBJECT_REF) the container
Hi all,
I'm studying the change_control package to create a simple example of data
commit to an EHR Server (to be used in a future course). I'm also reading the
service examples published on the wiki (Ocean Marand EHR Services).
As I understand it, when an EMR app (local) wants to commit data
12 matches
Mail list logo
