A hospital is leveraging a third-party-hosted, SaaS-based EMRS for all its regional locations. The EMRS will consolidate all existent stand-alone regional systems. All regional systems managers are co

The solution is SaaS-based, meaning the hospital does not control or choose the underlying IaaS provider; therefore, designing it to run on a popular IaaS provider is not within the architect's scope for a SaaS product.

Analyzing business requirements and communicating the use of dual service providers directly addresses availability concerns by demonstrating a strategy for high resilience and redundancy. Leveraging multiple service providers or ensuring the primary SaaS provider itself uses a multi-region or multi-vendor strategy significantly reduces the risk of a single point of failure impacting the EMRS availability.

Deploying client-to-site VPNs ensures secure connectivity to the SaaS application but does not directly enhance the availability of the SaaS service itself if the provider experiences an outage.

Deploying a SaaS EMRS within the hospital's headquarters contradicts the definition of SaaS, which is a service hosted and managed by a third-party provider, not by the customer on-premises.