3 ms·

>Even better if it targeted a domain-specific, stripped-down, locked-down Linux distro that could be netbooted by thin clients around the practice and deployed

>Even better if it targeted a domain-specific, stripped-down, locked-down Linux distro that could be netbooted by thin clients around the practice and deployed in a high-availability setup inside the firewall. I can hear it now... "This looks great, but my staff only knows about how to use Windows computers; I'll have to retrain them to use these strange new Lee-nuks things. Can't you just make this run in a little box like on the other guys' systems, so I can keep my Windows PC workstations? I'd like that because our time-clock software is only available for Windows and that will save us having to keep two CPUs and screens on the desks."

superuser2 12y ago
Maybe because it was their first (and only) EMR system, but in the practice I worked at, all the initial infrastructure was put in by Allscripts explicitly for EMR, with all other applications being secondary. They sold the boxes, set up the Windows domain, and managed everything. Only relatively recently did they start using it as their own infrastructure, instead of just the magic to make Allscripts EHR work. In that kind of scenario, it could just as easily have been Linux.
- fnordfnordfnord 12y ago
  > In that kind of scenario, it could just as easily have been Linux. In any of these systems, any general purpose OS would suffice. There is no real problem for people to move from one platform to another that can't be overcome in a short time.