Integrated computerized materials management system

[0002] The disclosure relates to a system for managing resources used when providing continuous physiological condition monitoring of a patient. Further, the present invention relates to a system for providing automatic asset location, notification of patient discharge, and usage and maintenance of metering, monitoring, and sensing equipment.

[0003] In hospitals or other healthcare settings, it is frequently necessary to observe critical physiological conditions of a patient, such as temperature, breath rate, pulse, blood pressure, electrocardiogram (ECG) data, and cardiac output. Further, other conditions may be observed, depending on the injury or illness of the patient.

[0004] The physiological condition data is obtained by sensors applied to the patient. These sensors may be connected to a monitor by cables. The monitor may be mounted beside the patients bed and may be connected to a central communications system for recording and monitoring the data. Metering units are also commonly used in healthcare settings to provide specified dosages of medication or fluids to patients. Hospitals or healthcare centers often have hundreds or even thousands of patient meters, monitors, and sensor modules. Typically, each meter, monitor, or sensor module is an electronic device connected to a hospital monitoring network. Such a hospital monitoring network typically has at least one central information center or central communications center connected thereto. The central information center or central communications center allows attendants to view patient data either real time or stored.

[0005] A work order system may be used to keep track of scheduled maintenance of the patient monitors or sensors, based on length of ownership of the meters, sensors, or monitors. However, the meters, sensors, and monitors are not continuously used. Meters, sensors, or monitors are continuously being connected and disconnected from the hospital monitoring network and the patient and lay idle or are transferred to a different location in the healthcare facility.

[0006] The work order system does not keep track of when a meter, sensor, or monitor is in use, where a meter, sensor, or monitor is in use, how long a meter, sensor, or monitor is in use, or the current status of a meter, sensor, or monitor.

[0007] Many of the meters, monitors, and sensors used are self-contained units having microprocessor devices that carry out instructions embedded in software. These units often require periodic software upgrades so that the monitors and sensors can facilitate doctors and medical staff to provide the best possible healthcare available using up to date metering, monitoring, and sensing equipment. When a meter, monitor, or sensor is scheduled for maintenance, the status of that meter, monitor, or sensor is not available to the work order system. Therefore, a maintenance technician may be dispatched to perform scheduled maintenance and arrive at the location of the meter, monitor, or sensor that is schedule for maintenance only to find that it is being used by a patient or that it is in another part of the hospital. Dispatching technicians to perform scheduled maintenance or scheduled upgrades when a meter, monitor, or sensor is not available is an unnecessary expense incurred by the healthcare facility. Furthermore, the difficulties that technicians face in locating meters, monitors, and sensors within a healthcare facility also causes lost man-hours by the technician and further unnecessary expense to be incurred by the healthcare facility.

[0008] Furthermore, although software upgrades are periodically available, it has conventionally been problematic to track what software upgrades have been performed and when. It has also been problematic to schedule periodic software upgrades.

[0009] Therefore, there is a need for an automated system that provides meter, monitor, or sensor maintenance information to technicians to provide schedule maintenance. Also, there is a need for an automatic system that schedules maintenance based on hour meter data rather than length of ownership data. Further, there is a need for an automated maintenance system that provides the status of devices and communicates their availability to a work order system and/or maintenance technicians. Further still, there is a need for an automated system that provides for locating equipment on a hospital network. Further still, there is a need for an automated system that automatically determines the software upgrades that have or have not been made. Further still, there is a need for an automated system of providing usage information to work order system. Further still, there is a need for an automated system which creates a record of when a new meter, monitor, or sensor is plugged into the hospital monitoring network.

[0010] An exemplary embodiment relates to a resource management system. The resource management system includes a first communications network, having a plurality of communication ports. The resource management system also includes a plurality of electronic devices configured to be in communication with the first communications network, each electronic device has an identifier associated therewith. The resource management system also includes a resource manager that is configured to be in communication with the first network and is configured to read the identifier of the electronic devices in communication with the first communications network.

