WO2014143082A1

WO2014143082A1 - Automated statistical process control chart creation

Info

Publication number: WO2014143082A1
Application number: PCT/US2013/036730
Authority: WO
Inventors: Rocco J. PERLA; Charles A. SCHOPP; Deborah Ann MACK; Richard T. Ellison, Iii
Original assignee: University Of Massachusetts
Priority date: 2013-03-14
Filing date: 2013-04-16
Publication date: 2014-09-18

Abstract

In an embodiment, patient information may be acquired. Patient-days information may be generated based on acquired patient information. The generated patient-days information may be stored. Infection information may be acquired. One or more workbooks may be generated based on the acquired infection information. Workbook information may be loaded from one or more of the generated workbooks. The loaded workbook information may be stored. An indication may be provided to generate one or more charts based on the stored workbook information and/or stored patient-days information. The indication may be provided via an interface. The charts may include, for example, one or more system-level charts and/or unit-level charts.

Description

AUTOMATED STATISTICAL PROCESS CONTROL CHART CREATION

Inventors: Rocco J. Perla, Charles A. Schopp, Deborah Ann Mack, and Richard Thomas Ellison III

BRIEF DESCRIPTION OF THE DRAWINGS

[0001] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments described herein and, together with the description, explain these embodiments. In the drawings:

[0002] FIG. 1 illustrates a block diagram of an example of a computing device;

[0003] FIG. 2 illustrates a block diagram of an example of a chart system;

[0004] FIG. 3 illustrates a block diagram of example tables that may be included in an infection control database;

[0005] FIGs. 4A-F illustrate an example interface that may be used with a chart system;

[0006] FIG. 5 illustrates an example of control chart that may be generated by a chart system;

[0007] FIGs. 6A-B illustrate an example of a run chart and t-chart, respectively, that may be generated by a chart system;

[0008] FIG. 7 illustrates a flow diagram of example acts that may be used to generate one or more charts; and [0009] FIGs. 8A-B illustrate a flow diagram of example acts that may be used generate one or more charts.

DETAILED DESCRIPTION

[0010] The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.

[0011] FIG. 1 illustrates a block diagram of an example embodiment of a computing device 100. Referring to FIG. 1, computing device 100 may include various components such as, for example, processing logic 120, primary storage 130, secondary storage 150, one or more input devices 160, one or more output devices 170, and/or one or more communication interfaces 180.

[0012] It should be noted that FIG. 1 illustrates an example embodiment of a computing device 100. Other embodiments of computing device 100 may include more components or fewer components than the components illustrated in FIG. 1. In addition, in other embodiments of computing device 100, the components may be arranged differently than as illustrated in FIG. 1.

[0013] For example, in an embodiment of computing device 100, secondary storage 150 may be contained at a remote site that provides "cloud" storage. The site may be accessible to computing device 100 via a communications network, such as, for example, the Internet. A communication interface 180 may be used to interface the computing device 100 with the communications network. Also, it should be noted that functions performed by various components contained in other embodiments of computing device 100 may be distributed among the components differently than as described herein.

[0014] Computing device 100 may include an input/output (I/O) bus 110 that may be used to communicate information between components in computing device 100. The information may include, for example, control signals and/or data. Examples of I/O buses that may be used to implement I O bus 110 may include serial AT attachment (SATA), peripheral component interconnect (PCI), PCI express (PCTe), universal serial bus (USB), small computer system interface (SCSI), serial attached SCSI (SAS), and/or some other I/O bus. [0015] Computing device 100 may include a memory bus 190 that may enable information, which may be stored in primary storage 130, to be transferred between processing logic 120 and primary storage 130. The information may include computer-executable instructions and/or data that may be executed, manipulated, and/or otherwise processed by processing logic 120. [0016] Processing logic 120 may include logic for interpreting, executing, and/or otherwise processing information. The information may be stored in, for example, primary storage 130 and/or secondary storage 150. In addition, the information may be acquired by one or more input devices 160 and/or communication interfaces 180.

[0017] Processing logic 120 may include a variety of heterogeneous hardware. For example, the hardware may include some combination of one or more processors, microprocessors, field programmable gate arrays (FPGAs), application specific instruction set processors (ASIPs), application specific integrated circuits (ASICs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), and/or other types of processing logic that may, for example, interpret, execute, manipulate, and/or otherwise process the information. Processing logic 120 may comprise a single core or multiple cores. An example of a processor that may be used to implement processing logic 120 is the Intel® Xeon® processor available from Intel Corporation, Santa Clara, California.

[0018] Input devices 160 may include one or more input devices that may be used to input information into computing device 100. The input devices may include, for example, a keyboard, computer mouse, microphone, camera, trackball, gyroscopic device (e.g., gyroscope), mini-mouse, touch pad, stylus, graphics tablet, touch screen, joystick (isotonic or isometric), pointing stick, accelerometer, palm mouse, foot mouse, puck, eyeball controlled device, finger mouse, light pen, light gun, neural device, eye tracking device, steering wheel, yoke, jog dial, space ball, directional pad, dance pad, soap mouse, haptic device, tactile device, neural device, multipoint input device, discrete pointing device, and/or some other input device. The information may include, for example, spatial (e.g., continuous, multi-dimensional) data that may be input into computing device 100 using a pointing device, such as a computer mouse and/or other forms of data, such as text that may be input using a keyboard.

[0019] Output devices 170 may include one or more output devices that may output information from computing device 100. The output devices may include, for example, a cathode ray tube (CRT), plasma display device, light-emitting diode (LED) display device, liquid crystal display (LCD) device, vacuum florescent display (VFD) device, surface-conduction electron-emitter display (SED) device, field emission display (FED) device, haptic device, tactile device, printer, speaker, video projector, volumetric display device, plotter, touch screen, and/or some other output device. Output devices 170 may be directed by, for example, processing logic 120, to output the information from computing device 100. Outputting the information may include presenting (e.g., displaying, printing) the information on an output device 170. The information may include, for example, text, graphical user interface (GUI) elements (e.g., windows, widgets, and/or other GUI elements), audio (e.g., music, sounds), and/or other information that may be outputted by output devices 170. [0020] Communication interfaces 180 may include logic for interfacing computing device 100 with, for example, one or more communications networks and enable computing device 100 to communicate with one or more entities (e.g., nodes) coupled to the

communications networks. The communications networks may include, for example, the Internet, wide-area networks (WANs), local area networks (LANs), 3G and/or 4G networks. Communication interfaces 180 may include one or more transceiver-like mechanisms that may enable computing device 100 to communicate with entities coupled to the communications networks. Examples of communication interfaces 180 may include a built-in network adapter, network interface card (NIC), Personal Computer Memory Card International Association (PCMCIA) network card, card bus network adapter, wireless network adapter, Universal Serial Bus (USB) network adapter, modem, and/or other device suitable for interfacing computing device 100 to a communications network. [0021] Primary storage 130 may provide storage for computing device 100. The storage may be used to store information that may be used by computing device 100. The information may be stored in a non-transitory tangible computer-readable medium. The information may include, for example, data and/or instructions that may be used to implement one or more embodiments of the invention.

