<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Is Web-based/SaaS Software Right for Your Practice?</title>
	<atom:link href="http://www.softwareadvice.com/medical/is-software-as-a-service-right-for-your-practice/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwareadvice.com/medical/is-software-as-a-service-right-for-your-practice/</link>
	<description>Free advice on selecting medical software.</description>
	<pubDate>Thu, 24 Jul 2008 17:31:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Don Fornes</title>
		<link>http://www.softwareadvice.com/medical/is-software-as-a-service-right-for-your-practice/#comment-321</link>
		<dc:creator>Don Fornes</dc:creator>
		<pubDate>Thu, 17 Jul 2008 16:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/medical/?p=3#comment-321</guid>
		<description>@tn26: That is a good question and one we hear a lot. It's bad news when a software vendor goes out of business, regardless of whether the product is SaaS or traditional on-premise software. 

In the case of SaaS, it is important that you verify what contingency plans a SaaS vendor guarantees in their subscription agreement. The vendor should provide a straightforward data export capability so that you can export your data at any time. Given that almost every system is built on standard relational databases, this is not a difficult facility to provide. The vendor should also have an arrangement with their data center that ensures that the system remains up and running for a period of time after they close their business. That way, customers will have adequate opportunity to export their data and work with a new vendor to get back up and running.

Vendor failure is a very difficult situation, but we believe that the challenge is the same regardless of whether your system is SaaS or on-premise.</description>
		<content:encoded><![CDATA[<p>@tn26: That is a good question and one we hear a lot. It&#8217;s bad news when a software vendor goes out of business, regardless of whether the product is SaaS or traditional on-premise software. </p>
<p>In the case of SaaS, it is important that you verify what contingency plans a SaaS vendor guarantees in their subscription agreement. The vendor should provide a straightforward data export capability so that you can export your data at any time. Given that almost every system is built on standard relational databases, this is not a difficult facility to provide. The vendor should also have an arrangement with their data center that ensures that the system remains up and running for a period of time after they close their business. That way, customers will have adequate opportunity to export their data and work with a new vendor to get back up and running.</p>
<p>Vendor failure is a very difficult situation, but we believe that the challenge is the same regardless of whether your system is SaaS or on-premise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tn26</title>
		<link>http://www.softwareadvice.com/medical/is-software-as-a-service-right-for-your-practice/#comment-314</link>
		<dc:creator>tn26</dc:creator>
		<pubDate>Thu, 17 Jul 2008 05:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/medical/?p=3#comment-314</guid>
		<description>What if the vendor goes out of business?  What will happen to your patients' data?</description>
		<content:encoded><![CDATA[<p>What if the vendor goes out of business?  What will happen to your patients&#8217; data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvia</title>
		<link>http://www.softwareadvice.com/medical/is-software-as-a-service-right-for-your-practice/#comment-167</link>
		<dc:creator>Sylvia</dc:creator>
		<pubDate>Sun, 22 Jun 2008 23:14:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareadvice.com/medical/?p=3#comment-167</guid>
		<description>One question about long-term pricing parity.  It seems like there would also be money saved in lower IT maintenance costs with a SaaS. For example, not having to maintain servers, etc. Are SaaS fees still about the same long term as having a client/server system when you factor in IT costs? 


Also who actually stores the data when using a SaaS?  Are there additional data integrity issues?</description>
		<content:encoded><![CDATA[<p>One question about long-term pricing parity.  It seems like there would also be money saved in lower IT maintenance costs with a SaaS. For example, not having to maintain servers, etc. Are SaaS fees still about the same long term as having a client/server system when you factor in IT costs? </p>
<p>Also who actually stores the data when using a SaaS?  Are there additional data integrity issues?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