[0011] Another embodiment relates to a hospital monitoring network. The hospital monitoring network includes a plurality of communication ports coupled to the hospital monitoring network, each communication port has a location identifier associated therewith. The hospital monitoring network also includes a plurality of hospital devices configured to be in communication with the hospital monitoring network. Each hospital device has an identifier associated therewith. The hospital monitoring network further includes a server configured to be in communication with the hospital monitoring network. The server is configured to read the identifiers of the hospital devices in communication with the hospital monitoring network via at least one of the communication ports. The server is configured to read the location identifiers of at least one communication port to which the electronic devices are in communication with.

[0012] Yet another embodiment relates to a resource management system. The resource management system includes a first communications network and a second communications network. The resource management system includes a plurality of monitors selectively coupled to at least one of the first communications network and the second communications network. The resource management system further includes a resource manager in communication with both the first communications network and the second communications network. The resource manager is configured to receive monitor information from at least one of the first communications network and the second communications network. The resource manager is configured to receive location information representative of the location of the monitors that are coupled to either of the first communications network and the second communications network.

[0013] Still yet, another embodiment relates to a resource management system. The resource management system includes a first means for communicating and a second means for communicating. The resource management system also includes a plurality of electronic devices selectively coupled to at least one of the first communicating means and the second communicating means. The resource management system also includes a means for managing resources in communication with both the first communicating means and the second communicating means. The managing means is configured to receive location identifiers and electronic device information from at least one of the first communicating means and the second communicating means.

[0014] Further still, another embodiment relates to a method of managing assets. The method includes communicating electronic device information over a first communications network. The method also includes receiving electronic device information from the first communications network by a resource manager. Further, the method includes communicating location information representative of the location of the electronic device over the first communications network and receiving location information from the first communications network by a resource manager.

[0015] The invention will become more fully understood from the following detailed description, taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like parts, in which:

[0016] FIG. 1 is a block diagram of an exemplary embodiment of a healthcare monitoring network.

[0017] Referring to FIG. 1, a block diagram of a hospital monitoring network 10 is depicted. Hospital monitoring network 10 includes a hospital enterprise network 20 which may be an intra hospital communications network or external communications network that is in communication with a plurality of other hospitals, service providers, equipment vendors, or other personnel (including, but not limited to, off-site doctors or healthcare technicians) or entities requiring information available from or provided by a hospital. The information communicated on hospital enterprise network 20 may be retrieved by a user through a browser 30, such as a web browser or other network user interfaces.

[0018] Hospital monitoring system 10 preferably includes a hospital monitoring network 40. Hospital monitoring network 40 may be, in a preferred embodiment, an inter hospital network such as the GE Marquette Unity Network® available from GE Marquette Medical, Inc., Milwaukee, Wis., or any other of a variety of mission critical networks. Further, hospital monitoring network 40 is a communications network that may be an Ethernet network supporting transmission control protocol/internet protocol (TCP/IP) standards or any other applicable communication protocols. In a preferred embodiment, hospital monitoring network 40 may be used to share clinical information between different parts of a healthcare facility, such as, but not limited to cardiology, patient monitoring, hospital information, and laboratory equipment. Further, in a preferred embodiment, hospital monitoring network 40 may be built using industry-standard equipment, for example IEEE 802.3 (Ethernet) cabling. A plurality of electronic devices and more particularly hospital devices such as, but not limited to, computers, patient monitors, patient meters, and patient sensors, and other communication and interfacing devices.

[0019] Hospital monitoring network 40 is preferably configured to be connected with a plurality of communication devices, such as, but not limited to, a telemetry tower 45, a patient monitor 50, a configured monitor 55, and a monitoring interface device 60. Further, in a preferred embodiment, computer and computer server devices such as a central station 65, a work order system 70, a managed use system 75 and a resource manager 80 may be in communication with hospital monitoring network 40. Further, any number of or variety of computer systems may be coupled to and in communication with hospital monitoring network 40.

