The invention relates to cleaning and sanitizing practices at a hospital or other healthcare facility.
Despite improvements in hand hygiene, stricter compliance requirements, and efforts to optimize isolation practices, hospitals and other healthcare facilities are losing the war on nosocomial or Hospital Acquired Infections (HAIs). A hospital acquired infection is an infection acquired in a hospital or other healthcare facility by a patient admitted for some reason other than that specific infection. Hospital acquired infections may include infections appearing 48 hours or more after hospital admission or within 30 days after discharge. They may also include infections due to transmission from colonized healthcare workers, or occupational exposure to infection among staff of the facility. Although the majority of hospital acquired infections are preventable, sadly their incidence has only increased.
Hospital acquired infections have become more rampant as antibiotic resistance spreads. Many factors contribute to the increased incidence of hospital acquired infections among hospital patients. For example, hospitals house large numbers of people who are sick and therefore have weakened immune systems. Medical staff move from patient to patient and see many patients a day, providing a way for pathogens to spread. Research indicates that hand hygiene practices are followed only 40% of the time by healthcare workers, even after exhaustive process improvements and training efforts. Many medical procedures, such as surgery, injections and other invasive procedures bypass the body's natural protective barriers, providing entry points for pathogens. The wide-spread use of antibiotics has contributed to the emergence of resistant strains of microorganisms in healthcare facilities and well as in the community.
Nearly ¾ of surfaces in patient rooms are contaminated even after housekeeping has been completed. Many high touch objects in the patient room, such as doorknobs, bedrails, telephone, etc. are continuously re-contaminated. Patients and healthcare workers are thus exposed to many sources for potential pathogen transmission within a hospital room.
In addition, between 70% and 90% of incoming patients carrying Methicillin-Resistant Staphylococcus aureus (MRSA) or Vanocomycin-Resistant Enterococci (VRE) are never identified and isolated. Many hospitals are unaware that MRSA lingers on patient room surfaces long after the colonized patient is discharged. Doctors and nurses carry MRSA on their lab coats and uniforms 65% of the time, potentially passing this organism to other patients or the environment.
It has been estimated that 1 out of every 20 patients contract hospital acquired infections. This translates to nearly 2,000,000 patients each year. By 1995, deaths from documented hospital acquired infections had escalated to almost 90,000 per year for an average of 345 per hospital. The costs associated with hospital acquired infections are significant. The cost to treat hospital acquired infections has been estimated to reach $30 to $50 billion per year. The average additional hospital costs for a patient contracting a hospital acquired infection is $15,275.
Although certain individuals, such as the critically ill, the elderly, young children and those with compromised immune systems are at greater risk, no patient is immune from the risk of acquiring an infection during a doctor visit or hospital stay.
In general, the invention relates to a comprehensive and systematic approach to cleaning and sanitizing practices at a hospital or other healthcare facility.
In one embodiment, the invention is direct to a system comprising a server computer that receives collected data from a healthcare facility, the collected data based on monitored validation points within a plurality of validation processes for the healthcare facility, a database coupled to the server computer that stores the collected data from the healthcare facility in association with hospital data that uniquely identifies the healthcare facility; the database further storing module data that defines modules within the healthcare facility and process map data that defines at least one validation process for each module within the healthcare facility, an analysis application resident on the server computer that analyzes the collected data and generates therefrom validation data indicative of cleanliness of the one or more healthcare facilities, and a reporting application resident on the server computer that generates reports that characterize the cleanliness of the healthcare facility based on the collected data, the validation data, the hospital data and the module data.
In another embodiment, the invention is directed to a method comprising identifying contamination vectors of hospital acquired infections within a healthcare facility, defining a plurality of modules within the healthcare facility, each module associated with a physical area within the healthcare facility or with a function performed within the healthcare facility, associating each of the plurality of modules with a different one of a plurality of cleaning process maps, monitoring validation points specified in one or more of the cleaning process maps, and verifying whether process parameters associated with each monitored validation point are satisfied.
The method may further include defining one or more of a patient room module, a critical care area module, a central sterile processing module, an operating room module, an emergency room module, a physical therapy module, a food service module, a public bathroom module, a procedure room module or a laundry area module. The method may further include defining one or more of a patient skincare module, a wound cleansing module, or a hand hygiene module. The method may further include correlating each of the plurality of modules with one or more of the contamination vectors. The method may further include generating one of the plurality of cleaning process maps based on the associated module and the contamination vectors correlated with the associated module. The method may further include training staff of the healthcare facility regarding the cleaning process maps. The method may further include re-training staff of the healthcare facility when the whether process parameters associated with certain of the monitored validation point are not satisfied. The method may further include generating validation data based on whether the process parameters associated with each monitored validation point are satisfied. The method may further include generating reports based on the validation data. In another embodiment, the invention is directed to a computer-readable medium comprising instructions that upon execution in a computer of a validated hospital cleaning processing system cause the computer to receive collected data from a healthcare facility, the collected data based on monitored validation points within a plurality of validation processes for the healthcare facility, store the collected data from the healthcare facility in association with hospital data that uniquely identifies the healthcare facility, store module data that defines modules within the healthcare facility, store process map data that defines at least one validation process for each module within the healthcare facility, analyze the collected data with respect to the process map data and generate therefrom validation data indicative of cleanliness of the one or more healthcare facilities, and generate at least one report that characterizes the cleanliness of the healthcare facility based on the collected data, the validation data, the hospital data and the module data.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features and advantages of the invention will be apparent from the description and drawings, and from the claims.
In general, the invention relates to comprehensive and systematic approach to cleaning and sanitizing practices at a hospital or other healthcare facility. A validated hospital cleaning process identifies hospital vectors of contamination; that is, possible sources through which hospital acquired infections (HAIs) may be spread. The validated process defines a plurality of modules within a hospital or other healthcare facility, each having an associated cleaning process map designed to meet the particular cleaning and/or sanitizing needs and challenges faced by that module. The cleaning process map for each module may be based, for example, on scientifically validated best practices of clearly defined cleaning processes. Various stages of the cleaning process map include validation points, at which certain parameters designed to ensure proper cleaning and/or sanitizing of the module are verified.
The validated hospital cleaning process may address clinical and cleaning procedures across many fronts within the hospital. The validated process may include some or all of the following: objective assessments, audits and measures; data collection, hazard analysis and critical control point identification; efficient and effective processes and protocols; training and interventions that change behaviors; consistent, automated and invisible monitoring; innovative products and technologies; clinical experts and personalized support services; quality assurance practices; implementation of best practices; and cleaning through clinical improvements that may reduce the incidence of HAIs.
The vector wheel also illustrates the contamination vectors within a hospital or other healthcare facility that may be identified by the validated process of the present invention. The contamination vectors are represented as “slices” on the vector wheel and may include, in no particular order:
Different areas of the hospital may require different levels of cleaning and/or sanitization. These may be classified, for example, as “clinical” and “clean.” The vector wheel of
Other areas on the vector wheel of
The data received from hospitals 22A-22N, as well as other data associated with the operation of the validated hospital cleaning system, may be stored on a database 40. Database 40 may store, for example, hospital data 42A-42N associated with each of the hospitals 22A-22N, respectively; module data 43A-43N associated with each of the hospitals 22A-22N, respectively; process map data 43A-43N associated with each of the hospitals 22A-22N, respectively; user data 43A-43N associated with each of the hospitals 22A-22N, respectively; storage data 43A-43N associated with each of the hospitals 22A-22N, respectively; validation data 43A-43N associated with each of the hospitals 22A-22N, respectively; and collected data 43A-43N associated with each of the hospitals 22A-22N, respectively.
Hospital data 41A-41N may include data that uniquely identifies or is associated with the respective hospital or other healthcare facility 22A-22N. As such, hospital data 41A-41N may include, for example, hospital identification information, employee information, date and time stamps, caregiver identification, visitor identification and additional information relating to other aspects of the corporation or operation and other information specific to each individual hospital 22A-22N.
Module data 42A-42N may include, for example, module identification information for each module in the respective hospital 22A-22N. Modules may be physical modules associated with physical areas of hospital or may be functional modules associated with functions carried out within a hospital. Physical modules may include, for example, patient rooms, critical care areas, central sterile processing, operating rooms, food service, bathrooms, laundry rooms, floors, etc. Functional modules may include, for example, patient skincare, wound cleansing, hand hygiene, etc. Because each hospital or healthcare facility may perform different functions and have different physical areas within the healthcare facility, module data 42A-42N may be specific to the respective healthcare facility 22A-22N.
Process map data 43A-43N may include, for example, information that addresses the cleaning and/or sanitizing requirements for each module within the respective hospital 22A-22N. User data 44A-44N may include, for example, information concerning those persons or entities authorized to access the reports generated by the validated hospital cleaning system for the respective hospital 22A-22N. Storage data 45A-45N may include, for example, information that addresses proper storage and validation processes for the equipment, tools, cleaning and/or sanitizing products associated with each module for the respective hospital 22A-22N. Collected data 46A-46N may include, for example, any data collected at the respective hospital 22A-22N relevant to the validated hospital cleaning system. Collected data 46A-46N may also include baseline data corresponding to the status of monitored validation points before implementation of the validated hospital cleaning system/method. Validation data 48A-48N may include, for example, the results of any analysis of collected data 46A-46N received from the respective hospital 22A-22N.
Server computer 30 includes an analysis application 32 that analyzes the collected data 46A-46N received from each of hospitals 22A-22N and stores the results for each hospital 22A-22N as validation data 48A-48N, respectively. A reporting application 34 generates a variety of reports that present the validation data generated by analysis application 34. Reporting application 34 may generate a variety of reports to provide users with both qualitative and quantitative data regarding the cleanliness of their hospital, and/or to compare data over time to determine whether improvement has occurred. Reporting application 34 may also users to benchmark multiple hospitals or other healthcare facilities. It may also be an assessment tool that is used post cleaning to assess the effectiveness of the use of the validated cleaning system/process and to determine whether the proper procedures are being followed.
Reports 49A-49N may be stored in database 40. Examples of the reports that may be generated by reporting application 34 are described with respect to
In one embodiment, local hospital database 24 may store all of the data types described above with respect to database 40 associated with that particular hospital 22. Hospital server computer 28 (or other local computer) may also include local analysis and reporting applications such as those described above with respect to analysis and reporting applications 32 and 34. In that case, reports associated with that particular hospital may be generated and viewed locally, if desired. In another embodiment, all analysis and reporting functions are carried out remotely at server computer 30, and reports are viewed remotely over network 52, such as the internet. In other embodiments, some hospitals 22 may include local storage and/or analysis and reporting functions while other hospitals 22 rely on remote storage and/or analysis and reporting. Thus, although the general case of data being stored at the server database 40 and analysis/reporting being carried out by the server computer 30 is described herein, it shall be understood that these storage, analysis and reporting functions may also be carried out locally or at some other location, and that the invention is not limited in this respect.
Each module 124A-124N is associated with a cleaning process map 126A-126N, respectively. The associated cleaning process map 126A-126N addresses the contamination vectors (
Each cleaning process map 126A-126N addresses the cleaning and/or sanitizing requirements of the associated module. For example, the patient room cleaning process map may include processes for stocking the patient room cleaning station, how cleaning personnel are notified of patient discharge, preparation of room for cleaning, removal of garbage, removal of linen, cleaning of bathroom, cleaning of the patient room, floor cleaning, and restocking of cleaning station, etc. The process map(s) associated with other module(s) within the hospital will include processes unique to that module aimed toward proper cleaning and/or sanitization practices and consideration of the relevant contamination vectors within that module.
Each cleaning process map 126A-126N lists all components and steps in the cleaning process. Validation points are inserted at certain identified process steps in the process flow map for each module. The validation points are inserted for identified process steps which, if not performed properly, there is a potential increased incidence of an unclean room or HAI infection risk.
As is also shown in
The validation processes 130A-130N refer to processes carried out at specified critical control points during the cleaning process, herein referred to as validation points. These validation points are identified points during the cleaning process at which certain parameters that may ensure proper cleaning and/or sanitizing of the module are verified.
For example, the validation processes for the patient room module may include verifying that a dispensed disinfectant solution contains the proper concentration of active ingredient, verifying that certain hard surfaces are contacted with a disinfectant impregnated cloth for a predetermined period of time, use of waterless sanitizer during hand washing, washing of hands both pre- and post-room cleaning, station cleaning, etc. The validation process map(s) associated with other module(s) within the hospital will include validation processes unique to that module aimed toward proper cleaning and/or sanitization practices within that module.
The validation processes for each module may be developed using the following considerations. Proper cleaning requires effective products and practices, training and monitoring. Effective disinfection and sterilization requires proper cleaning and storing, effective products and practices, training, compliance and monitoring. Clinical solutions require proper cleaning, effective disinfection and sterilization, innovative products and technology, process improvements, data analysis, training, compliance and monitoring. Depending upon the module and the vectors affecting that module, any number of these considerations may affect the resulting validation process.
The process flow map also includes monitoring procedures 136 which may be used to verify that the parameters are satisfied. These monitoring procedures 136 may include a definition of one or more of the following:
For example, the monitoring procedures for the validation point when disinfectant is dispensed may include regular dispenser validations and laboratory dispenser reliability testing to ensure that the concentration of active ingredient within the disinfectant falls within certain limits, laboratory testing on microfiber or other cleaning cloths to ensure that proper disinfectant concentration is delivered to the relevant surfaces (in other words, ensuring that the cloths do not absorb too much of the disinfectant), use of color coded cloths, carts with designated “clean” and “dirty” areas, and single use mops to eliminate cross contamination.
The results of the monitoring procedure(s) 136 are referred to herein as collected data. The collected data may be stored on the local hospital database 24 (see
As is further shown in
The results of the validation procedure is referred to herein as validation data. The validation data may be stored on the local hospital database for those installations where the local hospital server or other local hospital computer includes a local analysis application. Validation data 48A-48N for each hospital 22A-22N may also be stored on the server database 40 (see
If the analysis application 32 validation procedure indicates that the validation parameters were not satisfied, the validation process flow map may include a corrective action process 142. Corrective action 142 may include equipment troubleshooting, retraining of personnel in proper cleaning/sanitizing procedures, etc.
The validated hospital cleaning system/process may analyze the hospital data 41A-41N, module data 42A-42N, process map data 43A-43N, user data 44A-44N, storage data 45A-45N, collected data 46A-46N, and validation data 48A-48N either alone or in combination with each other to characterize cleanliness of the hospital or healthcare facility 22A-22N. The validated hospital cleaning system/process may also generate reports 49A-49N that present the data in various formats and present the analysis for review by a site manager, corporate or government entity or other body responsible for oversight of the healthcare facility or of the validated hospital cleaning process.
The dust pan may be prepped with a new dust bag. Personal protective equipment (PPE), such as gloves, masks, eye-protection, gowns, etc. is stocked onto the cleaning station. The appropriate cleaning solutions are dispensed and measured. Cloths and mops are saturated with cleaning solution. A room cleaning checklist and/or schedule may be mounted onto the cleaning station. The room cleaning checklist may include a list of what to clean and what to inspect during the patient room cleaning process. A textile inventory control plan may also be in place to keep track of textiles (sheets, towels, gowns, etc.) going into or out of the patient room.
The portion of the patient room validation process shown in
At main step “Notification of Patient Discharge” (160) includes some type of notice to cleaning personnel that a patient has been discharged. If the room is to be cleaned before a patient is discharged, this step may be skipped. The cleaning station is then transported to the patient room for cleaning (162).
The “Clean Bathroom” process step (182) may also include cleaning/wiping of the outside and/or inside of the bathroom trash can. The toilet may be flushed, or, in the alternative, the toilet may be left unflushed, thus leaving the colored water produced by the toilet cleaner present in the bowl as a visual indicator that the toilet has been cleaned. After cleaning the bathroom, the cloth used to clean the mirrors, etc. is placed in the dirty cloth bag. The toilet caddy/brush is returned to its storage spot on the cleaning station. The paper towel from the cleaning the mirror, etc. is placed in the trash. A notification that the bathroom was cleaned, such as colored water in the toilet bowl, wrap on toilet seat, etc. may also be included.
In addition, to the validation points (183A-183D) shown in
The “Clean Bathroom” process step (180) thus includes cleaning/wiping of some or all of a plurality of high touch points (HTP) (also referred to herein as high touch objects (HTO)). The high touch points for a bathroom may include, for example, the bathroom light switch, bathroom door knob, sink, toilet top, toilet handle, toilet hand hold/rails, bed pan cleaner, and/or any other physical item or area in a patient bathroom that may be frequently re-contaminated.
The “Clean Patient Room” process step (patient in room) may also include cleaning/wiping of some or all of a plurality of high touch points (HTP). The high touch points may include, for example, the light switch, door knob, telephone, TV, call box, tray table, bedside table, bedrails, and/or any other physical item or area in a patient room that may be frequently re-contaminated. The “Clean Patient Room” process step (patient in room) may also include wiping of all furniture including stools, tables, chairs, counters, etc.
Validation point(s) (191A-191C) occur during the “Clean Patient Room” process step. Here, validation of various cleaning procedures parameters to ensure that the patient room is properly cleaned and sanitized are monitored. For example, the validation point(s) (191A-191C) may require that all relevant surfaces are contacted with a disinfectant impregnated cloth and remain wet for at least 10 minutes with disinfectant. Monitoring may be accomplished via visual inspection of how long surfaces remain wet, photo- or chemiluminescent indicators, adenosine triphosphate (ATP), culture, etc., to ensure that proper cleaning/sanitizing procedures were adequately performed.
The “Clean Patient Room” process step (patient in room) may also include placing the used cloth(s) to the used cloth bag, getting trash bags from the cleaning station, installing new can liners (infectious waste can, used linen can, trash can, etc.), restocking room linens and other room supplies as needed, and other process steps necessary to prepare the room for another patient. Cloths for different areas or modules may be color coded, e.g., yellow cloths for bathroom, blue cloths for the patient room, etc., to reduce cross contamination between areas or modules.
The “Clean Patient Room” process may also include a notification that the patient room has been cleaned, such as a note card, hallway sign, swing out, etc. (194).
Validation point (211A) occurs when the cleaning station is wiped down with disinfectant. Here, validation of various cleaning procedures parameters to ensure that the patient room is properly cleaned and sanitized are monitored. For example, the validation point (211A) may require that all relevant surfaces of the cleaning station have been contacted with a disinfectant impregnated cloth and remain wet for at least 10 minutes (or other appropriate time corresponding with the disinfecting time of the product) with disinfectant. Monitoring may be accomplished via visual inspection of how long surfaces remain wet, photo- or chemiluminescent indicators, adenosine triphosphate (ATP), culture, etc., to ensure that proper cleaning/sanitizing procedures on the cleaning station were adequately performed.
Validation point(s) (211B-211C) occurs at the laundry site, where monitoring and validation of proper laundry procedures are performed to ensure proper handling/cleaning/disinfecting of laundry articles. Different laundry articles, such as cleaning cloths, bed linens, towels, gowns, etc., may have different laundry validation procedures.
Process 300 includes various testing methods that may be used to evaluate the effectiveness of the room cleaning. The testing may be performed both before and after the patient's room has been cleaned. Process 300 begins with identification of the particular high touch object involved (302). For example, high touch objects for the patient room module may include the sink, the toilet handle, the toilet seat, the bed pan cleaner, the toilet hand hold/rail, the bathroom door handle, the bed rail, the call button, the tray table, the bedside table, the telephone, and the room door knob.
One such test may include application of an indicator, such as a photoluminescent or chemiluminescent indicator, which is applied to a defined location on the high touch point prior to cleaning (304). Inspection of the indicator post cleaning may be used to determine whether the high touch object has been cleaned. In the patient room module, for example, the indicator would be applied in a well-defined manner to each of the high touch objects that are defined for that module. After completion of the cleaning procedure (310), the surface may be inspected with a black light to determine if the indicator was disturbed by the cleaning process (312). Training would be provided to hospital personnel on what constitutes a “passing” or “failing” result. For example, passing results may include complete removal of the indicator or disturbance of a circular swirl pattern. Failing results may include an untouched indicator and/or no evidence of wiping.
Another test may include examination of culture counts as an indication of cleaning effectiveness. A surface sample of aerobic culture counts are collected at defined locations on the surface of the high touch object before (306) and after (314) completion of the cleaning process. Presence of aerobic bacteria may be used to quantify cleaning effectiveness. Threshold levels for “passing” or “failing” aerobic culture counts may be set, or the total aerobic culture count may be stored and reported.
Another test may include examination of adenosine triphosphate (ATP) levels as indication of cleaning effectiveness. Defined locations on the surface of the high touch object are swabbed before (308) and after (316) completion of the cleaning procedure (310). Presence of ATP correlates with presence of microorganisms, and thus may be used to quantify cleaning effectiveness. Threshold levels for “passing” or “failing” ATP levels may be set, or the total ATP level may be stored and reported.
Training/certification may be provided to the relevant personnel to help ensure that the methodologies of the validated hospital cleaning method are followed. Consistent application by trained personnel of the methodologies described herein helps to increase accuracy and reliability of the validated hospital cleaning methods. For example, detailed instructions concerning application of the indicator may include the delivery method with which the indicator is applied (gel pen, swab, etc.) and how the indicator should be applied (swirl pattern, dot, etc.) may be provided. Similarly, detailed instructions concerning collection of ATP or culture samples (size of swab or culture, etc.) may also be provided. Information regarding the specific location at which the indicator should be applied or from where the ATP or culture should be taken (faucet post vs. faucet handle; near end of faucet handle vs. far end of faucet handle; top or bottom of flange of toilet flush; back, left or right side of toilet seat; location on toilet hand rail, etc.) may also be provided.
The data collected from verification process 300, as well as from all of the other verification processes of the validated hospital cleaning method, may be input manually (such as for visual inspection of the indicator or ATP or culture counts) or automatically for those pieces of data obtained from automated equipment.
Various modules and validation processes of the validated hospital cleaning system/method described herein may include infection prevention solutions including chemistries, equipment, dispensing, packaging, effective utilization processes, validation and auditing methods and ease-of-use automation technologies. These may include, for example, high level disinfectants, patient bathing/wipe/wash, equipment draping, site prep, wound cleaning, cart washing, floor tacky mats, patient screening/ID, patient pre-admission kits, room decontaminants, long life hard surface disinfectant, soft surface mist/vapor cleaning, ice machine conditioning, air filtration, visitor barriers/screens/kits, operating room cleaning solution, patient room cleaning solution, general instrument clean/sanitize, GI device clean/disinfect, fluid management/disposal, systems for cleaning/sanitizing, sensors/monitors/tracking devices, etc.
The validated hospital cleaning system/method may incorporate tools for data utilization and process improvements such as data collection, analysis, utilization and interpretation to achieve process improvements, behavioral changes and outcome measures. For example, the validated hospital cleaning method may include tools and technology to gather/manage information, outcome data collection, data analysis and utilization, peer hospital comparisons, industry metrics/standards.
The validated hospital cleaning system/method may also include quality assurance, such as oversight and monitoring of labor providers to assure cleaning and disinfection quality across the hospital to reduce the spread of HAIs (hospital staff, outside provider employees, contractors, etc.). Quality control may also receive input from various automated machines, such as chemical dispensers that dispense various cleaning solutions, to ensure that the concentration of active ingredient in a disinfectant or other chemical is within certain limits, that the appropriate amounts are being dispensed, etc.
The validated hospital cleaning process may capture many demographics as well as measure the effectiveness of following of the validated cleaning process. The data may include, for example, information related to room cleanliness, patient satisfaction scores, HAI infection risks and others. The data may be used as a feed back loop to assure the system has been followed as prescribed in the validated process which has been shown to yield improved results in these three areas. The validated hospital cleaning system/process may include capturing a baseline status of the cleanliness of the room or the cleanliness of each module within a hospital or other healthcare facility.
As described herein, some parts of the validated hospital cleaning process may be computer implemented, and as such may be incorporated into computer software or hardware. For example, a computer system may collect and analyze data generated during implementation of the validation processes. A computer implemented system may analyze data to determine whether a particular validation point has been satisfied, and may perform statistical analysis on a process, module or hospital-wide basis. This information may be stored and analyzed and reports generated to provide feedback to a facility manager or corporation. Furthermore, the analysis may be performed across multiple accounts, such as multiple accounts within a single corporation or organizational region, to compare, for example, one hospital in a corporation with other hospitals within the same corporation or to compare like modules of multiple hospitals.
The techniques described herein may be implemented in hardware, software, firmware or any combination thereof. If implemented in software, the techniques may be realized at least in part by a computer-readable medium comprising instructions that, when executed by computer of a validated healthcare processing system cause the computer to perform one or more of the techniques of this disclosure. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may comprise random access memory (RAM) such as synchronous dynamic random access memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), FLASH memory, magnetic or optical data storage media, a magnetic disk or a magnetic tape, a optical disk or magneto-optic disk, CD, CD-ROM, DVD, a holographic medium, or the like. The instructions may be implemented as one or more software modules, which may be executed by themselves or in combination with other software.
The computer-readable instructions may be executed in the computer of the system by one or more processors, general purpose microprocessors, ASICs, FPGAs or other equivalent integrated or discrete logic circuitry.
The instructions and the media are not necessarily associated with any particular computer or other apparatus, but may be carried out by various general-purpose or specialized machines. The instructions may be distributed among two or more media and may be executed by two or more machines. The machines may be coupled to one another directly, or may be coupled through a network, such as a local access network (LAN), or a global network such as the Internet. Accordingly, the term “processor,” as used herein may refer to any structure suitable for implementation of the techniques described herein.
The invention may also be embodied as one or more devices that include logic circuitry to carry out the functions or methods as described herein. The logic circuitry may include a processor that may be programmable for a general purpose or may be dedicated, such as microcontroller, a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a field programmable gate array (FPGA), and the like.
One or more of the techniques described herein may be partially or wholly executed in software. For example, a computer-readable medium may store or otherwise comprise computer-readable instructions, i.e., program code that can be executed by a processor to carry out one of more of the techniques described above.
The validated hospital cleaning method may also incorporate healthcare worker training and continuing education, such as teaching new or ongoing skills and changing paradigms and behaviors within hospitals. These may include, for example, central sterile on-site process training/validation/usage, compliance/ procedural training, training oversight/monitoring/interventions, comprehensive training to impact outcomes, medical school and association curriculum, certification training, etc. This may include both upfront and periodic refresher training, training materials and a training process created for each module to assure the housekeepers are following the best practice process and using the proper tools and products to assure the use of the validated process will yield the outcome of a clean room or module, and possibly a reduced HAI risk.
The validated hospital cleaning system and method thus provides a comprehensive, hospital-wide cleaning and sanitization practice that addresses cleaning, disinfection sterilization and clinical solutions that may increase hospital cleanliness and may reduce the spread of HAIs. Advantages of the validated hospital cleaning system and method may be documented improvements in environmental sanitation, perceptible room cleanliness, patient satisfaction scores, and HAI risk reduction and associated cost savings. Advantages may also include fewer patient deaths and patient complications due to HAIs. The validated hospital cleaning system and method may also provide cost reductions through improved operational efficiencies and a reduction in health care worker errors and inconsistencies.
Although the validated hospital cleaning system and method has been described with respect to hospitals or other healthcare facilities, it shall be understood that this concept may also be applied to the cleaning and sanitation best practice in many different enterprises in which an integrated approach to cleaning and/or sanitizing a portion of a facility or an entire facility is desired. For example, the modular validated hospital cleaning system and method may be adapted for use in applications such as hotel room cleaning, education facilities, long term care, restaurants, food service, food and beverage facilities, eating areas, rest rooms, food preparation areas, cooking areas, etc.
Various embodiments of the invention have been described. These and other embodiments are within the scope of the following claims.
This application claims the benefit of U.S. provisional Application Ser. No. 61/125,922 filed Apr. 30, 2008, the entire contents of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
3736584 | Hackett et al. | May 1973 | A |
3761909 | Schweitzer et al. | Sep 1973 | A |
3786467 | Cotter | Jan 1974 | A |
3801977 | Cotter | Apr 1974 | A |
3866198 | Cohen | Feb 1975 | A |
3961321 | Moss | Jun 1976 | A |
3986182 | Hackett | Oct 1976 | A |
4076146 | Lausberg et al. | Feb 1978 | A |
4117462 | Miller | Sep 1978 | A |
4198618 | Kleinschmidt | Apr 1980 | A |
4209776 | Frederick | Jun 1980 | A |
4275390 | Heywang et al. | Jun 1981 | A |
4319349 | Hackett | Mar 1982 | A |
4360905 | Hackett | Nov 1982 | A |
4486910 | Saalmann et al. | Dec 1984 | A |
4539846 | Grossman | Sep 1985 | A |
4590460 | Abbott et al. | May 1986 | A |
4644509 | Kiewit et al. | Feb 1987 | A |
4727522 | Steiner et al. | Feb 1988 | A |
4729120 | Steiner et al. | Mar 1988 | A |
4896144 | Bogstad | Jan 1990 | A |
4987402 | Nykerk | Jan 1991 | A |
4991146 | Ransdell et al. | Feb 1991 | A |
5083298 | Citterio et al. | Jan 1992 | A |
5110364 | Mazur et al. | May 1992 | A |
5150099 | Lienau | Sep 1992 | A |
5153520 | Dumbeck | Oct 1992 | A |
5202666 | Knippscheer | Apr 1993 | A |
5245317 | Chidley et al. | Sep 1993 | A |
5263006 | Hermesmeyer | Nov 1993 | A |
5309409 | Jones et al. | May 1994 | A |
5370267 | Schroeder | Dec 1994 | A |
5390385 | Beldham | Feb 1995 | A |
5430293 | Sato et al. | Jul 1995 | A |
5463595 | Rodhall et al. | Oct 1995 | A |
5570079 | Dockery | Oct 1996 | A |
5610589 | Evans et al. | Mar 1997 | A |
5625659 | Sears | Apr 1997 | A |
5661471 | Kotlicki | Aug 1997 | A |
5684458 | Calvarese | Nov 1997 | A |
5695091 | Winings et al. | Dec 1997 | A |
5731526 | Kindrick | Mar 1998 | A |
5764136 | Harron | Jun 1998 | A |
5765605 | Waymire et al. | Jun 1998 | A |
5771925 | Lewandowski | Jun 1998 | A |
H1743 | Graves et al. | Aug 1998 | H |
5793653 | Segal | Aug 1998 | A |
5812059 | Shaw et al. | Sep 1998 | A |
5900067 | Jones | May 1999 | A |
5913915 | McQuinn | Jun 1999 | A |
5917425 | Crimmins et al. | Jun 1999 | A |
5939974 | Heagle et al. | Aug 1999 | A |
5945910 | Gorra | Aug 1999 | A |
5952924 | Evans et al. | Sep 1999 | A |
5954069 | Foster | Sep 1999 | A |
5966753 | Gauthier et al. | Oct 1999 | A |
5977913 | Christ | Nov 1999 | A |
5979703 | Nystrom | Nov 1999 | A |
5987105 | Jenkins et al. | Nov 1999 | A |
6012041 | Brewer et al. | Jan 2000 | A |
6031461 | Lynn | Feb 2000 | A |
6038331 | Johnson | Mar 2000 | A |
6065639 | Maddox et al. | May 2000 | A |
6125482 | Foster | Oct 2000 | A |
6130607 | McClanahan et al. | Oct 2000 | A |
6147607 | Lynn | Nov 2000 | A |
6175308 | Tallman et al. | Jan 2001 | B1 |
6191693 | Sangsingkeow | Feb 2001 | B1 |
6211788 | Lynn et al. | Apr 2001 | B1 |
6213424 | Helfer-Grand | Apr 2001 | B1 |
6236317 | Cohen et al. | May 2001 | B1 |
6236953 | Segal | May 2001 | B1 |
6259956 | Myers et al. | Jul 2001 | B1 |
6278372 | Velasco, Jr. et al. | Aug 2001 | B1 |
6279777 | Goodin et al. | Aug 2001 | B1 |
6288641 | Casais | Sep 2001 | B1 |
6314282 | Weber et al. | Nov 2001 | B1 |
6331964 | Barone | Dec 2001 | B1 |
6351223 | DeWeerd et al. | Feb 2002 | B1 |
6360181 | Gemmell et al. | Mar 2002 | B1 |
6368420 | Angevaare et al. | Apr 2002 | B1 |
6375038 | Daansen et al. | Apr 2002 | B1 |
6392546 | Smith | May 2002 | B1 |
6404837 | Thompson et al. | Jun 2002 | B1 |
6417773 | Vlahos et al. | Jul 2002 | B1 |
6426701 | Levy et al. | Jul 2002 | B1 |
6476385 | Albert | Nov 2002 | B1 |
6485979 | Kippenhan et al. | Nov 2002 | B1 |
6523193 | Saraya | Feb 2003 | B2 |
6524390 | Jones | Feb 2003 | B1 |
6577240 | Armstrong | Jun 2003 | B2 |
6611207 | Yuan et al. | Aug 2003 | B1 |
6681003 | Linder et al. | Jan 2004 | B2 |
6707873 | Thompson et al. | Mar 2004 | B2 |
6727818 | Wildman et al. | Apr 2004 | B1 |
6730024 | Freyre et al. | May 2004 | B2 |
6749148 | Helfer-Grand | Jun 2004 | B2 |
6759959 | Wildman | Jul 2004 | B2 |
6778092 | Braune | Aug 2004 | B2 |
6781523 | Matsui et al. | Aug 2004 | B2 |
6792395 | Roberts | Sep 2004 | B2 |
6799085 | Crisp, III | Sep 2004 | B1 |
6882278 | Winings et al. | Apr 2005 | B2 |
6882315 | Richley et al. | Apr 2005 | B2 |
6883563 | Smith | Apr 2005 | B2 |
6917290 | Land | Jul 2005 | B2 |
6919567 | Iwasawa | Jul 2005 | B2 |
6956498 | Gauthier et al. | Oct 2005 | B1 |
6975231 | Lane et al. | Dec 2005 | B2 |
7015816 | Wildman et al. | Mar 2006 | B2 |
7023356 | Burkhardt et al. | Apr 2006 | B2 |
7042361 | Kazdin et al. | May 2006 | B2 |
7056050 | Sacks | Jun 2006 | B2 |
7067054 | Fritze | Jun 2006 | B2 |
7069188 | Roberts | Jun 2006 | B2 |
7075412 | Reynolds et al. | Jul 2006 | B1 |
7099781 | Heidl et al. | Aug 2006 | B1 |
7099856 | Barangan et al. | Aug 2006 | B2 |
7117374 | Hill et al. | Oct 2006 | B2 |
7119688 | Wildman | Oct 2006 | B2 |
7119692 | Leiffort et al. | Oct 2006 | B2 |
7142108 | Diener et al. | Nov 2006 | B2 |
7157045 | McVey | Jan 2007 | B2 |
7187287 | Ryal | Mar 2007 | B2 |
7191090 | Cunningham | Mar 2007 | B1 |
7201005 | Voglewede et al. | Apr 2007 | B2 |
7202780 | Teller | Apr 2007 | B2 |
7236097 | Cunningham | Jun 2007 | B1 |
7242307 | LeBlond et al. | Jul 2007 | B1 |
7248933 | Wildman | Jul 2007 | B2 |
7265673 | Teller | Sep 2007 | B2 |
7266347 | Gross | Sep 2007 | B2 |
7267531 | Anderson et al. | Sep 2007 | B2 |
7271728 | Taylor et al. | Sep 2007 | B2 |
7272537 | Mogadam | Sep 2007 | B2 |
7286057 | Bolling | Oct 2007 | B2 |
7292914 | Jungmann et al. | Nov 2007 | B2 |
7293645 | Harper et al. | Nov 2007 | B2 |
7315245 | Lynn et al. | Jan 2008 | B2 |
7330108 | Thomas | Feb 2008 | B2 |
7372367 | Lane et al. | May 2008 | B2 |
7375640 | Plost | May 2008 | B1 |
7400264 | Boaz | Jul 2008 | B2 |
7408470 | Wildman et al. | Aug 2008 | B2 |
7411511 | Kennish et al. | Aug 2008 | B2 |
7423533 | LeBlond et al. | Sep 2008 | B1 |
7425900 | Lynn et al. | Sep 2008 | B2 |
7440620 | Aartsen | Oct 2008 | B1 |
7443305 | Verdiramo | Oct 2008 | B2 |
7450472 | Guyvarch | Nov 2008 | B2 |
7457869 | Kernan | Nov 2008 | B2 |
7474215 | Scott et al. | Jan 2009 | B2 |
7477148 | Lynn et al. | Jan 2009 | B2 |
7482936 | Bolling | Jan 2009 | B2 |
7486193 | Elwell | Feb 2009 | B2 |
7487538 | Mok | Feb 2009 | B2 |
7490045 | Flores et al. | Feb 2009 | B1 |
7496479 | Garcia et al. | Feb 2009 | B2 |
7538680 | Scott et al. | May 2009 | B2 |
7551092 | Henry | Jun 2009 | B1 |
7597122 | Smith | Oct 2009 | B1 |
7600137 | Trappeniers et al. | Oct 2009 | B2 |
7605704 | Munro et al. | Oct 2009 | B2 |
7611030 | Reynolds et al. | Nov 2009 | B2 |
7616122 | Bolling | Nov 2009 | B2 |
7718395 | Carling | May 2010 | B2 |
7780453 | Carling | Aug 2010 | B2 |
7785109 | Carling | Aug 2010 | B2 |
20010039501 | Crevel et al. | Nov 2001 | A1 |
20010047214 | Cocking et al. | Nov 2001 | A1 |
20010053939 | Crevel et al. | Dec 2001 | A1 |
20010054038 | Crevel et al. | Dec 2001 | A1 |
20020000449 | Armstrong | Jan 2002 | A1 |
20020019709 | Segal | Feb 2002 | A1 |
20020050006 | Saraya | May 2002 | A1 |
20020103671 | Pederson et al. | Aug 2002 | A1 |
20020132343 | Lum | Sep 2002 | A1 |
20020135486 | Brohagen et al. | Sep 2002 | A1 |
20020145523 | Robaey | Oct 2002 | A1 |
20020175182 | Matthews et al. | Nov 2002 | A1 |
20020183979 | Wildman | Dec 2002 | A1 |
20030030562 | Lane et al. | Feb 2003 | A1 |
20030065536 | Hansen et al. | Apr 2003 | A1 |
20030074222 | Rosow et al. | Apr 2003 | A1 |
20030182180 | Zarrow | Sep 2003 | A1 |
20040001009 | Winings et al. | Jan 2004 | A1 |
20040015269 | Jungmann et al. | Jan 2004 | A1 |
20040028608 | Saul et al. | Feb 2004 | A1 |
20040049369 | Konicek et al. | Mar 2004 | A1 |
20040075347 | Biskup, Sr. et al. | Apr 2004 | A1 |
20040088076 | Gardner, Jr. | May 2004 | A1 |
20040090333 | Wildman et al. | May 2004 | A1 |
20040148196 | Kalies | Jul 2004 | A1 |
20040162850 | Sanville et al. | Aug 2004 | A1 |
20050086341 | Enga et al. | Apr 2005 | A1 |
20050102167 | Kapoor | May 2005 | A1 |
20050149341 | Eguchi et al. | Jul 2005 | A1 |
20050222889 | Lai et al. | Oct 2005 | A1 |
20060067545 | Lewis et al. | Mar 2006 | A1 |
20060067546 | Lewis et al. | Mar 2006 | A1 |
20060071799 | Verdiramo | Apr 2006 | A1 |
20060104245 | Narayanaswami et al. | May 2006 | A1 |
20060132316 | Wildman et al. | Jun 2006 | A1 |
20060139449 | Cheng et al. | Jun 2006 | A1 |
20060140703 | Sacks | Jun 2006 | A1 |
20060154642 | Scannell, Jr. | Jul 2006 | A1 |
20060223731 | Carling | Oct 2006 | A1 |
20060229821 | Brossette et al. | Oct 2006 | A1 |
20060272361 | Snodgrass | Dec 2006 | A1 |
20060273915 | Snodgrass | Dec 2006 | A1 |
20070008146 | Taylor et al. | Jan 2007 | A1 |
20070008147 | Bolling | Jan 2007 | A1 |
20070008149 | Bolling | Jan 2007 | A1 |
20070016466 | Taylor | Jan 2007 | A1 |
20070020212 | Bernal et al. | Jan 2007 | A1 |
20070029962 | Saeki | Feb 2007 | A1 |
20070044819 | Chan et al. | Mar 2007 | A1 |
20070055483 | Lee et al. | Mar 2007 | A1 |
20070056091 | Bolton et al. | Mar 2007 | A1 |
20070069884 | Waxman | Mar 2007 | A1 |
20070096930 | Cardoso | May 2007 | A1 |
20070182581 | Elwell | Aug 2007 | A1 |
20070198067 | Van den Heuvel et al. | Aug 2007 | A1 |
20070205861 | Nair et al. | Sep 2007 | A1 |
20070213877 | Hart et al. | Sep 2007 | A1 |
20070222599 | Coveley et al. | Sep 2007 | A1 |
20070229288 | Ogrin et al. | Oct 2007 | A1 |
20070247316 | Wildman et al. | Oct 2007 | A1 |
20070257803 | Munro et al. | Nov 2007 | A1 |
20070285277 | Scott et al. | Dec 2007 | A1 |
20070290865 | Lynn et al. | Dec 2007 | A1 |
20080001763 | Raja et al. | Jan 2008 | A1 |
20080019489 | Lynn | Jan 2008 | A1 |
20080046278 | Sanville et al. | Feb 2008 | A1 |
20080084315 | Pittz | Apr 2008 | A1 |
20080087719 | Sahud | Apr 2008 | A1 |
20080100441 | Prodanovich et al. | May 2008 | A1 |
20080103636 | Glenn et al. | May 2008 | A1 |
20080131332 | Nguyen et al. | Jun 2008 | A1 |
20080185540 | Turner et al. | Aug 2008 | A1 |
20080189142 | Brown et al. | Aug 2008 | A1 |
20080193631 | Kanamori et al. | Aug 2008 | A1 |
20080246599 | Hufton et al. | Oct 2008 | A1 |
20080266113 | Kennish et al. | Oct 2008 | A1 |
20080280380 | Dietz et al. | Nov 2008 | A1 |
20080303658 | Melker et al. | Dec 2008 | A1 |
20090002644 | Christensen et al. | Jan 2009 | A1 |
20090019552 | McLaughlin et al. | Jan 2009 | A1 |
20090051545 | Koblasz | Feb 2009 | A1 |
20090091458 | Deutsch | Apr 2009 | A1 |
20090102681 | Brennan, Jr. et al. | Apr 2009 | A1 |
20090112630 | Collins, Jr. et al. | Apr 2009 | A1 |
20090119142 | Yenni et al. | May 2009 | A1 |
20090138303 | Seshadri | May 2009 | A1 |
20090195385 | Huang et al. | Aug 2009 | A1 |
20090204256 | Wegelin | Aug 2009 | A1 |
20090219131 | Barnett et al. | Sep 2009 | A1 |
20090219172 | Wilbrod | Sep 2009 | A1 |
20090224907 | Sinha et al. | Sep 2009 | A1 |
20090224924 | Thorp | Sep 2009 | A1 |
20090267776 | Glenn et al. | Oct 2009 | A1 |
20100233020 | Klaassen et al. | Sep 2010 | A1 |
20100274640 | Morey et al. | Oct 2010 | A1 |
20100315243 | Tokhtuev et al. | Dec 2010 | A1 |
20100315244 | Tokhtuev et al. | Dec 2010 | A1 |
Number | Date | Country |
---|---|---|
19882120 | Oct 2010 | DE |
0921506 | Jun 1999 | EP |
1099400 | May 2001 | EP |
1201172 | May 2002 | EP |
1390204 | Dec 2004 | EP |
1034132 | Aug 2005 | EP |
1483728 | Oct 2006 | EP |
1791077 | May 2007 | EP |
1872802 | Jan 2008 | EP |
1913892 | Apr 2008 | EP |
2137749 | Oct 1984 | GB |
2217013 | Oct 1989 | GB |
2299405 | Oct 1996 | GB |
2324397 | Oct 1998 | GB |
2337327 | Nov 1999 | GB |
2340647 | Feb 2000 | GB |
2394654 | May 2004 | GB |
2417810 | Mar 2006 | GB |
2417811 | Mar 2006 | GB |
2425388 | Oct 2006 | GB |
2446871 | Aug 2007 | GB |
2437555 | Oct 2007 | GB |
2439306 | Dec 2007 | GB |
2439457 | Dec 2007 | GB |
10309540 | Nov 1998 | JP |
2003105819 | Apr 2003 | JP |
2003122823 | Apr 2003 | JP |
2005218999 | Aug 2005 | JP |
2006198318 | Aug 2006 | JP |
WO 9213327 | Aug 1992 | WO |
WO 9731350 | Aug 1997 | WO |
WO 9809261 | Mar 1998 | WO |
WO 9836258 | Aug 1998 | WO |
WO 0022260 | Apr 2000 | WO |
WO 0133529 | May 2001 | WO |
WO0221475 | Mar 2002 | WO |
WO 03079278 | Sep 2003 | WO |
WO 03082351 | Oct 2003 | WO |
WO 2005055793 | Jun 2005 | WO |
WO 2005055793 | Jun 2005 | WO |
WO 2005094711 | Oct 2005 | WO |
WO 2006036687 | Apr 2006 | WO |
WO 2007001866 | Jan 2007 | WO |
WO 2007090470 | Aug 2007 | WO |
WO2006135922 | Aug 2007 | WO |
WO 2007129289 | Nov 2007 | WO |
WO 2007133960 | Nov 2007 | WO |
WO 2008088424 | Jul 2008 | WO |
WO 2008133495 | Nov 2008 | WO |
WO 2010101929 | Sep 2010 | WO |
Entry |
---|
Chris Griffith, “Nosocomial infection, Are there lessons from the food industry?”, The Biomedical Scientist, pp. 697-699, Aug. 2006. |
John Bourn, Auditor General for Wales, “The Management and Delivery of Hospital Cleaning Services in Wales”, National Audit Office Wales, 39 pages, May 23, 2003. |
Mallow General Hospital, “Hygiene Services Assessment Scheme, Assessment Report”, 38 pages, Oct. 2007. |
Dix et al., “Environmental Surface Cleaning, First Defense Against: Infectious Agents”, Infection Control Today Magazine, 6 pages, Dec. 1, 2005. |
Yoshikura, “Workflow from Clean to Dirty. HACCP and Inclusiveness Principles in Effective Implementation of Hospital Infection Control”, Jpn. J. Infect. Dis., vol. 53, pp. 124-125, 2000. |
R. Quattrin, MD et al., “Application of Hazard Analysis Critical Control Points to Control Surgical Site Infections in Hip and Knee Arthroplasty”, Orthopedics, 31:132, SLACK Incorporated, 6 pgs, 2008. |
International Search Report and Written Opinion of the International Searching Authority from corresponding PCT Application Serial No. PCT/IB2009/051751 mailed Jan. 27, 2010 (8 pages). |
SaferCorp, LLC, SaferCorp Life Advantage Solutions presents SaferHands™ Hospital Automated Hand Hygiene Monitoring System, retrieved electronically from http://www.guardianics.com/ on Dec. 15, 2010, 14 pp. |
SaferCorp, LLC, Guardian™ Automated Infection Control Systems (GAICS), Feb. 6, 2010, 4 pp. |
Sturman et al., “Cornell Hospitality Report: A New Method for Measuring Housekeeping Performance Consistency,” CHR Reports, vol. 6, No. 11, Sep. 2006, 15 pp. |
Ophardt hygiene, Hygiene Compliance Solutions, 2009, 1 p. |
Elliot, “Determining Three Metrics for Cleaning Satisfaction,” found at http://www.facilitiesnet.com/equipmentrentaltools/article/Determining-Three-Metrics-for-Cleaning-Satisfaction--7698#, Nov. 2007, 2 pp. |
Van Ryzin et al., “Measuring Street Cleanliness: A Comparison of New York City's Scorecard and Results from a Citizen Survey,” Public Administration Review 68(2):295-303, Mar./Apr. 2008. |
Evaluating Municipal Services: Scorecard Cleanliness Program Prospectus, New York, found at http://www.worldsweeper.com/Street/Profiles/NYCScorecard.pdf, archived Jan. 5, 2009, 20 pp. |
Office Action from U.S. Appl. No. 12/766,714, dated Mar. 29, 2012, 20 pp. |
Response to Office Action dated Mar. 29, 2012, from U.S. Appl. No. 12/766,714, filed Jun. 28, 2012, 8 pp. |
Office Action from U.S. Appl. No. 12/787,097, dated Jun. 4, 2012, 5 pp. |
Response to Office Action dated Jun. 4, 2012, from U.S. Appl. No. 12/787,097, filed Sep. 4, 2012, 8 pp. |
Response to Office Action dated Feb. 5, 2013, from U.S. Appl. No. 13/369,056, filed May 3, 2013, 10 pp. |
Response to Final Office Action dated Sep. 17, 2012, from U.S. Appl. No. 12/766,714, filed Dec. 17, 2012, 10 pp. |
Office Action from U.S. Appl. No. 12/787,064, dated Dec. 6, 2012, 5 pp. |
Notice of Allowance from U.S. Appl. No. 12/787,097, dated Nov. 7, 2012, 8 pp. |
Al-Hamad et al., “How Clean is Clean? Proposed Methods for Hospital Cleaning Assessment,” Journal of Hospital Infection, vol. 70, Oct. 9, 2008, pp. 328-334. |
Lewis et al., “A Modified ATP Benchmark for Evaluating the Cleaning of Some Hospital Environmental Surfaces,” Journal of Hospital Infection, vol. 69, May 12, 2008, pp. 156-163. |
Exner et al., “Household Cleaning and Surface Disinfection: New Insights and Strategies,” Journal of Hospital Infection, vol. 56, 2008, pp. s70-s75. |
Griffith et al., “The Effectiveness of Existing and Modified Cleaning Regimens in a Welsh Hospital,” Journal of Hospital Infection, vol. 66, Jul. 26, 2007, pp. 352-359. |
Dancer, “How do we Assess Hospital Cleaning? A Proposal for Microbiological Standards for Surface Hygiene in Hospitals” Journal of Hospital Infection, vol. 56, 2004, pp. 10-15. |
Zuhlsdorf et al., “Cleaning Efficacy of Nine Different Cleaners in a Washer-Disinfector Designed for Flexible Endoscopes,” Journal of Hospital Infection, vol. 52, 2002, pp. 206-211. |
Office Action from U.S. Appl. No. 12/766,714, dated Sep. 17, 2012, 28 pp. |
Office Action from U.S. Appl. No. 13/369,056, dated Feb. 5, 2013, 16 pp. |
Response to Office Action dated Dec. 6, 2013, from U.S. Appl. No. 12/787,064, filed Mar. 6, 2013, 7 pp. |
Rifhat E. Malik et al., “Use of Audit Tools to Evaluate the Efficacy of Cleaning Systems in Hospitals,” Am. J. Infect. Control, vol. 31, No. 3, p. 181-187 2003. |
C. J. Griffith et al., “An Evaluation of Hospital Cleaning Regimes and Standards,” J. Hosp. Infect., vol. 45, p. 19-28 2000. |
Office Action from U.S. Appl. No. 12/766,714, dated Sep. 23, 2014, 20 pp. |
Office Action from U.S. Appl. No. 14/136,889, dated Dec. 12, 2014, 21 pp. |
Amendment in Response to Office Action mailed Sep. 23, 2014, from U.S. Appl. No. 12/766,714, filed Jan. 23, 2015, 10 pp. |
Number | Date | Country | |
---|---|---|---|
20090276239 A1 | Nov 2009 | US |
Number | Date | Country | |
---|---|---|---|
61125922 | Apr 2008 | US |