[go: up one dir, main page]

WO2015057667A1 - Système de soins basé sur un réseau - Google Patents

Système de soins basé sur un réseau Download PDF

Info

Publication number
WO2015057667A1
WO2015057667A1 PCT/US2014/060430 US2014060430W WO2015057667A1 WO 2015057667 A1 WO2015057667 A1 WO 2015057667A1 US 2014060430 W US2014060430 W US 2014060430W WO 2015057667 A1 WO2015057667 A1 WO 2015057667A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
event
computer
server
communication path
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2014/060430
Other languages
English (en)
Other versions
WO2015057667A9 (fr
Inventor
Thomas LIPOMA
Carson DARLING
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
REST DEVICES Inc
Original Assignee
REST DEVICES Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by REST DEVICES Inc filed Critical REST DEVICES Inc
Publication of WO2015057667A1 publication Critical patent/WO2015057667A1/fr
Publication of WO2015057667A9 publication Critical patent/WO2015057667A9/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation

Definitions

  • the present invention relates to a care system, and more particularly, to a network-based care system that interfaces to one or more networkable accessories and aids a caregiver in the care of a subject.
  • a networked computer-based system, method, and computer program product for providing care to an infant is disclosed.
  • First data is received through a first communication path at an event server from a first device.
  • the first device may be a childcare device or the first device may be a user device, such as a user's cellular telephone, networked personal computing device, or a health/sleep monitor.
  • the event server also receives second data from a second device through a second communication path.
  • the first communication path and the second communication path being at least partially different.
  • the second communication device may be childcare device.
  • the event server determines whether to send a control signal to a controllable childcare device or send an alert to a care giver.
  • the event server uses the first and second data and applies the data to predetermined logic to determine a result.
  • the predetermined logic may be an algorithm in the form of computer code that uses at least the first and second data as input to determine a next action.
  • the predetermined logic may use various source of data such as data stored in databases directly accessible by the event server, data stored on remote databases associated with another server that are not directly accessible and require requests for access, user preferences stored in a user database (e.g. user preferences may include expected sleep times, length of sleep, number of feedings, environmental conditions etc.)
  • a control signal is sent to the controllable childcare device for changing the state of the childcare device and causing it to assume a different behavior.
  • an alarm message is sent to the personal computing device of a caregiver based upon the result.
  • both a control signal and a separate alarm are transmitted from the event server.
  • the first and second data received by the event server may be data indicative of an event i.e. event data.
  • the event data may be based upon sensed data and other data, such as user preferences, historical data, environmental data etc. wherein a processor, such as a category server or a child care device may apply a set of criteria to determine if an actual event has occurred and the category server or child care device passes the event data to the event server.
  • a processor such as a category server or a child care device may apply a set of criteria to determine if an actual event has occurred and the category server or child care device passes the event data to the event server.
  • the first and second data may be the first and second data may be biometric data, video data, state information of a childcare device, environmental data, or state information of child development.
  • the first communication path includes one or more servers that process data to determine if an event has occurred based in part upon data received from the first device.
  • the data originating from the childcare device would not be event data, but the data transmitted from the server to the event server would be event data.
  • These servers may be category servers wherein a category server operates in conjunction with one or more childcare devices and the childcare devices perform a specified function (e.g. health monitoring, feeding monitoring, sleep monitoring etc.).
  • data received from the two devices and processed by the event server may result in a control signal being sent to a different childcare device.
  • data and events generated by two childcare devices may result in a control signal causing operation of a third childcare device.
  • the control signal that is sent to a child care device may provide an instruction or instruction set to the controllable child care device or the control signal may simply change the state of one or more parameters associated with the child care device.
  • the first communication path or the second communication path or both include the Internet.
  • Embodiments of the invention may include a second server. This second server communicates with the event server and provides data including event data to the event server. The second server may receive data from a device using a proprietary communication protocol. The second server is in communication with the event server and may transfer data from a childcare device or event data to the event server. The second server may reside within the second communication path. In certain configurations of the invention, the second data is transmitted by the second childcare device to the first childcare device prior to the second data being received by the event server.
  • the second data that is transmitted by the second childcare device may be transmitted to the event server through a personal computing device.
  • the predetermined logic at the event server may normalize, upsample, downsample, or perform a plurality of functions on the data.
  • user preferences may be entered into the system and stored at a database that is accessible by the event server.
  • Event data can be generated based upon the user preferences and the event data can be used to determine if an event has occurred.
  • the disclosed methodology may be implemented on a server by providing a computer program product with software code thereon for performing one or more of the steps of the methodology.
  • the computer is a server on which the computer program product is installed, which changes the server into an event server.
  • Figures 1 schematically illustrates an infant care system according to an illustrative embodiment of the invention
  • Figure la schematically shows another embodiment of the infant care system wherein the event server may be in communication with a second server that is associated with one or more child care devices or other devices that produce data;
  • Figure 2 schematically illustrates a method of decision making by the event server according to an embodiment of the invention
  • Figure 3 schematically illustrates a method of adding data to the information database from a category server according to an embodiment of the invention
  • Figure 4 schematically shows different sources of data being transmitted or requested by an event server for determining if an alert should be transmitted to a device associated with a user or an action should be initiated through a known communication protocol to one or more child care devices
  • caretaker user, and parent may be used interchangeably unless the context dictates otherwise;
  • data shall mean data from any source, but in particular data that is sensed by a sensor, such as a sensor associated with a child care device, a personal computing device (e.g. GPS information), or a health/sleep monitoring device or state information about one or more parameters of a device (e.g. child care device).
  • Data may be represented as, but is not limited to biometric data, video data, a child-care device state, environmental data, child developmental state, state of care provided to an infant, state of infant care. Data from a source can be used to determine if an "event" has occurred.
  • the term "event” shall mean the determination that an action has occurred based upon data from one or more sources.
  • the presence or absence of an event is determined by using received/retrieved data (e.g. data preferences, data sent from a childcare device, data sent from a user's computing device or health monitoring device) and applying the data to a criteria.
  • a childcare device may send data indicative of the movement of an infant and the position of an infant. This data may be used to determine if the infant is awake and thus, an event has occurred. The data is applied to predetermined criteria.
  • FIG. 1 schematically illustrates an infant-care system 100 according to an illustrative embodiment of the invention.
  • the system 100 preferably includes an event server 102 to negotiate information among category servers associated with an aspect of care for an infant.
  • the category servers may include an infant health-monitoring server 104, an infant- feeding monitoring server 106, and an infant-sleep monitoring server 108.
  • the category servers 104, 106, 108 preferably aggregate data from each of the respective category devices. It should be understood that each server may be independent and that the servers may be combined together such that the functionality of the event server and at least one of the category servers are performed by a single server system.
  • the servers may also be distributed, such that the event server operates across a plurality of processing devices or there is a plurality of servers of a particular type. For example, there may be more than one event server and more than one category server and these servers may be located at a single facility or at multiple facilities.
  • the health-monitoring server 104 communicates with a base station 110, which is operative ly linked to a health-monitoring controller 110a.
  • the monitoring controller 110a is a capacitive-based sensing device embedded in an article of clothing of the infant.
  • the Infant feeding monitor server 106 communicates with an infant feeding- system 112 to assist the caregiver in the feeding of the infant.
  • the feeding system 112 is a heater and chiller system for regulating temperature of an infant milk or formula.
  • the manner of communication between the servers 104, 106, 108 and the base station 110, the feeding system 112 and the infant-bed accessory 114 may be any known manner of
  • the devices could be associated with an IP address and communicate over a wireless LAN or through an Internet connection.
  • the health-monitoring controller 110a and the base station may communicate either wirelessly or via wire and may be part of a network.
  • Each communication path as shown in Fig. 1 may be a communication over a different network/system having different associated communication protocols.
  • the communication between the infant health monitor server 104 and the base station may be a proprietary communication link whereas the communication between the infant health monitor server 104 and the event server may be through the Internet using standard IP (Internet Protocol) communications.
  • IP Internet Protocol
  • the infant-care system and each of its components may be located either locally (local to the location of a user/infant being monitored) or remote from the location of the infant being monitored.
  • the infant-care system will generally be associated with a plurality of users/infants wherein each user will have one or more monitoring devices 110, 112, and 114 located at their premises and the system can be located at one or more server locations.
  • the components can be operated in a distributed fashion across multiple processing devices and located at different physical and logical locations within one or more networks.
  • the infant-sleep monitoring server 108 communicates with an infant-bed accessory 114 and assists the caregiver in putting the infant to sleep.
  • the infant-bed accessory 114 is an infant mobile with configurable lights, sound, and motion output.
  • Examples of the health monitoring controller 110a and base stations 110 are described in U.S. patent application, serial no. 13/745,098, and U.S. provisional application, serial no. 61/713,177, by Lipoma et al.
  • An example of the feeding system 112 is described in U.S. patent application, serial no. 61/875,310, by Lipoma et al.
  • An example of the infant-bed accessory 114 is described in co-pending U.S. provisional application, titled "Infant Sleeping Aid and Infant-Bed Accessory", filed on October 14, 2013, by Lipoma et al. These applications are incorporated herein by reference in their entireties.
  • the category servers 104, 106, 108 or the event server 102 may interface to a cellular network to receive signals and data from personal computing devices.
  • personal computing devices may include, without limitation, a personal phone, a computer, a tablet, or any other suitable electronic device, which is connected to the internet and can display an output.
  • the system 100 includes an infant information database 116 to store information measured or determined at the base station 110, the feeding system 112, and the infant-bed accessory system 114.
  • the base station 110 preferably measures physiological states of the infant, including, but not limited to movement, heart rate, breathing rate, body temperature, skin temperature, blood oxygen saturation level, location, noise, moisture level of the infant's garments (such as diapers), and body temperature.
  • the base station 110 may maintain a determined state of the infant from the physiological state information, such as:
  • the infant feeding system 112 preferably measures the time of use information associated with the feeding of the infant as well as the feeding quantity and the environment around the feeding system 112.
  • the feeding system 112 may maintain an expected feeding schedule for the infant.
  • the infant-bed accessory system 114 assists the caregiver in putting the infant to sleep by providing lulling or calming lights, sounds, or motion.
  • the infant-bed accessory systems 114 preferably measures physiological states of the infant including, but not limited to, whether the infant is awake or sleep.
  • the infant-bed accessory 114 may also measure environmental conditions around the infant, including temperature levels, humidity levels, and noise levels.
  • the devices 110, 112, 114 may operate in conjunction with the system 100 in helping make better decisions at each of the respective infant care device 110, 112, 114.
  • the respective infant care device 110, 112, 114 may be configured to operate independently of one another.
  • the collected information of each device is preferably employed in the controls of the other devices to improve the system's assistance of care provided by the caregiver.
  • the device 110, 112, or 114 may send that information to the system 100 or may share them directly with the other devices 110, 112, or 114 across a local network 120.
  • the device sends that information to the devices category server 104, 106, 108.
  • the category server 104, 106, 108 may then decide whether to provide the information to the infant information database 116. If any of the device category servers 104, 106, 108 generates an event, the category server 104, 106, 108 may send that event to the event server 102.
  • the category servers 104, 106, 108 may interface to a cellular network to receive signals and data from the personal computing devices.
  • the category servers 104, 106, 108 may receive preferences and information from the personal computing device to generate an event.
  • the event server 102 may receive the preferences and information directly, and it may generate them as a subsequent event to process.
  • the event server 102 may send an alert to a caregiver or perform some action. For example, an alert may be communicated from the event server to a text messaging address, an e-mail address, to a telephone number (cellular/landline) or via other known communication systems.
  • An action may include relaying the event to the other devices 110, 112, and/or 114. To do so, the event server 102 may send the alert through the category servers 104, 106, 108. The action may also include initiating a process to determine whether to send commands to respective devices 110, 112, 114.
  • a health monitoring device 110 collects data associated with the infant and sends the data to the health-monitoring server 104. Assume, for example, that the health-monitoring server 104 decides that the data indicates that the infant has woken up - the server 104 then sends an event to the event server 102. The event server 102 would then decide whether to send an alert to a personal computer device, such as the caregiver's mobile phone. The event server 102 may then interrogate the database 116 for other states of the infant, such as whether the infant is hungry.
  • the event server 102 may then send an event back down the infant-feeding monitoring server 106, which then sends the event to the feeding system 112.
  • the event may include a command to initiate a control state for the temperature controls of the feeding system 112.
  • Fig. 1 A schematically shows an alternative embodiment of the infant care system.
  • the infant care system of Fig. 1 may include a plurality of servers.
  • the system includes a system server 150 that may perform the functions of the event server (102) and one or more of the category servers (104, 106, 108) of Figure 1.
  • the system server 150 may include one or more databases, including an infant data database, a user preferences database, and a database that maintains historical information. Historical information may be a compilation of data from the plurality of users/child care devices that are coupled to the childcare system.
  • a second server 160 may be part of the system 100 or in
  • this second server 160 receives in information from networked devices (i.e. child care devices 167, personal computing devices 165, and/or health/sleep monitoring devices 169).
  • the second server 160 may operate independently of the system server 150 and of the childcare system.
  • the second server 160 may have proprietary communications with one or more childcare devices.
  • the second server 160 can provide information received through these proprietary communications to the system server 150 and this information can be used in determining a next action or whether an alert should be sent to a caregiver.
  • This second server 160 may be in communication 180 with the system server 150 and cause alerts to be passed either directly back to a user's personal computer device 165 or to one or more of the child care devices 167. These alerts may be generated based upon information communicated to the system serve 15 Or.
  • the system server 150 may simply pass data from child care devices 167 to the second server 160 or the system server 150 may provide the second server 160 with additional data (statistics, personal data about the user or infant, indication of the occurrence of an event, historical data) and/or an algorithm for determining whether an alert or message (e.g. a control signal for the child care device) should be passed to a user's communication device or to one or more of the child care devices. Additionally, the system server 150 may pass the alert to the second server 160 and the second server may communicate with one or more of the childcare devices 167. Thus, not all of the childcare devices 167 need to communicate directly with the system server 150.
  • Devices from different product categories can work independently, but then have their respective server (such as the second server or another server) transmit data to other servers such that the system server 150 could aggregate data from different sources (child care devices, health/sleep monitor devices) and determine based upon a predetermined algorithm using the aggregated data whether an alert or other message should be sent to a personal computing device or to a child care device.
  • their respective server such as the second server or another server
  • an audio monitor 175 may have a one-way communication to a webserver 170.
  • the audio monitor 175 functions independently and would have no way of interacting with the system server 150 or with any other childcare devices 167 that communicate directly with the system server 150.
  • the server 170 that the audio monitor communicates with can then send data or events to the system server 150 over a communication path 180, the data received from the audio monitor may be used in combination with other data received from one or more child care devices for determining whether to generate separate events/alerts/data/actions
  • FIG. 2 schematically illustrates a method of decision making by the event server 102.
  • the event server 102 first checks (in state 202) for new events. The event server 102 then determines (in state 204) if there is a new event. If there is a new event, the event server 102 reads (in state 206) data from the information database 116.
  • the data from the information database 116 may include permission and/or preferences to send a notification to the personal computing device as well as and a trigger to initiate a process associated with the event.
  • the data from the information database 116 may include information about a user such as the sleep state of the user.
  • the event server 102 determines (in state 208) if the user should be notified.
  • the event server 102 sends (in state 210) an alert to the personal computing device.
  • the event server 102 checks (in state 212) whether the event should be sent to the device 110, 112, or 114. If the alert should be sent to the device 110, 112, 114, then the event server 102 sends (in state 214) the alert and checks (in state 202) for new events.
  • An alert may refer to a notification, a message, a report, and any trigger to inform a user of some information.
  • the event server 102 may receive events from feeding systems 112, sleeping-aid systems 114, monitoring systems 110, or the category servers 104, 106, 108.
  • the event server 102 may also receive events from the personal computing device or from its own internally generated processes.
  • Table 1 shows examples of events that may be initiated by the infant care devices 104, 106, or 108.
  • the table lists the event, the source of the event, the action to determine whether to send as alert, and other actions associated with the event.
  • event server 102 pulls stored notification preferences of the caregiver of the respective event and sends out an alert where the permission is given.
  • Event 1 may cause several actions by the event server 102.
  • the event server 102 may initiate events to determine whether the infant is hungry (event 3), is irritated (event 4), is moody (event 5), is fussy (event 6), is or crying (event 7). Subsequently, depending on the determined state of the infant (in events 3, 4,5, 6, and/or 7), the event server 102 may (i) do nothing, (ii) send information/commands to the feeling-system 112 to initiate a temperature control action or (iii) send information/commands to the sleeping-aid system 114 to initiate a lulling sequence to calm the infant back to sleep.
  • Event 2 indicates that the infant is asleep.
  • the event server 102 pulls stored notification preferences of the caregiver of this event and sends out an alert where the permission is given.
  • the event server 102 may determine the source of the event and relay the information to the other devices.
  • system 114 system 114; if from sleeping-aid system 114, send the event to the feeding system 112
  • Table 2 shows events preferably generated by the event server 102.
  • Events 8 and 9 indicate that a sleep schedule or a feeding schedule, respectively provided by the caregiver has met a specific condition, such as time.
  • the event server 102 or the respective category servers 104, 106, 108 may monitor for specific conditions that the caregiver has selected.
  • the event server 102 may send a command to the sleeping-aid system 1 14 to turn on when infant is determined to be awake, is not hungry, and is not irritated.
  • the event server 102 may send commands to initiate temperature control of the feeding system 112 upon the infant being determined to be hungry and that the personal computer device associated with the user is in a specified proximity to the feeding system 112.
  • the event server 102 may provide notification to the personal computing device upon new recommendations for the sleeping time or the feeding being determined.
  • Table 3 shows events preferably generated by the personal computing device.
  • the event server 102 receives feeding or lulling instructions as preferences from the caregiver.
  • the event server 102 may relay the information to the respective care device (112, 114) (such as in event 14), or it may initiate a process to monitor for such conditions (events 15 and 16).
  • the monitoring process may generate subsequent events, such as events 8 or 9.
  • the personal computing device may generate an event to indicate to the various system of the proximity of the caregiver.
  • the event server 102 may relay the information to the respective care device 112 or 114.
  • the personal computing device may generate an event to indicate a remote-talking session with the infant.
  • the event server 102 may send the information to the sleeping-aid system 114 to disable the activating of the sound or lights output and not disturb the talking session.
  • Events 19-21 are a house-cleaning operations in which the event server 102 updates the notification preferences upon a preference being received (event 19) or updates the information database 116 with a respective device ID (event 20 or 21).
  • Table 3 Receive feeding personal Send information to the information computing feeding system 112.
  • Table 4 shows events preferably generated by the monitoring system 110.
  • the event server 102 pulls notification preferences of the user to determine whether to alert the user of a measured state of the infant, including abnormal breathing rate (event 22), abnormal temperature (event 23), or unsafe conditions (event 24).
  • Figure 3 schematically illustrates a method of adding data to the information database 116 from a category server 104, 106, or 108.
  • the server 104, 106, or 108 first checks (in state 302) for data.
  • the server 104, 106, or 108 determines (in state 304) if the data is new by comparing the received data to entries in the information database 116.
  • a buffer may be maintained of recently retrieved information from the database 116.
  • the category server 104, 106, 108 then checks (in state 306) for the infant ID number and associates the information to the infant.
  • the infant information database maintains an infant ID identifier with each event or data.
  • the category server 104, 106, 108 then adds (in state 308) the information into the infant information database 112.
  • Fig. 4 represents the confluence of data within the childcare system from a plurality of sources including childcare devices 400, and health/sleep monitoring devices, data about a device retrieved or sent from a server 410, and data that is retrieved or sent from a database 420.
  • This data is used to decide whether an event is generated 430.
  • the event may be generated based on an algorithm using the data and the event can be generated at the childcare device, at a category server or within the event server/system server.
  • the event server/system server will determine whether an alarm or control signal is generated and sent from the event server 440.
  • the alarms 460 are sent to a personal computing device 480 and control signals 450 are sent to a childcare device 470.
  • Data can be generated by a childcare device 400, sensor 400A, or other device that includes a sensor and the data can be provided either directly or indirectly to the event server.
  • Data 490 may also be generated by a device such as a caretaker's personal computing device 480 or from the computing device of someone else associated with the infant (e.g. a parent, babysitter, nurse, doctor, nutritionist, pharmacist etc.).
  • a caretaker may have an associated health/sleep tracking device that stores information about the health/alertness of the caretaker. This information may be sensed by the health/sleep monitoring device and stored at a server (e.g. the health/sleep device server).
  • the server for the health tracker/sleep monitoring device may store the information and make the information available to the event server.
  • the event server may use the information about the sleep state of the caregiver in determining whether an alarm should be sent to the caregiver.
  • the event server may also query a database regarding information that is needed to determine if an event has occurred.
  • This database may include user preferences and may also include historical information about the user/infant or historical information for all users/infants or a subset of all users/infants that are associated with the system.
  • User preferences can be stored locally at the event server or on a different server in a database. It should be clear to one of ordinary skill in the art that data from different sources may originate from different locations, but the data will eventually arrive at and be used by the event server in the determination of whether an event has occurred and whether an alert or a control signal should be generated and sent to a child care device.
  • a networked baby monitor may detect that a baby has woken up based upon the sensed movement of the baby or based upon increased vital signs and can then send this information along with the parents' data and alert preferences to the event server.
  • the alert preferences and user data (alertness of the
  • caregiver/parent(s) may be stored on a remote server in a database.
  • the event server could poll the remote database to get the parents sleep data to determine how asleep each parent are, and the event server can then send an alarm to an awake parent rather than sending an alarm to both parents.
  • data used by the event server may originate from childcare devices, received from a database (e.g. a user preference database), received from a server (health/sleep information of a parent/caregiver) or received directly from a device wherein data from device is directly transmitted to the server.
  • Double-ended arrows generally indicate that activity may occur in both directions (e.g., a command/request in one direction with a corresponding reply back in the other direction, or peer-to-peer communications initiated by either entity), although in some situations, activity may not necessarily occur in both directions.
  • Single-ended arrows generally indicate activity exclusively or predominantly in one direction, although it should be noted that, in certain situations, such directional activity actually may involve activities in both directions (e.g., a message from a sender to a receiver and an acknowledgement back from the receiver to the sender, or establishment of a connection prior to a transfer and termination of the connection following the transfer).
  • the type of arrow used in a particular drawing to represent a particular activity is exemplary and should not be seen as limiting.
  • a device may include, without limitation, a bridge, router, bridge-router (brouter), switch, node, server, computer, appliance, or other type of device.
  • Such devices typically include one or more network interfaces for communicating over a communication network and a processor (e.g., a microprocessor with memory and other peripherals and/or application-specific hardware) configured accordingly to perform device functions.
  • Communication networks generally may include public and/or private networks; may include local-area, wide-area, metropolitan-area, storage, and/or other types of networks; and may employ communication technologies including, but in no way limited to, analog technologies, digital technologies, optical technologies, wireless technologies (e.g., Bluetooth), networking technologies, and internetworking technologies.
  • devices may use communication protocols and messages (e.g., messages created, transmitted, received, stored, and/or processed by the device), and such messages may be conveyed by a communication network or medium.
  • a communication message generally may include, without limitation, a frame, packet, datagram, user datagram, cell, or other type of communication message.
  • references to specific communication protocols are exemplary, and it should be understood that alternative embodiments may, as appropriate, employ variations of such communication protocols (e.g., modifications or extensions of the protocol that may be made from time-to-time) or other protocols either known or developed in the future.
  • logic flows may be described herein to demonstrate various aspects of the invention, and should not be construed to limit the present invention to any particular logic flow or logic implementation.
  • the described logic may be partitioned into different logic blocks (e.g., programs, modules, functions, or subroutines) without changing the overall results or otherwise departing from the true scope of the invention.
  • logic elements may be added, modified, omitted, performed in a different order, or implemented using different logic constructs (e.g., logic gates, looping primitives, conditional logic, and other logic constructs) without changing the overall results or otherwise departing from the true scope of the invention.
  • the present invention may be embodied in many different forms, including, but in no way limited to, computer program logic for use with a processor (e.g., a microprocessor, microcontroller, digital signal processor, or general purpose computer), programmable logic for use with a programmable logic device (e.g., a Field Programmable Gate Array (FPGA) or other PLD), discrete components, integrated circuitry (e.g., an Application Specific Integrated Circuit (ASIC)), or any other means including any combination thereof.
  • Computer program logic implementing some or all of the described functionality is typically implemented as a set of computer program instructions that is converted into a computer executable form, stored as such in a computer readable medium, and executed by a microprocessor under the control of an operating system.
  • Hardware-based logic implementing some or all of the described functionality may be implemented using one or more appropriately configured FPGAs.
  • Source code may include a series of computer program instructions implemented in any of various programming languages (e.g., an object code, an assembly language, or a high-level language such as Fortran, C, C++, JAVA, or HTML) for use with various operating systems or operating environments.
  • the source code may define and use various data structures and communication messages.
  • the source code may be in a computer executable form (e.g., via an interpreter), or the source code may be converted (e.g., via a translator, assembler, or compiler) into a computer executable form.
  • Computer program logic implementing all or part of the functionality previously described herein may be executed at different times on a single processor (e.g., concurrently) or may be executed at the same or different times on multiple processors and may run under a single operating system process/thread or under different operating system processes/threads.
  • computer process refers generally to the execution of a set of computer program instructions regardless of whether different computer processes are executed on the same or different processors and regardless of whether different computer processes run under the same operating system process/thread or different operating system processes/threads.
  • the computer program may be fixed in any form (e.g., source code form, computer executable form, or an intermediate form) either permanently or transitorily in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM), a magnetic memory device (e.g., a diskette or fixed disk), an optical memory device (e.g., a CD-ROM), a PC card (e.g., PCMCIA card), or other memory device.
  • a semiconductor memory device e.g., a RAM, ROM, PROM, EEPROM, or Flash-Programmable RAM
  • a magnetic memory device e.g., a diskette or fixed disk
  • an optical memory device e.g., a CD-ROM
  • PC card e.g., PCMCIA card
  • the computer program may be distributed in any form as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).
  • a computer system e.g., on system ROM or fixed disk
  • a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).
  • Hardware logic including programmable logic for use with a programmable logic device
  • implementing all or part of the functionality previously described herein may be designed using traditional manual methods, or may be designed, captured, simulated, or documented electronically using various tools, such as Computer Aided Design (CAD), a hardware description language (e.g., VHDL or AHDL), or a PLD programming language (e.g., PALASM, ABEL, or CUPL).
  • CAD Computer Aided Design
  • a hardware description language e.g., VHDL or AHDL
  • PLD programming language e.g., PALASM, ABEL, or CUPL
  • Programmable logic may be fixed either permanently or transitorily in a tangible storage medium, such as a semiconductor memory device (e.g., a RAM, ROM, PROM,
  • EEPROM electrically erasable programmable read-only memory
  • Flash-Programmable RAM a magnetic memory device
  • an optical memory device e.g., a CD-ROM
  • the programmable logic may be fixed in a signal that is transmittable to a computer using any of various
  • the programmable logic may be distributed as a removable storage medium with accompanying printed or electronic documentation (e.g., shrink wrapped software), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the communication system (e.g., the Internet or World Wide Web).
  • a computer system e.g., on system ROM or fixed disk
  • a server or electronic bulletin board over the communication system
  • some embodiments of the invention may be implemented as a combination of both software (e.g., a computer program product) and hardware. Still other embodiments of the invention are implemented as entirely hardware, or entirely software.
  • embodiments of the present invention may employ conventional components such as conventional computers (e.g., off-the-shelf PCs, mainframes, microprocessors), conventional programmable logic devices (e.g., off-the shelf FPGAs or PLDs), or conventional hardware components (e.g., off-the-shelf ASICs or discrete hardware components) which, when programmed or configured to perform the non-conventional methods described herein, produce non-conventional devices or systems.
  • conventional computers e.g., off-the-shelf PCs, mainframes, microprocessors
  • conventional programmable logic devices e.g., off-the shelf FPGAs or PLDs
  • conventional hardware components e.g., off-the-shelf ASICs or discrete hardware components

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)

