Member Login:   Email: Password: 



The key to any successful hospital-acquired infection (HAI) prevention program is compliance. With new patient safety initiatives and CMS mandates, compliance is even more critical to ensuring positive outcomes.

The Compliance Alliance Program can help your facility comply with CDC Guidelines and an evidence-based protocol. It gives nursing leaders a simple, fun way to empower fellow clinicians to help eliminate HAIs. The program is easy to manage and can help your facility achieve up to 90% or greater compliance.

Should your unit/facility accept this mission, the following criteria must be met in your quest to help eliminate HAIs. Remember, your Sage Products representative will be there to help you along the way.

Each unit will:

  1. Appoint an agreed upon number of Compliance Alliance team members.
  2. Measure staff compliance to the protocol.
  3. Measure HAI rates in conjunction with compliance.
  4. Compare units' compliance rates to promote healthy competition.
  5. Celebrate success when the HAI target reduction goal is reached.

Each team member will be asked to complete the following duties each week:

  • Make sure appropriate Sage Products are in patient rooms and properly set up.
  • Verify products are being used in accordance with your protocol. If not, ask why.
  • Communicate the link between compliance and HAI prevention to fellow clinicians.
  • Continue to educate and enforce compliance to your protocol.
  • Work with your Sage Products representative to measure protocol compliance.
  • Have fun and CELEBRATE SUCCESS!!

Implement the Compliance Alliance Program at your facility today!

For a printable program information sheet (.pdf), click here.


 

Error Occurred While Processing Request The web site you are accessing has experienced an unexpected error.
Please contact the website administrator.

The following information is meant for the website developer for debugging purposes.
Error Occurred While Processing Request

Could not find the included template ../complianceFooter.htm.

Note: If you wish to use an absolute template path (for example, template="/mypath/index.cfm") with CFINCLUDE, you must create a mapping for the path using the ColdFusion Administrator. Or, you can use per-application settings to specify mappings specific to this application by specifying a mappings struct to THIS.mappings in Application.cfc.
Using relative paths (for example, template="index.cfm" or template="../index.cfm") does not require the creation of any special mappings. It is therefore recommended that you use relative paths with CFINCLUDE whenever possible.
 
The error occurred in D:\inetpub\wwwroot\sageproducts2\complianceAlliance\index.cfm: line 75
 
73 : 	</tr>
74 : </table>
75 : <cfinclude template="../complianceFooter.htm">
76 : 
77 :
Resources:

Browser   CCBot/1.0 (+http://www.commoncrawl.org/bot.html)
Remote Address   38.107.179.229
Referrer  
Date/Time   04-Feb-12 01:40 AM
Stack Trace
at cfindex2ecfm1959583476.runPage(D:\inetpub\wwwroot\sageproducts2\complianceAlliance\index.cfm:75) 

coldfusion.tagext.lang.IncludeTag$NoSuchIncludeTemplateException: Could not find the included template ../complianceFooter.htm.
	at coldfusion.tagext.lang.IncludeTag.setTemplate(IncludeTag.java:349)
	at cfindex2ecfm1959583476.runPage(D:\inetpub\wwwroot\sageproducts2\complianceAlliance\index.cfm:75)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:231)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:416)
	at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
	at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:363)
	at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
	at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
	at coldfusion.filter.PathFilter.invoke(PathFilter.java:87)
	at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
	at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
	at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
	at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
	at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
	at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
	at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:53)
	at coldfusion.CfmServlet.service(CfmServlet.java:200)
	at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
	at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
	at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
	at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
	at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
	at jrun.servlet.FilterChain.service(FilterChain.java:101)
	at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
	at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
	at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
	at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
	at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
	at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
	at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
	at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
	at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)