From: Rob HYDE <b52bubba@verizon.net>
To: n95mask@lists.bufferbloat.net
Subject: [N95mask] SoClean NOT FDA approved and possibly harmful! per 2/27/2020
Date: Fri, 20 Mar 2020 13:29:55 -0400 [thread overview]
Message-ID: <4AE04EFE-C234-4D97-A452-A0043D331E7B@verizon.net> (raw)
In-Reply-To: <4AE04EFE-C234-4D97-A452-A0043D331E7B.ref@verizon.net>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Just found this, which is bad: https://www.fda.gov/news-events/press-announcements/fda-reminds-patients-devices-claiming-clean-disinfect-or-sanitize-cpap-machines-using-ozone-gas-or <https://www.fda.gov/news-events/press-announcements/fda-reminds-patients-devices-claiming-clean-disinfect-or-sanitize-cpap-machines-using-ozone-gas-or> It basically says that not only is a machine like the SoClean not FDA approved and illegally marketed, but that the ozone is dangerous.
😟
I had the same thought of using the SoCLean to clean respirators and talked to a bottom-line CSR this morning. Of course she said the “machine is not compatible with respirators,” as she would have to say for liability. She was unable to explain how it might ‘hurt the machine,” and that an engineer would need to explain that. I did ask her to send the idea/question up the chain, and emphasized ti could be very good for the company if it could be done. reuse-of-disposable-medical-masks-during-flu-pandemic-not-recommended-reusing-respirators-is-complicated <https://www.nationalacademies.org/news/2006/04/reuse-of-disposable-medical-masks-during-flu-pandemic-not-recommended-reusing-respirators-is-complicated>
PMC5432778 <https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5432778/> this research appears to be commercially sponsored (conflict of interest)
[-- Attachment #2: Type: text/html, Size: 5011 bytes --]
parent reply other threads:[~2020-03-20 17:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4AE04EFE-C234-4D97-A452-A0043D331E7B.ref@verizon.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE04EFE-C234-4D97-A452-A0043D331E7B@verizon.net \
--to=b52bubba@verizon.net \
--cc=n95mask@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox