Currently, we are working with desktops in our offices, and no computer in the patient exam room. What mobile computer would would you suggest? I have seen some old threads suggesting convertible tablets, but I am thinking that an ultrabook would be ideal (light, powerful).
The majority of Providers that have an opinion about screen size prefer at least a 15" machine. Once folks are in the bifocal demographic, the preference for screen size goes up. For price/performance, a solid alternative is a walk mounted desktop with the monitor and keyboard on a swivel tray.
We will need to run a few web based programs at the same time to interface with our lab and the hospital. I need to make sure that whatever we try has enough power to do the job quickly. Probably needs to be able to run dragon.
Not sure if I am miss-reading your mention of the interfaces, but those generally run on the server if there is an AC interface. If the interfaces are for individual users, then your network throughput and Internet provider performance will have the largest impact on the speed of the connection.
As far as Dragon, performance of the local machine is going to be key. We have had a few conversations around here about implementing Dragon - the short form - the more memory and processors the better.
Any thoughts?
We are a smallish practice, have 5 MD's, and three midlevels. Three physical locations. Equal number of MA's.
thanks
So, one of the challenges of having multiple Doctors and mid-levels practicing in multiple locations is having a central server, as well as backup servers in each location in the event of a connectivity outage. An alternative solution is a shared managed environment, with machines in each location that can serve as a backup server in the event of an outage, as well as a rolling disaster recovery and data resolution system. {disclosure - that is one of the services that we offer, so I know a bit about them]. The last bit is a mouthful, but that basically means having a plan so that each location can continue to practice, and then dealing with smoothing out the data after you outage is repaired.
You may find that different users are going to desire different implementations; that may also weigh on your final choices.