Abstract

L'invention concerne un système informatisé en réseau, un procédé et un produit-programme d'ordinateur pour fournir des soins à un nourrisson. Des premières données sont reçues, en provenance d'un premier dispositif, par l'intermédiaire d'un premier trajet de communication au niveau d'un serveur d'événements. Le premier dispositif peut être un dispositif de garde d'enfant, ou le premier dispositif peut être un dispositif utilisateur, tel qu'un téléphone cellulaire d'un utilisateur, un dispositif informatique personnel en réseau ou un dispositif de surveillance de santé/sommeil. Le serveur d'événements reçoit également des secondes données depuis un second dispositif par l'intermédiaire d'un second trajet de communication. Le premier trajet de communication et le second trajet de communication sont au moins partiellement différents. Le second dispositif en communication peut être un dispositif de garde d'enfant. Le serveur d'événements détermine s'il doit envoyer un signal de commande à un dispositif de garde d'enfant pouvant être commandé ou envoyer un signal commande à un dispositif de garde d'enfant pouvant être commandé. Le serveur d'événements utilise les premières et secondes données et applique les données à une logique prédéterminée pour déterminer un résultat. Un signal de commande est envoyé au dispositif de garde d'enfant pouvant être commandé pour changer l'état du dispositif de garde d'enfant et pour lui faire avoir un comportement différent. Dans une variante, un message d'alerte est envoyé au dispositif informatique personnel d'un soignant sur la base des résultats.
PCT/US2014/060430 2013-10-14 2014-10-14 Système de soins basé sur un réseau Ceased WO2015057667A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US201361890519P 2013-10-14 2013-10-14
US201361890380P 2013-10-14 2013-10-14
US201361890401P 2013-10-14 2013-10-14
US61/890,519 2013-10-14
US61/890,401 2013-10-14
US61/890,380 2013-10-14