[0022] Primary storage 130 may include one or memory devices that may be used to store the information. The memory devices may be volatile and/or non- volatile. The memory devices may include, for example, dynamic RAM (DRAM) devices, flash memory devices, static RAM (SRAM) devices, zero-capacitor RAM (ZRAM) devices, twin transistor RAM (TTRAM) devices, read-only memory (ROM) devices, ferroelectric transistor RAM (FeTRAM) devices, magneto-resistive RAM (MRAM) devices, phase change memory (PCM) devices, PCM and switch (PCMS) devices, nanowire-based devices, resistive RAM devices (RRAM), serial electrically erasable programmable ROM (SEEPROM) devices, serial flash devices, and/or other types of memory devices. [0023] Primary storage 130 may be accessible to processing logic 120 via memory bus

190. Bus 190 may be a wired bus that may carry signals and/or data between primary storage 130 and processing logic 130.

[0024] Primary storage 130 may include computer-executable instructions and/or data that may implement operating system (OS) 132 and one or more applications (APP) 134. The computer-executable instructions may be executed, interpreted, and/or otherwise processed by processing logic 120. Computer-executable instructions and/or data used to implement OS 132 and/or APP 134 may include computer-executable instructions and/or data that may implement one or more embodiments of the invention.

[0025] OS 132 may be a conventional operating system that may implement various conventional operating system functions. The functions may include, for example, (1) scheduling one or more portions of APP 134 to run on (e.g., be executed by) processing logic 120, (2) managing primary storage 130, and/or (3) controlling access to various components in computing device 100 (e.g., input devices 160, output devices 170, communication interfaces 180, secondary storage 150) and/or information received and/or transmitted by these

components. [0026] Examples of operating systems that may be used to implement OS 132 may include the Linux operating system, Microsoft Windows operating system, the Symbian operating system, Mac OS operating system, and the Android operating system. A distribution of the Linux operating system that may be used is Red Hat Linux available from Red Hat Corporation, Raleigh, North Carolina. Versions of the Microsoft Windows operating system that may be used include Microsoft Windows Mobile, Microsoft Windows 8, Microsoft Windows 7, Microsoft Windows Vista, and Microsoft Windows XP operating systems available from

Microsoft Corporation, Redmond, Washington. The Symbian operating system is available from Accenture PLC, Dublin, Ireland. The Mac OS operating system is available from Apple, Inc., Cupertino, California. The Android operating system is available from Google, Inc., Menlo

Park, California.

[0027] APP 134 may include a software application that may execute under control of OS 132 on computing device 100. APP 134 and/or OS 132 may contain provisions for processing information (e.g., data) that may be contained in one or more databases, such as databases 154. These provisions may be implemented using data and/or computer-executable instructions contained in APP 134 and/or OS 132. [0028] Secondary storage 150 may include one or more storage devices 152. The storage devices 152 may be accessible to processing logic 120 via I/O bus 110. The storage devices 152 may store information (e.g., data, computer-executable instructions). The information may be executed, interpreted, manipulated, and/or otherwise processed by processing logic 120. The information may include computer-executable instructions and/or data that may implement one or more embodiments of the invention.

[0029] A storage device 152 may include volatile or non- volatile storage for storing the information. Examples of devices that may be used to implement storage device 152 may include one or more magnetic disk drives, optical disk drives, RAM drives, flash drives, solid state disks (SSDs), hybrid drives, and/or other storage devices. The information may be stored on one or more non-transitory tangible computer-readable media contained in the storage devices. Examples of non-transitory tangible computer-readable media that may be contained in the storage devices may include magnetic discs, optical discs, volatile memory devices, and/or non-volatile memory devices.

[0030] The storage devices may include one or more databases 154. The databases 154 may contain information that may be used, for example, by one or more APPs 134. Examples of databases that may be included in databases 154 will be described further below. [0031] A chart system may be a system that may include provisions for processing information and/or generating one or more charts based on the processed information. The one or more charts may include, for example, one or more p-charts, moving range (e.g., Xmr) charts, c-charts, u-charts, and/or other types of charts. FIG. 2 illustrates a block diagram of an example of a chart system 200 that may be implemented by one or more computing devices. The computing devices may include, for example, computing device 100.

[0032] Referring to FIG. 2, chart system 200 may include various components, such as, for example, a patient data repository 202, a patient-days report 206, a unit stats database 214, an infection data repository 204, workbooks 216, 218, and 220, an infection control chart manager 222, an infection control database 300, and charts 230. It should be noted that chart system 200 is an example embodiment of a chart system. Other embodiments of chart system 200 may include more components or fewer components than illustrated in FIG. 2. Moreover, functions performed by various components contained in other embodiments of chart system 200 may be distributed among the components differently than as described herein. [0033] The patient data repository 202 may include information about one or more patients that may be admitted to one or more care centers. The care centers may include, for example, one or more hospitals, clinics, medical research centers, and/or other types of care centers. The information may include, for example, names of patients, locations of the patients within the care centers, and/or a number of days the patients have been admitted to the care centers. The patient data repository 202 may be organized as one or more databases that may be included in, for example, databases 154. An example of a system that may be used to generate and/or maintain patient data repository 202 is MediTech which is available from MediTech, Westwood, Massachusetts.

[0034] Information contained in the patient data repository 202 may be used by chart system 200 to generate a patient-days report 206. The patient-days report 206 may include information about patients admitted to the care centers. The information may include, for example, a number of patients at a particular care center, a number of days the patients have been in the care center, and/or a number of patient-days associated with the care centers.

[0035] A number of patient-days associated with a care center may be identified based on, for example, a number of patients in the care center and a number of days the patients have been in the care center. An example of a patient-days formula that may be used to identify a number of patient-days is as follows:

patient-days =

(number of patients in a care center) * (number of days the patients have been in the care center)

[0036] For example, suppose the care center is a hospital that contains 30 patients that have been in the hospital for 10 days. The patient-days report 206 may include the number of patients in the hospital (which in this example is 30), the number of days the patients have been in the hospital (which in this example is 10), and/or the number of patient-days (which in this example is 300, i.e., 30 multiplied by 10) associated with the hospital.

[0037] The unit stats database 214 may contain information that may be associated with information contained in the patient data repository 202 and/or patient-days report 206. The information may include information, such as, for example, patient-days information and/or other information. Unit stats database 214 may store the information in a database that may be included in databases 154.

[0038] Infection data repository 204 may include information about infections that may occur at one or more care centers. The information may include, for example, a number of infections, locations in the care centers where the infections occurred, dates of the infections, patients affected by the infections, type of infections, and/or other information. Information included in infection data repository 204 may be stored in a database that may be included in databases 154. Systems that may be used to generate and/or maintain infection data repository 204 may include, for example, TheraDoc which is available from Hospira, Inc., Lake Forest, Illinois and Soarian which is available from Siemens AG, Munich, Germany.

[0039] The workbooks 216, 218, and 220 may contain information that may be based on information contained in the infection data repository 204. Information contained in workbooks 216, 218, and 220 may include, for example, a number of infections, locations in a care center where the infections occurred, dates of the infections, patients affected by the infections, and/or other information. Information contained in the workbooks 216, 218, and 220 may be organized, for example, by infection type where a particular workbook includes information associated with an infection type. The workbooks 216, 218, and 220 may be spreadsheet workbooks that may be formatted for use with, for example, one or more spreadsheet applications, such as Microsoft Excel, Apache Open Office Calc, and Libre Office Calc. Excel is available from Microsoft Corporation, Apache Open Office Calc is available from the Apache Software Foundation, Forest Hill, Maryland and Libre Office Calc is available from The Document Foundation, Berlin, Germany.

