I have code to build the archetypes from the internal source of
the R-MIM's rather than the schemas. I will be publishing
this through eclipse shortly.
I will be able to go the other way too, but both formats will
need modifications for gap coverage. I am presenting changes
to the RMIM diagrams to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Churches schreef:
> Bert Verhees wrote:
>> I stopped this work because there is a bug in the java-kernel concerning
>> Archetype-slots, which are really necessary for this job.
> ...
>> The code I wrote is however based on the 0.95 kernel. But it
Hi Tom
> The main difference architecturally is that there in openEHR there is a
> reference model from which software and systems can be built.
This is not a difference; it's true of HL7 as well
> Archetypes
> and templates simply designate legal configurations of instances of the
> referenc
Williamtfgoossen at cs.com wrote:
> In een bericht met de datum 14-9-2006 20:33:51 West-Europa
> (zomertijd), schrijft Thomas.Beale at OceanInformatics.biz:
>
>
>> Hi William,
>>
>> Since I am not 100% sure of the details of what you want to do, I won't
>> make any claims yet, but it seems to me t
Williamtfgoossen at cs.com wrote:
>
> Yes, it is currently not possible in the archetype editor to define
> the goal of an instrument, have a abstract of the evidence base in the
> clinical world underpinning it, work instructions, interpretation
> guidelines, references to the literature or web
f the result of resoning :-)
thanks again,
William
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060914/2a91336d/attachment.html>
Thanks,
William
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060914/611c5c76/attachment.html>
nts/20060914/1d2e3db0/attachment.mht>
>> al").
>
> well, I can't speak for "the designers" (I'm spending some time with him
> today on this subject ;-) , but archetypes and HL7 models are the
> same thing.
> I can interconvert between them. The only issues are syntactical
> differences
> in things that are allowed in each lang
>> al").
>>
>
> well, I can't speak for "the designers" (I'm spending some time with him
> today on this subject ;-), but archetypes and HL7 models are the same thing.
> I can interconvert between them. The only issues are syntactical differences
> in things that are allowed in each languag
Grahame Grieve wrote:
> Hi Tom
>
>
>> The main difference architecturally is that there in openEHR there is a
>> reference model from which software and systems can be built.
>>
>
> This is not a difference; it's true of HL7 as well
>
I think people would have a hard time finding it - w
Dear William,
Please note that some of the vocabulary mappings, and correspondence with the
main HL7 Act specialisations are provided in 13606 Part 3. I recognise this is
not the complete solution you seek, but it is a start.
(The Enquiry draft of Part 3 was recently circulated to CEN Working G
de for ADLv1.4 and java ADL parser is for 1.3.
Is there available ADL1.4 or ADL2.0 parser?
Any help will be appreciated.
rgds
minreddy
-
Get your email and more, right on the new Yahoo.com
-- next part --
An HTML attachmen
useful tool for any standard development once
Grahame Greave has done his tooling work.
William
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060914/7cce4589/attachment.html>
://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060914/ef6f94c6/attachment.html>
15 matches
Mail list logo
