On 14/06/2013 10:09, Daniel Karlsson wrote:
>>
>> To write generic transformations is not trivial, I expect.
>> If possible at all.
> I do not agree. I believe this is what every implementer necessarily has
> to do, to provide a two-way transformation between a canonical form and
> any serialization and/or persistence form with a different set of
> requirements (query performance, OLTP vs. OLAP, space requirements,
> legacy systems integration, etc. etc. etc.). Not trivial but done on a
> regular basis.
>
>
Just to clarify to everyone (who may not be completely following
here)... there are 2 types of serialisations of data that can be done,
according to the following chains:
* canonical object RM form -> canonical XML form
o -> XML will be an instance of the standard openHER (/ other) XSD
o all such XML instances conform to the one schema, worldwide...
* canonical object RM form -> TDS XML form, known as TDD
o -> XML will be an instance of each TDS, where there is one TDS
for each Template
o all instances of a given TDS conform to that TDS, but of course
not to another TDS
o TDD -> canonical data transform is needed to put the data into
patient-centric longitudinal form, so that different data
streams from different places / applications (but often
containing the same logical data, e.g. vital signs) can be
aggregated and computed with
Both transforms have been implemented and in use for some years now. The
reverse transform (canonical data -> TDD) I don't think has ever been
implemented because currently it's not that useful.
It would become useful if we were to start to standardise on 'openEHR
messages', i.e. TDSs that would act as message standards. The advantage
of these over current message standards would be that a) the payload is
generated from single source models and b) the payload is separated from
the message envelope and control aspects of the infrastructure.
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/713ce15a/attachment.html>
