JP2005514078A - Apparatus and method for managing patient data - Google Patents

Abstract

  Devices (10, 44, 44 ', 100, 200) and methods for patient point of care data management are provided. Patient point-of-care data is obtained in real-time or near real-time, with subscribers (34, 36) on the local computer display screen (48, 48 ', 118), the remote computer display screen (48, 48', 118) or both. ) Or available to authorized users. In some embodiments, data related to multiple patients is available and some may be viewed simultaneously on the computer display screen (48, 48 ', 118). In some embodiments, patient practice data from multiple hospitals (24, 26) may be available.

Description

  The present disclosure relates generally to healthcare data systems, and more particularly to an apparatus and method for collecting and distributing patient point-of-care data. More particularly, the present disclosure relates to a method and apparatus for managing patient point-of-care data.

This application is incorporated by reference in US Provisional Patent Application No. 60 / 291,043, filed May 15, 2001, and US Provisional Patent Application No. 60 / 327,496, filed October 5, 2001. And claims the priority under 35 USC 119 (e), the disclosures of each of which are incorporated herein by reference.

  Data systems have been developed that provide information to various groups within the medical industry. That is, such data systems include systems that collect, process, and store certain information about the patient. For example, data systems used in the health insurance industry have been developed for the purpose of collecting, storing and processing patient information such as demographic information, diagnostic information, and treatment information. That information may be used by the insurance provider to make and track payments made on behalf of the patient as part of the patient's benefit plan.

  As is well known, hospitals may also maintain a data system used in providing patient care within the hospital itself (as opposed to providing data to an external party such as an insurance company). . With respect to such a data system, a hospital may maintain a database that includes information related to individual patients and nursing provided by the hospital.

  Many of the traditional data collection and management systems used in medical environments provide collection, storage, and processing of patient point-of-care data in real-time or near real-time across many patients in a hospital or a single hospital Not done. That is, some health systems may be useful for collecting and maintaining patient treatment data, but such systems are used in this disclosure to sense data from sensors associated with the patient and to treat the patient. It does not include the ability to collect “clinical point data” for patients, including device data from the device being used. For example, sensing data (eg, heart rate, blood pressure, respiratory rate, body temperature, or other types of sensed data) and device data (eg, temperature in an infant incubator) are usually not used by insurance companies, so insurance The data system used by the company does not collect it. Moreover, certain hospital data systems have been useful in collecting certain types of sensing data, but such systems are designed to be used only within one hospital, resulting in other hospitals. Does not contain information about patients.

  According to the present disclosure, the data collection and management system is configured such that an authorized user or subscriber can access patient point-of-care data online, in real time or near real time. In disclosed embodiments, patient point-of-care data may be collected from patients and / or devices located at multiple medical facilities. In other disclosed embodiments, clinical site data is collected from multiple patients and / or devices located at a single medical facility. In embodiments where clinical site data is collected from multiple medical facilities, the system includes a central database that stores clinical site data from each facility. In some embodiments, the system is configured to allow access to a database of point-of-care data over the Internet.

  Further in accordance with the present disclosure, a method for providing sensed patient data to a subscriber includes providing a database that collects patient practice data online from a plurality of patients in a plurality of hospitals. Each patient and each hospital are identified by their respective identification codes. The method includes collecting and classifying sensed patient data. The method further includes allowing the subscriber online access to a database of point-of-care data.

  Further, according to the present disclosure, a method of operating a medical data system receives patient point of care data associated with a plurality of patients located in a plurality of hospitals, and the received patient point of care data is stored in a database. Including storage. A portion of the patient practice data is generated by a plurality of sensors that sense at least one physical characteristic each associated with each patient. In certain embodiments, the method further includes entering at least a portion of the patient practice data into the database. The method further includes retrieving at least a portion of the point-of-care data from the database upon receipt of the request from the subscriber. The method also includes transmitting sensed patient data to the subscriber.

  In accordance with the present disclosure, a medical data system includes a communication device that transmits and receives patient practice data, a storage device that holds a patient database, and a process that is electrically connected to both the communication device and the storage device. A unit. The medical data system also includes a memory device that is electrically connected to the processing unit. The memory device has a plurality of operating instructions stored therein, and when executed by the processing unit, the processing unit receives patient point-of-care data associated with a plurality of patients located in a plurality of hospitals. Operate the communication device. A portion of the sensed patient practice data is generated by a plurality of sensors each sensing physical characteristics associated with each patient. Further, the plurality of instructions, when executed by the processing unit, causes the processing unit to enter patient point of care data into a database. The plurality of instructions, when executed by the processing unit, causes the processing unit to retrieve from the database at least a portion of the patient practice data upon receipt of the request from the subscriber. Further, when the plurality of instructions are executed by the processing unit, the processing unit causes the communication device to operate to transmit the retrieved patient practice data to the subscriber.

  Furthermore, according to the present disclosure, a patient care apparatus for use in a medical facility having a network of computer devices is provided. The patient care apparatus includes a support structure, a computer coupled to the support structure, and a mattress supported by the support structure. The mattress has a surface on which the patient lies. The computer receives patient practice data including data representing at least one vital sign of the patient. The computer is connected to the network and sends patient point of care data to at least one of the network's computer devices.

  Also according to the present disclosure, a patient care apparatus includes a support structure, a mattress supported by the support structure, a computer coupled to the support structure, and a camera coupled to the support structure. The computer has a display screen. The image from the camera is shown on the first part of the display screen, and the patient practice data is shown on the second part of the display screen.

  In some embodiments, images from the camera can be accessed over the Internet for viewing on a remote computer display screen. In another embodiment, the computer is configured such that images from the camera can be emailed to an email address. In an exemplary embodiment, when the computer receives an appropriate command, environmental data such as temperature or humidity associated with the patient space around the mattress, personal patient data, stored patient radiographs, Stored patient ultrasound images, stored laboratory test results, recorded video messages, control unit for listening to recorded voice messages, control unit for sending e-mail, for video conferencing Control section for browsing the internet, data on manufacturer sales or service, list of supplies related to patient care, schedule of patient appointments, pharmacotherapy data including dosage data, and The type of clinical site data of one or more patients supported on other patient care devices Any one or more of the pressure data is shown on other parts of the display screen. Any or all of these other types of data may be used to read into a central database that can be accessed online by authorized users or subscribers.

  In accordance with the present disclosure, a patient care system includes a patient support device having a surface on which a patient lies and a computer corresponding to the patient support device. The computer has a reading device and a display. Further, the computer is configured to store patient practice data. Patient practice site data includes a first subset of patient practice data and a second subset of patient practice data. The patient care system further comprises a first token and a second token. The computer is configured to allow access to the first subset of patient practice data when the first token is presented to the reader, and the computer is presented to the reader with the second token. It is configured to allow access to a second subset of patient practice data.

  In the illustrated embodiment, the patient care device is an infant thermal support device that can operate as either an infant incubator or a radiation incubator. The illustrated infant heat assist device has a vertical column to which a canopy and a radiant heater are coupled. The column can be extended and contracted to raise and lower the canopy and radiant warmer. The arm assembly is coupled to the lower portion of the column and is rotatable about a vertical axis. The computer is coupled to the end of the arm assembly so that the computer is spaced from the column. The arm assembly includes a plurality of arm portions configured to allow movement of the computer about the column from a first side of the infant thermal support device to a second side of the infant thermal support device.

  Further features will become apparent to those of ordinary skill in the art upon review of the following detailed description of illustrative embodiments illustrating the best mode of carrying out a method and apparatus for managing patient point-of-care data as long as it is currently recognized. right.

