Hang on a little longer!
Tell us about your challenges, and we’ll come up with a viable solution!
On-premises | In the cloud | |
Deployment | The solution is deployed in house | Resources are hosted by the cloud provider |
Control | The user is in control of everything | Depends on the selected service model. With software-as-a-service, the cloud vendor is in control. With Infrastructure-as-a-service, the user is mostly in control |
Security | The user is responsible for securing their data | The cloud vendor hires highly qualified security experts. They offer disaster recovery, backups, encryption, protection against cyberattacks, etc. |
Compliance | The user is responsible for compliance | The user needs to search for a compliant cloud vendor, but if a breach occurs, the user still pays the price |
Costs | High. Infrastructure is acquired by the user, who also pays for maintenance and licensing independently of the usage capacity | Relatively low. The user only pays for the resources consumed. No maintenance costs. No need to purchase and set up infrastructure |
Deployment speed | Slow. Hardware and software need to be acquired and installed locally | Fast. Cloud-based software is deployed over the internet in a matter of days or even hours |
Scalability | The user will need to purchase additional HW/SW components | Highly scalable. Resource availability is adjusted to clients’ needs and can be scaled up or down on demand |
IT department capabilities | Strong IT department is required to handle installation, maintenance, security, etc. | Depends on the deployment model. With the public cloud, the user’s IT department does not interfere much. With other models, its up to the user to decide on its degree of involvement |
Maintenance | The user is responsible for maintenance | Cloud vendor is responsible for maintenance, backups, and disaster recovery |
Connectivity | The user doesn’t rely on internet connectivity | The user needs a reliable internet connection to reach the cloud |
What it offers | Best suited for | Cloud vendor controls | Healthcare organization controls | Most common applications | |
---|---|---|---|---|---|
Software as a Service (SaaS) | All the healthcare data is hosted in the cloud and can be accessed through a web browser | Small healthcare organizations with limited IT budget and capacity | Servers Storage OS Applications Data Middleware Runtime | - | Email servers CRM systems Document editors Medical practice management systems Health information exchange |
Platform as a Service (PaaS) | Provides an environment for organizations to deploy their existing applications and supports custom application development. With PaaS, users access their data through a custom app instead of a web browser (as it is in SaaS). | Mid-size to large healthcare organizations that can build cloud-based custom solutions in house or hire external IT talent | Servers Storage OS Middleware Runtime | Applications Data | Connected devices |
Infrastructure as a Service (IaaS) | Offers storage and computing resources, such as physical servers and virtual machines, and grants users extensive control over all this infrastructure | Large organizations with dedicated technical IT teams | Servers Storage | Applications Data OS Middleware Runtime | Implementing complex EHR solutions |