Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Remote Desktop Connection and Multiple Printers within CPS 10.1.3.300

General Discussion

Last Post by lic08 11 years ago

13 Posts

4 Users

0 Reactions

70 Views

RSS

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

Hello Everyone!

We are currently a hosted site using a Remote Desktop Connection to access CPS. Currently we have providers that have multiple printers in the office. One for handouts and the other solely dedicated to printing prescriptions. In one office in particular we are having an issue where the rx printer does not stick and both providers are needing to choose it every time. I am checking to see if someone has experienced this and if you have any possible solutions. Currently at the site and am going to try a few things to see if this will in fact stick for me, but any feedback would be greatly appreciated.

Thanks! Smile

Posted : April 9, 2013 1:02 am

glamontagne

(@glamontagne)

Posts: 89

Estimable Member

Hello, this is a very common problem. To get the printers to stick, you'll need to log into the terminal server as an administrator. Navigate to the emr.ini file. This is usually found in c:\Program Files x86\Centricity Practice Solution 10\Client. In that file, look for UseClientName=FALSE and change it to UseClientName=TRUE. Save the file and you should be able to set the printers to what you need them for. Hope this helps.

Best of luck,

Gary

Posted : April 9, 2013 1:21 am

Sirna

(@sirna)

Posts: 384

Honorable Member

Topic starter

Thank you for the feedback. Would this then keep the printers all the time if chosen from Select Printers within CPS?

Posted : April 9, 2013 1:25 am

glamontagne

(@glamontagne)

Posts: 89

Estimable Member

Yes, when you set up your printers through the select printers button in CPS, the settings should stick. Let me know how you make out.

Gary

Posted : April 9, 2013 1:36 am

joshua.tilson

(@joshua-tilson)

Posts: 130

Estimable Member

Just be aware that these printers will stay, but they are tied to the computer name inside the Centricity chart module.

This means that if you have people that share computers but use different printers will have issues with the "wrong" printer being printed to.

Also for us when a provider moves from site to site with the same laptop, they have to reset default printers every time, or Centricity will print to the wrong printers once again.

Posted : April 9, 2013 2:23 am

lic08

(@lic08)

Posts: 286

Reputable Member

how do you get around printer redirect? the Client name might be the same, but the printer redirect session id changes with every login.

Posted : June 12, 2013 1:15 am

joshua.tilson

(@joshua-tilson)

Posts: 130

Estimable Member

lic08 said:

how do you get around printer redirect? the Client name might be the same, but the printer redirect session id changes with every login.

See what Gary said in a previous post in this thread. Set ClientName= TRUE in the emr.ini file, that way the printers are assigned by client name and not session ID.

Posted : June 12, 2013 1:38 am

lic08

(@lic08)

Posts: 286

Reputable Member

Since i'm using easy print for terminal server, the printer name is "printername (redirect session id)". The session id changes so even though the clientname remains the same, the printer names alway changes.

Posted : June 12, 2013 5:43 am

joshua.tilson

(@joshua-tilson)

Posts: 130

Estimable Member

lic08 said:

Since i'm using easy print for terminal server, the printer name is "printername (redirect session id)". The session id changes so even though the clientname remains the same, the printer names alway changes.

I see how that could be a problem. Has it created any issues for you yet? We have printers installed on to terminal servers through a print server so we are not using print redirection, and it works reasonably well for us. I cannot however comment on how to deal with the EasyPrint redirection, sorry.

Posted : June 12, 2013 5:53 am

lic08

(@lic08)

Posts: 286

Reputable Member

is it complicated to manage different types of printers through terminal server? did you ever encountered any issues with printers that did not work properly or usb printers that connects directly to the client's pc? Thanks.

Posted : June 12, 2013 6:06 am

joshua.tilson

(@joshua-tilson)

Posts: 130

Estimable Member

It is relatively simple in theory, the way CPS handles printers makes things unnecessarily complicated.

For instance we install all the printers on our "print server" then from Terminal servers we go out and install a network printer from the print server. Then for each user we add that printer in their terminal services login.

So far so good. However now we have multiple remote locations sharing the same terminal servers and providers and other employees that travel from site to site. Now we have issues where Windows and CPS say they are printing in one location but the SQL table Printers says something else so we have lost print jobs or errors about being unable to access the printer.

So the trouble isn't with terminal services or managing the printers on them per se, but more with CPS.

That being said the only real problem we had was when we first upgraded to CPS 9.5 and Windows server 2008 R2.

HP Printers, ANY HP printers caused the Print Spooler service to crash and burn on the servers, this caused CPS to not load the chart module, which required a reboot of the terminal servers to fix. Microsoft has since released a few patches for printing in Server 2008 R2 and it does not happen AS often, and when it does we can typically restart the service instead of the server. However we still do not us HP printers or allow them on our Terminal Servers.

If you have any other questions feel free to let me know.

Posted : June 12, 2013 6:17 am

glamontagne

(@glamontagne)

Posts: 89

Estimable Member

We used to pass printers to the terminal servers using a print server like Josh. When we started having to print visit summaries for our patients at checkout, it would be deathly slow at our remote offices. What we found, was that installing the network printer as a local printer on the terminal server, would greatly speed up the printing for all the users.

Posted : June 12, 2013 6:21 am

lic08

(@lic08)

Posts: 286

Reputable Member

we have mostly HP printers 🙂

Posted : June 12, 2013 6:54 am

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed