Difference between revisions of "Touchworks Impact Integration"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
(New page: In v10, Touchworks Clinical product (works database) updates the Scan/Forms product (impact database) with various events. NOTE: This is database specific information and should only be c...)
 
Line 1: Line 1:
 
In v10, Touchworks Clinical product (works database) updates the Scan/Forms product (impact database) with various events.
 
In v10, Touchworks Clinical product (works database) updates the Scan/Forms product (impact database) with various events.
 +
  
 
NOTE: This is database specific information and should only be considered by an experienced database administrator
 
NOTE: This is database specific information and should only be considered by an experienced database administrator
 +
  
 
The most common Ive seen to be problematic for some customers is the User Password updates.
 
The most common Ive seen to be problematic for some customers is the User Password updates.
 +
  
 
Ideally, if everything is setup correctly, changing a user's password in TWUser Admin will automatically update the same user's password in Scan.
 
Ideally, if everything is setup correctly, changing a user's password in TWUser Admin will automatically update the same user's password in Scan.
 +
  
 
This integration is driven by the following stored procedures and tables:
 
This integration is driven by the following stored procedures and tables:
 +
 
1. works..FileProvider is called by Touchworks upon the user clicking save in TWUser Admin's Edit
 
1. works..FileProvider is called by Touchworks upon the user clicking save in TWUser Admin's Edit
 +
 
2. works..FileProvider then looks up integration information in the works..integration_de table
 
2. works..FileProvider then looks up integration information in the works..integration_de table
 +
 
3. works..FileProvider then calls impact..spInsertUpdateDeleteUser  
 
3. works..FileProvider then calls impact..spInsertUpdateDeleteUser  
 +
 
4. impact..spInsertUpdateDeleteUser updates the password information in the impact..sec_users table
 
4. impact..spInsertUpdateDeleteUser updates the password information in the impact..sec_users table
 +
 
5. Password for user in both works and impact is now in sync
 
5. Password for user in both works and impact is now in sync
 +
  
 
Troubleshooting:
 
Troubleshooting:
 +
 
1. Id suggest making sure all tables/procedures exist
 
1. Id suggest making sure all tables/procedures exist
 +
 
2. Make sure chvoe login as read/execute access to relevant tables/procs in impact database
 
2. Make sure chvoe login as read/execute access to relevant tables/procs in impact database
 +
 
3. Verify works..integration_de has valid data.  This is what ive seen in working systems:
 
3. Verify works..integration_de has valid data.  This is what ive seen in working systems:
 +
  
 
select * from integration_de
 
select * from integration_de
 +
0 0 0 0                     N N Y 2004-02-02 12:34:42.030
 +
  
0 0 0 0                     N N Y 2004-02-02 12:34:42.030
 
 
2 890030 0 2 AIC      Impact TWIS      N N Y 2006-08-02 19:32:17.623
 
2 890030 0 2 AIC      Impact TWIS      N N Y 2006-08-02 19:32:17.623

Revision as of 14:30, 21 April 2009

In v10, Touchworks Clinical product (works database) updates the Scan/Forms product (impact database) with various events.


NOTE: This is database specific information and should only be considered by an experienced database administrator


The most common Ive seen to be problematic for some customers is the User Password updates.


Ideally, if everything is setup correctly, changing a user's password in TWUser Admin will automatically update the same user's password in Scan.


This integration is driven by the following stored procedures and tables:

1. works..FileProvider is called by Touchworks upon the user clicking save in TWUser Admin's Edit

2. works..FileProvider then looks up integration information in the works..integration_de table

3. works..FileProvider then calls impact..spInsertUpdateDeleteUser

4. impact..spInsertUpdateDeleteUser updates the password information in the impact..sec_users table

5. Password for user in both works and impact is now in sync


Troubleshooting:

1. Id suggest making sure all tables/procedures exist

2. Make sure chvoe login as read/execute access to relevant tables/procs in impact database

3. Verify works..integration_de has valid data. This is what ive seen in working systems:


select * from integration_de 0 0 0 0 N N Y 2004-02-02 12:34:42.030


2 890030 0 2 AIC Impact TWIS N N Y 2006-08-02 19:32:17.623