Difference between revisions of "Allscripts Enterprise EHR - OID SSMT Fundamentals"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
(Created page with "==Q & A== ====Are you planning on covering flowsheets?==== Not on our OID Webcast series, but we have discussed hosting a webinar for flowsheets. I'll make note of you request.")
 
Line 2: Line 2:
 
====Are you planning on covering flowsheets?====
 
====Are you planning on covering flowsheets?====
 
Not on our OID Webcast series, but we have discussed hosting a webinar for flowsheets. I'll make note of you request.
 
Not on our OID Webcast series, but we have discussed hosting a webinar for flowsheets. I'll make note of you request.
 +
====Can you user SSMT to copy from the Prod environment to test to keep systems in sync?====
 +
This depends on the volume and nature of data involved.
 +
If items are built in one enviroment, then copied into another environment, SSMT is a good option, but if items are being modified, and those modifications migrated with SSMT, make sure the systems are in sync before hand. If the systems are not in sync, the new rows could error out OR create duplicates that you don't want.
 +
For instance, if your Requested Performing Locations dictionary names were the slightly different in environments (Hospital Laboratory vs. Hospital Lab), an SSMT load into one environment would work, but would error out on the other.

Revision as of 21:54, 26 January 2011

Q & A

Are you planning on covering flowsheets?

Not on our OID Webcast series, but we have discussed hosting a webinar for flowsheets. I'll make note of you request.

Can you user SSMT to copy from the Prod environment to test to keep systems in sync?

This depends on the volume and nature of data involved. If items are built in one enviroment, then copied into another environment, SSMT is a good option, but if items are being modified, and those modifications migrated with SSMT, make sure the systems are in sync before hand. If the systems are not in sync, the new rows could error out OR create duplicates that you don't want. For instance, if your Requested Performing Locations dictionary names were the slightly different in environments (Hospital Laboratory vs. Hospital Lab), an SSMT load into one environment would work, but would error out on the other.