Difference between revisions of "Problem list not searchable"
Jump to navigation
Jump to search
Tony.Yelacic (talk | contribs) (New page: I recently had this issue arise while migrating my current customer from a Test system to Live system. Upon login to the Live system, the logged in user was unable to search for problem...) |
Max.Stroud (talk | contribs) |
||
Line 1: | Line 1: | ||
I recently had this issue arise while migrating my current customer from a Test system to Live system. | I recently had this issue arise while migrating my current customer from a Test system to Live system. | ||
− | Upon login to the Live system, the logged in user was unable to search for problems when trying to add a problem to a patient's HMPs. After ensuring the ICD-9 codes and Problems were in the database, I reviewed the "Problem" dictionary and discovered that the entire "Problem" dictionary in the live system had the "Inactive" flag set. | + | Upon login to the Live system, the logged in user was unable to search for problems when trying to add a problem to a patient's HMPs. After ensuring the [[ICD-9]] codes and Problems were in the database, I reviewed the "Problem" dictionary and discovered that the entire "Problem" dictionary in the live system had the "Inactive" flag set. |
I believe this can be resolved by running a SQL script to change the "Inactive" flag but am waiting to here from Allscripts. I will update this article when I get word. | I believe this can be resolved by running a SQL script to change the "Inactive" flag but am waiting to here from Allscripts. I will update this article when I get word. |
Revision as of 16:00, 8 May 2008
I recently had this issue arise while migrating my current customer from a Test system to Live system.
Upon login to the Live system, the logged in user was unable to search for problems when trying to add a problem to a patient's HMPs. After ensuring the ICD-9 codes and Problems were in the database, I reviewed the "Problem" dictionary and discovered that the entire "Problem" dictionary in the live system had the "Inactive" flag set.
I believe this can be resolved by running a SQL script to change the "Inactive" flag but am waiting to here from Allscripts. I will update this article when I get word.