Integration ReGeneration

1
Integration Re-Generation
Your guide to Salvation when an integration has
just gone to He_ _
2
Weve all been thereEIS is installed, we
verified it is accessible using HTTP. But No
Data is flowing from the clinical application
.Where to from Here?

• Agenda
• Part One - EIS
• Quick Review of integration types and paths
• Step-By-Step approach to problem isolation
• Cures for the common issues
• Part Two
• Interface Plug-In
• CIM
• Advanced techniques for the adventurous
• When all else fails Next Steps

3
Integration Styles

• Enterprise Supports 3 Integration Options
• Real-Time via EIS Web Service
• File Based via Interface Plug-in Service
• File Based via EIS Backward Compatibility With
  CIM (EIS Tools installed on clinical system,
  Monette Hi-Tech to CareTracker is only
  integrations using the CIM)

4
EIS, the Heart of It All Current Pathways of
Integration Import Processes
Clinical database
CareTracker Database
DTS Job
FTP Plug-in
Failed Msgs
Res., Census
Enterprise Middle Tier
Interface Plug-in
XSLT
Batch Export
Ctimport
HL7 Sender
XML MSG
XML Data Validation
EIS Web Service
Online Clinical Application
XML MSG
XML MSG
XSLT
Integration Engine
EISApp
Enterprise Network
Clinical Network
5
EIS, The Heart of It All Current Pathways of
Integration Export Processes
Clinical database
CareTracker Database
Output File
Stored Procedure
Crystal RPT Engine
MDS Report Request
XSLT
XML Data Validation
EIS Web Service
Other Report Requests
XML MSG
CIM MDS Reporting
CREPORT
XSLT
EISApp
Enterprise Network
Clinical Network
6
No Examination Without Identification
What type of installation is This? CareTracker
ChargeTracker CareTracker and ChargeTracker
Combined What Type of Integration is
This? Real-time using EIS EIS Checkup File
Based using the Interface Plug-in EIS Checkup
Interface Plug-in
Checkup File Based using the
CIM EIS Checkup CIM Checkup The title page
of the user documentation identifies which
Integrations are using the Interface Plug-in.
All other Integrations are using EIS in
real-time except for Monette And Hi-Tech to
CareTracker which uses the CIM.
7
Start with The Heart - Unlocking EIS Health

• Step One Check Pulse
• Check Event Logs
• Check ../EIS/Log Folders (New in 8.0)

• Step Two Perform Stress Test
• Exercise EIS using EISApp Test Tool

• Step Three Examine Circulatory System
• Request EIS From Clinical Server
• http//ltweb_site_name/eis/eis.asmx
• Exercise EIS From Clinical Server
  using EISApp test tool

8
Check Event Logs Mgmt_Err
9
Check Event Logs Mgmt_Err

• Common Errors Found in Mgmt_Err
• Registration/Authentication
• Check to see if EIS is registered (Administration
  Tab, View or Install Modules and Kits link)
• If not, register EIS
• If EIS is registered, 8.0 has a new
  authentication capability. This is enabled in
  the EIS_Config file in the ../WEB/Config Folder.
  If this mode has been enabled, the calling
  application must pass an authentication key in
  its SOAP header that matches the authentication
  key string in the EIS_Config file. Currently
  only in use by Adventist. To test to see if this
  is the issue, change Authentication to False in
  the EIS_Config file and perform an IISRESET. Try
  sending information to EIS and see if it is
  successful. If it is, the sending application is
  not sending an authentication key or it is
  sending the wrong key.

10
Check Event Logs Mgmt_Err

• Common Errors Found in Mgmt_Err (Continued)
• Web Service Timeout
• This is likely to be a result of a request to
  process an unusually large transaction set (gt 4
  megabytes) or a SQL error occurs in trying to
  process the request.
• Often the error message in the log will point you
  to the source issue
• If it appears to be an unusually large
  transaction, contact the Integration Analyst or
  Development Team for assistance.

11
Check Event Logs Mgmt_Err

• Common Errors Found in Mgmt_Err (Continued)
• There is no row at position 0
• This is generally a result of a required key
  value missing in CareTracker.
• It is commonly associated with the facility id
  not being set up in CareTracker. I.E. the
  clinical facility id is not the same as the
  CareTracker facility id, and the secondary id has
  not yet been entered on the CareTracker facility
• If could also be generated by an xslt
  transformation changing the value behind the
  scenes. See what the value is in the
  ProcessedMessages log folder to identify this
  type of error