[0020] Telemetry tower 45 preferably has a plurality of receivers. In a preferred embodiment, telemetry tower 45 has 16 receivers. Further, in a preferred embodiment telemetry tower 45 may be an APEX® telemetry transmitter available from GE Marquette Medical Systems, Inc. Associated with telemetry tower 45 is an antenna 47 configured to transmit and receive preferably radio frequency (RF) or ultra high frequency (UHF), or any other appropriate electromagnetic signal 49. Telemetry tower 45 is therefore in communication with a plurality of mobile clinical devices 46, each mobile clinical device has an antenna 48 associated therewith configured to transmit and receive signals 49 to and from telemetry tower 45. Therefore, signals to and from mobile clinical device 46 are communicated on hospital monitoring network 40 through telemetry tower 45.

[0021] Patient monitor 50 may be coupled to hospital monitoring network 40. Patient monitor 50 may be a patient monitor that tracks and displays patient sensor and monitor data for a single patient. Patient monitors of this type include but are not limited to the Solar 8000 available from GE Marquette Medical Systems, Inc.

[0022] Patient monitor 50 may be coupled to and in communication with a multiplexing device 51 such as Octanet available from GE Marquette Medical Systems, Inc. Multiplexing device 51 provides a plurality of ports, preferably eight (8) ports whereby a plurality of patient monitoring devices may be coupled thereto. Multiplexing device 51 acts to bring data from a plurality of patient monitoring and sensing devices into one device to be communicated to a patient monitor 50, or the like.

[0023] Patient monitor 50 may be configured to include a transportation acquisition module (TRAM®) available from GE Marquette Medical Systems, Inc. that is configured to travel with the patient when the patient moves throughout the hospital or healthcare facility. Multiplexing device 51 has a plurality of ports which are preferably coupled to the plurality of patient meters, monitors, or sensors 52 which may be any of a plurality of patient metering, monitoring, and sensing devices including but not limited to ventilators, gas analyzers, intervenes pumps, other bedside clinical devices, or other devices including those which are not necessarily medical devices per se.

[0024] Each device 52 preferably has a device identification cable adapter (DIDCA™) 53 coupled thereto. Each DIDCA 53 is configured to return a unique digital identifiers (e.g., identification number) that is unique to each device 52. In the present embodiment, the number is unique to each DIDCA and is correlated to devices 52. Each DIDCA automatically identifies a device as soon as it is connected to the network.

[0025] Each device 52 is configured to retrieve information directly or indirectly from patient clinical bedside devices. Such information is communicated through DIDCA 53 to multiplexing device 51 along with the unique identification number associated with device 52. Multiplexing device 51 collects data from the plurality of devices 52 and communicates that information to a patient monitor 50. Patient monitor 50, preferably has a unique Ethernet address and is configured to communicate monitor information along hospital monitoring network 40.

[0026] Configured monitors 55 may also be connected and in communication with hospital monitoring network 40. Configured monitors are preferably Eagle 4000 or Eagle 3000 configured monitors available from GE Marquette Medical Systems, Inc., or possibly other configured monitors that are capable of communicating patient information along the hospital monitoring network 40. Configured monitors 55 are full featured vital sign monitors that offer software and hardware options which allow it to be configured to meet the needs of specific care units. For example, in a preferred embodiment configured monitor 55 may be used to monitor basic standard of care parameters and can be expanded to include a plurality of other parameters such as, but not limited to invasive pressures, thermal dilution, cardiac output, electrocardiogram analysis among other parameters. In an alternative embodiment, configured monitors may be wireless configured monitors 56 in communication with a network interface, such as Ethernet interface 57, and communicating via a wireless Ethernet signal 58.

