This webcast introduces AE-EHR Clinical Exchange Document (CED) capabilities as well as an approach to exchange an unsolicited CED within the ConnectR interface engine.

1. ConnectR Interface
Webcast Series
Clinical Exchange Document
March 2011

2. Welcome
• What is a Clinical Exchange Document (CED)?
• Continuity of Care Document (CCD)
• Web Services
• Database Components
• ConnectR Superset Source
• ConnectR Interface Mapping & Script
• Output & Formatting
• Q&A – Chat and Live
March 2011

3. Clinical Exchange Document
• Generally accepted format of patient data that is used to share
information between systems.
• CCR (Continuity of Care Record) and Medical Summary (a CDA)
are the two CED formats that are supported in V11.
• CED is an Allscripts term to cover all the different formats that
are supported.
• Xml documents - essentially encounter summaries containing
allergies, medications, immunizations, problems, vitals, results.
• These extracts can be printed or saved as an xml document.
• The xml document can be imported into other TouchWorks
systems or other EHR's that support the format.
• http://wiki.galenhealthcare.com/Clinical_Exchange_Document
March 2011

4. Clinical Exchange Document continued
March 2011

5. Continuity of Care Document
• CCD was developed as a collaborative effort between ASTM and
HL7, combining the benefits of ASTMs Continuity of Care Record
or CCR and the HL7 Clinical Document Architecture (CDA)
specifications.
• It is intended as an alternate implementation to the one specified
in ASTM ADJE2369 for those institutions or organizations
committed to implementation of the HL7 Clinical Document
Architecture
March 2011

6. Web Services
• http://www.object-ideas.com/web-services.htm
• http://en.wikipedia.org/wiki/Web_service
• A Web service is a method of communication between two electronic devices
over a network.
• Other systems interact with the Web service in a manner prescribed by its
description using SOAP messages, typically conveyed using HTTP with an XML
serialization in conjunction with other Web-related standards
• SOAP
– Messages are exchanged using the Simple Object Access Protocol (SOAP).
– It is used to construct the request & response message(s), to and from the web
service.
– In essence SOAP is the mechanism to make remote procedure calls.
– SOAP uses structured XML messages between the requestor and the supplier of
a web service.
March 2011

7. Database Components
• Custom Stored Procedure - FileCEDEvent
– Populate event table with CED events based upon predetermined criteria
– For our example, our criteria was those patients with recent demographic
changes
• Custom SQL Server Job
– Run the FileCEDEvent stored procedure at a certain interval
– We chose to run every 5 minutes
March 2011

8. ConnectR Superset Outbound Source
http://wiki.galenhealthcare.com/ConnectR_Superset_Source
March 2011

9. ConnectR Interface Mapping
March 2011

10. ConnectR VBScript – Executes Web Service Call
March 2011

11. Output & Formatting
• The output xml will not be
formatted.
• Utilize the following Allscripts-
provided xsl to properly format
the document so that it renders
nicely when opened in IE
• Open in notepad, and prefix the
document with the following:
• <?xml-stylesheet type='text/xsl'
href='http://www.allscripts.com/r
esources/tools/STYLES/ALLSCR
IPTS_CED.XSL'?>
March 2011

12. Thank you for joining us today, for additional
assistance….
You can contact us through our website at
www.galenhealthcare.com
March 2011