12
Check ../EIS/LOG Folders
13
Check ../EIS/LOG Folders

• These Folders are only available starting with
  8.0
• ReceivedMessages
• Contains the xml message received by EIS before
  any XSLT Transformations
• If Messages exist in this folder, EIS is
  receiving requests successfully.
• Messages are kept for 7 days and then removed. A
  message may survive longer than 7 days if no
  activity occurs. Messages are only removed when
  a new message is received.
• Messages in this folder can be used to verify
  what a clinical system sent to EIS. If there is
  a question about a certain update, this folder
  can be searched to verify that the message was
  received, and what the content of that message
  was.

14
Check ../EIS/LOG Folders

• (Continued)
• ProcessedMessages
• Contains the xml message processed by EIS after
  any XSLT Transformations have been applied
• If Messages exist in this folder, EIS is
  receiving requests successfully and is attempting
  to process them.
• Messages are kept for 7 days and then removed. A
  message may survive longer than 7 days if no
  activity occurs. Messages are only removed when
  a new message is received.
• Messages in this folder can be used to verify
  what the final XML message content looked like.
  Comparing received message with final message
  shows how XSLT is affecting XML message content.

15
Check ../EIS/LOG Folders

• (Continued)
• ReturnedData
• Contains the xml message EIS returned to the
  calling application
• If Messages exist in this folder, EIS processed
  requests successfully or with no fatal errors.
  Content being returned is either status code for
  modify transactions, or report content for report
  request transactions.
• Messages are kept for 7 days and then removed. A
  message may survive longer than 7 days if no
  activity occurs. Messages are only removed when
  a new message is received.
• Messages in this folder can be used to verify
  what the XML message content returned to a
  clinical applications looked like.

16
Check ../EIS/LOG Folders

• (Continued)
• Errors
• Contains an xml message with any fatal errors
  encountered by EIS when it was attempting to
  process a request
• If Messages exist in this folder, EIS was not
  able to process the request successfully
• Messages are kept for 7 days and then removed. A
  message may survive longer than 7 days if no
  activity occurs. Messages are only removed when
  a new message is received.
• Messages in this folder can be used to help
  troubleshoot why a specific request failed.

17
Check ../EIS/LOG Folders

• (Continued)
• Why no messages are appearing in any of the
  folders
• The message sent by the calling application is
  failing to validate in EIS (Validate doesnt log)
• Networking issue EIS is not receiving the data
• A validation issue can be determined by using the
  EISApp test tool (will be covered later in this
  tutorial)
• Networking issues may require advanced techniques
  to prove (covered later in this tutorial).

18
Check ../EIS/LOG Folders

• Common Issues Recorded in Errors Folder
• Configuration Mismatch
• Resident import level must be 2 or higher to use
  the census object. Please update the EIS
  settings in the Resource Enterprise Manager
• Update the Interface Tab of the website in the
  Resource MMC to the proper configuration values.
  (Refer to user documentation for a given vendor,
  section 3 for specific settings)

19
Check ../EIS/LOG Folders

• Common Issues Recorded in Errors Folder
• Missing XSLT Transformation
• An unexpected error occurred during processing
  the file. Error Could not find file 'e\program
  files\resource systems\resource enterprise
  manager\Installs\Trouble\Web\Versions\8.0.0\eis\XS
  LT\Crap.xslt'.
• The EIS_Config folder has an xslt transformation
  configured for this transaction type (Resident,
  Census, Staff, Item) but the xslt script is not
  in the ../EIS/XSLT folder. Locate the missing
  file and place it in this folder.

20
Check ../EIS/LOG Folders

• Common Issues Recorded in Errors Folder
• Data Errors
• Resident recnum not Valid! LineNumber 2
• There was a problem with the resident id in the
  second record of the transaction. This record
  was not processed, it was rejected. Review the
  Received Messages folder for the original XML
  message to determine why the data was considered
  invalid by EIS.
• This is just a sample of the types of data errors
  you may encounter. You will need to examine the
  error message content to help determine the type
  and cause of the error.

21
Sample Error Message Content
22
EISApp A Troubleshooters Best Friend

• EISApp is a Tool to exercise EIS functionality
• Windows Based
• Can be installed on a CareTracker server
• Can be installed on a Clinical server
• Sends Raw XML Messages to EIS
• Packaged as a zip file, download, unzip
• set URL, and its ready to use
• Versions available for each Release and
• specific vendor custom versions of EIS
• 7.0.1
• 7.0.2
• 8.0.0
• Keane 8.0
• QuickCARE 8.0

