Hello,
It is two separate projects. The project I describe is a research and
education project performed by Erik Sundvall, Martin Eneling, Marie
Sandstr?m, Rong Chen, H?kan ?rman, Daniel Karlsson and myself at Department
of Biomedical Engineering at Link?ping University in Sweden. Erik will
probably send out some more information about the project soon.
Greetings,
Mikael
-----Original Message-----
From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Tomas
Sn?ckerstr?m
Sent: den 6 oktober 2010 17:03
To: For openEHR technical discussions
Subject: RE: openEHR and iPhone/iPad anyone?
No offence but I prefer not to top-post. Specially considering this
thread is moving a bit OT.
Please comment below.
ons 2010-10-06 klockan 11:24 +0200 skrev Mikael Nystr?m:
> Hello,
>
> It is correct that we in Link?ping currently work on an implementation of
> openEHR using the REST approach. The implementation will be open source
when
> the implementation is ready. (In fact Erik and Marie are currently
> discussing the latest commit to the project just outside my office door!)
I'm not familliar with what Mikael is involved in but I can tell that at
least the major integration project IFK2 is "heavily inspired" by the
REST philosophy.
The project adresses the possibility to integrate care documentation
applications (i.e. the journal) with quality-metrics systems. (In Sweden
there are several national wide registers dedicated to QA for certain
care processes)
For several reasons we developed a model where we separate the semantics
of the content from the model of the communication. Essentially we want
an interaction model that is dependent on the operations in the register
rather than the semantics of the domain objects.
Access is going to be governed via a SAML-ticket architecture against a
large user and service directory and services are accessed through a
MULE based service bus. The registers develop and publish changes to
their data requests on a regular basis. Hence it is nessecary to
decouple the services provided by the registers from the data requested
by the service.
For other reasons, we use a normal SOA architecture but, essentially
there are only operations defined for normal CRUD actions. One might
have the right to read but not write, create but not modify, et.c.
The semantics of the content is then packed to an (unpractically large)
CLOB wich is marshalled and validated on the end node.
This way, templates can be updated w/o the need to redefine the
services.
Project is being delivered for evaluation but there are some tecnical
conclusions being written for intended publication by the end of the
year.
Very REST, but a bit Off Topic in the dicussion on how I am to
professionally motivate my employer to purchase me an iPad... ;-)
Regards
Tomas
/.../
_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
