Home Forums Discussions Feedback and Recommendations Multiple Offices

Sandeep, you have a good sense of humor. Certainly needed for this business. Thanks for the explanation. This is a compliment.

OUCH ...It felt like a GERD attack!!!

Yeah, but we like to have fun on the board sometimes. I'll send you over some Zantac.

No nedd to send any Zantac, we do get free samples!!!

I have used LogMeIn with AC. It is quite slow on our T1 line from hospital to my office computer. Is that a function on the T1 line? How fast is Remote Desktop?

I'd check your network performance to an external https connection. Not surprisingly, I have found that hospitals have more significant performance issues once the traffic goes across the edge of their network. In simple terms, as your traffic leaves the local location there is significant slow-down, generally due to security [firewalls, intrusion detection, data protection, traffic shaping, generalized packet inspection].

If you are in a 4G/LTE market, you may get significantly better performance using your laptop across your phone's data connection.

Lindsay,

A T1 is 1.54Mbs down and up. It has the advantage of that it is always that speed, e.g. unlike cable it isn't shared with others. It is also more secure.

As to your question on RDP, it is faster in that it is quicker to start, although LogMeIn ignition makes that a tie. It is probably a slight bit faster, but you should be getting rather good speeds with LMI on a T1. Go to www.dslreports.com and test your speed.

Bert- I hadn't tried LogMeIn from the hospital to my Family Practice office in several months. I just tried it again tonight, and it's quite fast now-no noticeable delay. Maybe I am bypassing the VPN/T1 and using DSL? I think the hospital recently upgraded the VPN from fractional T1 to full T1. I'll talk to the IT folks. I can see how it would work for an organization like our small hospital to use Remote Desktop Protocol - having one central server serving multiple offices. Anyone currently doing this with AC? Any concerns about having 3 different offices, multiple specialties all owned by one hospital having access to altering a shared chart?

It would have to be an awfully small hospital to use DSL. I would imagine they would use T1 or even T3. And, I doubt they would allow you to bypass their secure network.

You are asking an awfully big question. The only way to share one database would be if all the patients were patients of one group. I don't see how that would be possible if GI or Neuro were sharing the same database. There would be HIPAA problems for sure. Maybe I am misunderstanding your question. As far as the logistics, having a terminal server at the central office to access the AC databases on the application/file server would work using RDP.

Bert: You understand correctly about sharing a database. Our hospital/employer owns our remote FP group (4 providers) 8 miles from the hospital campus, a gen surgeon/GI/ortho in 1 group on campus, and 2 FP's in a group on campus. In May they tried to implement a crappy (as in Fortran) underdeveloped EMR (CPSI)for all docs using a single database. I have the same privacy concerns, plus concerns about data corruption. All the docs are under 1 umbrella, like a group practice without walls, but it is not presented to the public like one practice. The EMR rollout was a disaster - everyone hated it except administration, and they backed off-we stopped using the EMR, but are trying to bring it back in order to recoup the money they invested in this piece of crap by planning to get Meaningful Misuse funds. I am the only one using Amazing Charts, and all the staff and docs in my group want AC.

Then the answer is simple. You have already taken the lead here.expand your EMR to include your group, then show administration your result with every intention of using AC no matter their take on it.

Bert: Right on! Occupy our office! Watch out for the pepper spray.