XML versions of the ADL

Greg and others, We have configured an auto-build process to convert the ADL archetypes to XML located at http://svn.openehr.org/knowledge/archetypes/dev. They now all exist and are valid against the RM 101 XML Schema. Let me know if you find any issues with the XML content. Regards Heath > --

Exchanging codified content via HL7

Greg, Very interesting question, there is actually working being done within Standards Australia to determine how to represent archetyped content in HL7 V2. This work is not yet complete, but your suggestion is one of the options except the [at] is not required as all archetype root nodes have

OpenEHR queries

An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/310ec56b/attachment.html>

Antw: Re: {Disarmed} Antw: Call For Participation in HIT Definitions Work Gro...

URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/4e466890/attachment.html>

{Disarmed} Antw: Call For Participation in HIT Definitions Work Groups

I agree with that concern. I will be even more concerned if the definitions are different - particularly the use of EMR. But what's one more? Ed Hammond Williamtfgoossen@

{Disarmed} Antw: Call For Participation in HIT Definitions Work Groups

v. De Stinse 15 3823 VM Amersfoort email: Results4Care at cs.com phone + 31654614458 fax +3133 2570169 Dutch Chamber of Commerce number: 32121206 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/505d1a83/attachment.html>

Call For Participation in HIT Definitions Work Groups

--- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/d542c0ee/attachment.html>

XML versions of the ADL

Greg, I agree with Tim, that you can't always expect Ocean to provide these tools. We just happen to be one of the main contributors to the openEHR foundation. As Tim said, the openEHR specs are the normative artefacts including the XML schemas provided at http://svn.openehr.org/specification/TAGS/

OpenEHR queries

An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/2e87aff0/attachment.html>

Dr LONJON France XML versions of the ADL

Hello heath In the examples you show, " located at http://svn.openehr.org/knowledge/archetypes/dev. " there is a french version pending and write? This is that there are people interested in doing the job? best regard's Dr R LONJON Clermont Fd - France Selon Heath Frankel : > Greg and othe

OpenEHR queries

An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/551ff23a/attachment.html>

OpenEHR queries

bility using db4o. > > // Erik > ___ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > ------ next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/c864b312/attachment.html>

OpenEHR queries

On 11/7/07, Randolph Neall wrote: > Can I assume that what Thomas here advocates, ("relational databases can be > used very effectively as a low-level store of blobs keyed by path") is what > how the ocean persistence layer actually works? Beyond this, Thomas > apparently has little use for the ca

OpenEHR queries

ling list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

XML versions of the ADL

An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071107/d99595a5/attachment.html>

XML versions of the ADL

Looks good to me, The only issues I am hitting so far are due to the original ADL e.g. openEHR-EHR-OBSERVATION.dimensions.v1.adl defines at0013 (Object: The object, axis or body part that is being measured) as a DV_CODED_TEXT but without associated codes. I don't know if it is helpful if I high

Exchanging codified content via HL7

So I have completed a first pass at parsing the OpenEHR content, extracting some initial information I would import into to my application. More work to be done but if you look at this text file as a preliminary output from the process: http://www.patientos.org/forum_temp/openehr.txt My question