23
EISApp Installation setup
Copy desired version of EISApp to a folder on the
server Unzip EISApp to the folder Change
directories to the Bin folder in the EISApp
folder Edit the EISApp.exe.config file using
Notepad and change all URL references to the URL
for EIS on your CareTracker Server and then save
and exit Notepad Copies of EISApp can be
obtained from the Resource Systems download
site
24
EISApp Folder Structure
25
EISApp Edit Config (bin folder)
26
EISApp EISApp.exe.config, change URL
27
EISApp EISApp.exe.config, change URL
28
EISApp Run EISApp
29
EISApp TestFiles folder, for test xml trxs
30
EISApp Copy test xml
Open the residents.xml file in Notepad Select
all text Copy to windows clipboard Close
residents.xml file
31
EISApp Paste xml text into clipboard
32
EISApp Edit text, set correct facility id
33
EISApp Validate
34
EISApp Validation Failures
If validation fails and you havent created
syntax errors in the test XML, EIS is Dead!

• Common Issues
• The wrong Version of EIS is installed
• For example, Keane custom
• installed, should be standard 8.0
• Communication Issues
• There are problems in IIS or the
• network
• Configuration Issues
• Trying to process census trx and resident
• level 2 is not configured in Interface tab

35
EISApp Upload
36
EISApp Upload
If the second line failed to upload, this is
correct, EIS is alive and well! If the first
line has errors, then there are problems in EIS.
The error message should give some idea of
what The problem is. You can use the Resident
maintenance function in CareTracker to verify
that the information for the resident In the
first line of xml was processed correctly. If
the Resident Import Level is 2, you will need
to check the Show discharged residents box in
order to see this Resident in the list of
residents.
37
EISApp Upload Next Steps

• If your test shows that EIS is functioning
  properly
• Copy EISApp to clinical server and repeat test
• If you can access EIS from the clinical server,
  then
• Network Issues
• Firewall Issues
• If remote EISApp test is successful, then
  Clinical System or
• Interface Plug-In or CIM

38
EISApp BugBuster

• If all tests to this point are successful, you
  can use
• EISApp to troubleshoot the calling applications
• Xml transaction.
• Find calling applications xml message in
• ReceivedMessages Log Folder.
• Edit message using NotePad and select
• all contents. Copy to clipboard, and then
• paste into EISApp clipboard.
• Execute the EISApp validate and upload steps
• from the previous slides. This should give
  an
• indication of why the calling applications
  xml
• transaction isnt processing.

39
EISApp GetDataXmlStream

• Can retrieve any CareTracker report via
• EIS
• Generally used to validate MDS
• Interface Reports
• Results can be
• Displayed to screen
• Displayed as data table in final
• output format

40
EISApp GetDataXmlStream
41
EISApp TestFiles folder, for test xml trxs
42
EISApp Copy test xml
Open the SectionG.xml file in Notepad Select
all text Copy to windows clipboard Close
SectionG.xml file
43
EISApp Paste xml text into clipboard
44
EISApp Edit text, set parameter values
45
EISApp Validate
46
EISApp Retrieve Data
47
EISApp Retrieval Failures
If retrieval fails and you havent created syntax
errors in the test XML, there could be several
sources of the failure!

• Common Issues
• The input parameters is wrong
• For example, the date range you are
• using doesnt have any data in
• CareTracker
• Wrong Report Name
• The report name you are asking for doesnt match
  in CareTracker
• Mismatch in Report Parameters
• Not all the required parameters are being passed
  in the request

48
EIS All Systems Go.
If all of your tests for EIS have passed
including Network access then we need to look
further.
The Network The Calling Application
The CIM
The Interface Plug-in
49
EIS All Systems Go.
If the integration style is real-time using web
services (EIS) then the problem could be in The
calling application The network
If the integration style is using the Interface
Plug-In then the problem could be in The
calling application The network
The Interface Plug-In
If the integration style is using the CIM then
the problem could be in The calling application
The network The CIM
(EIS Tools, deployment and config)
50
Intermission Take a Break!End of Part One
51
The Interface Plug-In The Detailed View

• Optional Module not installed by default
• Can be installed on separate server including
  non-CareTracker systems
• File Access Based (local, mapped and remote files
  )
• Maps file content to XML and then calls EIS web
  service
• Can process a single file or an entire directory
  using std Microsoft pattern matching ( .txt,
  resident.txt)
• Approach Used for RFW to ChargeTracker
  Implementations