[0040] The workbooks 216, 218, and/or 220 may be stored in one or more files that may be accessible to a computing device. For example, the workbooks 216, 218, and/or 220 may be stored in one or more files contained in secondary storage 150. The files may be accessible to computing device 100.

[0041] In chart system 200, workbooks 216, 218, and/or 220 may include information regarding infections. The information may be associated with one or more care centers. The information may include, for example, occurrences of certain types of infections at the care centers. For example, workbook 216 may include information related to occurrences of

Clostridium difficile (C. difficile) type infections that may have occurred at one or more of the care centers. In addition, workbook 218 may include information related to occurrences of Methicillin-resistant Staphylococcus Aureus (MRS A) type infections and workbook 220 may include information related to occurrences of Vancornycin-resistant Enterococci (VRE) type infect ons that may have occurred at one or more of the care centers.

[0042] It should be noted that workbooks 216, 218, and 220 are examples of workbooks that may be generated from information contained in the infection data repository 204. Other workbooks may include information related to other information that may be included in infection data repository 204. [0043] Infection control chart manager 222 may, for example, (1) acquire information that may be contained in the unit stats database 214 and/or one or more workbooks 216, 218, 220, (2) populate infection control database 300 with information that may be based on the acquired information, and (3) generate one or more charts 230from information that may be contained, for example, in the infection control database 300. [0044] Specifically, infection control chart manager 222 may include an interface (e.g., a

GUI) that may enable one or more parameters to be specified. An example of an interface that may be used with infection control chart manager 222 will be described further below. The parameters may be used by infection control chart manager 222 to, for example, read information from the unit stats database 214 and/or one or more workbooks 216, 218, 220. The information may include information about infections and/or patient-days.

[0045] Infection control chart manager 222 may store information in infection control database 300 wherein the information stored in the infection control database 300 may be based on the information read from the unit stats database 214 and/or workbooks 216, 218, and 220. The information may be stored in one or more records that may be contained in one or more tables in infection control database 300. Details of tables that may be included in infection control database 300 will be described further below. Infection control chart manager 222 may generate one or more charts 230 based on information that may be stored in the infection control database 300.

[0046] Infection control chart manager 222 may utilize one or more tools to generate one or more of the charts 230 or portions thereof. An example of a tool that may be used by infection control chart manager 222 to generate one or more charts 230 or portions thereof is QI Macros which is available from KnowWare International Inc., Denver, Colorado.

[0047] Charts 230 may include various types of charts. For example, charts 230 may include control charts, run charts, and/or other types of charts. The charts may be generated at a system level (e.g., for a group of care centers) and/or a unit level (e.g., for particular units within a care center). One or more of the charts 230 may be used for statistical process control (SPC).

[0048] A control chart may be a type of chart that may be used evaluate a performance of a process and/or system (e.g., care system) over time. For example, a control chart may be used to evaluate a stability and/or capability of the process and/or system over time. The control chart may be generated from information (e.g., performance data) collected about the process and/or system.

[0049] The control chart may include, for example, a family of charts that may be used to monitor, assess, and/or improve performance of the process and/or system. For example, variation represented in the control charts may be studied to determine whether changes made to the process and/or system have led to improvement. The control chart may, for example, (1) center attention on detecting and/or monitoring process and/or system variation over time, (2) provide a tool for ongoing assessment of the process and/or system, (3) differentiate special causes (e.g., non-random causes) from common causes (e.g., random causes) of variation, (3) act as a guide for decision making (which may lead to taking action), (4) guide the process and/or system to achieve more consistent and/or predictable performance that may be associated with a higher level of quality, lower cost, and/or increased capability, (5) serve as a common language for discussing process and/or system performance, and/or (6) create analytic standards for decision-making in various levels of an organization (versus, for example, standards that may be based on capricious and/or idiosyncratic criteria).

[0050] A run chart may be a type of chart that may be considered, for example, a simpler version of applied time series graphics that may identify random and/or non-random patterns in data. One way a run chart may differ from a control chart is that a run chart may not include statistically computed sigma limits (discussed further below) whereas a control chart may include these limits. A run chart may include data displayed in time order with a median of the data presented in the chart as a centerline.

[0051] A chart 230 may include, for example, one or more points that may represent one or more individual data values and/or a statistic (e.g., a mean, median, moving range, proportion). The statistic may represent, for example, a measurement of a quality characteristic in samples taken from a process and/or a system at different times (e.g., monthly, quarterly). A chart 230 may report, for example, the statistic, one or more statistics that may be derived from the statistic (e.g., a mean of means, a mean of ranges, a mean of proportions), and/or other information, such as, for example, sigma limits (e.g., a measure of dispersion for a process and/or system moving forward in time).

[0052] The chart 230 may also include upper and lower control limits (sometimes called

"natural process limits" or "sigma limits") that may indicate, for example, a threshold at which point associated with a process and/or a system reflected in the chart 230 may be considered statistically unlikely (i.e., special case). These limits may be indicated in the chart by one or more lines that may be drawn three standard errors (plus/minus) from a center line that may represent the process and/or system average.

[0053] The chart 230 may include other features, such as, for example, lines that may identify sigma limits above and below the center line. The chart 230 may be divided into zones, with an addition of rules governing, for example, frequencies of observations in a particular zone that may identify non-random signals. One or more annotations with events of interest may be included in the chart 230.

[0054] Examples of control chart types that may be included in charts 230 may include p-charts (which may show, for example, a proportion of nonconformities in a sub-group), u- charts (which may show, for example, nonconformities per unit within a sub-group), c-charts (which may show, for example, a number of nonconformities in a sub-group), t-charts (which may be used, for example, to monitor serious but rare events and/or outcomes), and/or other types of charts that may be related, for example, to statistical process control. The charts may be used, for example, to study and/or examine specific processes and/or systems over time and/or determine whether changes made to an underlying cause are leading to improvements. [0055] A chart 230 may apply, for example, to (1) an entire care system (e.g., a care center, health system, county, region) and/or (2) a unit and/or sub-system level within a care system. A chart 230 that may apply to an entire care system may be referred to as a "system- level chart". A chart 230 that may apply to a unit and/or sub-system level within a care system may be referred to as a "unit-level chart". A system-level chart may show various statistics associated with a care system. A unit-level chart may show various statistics associated with various units and/or sub-system levels of a care system. A unit and/or sub-system level of a care system may include, for example, a sub-division (e.g., intensive care unit (ICU), pediatrics ward, emergency room (ER)) within the care system, and/or entities that may be defined as a unit and/or sub-system level with the care system, such as, for example, a floor within a care center.

[0056] As noted above, infection control database 300 may store information related to information stored in the unit stats database 214 and/or information contained in workbooks 216, 218, and 220. Infection control database 300 may be organized as a database that may contain, for example, one or more tables. FIG. 3 illustrates example tables that may be included in infection control database 300.

[0057] Referring to FIG. 3, infection control database 300 may include an infections table 310, an infections type table 320, a locations table 340, and a patient-days table 350. It should be noted that FIG. 3 illustrates examples of tables that may be included in infection control database 300 and that other embodiments of infection control database 300 may be organized to include more tables or fewer tables than illustrated in FIG. 3. Moreover, other embodiments of infection control database 300 may store more information or fewer information that as described herein. In addition, in other embodiments of infection control database 300, information may be stored differently than as described herein.

[0058] The infections table 310 may include information associated with occurrences of infections. The infections may have occurred at, for example, one or more care centers. The information may be stored in one or more records that may be contained in the infections table 310 where a record may represent, for example, an occurrence of an infection at a particular location. Information in a record may include, for example, a type of infection (e.g., C. difficile, MRSA, VRE), date of infection, care center where the infection occurred, unit that reported the infection, organisms involved in the infection, and/or other information, such as a date and/or time the information was entered into the infection control database 300.

[0059] The infection types table 320 may include information that may describe types of infections that may be recorded in the infections table 310. Information in infection types table 320 may be stored in one or more records that may be contained in the infection types table 320 where a record may represent, for example, an infection type. A record may include, for example, information about a particular infection type. For example, information contained in a record may include a full name (e.g., full medical name) of an infection type, a short name of the infection type, and/or other information, such as a code (e.g., a number) that may be used to identify the infection type.

[0060] The locations table 340 may include information about one or more locations where, for example, an infection may occur. Examples of locations may include care centers, locations within care centers (e.g., a floor, a grid location on a floor), and/or other locations. The information may include, for example, descriptive information that may be associated with the locations. The information may be stored in one or more records that may be contained in the locations table 340 where a record may represent, for example, a location. Here, information contained in a record may include, for example, a full name associated with the location, a short name associated with the location, and/or a code (e.g., a number) that may be used to identify the location.

[0061] The patient-days table 350 may include patient-days information. The patient- days information may be associated with a particular location. Examples of locations may include care centers, locations within care centers, and/or other locations. The location may be represented by one or more records contained in the locations table 340.

[0062] Information in the patient-days table 350 may be stored in one or more records where a record may represent, for example, a number of patient-days for a particular location and/or a reporting date. Information in a record may include, for example, a reporting date, a location, and/or patient-days information. The reporting date may include, for example, a date and/or time when the patient-days information was determined. The location information may include information that may represent, for example, a location (e.g., a care center, location within a care center) associated with the patient-days information. The location may be represented by one or more records contained in the locations table 340. The patient-days information may include information that may represent, for example, patient-days that may be associated with (1) a period of time relative to the reporting date information and (2) the location information. The patient-days information may include, for example, a number that may represent patient-days. The number may be generated, for example, based on the patient-days formula described above.

[0063] Infection control database 300 may be implemented using a database management system (DBMS). Examples of DBMS's that may be used to implement infection control database 300 may include Microsoft Access, Microsoft SQL Server, Oracle, MySQL, Sybase, PostgreSQL, and IBM DB2. Microsoft Access and Microsoft SQL is available from Microsoft Corporation. MySQL and Oracle is available from Oracle Corporation, Santa Clara, California. Sybase is available from SAP AG, Waldorf, Germany. PostgreSQL is available from PostgreSQL Global Development Group. IBM DB2 is available from IBM Corporation, Armonk, New York.

[0064] A chart system, such as chart system 200, may incorporate an interface that may be used to, for example, control an operation of features that may be provided by the chart system. FIGs. 4A-F illustrate an example interface that may be used with a chart system, such as chart system 200. In chart system 200, the example interface may be incorporated, for example, in infection control chart manager 222.

[0065] It should be noted that the interface illustrated by FIGs. 4A-F is an example of an interface that may be used with a chart system, such as, for example, chart system 200. Other interfaces that may be used with a chart system may be different than the interface illustrated in FIGs. 4A-F. For example, an interface that may be used with the chart system may include components (e.g., widgets) other than components illustrated in FIGs. 4A-F or may be text based (e.g., command-line based). [0066] FIG. 4A illustrates an example interface 420 that may be used to load information contained in one or more workbooks 216, 218, 220 into chart system 200. The loaded information may be used by chart system 200 to generate one or more charts 230. The loaded information may be stored in infection control database 300.

[0067] Referring to FIG. 4A, interface 420 may include provisions for (1) specifying a path name associated with a file that may contain a workbook 216, 218, 220; (2) providing an indication to load information from the workbook 216, 218, 220 into infection control database 300; (3) indicating a status that may be associated with loading the information; (4) providing an indication to store the information into the infection control database 300; and/or (5) displaying messages. [0068] The provisions for specifying a path name associated with a file containing a workbook 216, 218, 220 may include, for example, an edit box 422 that may be used to specify text that may represent the path name. Here, a user may specify the path name, for example, by entering text that represents the path name into the edit box 422.

[0069] The provisions for providing an indication to load information from the workbook 216, 218, 220 into infection control database 300 may include, for example buttons 423 and 425. Specifically, button 423 may be used to provide an indication that information from one or more workbooks 216, 218, 220 are to be loaded, for example, into storage. Button 425 may be used to provide an indication that the loaded information is to be stored in infection control database 300. Buttons 423 and 425 will be described in more detail below. [0070] The provisions for indicating a status that may be associated with loading the information from the workbook 216, 218, 220 into infection control database 300 may include a text box 424 which may display, for example, text related to the status (e.g., error information). The provisions for displaying messages may include a text box 426 that may display text related to the messages. [0071] Operationally, a user may load information from a workbook 216, 218, 220 by (1) specifying a path name of a file containing the workbook 216, 218, 220 in edit box 422 and (2) selecting (e.g., pressing, clicking) button 423. Selecting button 423 may provide (e.g., generate) an indication that the workbook 216, 218, 220 is to be loaded. The indication may be sent to infection control chart manager 222. [0072] Infection control chart manager 222 may acquire (e.g., receive, read) the indication (e.g., a message, a calling of a callback routine). In response to receiving the indication, infection control chart manager 222 may access the file specified in edit box 422 and acquire information in a workbook 216, 218, 220 contained in the file. Infection control chart manager 222 may process the acquired information which may include, for example, checking a quality and/or an integrity of information and/or storing the information in primary storage 130 and/or secondary storage 150.

[0073] If an error condition is encountered, infection control manager 222 may provide a message in text box 424 that may report the error condition. For example, if infection control manager 300 cannot locate the file containing the workbook 216, 218, 220 using the information specified in edit box 422, the infection control manager 222 may indicate that the file cannot be found in text box 424. Also, for example, one or more errors that may be associated with acquiring the information from the workbook 216, 218, 220 (e.g., a file read error, workbook format error) may be reported by infection control manager 222 in text box 424. In addition, for example, if infection control manager 222 detects that the quality and/or integrity of the information is compromised (e.g., does not meet certain predefined criteria) a message may be reported in text box 424 by infection control manger 222 that may indicate such. [0074] After information contained in one or more workbooks 216, 218, 220 is loaded, the user may select button 425. Selecting button 425 may provide an indication that the information is to be stored in the infection control database 300. Infection control chart manager 222 may acquire the indication and store information acquired from the one or more workbooks 216, 218, 220 into infection control database 300. After storing the information in the infection control database 300, infection control manager 222 may display a message in text box 426 which may indicate that the information has been stored in infection control database 300.