Publications (2)

Publication Number Publication Date
WO2015057667A1 true WO2015057667A1 (fr) 2015-04-23
WO2015057667A9 WO2015057667A9 (fr) 2015-07-09

Family

ID=51894200

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/060430 Ceased WO2015057667A1 (fr) 2013-10-14 2014-10-14 Système de soins basé sur un réseau

Country Status (1)

Country Link
WO (1) WO2015057667A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016022277A1 (fr) * 2014-08-03 2016-02-11 Morpheus, Llc Système et procédé de surveillance d'humains

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010051765A1 (en) * 1999-03-31 2001-12-13 Walker Jay S. Patient care delivery system
US20050038326A1 (en) * 2003-05-30 2005-02-17 Michael Mathur System, device, and method for remote monitoring and servicing
US20050146431A1 (en) * 2003-12-31 2005-07-07 Ge Medical Systems Information Technologies, Inc. Alarm notification system, receiver, and methods for providing live data
US20120169467A1 (en) * 2010-12-31 2012-07-05 Condra David L Patient alert management system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010051765A1 (en) * 1999-03-31 2001-12-13 Walker Jay S. Patient care delivery system
US20050038326A1 (en) * 2003-05-30 2005-02-17 Michael Mathur System, device, and method for remote monitoring and servicing
US20050146431A1 (en) * 2003-12-31 2005-07-07 Ge Medical Systems Information Technologies, Inc. Alarm notification system, receiver, and methods for providing live data
US20120169467A1 (en) * 2010-12-31 2012-07-05 Condra David L Patient alert management system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016022277A1 (fr) * 2014-08-03 2016-02-11 Morpheus, Llc Système et procédé de surveillance d'humains