=== Detailed Description of Drawings ===
Referring now to FIG. 1, an exemplary embodiment of a patient practice data system 10 including a repository network 12 having several servers such as a hospital interface server 14, an internal data server 16, and a subscriber interface server 18. Is shown. As discussed in further detail below, the hospital interface server 14 communicates with several different hospital networks 24, 26, each associated with several different hospitals 28, 30, and is being treated at the hospital 28, 30. It stores patient point-of-care data related to many patients. The terms “hospital”, “medical facility”, and “facility”, as used in this disclosure, including claims, provide medical care, including hospitals, nursing homes, outpatient surgery centers, clinics, rehabilitation centers, etc. It is intended to cover all types of facilities. Also, as discussed in further detail below, the subscriber interface server 18 communicates with a number of legitimate users or subscribers 34,36. Although only two hospitals 28, 30 and two subscribers 34, 36 are shown in FIG. 1 for simplicity, the repository network 12 may be associated with any number of hospitals with any number of subscribers. Exchanging data with any number of hospital networks is within the scope of this disclosure.

  Each of the servers 14, 16, 18 may be configured as a component of either individual hardware or software. That is, each of the servers 14, 16, 18 along with other commonly used hardware components such as high bandwidth data routers, along with corresponding memory devices (eg, RAM modules, hard drives, or other types of storage devices). ) Including a processing unit (not shown) or the like, may be embodied as a separate (ie, independent) hardware device. The servers 14, 16, and 18 may each be embodied as individual software components that operate as a common part of server hardware similar to that described above. Any combination of the above configurations is within the scope of this disclosure.

  In one exemplary embodiment, the individual hospital networks 24, 26 communicate with the repository network 12 via any type of network that can interconnect the networks 12, 24, 26. For example, the network utilized to enable communication between the individual hospital networks 24, 26 and the repository network 12 may be a global network such as the Internet 32. As will be appreciated, although a specific configuration of networks (ie, the Internet 32) is described in this disclosure and shown in the drawings, other network configurations are also contemplated to be used with this disclosure. For example, the network may be embodied as a unique network such as another global network or alternatively a wide area network (WAN).

  Individual subscribers 34, 36 may also communicate with repository network 12 via a similar network configuration. That is, in the exemplary embodiment described in this disclosure and shown in the drawings, individual subscribers 34, 36 may communicate with repository network 12 over the Internet 32. However, as discussed above, other network configurations, such as other global networks or unique WANs, could be used to allow individual subscribers 34, 36 to communicate with the repository network 12.

  The repository network 12 includes several storage devices 20. The storage device 20 is used to maintain a number of patient databases 22. That is, the repository network 12 communicates with the hospital networks 24, 26 (via the hospital interface server 14) and accumulates data related to patients admitted to each hospital 28, 30. Such data is maintained in the patient database 22 and used by subscribers 34 and 36. In such a configuration, the data server 16 controls the movement of information in and out of the database 22.

  As will be described in more detail below, the above configuration of the data system 10 allows patient data from a relatively large number of hospitals to be stored in real time or near real time. Such accumulated data may be selectively made available to a large number of subscribers 34, 36 for clinical research, routine therapy, and the like.

  Each hospital network includes an internal data server 38, a storage device 40, and an external communication server 42. The internal data server 38 communicates with several devices utilized within the hospitals 28, 30, receives patient care data therefrom and stores it in several databases maintained by the storage device 40. In particular, each hospital 24, 26 utilizes several patient care devices 44 to provide the patient with the necessary care. The patient care device may take the form of any type of device utilized in a hospital or similar nursing facility providing nursing to a patient. For example, patient care device 44 may take the form of an infant incubator, heart-lung machine, EKG, ECG, MRI, X-ray, blood analyzer, or some other type of device commonly used to provide nursing care to a patient. Also good.

  In an exemplary embodiment of a patient care device 44 'described in further detail below with reference to FIGS. 5-25, the device 44' is described in U.S. Patent Nos. 5,453,077, 5,817,002. 5,817,003, 5,759,149, 5,971,913, 5,971,914, 6,022,310, 6,024,694, 6,036,634, 6,049,924, 6,071,228, 6,270,452, 6,296,606, and 6,345,402, and the United States Patent application 09 / 688,528 (filed on October 16, 2000), 09 / 571,449 (filed on May 16, 2000), 09 / 838,789 (April 20, 2001) Application), and 10 / 027,496 (2001) The form of the described type of incubator and warmer December 21 filed). Each patent and patent application mentioned in the above sentence is incorporated herein by reference. That is, the patient care apparatus 44 ′ (for example, an infant incubator) includes a number of sensors (not shown) that collect data related to its operation (hereinafter “apparatus data”). For example, the patient care device 44 'includes sensors that determine the temperature within the device, the rate at which intravenous drugs are administered, the oxygen content of the air within the device, the weight of the patient, and / or the air circulation rate within the device. But you can.

  In addition, several other patient sensors 46 are also utilized to collect patient related data (hereinafter “sensing data”). For example, sensors may be used to measure patient skin and / or internal temperature, patient heart rate and / or respiratory rate, patient blood oxygen level, patient blood pressure, and / or patient water excretion level. Also good. As will be appreciated, some sensors 46 may be integrated with the patient care device 44. For example, in the case of an infant incubator, a temperature sensor that monitors the patient's skin temperature may be integrated with the incubator. That is, certain types of “sensing data” may be characteristic of “device data”.

  Patient data may also be entered manually using some manual input devices such as a personal computer (PC) 48 (hereinafter “manual data”). Manual data may take the form of a patient code such as a patient identification number. Manual data may also take the form of demographic information such as age, gender, race, and other information about the patient that is normally collected when the patient is admitted, such as patient height and weight. In addition to the information collected during hospitalization, manual data may take the form of information collected when a patient is discharged from a hospital or transferred to another facility. If the patient was monitored by a home monitoring system prior to hospitalization, the information collected by this home monitoring system may be entered manually (and if the home monitoring system is communicating with the hospital network, It may be entered directly by the home monitoring system).

  In addition, diagnostic data such as diagnostic codes may be manually entered using the PC 48 to identify the disease or condition that is the reason for treating the patient. Similarly, therapy data, such as a therapy code, may also be entered manually by use of the PC 48 to identify the treatment and / or medication used in treating the patient. As will be appreciated, the diagnostic and treatment codes are provided in generally accepted forms such as the Medicare (Federal) and insurance codes, or any other type of code commonly used in the medical industry. May be.

  The patient data described above is communicated to the hospital's internal data server 38 and stored in one of the databases associated with the storage device 40. As will be appreciated, such data may be communicated within hospitals 28, 30 by use of one or more wired or wireless networks. For example, some of the devices associated with the hospitals 28, 30 such as the PC 48 may be connected to the data server 38 via a wired network (eg, Ethernet) and other configurations such as the patient care device 44 The element may support wireless communication to the data server 38. In addition, other types of devices (eg, personal digital assistants (PDAs) or bar code scanners that scan the patient's annulus) may be used to enter patient data, as well as wired or wireless connections. You may communicate with the data server 38 via.

  Hospital network 24, 26 communication servers 42 communicate patient data held in the hospital database to the repository network 12 via the Internet 32. The communication server 42 It may be configured to communicate with the repository network 12 through the use of any of a number of communication protocols. For example, The communication server 42 “Package” the updated patient data into an email message, You may comprise it as an electronic mail (Email) server which mails to the repository network 12 via the internet 32. FIG. Also, The communication server 42 It may be configured as a file transfer protocol (FTP) or hypertext transfer protocol (HTTP) server configured to transfer files containing patient data to the repository network 12. As will be recognized, Any other communication protocol may be used, including a secure communication protocol that ensures the security of the transmitted information.

  On the other hand, the repository network 12 receives data transferred using the corresponding server configuration from the communication server 42. That is, the hospital interface server 14 of the repository network 12 may be configured similarly to the communication servers 42 of various hospitals and communicate with each other. For example, if the hospital communication server 42 is configured as an email server, the hospital interface server 14 of the repository network 12 is also configured as an email server, thereby enabling the transfer of email messages between the two servers. Also good. Similarly, if any or all of the hospital data server 42 is configured as an FTP and / or HTTP server, the hospital interface server 14 may be configured as such. As will be appreciated, the hospital interface server 14 of the repository network 12 is configured to communicate with the hospital communication server 42 in any number of different protocols to provide flexibility in how the repository network 12 receives data. Also good.

  An internal data server 16 associated with the repository network 12 stores or otherwise processes information received from the patient networks 24, 26 in appropriate fields of the patient database 22 maintained in the storage device 20. For example, the internal data server 16 periodically parses incoming email messages from the hospital networks 24, 26 into appropriate data fields and stores them in one of the patient databases 22. When using an FTP or HTTP transfer protocol, the data server 16 extracts the relevant data from the transferred file and stores it in one of the patient databases 22 as well.

  A subscriber interface server 18 is provided for interfacing with subscribers 34,36. That is, the subscriber interface server 18 authenticates the subscriber to allow access to the database and manages subscriber accounts (adding new accounts, deleting accounts, and / or changing subscription levels), Formatted subscriber query (ie, data request), accessed patient database 22 to fulfill subscriber query (or interface with internal data server 16 to access database 22), and retrieved for subscriber Perform tasks such as formatting the data and sending the requested data to the subscribers 34,36. In one exemplary embodiment, subscriber interface server 18 is configured as a web server that allows interaction between repository network 12 and subscribers 34, 36 via Internet 32.

  Thus, as described in this application, the data system 10 may operate to provide subscribers 34, 36 with real-time or near real-time patient data. In particular, data collected by the hospital networks 24, 26 is first stored in the hospital storage device 40. Specifically, during operation of the patient care device 44, device data generated by the patient care device 44 is transmitted to the storage device 40 via the hospital networks 24, 26 and entered into the associated database. Similarly, sensing data generated by the sensor 46 is also transmitted to the storage device 40 via the hospital network 24, 26 and entered into the associated database. In addition, any data (eg, diagnostic codes and / or treatment codes) entered via the PC or PDA 48 is transmitted to the storage device 40 via the hospital network 24, 26 and entered into the associated database. If the patient is a new patient, initial patient information such as patient identification code and / or demographic information is transmitted from the PC 48 used to enter such manual patient data into a database associated with the storage device 40. Also good.

  Each time any new received data is received or at regularly scheduled short intervals, the hospital communication server 42 queries the hospital database 40 and retrieves the new received data. The communication server 42 then “packages” the data into a formatted file (eg, an email message or FTP / HTTP file) and then sends the data to the repository network 12 over the Internet 32. The hospital interface server 14 of the repository network 12 receives this data transmission from the hospital networks 24, 26, presents the received file to the data server 16, and the data server 16 stores the data in the transmission file in the patient database 22. Parse or otherwise process into a format suitable for For example, an exemplary data structure for holding the patient database 22 is shown in FIG. In particular, the patient database 22 is configured to include a field 52 that includes a unique patient identification number assigned to each patient and a field 54 that includes a hospital identification number associated with the hospital or nursing facility where the patient is located. . Patient data 22 also includes personal data (PD1-) such as age, weight (ie, weight that was not initially sensed by the sensor), height, race, sex, or other information related to the patient. One or a plurality of fields 56 holding PDX) are included. The patient database 22 further includes one or more fields 58 that hold diagnostic codes (DC1-DCX) associated with the patient's disease or condition. Similarly, the patient database 22 also includes one or more fields 60 that hold treatment codes (TC1-TCX) associated with treatments and / or drug therapies utilized to treat the patient's disease or condition. included.

  Still further, the patient database 22 is configured to include a number of data fields 62 that hold sensing data (SD1-SDX) generated by a sensor 46 that monitors the patient. For example, both historical data and current data associated with the patient's skin temperature, oxygen saturation level, respiratory rate, blood pressure, heart rate, or other forms of sensed data are maintained in the data field 62. In a similar manner, the patient database 22 is configured to include a number of data fields 64 that hold device data (DD1-DDX) generated by the point-of-care device 44 utilized during patient treatment. . For example, related to temperature, rate of intravenous drug administration, oxygen and / or moisture content in the device, air circulation rate in the device, how long the device is open to the atmosphere, or other forms of device data Both current and historical data are stored in the data field 64.

  As will be appreciated, the configuration of the patient database 22 described in this application and in FIG. 2 is exemplary in nature. That is, the configuration of the patient database 22 may be modified to fit the data system 10 of a given design. Further, as will be appreciated, a number of databases 22 may have redundant information, some of which may be retained to suit the needs of a given data system 10 You may adjust according to the field.

  As explained above, subscribers 34 and 36 may access data in patient database 22. Subscribers 34, 36 are collected by research groups, health organizations, hospitals themselves (ie, some hospitals can be both data providers and subscribers), individual physicians, pharmaceutical or medical device companies, or repository network 12. It can take many forms, including some other entity that may be interested in the data. Typically, the subscribers 34, 36 use a web browser to access the patient database 22 with a personal computer. In particular, the subscriber's PC transmits a data request to the server 18 after connecting to the subscriber interface server 18 via the Internet 32. The subscriber interface server 18 validates or otherwise determines whether a particular subscriber has the right to access the patient database 22 and, if so, what subscription level. That is, in one exemplary embodiment, a subscriber may subscribe at various subscription levels based on the subscriber's data needs. In essence, the greater the subscriber's data needs, the greater the costs associated with the subscription. Also, the subscription level and associated costs include, for example, connection time to the repository network 12, amount and / or grade of data required by the subscriber, timeliness of required data (eg, real time / near real time). Or archived data) and / or the type of connection to the repository network 12 (eg, direct connection or web access).

  In any event, once the subscriber interface server 18 confirms the subscriber's identity and subscription level, the server 18 begins processing the subscriber's data request. In doing so, the subscriber interface 18 itself may query the patient database 22, or alternatively, communicate the data request to the internal data server 16 and query the patient database 22 therefrom. In either case, the requested data is retrieved from the patient database 22, formatted into the desired format, and transmitted by the subscriber interface server 18 to the subscribers 34, 36 via the Internet 32.

  Referring now to FIG. 3, another exemplary embodiment of a patient practice data system according to the present disclosure (denoted by reference numeral 100 below) is shown. Data system 100 is somewhat similar to data system 10. Accordingly, the same reference numerals are used in FIG. 3 to indicate similar components that are similar to those previously discussed with respect to FIGS. 1 and 2 and are not worth further discussion. The main difference between data system 10 and data system 100 is that data system 100 does not utilize a central server / database mechanism at each individual hospital 28, 30, and instead repositories over the Internet 32. The point is that a device configured to communicate directly with the network 12 is used.

  In particular, as shown in FIG. 3, the patient care device 44 provides a direct connection to the Internet 32 so that the patient care device 44 can communicate directly with the repository network 12 over the Internet 32. A configuration with networking hardware such as a router may be used. Similarly, the control hardware to which the sensor 46 is connected also provides a direct connection to the Internet 32 so that the control hardware associated with the sensor 46 can communicate directly with the repository network 12 via the Internet 32. It may be configured with networking hardware such as a modem or data router. Still further, the PC 48 may also include networking hardware such as a modem or data router that allows manual data input thereby to be communicated directly to the repository network 12 via the Internet 32.

  The configuration of data system 100 is particularly useful when a given hospital does not have, for example, an existing network infrastructure. In particular, if a given hospital does not have an existing network infrastructure, the concept of the present application can be used without requiring significant capital investment to design, configure and implement such a network on the hospital side. Also, as will be appreciated, the repository network 12 receives data from both types of hospitals (ie, hospitals with and without a centralized network structure) (eg, through the use of multiple types of hospital interface servers). You may comprise.

  Referring now to FIG. 4, yet another exemplary embodiment of a patient practice data system according to the present disclosure (shown below by reference numeral 200) is shown. Data system 200 is somewhat similar to data systems 10 and 100. Accordingly, the same reference numerals are used in FIG. 4 to indicate similar components that are similar to those previously discussed with respect to FIGS. 1-3 and are not worth further discussion. The main difference between the data system 200 and the data systems 10, 100 is that the data system 200 does not use the Internet 32 to communicate with the data repository, but instead, via the direct connection 202, the repository network 12. It is a point to communicate directly with.

  For example, the direct connection 202 may be in the form of a telephone connection that connects to the repository network 12 using a point-to-point protocol (PPP) and then communicates. Such a configuration may be utilized when it is desirable to avoid the use of a publicly accessible global network such as the Internet 32. Also, as will be appreciated, the repository network 12 may be configured to receive data from a hospital configured in any of the ways described above (eg, using multiple types of hospital interface servers). Good. In particular, the repository network 12 may be configured to include an interface server that receives data transmissions both via the Internet 32 (described above with respect to the data systems 10 and 100) and via the direct connection 202.

  As will be appreciated, other configurations of patient practice data systems are contemplated for use with the present disclosure. For example, instead of actually storing patient data in a storage device associated with the repository network 12 (ie, storage device 20), the patient data may actually be held in each individual hospital network. In this configuration, a database associated with the repository network 12 is utilized to maintain an index of patient data stored at each external location (ie, each hospital). That is, when subscribers 34, 36 request specific information, the server associated with repository network 12 determines the location of the relevant data from a number of hospital networks and then retrieves the data. The retrieved data may then be formatted and presented to subscribers 34 and 36. Also, as will be appreciated, instead of actually retrieving the data for the subscribers 34, 36, the repository network 12 simply accesses the network address of the patient data stored on the hospital network. It may be provided to the subscriber along with the authentication information so that the subscriber can directly access the hospital network.

  Therefore, as described in this application, the patient point of care data system of the present disclosure has numerous advantages over previously designed medical data systems. For example, the data system of the present disclosure allows for the collection and distribution of real-time or near real-time patient data regarding the treatment of many different patients receiving treatment at many different hospitals. In particular, unlike traditionally designed intra-hospital networks such as hospital LANs, the data system of the present disclosure allows for the collection and distribution of patient data for patients located in a relatively large number of different hospitals. In this way, research over a wide geographic area can be done quickly and easily. Also, such systems provide a relatively large sample size patient because data associated with a large number of patients is available.

  In addition, by collecting sensory and device data in addition to diagnostic and treatment data, patient status on a near real-time or near real-time basis (based on the interval at which data is transmitted from the hospital to the repository network 12) Can be monitored. This sensing and device data is particularly useful for tracking patient response to certain treatments and medications.

  Still further, while the data system according to the present disclosure allows patient data to be distributed to a large number of subscribers, other methods may necessitate an increase in the number of resources that collect such data. For example, a pharmaceutical company may access the patient database 22 to track the responses of patients who have been administered drugs manufactured by the company. Similarly, a pharmaceutical company may access the patient database 22 for marketing purposes. For example, a company may utilize the patient database 22 to determine the percentage of patients with a particular disease that is being treated with one or more drugs of the company.