[0075] FIG. 4B illustrates an example interface 430 that may be used to specify patient- day information that may be used when generating one or more charts 230. The specified patient-day information may be associated with a reporting date. Referring to FIG. 4B, interface 430 may include provisions for (1) specifying a reporting date; (2) specifying patient-days for one or more locations; and/or (3) providing an indication to store the specified reporting date and patient-day information.

[0076] The provisions for specifying a reporting date may include a combo box 432. A list associated with the combo box 432 may be populated based on various criteria, such as, for example, reporting periods associated with the patient-days information.

[0077] The provisions for specifying patient-days associated with one or more locations may include one or more text boxes 433 where a text box 433 may be used to specify patient- days information for a particular location. For example, a location may include a care center, such as a hospital. A text box 433 may be used by a user to specify patient-days information associated with the care center. [0078] The patient-days information specified in text boxes 433a-b may be associated with the reporting date specified in combo box 432. Thus, for example, suppose that the reporting date specified in combo box 432 is "September 2012". The patient-days information specified in text box 433a may be a number of patient-days for a particular location in the month of September of the year 2012.

[0079] The provisions for providing an indication to store the specified reporting date and patient-day information may include button 434. Selecting button 434 may provide an indication that the patient-day information specified in text boxes 433a-b and the reporting date specified in combo box 432 are to be stored. The specified information may be stored, for example, as a record that may be added to patient-days table 350.

[0080] Operationally, a user may specify a reporting date associated with patient-days in combo box 432 and a number of patient days associated with a particular location in a text box 433. After the reporting date and number of patient-days are specified, the user may select button 434. Selecting button 434 may provide an indication that the number of patient-days for the specified reporting date is to be stored in the infection control database 300. The indication may be provided to infection control chart manager 222.

[0081] Infection control chart manager 222 may acquire the indication and store patient- day information specified in one or more text boxes 433 in infection control database 300. Further, the location associated with the specified patient-day information and/or the reporting date specified in combo box 432 may be stored in the infection control database 300. [0082] Chart system 200 may include an interface that may be used to update information used for generating a chart 230. The information may be stored, for example, in infection control database 300. Portions of the information may be supplied from one or more workbooks 216, 218, 220. The updated information may be supplied, for example, by a user. [0083] FIG. 4C illustrates an example of an interface 440 that may be used to load and/or update information that may be used to generate one or more charts 230. The information may be based on information that may be contained in one or more workbooks 216, 218, 220 and/or infection control database 300. Referring to FIG. 4C, interface 440 may include, for example, an information display area 442, combo boxes 443, 444, and/or buttons 445, 446 447. [0084] The information display area 442 may display information that may be used to generate the charts 230. The information may be organized, for example, as a spreadsheet that may contain one or more cells. The cells may organized into one or more rows and one or more columns where a given row may include, for example, columns for a reporting date, a number that may represent a count of infections, and/or a number of patient-days. The row may also include, for example, columns for a count of infections and/or patient-day information that may be contained in infection control database 300.

[0085] The information that is loaded may be associated with a particular infection type and/or a location. Interface 440 may include provisions for specifying an infection type and/or a location associated with the information. The infection type may be specified in combo box 443 and the location may be specified in combo box 444. [0086] Button 445 may be used to provide an indication to load the information based on the infection type and/or location specified by combo boxes 443 and 444, respectively. The information may be based on information contained in one or more workbooks 216, 218, 220 and/or infection control database 300. An option may be provided to enable the loaded information to be updated. For example, an option may be provided to add a row to the loaded information.

[0087] Button 446 may be used to provide an indication that the loaded information is acceptable for generating a chart 230. For example, a user may review the information displayed in information display area 442 and determine that the information is acceptable for use in generating a chart 230. An indication that the information is acceptable may be provided by selecting button 446. As will be described further below, after acquiring the indication, infection control chart manager 222 may store the information in, for example, infection control database 300.

[0088] Buttons 447 may be used to cycle through information that may be used to generate one or more charts 230. Specifically, button 447a may be used to provide an indication to load information for a chart without, for example, specifying infection type and/or location information in combo boxes 443 and 444, respectively. Button 447b may be used to provide an indication that information is acceptable and may be stored in the infection control database 300, such as described above. Button 447c may be used to review the information after it is stored and button 447d may be used to restart at the beginning of the cycle.

[0089] Operationally, an infection type and/or location may be specified in combo boxes 443 and 444, respectively, by a user. The user may select button 445 to provide an indication that information associated with the specified infection type and/or location is to be loaded. Infection control chart manager 222 may acquire the indication and access one or more workbooks 216, 218, 220 and/or infection control database 300 to acquire the information.

Acquiring the information may include, for example, reading and/or receiving the information from the one or more workbooks 216, 218, 220 and/or infection control database 300.

[0090] After acquiring the information, infection control chart manager 222 may display the information in information display area 442. The user may make changes to the information, for example, by entering information into the area 442. After determining the information acceptable, the user may select button 446 to provide an indication that, for example, the information is acceptable. Infection control chart manager 222 may acquire the indication and, in response to the acquired indication, store the information, for example, in infection control database 300.

[0091] FIG. 4D illustrates an example interface 450 that may be used to generate one or more charts 230. Referring to FIG. 4D, interface 450 may include provisions for specifying an infection type and a location that may be associated with a particular chart 230. Interface 450 may also include provisions for indicating, for example, that a chart 230 associated with the specified infection type and location is to be generated and/or provisions for indicating that a series of charts 230 is to be generated. [0092] Specifically, combo boxes 452 and 453 may be used to specify an infection type and a location, respectively, that may be associated with a particular chart 230. Button 454 which may be used to provide an indication to generate the chart 230 associated with the infection type and location specified in combo boxes 452 and 453, respectively. Button 456 may be used to provide an indication to generate a series of charts 230.

[0093] Operationally, for a particular chart 230, an infection type and a location may be specified in combo boxes 452 and 453, respectively. The infection type may include an infection type that may be represented in infection types table 320 (FIG. 3) and the location may include a location that may be represented in locations table 340. After the infection type and location are specified, button 454 may be selected. Selecting button 454 may cause an indication to be generated that may indicate that a chart 230 associated with the specified infection type and location is to be generated.

[0094] Infection control chart manager 222 may acquire the indication and generate the chart 230 based on information that may be contained in, for example, infection control database 300. Specifically, after acquiring the indication, infection control information may acquire information the information from the infection control database 300. The information may include, for example, information that may be contained in the infections table 310 and/or information that may be contained in the patient-days table 350. Afterwards, infection control chart may generate the chart 230 based on the acquired information.

[0095] To generate a series of charts 230, operationally, button 456 may be selected.

Selecting button 456 may cause an indication that a series of one or more charts 230 is to be generated. Infection control chart manager 222 may acquire the generated indication and generate the series of charts 230 based on information contained in, for example, the infection control database 300.

