Notifications
Clear all
Topic starter
This fix for us, opened up a whole new can of worms. Certain attachments trigger the "Start Centricity Practice Solution" browser page to move to the front of their terminal sessions after closing out the attachment. Our users keep calling to tell us that they got kicked out, when in fact, their session was just hiding behind this extraneous page. Does anyone know where I could go from here?
Posted : November 29, 2012 5:13 am
Gary,
How bizarre that you are experiencing those other issues. I have to admit that I have not had those worms rear their heads when I have implemented the "fix". If you want, I can send you a copy of my file so you can compare it to yours and see if there are any differences. Which attachments are misbehaving?
Terri
Posted : November 29, 2012 11:35 am
Topic starter
Hi Terri,
It appears to be anything that was scanned in via Docutrak. Our Indxlogic documents open just fine without issue. It is quite strange and might have to do with how the document paths are created.
Posted : November 29, 2012 10:21 pm
glamontagne said:
This fix for us, opened up a whole new can of worms. Certain attachments trigger the "Start Centricity Practice Solution" browser page to move to the front of their terminal sessions after closing out the attachment. Our users keep calling to tell us that they got kicked out, when in fact, their session was just hiding behind this extraneous page. Does anyone know where I could go from here?
Personally, I always end up closing that "Start Centricity Practice Solution" browser page as soon as the main application window loads after I login. Do your users keep it open for some reason, or is it actually relaunching the window?
Posted : December 3, 2012 1:16 am
Topic starter
When our users login via Terminal server, that window "hides" behind the application. Centricity opens when they log into the terminal server, they don't hit a desktop.
Posted : December 3, 2012 1:32 am
Topic starter
I just wanted to provide an update on my problem and how I solved it. I started messing around with tabbed browsing behavior, and was able to force the attachments to open up in a new window. I was able to make the change via local group policy on our remote desktop servers. The policies are located at Computer Configuration, Windows Components, Internet Explorer. One is called Turn off Tabbed Browsing, and the other is called Turn off configuration of Windows reuse. The second policy, you need to enable and choose from the dropdown "Open in a new Internet Explorer window." After doing this, the attachments all open up correctly without messing with the Start Centricity page.
Posted : December 12, 2012 11:56 pm
I just came across this thread as I was searching for a similar solution. Not sure that this will help anyone, but the changes mentioned below worked in CPS 12.0.13 and should work in both older and future versions of the product as the application launch is handled primarily by Windows.
Twerner mentioned in her post re adjusting the melsetvar.txt file value for _Browsermode from '0' (zero) to '1' to disable the built in wrapper Centricity uses for common files types (PDF's, HTTP(S) links and things of the like). We wanted something similar, but in our case didn't want to disable the "Centricity Practice Solutions Browser" all together. Our use case surrounded a PACS integration which sends messages to LinkLogic which are then imported as secure links into the patient chart.
We found that when trying to open these links through the Centricity wrapper that most functions and images did not load correctly. However when opened under Internet Explorer directly, everything behaved normally. We wanted to selectively use Internet Explorer for just these links as most of our users are comfortable with the streamlined look of the Centricity Browser.
After some testing, it turns out that if you add the following to the path of your attachment, Windows will try and open the file with it's default Internet Browser (which as of writing this will still be IE due to CPS launch requirements). Example below:
- Normal path to a PDF stored in Document Management
http://doc_mgmt/attachment.pdf - Adjusted path including the windows protocol
URL:http://doc_mgmt/attachment.pdf
The same should also work for web links if you'd like to open the full browser, which is what we did for the PACS.
How you make that adjustment to the path can be accomplished in a number of ways. For us we are using Mirth to sit between the sending PACS system and LinkLogic, the logic for updating that link is happening there. You could also go the SQL route, but that is less attractive for a perpetual solution. Depending on the sending party, they may also be able to edit what they are sending and save you the trouble of making any adjustments.
Hope this helps someone else in the future.
Posted : July 20, 2018 11:57 am
Page 2 / 2
Prev
