Network - Female Barrier Methods - Volume 20 - Nº2 - 2000 - 03 - Network: New Devices May Be Easier to Use

Equipe Editorial Bibliomed

Diaphragms, sponges and cervical caps are evolving. Future versions of diaphragms and cervical caps should be easier to insert and remove, yet harder to dislodge during sexual intercourse. They will be made of silicone rubber, which has a longer shelf life than does latex rubber and is safe for users with latex allergy. Sponge development, in general, aims at reducing vaginal irritation by lowering spermicide doses.. . Diaphragms. . Studies involving some 2,800 U.S. women suggest that, during typical use, the diaphragm may be somewhat more effective than the contraceptive sponge or cervical cap.1 However, disadvantages of conventional diaphragms are that they must be fitted by a provider, are made of latex rubber, can be unwieldy to insert and remove, and should not be left in place for longer than 24 hours.. . Two diaphragm-like devices have been designed to resolve some of these problems: the Lea's Contraceptive and the SILCS intravaginal barrier (pronounced "silks"). Both come in one size; thus, clients need not be fitted for the devices. Both are made of silicone rubber, not latex.. . The Lea's Contraceptive, a cup-shaped barrier with a loop for removal, can be left in place for up to 48 hours. It also features a one-way valve to allow for the passage of cervical secretions and assure a tight fit. ...

Palavras chave: contraceptive, --, barrier, cervical, sponge, may, devices, use, latex, silcs, conrad, hours, has, rubber, diaphragm, silcs intravaginal barrier, latex rubber, intravaginal barrier, cervical caps, hours --,

Divulgação



conteúdos relacionados
Search_LibdocFree @SearchWordsAux='03 - Network: New Devices May Be Easier to Use contraceptive, --, barrier, cervical, sponge, may, devices, use, latex, silcs, conrad, hours, has, rubber, diaphragm, silcs intravaginal barrier, latex rubber, intravaginal barrier, cervical caps, hours --, ',@type='ARTICLE', @libdocidant=13233, @max_rows=10, @key_rank=0

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

Element RECORDCOUNT is undefined in GETRELACIONADOS.

 
The error occurred in D:\inetpub\wwwroot\Ehealth\Pdoc\inc\incContRelArtNot.cfm: line 9
7 :                     @max_rows=10, @key_rank=0
8 :                 </cfquery>
9 :                 <cfif getrelacionados.recordcount gt 0>
10 :                 <!-- notícias médicas -->
11 :                 <div class="box-conteudo">

Resources:

Browser   claudebot
Remote Address   3.233.232.21
Referrer   https://www.bibliomed.com.br/lib/ShowDoc.cfm?LibDocID=13233&ReturnCatID=11533&titulo=03-network-new-devices-may-be-easier-to-use.html
Date/Time   29-Mar-24 07:46 AM
Stack Trace
at cfincContRelArtNot2ecfm825854558.runPage(D:\inetpub\wwwroot\Ehealth\Pdoc\inc\incContRelArtNot.cfm:9) at cfshowDoc2ecfm2099003046.runPage(D:\inetpub\wwwroot\Ehealth\commondev\lib\showDoc.cfm:245)

coldfusion.runtime.UndefinedElementException: Element RECORDCOUNT is undefined in GETRELACIONADOS.
	at coldfusion.runtime.CfJspPage.resolveCanonicalName(CfJspPage.java:1724)
	at coldfusion.runtime.CfJspPage._resolve(CfJspPage.java:1620)
	at coldfusion.runtime.CfJspPage._resolveAndAutoscalarize(CfJspPage.java:1794)
	at coldfusion.runtime.CfJspPage._resolveAndAutoscalarize(CfJspPage.java:1787)
	at cfincContRelArtNot2ecfm825854558.runPage(D:\inetpub\wwwroot\Ehealth\Pdoc\inc\incContRelArtNot.cfm:9)
	at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:231)
	at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:416)
	at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2722)
	at cfshowDoc2ecfm2099003046.runPage(D:\inetpub\wwwroot\Ehealth\commondev\lib\showDoc.cfm:245)
	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.BrowserDebugFilter.invoke(BrowserDebugFilter.java:74)
	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)