enehr-technical_lists.openehr.org
___
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/c0e3ea26/attachment-0001.html>
---
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/e9787307/attachment.html>
chment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/8c9d4f5b/attachment.html>
7;s an overlap. But that's a separate (and important) issue. I was
> asking about the possibility of having more compact serialization
> formats.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/a9baa6e5/attachment.html>
On 14/06/2013 10:38, Ian McNicoll wrote:
> Hi Daniel,
>
> I should have been more precise. I still don't see how it would be
> possible to create a single generic Canonical XML -> TDD transform.
actually it would not even be all that hard. It is just a case of doing
a data-level transform that c
our system.
--
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/208608ee/attachment-0001.html>
Gerard, Ian, Thomas, thanks for all answers.
On Fri, 2013-06-14 at 11:17 +0100, Thomas Beale wrote:
>
> Let me clarify a few things here.
>
> There are many possible TDSs that can be generated from a given
> template. Some users want a 'flat schema' with minimal meta-data,
> which makes working
Well, in ADL specialization allows extension
>From here
>(http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633#openEHRADL&AOM1.5-SpecialisationSemantics)
"extensions, i.e. object constraints added to a container attribute
with respect to the corresponding attribute in the parent archet
ult target.
The question is: How much information is lost as a result of the transformation
of a Template to an XML derivative?
But again: I think all this implementation stuff is outside the scope of CIMI.
>
> - thomas
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/4b193f3d/attachment.html>
Hi Gerard,
see below...
On Fri, 2013-06-14 at 11:54 +0200, Gerard Freriks wrote:
>
> See below
> Gerard Freriks
> +31 620347088
> gfrer at luna.nl
>
> On 14 jun. 2013, at 11:09, Daniel Karlsson
> wrote:
>
> > On Fri, 2013-06-14 at 09:56 +0200, Gerard Freriks wrote:
> > > Hi,
> > >
> > >
> >
On 14/06/2013 12:19, Diego Bosc? wrote:
> Well, in ADL specialization allows extension
>
> >From here
> >(http://www.openehr.org/wiki/pages/viewpage.action?pageId=196633#openEHRADL&AOM1.5-SpecialisationSemantics)
> "extensions, i.e. object constraints added to a container attribute
> with respect
On 14/06/2013 12:31, Daniel Karlsson wrote:
> Gerard, Ian, Thomas, thanks for all answers.
>
> On Fri, 2013-06-14 at 11:17 +0100, Thomas Beale wrote:
>>
> Such a standard TDS/TDD would have made the Swedish 2009-10 quality
> registry project significantly easier and a lot of the criticism towards
>
HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/cf40f626/attachment.html>
string processing (I'm not sure if that is what you are
implying with things like
"ENTRY:Observation:ClinicalFinding:BodyTemperature" above).
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/02143ac8/attachment.html>
> transformation problematic? Could anything be changed to make the
>>> transformation possible?
>>
>>
>> ___
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/ccc304ad/attachment-0001.html>
next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/713ce15a/attachment.html>
ven that clear on what the need would be, but (see my other
post), it would be nearly trivial, assuming that a reasonable TDS was
designated as the default target.
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/4658baa5/attachment.html>
Foundation www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/e513d0c7/attachment-0001.html>
al at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
Ocean Informatics <http://www.oceaninformatics.com/>*Thomas Beale
Chief Technology Officer*
+44 7792 403 613Specification Program, /open/EHR
<http://www
On Fri, 2013-06-14 at 09:56 +0200, Gerard Freriks wrote:
> Hi,
>
>
> While we are at it.
>
>
> -1-
> Why do we need a TDD?
> Isn't a Template just a Composition archetype with Sections archetypes
> and ENTRY archetypes and Cluster archetypes and Element archetypes
> plus data types.
With ADL 1.
___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/c4c77563/attachment.html>
tion possible?
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130614/ddeb7b6f/attachment.html>
Hi Ian,
On Thu, 2013-05-30 at 10:34 +0100, Ian McNicoll wrote:
> Hi Erik,
>
>
> The Ocean TDD->canonical transform is available at
>
>
> http://openehr.codeplex.com/SourceControl/latest#176376
>
>
>
> look for TDD_to_openEHR.xsl
>
>
> As far as I know a generic reverse transform is not po
23 matches
Mail list logo