[0027] A network interface device 60 may also be coupled to and in communication with hospital monitoring network 40. Network interface device 60, like configured monitors 55, patient monitor 50 and telemetry tower 45, has its own unique Ethernet address used for communicating along hospital monitoring network 40. Network interface device 60 much like multiplexing device 51 has a plurality of communication ports, in a preferred embodiment eight (8) ports. In a preferred embodiment, network interface device 60 may preferably be an Octacomm, available from GE Marquette Medical Systems, Inc. Network interface device 60 serves as an interface between hospital monitoring network 40 and up to eight (8) bedside devices, such as but not limited to ventilators, infusion pumps, and vital sign monitors. Network interface device 60 acts to bring data together from a plurality of patient monitoring devices 62. Patient monitoring devices 62 may be the same as or different than devices 52 that are connected to multiplexing device 51. In a preferred embodiment, devices 62 have DIDCAs 63 coupled to and associated with devices 62. Therefore, each device 62 has associated therewith by DIDCA 63 a unique identification number. Similar to devices 52, patient monitoring information and data is collected via devices 62 and broadcast through DIDCAs 63 to network interface device 60 patient data is then collected and brought together in network interface device 60 where it can be communicated to hospital monitoring network 40 and associated with the unique Ethernet address of network interface device 60.

[0028] A central station 65 may be coupled preferably to both hospital monitoring network 40 and hospital enterprise network 20. Central station 65 may preferably be a PRISM™ clinical information center (CIC) available from GE Marquette Medical Systems, Inc. CIC is a PC based central station running under Windows NT®. The CIC provides centralized monitoring of patients that are connected to Solar® monitors, Eagle® monitors and APEX® telemetry transmitters. CIC may be configured to display up to four (4) real-time wave forms per patient for up to sixteen (16) patients. A display window is provided on the CIC for each patient. The display window shows wave forms and vital information in digital form, including, but not limited to patient name, bed number, arrhythmia messages, alarms on/off, alarm message line, heart rate, PVC count, transmitter number, ECG lead label, pacemaker status, ST measurement, graph status, additional parameter numerics from Solar or Eagle monitors and date/time. Any number of central stations may be in communication with hospital monitoring network 40. Central station 65 retrieves information communicated along hospital monitoring network 40 from any of the number of monitors, sensors and devices that are in communication with hospital monitoring network 40. Central station 65 has the ability to display, record, and/or communicate any of the information communicated along the network. For example, a central station 65 may be used in a certain hospital section, department, or ward, so that a plurality of patients can be simultaneously monitored at a centralized location, such as, but not limited to a nurses station.

[0029] Optionally a managed use server or computer system 75 may be coupled to and in communication with hospital monitoring network 40. Managed use system 75 further includes a modem 76 coupled thereto for communications across a standard telephone line or other communication lines such as coaxial lines, fiberoptic lines, cellular, radio or satellite signal lines. Managed use system 75 is preferably used to communicate with a hospital equipment provider, or a service provider for a hospital equipment supplier. Managed use system 75 makes it possible for a hospital or healthcare facility to use equipment strictly on a pay-per-use system, whereby the hospital pays a medical equipment provider only for the time for which the medical equipment is being used. Managed use system 75 collects information from the hospital monitoring network communicates that information via modem 76 to a service provider who processes the information and sends out a bill, based on the information collected, to the hospital.

[0030] A work order system 70 database may be coupled to the hospital enterprise network 20. In a preferred embodiment, work order system 70 is WOSYST® for Windows® available from St. Croix Systems, Inc., St. Croix Falls, Wis. Work order system 70 is configured to schedule maintenance based on length of ownership of devices such as telemetry tower 45, patient monitor 50, configured monitor 55, network interface device 60, Octanet 51, monitors or sensors 52 and monitors or sensor 62, and any other devices that may be coupled to network 40. Data input to work order system 70 is conventionally input by hand using little or no automation. Work order system 70 provides a capital equipment database system however work order system 70 does not provide real-time location of and management of hospital assets.

[0031] In a preferred embodiment, a resource manager 80 is coupled to both hospital monitoring network 40 and hospital enterprise network 20. Resource manager 80 is preferably a PRISM® integrated computerized maintenance management system (ICMMS) available from GE Marquette Medical Systems, Inc. In a preferred embodiment the ICMMS software is configured to run under Windows NT®. Resource manager 80 is configured to reduce the time and complexity associated with preventive and schedule maintenance of patient monitoring equipment. Resource manager 80, which in one embodiment is a computer server running ICMMS software, preferably provides automatic asset location, notification of patient discharge and use metering of equipment that is connected to the hospital monitoring network 40. In a preferred embodiment, each patient room, or other location throughout the hospital or healthcare facility have communication ports. The communication ports are configured to be connected to hospital monitoring network 40 and are further configured to connect to and be in communication with any of a plurality of patient devices including but not limited to telemetry tower 45, patient monitor 50, multiplexing device 51, patient monitor and sensing devices 52, configured monitors 55, network interface device 60, patient monitoring devices 62. In a preferred embodiment, each communication port has digital information (e.g., location tag or location identification) associated therewith for communicating across network 40.

