Greg,
Interfacing with existing systems using messaging such as HL7 is something I
have been doing for some time now and we have a considerable amount of
infrastructure to make it happen.  Ocean Informatics was involved in an
Interoperability Demonstration (similar to the IHE Demonstration at HIMMS)
at the recent MedInfo international health informatics conference in
Brisbane.  We demonstrated accepting HL7 V2 lab, ADT and referral messages
from other vendor system and stored them as openEHR compositions using both
base and specialised archetypes.  The process involved building a template
of those archetypes for each message type and mapping the HL7 into those
templates.  We also demonstrated converting an openEHR composition directly
committed in an openEHR repository to HL7 CDA.  The original creation of the
composition utilised a template but the actual conversion to CDA simply
utilised the knowledge in the archetype models to understand and develop the
transformation to the associated HL7 clinical statements within the CDA.
This CDA document was then submitted to another vendors IHE XDS repository.
This same process can be used to create HL7 v2 messages or any other format
you wish.


Regards
?
Heath
?
Heath Frankel
Product Development Manager
Ocean Informatics

Ground Floor, 64 Hindmarsh Square
Adelaide, SA, 5000
Australia
?
ph:?+61 (0)8 8223 3075
mb: +61 (0)412 030 741 
email:?heath.frankel at oceaninformatics.com 


 

> -----Original Message-----
> From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
> bounces at openehr.org] On Behalf Of Greg Caulton
> Sent: Saturday, 20 October 2007 9:12 PM
> To: For openEHR technical discussions
> Subject: Interfaces and Templates
> 
> Sorry, I meant to start a new thread, not hijack.  Let me do it now.
> 
> A couple more questions (by the way Leslies description was awesome
> and makes total sense).
> 
> Interfaces
> 
> a) When creating a generic outbound or inbound interface with an
> extrernal system - do you build based upon the archetypes only - i.e.
> provide as many values possible?  or your specializations? or is this
> all mute and we stick with HL7?
> 
> Templates, as a collection for a use case.  I looked out in Subversion
> but only see one out there:
> http://svn.openehr.org/knowledge/templates/dev/html/
> 
> b) Do templates or specializations or archetypes define workflow
> e.g.
> record results, based upon results collect additional information or not?'
> 
> In the case were a doc just wants to replicate a paper form but not
> improve it would I build a template or stick with Archetypes? So
> implementing a form like this:
> 
> http://home.cogeco.ca/~epiphany/FPDoctor-Perfect-Progress-Note-2.0.pdf
> 
> thanks!
> 
> 
> Greg Caulton
> Boston, MA
> http://www.patientos.org
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical



Reply via email to