Integration is not necessarily only about messaging and information exchange between systems. Integration also includes making two software components work together within a system, such as a middleware component and a presentation portal that are source from different vendors. Anytime two system components have different underlying information models and need to be made to work together you transform one components information model into the other using integration components (or adapters). This is also why integration is different to interoperability, if two component were interoperable then you wouldn't need the integration components. When an existing software system is not interoperable with openEHR we can use a TDS pipeline to integrate with openEHR.
Heath > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Tim Cook > Sent: Tuesday, 27 November 2007 12:15 PM > To: For openEHR technical discussions > Subject: RE: Compact XML format...? > > > Hi Heath, > > On Tue, 2007-11-27 at 11:32 +0100, Heath Frankel wrote: > > As stated previously, the TDS is not > > intended for information exchange, but as a tool for integration. > > This may be getting too philosophical for my small brain. > > I do apologize for being so "dense". But I cannot reconcile the > difference you are claiming between "information exchange" and > "integration". > > Isn't 'integration' the process of validating/coordinating 'information > exchange'? > > Cheers, > Tim > > -- > Timothy Cook, MSc > Health Informatics Research & Development Services > LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook > > ?I don?t know. I only work here.? :-) > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