[0096] Specifically, after acquiring the indication, infection control chart manager 222 may acquire information from the infection control database 300. The information may include, for example, information that may be contained in the infections table 310 and/or information that may be contained in the patient-days table 350. Afterwards, infection control chart may generate the series of charts 230 based on the acquired information. The series of charts 230 may include, for example, a predefined set of one or more individual charts 230 that may be associated with predefined infection types and/or locations.

[0097] FIG. 4E illustrates an example interface 460 that may be used to generate one or more charts 230 that may include one or more unit charts. Referring to FIG. 4E, interface 460 may include provisions for (1) specifying an infection type and a location (e.g., of a unit) that may be associated with a particular chart 230, and (2) indicating that a particular chart 230 associated with the specified infection type and location is to be generated. Interface 460 may also include provisions for indicating that a series of charts 230 are to be generated. [0098] Specifically, combo boxes 462 and 463 may be used to specify an infection type and a location, respectively, that may be associated with a particular chart 230. The specified location may be associated with, for example, a particular unit in a care center. Button 464 which may be used to generate the chart 230 associated with the specified infection type and location. Button 466 may be used to generate a series of charts 230 that may be associated with, for example, one or more units and infection types. [0099] Operationally, for a particular chart 230, an infection type and a location may be specified in combo boxes 462 and 463, respectively. The infection type may include an infection type that may be contained in infection types table 320 and the location may include a location that may be contained in locations table 340. [00100] After the infection type and location are specified, button 464 may be selected.

Selecting button 454 may cause an indication to be generated that may indicate that a chart 230 (e.g., unit chart) associated with the specified infection type and location is to be generated. Infection control chart manager 222 may acquire the indication and generate the chart 230 based on information that may be contained in infection control database 300. [00101] Specifically, after acquiring the indication, infection control chart manager 222 may acquire the information from the infection control database 300. The information may include, for example, information that may be contained in the infections table 310 and/or information that may be contained in the patient-days table 350. Afterwards, infection control chart manager 222 may generate the chart 230 based on the acquired information. [00102] To generate a series of charts 230, button 466 may be selected. Selecting button

466 may cause an indication that a series of charts 230 is to be generated. Infection control chart manager 222 may acquire the indication and generate the series of charts 230 based on, for example, information contained in the infection control database 300.

[00103] Specifically, after acquiring the indication, infection control information may acquire the information from the infection control database 300. The information may include, for example, information that may be contained in the infections table 310 and/or information that may be contained in the patient-days table 350. Afterwards, infection control chart manager 222 may generate the series of charts 230 based on the acquired information. The series of charts 230 may include, for example, a predefined set of one or more individual unit charts that may be associated with predefined infection types and/or locations.

[00104] FIG. 5 illustrates an example chart 520 that may be included in charts 230. The chart 520 may be generated, for example, by infection control chart manager 222. Referring to FIG. 5, chart 520 may include a plot of information associated with a particular type of infection for a particular location. The information may be related, for example, to a rate of infections that may occur over a period of time. The rate of infections may be a rate of infections per some number of patient-days (e.g., 1000 patient-days).

[00105] Chart 520 may include a plot 528 that may represent a rate of infections for a given month. The plot 528 may include a series of points where a point may represent a particular rate of infections for a particular month. For example, plot 528 includes point 522. Point 522 may represent a rate of infections for the month of March 2011.

[00106] Chart 520 may include one or more annotations. The annotations may provide information that may be helpful when interpreting the chart 520. For example, annotation 523 is associated with point 522. The annotation 523 indicates that at point 522 the use of bleach wipes was instituted. As can be seen in plot 528, after the use of bleach wipes was instituted the rate of infections decreases for two months. From this information, one might interpret the plot 522 as showing that instituting the use of bleach wipes may have caused a decrease in the rate of infections, when in fact this appears to be a random variation as subsequent points begin to head in the opposite direction. Presenting analytic models in time series, such as depicted in chart 520, may aid in distinguishing between special and common cause variation. It is possible that a negative economic impact of making decisions without using an SPC analytic model may be significant and may lead to decisions that may, for example, actually increase variation and lead to worse outcomes.

[00107] It should be noted that an annotation that may correlate to a point in a chart, such as described above, is an example of a type of annotation that may be included in chart 520 and that chart 520 may include other types of annotations. For example, chart 520 may include one or more annotations related to changes made to a system and/or process over time in relation to a signal of non-random variation of a plot, such as plot 528.

[00108] FIGs. 6A-B illustrate examples of a run chart 620 and a t-chart 640 that may be included in charts 230. The charts 620 and 640 may be generated, for example, by infection control chart manager 222. [00109] A run chart, such as chart 620, may be a helpful analytic tool in situations where, for example, few data points are available. Thus, for example, run charts may be used for unit- level charts where a smaller size of a unit may mean fewer data points. A t-chart, such as chart 640, may be used, for example, when dealing with rate events.

[00110] Referring to FIG. 6A, chart 620 may include a plot that may indicate, for example, an acquisition (e.g., infection, colonization) and a number of days between acquisitions. The acquisitions may be associated with a particular infection type (C. difficile) and/or location (e.g., care center). The plot may also include a series of points where a point may represent an acquisition. For example, point 622 may indicate an acquisition that occurred on March 22, 2011. [00111] A point may be represented in the plot using a symbol that may indicate, for example, a type of acquisition. In chart 620, a triangular- shaped point may be used to indicate an infection and a circular- shaped point may be used to represent colonization. Thus, for example, point 622 indicates an infection and point 623 indicates colonization.

[00112] Chart 620 may include various statistics. For example, line 624 may indicate a median value with respect to the points plotted in the chart.

[00113] Referring now to FIG. 6B, chart 640 may include a plot that may also indicate, for example, acquisitions and number of days between acquisitions (vertical axis). The horizontal axis indicates when an acquisition occurred. For example, point 642 may indicate an acquisition that occurred on December 6, 2012.

[00114] As in chart 620, a point in chart 640 may be represented using a symbol that may indicate, for example, a type of acquisition. In chart 640, a triangular- shaped point may be used to indicate an infection and a circular- shaped point may be used to represent colonization. Thus, for example, since point 642 is circularly- shaped, point 642 may indicate colonization. Also, since point 643 is triangularly- shaped point 643 may indicate an infection. [00115] Chart 640 includes various statistical indications. For example, line 644 may indicate an upper control limit and line 645 may indicate a center line. Chart 640 may include one or more annotations. For example, annotation 646 may indicate that line 644 is an upper control limit and annotation 647 may indicate a value associated with the line 644. [00116] Note that the acquisition at point 642 indicates an acquisition that occurred 16 days from the acquisition immediate preceding it. This is an example of a clinical measure that may be represented in a chart 640. Note that charts, such as charts 230, may represent other measures. These measures may include, for example, clinical and/or non-clinical measures. For example, a chart 230 may represent a measure that may include administrative data such as days between billing errors.

[00117] FIG. 7 illustrates a flow diagram of example acts that may be used to generate one or more charts, such as charts 230. The acts may be performed by one or more computing devices. An example of a computing device that may perform the acts includes computing device 100.