• Available Integrations
• Resident Demographic Import
• Census Import
• Generic
• Full Census Object
• Staff Import
• Item (Product/Inventory) Import

52
The Interface Plug-In Folder Structure

• Parent Folder is ../Program Files/Resource
  Systems/Resource Enterprise/Installs/ltinstall
  namegt/PluginService/Versions/ltReleasegt/InterfacePl
  ugin
• Backup Folder contains copy of last 100 files
  processed by the Interface Plug-In
• BadMessages Folder contains xml messages that
  failed to update and have been retried 60 times
  and still failed.
• Exp Folder contains the special Exp files that
  contain mapping and processing instructions for
  all the files the Interface Plug-In is supposed
  to process
• Log Folder contains a log of status and error
  messages for the Interface Plug-In. May also
  contain a trace file.
• QueuedMessages Folder contains xml files with
  entries that the Interface Plug-In was unable to
  process. These entries will be re-tried each
  time the Interface Plug-In runs for a maximum of
  60 times
• XSLT Folder contains xslt transformations
  referenced in an exp file. These are
  transformations the Interface Plug-In will
  perform on incoming data

53
The Interface Plug-In Exp Files

• Each .Exp file identifies one or more files to
  process
• Multiple .Exp files can be defined when multiple
  integrations are required (For example, resident
  and census)
• .Exp files are processed in alphabetical order
• The Interface Plug-In checks for .Exp files once
  every 60 seconds. The latest version of the
  files are used. If a .Exp file changes, there is
  no need to restart the Interface Plug-In. The
  changes will take effect in the next polling
  cycle automatically
• .Exp files contain three sections, The first
  section identifies the
• field(s) to be processed and settings that
  control the behavior of the Interface Plug-In.
  The second section contains definitions that map
  the input file contents to Resource Systems xml
  for a given integration type (Resident, Census,
  Staff, Items). The third section is just a
  documentation section that explains entries in
  the first two sections.
• The information contained in the .Exp is critical
  to the correct functioning of the Interface
  Plug-In and a given integration
• Detailed documentation of the .Exp file and its
  key settings are available in the user
  documentation for each integration. (Customs for
  Pilots are the exception, in these instances,
  contact your integration analyst

54
Exp Setup section, delimited files

• Setup
• FILETYPERESIDENT (Resident,
  Census, Item, Staff)
• IMPORTFILENAMEC\temp\ (Full File name or
  directory, if directory end with \ )
• FILEFORMATDELIMITED (Fixed or
  Delimited)
• DELIMITOR,
  (Delimiter character, use \t for tab \r for cr )
• FIELDWRAPPER (Character
  wrapping field values)
• INCLUDESHEADERNO (If first line of
  file is headings, set to yes to ignore)
• TRUNCATEFIELDSYES (Yes truncate to
  length in schema)
• UNIXTODOSNO (Yes
  convert line termination from LF to CRLF )
• HASFACILITYINDATAYES (A facility
  identifier is included in the data0
• EISURLHTTP//integrations.tdpi.com/kindred/EIS/ei
  s.asmx
• WEBSERVICETIMEOUT120 (seconds to wait for
  call to EIS to complete)
• LOADMETHODAUTO (Signals EIS to
  operate in load mode)
• BACKUPYES (Source
  file will be saved to backup folder)
• DIAGNOSTICYES (Special mode
  that creates log files for
  Troubleshooting)
• ADDFACILITYTOIDYES (Resident id
  facilityid-residentid )
• VALIDATEONLYNO (Test mode, parse
  file but dont sent to EIS)
• WATCHDIRECTORYYES (Will process requested
  files in directory)
• FILEPATTERNMATCH"ResidentData.txt (File
  pattern match to process)

55
Exp FieldList section, delimited files

• FieldList
• FIELD1 RESIDENTFIRSTNAME,C (Unique
  identifier,
• 
  xml tag, data type,
• 
  special formatting)
• FIELD2 RESIDENTMIDDLEINITIAL,C
• FIELD3 RESIDENTLASTNAME,C
• FIELD4 ADMIT,D,MM/DD/YYYY
• FIELD5 DISMISS,D,MM/DD/YYYY
• FIELD6 RESIDENTROOM,C
• FIELD7 FACILITYID,C
• FIELD8 RESIDENTREF,C
• FIELD9 RESIDENTLOCATION,C
• FIELD10 RESIDENTSTATUS,C
• FIELD11 STATUSEFFECTIVEDATE,D,MM/DD/YYYY
• FIELD12 SECONDARYID,C

56
Exp Setup section, fixed length files

• Setup
• FILETYPERESIDENT (Resident,
  Census, Item, Staff)
• IMPORTFILENAMEC\temp\ (Full File name or
  directory, if directory end with \ )
• FILEFORMATFixed (Fixed or
  Delimited)
• INCLUDESHEADERNO (If first line of
  file is headings, set to yes to ignore)
• TRUNCATEFIELDSYES (Yes truncate to
  length in schema)
• UNIXTODOSNO (Yes
  convert line termination from LF to CRLF )
• HASFACILITYINDATAYES (A facility
  identifier is included in the data )
• EISURLHTTP//integrations.tdpi.com/kindred/EIS/ei
  s.asmx
• WEBSERVICETIMEOUT120 (seconds to wait for
  call to EIS to complete)
• LOADMETHODAUTO (Signals EIS to
  operate in load mode)
• BACKUPYES (Source
  file will be saved to backup folder)
• DIAGNOSTICYES (Special mode
  that creates log files for
  Troubleshooting)
• ADDFACILITYTOIDYES (Resident id
  facilityid-residentid )
• VALIDATEONLYNO (Test mode,
  parse file but dont sent to EIS)
• WATCHDIRECTORYYES (Will process
  requested files in directory)
• FILEPATTERNMATCH"ResidentData.txt (File
  pattern match to process)
