Difference between revisions of "Allscripts Enterprise EHR - OID SSMT Fundamentals"
Steve.Stahr (talk | contribs) (→Q & A) |
Steve.Stahr (talk | contribs) |
||
| Line 6: | Line 6: | ||
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. | 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. | 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. | ||
| − | + | ====In a practical sense, if you need to add one item, wouldn't you just add it in the dictionary? (*referring to the fact that the presenter created a single orderable using SSMT)==== | |
Yes, that would be an efficient and simpler way to do it. In this case, I just used a single entry into SSMT for training purposes. | Yes, that would be an efficient and simpler way to do it. In this case, I just used a single entry into SSMT for training purposes. | ||
Revision as of 21:57, 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.
In a practical sense, if you need to add one item, wouldn't you just add it in the dictionary? (*referring to the fact that the presenter created a single orderable using SSMT)
Yes, that would be an efficient and simpler way to do it. In this case, I just used a single entry into SSMT for training purposes.