[0032] Resource manager 80 may preferably be configured to identify the first time that any new equipment coming into the hospital is plugged into hospital monitoring network 40. Resource manager 80 therefore keeps a record of the new equipment thereafter. When it is time for equipment to undergo routine preventive maintenance, a technician is alerted that maintenance is needed and further is informed of the location of the specific device in the hospital by way of a location identifier associated with the communication port with which the device communicates. Furthermore, resource manager 80 may identify if the device needing maintenance is being used by a patient, and when that patient will be discharged or no longer needs to use the device therefore freeing up its availability for service, this saves precious work time of technicians.

[0033] Resource manager 80 provides automatic asset location. In hospitals and healthcare facilities, equipment is often moved from its assigned location thereby causing time consuming delays as technicians search for the device throughout the hospital or healthcare facility. Resource manager 80 allows users to provide a query to the system to ascertain the exact location, and the current software level of most devices connected to hospital monitoring network 40.

[0034] In a preferred embodiment, work order system 70 can signal a paging system 83 to notify a technician, carrying a pager 84, when a piece of equipment is schedule for preventive maintenance or to notify him or her when specified equipment is no longer in use by a patient.

[0035] Resource manager 80 preferably has a modem 82 coupled thereto. Modem 82 allows a user to dial into and connect with resource manager 80. A user may then be able to view information available through resource manager 80 and in a preferred embodiment a user will be able to view information stored in work order system 70.

[0036] Resource manager 80 also facilitates use metering that provides hour meter data, that is data based on the time a particular device has been in use. Not only does this provide for simple pay-for-use accounting, but it also provides for accurate assessment of service requirements for each device thereby providing efficiency in the use of a technician's time as compared with a conventional calendar-based maintenance schedule.

[0037] Resource manager 80 preferably receives device information including, but not limited to location, unique identification number (physical Ethernet address, a serial number, or a DIDCA number) hardware revisions, software revisions, software error logs, device usage (patient admitted), and other device status like internal temperatures, etc.

[0038] Resource manager 80 provides automation of scheduled maintenance and other tasks including, but not limited to, device monitoring, providing software and hardware upgrades, and automated pay-per-use billing. Further, resource manager 80 is able to communicate across hospital enterprise network 20 and provide data directly to work order system 70 therefore providing work order system 70 with an automated method of gathering input data. Furthermore, resource manager 80 allows hospital equipment to be readily located, or if no longer on the network, resource manager 80 can provide information as to where and when the equipment was last used. This information may be provided to a user through a browser such as browser 30 in communication with hospital enterprise network 20, or in an alternative embodiment coupled to and in communication with hospital monitoring network 40.

[0039] While the preferred embodiment refers to a resource manager coupled to two communication networks, the present invention may also be applied to a resource manager coupled to a single communications network.

[0040] Further, while the preferred embodiment refers to patient meters, monitors, or sensors, this phrase is to be interpreted broadly. The embodiment can encompass those situations in which any electronic device is coupled to and in communication with a communications network.

[0041] Further still, those who have skill in the art will recognize that the present invention is applicable with many different hardware configurations software architectures, communications protocols, and organizations or processes.

[0042] While the detailed drawings, specific examples, and particular formulations given describe preferred embodiments, they serve the purpose of illustration only. The materials and configurations shown and described may differ depending on the chosen performance characteristics and physical characteristics of the communication networks. For example, the type of communications network or communication protocols used may differ. The systems shown and described are not limited to the precise details and conditions disclosed. Furthermore, other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the preferred embodiments without departing from the spirit of the invention as expressed in the appended claims.