Hi All,
Our advanced problem search appears to be not working- saying it cannot connect to advanced specificity search. Our VAR mentioned that other customers have reported this too- just in a bind for a work around since we don't use custom problem lists for our providers, they always either use the smart search or the advanced search. Any ideas?
Thanks
I went into administration - system-advanced features - unclicked the advanced search box and clicked the enabled task management. We were at least able to find dx.
Dmiller1953 is correct and GE has said to use that workaround to help but there are still some users who cant use the feature.
But our task management is already enabled? So just unclick the Advanced specificity search?
That appears to have worked as a work around- thanks to you both!
Amy
As some of you know, AngleMD offers a third-party problem search encounter form (called AngleSearch) which serves as an adjunct/alternative to the Advanced Problem Search. It leverages ICD-10 terminology from Intelligent Medical Objects (IMO), and our licensing terms with IMO allow practices to try the application risk free for up to 30 days.
If any practices would like to use this simple alternative to the Advanced Problem Search while that service is temporarily unavailable, AngleMD would be happy to help. There would be no cost or obligation, and getting it up and running is as simple as creating a quickText macro for most practices (which can be done in mere moments). When the Advanced Problem Search feature comes back on-line, you can just delete the quickText macro, with nothing more to uninstall (but you would also be welcome to continue the trial for a full 30 days and find out why so many practices prefer the IMO terminology set).
If interested, or you would like to learn more, please contact:
David Gonzalez MD
971-275-0770
http://anglemd.com/anglesearch/
We use this product and love it!
Ours started working this morning.
We use AngleSearch as well, and our staff loves it, especially the ones going behind our physicians to clean up coding errors.
-Chris
We found that TLS1 was the cause of this. CPS12.2 and below has TLS1 explicitly set directly in the server.xml but the site that Advanced Problem Search points to ( https://ge1.healthlanguage.com) just started denying TLS1 connections without any warning. We have CPS12.3 in a test environment and it was not having this problem because it is set to use TLS1.0, TLS1.1, or TLS1.2 by default.
In short, we had to force CPS12.2 to stop using TLS1.0 and to use TLS1.1 and TLS1.2 on our Citrix master image template. I am reluctant to list out here the exact steps we took because some of it might not apply to your environment and could make things worse. I believe GE Support is aware of this now and can guide you through fixing it but if not, feel free to contact me directly if you want to discuss technical specifics.
Update- ours fixed over the weekend when GE announced it was working again. Thanks to all and I have passed along the AngleMD information to our CFO and Business office manager. 🙂