Thus, according to the present disclosure, a method for patient data management comprises:
Collecting patient clinical data on a near real-time basis,
Deliver patient practice on a near real-time basis,
Identifying multiple hospitals each having a unique hospital code;
Identifying multiple patients at multiple hospitals, each having a unique patient code;
Identifying patient practice data associated with each of a plurality of patients;
Identifying demographic data associated with each of a plurality of patients;
Identifying diagnostic data associated with each of a plurality of patients;
Identifying treatment data associated with each of a plurality of patients;
Identifying sensing data generated by several sensors utilized to sense several conditions associated with each of a plurality of patients;
Identifying device data generated by several patient care devices utilized in the treatment of each of a plurality of patients;
Sending a unique hospital code to the repository network;
Sending a unique patient code to the repository network;
Sending patient data associated with each of a plurality of patients to a repository network;
Sending demographic data associated with each of a plurality of patients to a repository network;
Sending diagnostic data associated with each of a plurality of patients to a repository network;
Sending treatment data associated with each of a plurality of patients to a repository network;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients to a repository network;
Sending device data generated by a number of patient care devices used in the treatment of each of a plurality of patients to a repository network;
Sending a unique hospital code to the repository network via the global network;
Sending a unique patient code to the repository network via the global network;
Sending patient point-of-care data associated with each of a plurality of patients via a global network to a repository network;
Sending demographic data associated with each of a plurality of patients via a global network to a repository network;
Sending diagnostic data associated with each of a plurality of patients via a global network to a repository network;
Sending treatment data associated with each of a plurality of patients via a global network to a repository network;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients via a global network to a repository network;
Sending device data generated by several patient care devices used in the treatment of each of a plurality of patients via a global network to a repository network;
Storing a unique hospital code in a patient database associated with the repository network;
Storing the unique patient code in a patient database associated with the repository network;
Storing patient data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing demographic data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing diagnostic data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing treatment data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients in a patient database associated with a repository network;
Storing device data generated by several patient care devices utilized in the treatment of each of a plurality of patients in a patient database associated with a repository network;
Retrieving a unique patient code from a patient database associated with the repository network;
Retrieving patient data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving demographic data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving diagnostic data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving treatment data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving device data generated by several patient care devices utilized in the treatment of each of a plurality of patients from a patient database associated with a repository network;
Sending a unique patient code retrieved from a patient database associated with the repository network to the subscriber;
Sending patient data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending demographic data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending diagnostic data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending treatment data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending device data generated by a number of patient care devices used in the treatment of each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Formatting the data retrieved from the patient database before sending it to the subscriber;
Any one or more of changing the content of data that is retrieved and transmitted to the subscriber based on the subscriber's subscription level is included in any combination.