• INPUTXSLTKindredResidentFilter.xslt ( xslt
  transformation before EIS)

57
Exp FieldList section, fixed length files

• FieldList
• FIELD1 RESIDENTLASTNAME,C,1,12,0 (Unique Id,
  XMLTag, data type,
• 
  starting position, ending
• 
  position, decimals,
• 
  special formatting)
• FIELD2 RESIDENTFIRSTNAME,C,13,15,0
• FIELD3 RESIDENTREF,C,28,5,0
• FIELD4 RESIDENTROOM,C,33,7,0
• FIELD5 SECONDARYID,40,11,0
• FIELD6 RESIDENTLOCATION,C,59,3,0
• FIELD7 ADMIT,D,0,0,0,,NOW
• FIELD8 Dismiss,D,60,10,0,MM/DD/YYYY

58
Exercise the Limbs - Checking Interface Plug-In
Health

• Step One Check Pulse
• Check Interface Plug-In Backup Folder
• Check Event Logs (Plg_Err)
• Check Plug-In Log Folder
• Check EIS Log Folder

• Step Two Perform Stress Test
• Turn On Diagnostics in .Exp re-run
• Exercise Interface Plug-In using a test
• file against a test site

59
Check Interface Plug-in Backup Folder

• ..\InterfacePlugin\Backup
• Contains a copy of the last 100 files transmitted
• Check this folder to see if any files have been
  received
• The presence of a file in this folder doesnt
  mean it has been processed successfully. It does
  mean that the plug-in was able to see the file
  and it tried to process it. If it was not
  processed successfully the file may have data
  errors or there are downstream problems with the
  network or EIS