[00118] Referring to FIG. 7, at block 710, an indication to generate the one or more charts from a first set of information may be acquired. The first set of information may be contained in a database, such as, for example, infection control database 300. At least part of the first set of information may include information that may be based on, for example, a second set of information that may be contained in one or more spreadsheet workbooks. [00119] For example, infection control chart manager 222 (FIG. 2) may provide (e.g., display) an interface, such as interface 450 (FIG. 4D) and/or 460 (FIG. 4E). The interface may include one or more provisions that may be used to provide an indication that one or more charts are to be generated from a first set of information that may be contained in infection control database 300. Workbooks 216, 218, and/or 220 may be spreadsheet workbooks and may contain a second set of information. At least part of the first set of information may be based on the second set of information.

[00120] Specifically, the interface may include a button, such as, for example button 454,

456, 464, or 465. Selecting the button (e.g., pressing the button) may cause an indication to be generated. The indication may indicate that one or more charts are to be generated from information contained in, for example, infection control database 300. The indication may include, for example, a message, a call of a callback routine, and/or some other indication. The generated indication may be acquired by infection control chart manager 222.

[00121] For example, if the indication is a message, the infection control chart manager 222 may acquire the indication by receiving the message. Afterwards, the infection control chart manager 222 may determine from the message that the button was selected. If the indication is a callback routine, calling the callback routine may, for example, provide an indication to the infection control manager 222 that the button was selected. The infection control manager 222 may determine that the button was selected by virtue of the callback routine being called. [00122] At block 720 the first set of information is acquired. The first set of information may include, for example, infection and/or patient-days information that may be contained in a database, such as infection control database 300. The infection information may include information that may be associated with one or more occurrences of one or more infections. The patient-days information may include information associated with patient-days. The patient-days may include patient-days associated with one or more locations (e.g., care centers). The first set of information may be acquired in response to acquiring the indication.

[00123] For example, in response to acquiring the indication, infection control chart manager 222 may read infection information and/or patient-days information from infection control database 300. The infection information contained in infection control database 300 may be generated based on information about one or more occurrences of one or more infections that may be contained in one or more workbooks 216, 218, 220. Moreover, the infection information contained in infection control database 300 may be generated based on, for example, patient- days information that may be contained in unit stats database 214 and/or information provided via interface 430 (FIG. 4B).

[00124] The infection information and/or patient-days information that is acquired from infection control database 300 may be constrained based on information that may be provided by, for example, an interface. For example, infection and/or patient-days information acquired from infection control database 300 may include infection and/or patient-days information associated with (1) an infection type that may be specified in combo boxes 452 and/or 462, and/or (2) a location that may be specified in combo boxes 453 and/or 463. [00125] At block 730, one or more charts may be generated based on the acquired first set of information. For example, suppose that the first set of information includes infection and patient-days information. Further, suppose that infection control chart manager 222 acquires the first set of information from infection control database 300. After acquiring the first set of information, infection control chart manager 222 may generate charts 230 and/or 232 based on the acquired first set of information. [00126] Specifically, for a chart 230, in interface 450 an infection type and a location may be specified in combo boxes 452 and 453, respectively. Afterwards, button 454 may be selected to generate an indication that a chart 230 is to be generated. Infection control chart manager 222 may receive the indication, acquire infection and patient-day information from infection control database 300. The acquired information may be associated with the specified infection type and location. After acquiring the information from infection control database 300, infection control chart manager 222 may generate a chart 230 that may be associated with the specified infection type and location.

[00127] In interface 460, an infection type and location may be specified in combo boxes

462 and 463, respectively, and button 464 may be selected to generate an indication that a chart 230 (e.g., a unit chart) is to be generated. Infection control manager 222 may receive the indication, acquire infection and patient-day information, such as described above, and generate a chart 230 that may be associated with the specified infection type and location.

[00128] After a chart, such as, for example, chart 230, is generated, the chart may be distributed and analyzed. An action may be taken based on the analysis. For example, suppose a chart 230 is generated, such as described above, where the chart 230 is a unit chart that contains various annotations and shows a decrease in a number of days between acquisitions of infections in a particular unit. The generated chart 230 may be distributed to the unit. In response to data represented in the chart 230, unit staff and/or management may take various actions (e.g., modify existing procedures, test new changes, discuss improvement strategies with front-line staff, institute new procedures) to increase the number of days between acquisitions. An example of a value that may be associated with the generated chart 230 may be that actions taken that may change a system and/or process may be noted on the chart 230 and may be monitored in real time to determine whether the changes are leading to improvements.

[00129] It should be noted that a third set of information may be acquired and the first set of information and/or the second set of information may be modified based on the acquired third set of information. The modified first set of information and/or second set of information may be stored.

[00130] Specifically, the third set of information may be acquired, for example, via an interface, although the third set of information may be acquired from other sources, such as, for example, a file and/or in a message. The modification may include, for example, changing information in the first and/or second set of information, adding information to the first and/or second set of information, and/or otherwise modifying the first and/or second set of information, the modified information may be stored, for example, in a file and/or database.

[00131] For example, suppose computing device 100 loads information from workbook

216 into primary storage 130 and displays the loaded information in interface 440. A user may enter information via the interface 440 by selecting (e.g., clicking on) a cell contained in information display area 442 and entering the information. The information in the workbook 216 may be modified based on the information entered by the user. Computing device 100 may store the modified workbook 216 in primary storage 130 and/or secondary storage 150. For example, the modified workbook 216 may be stored in a file contained in secondary storage 150 and/or infection control database 300 which may be contained in secondary storage 150. [00132] FIGs. 8A-B illustrate a flow diagram of example acts that may be used generate one or more charts, such as, for example, charts 230. The acts may be performed by one or more computing devices. An example of a computing device that may perform the acts includes computing device 100.

[00133] Referring to FIG. 8 A, at block 810, patient information may be acquired. For example, the patient information may be contained in patient data repository 202 and may include patient information, such as described above. Computing device 100 may acquire the information by reading the information from the patient data repository 202.

[00134] At block 815, patient-days information may be generated, for example, based on the acquired patient information. At block 820 the patient-days information may be stored. For example, after acquiring the patient information, computing device 100 may generate patient- days information, for example, based on the acquired patient information. Computing device 100 may store the generated patient-days information in unit stats database 214 and/or infection control database 300.

[00135] At block 825, infection information may be acquired. For example, the infection information may be contained in infection data repository 204 and may include information about infections, such as described above. The infection information may be acquired by computing device 100 by, for example, reading the infection information from the infection data repository 204.

[00136] At block 830, one or more spreadsheet workbooks may be generated based on, for example, the acquired infection information. For example, computing device 100 may generate one or more spreadsheet workbooks from infection information acquired at block 825.

[00137] At block 835 (FIG. 8B), information may be loaded from the generated spreadsheet workbooks. For example, computing device 100 may load workbook information from the spreadsheet workbooks generated at block 830. The workbook information may be loaded into storage, such as, for example, primary storage 130 and/or secondary storage 150.