Further according to the present disclosure, the data system comprises:
A storage device holding a patient database;
A processing unit electrically connected to the storage device;
A memory device electrically connected to the processing unit, the memory device being executed by the processing unit;
Identifying multiple hospitals each having a unique hospital code;
Identifying multiple patients at multiple hospitals, each having a unique patient code;
Identifying patient data associated with each of a plurality of patients;
Identifying demographic data associated with each of a plurality of patients;
Identifying diagnostic data associated with each of a plurality of patients;
Identifying treatment data associated with each of a plurality of patients;
Identifying sensing data generated by several sensors utilized to sense several conditions associated with each of a plurality of patients;
Identifying device data generated by several patient care devices utilized in the treatment of each of a plurality of patients;
Sending a unique hospital code to the repository network;
Sending a unique patient code to the repository network;
Sending patient data associated with each of a plurality of patients to a repository network;
Sending demographic data associated with each of a plurality of patients to a repository network;
Sending diagnostic data associated with each of a plurality of patients to a repository network;
Sending treatment data associated with each of a plurality of patients to a repository network;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients to a repository network;
Sending device data generated by a number of patient care devices used in the treatment of each of a plurality of patients to a repository network;
Sending a unique hospital code to the repository network via the global network;
Sending a unique patient code to the repository network via the global network;
Sending patient data associated with each of a plurality of patients over a global network to a repository network;
Sending demographic data associated with each of a plurality of patients via a global network to a repository network;
Sending diagnostic data associated with each of a plurality of patients via a global network to a repository network;
Sending treatment data associated with each of a plurality of patients via a global network to a repository network;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients via a global network to a repository network;
Sending device data generated by several patient care devices used in the treatment of each of a plurality of patients via a global network to a repository network;
Storing a unique hospital code in a patient database associated with the repository network;
Storing the unique patient code in a patient database associated with the repository network;
Storing patient data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing demographic data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing diagnostic data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing treatment data associated with each of a plurality of patients in a patient database associated with a repository network;
Storing sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients in a patient database associated with a repository network;
Storing device data generated by several patient care devices utilized in the treatment of each of a plurality of patients in a patient database associated with a repository network;
Retrieving a unique patient code from a patient database associated with the repository network;
Retrieving patient data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving demographic data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving diagnostic data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving treatment data associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients from a patient database associated with a repository network;
Retrieving device data generated by several patient care devices utilized in the treatment of each of a plurality of patients from a patient database associated with a repository network;
Sending a unique patient code retrieved from a patient database associated with the repository network to the subscriber;
Sending patient data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending demographic data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending diagnostic data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending treatment data associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending sensing data generated by a number of sensors utilized to sense a number of conditions associated with each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Sending device data generated by a number of patient care devices used in the treatment of each of a plurality of patients retrieved from a patient database associated with a repository network to a subscriber;
Formatting the data retrieved from the patient database before sending it to the subscriber;
Causes the processing unit to perform one or more or any combination thereof of changing the content of data retrieved and transmitted to the subscriber based on the subscriber's subscription level.

  Referring now to FIGS. 5-5, an exemplary patient care apparatus 44 ′ includes a base 72, an infant support platform 74 on the base 72, and an infant compartment 76 on the platform 74, as shown in FIG. And has. The illustrated patient care apparatus 44 'is an infant temperature support apparatus operable as an infant incubator, an infant radiant warmer, or both. However, the features of the device 44 'described below with reference to FIGS. 5-25 include hospital beds, infant incubators, infant radiant warmers, stretchers, operating tables or chairs, wheelchairs and rotating mattresses, Other types of patient treatment such as percussion mattresses, low air loss mattresses, or any other type of device that provides a place for the patient to rest in a medical environment, including mattresses that include fluidized bead surfaces or devices with therapeutic surfaces Applicable to the device. The term “mattress” (s), as used in this disclosure, including the claims, is described in single layer mattresses, multilayer mattresses, zone mattresses, foam mattresses, inflatable floats, and the above sentence. It is intended to cover all types of human support elements, including any therapeutic surface, and combinations and equivalents thereof, and any other type of cushion known to support humans.

  The illustrated base 72 operates to operate a structure or frame 78, a set of casters or wheels 80 connected to the frame 78, and a drive mechanism (not shown) to change the height of the platform 74 relative to the base 72. It has a set of foot pedals 82 that are connected by a caregiver and a set of bumpers that protect the pedals 82 from unexpected impact. Platform 74 includes a lower portion 86 that shields the drive mechanism and other components of device 44 from view. The platform 74 also includes an upper portion 88 that supports components of the humidification system (not shown) of the device 44 and supports components of the convection heating system (not shown).

  The infant compartment 76 includes a pair of side walls 90 and a pair of end walls 92. A pair of access doors 94 are connected to each side wall 90 and cover each access port (not shown) formed on the side wall 90, and the closed position shown in FIG. Can be moved between an open position (not shown) that allows the caregiver to access the infant in the patient space formed by. Each end wall 92 includes one or more line passages through which electrical lines and fluid conduits are passed into the patient space. Some or all of the side walls 90 and end walls 92 can be rotated from their respective raised positions shown in FIG. become able to.

  The infant compartment 76 further includes a canopy 98 having a pair of canopy pieces 110 as shown in FIG. The device 44 ′ includes an overhead arm 112 to which a canopy piece break 110 is connected, with the lower edge of the canopy piece break close to the upper edge of the side wall 90 and end wall 92 to substantially seal the patient space. 5 is rotated between a lowered position shown in FIG. 5 and a raised position (not shown) that is more accessible to the infant in the patient space. One or more infrared radiation sources (not shown) are installed on the underside of arm 112 and, when activated, provide radiant heat to the patient space to warm the infant. The device 44 'includes a post 114 having an upper end from which an overhead arm 112 extends in a cantilevered manner. The pillar 114 is telescopically extendable and retractable and raises and lowers the canopy 98, the arm 112, and the infrared radiation source vertically as a single body. The device 44 ′ has a drive mechanism that operates to extend and retract the column 114.

  Also, as shown in FIGS. 5-8, the device 44 ′ includes a computer support 116 and a computer 48 ′ coupled to the support 116. The computer 48 'is configured to receive patient point-of-care data from a patient supported on the device 44' and the device 44 'itself. Computer 48 'has a display screen 118 on which patient point of care data is displayed in various combinations depending on instructions received by computer 48' from a user, as will be described in more detail below. In addition, the computer 48 ′ transmits data including patient point-of-care data related to the device 44 ′ and the patient supported thereon to the hospital network, and from the network, other devices substantially similar to the device 44 ′ and Various types of data are configured to be retrieved from the network, including patient point-of-care data associated with other devices supported thereon. Thus, patient point-of-care data associated with the device 44 'and the patient supported thereon, along with other types of data that can be retrieved by the computer 48' from the network, on the screen 118 of the computer 48 'at the point of care. Can see. The data types displayed on the screen 118 will be described in detail below with reference to FIGS. However, within the scope of the present disclosure, other types of data including any of the data described above with reference to FIGS. 1 to 4 may be displayed on the screen 118 in addition to or instead of the data described below. It is.

  The illustrated computer support 116 is an arm assembly (hereinafter referred to as “arm assembly 116”) configured to change the position of the computer 48 ′ relative to other parts of the device 44 ′. As shown in FIGS. 5 and 7, the arm assembly 116 includes a first arm 120, a first U link 122, a second arm 124, and a second U link 126. First arm 120 has a collar portion 128 coupled to the lower region of pillar 114, a main portion 130 angled outward and upward from collar portion 128, and extends substantially horizontally outward from portion 130. A pair of flanges 132. The arm 120 is pivotable about a first vertical axis 134 formed by an interconnection between the post 114 and the collar portion 128. The first U link 126 is coupled to the flange 132 for pivotal movement about the second vertical axis 136, and the second arm 124 is pivoted about the first horizontal axis 138. To the U-link 126. The second U link 126 is coupled to the outer end of the second arm 124 for pivotal movement about the third vertical axis 140, and the computer 48 ′ pivots about the second horizontal axis 142. Is coupled to the second U-link 126.

  The second arm 124 is a balancing arm having a balancing element, such as a spring or dashpot, which provides sufficient balancing force to balance the weight of the computer 48 'so that the computer 48' 124 is held in place after it has been adjusted to the desired position around the axis 138. Further, the second arm 124 has an orientation mechanism such as a parallelogram link mechanism that maintains the direction of the U link 126 and the computer 48 ′ with respect to the ground when the arm 124 rotates about the axis 138. included. For example, the display screen 118 is in a generally vertical direction when the arm 124 is in the lowered position and facing away from the arm 120 as shown in FIG. In the case of rotating to some other position such as the intermediate position shown in FIG. 5 (solid line), the orientation mechanism moves the display screen 118 to the arm 120 when the arm 124 moves between the lowered position and the intermediate position. Hold in a nearly vertical direction opposite. Further details of counterbalancing arms can be found in US Pat. Nos. 6,012,693, 5,992,809, 5,842,672, 5,826,846, 5,743,503 and 5 No. 340,072, each of which is incorporated herein by reference.

  In the illustrated embodiment, the pivoting movement of the arm 120 about the vertical axis 134 is only the degree of freedom of the arm 120 relative to the column 114. As a result, the height of the flange 132 and U link 122 above the floor on which the device 44 ′ is installed is approximately the same height as the arm 120 rotates along the axis 138. Of course, adjusting the height of the platform 74 relative to the base 72 also adjusts the height of the arm 120 relative to the floor. The rotational movement of the U link 122 around the vertical axis 136 is only the degree of freedom of the U link 122 relative to the arm 120, and the rotational movement of the arm 124 around the horizontal axis 138 is only the degree of freedom relative to the U link 122. Further, the rotational movement of the U link 126 around the vertical axis 140 is only the degree of freedom of the U link 126 relative to the arm 124, and the rotational movement of the computer 48 ′ around the horizontal axis 142 is computer 48 ′ relative to the U link 126. Is the degree of freedom. However, the computer support 116 has a different number of coupling elements and the interconnection between adjacent coupling elements has multiple degrees of freedom (e.g., rotation about multiple axes, telescopic motion, or linear extension / contraction). It is also within the scope of this disclosure.

  In the embodiment of the arm assembly 116, one or more stops, such as lugs, pins, surfaces, etc., are included or provided in the interface between the elements 114, 120, 122, 124, 126, 48 ′, each having a pivot axis. 134, 136, 138, 140, 142 to limit the amount of movement of these elements. Furthermore, embodiments of arm assembly 116 include various anti-friction components such as thrust bearings, radial bearings, plain bearings, bushings, etc. disposed between elements 114, 120, 122, 124, 126, 48 ′. . In one embodiment, friction joints are provided between the U link 126 and the computer 48 ′ and between the U link 126 and the arm 124. The friction joint is configured such that the computer 48 ′ does not move relative to the arm 124 by the normal force applied by a user who enters commands or data by touching the keyboard 144 or the display screen 118. However, when the friction joint applies a threshold amount to the computer 48 ′ that exceeds the normal force associated with entering commands or data on the keyboard 144 or screen 118, the computer 48 ′ is positioned relative to the arm 124. It is the composition which changes.

  In the exemplary embodiment of the device 44 ′, the arm assembly 116 and the computer 48 ′ are shown in FIG. 6 (solid line), where the computer 48 ′ is arranged next to the platform 74 and the first side of the infant compartment 76. It is movable between a first position and a second position shown in FIG. 6 (imaginary line), where the computer 48 ′ is placed alongside the platform 74 and the second side of the infant compartment 76. . Of course, the arm assembly 116 and the computer 48 'can be positioned at any of a myriad of positions within the range of motion of the elements 120, 122, 124, 126, 48'. Also, in the illustrated embodiment, the length of the arm 120 from the shaft 134 to the shaft 136 is longer than the lateral distance from the shaft 134 to the side of the infant support platform 74, so that the position where the computer 48 'can be placed is large. The portion is outside the “bottom area” of the platform 74 and infant compartment 76. Thus, a user sitting in a chair adjacent to the device 44 'can place the computer 48' in a position suitable for use while sitting in the chair, and a user standing next to the device 44 'is standing. The computer 44 'can be placed at a position suitable for use as it is.

  The ability to operate the computer 48 'in such a wide range of positions relative to other parts of the device 44' is either integrated with the device but fixed in position on the device, or one or It is an improvement over a patient support device having a computer with limited mobility such that it can only move within two degrees of freedom. In addition, by suspending the computer 48 ′ away from the rest of the device 44 ′ (ie, outside the “bottom area” of the platform 74 and compartment 76), the screen 118 and keyboard 144 can be moved to the computer 48 ′ and keyboard. The 144 can be made larger, for example, installed on or directly supported by the pillar 114, platform 74, or compartment 76.

  The illustrated computer 48 ′ has a plate 146 that is a back panel to which a display screen 118 and a keyboard 144 are coupled, as shown in FIG. The bracket 148 is installed on the back panel 146 and connected to the U link 126. The camera housing 150 is connected to the upper portion of the panel 146 and overhangs a portion of the display screen 118. A video camera (not shown) is disposed in an inner region of the housing 150 and receives an image through an opening 152 formed in a front portion of the housing 150 as shown in FIG. As shown in FIGS. 7 and 8, the wires associated with the computer 48 ′, such as power lines, data lines, video lines, etc., are bundled into a cable 154 and from the panel 146 to the internal area of the platform 74 through the internal area of the arm assembly 116. Is wired. In the illustrated embodiment, most of the cable 154 is disposed in the interior region of the arm assembly 116, but a portion of the cable 154 is disposed outside the arm assembly 116 and corresponds to the seam of the arm assembly 116.

  The device 44 'includes a controller 156 that controls the operation of various functions of the device 44', schematically illustrated in FIG. Functions controlled by the controller 156 include operation of the radiant warmer, operation of the convection heating system, operation of the humidification system, raising / lowering the canopy 98 and raising / lowering the platform 74 relative to the base 72. Controller 156 also receives various types of data from computer 48 'and various other input devices. In addition, the controller 156 transmits various types of data to the computer 48 ′ via the appropriate data line in the cable 154 and extends from the controller 156 to a medical facility data port or wall outlet 159. 158 to the hospital network. Similarly, data from the hospital network is transmitted to the control device 156 through the line 158. That is, according to the present disclosure, apparatus 44 ′ and computer 48 ′ can not only provide data including patient point-of-care data to any system 10, 100, 200, but also receive data from system 10, 100, 200. You can also In other words, device 44 ′ and computer 48 ′ are configured to serve as subscribers 34, 36 of systems 10, 100, 200.

  The device 44 'includes, for example, an air temperature sensor that senses the temperature in the patient space, an infant body temperature sensor that senses the body temperature of the infant, a humidity sensor that senses the humidity in the patient space, and a noise level to which the infant is exposed. Noise sensors, light sensors that sense the light level to which the infant is exposed, fan speed sensors that sense the speed at which the fans of the convection heating system operate, and heaters of the device 44 ' One or more environmental sensors and other types, such as a current sensor that senses the amount of current, a sensor that senses whether each canopy piece 110 is in the up or down position, and a sensor that senses the rise of the overhead arm 112 Sensors are included. Device 44 ′ includes suitable electrical lines (not shown) that interconnect the various sensors described above with controller 156. In addition, controller 156 includes electrical circuitry that processes, conditions, converts, or otherwise manipulates the signals provided by the sensors included in device 44 'into usable data. Thus, the signals provided by these various types of sensors can be viewed on the display screen 118 and transmitted to the hospital network and / or a central database where subscribers or legitimate users can retrieve data as described above. Provide some of the patient's point-of-care data.

  Device 44 ′ further includes a video camera 160 and a video data line 162 extending from camera 160 to controller 156. Camera 160 includes a lower portion or cradle 164 connected to one of end walls 92 and an upper portion 166 that is rotatable along a horizontal axis 168. The upper portion 166 of the camera 160 is directed to the infant supported in the patient space formed by the infant compartment 74, and the video signal from the camera 160, including the infant image data, is transmitted via the line 162 to the controller 156. To be told. The device 44 'also has a connection port 170 including a plurality of connectors 172 to which external data lines or patient care modules (not shown) are connected. A set of internal data lines 174 extend from each connector 172 to the controller 156.

  Some external data lines or patient care modules connected to connector 172 provide sensing data regarding various infant physiological conditions such as heart rate, respiratory rate, blood chemical composition, blood pressure, and the like. Also, other external data lines or patient care modules connected to connector 172 may provide nutritional data (eg, the amount of formula supplied to infants via the nasogastric feeding tube), intravenous fluid administration. Data related to various other aspects of patient care, such as data relating to waste products discharged by infants, data relating to phototherapy, electrocardiograph (EKG) data, electroencephalograph (EEG) data. Thus, connection port 170 allows data relating to devices external to device 44 'to be communicated to controller 156, computer 48', and the hospital network. Although the illustrated connection port 170 is accessible on the lower portion 86 of the infant platform 74, it is disclosed that the device 44 'has a connection port located anywhere on the device, including within the infant compartment 74. Is within the range. The device 44 ′ has a power line 176 that receives standard 110V, 60 Hz power from a medical facility power outlet 178.

  The controller 156 includes one or more microprocessors, microcontrollers, signal processing circuits, output adjustment circuits, memory circuits, I / O circuits, and the like. In some embodiments, the computer 48 'may have associated microprocessors or microcontrollers and associated circuitry that communicates with the circuitry of the controller 156 via an appropriate communication protocol. In other embodiments, computer 48 ′ is controlled by the circuitry of controller 156.

  The illustrated computer 48 'includes a bar code reader 178 shown in FIG. 8, which presents the token so that the token owner can gain access to certain information. In accordance with the present disclosure, a “low access” token 180 is provided to an infant relative supported on the device 44 ′ and a “high access” token 182 is provided to doctors, nurses, and other caregivers. Each token 180, 182 includes a barcode 184 that is read by the reader 178. Since the barcode 184 associated with token 180 is different from the barcode 184 associated with token 182, computer 48 'can identify which token 180, 182 was presented to reader 178. If the token 182 is presented to the reader 178, the owner of the token 182 can access all available information via the computer 48 ', but if the token 180 is presented to the reader 178, The owner of the token 180 can access only a limited amount of information via the computer 48 '. Tokens that permit intermediate level access (ie, access to more information than can be accessed by token 180 but less than information accessible by token 182) are also within the scope of this disclosure.

  The illustrated tokens 180, 182 are cards with a barcode 184 printed thereon or otherwise affixed, for example, with a label. Computer 48 'is magnetic for cards holding magnetic strips, tokens that transmit coded radio frequency (RF) signals, proximity cards, and other types of related tokens such as tokens that transmit or reflect infrared energy. It is also within the scope of this disclosure to have a reader other than a bar code reader, such as a strip reader, RF receiver, proximity card reader, and infrared energy receiver. It is also within the scope of this disclosure for a user to gain access to information by entering a user ID and password into the appropriate fields appearing on the display screen 118 of the computer 48 ′.

  In the following description, various data or information “appears on display screen 118” or “displays on screen 118” (or “appears” or “displays” on a portion or window of screen 118). Etc. or similar statements, the circuit of the controller 156 and / or the circuit of the computer 48 'and / or the circuit in the computer device of the hospital network execute one or more respective computer programs to obtain data. Or it should be understood that the information is represented on screen 118. Further, where there is a description or similar description such as “run software” or “run software” to achieve a function, computer 48 ′ may include one or more computer devices in the hospital network. Is intended to cover embodiments where the controller 156 is running or running software, and where the computer 48 'itself is running or running software.

  In the following description, if the icon or button is “selected” or “highlighted” or the user “selects” or “highlighted” the button or icon, or the like, It should be understood that the disclosure is intended to cover all methods of selecting or inverting a graphic or character image such as an icon or button that appears on a computer screen. These graphic or character images can be selected, for example, by moving the computer mouse over the part of the image to be selected and then clicking (or double-clicking) a button on the computer mouse. Use the Up and Down arrow keys to highlight various images, and when the desired image is highlighted, press the “Enter” key on the keyboard. Use the “Tab” key on the computer keyboard to view the various images. Highlight the desired image, press the “Enter” key on the keyboard, touch the computer screen with a light pen over the part of the screen that has the desired image, and use the voice control software to verbally display the desired image If selected and the computer screen is a touch screen, the touch screen Touching portion having a desired image may be achieved in such a way.

  Either one of tokens 180, 182 is presented to reader 178, or one of tokens 180, 182 is presented to reader 178, but for some period of time without any instructions being entered on computer 48 ' For example, a default screen 186 as shown in FIG. 9 appears on the display screen 118. Screen 186 appears as a “split screen” display, and various types of data appear in the associated window of the split screen.

  Individual patient information is shown in the individual information window 188 in the upper left area of the screen 186 as shown in FIG. Personal information includes the patient's name, the bed number to which the patient is assigned, an alarm indicator (flashing or otherwise indicating that the condition has changed and the alarm condition has been sensed), the patient's age, Includes the recent weight and the date on which it was measured, the patient's birth weight, the physician assigned to the patient, and the nurse assigned to the patient. Below window 188 is an image window 190 that displays the patient's video image captured by camera 160 in real time. Below the window 190 is an environmental window 192 that displays environmental data such as the temperature in the compartment 76, the patient's body temperature, the relative humidity in the compartment 76, and the percent oxygen concentration in the compartment 76. Below the window 192 is a vital signs data window 194, inspiratory oxygen component (FIO2), respiratory rate (RR), maximum inspiratory pressure (PIP), continuous positive airway pressure (CPAP), inspiratory / expiratory gas ratio (I: E :) and vital signs data such as positive end-breath pressure (PEEP).

  A vital signs graph window 196 is displayed on the screen 186 in the upper center area of the screen 86. Window 196 includes a graphical representation of the patient's heart rate, arterial blood pressure, venous blood pressure, and respiratory rate. The patient's pulse oxygen saturation (SpO 2) is also described in window 196. Below window 196 is a blank window 198. Below the window 198 is a control bar 210 having a bed icon 212, an arm icon 214, an angle icon 216, a minus sign icon 218, a plus sign icon 220, and a message icon 222. When the user selects the icon 212, the icon 212 is highlighted and then pressing either the minus sign icon 218 or the plus sign icon 220 causes the platform 74 (and the components supported by the platform 74) to move to the base 72. Descend or rise respectively. When the user selects the icon 214, the icon 214 is highlighted, and then pressing either the minus sign icon 218 or the plus sign icon 220 causes the pillar 114 to contract or extend relative to the platform 74, respectively, and the arm 112, canopy. 98, move the radiant warmer and any other components connected to any of them downward or upward, respectively. When the user selects icon 216 and then presses either the minus sign icon 218 or the plus sign icon 220, the mattress supported by the infant platform 74 is associated with the tilt mechanism of the device 44 ', respectively, so Move to Burg position or reverse Trendelenburg position.

  On the right hand side of the screen 186 (from the top to the bottom of the screen), a user name window 224, a time window 226, a main display control window 228, a second image window 230, and a control button window 232 are displayed. Since tokens 180 and 182 are not presented to reader 178, user name window 224 and control button window 232 are blank. In some embodiments, two cameras, such as camera 160, may be installed in compartment 76. In such an embodiment having two cameras, the second image window 230 displays images from one camera and the first image window 190 displays images from the other camera. In the illustrated embodiment, the windows 190, 230 may display duplicate images of the patient in response to user input. That is, other types of data may be displayed in one of the windows 190, 230 in response to user input, so that the patient image from the camera 160 is also displayed in the other of the windows 190, 230. be able to.

  The window 228 includes a “mode” button 234, a “content” button 236, a “single” button 238 and a “multi” button 240. When the user selects or highlights button 234, the user has the option of selecting either button 238 or button 240. When the user first selects button 234 and then selects button 238, data relating to the patient of the particular device 44 'connected to computer 48' appears on display screen 118, for example, as shown in FIG. When the user first selects button 234 and then selects button 240, data associated with a number of patient support devices 44, including device 44 ', will be displayed on display screen 118, as described in more detail below in connection with FIG. Appears on top. When the user selects button 236, the user has the choice of changing the type of data, formatting the data, and arranging the window containing the data that appears on the screen that the user is currently viewing. For example, if the user selects button 236 while viewing default screen 186, the user can change the information that appears on screen 186 in a desirable manner. Therefore, it is within the scope of this disclosure for the user to customize the data that appears on each screen described in this application. Since the computer 48 ′ associates the customized screen with each user who owns the tokens 180, 182, the screen is automatically set for the particular user who presented his token to the reader 178.

  When a relative or other person presents the “low access” token 180 to the reader 178 of the computer 48 ′, a low access home screen 242 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. The screen 242 includes windows 188, 190, 192, 194, 196, 198, and 226 as in the case of the screen 186, but the data in each window is updated almost in real time as the data changes. The The hospital network, computer 48 ′, and / or controller 156 stores user identification information associated with a particular barcode on the card 180. Accordingly, the name of the user to whom the card 180 is assigned appears in the window 224. In the illustrated example, as the data appearing in windows 188 and 224, respectively, Kevin Jones is the name of the patient supported on device 44 'and the owner of token 180 is Kevin's mother Sarah.・ It is Jones (Sarah Jones).

  The window 232 of the screen 242 includes a record button 244, a setting button 246, a video button 248, a video conference button 250, an email button 252, a web button 254, a logout button 256, and a main screen button 258. When the user selects button 244, the graph and related information that appeared in window 196 when button 244 was selected are printed by a hospital network, controller 156, or a printer (not shown) connected to computer 48 '. Is output. When the user selects button 246, the user can select images and / or data to store and / or attach to the email. For example, the user has the option of capturing an image of an infant patient appearing in window 190 and emailing the image to a recipient, such as another relative. When the user selects button 248, computer 48 'executes a software program that allows the user to leave a video message to any other person who has a token to access data via computer 48'. A camera placed in the housing 150 of the computer 48 'captures the video image of the user leaving the video message, and a microphone placed in the housing 150 of the computer 48' or connected to the microphone jack 260 (FIG. 8) Capture the audio part of the message. It is within the scope of this disclosure to program computer 48 'with any known video messaging software.

  When the user selects button 250, computer 48 'executes a software program that allows the user to set up or join a video conference. It is within the scope of this disclosure to program computer 48 'with any known video conferencing software. When the user selects the message icon 222, a message screen 260 appears on the display screen 118 of the computer 48 ', for example, as shown in FIG. Table 262 has one or more lines of information about any email or video message sent to the user but not yet viewed by the user. Table 262 has one or more lines of information about any emails of video messages that the user has sent but have not yet deleted or deleted.

  Each entry in the tables 262, 264 has either a video icon 266 or an email icon 268 indicating whether the associated message is a video message or an email, respectively. In addition, each item in table 262 has a play button 267 that the user selects to play the associated video message, and each item in table 264 includes a delete button that the user selects to delete the transmitted message from table 264. 269. Each item in the table 262 includes the name of the person who sent the message, the subject of the message, the date when the message was sent to the user, and the time when the message was sent to the user. Similarly, each item in the table 264 includes the name of the person to whom the user sent the message, the subject of the message, the date when the user sent the message, and the time when the user sent the message.

  A scroll icon 270 is provided to the right of the tables 262, 264 in the window 198 so that if the table 262, 264 has more items than can be displayed in the window 198 simultaneously, the user can scroll through the items in the tables 262, 264. A reception button 272, a transmission button 274, and a new button 276 exist at the lower end of the window 198 on the screen 260. If the user wants to place the received message table 262 at the top of the window 198, the user selects the receive button 272, and if the user wants to place the send message table 264 at the top of the window 198, the user selects the send button 274. If the user wants to see only newly received messages, the user selects button 276.

  As a result of the user selecting the message icon 222, the record, setting, and video buttons 244, 246, 248 in the window 232 are displayed on the screen 260 as shown in FIGS. 11 and 12, with a play button 278, a stop button 280, And a rewind button 282. When the user highlights one of the play buttons 267 that appear in the table 262 and then selects the play button 278 that appears in the window 232, for example, as shown in FIG. 12, the computer 48 'displays the highlighted play button 267. Play video messages for items related to. While the selected video message is being played, the video data stored in the memory of the computer 48 'is displayed in the window 230, and the audio data is accommodated in or connected to the computer 48' (not shown). Alternatively, it is provided to any of headphones (not shown) connected to the headphone jack 284 (FIG. 8) of the computer 48 ′. The user can adjust the volume of the audio data by moving the volume knob 285 (FIG. 8) or by selecting the icons 218, 220 on the control bar 210. If the user wishes to stop playing the video message, the user selects button 280. If the user wants to rewind the video message, the user selects button 282.

  When the user selects the email button 252 that appears in the window 232 of the screens 242, 260, an email screen 286 appears on the display screen 118 of the computer 48 ', for example, as shown in FIG. The email screen 286 has an email window 296 that replaces the vital signs window 196 of the screens 242, 260. However, the image window 190 is replaced by an auxiliary vital signs window 290 that includes tabular vital signs information instead of a graphical form so that the user can continue to view vital signs data on the screen 286 in near real time. In the exemplary embodiment, the image from camera 160 is shown in window 230 on screen 286 to replace window 190 with window 290.

  The email window 296 has a command bar 288 that includes various icons that allow the user to perform several functions associated with creating an email. In the illustrated example, the command bar 288 includes icons such as send, cut, copy, paste, undo, grammar check, spell check, and attachment. The functions related to each icon are known. For example, using the attachment icon, the user has the option of attaching any data and / or images that the user has stored in the memory of the computer 48 'using the settings button 246 as described above. The window 296 also includes a “destination” dialog box 292 and a “CC” dialog box 294, in which the user inputs the name of the recipient of the email created by the user. Window 296 further includes a “Subject” dialog box 298 where the user enters an email subject and a message dialog box 300 where the user enters an email message.

  The window 296 further includes, for example, a font dialog box (with an associated drop-down menu arrow), a text size dialog box (with an associated drop-down menu arrow), a text indentation icon, a bold icon, an italic icon, an underline icon, Some icons and dialog boxes are included, such as text color icons, text alignment icons, and bullet icons. The functions associated with each text format icon are well known. It is within the scope of this disclosure to customize the command bar 288 and the text format bar 310 to include icons that perform related functions when selected. Such customization capabilities are included in commercially available email software packages, such as Novell Groupwise email software and Lotus Notes email software.

  For example, if the user selects the web button 254 that appears in the window 232 of the screens 242, 260, 286, for example, a website hosted by the hospital where the device 44 'is installed or a web hosted by the manufacturer of the device 44'. A home page (not shown) of a designated website such as a site appears in window 198. In addition, a web page window that overlaps a number of windows appearing on the screen 118 of the computer 48 ′ may be displayed. A computer 48 'allows a user to connect to and browse the Internet (also known as the World Wide Web), and is activated when the button 254 is selected. ) Software or programmed by suitable web browser software, such as Microsoft Explorer (registered trademark) software. When the user selects the main screen button 258, the computer 48 'responds with a screen 242 whose example is shown in FIG. When the user selects the logout button 256, the computer 48 'responds with a screen 186, an example of which is shown in FIG.

  When a person such as a doctor or nurse presents a “high access” token 182 to the reader 178 of the computer 48 ′, a high access home screen 312 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. . The screen 312 includes windows 188, 190, 192, 194, 196, 198, 226 as in the screen 186, but the data in each window is updated in near real time as the data changes. The The hospital network, computer 48 ′, and / or controller 156 stores user identification information associated with a particular barcode 184 on the card 182. Accordingly, the name of the user to whom the card 182 is assigned appears in the window 224. In the illustrated example, as the data appearing in window 224 indicates, the owner of token 182 is Dr. Jane Smythe, the physician in charge of Kevin Jones.

  As with the window 232 of the screen 242, the window 232 of the screen 312 includes a record button 244, a setting button 246, a video button 248, a video conference button 250, an email button 252, a web button 254, a logout button 256, and a main button. A screen button 258 is included. However, as shown in FIG. 14, the window 232 of the screen 312 further includes a sales / service button 314, a research button 316, a supplies button 318, a pump / fluid button 320, an evaluation button 322, a schedule button 324, a radiology button. 326, drug therapy button 328, education button 330, examination room button 332, and call button 334 are included. Selecting buttons 244, 246, 248, 252, 254, 256, 258 on screen 312 and any other screen accessible from high access home screen 312, described above with reference to FIGS. Screens and data similar to those appear on the display screen 118 of the computer 48 '. Further, the screen 312 has icons 212, 214, 216, 218, 220, and 222, and when selected, the same data as in the case of each of the corresponding buttons described above with reference to FIGS. The message table that is retrieved and / or performed a similar function but appears in window 198 of screen 312 when icon 222 is selected is received or transmitted by the owner of token 182 rather than the owner of token 180. The item corresponding to the received message is included.

  When the user selects the video conference icon 250, a video conference control screen 336 appears on the display screen 118 of the computer 48 'as shown, for example, in FIG. The window 198 on the screen 336 has a video conference control panel 338 that includes a “Select Patient Bed” button 340, a “Enter URL / IP Address” button 342, and a “Connect” button 344. After the user selects button 340 on screen 336, the user can identify which device 44 has an associated image available on the video conference. In this example, the default patient bed is device 44 '. However, the user has the option to select any patient bed (ie, device 44) connected to the hospital network. After the user selects button 342, the user can identify the other participant (s) in the video conference by Internet address (es). After the user identifies the patient bed and recipient included in the video conference, the user selects button 344 to connect to the recipient. Thus, according to the present disclosure, video conferencing is accomplished by the World Wide Web. However, it is also within the scope of this disclosure to program computer 48 'with any known video conferencing software, including software that enables video conferencing via LAN, WAN, or direct line communication.

  When the user selects button 250, thereby causing screen 336 to appear on display screen 118 of computer 48 ', record, settings, and video buttons 244, 246, 248 are replaced by camera control bar 346, The camera control bar 346 includes a zoom out button 348, a zoom in button 350, and a camera switch button 352 in the illustrated embodiment. Any one or more cameras of the device 44 ′, including the camera in the housing 150 of the computer 48 ′ and the camera installed in the compartment 76, are motorized and a camera control bar 346 pans the camera left and right. It is within the scope of this disclosure to include buttons that move the camera up and down and control brightness or hue or some other parameter associated with the video camera.

  By selecting button 352, the user can switch between images appearing in window 230, which is typically an image from one camera of another participant in the video conference. Thus, by successively selecting button 352, the user can continue to view images associated with each camera associated with other participants in the video conference, associated with camera 160 and on computer 48 '. Images associated with the camera in the housing 150 can also be viewed. By selecting button 348, the user can zoom in on the image that appears in window 230, and by selecting button 350, the user can zoom out from the image that appears in the window. Thus, if the image appearing in the window 230 is from a camera associated with one of the other participants in the video conference, the computer 48 'may cause the other participant's camera to respond to a signal generated by the computer 48'. Assuming it is configured to be controlled, an appropriate signal is generated to control the cameras of other participants.

  In some embodiments, the user controls the images that are sent to other participants in the video conference. In these embodiments, window 230 shows images available to other participants in the video conference. Also, in such an embodiment, successive selection of button 352 causes the image shown in window 230 to relate to the image associated with camera 160 and the camera within housing 150 (and any other camera of device 44 '). You can switch between the images that you want, and you can select buttons 348 and 350 to zoom out or zoom in on the images that appear in window 230, respectively. During a video conference, the volume knob 285 or icons 218, 220 are used to adjust the volume of the audio portion of the conference.

  When the user selects the sales / service button 314 in the window 232, a sales / service screen 354 appears on the display screen 118 of the computer 48 'as shown, for example, in FIG. The window 198 on the screen 354 has a service contact table 356 and a sales contact table 358. Table 356 includes a photograph of the customer service representative or technician assigned to the hospital associated with the device 44 ', the name of the customer service representative or technician, and the customer service representative or technician contact phone number. Service contact information such as number is included. In addition, table 356 has a service icon 360 that, when selected, causes an email screen 286 to appear on display 118 where the customer service representative or technician's email address has already been entered into dialog box 292. Thus, the user can create and send an email message to request service information, or request a visit by a customer service representative or technician.

  Table 358 includes sales contact information such as a picture of the salesperson assigned to the hospital associated with the device 44 ', the name of the salesperson, and the contact phone number of the salesperson. In addition, table 358 has a sales icon 362 that, when selected, causes an email screen 286 to appear on display 118, where the sales representative's email address has already been entered into dialog box 292. The user can create and send an email message to request sales information or request a sales representative visit. Table 358 also has a manufacturer web link icon 364 that, when selected, causes the manufacturer's website home page for device 44 'to appear on display screen 118 of computer 48'. In the illustrated example, “Hill-Rom” is displayed above the button 314 and icon 364, respectively, indicating that Hill-Rom is the manufacturer of the device 44 ′. Also, other text such as “Sales / Service” or “Manufacturer Contact” may be displayed on the button 314, and the icon 354 may be, for example, “Manufacturer Home Page” or “Manufacturer Website”. Other text such as “Link to” may also be displayed. In addition, table 358 has a help icon 366 that, when selected, links the user to the help program on computer 48 '. Using the help program, the user can enter queries or retrieve information about the operation of the device 44 '.

  When the user selects the research button 316, a research screen 368 appears on the display screen 118 of the computer 48 ', for example, as shown in FIG. The illustrated screen 368 includes a correlation parameter window 370, a first study data window 376, and a second study data window 378. Windows 370, 376, 378 replace several windows or portions thereof that were displayed on display screen 118 before button 316 was selected. For example, the vital signs graph window 196 is replaced with windows 370, 376, 378. However, the image window 190 is replaced by an auxiliary vital signs window 290 that includes tabular vital signs instead of graphical, so that the user can continue to view vital signs data on the screen 386 in near real time.

  Perform classification, assimilation, mining, graphing, tabulation, correlation, etc. into some data accessible from some part of any patient point of care data management system described in this application, including systems 10, 100, 200 Presenting to the user on the research screen 368 is within the scope of this disclosure. In the illustrated example, window 370 includes a combination of six parameter input icons 372 each having a menu arrow 374. To select the parameters to be correlated, the user selects the arrow 374 for each icon 372 and displays the associated parameter selection menu on the screen 368. The user then selects one of the parameters from the parameter selection menu. This parameter selection is repeated until the user selects the desired number of parameters (up to 6 in the illustrated example).

  Based on the selected parameters, some data is provided to the computer 48 ′ from a database included in the network or system of which the device 44 ′ is a part and displayed in the windows 376 378 of the screen 368. As shown in FIG. 17, window 376 has a first study result icon 380 and window 378 has a second study result icon 382. Each icon 380, 382 has a “next” arrow 384 associated with it. By successively selecting either icon 380, 382, the user can scroll through available study data. In an alternative embodiment, selecting icon 380, 382 will present a drop-down menu of available study data selections in the respective windows 376, 378 so that the user can display from the menu in the corresponding window 376, 378. The desired research data should be selected.

  In the illustrated example of FIG. 17, “nervous state” is displayed in icon 380 and an associated bar graph 386 (eg, Brazelton assessment) appears in window 376. In the illustrated example, “Mother age” is displayed in the icon 382 and a related pie chart 388 appears in the window 378. In certain embodiments, study data displayed in windows 376, 378 may be based on real-time patient practice data for various patients for which systems 10, 100, 200 are currently receiving data. In another embodiment, the data shown in windows 376, 378 is based on historical patient clinic data for various patients from which system 10, 100, 200 has received data in the past. In yet another embodiment, the study data appearing in windows 376, 378 is based on data received from some other source or manually entered into systems 10, 100, 200. It is within the scope of this disclosure for study data accessible via computer 48 'to be based on an aggregation or combination of data from any of the data sources described above.

  When the user selects the supply icon 318 from the menu 232, a supply screen 390 appears on the display screen 118 of the computer 48 'as shown, for example, in FIG. The illustrated screen 390 includes a supply worksheet window 392 and a supply list window 394. Windows 392 and 394 replace windows 196 and 198 that were displayed on display screen 118 prior to selecting button 318. As a result, data from the vital signs graph window 196 is shown in near real time in tabular form in an auxiliary vital signs window 290 that replaces window 190. Further, the image from camera 160 is shown in window 230 on screen 390 by replacing window 190 with window 290.

  Window 394 of screen 390 has a list of supplies available to the infant and / or available near storage compartment or device 44 '. The list of supplies that appear in the window 394 includes an item column 396 that indicates the name of the related supply, an “inventory” column 398 that indicates the number of available item units, and, if applicable, the type of unit (eg, bag , A unit column 400 indicating a group, a package, and a bottle). In the illustrated example, the list of supplies in window 394 includes 4 bags of glucose-added saline (D5W 500CC solution), 8 bags of ER 500CC intravenous solution, 2 sets of ECG pads, 13 paper diapers, 2 tapes. 25 gram IV, 1 temperature patch, 3 blankets, 5 sponges, 3 sheets, 1 catheter 25, 3 stockinets, and 13 additional paper diapers. It is within the scope of this disclosure to include in the supply list any type of supplies used for patient care.

  The window 394 has a plurality of edit icons 410 arranged next to each supply item listed in the window 394 as shown in FIG. The window 394 also includes an operation icon column 412 including an add icon 414, a use icon 416, a delete icon 418, and an order icon 420. After the user selects a particular supply item, by selecting the associated icon 410, the user can select the appropriate one of the icons 414, 416, 418, 420 and perform the desired operation. For example, if the user intends to use one or more items of the selected item, the user selects icon 414 to add the item to one or more selected items, and the user selects icon 416. Further, if the user wants to delete one or more items from the item selected but does not plan to use other items to delete, the user selects icon 418. By selecting icon 416, the system associated with device 44 'charges the patient for using the selected item, while when icon 418 is selected, the system associated with device 44' charges the patient. do not do. The selection of the icon 418 corresponds to, for example, when the selected supply is used by another patient or returned to the supply room of the hospital. Selecting icon 420 allows the user to order more selected items from the hospital supply room.

  Whenever one of the icons 414, 416, 418, 420 is selected, a quantity dialog box (not shown) appears in the quantity column next to one of the selected icons 414, 416, 418, 420. The user enters the unit quantity of the selected supply that the user wants to add, use, delete, or order, depending on the situation. If none of the edit icons 410 are selected before the user selects either icon 414 or icon 420, selecting either icon 414, 420 activates window 392, and the user enters the situation. In response, information about supplies to be added or ordered can be entered into window 394. Window 394 further includes a “Save and Exit” icon 424 that the user selects after editing window 394 and / or entering information in window 392. When icon 424 is selected, the information appearing in columns 396, 398, 400 is automatically updated. Window 394 has a “Cancel” icon 426 that the user selects if he wants to cancel any changes made to windows 392, 394.

  When the user selects button 320 in window 232, a pump / fluid screen 428 appears on display screen 118 of computer 48 'as shown, for example, in FIG. Window 198 of screen 428 has an intake table 430 and an discharge table 432. The intake table 430 describes various types of information regarding fluids that are infused, pumped, or otherwise delivered to the patient. Each entry in the illustrated table 430 includes the number of the pump that administers the associated fluid to the patient, the number of the associated fluid bag, the contents of the associated bag, the site of the patient administering the fluid, and the fluid administered to the patient. It provides information such as the speed (cubic centimeter / hour) to be used, the amount of fluid delivered to the patient during the day, the amount of fluid delivered to the patient during the current shift, and so on. In addition, the table 430 has a “total” row 434 that includes the total rate at which all fluids are administered to the patient, the total amount of all fluids delivered to the patient during the day, and the current shift. The total amount of all fluid delivered to the patient is shown. The effluent table 432 lists the volumetric rates (cubic centimeters / hour) at which various types of fluids are evacuated from the patient. Table 432 also lists the total fluid drained from the patient.

  In the illustrated example, the fluids shown in Table 430 as being delivered to the patient include glucose-added saline (DSW), lactated Ringer's solution (LR), blood, prescription drugs, and HAYRX 8547302. However, it is within the scope of this disclosure for Table 430 to include any type of fluid that can be used in a medical environment to treat a patient. In the illustrated example, the fluids shown in Table 432 as being drained from the patient include urine, stool, vomiting (eg, vomiting), gastric fluid, thoracic fluid, and blood. It is within the scope of this disclosure for other types of patient fluids to be shown in Table 432. If necessary, a scroll icon 436 is provided next to the tables 430 and 432 so that the user can scroll through all items appearing in the tables 430 and 432.

  When the user selects the button 322 on the control button menu 232, an evaluation screen 438 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. Window 198 of screen 438 has a series of text 440 indicating the patient's assessment by the physician. In the illustrated example, a series of text 440 shows that the initial APGAR (ie, an index based on infant muscle tone, heart rate, reflex sensitivity, neonatal color, and respiratory effort) after the patient has 13 hours of dystocia. 3.8, 10 minute APGAR was 5.2, the patient's calculated gestation period was 32 weeks, and the patient's lung condition was good initially but then The patient has been shown to require respiratory support. However, as will be appreciated, the types of information and descriptions that a physician or caregiver can include in any individual assessment is virtually unlimited. The text 440 may be entered manually on the keyboard 144 of the computer 48 'or accessed by the computer 48' from another computing device included in the system and having the evaluation stored therein.

  When the user selects the button 324 on the control button menu 232, a schedule screen 442 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. Window 198 of screen 442 has a schedule table 444, which has a date / time column 446, a work column 448, and a completion column 450. The information in column 446 indicates the date and time when the scheduled work will be performed or has already been performed. The information in column 448 briefly describes the work that will be done in the future or that has already been done. The information in column 450 indicates whether the work has been done or has not been done yet. In the illustrated example, the tasks listed in Table 444 include several 45 spectroscopic therapy sessions, chest x-rays, several physical therapy (PT) sessions, and ophthalmic examinations. It is within the scope of this disclosure for any type of work to be included in Table 444. In the illustrated example, the phrase “waiting” in the item indicates that the associated work has not yet been performed, and the phrase “completed” in the item indicates that the associated work has already been performed. . If necessary, a scroll icon 452 is provided beside the table 444 so that the user can scroll through the items listed in the table 444.

  When the user selects the button 326 on the control button menu 232, a radiology screen 454 appears on the display screen 118 of the computer 48 ', for example, as shown in FIG. The screen 454 includes a radiology image window 456, a radiology evaluation window 458, and a radiology selection table 460. Window 456 includes one or more radiological images 462 and any accompanying data associated with the images. The image 462 includes, for example, an ultrasonic image and / or an X-ray image. The window 458 includes a row 464 of information indicating the name of the person who interpreted the image and the date and time when the image was interpreted. Window 458 also has a series of text 466 that provides patient assessments based on the images that appear in window 456. In the illustrated example, text 464 indicates that the image is a head ultrasound image through the patient's fountain, and that the ultrasound image indicates a significant enlargement of the left ventricle commensurate with hydrocephalus. It indicates that the right ventricle is within normal limits and that there was no abnormal flow pattern as indicated by the duplex and color Doppler methods. As will be appreciated, the type of information and description that a physician or caregiver can include in any individual assessment that appears in window 458 is virtually unlimited. Images and data appearing in windows 456, 458, 460 are stored in the memory device of computer 48 ', controller 156, or any other computer device included in the associated system.

  As shown in FIG. 22, the table 468 includes a date and time column 468, a study column 470, and a ready column 472. The date and time when the associated radiological image was taken are listed in column 468. The information in column 470 briefly describes the type of radiological image for each item in table 468. The information in column 472 indicates whether the radiology image is ready for viewing or whether the radiology image is still being processed. In the illustrated example, the types of radiological images described in column 470 include several ultrasound images (US), fountain images, and several x-ray chest images. Also, in the illustrated example, the phrase “Ready” appears in column 472 for each item, indicating that each associated radiological image is ready to be viewed.

  Table 468 includes a plurality of “select” icons 474 arranged next to each item listed in table 460 as shown in FIG. The user selects the desired icon 474 and then selects the view icon 476 to view the individual radiological image (s) associated with the selected icon 474 within the window 456 and associated within the window 458. Visually check the evaluation. If necessary, a scroll icon 478 appears beside the table 460 so that the user can scroll through all the items in the table 460. If necessary, a similar scroll icon (not shown) is provided next to the rating 466.

  When the user selects the button 328 on the control button menu 232, a medication therapy screen 480 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. The window 198 of the screen 480 has a medication therapy screen 482 having a drug name column 484, a supply column 486, a dose / kg column 488, a dose (mg) column 490, and a dose (ml) column 492. The name of the medication prescribed to the patient is listed in column 484. In the illustrated example, atropine, NAHCO3, calcium gluconate, glucose (10%), epinephrine 1: 10,000, lasix, and lidocaine (2%) appear in column 484. However, it is within the scope of this disclosure for any type of drug prescribed to the patient to be included on Table 482. For each drug listed in column 484, column 486 indicates the amount delivered, column 488 indicates the dose per kilogram, column 490 indicates the dose in milligrams, and column 492 indicates the dose in milliliters. Show. Computer 48 ′ automatically calculates the dosage shown in column 490 by multiplying the patient's weight by the associated number appearing in column 488. In addition, computer 48 ′ automatically calculates the dosage shown in column 492 by dividing the number appearing in column 486 by the corresponding number appearing in column 490.

  As illustrated in FIG. 23, the table 482 includes a weight change icon 494, a necessary amount edit icon 496, an information acquisition icon 498, and a detail icon 500. When the user selects icon 494, the user can change the patient's weight, and accordingly computer 48 'automatically adjusts the dosages appearing in columns 490 and 492 based on the new weight. When the user selects icon 496, the user can add drugs to table 482 and delete drugs from table 482. When the user selects icon 498, the user can obtain information about the medication that can be administered to the patient. When the user selects the icon 500, the user can obtain other types of information such as interpretation of the data appearing in the table 482 and information regarding historical data regarding medications and doses of medications administered to the past patient.

  When the user selects button 330 from control button menu 232, the user can link to various educational modules (not shown). The education module may be stored in a hospital network computer device or accessed over the Internet. In some embodiments, the education module may be linked or associated with an institution that can provide continuing education credits for completing various education modules. That is, after selecting the button 330, the user can activate an education module, read the teaching materials associated with the module, and take the test electronically. If the user passes the exam, continuing education credits are given to the user. In view of the present disclosure, during the first session, the user uses the computer 48 'to complete only a portion of the education module, and during the second subsequent session, the user uses the computer 48'. The education module may be completed.

  When the user selects the button 332 from the control button menu 232, the examination room screen 510 appears on the display screen 118 of the computer 48 ′, for example, as shown in FIG. Screen 510 includes a laboratory graph 512 and a laboratory table 514. The illustrated graph 512 and table 514 relate to laboratory test results of the patient's blood. The graph 512 and the table 514 include the white blood cell count (WBC), the red blood cell count (RBC), the red blood cell distribution width (RDW), the hematocrit (HCT), the hemoglobin (HGB), the average red blood cell hemoglobin amount (MCH), and the average red blood cell hemoglobin. Information on concentration (MCHC) and platelets (PLT) is included. However, it is within the scope of this disclosure for all types and types of laboratory test results to be displayed on screen 510. Laboratory test results are stored on any computer device in the system or network that is part of the device 44 'and accessible to the computer 48' for viewing the results.

  Graph 512 shows the date and time when various blood samples were taken from the patient. Table 514 also shows the date and time when various blood samples were collected from the patient, but table 514 further shows the location of the hospital where the sample was taken, the range of each item in table 514, and each item in table 514. Indicates the unit related to. The y-axis of the graph 512 is a normal value percentage and ranges from 30 percent to 150 percent. The data in table 514 is often actual blood test readings for individual characteristics of the blood sample in each specified unit. If necessary, a scroll icon 516 appears next to the table 514 so that the user can scroll up and down to see all the information contained in the table 514.

  The computer 48 'can function as a communication device for the nurse call system. Nurse call systems are described in U.S. Patent Nos. 6,362,725, 5,822,544, 5,838,223, 5,689,229, 5,561,412, 594,786, 4,967,195, and 4,601,064, each of which is incorporated herein by reference. When the user selects the call button 334 from the control button menu 232, the user can answer a “call” made by a remote user of the nurse call system. To answer the call, the user of computer 48 ′ speaks into a microphone housed in computer 48 ′ or a microphone connected to microphone jack 261 and communicates with the remote user. In addition, audio from a remote user is heard by the user of the computer 48 ′ through headphones included in a speaker or headphone jack 284 included in the computer 48 ′.

  When the user associated with the card 182 selects the multi-button 240 in the window 228, a multiplex device screen 520 appears on the display screen 118 of the computer 48 'as shown, for example, in FIG. Screen 520 includes a first column of information including windows 188, 192, 194, 290 related to the first patient and windows 188 ', 192', 194 ', 290' related to the second patient. It has a second column of information and a third column of information including windows 188 ", 192", 194 ", 290" associated with the third patient. Windows 224, 226, 228, 230, 232 also appear on the screen 520.

  The above description of the types of data shown in windows 188, 192, 194, 290 applies to windows 188 ', 188 ", 192', 192", 194 ', 194 ", 290', 290" as well. That is, the patient practice data of multiple patients can be viewed simultaneously on the display screen 118 of the computer 48 '. In some embodiments, when a user selects any portion of the first, second, or third column that has data associated with the first, second, and third patients, respectively, the user is directed to each patient. In some cases, an image from the camera 160 is displayed in the window 230. Further, when the user selects the content button 236 after selecting the button 240, the user selects the patient from whom the data is obtained, the type of data shown for each patient, the format of the data, and the data appearing on the screen 520. You can change the layout of the window that contains it. It is within the scope of this disclosure to show on-screen 520 clinical practice data for patients with more than three patients or fewer than three patients.

  The above description of the various types of patient practice data appearing on the various screens shown in FIGS. 9-25 is not intended to limit the present disclosure to only the types of data shown. In accordance with the present disclosure, all types of patient practice data may be displayed on the display screen 118 of the computer 48 ′ in one or more windows. In addition, much of the patient practice data described in this application is obtained in real-time or near real-time, but historical patient practice data for one or more patients is displayed on the display screen 118 of the computer 48 '. Displaying is within the scope of the present disclosure.

  While devices and methods for patient point of care data management have been described in detail with reference to certain preferred embodiments, changes and modifications as described and defined in the following claims are within the scope of this disclosure. And do not depart from the spirit.

FIG. 1 is a block diagram of a system for collecting and distributing patient practice data according to the present disclosure. A repository network having a hospital interface server and a subscriber interface server connected to the Internet, and each computer system is a data server. And a plurality of hospital computer systems connected to the Internet, each having a plurality of patient point-of-care data collection devices connected to a data server, and a plurality of subscribers connected to the Internet to access patient point-of-care data It shows. FIG. 2 is a table showing some exemplary data fields from which data can be read during operation of the system of FIG. FIG. 3 is a block diagram similar to FIG. 1 of another embodiment of a patient point-of-care data collection and distribution system according to the present disclosure, with a repository network connected to the Internet and a plurality of connected to the Internet. 1 shows a clinical site data collection device and a plurality of subscribers connected to the Internet. FIG. 4 is a block diagram similar to FIG. 1 of another embodiment of a patient practice data collection and distribution system according to the present disclosure, including a repository network having a hospital interface server and a subscriber interface server; FIG. 2 shows a plurality of hospital computer systems connected to a hospital interface server of a repository network by direct connection, a subscriber interface server of a repository network connected to the Internet, and a plurality of subscribers connected to the Internet. FIG. 5 is a perspective view of a patient care apparatus configured to collect patient practice data according to the present disclosure, including a wheeled base, an infant support platform on the base, and an infant enclosure on the infant support platform. And a patient support device having an arm assembly extending from the infant support platform and a computer coupled to the arm assembly. FIG. 6 is a top view of the patient care apparatus of FIG. 5 in a first position (solid line) where the computer is located on the first side of the infant support platform and the computer on the second side of the infant support platform. The arm assembly and computer which can be moved around a rotation axis between the arranged second positions (imaginary lines) are shown. FIG. 7 is a rear perspective view of the patient care apparatus of FIG. 5, with the arms of the arm assembly being pivotable with respect to the infant support platform and several axes with which the computer is pivotable with respect to the arm assembly. Indicates the axis (imaginary line). FIG. 8 is an enlarged perspective view of a part of the patient care apparatus of FIG. 5, having a reading device to which a token is presented, and an internal area of the infant support platform via a first data line (imaginary line). A pair of tokens under the computer connected to the control device (imaginary line) located in the middle and the infant support under the control device connected to the control device via respective sensing data lines (imaginary line) Multiple sensor connection ports accessible to the bottom of the platform, a camera connected to the infant enclosure and connected to the control device via a video data line (imaginary line), and hospital network data via a second data line The control device connected to the port. FIG. 9 is an example of a screen printout of a default screen that appears on the computer display screen before any of the pair of tokens is presented to the computer reader. FIG. 10 shows a low-level view that appears on the display screen when a first token of a pair of tokens that allows access to only the limited amount of patient practice data for the owner is presented to the computer reader. It is an example of the screen print output of an access home screen. FIG. 11 is an example of a screen printout of a message screen that appears on the display screen when a message icon is selected on the low access home screen of FIG. FIG. 12 is an example of a screen printout of a video message screen that appears on the display screen when the video message icon is selected on the message screen of FIG. FIG. 13 is an example of a screen printout of an email control screen that appears on the display screen when the email icon is selected. FIG. 14 shows a high access home screen that appears on the display screen when a second token of the pair of tokens is presented to the computer reader that allows the owner to access all patient practice data. It is an example of screen printing output. FIG. 15 is an example of a screen printout of a video conference control screen that appears on the display screen when a video conference icon is selected from the main menu associated with the high access home screen. FIG. 16 is an example of a screen printout of the sales and service screen that appears on the display screen when the sales and service icon is selected from the main menu. FIG. 17 is an example of a screen printout of a survey screen that appears on the display screen when a survey icon is selected from the main menu. FIG. 18 is an example of a screen printout of the supply screen that appears on the display screen when the supply icon is selected from the main menu. FIG. 19 is an example of a screen printout of the pump / fluid screen that appears on the display screen when the pump / fluid icon is selected from the main menu. FIG. 20 is an example of a screen printout of an evaluation screen that appears on the display screen when an evaluation icon is selected from the main menu. FIG. 21 is an example of a screen printout of a schedule screen that appears on the display screen when a schedule icon is selected from the main menu. FIG. 22 is an example of a screen printout of the radiology screen that appears on the display screen when the radiology icon is selected from the main menu. FIG. 23 is an example of a screen printout of a drug therapy screen that appears on the display screen when a drug therapy icon is selected from the main menu. FIG. 24 is an example of a screen printout of the laboratory screen that appears on the display screen when the laboratory icon is selected from the main menu. FIG. 25 is an example of a screen printout of a multi-mode screen that appears on the display screen when a multi-icon is selected.

Claims (49)

A patient care device,
A support structure;
A mattress supported by the support structure;
A computer coupled to the support structure;
A camera coupled to the support structure, wherein the computer has a display screen, an image from the camera is shown on a first portion of the display screen, and patient practice data is displayed on the display screen. Patient care device shown on 2 part.   The patient care apparatus according to claim 1, wherein the computer is configured to make an image from the camera accessible via the internet for viewing on a display screen of a remote computer.   The patient care apparatus of claim 1, wherein the computer is configured to allow an image from the camera to be emailed to an email address.   The patient care apparatus according to claim 1, wherein the display screen has a third portion in which environmental data indicating environmental conditions in a patient space near the mattress is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which patient-specific data is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a stored radiological image of the patient is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a stored ultrasound image of the patient is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which stored laboratory test results are shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion in which a recorded video message is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a control unit for listening to a recorded voice message is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a control unit for sending an e-mail is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a control unit for conducting a video conference is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a control unit for browsing the Internet is shown.   The patient care apparatus of claim 1, wherein the display screen has a third portion in which a list of supplies related to patient care is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion on which a schedule of patient medical appointments is shown.   The patient care apparatus according to claim 1, wherein the display screen has a third portion in which data relating to medications associated with the patient is shown.   The patient care of claim 1, wherein the display screen has a third portion in which additional point-of-care data relating to at least one other patient supported on at least one other patient care device is shown. apparatus. A patient care system,
A patient support device having a surface on which the patient lies;
A computer corresponding to the patient support device, the computer having a reader and a display, configured to store patient data including a first subset of patient data and a second subset of patient data A computer,
A first token, wherein the computer is configured to allow access to the first subset of patient data when the first token is presented to the reader;
A second token, wherein the computer is configured to allow access to the second subset of patient data when the second token is presented to the reader. Patient nursing system provided.   19. The patient care system according to claim 18, wherein the patient care device is an infant heat support device that operates as an infant incubator in one mode and can operate as a radiation incubator in the other mode.   The computer includes a column, a canopy supported with respect to the column, a radiant warmer supported with respect to the column, and an arm assembly connected to a lower portion of the column. 20. Patient care according to claim 19, wherein the patient assembly is connected to the arm assembly spaced from the column, the arm assembly being pivotable along a vertical axis to change the position of the computer relative to the column. system.   21. A patient care system according to claim 20, wherein the column is extendable and retractable to raise and lower the canopy and the radiant warmer relative to the surface.   The arm assembly includes a plurality of arm portions configured to allow a computer to be moved about the column from a first side of the infant thermal support device to a second side of the thermal support device. 20. The patient care system according to 20.   The patient care system according to claim 18, wherein the computer is installed in the patient support apparatus.   24. A patient care system according to claim 23, wherein the patient support device comprises an infant incubator.   The reader comprises a barcode reader, and the first token holds a first barcode read by the barcode reader when the first token is presented to the barcode reader. The patient care system of claim 18, wherein the second token holds a second barcode read by the barcode reader when the second token is presented to the barcode reader. . An infant support device,
The base,
An infant support platform coupled to the base and configured to support the infant;
A canopy disposed on the infant support platform, wherein an infant compartment in which the infant is disposed is formed between the canopy and the infant support platform;
A camera oriented towards the infant to provide a video image of the infant;
A patient sensor that senses at least one physiological condition of the infant;
A data management system for receiving an infant video image from the camera and receiving sensing data indicative of at least one physiological condition from the sensor, the infant video image and data indicative of at least one physiological condition of the infant; An infant support apparatus comprising: a data management system having a display screen for simultaneously displaying   And further comprising an environmental sensor for sensing at least one environmental condition in the infant compartment, wherein the data management system receives data indicative of at least one environmental condition from the environmental sensor, and the display screen comprises a video image of the infant and 27. The infant support apparatus according to claim 26, wherein data indicating at least one environmental condition is displayed simultaneously with data indicating at least one physiological condition.   27. The infant support apparatus of claim 26, wherein the data management system comprises a computer supported relative to the infant support platform, the computer comprising the display screen.   29. The apparatus of claim 28, further comprising an arm assembly extending from the infant support platform, wherein the computer is connected to the arm assembly and the arm assembly is movable to allow repositioning of the computer relative to the infant support platform. The infant support apparatus as described. A patient care system,
A plurality of patient support devices each having a surface on which the patient lies;
A plurality of computers, each computer coupled to a respective patient support device, each computer receiving patient point of view data indicative of at least one physiological condition of the patient supported by the respective patient support device; Receiving and configuring each computer to communicate each patient's point-of-care data to each of the other computers so that patient point-of-care data associated with all of the plurality of patients can be accessed at each of the plurality of computers. A patient care system comprising a plurality of computers.   31. A patient care system according to claim 30, wherein each of the plurality of computers is repositionable relative to a respective patient support device.   The patient care system according to claim 30, wherein each of the plurality of patient support devices can function as an infant incubator. A patient care device for use in a medical facility having a network of computer devices,
A support structure;
A mattress supported by the support structure and having a surface on which a patient lies;
A computer support attached to the support structure;
A computer attached to the computer support, the computer being connected to the network, the computer support being configured to allow repositioning of the computer relative to the support structure, the computer comprising: Configured to receive patient point-of-care data including data representing at least one physiological condition of the patient, and wherein the computer is configured to transmit patient point-of-care data to at least one of the computer devices of the network Patient care equipment.   A canopy disposed on the mattress; and a column extending between the support structure and the canopy, wherein the computer support includes an arm assembly, and the arm assembly is an axis formed by the column. 34. The patient care apparatus of claim 33, wherein the patient care apparatus is pivotable about and the computer is installed in the arm assembly. A patient point of care data management system,
A first computing device configured to collect patient point-of-care data, wherein the first portion of the patient point-of-care data indicates at least one physiological condition of the patient; A second portion indicates operating parameters of the patient care device associated with the patient, and the first and second portions of the patient practice data are collected in near real time by the first computing device;
A second computer device network-connected to the first computer device, having a database in which the clinical practice data of the patient is stored and the medical record data relating to the patient is stored;
A third computer device connected to the second computer device and configured to allow an authorized user to access the patient practice data and the medical record data; Patient point of care data management, wherein the computer device comprises a display screen wherein the patient point of care data is visible in near real time and at least a portion of the medical record data is visible simultaneously with the patient point of care data system.   36. A patient practice data management system according to claim 35, wherein the medical record data includes a radiological image of the patient.   37. A patient practice data management system according to claim 36, wherein the radiological image comprises an ultrasound image.   37. The patient practice point data management system according to claim 36, wherein the radiological image includes an X-ray image.   36. The patient point of care data management system according to claim 35, wherein a video image of a patient is displayed on the display screen of the third computer device simultaneously with the medical record data and the point of care data of the patient.   36. A patient practice data management system according to claim 35, wherein the medical record data includes laboratory data relating to at least one laboratory examination.   41. The patient practice data management system of claim 40, wherein the at least one laboratory test comprises a blood test. A medical data system,
A communication device for transmitting and receiving patient practice data;
A storage device having a database in which patient practice data is stored;
A processing unit electrically connected to both the communication device and the storage device;
A memory device electrically connected to the processing unit, wherein when executed by the processing unit, the processing to receive patient practice data related to a plurality of patients housed in a plurality of hospitals A medical data system comprising: a memory device storing therein a plurality of operation instructions for operating the communication device by a unit.   43. The medical data system of claim 42, wherein a portion of the patient practice data is generated by a plurality of sensors that sense physical characteristics of each patient. 43. The medical data system of claim 42, wherein when the plurality of instructions are executed by the processing unit, the processing unit inputs the patient practice data into a database.   45. When the plurality of instructions are executed by the processing unit, upon receiving a request from a subscriber, the processing unit retrieves at least a portion of the patient practice data from the database. Medical data system.   43. The medical treatment according to claim 42, wherein when the plurality of instructions are executed by the processing unit, the processing unit operates the communication device to send the retrieved patient practice data to the subscriber. Data system. A method of operating a medical data system, the method comprising:
Receiving patient point-of-care data related to multiple patients in multiple hospitals;
Storing the received patient practice data in a database and generating at least a portion of the patient practice data by a plurality of sensors that sense at least one physical characteristic of each patient;
Upon receiving a request from a subscriber, retrieving at least a portion of the patient practice data from the database;
Transmitting the retrieved patient practice data to the subscriber.   48. The method of claim 47, further comprising manually entering at least a portion of the patient practice data into the database. A method of providing patient clinical data to a subscriber,
Providing a database configured to store patient practice data from a plurality of patients in a plurality of hospitals, identifying each of the patients and each of the hospitals with a respective identification code;
Collecting the patient practice data from the plurality of patients and collecting at least a portion of the patient practice data on a substantially real-time basis;
Allowing a subscriber to have online access to the database for simultaneous and near real-time viewing of patient point-of-care data associated with one or more patients from one or more hospitals.

Images