• You can open the file in notepad and do a quick
  eyeball test to see if there are any records
  that look malformed (blank row, short data,
  illegal characters, etc.

60
Check Event Logs Plg_Err
61
Check Event Logs Plg_Err

• Common Errors Found in Plg_Err
• There is no row at position 0
• This is generally a result of a required key
  value missing in CareTracker.
• It is commonly associated with the facility id
  not being set up in CareTracker. I.E. the
  clinical facility id is not the same as the
  CareTracker facility id, and the secondary id has
  not yet been entered on the CareTracker facility
• If could also be generated by an xslt
  transformation changing the value behind the
  scenes. See what the value is in the
  ProcessedMessages log folder to identify this
  type of error

62
Check Event Logs Plg_Err

• Common Errors Found in Plg_Err (Continued)
• Web Service Timeout
• This is likely to be a result of a request to
  process an unusually large transaction set (gt 4
  megabytes) or a SQL error occurs in trying to
  process the request.
• Often the error message in the log will point you
  to the source issue
• If it appears to be an unusually large
  transaction, contact the Integration Analyst or
  Development Team for assistance.

63
Check Event Logs Plg_Err

• Common Errors Found in Plg_Err (Continued)
• Requested Index is Beyond End of Record
  This is likely a result of a reference in the
  FieldList section of the .Exp file using offsets
  that are beyond the end of the record in the
  Source File.
• Check the index values being used in the .EXP
  file to make sure they are within the size of the
  record
• This can also be caused by a blank or short data
  row in the Source File.
• Examine the source file for short rows. Also
  check the end of the file to see if blank records
  have been written there. I.E. there are extra
  carriage return line feed combinations.

64
Check ../InterfacePlugIn/LOG Folders
65
Check ../InterfacePlugIn/LOG Folders
66
Check ../EIS/LOG Folders
67
Interface Plug-In Stress Test Using Test Files
and Test Sites

• Turn On diagnostics and re-run
• In Setup section of the exp file
• change DIAGNOSTICNO to
• DIAGNOSTICYES
• Copy file from backup folder to source
• file name and path
• Sourcedata.xml and XmlSentToEIS.xml are
  created in the
• Source path. Examine contents
• In InterfacePlugin\Log folder there is
• an Interface.trc file that a developer
• can use to determine where the
• Plug-In was in the code when it failed
• Make sure to turn-off diagnostics when
• finished.

68
Interface Plug-In Stress Test Using Test Files
and Test Sites (Cont)

• Vendor specific test sites
• http//integrations.tdpi.com
• TRIAD14

• Customer system
• Modify EXP file to point to vendor
• specific test site on TRIAD14

69
CIM Compatibility Mode The Detailed View

• Optional Module not installed by default
• Bundled as a separate set-up package (EISTools)
  and supplied to the vendor
• Can be installed on the vendors server, or each
  client workstation
• Consists of two executables CTimport.exe and
  CReport.exe
• File Access Based (local, mapped and remote files
  )
• Maps fixed CSV file content to XML and then calls
  EIS web service
• Can only process a single file
• Generally invoked from within vendors clinical
  application
• Available Integrations
• Resident Demographic Import
• Census Import
• Generic
• Full Census Object
• Staff Import
• Item (Product/Inventory) Import
• MDS or other report information export

70
The CIM Folder Structure

• There is none the CTimport.exe and CReport.exe
  programs can be installed at the location of
  choice.

71
Exercise the Limbs - Checking CIM Health

• Step One Check Pulse
• Check ActivityLog.log
• This file will be created in the same folder the
  CTimport.exe and CReport.exe programs reside in

• Step Two Perform Stress Test
• Exercise CIM using a test
• file against a test site

72
Exercising the CIM

• Invoking The Import Process
• ctimport.exe "c\program files\resource
  systems\eistools\ctkexp002.csv','http//integratio
  ns.tdpi.com/trouble/eis/eis.asmx','False','Residen
  t
• Common issues
• 1. Syntax is exact and unforgiving
• 2. The file
  reference parameter must include a drive
• designation,
  even if it is in the logged in folder
• 3. Security and web
  permissions If ctimport is
• being run from
  a mapped drive on a 2003 server,
• there are
  additional security settings in the browser and
• the .NET
  Framework that must be set on the local
• workstation
  invoking the ctimport.exe process

73
Exercising the CIM (cont)

• Invoking The Reporting Process
• creport.exe "'http//integrations.tdpi.com/eis/eis
  .asmx','Observation Detail Interface','D',C\Myte
  st.txt','CSF','','Resident Id',1009',1009','Obser
  ve Date',04/01/2005',04/30/2005',
• Common issues
• 1. Syntax is exact and unforgiving
• 2. The file
  reference parameter must include a drive
• designation,
  even if it is in the logged in folder
• 3. The input parameters must
  match the report settings
• 4. Security and
  web permissions If creport is
• being run
  from a mapped drive on a 2003 server,
• there are
  additional security settings in the browser and
• the .NET
  Framework that must be set on the local
• workstation
  invoking the ctimport.exe process

74
Advanced techniques for the adventurous

• Packet Sniffing Chasing SOAP message/network
  issues
• Install on the CareTracker server
• To prove end to end connectivity
• To examine SOAP message
• sent by the vendor
• Install on clinical vendor server
• To prove message is being sent
• To examine initial SOAP message
• contents
• To assist with firewall issues

75
Advanced techniques for the adventurous
Packet Sniffing The Tools WireShark
opensource utility http//www.wireshark.
org/ Effetech EtherDetect 30 day trial
http//www.effetech.com
76
Places to Experiment
If you wish to experiment with some of the
techniques covered in the presentation a site has
been created for this purpose CareTracker
Home Page http//integrations.tdpi.com/t
rouble EIS Web Service
http//integrations.tdpi.com/trouble/eis/eis.asmx
Standard su passwords are in effect
77
When All Else Fails Next Steps
Youve been through all the steps and it seems
like youre chasing youre tail. Call the
integration analyst or development.. Then go
tip a few! You need it by now!