[00138] Note that the workbook information may be loaded in response to an indication that may be acquired by computing device 100. For example, suppose workbook 216 is generated based on information that may be associated with occurrences of C. difficile type infections that may have occurred at multiple locations. Further, suppose that the generated workbook 216 is stored in a file contained in secondary storage 150. Computing device 100 may display interface 440. A user may specify the infection type and a location via the interface 440. Afterwards, the user may select button 445. Selecting button 445 may generate an indication that information associated with the infection type and the location is to be loaded. Specifically, computing device 100 may acquire the indication and, in response to acquiring the indication, (1) read information associated with the specified infection type and location from the workbook 216 contained in the file and (2) load the information into, for example, primary storage 130. [00139] At block 840, the loaded workbook information may be stored. The information may be stored, for example, in a database. For example, after loading the information from the workbooks, computing device 100 may store the loaded information and/or information that may be based on the loaded information in, for example, infection control database 300. [00140] At block 845 an indication to generate one or more charts may be acquired. For example, infection control chart manager 222 may provide an interface, such as interface 450, that may include a button, such as button 454 or 456. The button may be used to generate an indication that the one or more charts 230 are to be generated. The generated indication may be acquired by the infection control chart manager 222. [00141] For example, the button may be selected, such as described above. Selecting the button may cause a message to be generated. OS 132 may process the message and in turn call a callback routine associated with infection control chart manager 222. The callback routine being called may provide an indication to infection control chart manager 222 that one or more charts 230 are to be generated. [00142] At block 850, one or more charts may be generated, for example, based on the stored workbook information and/or patient-day information. For example, suppose workbook information and patient-days information are stored in infection control database 300. Infection control chart manager 222 may acquire (e.g., read) the stored workbook information and/or patient-days information from the infection control database 300 and generate one or more charts 230 based on the acquired stored workbook information and/or patient-days information. The charts 230 may be generated in response to the infection control chart manager 222 acquiring an indication that the charts 230 are to be generated. The indication may be provided via an interface, such as interface 450.

[00143] The generated charts may be distributed and/or analyzed. Distribution may include forwarding the charts to various units that may analyze the charts. A unit may include, for example, a care center, a sub-division within a care center, and/or entities that may be defined as a unit, such as described above. Analysis may include, for example, reviewing the charts to identify trends.

[00144] One or more actions may be taken based on one or more analyses of the generated charts. For example, an analysis of one or more of the generated charts may show a trend that may suggest that certain procedures and/or practices may need to implemented and/or modified. Action may be taken to implement and/or modify the procedures and/or practices.

[00145] Techniques described herein may be used to generate one or more reports that may be based on rates of patients developing various conditions after receiving certain treatments. For example, techniques described herein may be used to generate one or more reports that may show (1) a rate of patients developing acute kidney injury after antibiotic therapy with differing antibiotics, (2) a rate of patients developing a low white blood cell count after receiving a particular antibiotic, and/or (3) a rate of acute renal failure in patients admitted to select ICUs or receiving intensive treatment for congestive heart failure. Also techniques described herein may be used, for example, on pharmacy interventions. Here, for example, reports may be generated that may show pharmacist therapeutic interventions in general or for specific drugs on a unit or care center- wide basis. [00146] The foregoing description of embodiments is intended to provide illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, while a series of acts has been described above with respect to FIGs. 7 and 8A-B, the order of the acts may be modified in other implementations. Further, non-dependent acts may be performed in parallel.

[00147] Also, the term "user", as used herein, is intended to be broadly interpreted to include, for example, a computing device (e.g., fixed computing device, mobile computing device) or a user of a computing device, unless otherwise stated. [00148] It will be apparent that one or more embodiments, described herein, may be implemented in many different forms of software and/or hardware. Software code and/or specialized hardware used to implement embodiments described herein is not limiting of the invention. Thus, the operation and behavior of embodiments were described without reference to the specific software code and/or specialized hardware— it being understood that one would be able to design software and/or hardware to implement the embodiments based on the description herein.

[00149] Further, certain features of the invention may be implemented using computer- executable instructions that may be executed by processing logic, such as processing logic 120. The computer-executable instructions may be stored on one or more non-transitory tangible computer-readable storage media. The media may be volatile or non- volatile and may include, for example, DRAM, SRAM, flash memories, removable disks, non-removable disks, flash driver, and/or other storage media.

[00150] No element, act, or instruction used herein should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article "a" is intended to include one or more items. Where only one item is intended, the term "one" or similar language is used. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise.

[00151] It is intended that the invention not be limited to the particular embodiments disclosed above, but that the invention will include any and all particular embodiments and equivalents falling within the scope of the following appended claims.

Claims

CLAIMS What is claimed is:

1. A method comprising:

acquiring an indication to generate one or more charts from a first set of information contained in a database, at least part of the first set information being based on a second set of information contained in one or more spreadsheet workbooks; and

in response to the indication:

acquiring the first set of information from the database, and

generating the one or more charts based on the acquired first set of information.

2. The method of claim 1, wherein the first set of information includes information associated with one or more occurrences of one or more infections.

3. The method of claim 1, wherein the first set of information includes information associated with patient-day information.

4. The method of claim 1, wherein the one or more charts include at least one of a system- level chart and a unit-level chart.

5. The method of claim 1, further comprising:

acquiring an indication to load the second set of information from one or more of the spreadsheet workbooks; and in response to the indication, loading the second set of information into storage associated with one or more computing devices.

6. The method of claim 5, further comprising:

generating the first set of information based on the loaded second set of information; and storing the first set of information in the database.

7. The method of claim 1, further comprising:

acquiring a third set of information via an interface; and

modifying the first set of information based on the third set of information.

8. The method of claim 7, further comprising:

storing the modified first set of information in the database.

9. One or more tangible non-transitory computer readable media storing one or more computer executable instructions for execution by one or more computing devices, the media storing:

one or more instructions for acquiring an indication to generate one or more charts from a first set of information contained in a database, at least part of the first set information being based on a second set of information contained in one or more spreadsheet workbooks;

one or more instructions for, acquiring the first set of information from the database; and one or more instructions for generating the one or more charts based on the acquired first set of information.

10. The media of claim 9, wherein the first set of information includes information associated with one or more occurrences of one or more infections.

11. The media of claim 9, wherein the first set of information includes information associated with patient-day information.

12. The media of claim 9, wherein the one or more charts include at least one of a system- level chart and a unit-level chart.

13. The media of claim 9, further storing:

one or more instructions for acquiring an indication to load the second set of information from one or more of the spreadsheet workbooks; and

one or more instructions for loading the second set of information into storage associated with one or more computing devices.

14. The media of claim 13, further storing:

one or more instructions for generating the first set of information based on the loaded second set of information; and

one or more instructions for storing the first set of information in the database.

15. The media of claim 9, further storing:

one or more instructions for acquiring a third set of information via an interface; and one or more instructions for modifying the first set of information based on the third set of information.

16. The media of claim 15, further storing:

one or more instructions for storing the modified first set of information in the database.

17. A system comprising:

processing logic for:

acquiring an indication to generate one or more charts from a first set of information contained in a database, at least part of the first set information being based on a second set of information contained in one or more spreadsheet workbooks, and in response to the indication:

acquiring the first set of information from the database, and

18. The system of claim 17 wherein the first set of information includes information associated with one or more occurrences of one or more infections.

19. The system of claim 17, wherein the first set of information includes information associated with patient-day information.

20. The system of claim 17, wherein the one or more charts include at least one of a s level chart and a unit-level chart.