Also Published As

Publication number Publication date
WO2015057667A9 (fr) 2015-07-09

Similar Documents

Publication Publication Date Title
US20150094830A1 (en) Network-based Care System
Jabbar et al. IoT-BBMS: Internet of Things-based baby monitoring system for smart cradle
US20200281521A1 (en) Apparatus, system, and method for monitoring sleep patterns
CN111542865A (zh) 监视器和监视系统
JP6263892B2 (ja) 情報処理装置、情報処理方法、プログラムおよび情報処理システム
KR100376417B1 (ko) 감시시스템
JP2004181218A (ja) 乳幼児の状況監視システムおよび状況監視方法
US11138861B2 (en) Easily customizable inhabitant behavioral routines in a location monitoring and action system
JP6266855B1 (ja) 就寝状態検出システム、就寝状態検出装置および就寝状態検出用プログラム
Kumar et al. [Retracted] Internet of Things‐Based Patient Cradle System with an Android App for Baby Monitoring with Machine Learning
EP3471050A1 (fr) Dispositif, procédé, et système destinés à surveiller une personne surveillée
WO2015057667A1 (fr) Système de soins basé sur un réseau
Patke et al. An innovative approach for infant monitoring system using pulse rate and oxygen level
CN204520704U (zh) 母子手环
Kumar et al. Smart Monitoring System for Physically Handicapped Infants using IoT
Nazee et al. Revolutionary Baby Care Solution: Enhanced Cradle with Advanced Monitoring System
TWM557892U (zh) 生理參數雲端看護系統
Kumar et al. Next-Generation IoT Smart Cradle System for Infant Health and Monitoring
KR20200143097A (ko) 유아의 상태를 실시간으로 확인할 수 있는 유아 돌봄 시스템
Mala et al. Smart Cradle: A Secured Assistance and Monitoring System for Baby Using IoT
Harika et al. Smart cradle system
Samhita et al. IoT-Enabled Modern Parenting with Infant Guard
CN115705768A (zh) 监测系统和方法
TW201738835A (zh) 健康照護系統
Lokhande et al. Internet of Things Based Baby Monitoring System for Smart Cradle

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14796592

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14796592

Country of ref document: EP

Kind code of ref document: A1