EP3123438A1 - Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique - Google Patents

Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique

Info

Publication number
EP3123438A1
EP3123438A1 EP15769644.4A EP15769644A EP3123438A1 EP 3123438 A1 EP3123438 A1 EP 3123438A1 EP 15769644 A EP15769644 A EP 15769644A EP 3123438 A1 EP3123438 A1 EP 3123438A1
Authority
EP
European Patent Office
Prior art keywords
mobile device
clinical
proximity
backend
patient
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
EP15769644.4A
Other languages
German (de)
English (en)
Other versions
EP3123438A4 (fr
Inventor
Jacob Mark
Sajikumar ARAVIND
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.)
Mobile Heartbeat LLC
Original Assignee
Mobile Heartbeat LLC
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 Mobile Heartbeat LLC filed Critical Mobile Heartbeat LLC
Priority to EP22187295.5A priority Critical patent/EP4141883A1/fr
Priority claimed from PCT/US2015/023389 external-priority patent/WO2015149073A1/fr
Publication of EP3123438A1 publication Critical patent/EP3123438A1/fr
Publication of EP3123438A4 publication Critical patent/EP3123438A4/fr
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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • 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/20—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 management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2111—Location-sensitive, e.g. geographical location, GPS

Definitions

  • the aspects of the exemplary embodiment generally relate to controlling an aspect of clinical process by using location-based data correlated with clinical tasks of a clinical process.
  • the current method of controlling a patient care team involves manually setting up and controlling patient care teams.
  • the current methods may be supplemented or improved by location-aware methods dynamically enhance patient care teams.
  • Location-aware methods may also be leveraged to dynamically track patient care assets.
  • FIG. 1 illustrates a schematic representation illustrating an overview of the system for controlling an aspect of clinical process by using location-based data
  • FIG. 1A illustrates a block diagram illustrating the communication between a system backend and a mobile device
  • FIG. 2 illustrates an exemplary flowchart of the operation of the system
  • FIG. 3 illustrates another exemplary flowchart of the operation of the system.
  • FIGS. 4-4A illustrates another exemplary flowchart of the operation of the system.
  • FIG. 5 illustrates another exemplary flowchart of the operation of the system.
  • FIG. 6 illustrates another exemplary flowchart of the operation of the system.
  • FIG. 7 illustrates another exemplary flowchart of the operation of the system.
  • FIG. 8 illustrates a schematic representation illustrating an overview of the system utilizing a system for setting and controlling the functionalities of mobile devices.
  • FIG. 9 illustrates another exemplary flowchart of the operation of the system.
  • FIG. 10 illustrates another exemplary flowchart of the operation of the system.
  • FIG. 11 illustrates another exemplary flowchart of the operation of the system.
  • FIGS. 11A-11B illustrates an exemplary block diagram of the system
  • FIG. 12 illustrates another exemplary block diagram of a portion of the mobile device.
  • FIG. 13 illustrates another exemplary block diagram of a portion of the mobile device.
  • FIG. 14 illustrates another exemplary block diagram of a portion of the mobile device.
  • FIG. 15 illustrates a schematic representation illustrating an overview of the system utilizing a system for proximity-based automated login operations
  • FIGS. 16A-B illustrates a schematic representation of an overview of the system for dynamically enhancing a patient care team; and [00022]
  • FIG. 16C illustrates an exemplary user interface of a real-time clinical team directory;
  • FIG. 16D illustrates another exemplary interface of a real-time clinical team directory
  • FIG. 16E illustrates an exemplary flow chart of the operation of the system
  • FIG. 17 illustrates a schematic representation of an overview of the system for dynamically tracking a patient care asset
  • FIG. 17A illustrates an exemplary flow chart of the operation of the system.
  • the disclosed embodiment encompasses any situation where a physical process is used to control physical tasks. This may include, for instance, warehouse, retail, factory, offices or any other situations where multiple workers or project-workers may be working concurrently on a series of physical tasks to complete a common objective.
  • physical process pathways are also referred to as clinical processes within this application and pertain to a clinical or hospital context.
  • physical tasks are referred to as clinical tasks within this application and also pertain to a clinical or hospital context .
  • Fig. 1 illustrates an exemplary schematic diagram illustrating the system.
  • the present invention will be described with reference to the embodiment shown in the drawings, it should be understood that the present exemplary embodiments can be used individually or in any suitable combination thereof.
  • the aspects of the disclosed embodiment will be described with reference to the drawings, it should be understood that the aspects of the disclosed embodiment can be embodied in many alternate forms.
  • any suitable size, shape or type of elements or materials could be used.
  • system backend 11 is depicted.
  • the system backend 11 is in the form of a general purpose computer system or server system.
  • the system backend 11 can also be multiple computers or servers or any other suitable device.
  • the system backend 11 may be a cloud service provider where processing may be performed by means of a distributed computing system wherein the system backend
  • the system backend 11 is operating on many servers or computers concurrently or in parallel.
  • the system backend 11 is virtual hardware, for example, a virtual server running within a cloud service provider running the system backend 11.
  • the system backend 11 further comprise a mobile device management server 114.
  • the mobile device management server 114 is a module which is configured to manage and control the functionalities of a mobile device remotely according to a predetermined system of rules or criteria.
  • the mobile device management server 114 may be configured to limit access to certain functionalities of a mobile device that may be in communication with the system backend 11 but also provide other functionalities such as but not limited to providing different user interface features and/or enabling applications as will be described further below.
  • the mobile device management server 114 which can also activate "log-in" functionalities, i.e. turning on a Mobile Heartbeat app, which was described in the Workflow and Resource Management System with Integrated Bi-Directional Communications as described in U.S. Patent Application No. 13/027,158, filed on 2/14/2011, which was previously incorporated by reference in its entirety.
  • backend 11 can communicate over a network 12 with mobile devices 16 that also communicate over network 12.
  • the network 12 is a wireless network.
  • the wireless network may be an 802.11 network, but may also be Bluetooth, Bluetooth LE, GSM, RF or any other suitable form of network.
  • the network 12 is a wired network.
  • the backend 11 is able to enable a variety of data communication technology, for example, but not limited to voice-over-IP, video-over-IP, text messaging, public switched telephone networks, or any other form of bidirectional communication. This may take the form of, for example, a voice over IP telephony server 113.
  • the backend may also run an enterprise application 111 within a server environment or a cloud environment .
  • the enterprise application 111 is implemented using a computer code comprising instructions that may be executed by a processor or multiple processors within the backend 11.
  • the code may be embodied in a computer- readable medium such as a magnetic or optical disk, programmable memory chip, or any other non-transitory computer-readable medium.
  • the enterprise application may communicate with a database 112 and access and update the information within the database.
  • the database 112 may be a login database comprising a database containing information pertaining to user logins, personalized settings and data, and any other suitable credential information.
  • the enterprise application 111 acts as the controller for the workplace and resource system.
  • the login database may be used as part of an automated login system, for example, the one described in Automated Login Initialization On Detection of Identifying Information (hereinafter "Quick Launch”) as described in U.S. Patent Application 13/616,483 filed on 9/14/2012, the disclosure of which is incorporated by reference herein in its entirety.
  • the enterprise application 111 acts as a controller for the clinical process control and presentation system.
  • the server environment upon which the enterprise application 111 runs may take the form of, for example, Java servlets, or any other suitable environment upon which an enterprise application may execute.
  • Login management application 114 may also be on the backend 11 to manage users and device logins .
  • the system backend 11 may be configured for any sort of suitable reasonable use and may not be dedicated specifically for login procedures .
  • the system backend 11 is configured to manage a clinical process that comprises a series of clinical tasks for the care of a common patient which have a predetermined end. Each of the clinical tasks of the clinical process is associated with a clinical task location and each of the clinical task locations for a physical task is different from the clinical task locations of another physical task.
  • the system backend 11 maintains a clinical process directory representing a list of patients or a list of clinical processes.
  • the clinical process directory is comprised of a number of selectable elements which may be represented and interacted with on a mobile device 16 (to be described in greater detail below) .
  • Each of the clinical tasks in the series of clinical tasks for a clinical process corresponds to different selectable elements within the clinical process directory so that each selectable element represents a different clinical task and its associated clinical task location.
  • an array of low energy (LE) beacons (also referred to as "Beacons”) 15 is shown.
  • the array of Beacons may be arranged in a predetermined relationship that may allow for differentiating between different physical locations.
  • each Beacon 15 represents a physical location within an array space.
  • the Beacons 15 allows for objects to resolve, roughly, where they are relative to an array space by resolving which Beacons 15 they are in proximity with. In other aspects, the Beacons 15 may also allow for objects to resolve where they are relative to a space by resolving Beacons 15 that they are in proximity with as well as measuring the changes in proximity to various Beacons 15 to determine relative movements of the object.
  • a Beacon 15 is placed in every hospital room, every ward and every surgical room. However, in other contexts, a Beacon 15 may be placed anywhere near a physical location to represent that physical location - for instance, different storage racks in a storage warehouse or departments within a retail store or any other suitable example.
  • the Beacons 15 may be placed such that they are in an arrangement with some locational relationship relative to each other and subdivides locations into sublocations by which localization may be determined.
  • Each Beacon 15 may have a Beacon transceiver 15A which may each broadcast a Beacon signal which identifies each particular beacon.
  • the Beacon transceiver 15a may transmit via Bluetooth® Low Energy (BLE) .
  • BLE Bluetooth® Low Energy
  • any suitable form of beacon may be used.
  • a Beacon 15 may transmit simple RF signals, or may be RFID based, NFC, a Wi-Fi signaling device or any other suitable means of broadcasting a Beacon 15 signal.
  • more exotic means of Beacon 15 signals may be used, for instance, infrared or visible light beacons.
  • the array of Beacons 15 are arranged in such away with overlapping zones between the Beacons 15 and between arrays.
  • a mobile device 16 may detect more than one low energy beacon signal, especially in a densely situated location. For instance, on a hospital floor, the beacon signals may bleed through the floors or through the walls . In a locale with many beacons, a mobile device 16 may also be within the proximity of a multiple of beacons. However, the mobile device 16 may be able to detect each of the beacon signals and discriminate or resolve which beacon it is closest in proximity based on the beacon signals received by the mobile device 16.
  • the low energy beacon 15 arrays is distributed separately, one on each floor.
  • one set of array may be for a first floor and a second set of the low energy beacon array may be arranged on the second floor.
  • This is possible where the location is divided up into different locations such as wards.
  • There may be an issue of bleed through where beacon signals from different arrays are detected by a mobile device.
  • it may be possible for a mobile device to discriminate which beacon is the proper beacon to use for proximity purposes based on which distinct array the mobile device 16 is assigned or associated with. For instance, a nurse assigned to work only on a particular floor or wing may have a mobile device 16 which may only use the low energy beacon signals from the array on the floor assigned to them and disregard signals from other floors or other wards detectable because of bleed through .
  • a number of fungible mobile devices 16 may communicate over the network 12.
  • the network 12 may be a wireless network in some embodiments.
  • the wireless network may be an 802.11 network, but may also be Bluetooth, WiMAX, BLE, RF, GSM or any other suitable form of network.
  • the network 12 may also be a wired network.
  • the mobile devices 16 may be generally fungible devices as previously noted, that is, one mobile device 16 may be interchangeable with any other mobile device 16.
  • mobile device 16 may store no personalized settings or data desirable for operation, instead relying on data received from the system backend 11 by means of a device data application 161.
  • the mobile device 16 may be unique to the user, but configured so that functionalities available within the system are locked or blocked when no longer logged in.
  • the availability of the functionalities of the mobile device 16 based on the state of the mobile device 16 is described in greater detail the system described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES as described in U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and Non-provisional U.S. Application No. 14/621,281, filed 2/12/2015, the disclosures of which are incorporated by reference herein in their entireties.
  • the mobile device 16 has a mobile device processor.
  • the mobile device processor is a CPU or System on a Chip (SOC), but in alternate aspects, the mobile device processor may be any suitable processor.
  • the mobile processor may be used to execute a data application 161.
  • the data application 161 may communicate with backend 11 through the data module 116, for example via Web Services such as SOAP protocols, or any other suitable communications protocols and may be capable of accessing and updating data stored within the database 112, possibly through the login manager 114.
  • the device data application 162 may take the form of a native application designed to run as computer code executed by mobile device 16.
  • the computer code may be embodied in a computer-readable medium stored on mobile device 16 such as magnetic or optical disk, programmable computer chip or any other non-transitory computer-readable medium.
  • the device data application 161 may also take the form of a non-native application, for example, a Java-based application running on a virtual machine or a web-based application such as an HTML5 application.
  • the mobile devices 16 may also be in the form of Personal Digital Assistants (PDAs), computer terminals, or any other suitable device capable of running the device data application 166 described above.
  • PDAs Personal Digital Assistants
  • Other devices may also be able to communicate with backend 11 through the network 12 as described above.
  • Each of the mobile devices 16 may further have a beacon signal receiver 16a.
  • the beacon signal receiver 16a may be used to receive a Beacon signal from a Beacon transceiver 15a and may be in communication with the Beacon transceiver 15a.
  • the mobile device 16 may further receive the Beacon signal and allow the mobile device 16 to resolve the mobile device 16 's proximity based on the beacon signal received from the array of Beacons 15 and to correlate the mobile device 16 's proximity with a physical task location.
  • the mobile device 16 may then signal the mobile device 16 proximity to the system backend 11.
  • the beacon signal receiver 16a may receive Bluetooth® Low Energy (BLE) signals. However, in alternate aspects, any suitable form of beacon signal may be received.
  • BLE Bluetooth® Low Energy
  • the beacon signal receiver 16a may receive simple RF signals, or may be RFID based, NFC, a Wi-Fi signaling device or any other suitable means of receiving a Beacon signal.
  • the beacon signal receiver 16a may also receive more exotic means of signaling, including with infrared or visible light signals .
  • each of the mobile devices 16 may have a different predetermined characteristic relating to effecting at least one of the clinical tasks of a clinical process and altering the state of a corresponding clinical process.
  • the predetermined characteristic may include, for instance, the functional groups or the user that the mobile device 16 is associated with (e.g. in the system backend 11) .
  • the functional groups or user permissions may be similar to those described in, for example, the one described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES as described in U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and U.S. Application No.
  • the system backend 11 may further have a location-based module 118.
  • the system backend 11 may use the location- based module 118 to register a device proximity signaled from the mobile device 16 (which the mobile device 16 resolved from the signals received from the Beacon transceiver 15a with the beacon signal receiver 16a) .
  • the system backend 11 may correlate the mobile device proximity with the location of a clinical task of a clinical process generated by the system backend 11.
  • the system backend 11 may further be configured to initiate a predetermined action associated with the state of a clinical task based on the mobile device proximity.
  • the system backend 11 may further be configured to determine whether a mobile device 16 is available to receive a communication related to a corresponding clinical task based on the proximity resolved by the mobile device with respect to the clinical task.
  • the mobile devices 16 are in communication with the system backend 11.
  • Fig. 1A a diagram illustrating the communication between system backend 11 and mobile devices 16 is shown.
  • the mobile devices 16 are configured to present (e.g. on a user interface on the display of a mobile device 16) a list of patients corresponding to a clinical process directory 100 to a user. Each listed patient of the list of patients presented by the mobile device 16 is received from and dynamically updated by the system backend 11.
  • the list of patients 100 presented by the mobile device 16 substantially corresponds to a listing of clinical processes.
  • each clinical process directory 105 is comprised of different selectable elements where each selectable element of the clinical process directory represents a different clinical task 110 and its location.
  • the selectable elements are selectable by the user via the device user interface as will be described in further detail below.
  • the predetermined characteristics of the mobile device 16 enable a user to alter the state of a corresponding selectable element within the clinical process directory 105.
  • Altering the state of a selectable element within the clinical process directory is changing the state of a clinical task 110 and may include, for example, signaling that a user is on the way to a clinical task 110 and the associated clinical task location based on a resolved location of a mobile device 16. However, in other aspects, altering the state of a selectable element may also include escalating a clinical task 110.
  • each of the selectable elements (e.g. clinical tasks 110) within the clinical process directory further corresponds to a care team directory 115 associated with each patient clinical task.
  • the care team directory 115 is generated and dynamically updated by the system backend 11 and includes a listing of available care members of a patient clinical team associated with a patient clinical task.
  • the care team directory 115 maintained by the system backend 11 and presented by the mobile device 16 may comprise one or more care team directory selectable elements 120.
  • the care team directory selectable elements 120 may be associated with a care member of a patient clinical team (e.g. each of the different selectable elements represents a different corresponding member of the clinical team that is associated with the corresponding clinical task 110 of the clinical process 105) and reflect the availability of the care member of the patient clinical team based on the care member's location and/or proximity.
  • the selectable elements within the clinical process directory 100 also corresponds to any suitable information in a clinical setting and pertaining to a clinical process, for example, clinical laboratory work or laboratory results.
  • the system backend 11 is able to maintain and dynamically update the clinical process directory 100, the clinical process 105, clinical task 110 and the care team directory 115 based on the resolved proximities of the mobile devices 16 within the system.
  • the dynamically updated clinical process directory 100, the clinical process 105, clinical task 110 and the care team directory 115 is also dynamically represented on the mobile devices 16 in real time.
  • the dynamical enhancement and updating of care team directories 115 is described below in greater detail.
  • the system backend 11 also has an Application Programming Interface (API) module 117.
  • the enterprise application 111 can communicate with the API module 117.
  • the API module 117 provides an interface for a third party user 17 to access clinical data from a generated clinical process 105 (e.g. clinical process directory 100, the clinical process 105, clinical task 110 and the care team directory 115) corresponding to a particular patient with the system backend 11 substantially in real time.
  • third party users 17 include third party application makers which request access to at least a portion of the information associated with the clinical process directory 100.
  • third party users 17 may include, for instance, web developers making healthcare tracking portals, widget makers which display information related to patients or any other suitable application.
  • Third party users 17 can also include suitable hardware manufacturers, for instance, those that create devices for tracking a clinical process 105. For instance, this may include bedside displays or smart watches or wearable devices or any other suitable devices which may access a patient's clinical process 105.
  • the API module 117 functions as an intermediary interface between the third party user 17 and the enterprise application 1111.
  • the third party user 17 can access the clinical process directory 100 and care team directory 115 generated by the system backend 11 by making calls to the API 117. It is noted that any changes to the state of the clinical process directory 100, or clinical processes 105, clinical tasks 110 or care team directory 115, whether caused by a mobile device 16 or by the system backend 11 will immediately and dynamically available on all devices which can access the API module 117.
  • the Beacons 15 of the low energy beacon array is arranged in a predetermined relationship (for instance, in each location of an array space) which allow differentiating between different clinical task locations for the clinical tasks of a clinical process.
  • the Beacons 15 transmit identifying beacon signals.
  • the Beacons 15 are communicably connected to mobile devices 16.
  • the mobile devices 16 receive the Beacon 15 signals.
  • the mobile device 16 can discriminate between the Beacon 15 signals between near and far Beacons 15.
  • the mobile device 16 identifies the proximate Beacon 15 (e.g. the Beacon 15 that is the closest in proximity) and uses the proximate Beacon 15 to resolve the proximity of the mobile device 16.
  • the locational units within an array space i.e. a predetermined work environment
  • the array space is a hospital or a healthcare facility in this context that is divided into different wards or wings.
  • further subsections of each locational unit may be identified. For instance, once a hospital has been divided into different wards or wings, the wards or wings may further be divided into smaller locational subunits or subsections. For instance, a ward may be divided up into beds or rooms .
  • a Beacon 15 of the low energy beacon array is installed at each subsection within each locational unit.
  • each mobile device 16 is configured or enabled to receive a communication from the Beacon 15. As noted, in one aspect, this communication is a beacon signal transmitted by the Beacon signal transceiver 15a and received by the Beacon signal receiver 16a. In alternate aspects, these may be any suitable form of localization signals.
  • the mobile devices 16 receive the beacon signals with the beacon signal receiver 16a and discriminate between the beacons that are closes and further away. The mobile device 16 may use this to identify the proximate beacon 15 (i.e. the one closes to the mobile device) and use this to resolve the proximity of the mobile device 16 at block 306 to a Beacon 15.
  • the Beacons 15 of the low energy beacon array is arranged in a predetermined relationship (for instance, in each location of an array space) which allow differentiating between different clinical task locations for the clinical tasks 110 of a clinical process 105.
  • a group of mobile devices 16 are connected via the network to the system backend, each mobile device 16 may have a different predetermined characteristic.
  • the predetermined characteristics may be different functional groups or user permissions associated with each mobile device 16 similar to those described in, for example, the one described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES as described in U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and Non-provisional U.S. Application No. 14/621,281, filed on 2/12/2015, the disclosures of which were previously incorporated by reference their entireties.
  • the low energy beacon array of Beacons 15 may be communicably connected to each of the mobile devices 16 via beacon signals (i.e. localization signals) .
  • Each mobile device 16 can resolve its relative proximity from the beacon array relative to a clinical task 110 location in block 504.
  • each mobile device 16 may signal its resolved relative mobile device proximity to the system back 11.
  • the system backend 11 registers the mobile device 17 proximity based on the mobile device 16 localization performed at block 504.
  • the system backend 11 initiates a predetermined action associated with the state of a clinical task based on the resolved mobile device proximity at block 507.
  • the predetermined actions include changing a state of the clinical task 110 within the clinical process 105.
  • the predetermined actions include registering the real time presence of a mobile device 16 relative to the location represented by a clinical task 110.
  • the predetermined action may also be selecting between sending and not sending a communication to the mobile device 16 based on registering the mobile device real time presence at the proximity represented by the clinical task.
  • the mobile devices 16 is configured to receive communications from the system backend 11 related to a clinical process 105.
  • the communication may be, for instance, an alarm generating signal or a signal turning off an alarm on the mobile device.
  • the predetermined action may also be escalating an alarm to another of the mobile devices based on the real time presence of the mobile device 16 and other mobile devices 16.
  • the predetermined action may also include mapping the group of mobile device 16 proximities as well as tracking the real time presence of each of the mobile device 16 with respect to a clinical task 110.
  • the predetermined action may be registering and tracking of each mobile device 16 proximity and real time presence relative to a corresponding clinical task 105.
  • any suitable predetermined action may be used.
  • the predetermined actions may include multi-stepped actions.
  • the predetermined action 401 may include block 402 where the mobile device 16 communicates status of the user and a relative proximity of a mobile device 16 to the system backend 11.
  • the system backend 11 in block 403 can update the status and relative proximity of a user associated with the mobile device 16 based on the information received in block 402.
  • this updated status and relative proximity of a user can manifest in an updated care team directory 115, or an updated clinical process directory 105 which will be described in greater detail below.
  • the system backend 11 can further correlate the mobile device's relative proximity with a clinical task 110 of a clinical process 105 on the basis of the resolved proximity according to the detected beacon signal. That is, the system backend 11 can determine whether the resolved proximity for a mobile device 16 correlates to a proximity or location associated with a physical task. For example, if a clinical task 110 of a clinical process 105 has a location or proximity associated with a particular room, if the mobile device 16 's resolved proximity is near the beacon found in that particular room, then the system backend 11 will be able to correlate the resolved proximity with the location associated with the clinical task 110 of the clinical process 105.
  • the system backend 11 may be able to determine that when a mobile device 16 has been detected within the proximity of the particular location of the clinical task 110, then it would appear that the user of the mobile device 16 has arrived to address that clinical task 110 of the clinical process 105.
  • the system backend 11 may track mobile device proximity for auditing purposes, for example, to see how quickly users are arriving at locations associated with clinical tasks 110 of a clinical process 105 in response to alerts or notifications. In alternate aspects, any other data used for auditing performance may be suitable.
  • the system backend 11 may also disable escalations or alerts for a clinical task of the clinical process 105 based on the mobile device 16 proximity.
  • the system backend 11 may disable the alerts or notifications associated with that clinical task 110 because a user has arrived to address that clinical task 110.
  • the system backend 11 will escalate the alert to a higher level to ensure that the clinical task is completed.
  • the system may be used to enhance patient care teams and improve patient care dynamically, on a real-time or on a substantially real-time basis. Dynamic enhancement of patient care teams (e.g. generating a dynamically updated care team directory 115) is described further below in greater detail.
  • a system backend 11 is initialized with a clinical process directory 100, which, as noted is communicated to a mobile device 16 and presented on the mobile device 16 in the form of a patient list.
  • the clinical process directory 100 maintained by the system backend 11 and communicated to the mobile device 16 has one or more clinical process 105c.
  • Each clinical process 105 includes at least one clinical task 110.
  • Each of the clinical tasks 110 may have a location or proximity or beacon associated with the clinical task 110.
  • the system backend 412 generates an alert/notification based on a clinical task 110 of the clinical process 105.
  • the system backend 11 may receive resolve proximities of the mobile devices 16 within the network 12 that are communicating with the system backend 11.
  • the system backend 11 determines whether there is a mobile device 16 with a resolved proximity that is at the location associated to the clinical task with the alert/notification that is still currently active. If there is a mobile device 16 with a resolved proximity at the location associated with the physical task, the flow goes to 417, where the system backend 11 disables the alert/notification. This may mean, for example, that the system backend 11 recognizes that a mobile device 16 has arrived at the location associated with the clinical task 110 in order to resolve the clinical task 110.
  • the flow may go to block 415, where the system backend 11 may escalate the alert/notification to the next level.
  • the system backend 11 may escalate the alert/notification to the next level. This may mean, for instance, whereas generally, the alert/notification is generally sent to one or a small number of individuals, as the alert is escalated, the alert is brought to the attention of more and more individuals - for instance, supervisors or managers to ensure that the clinical task 110 is resolved.
  • the system backend 11 is configured to dynamically enhance a care team directory 115 for a clinical task 110 by expanding the number of the care team members 120 as part of the care team directory 115 associated with the clinical task 110.
  • the system backend 11 at block 416 also checks to see if there is a mobile device 17 with are solved proximity at the location associated with the clinical task 110 periodically. If a mobile device 16 has a resolved proximity at the location associated with the clinical task, the escalated alert/notification is disabled and the flow returns to 417. If, however, there is not, the flow returns to block 415 where the query will continue until some user responds to the alert/notification .
  • a system backend connected to a network is initialized.
  • a group of mobile devices 16 is initialized, each mobile device communicably connected to the system backend 11.
  • Each mobile device 16 may have a different predetermined characteristic related to the effecting of at least one physical task and altering the state of a corresponding clinical process related to that clinical task.
  • the system backend 11 determines whether each of the mobile devices 16 may be available to receive a communication related to the corresponding clinical task based on localization signals from the mobile device 16.
  • a system backend 11 connected to the network is initialized.
  • a group of mobile devices 16 may be communicably connected to the system backend 11, each mobile device having a different predetermined characteristic related to effecting a physical task and altering the state of a corresponding clinical task.
  • a low energy beacon array of Beacons is arranged in a predetermined relationship with and differentiating between different clinical task locations.
  • each Beacon 15 of the low energy beacon array broadcasts a beacon signal.
  • the mobile devices 16 receive the beacon signal with the beacon signal receiver 16a.
  • each mobile device 16 resolves its proximity from the beacon signal from the low energy beacon array relative to a clinical task location of a clinical process.
  • the system backend 11 registers each mobile device's proximities and map each of the mobile devices 16, allowing the system backend 11 to track a real-time proximity of each mobile device 16.
  • the Beacons 15 may also facilitate other actions by leveraging the localization capabilities of mobile devices 16 using the beacons 15.
  • the beacons 15 may facilitate a means to dynamically enhance patient care teams and to enhance clinical work flows and improve patient care in a substantially real-time basis. This may be accomplished in an instance of a patient care clinical process 105 having multiple patient clinical tasks 110 (for example, medicine, diagnostics, patient laboratory work, etc.).
  • patient clinical tasks 110 for example, medicine, diagnostics, patient laboratory work, etc.
  • the patient care team may include, for example, nurses, doctors, lab technicians and any other suitable members of a patient care team.
  • the patient care team may also include, for instance, administrators, managers and overseers for each group.
  • the patient care team members within a patient care system may be dynamically selected within a healthcare facility (which may be integrated or distributed) .
  • Each of the patient care team members may be associated with a mobile device 16.
  • Each of the mobile devices 16 may be able to resolve its relative proximity based on the beacons 15 similar to what is described above.
  • the system backend 11 may, dynamically and in real-time, make enhancements to the patient care team to generate a care team directory 115.
  • the system backend 11 may dynamically generate, in realtime, a care team directory 115 by determining status (e.g. whether a patient care team member is busy with another task) or by determining availability (whether a patient care team member is within a certain facility) of the patient care team members.
  • the system backend 11 may also further enhance a patient care team by other criteria in addition to the resolved proximities of each patient care team member. Such criteria may include, for instance, manually entered status of each patient care team members on their mobile devices 16 (e.g. if a patient care team member indicated that they are on a break or if they are having a meal) .
  • the enhanced patient care team is represented on the mobile device as the care team directory 115 and is communicated to the mobile device 16 from the system backend 11.
  • the system backend 11 is able to dynamically resolve care team members of a patient clinical team by dynamically updating a care team directory 115.
  • the care team directory 115 is generated by the system backend and is presented by the mobile device 16 as one or more care team directory selectable elements 120 associated with an available patient care team member based on the resolved proximity of each patient care team member according to their associated mobile device 16.
  • the total group of patient care team members 16c-j includes all of the care members of a patient care team within a hospital, healthcare facility or clinical facilities responsible for the patient care, or patient care related task for a given patient (s) .
  • the system backend 11 can dynamically identify and generate the patient care team.
  • the patient care team may include all of the nurses assigned (in a backend registry) to take care of a particular patient during his stay (e.g. with respect to a clinical process for a particular patient), and are linked via responsive mobile device 16c-j to patient system backend 11 during a common predetermined period of time (e.g.
  • the low energy beacons 15c-f may substantially correspond with the beacon 15 described previously and are arranged within an array space.
  • the low energy beacons 15c-f may also be detectable by mobile devices 16c-j, which also substantially corresponds with the mobile device 16.
  • Each of the mobile devices 16c-j is associated with a particular member of a patient care team. This association may be tracked in real time by the system backend 11 as described in greater detail herein.
  • Each mobile device 16c-j may be configured to resolve its relative proximity based on the detected proximity to one or more of the low energy beacons 15c-f.
  • the respective resolved proximities may enable the system backend 11 to determine the relative positions of each patient care team member within a healthcare facility (or across multiple facilities) .
  • the system backend 11 may be configured to dynamically generate the patient care team based on the automated login initialization described in greater detail further herein (see Fig. 15) .
  • the care team members may be coupled or linked, via their mobile devices 16c-16j to each other, sharing various functions and data on their devices with respect to the given patient (s) .
  • the care team members, and more specifically the respective mobile devices 16c- 16 j associated with each member of the patient care team (for the purposes of simplicity, the patient care team member and his/her associated mobile device 16c-j are interchangeably used) , as well as functions and data associated therewith are dynamically modified, thereby enhancing information and function of the care team members, and hence of the patient care team, based on proximity data.
  • the system backend 11 may thus dynamically enhance or generate the enhanced patient care team 1601 (corresponding to the care team directory 115) based on the resolved proximities of each patient care team member (represented by mobile devices 16c-j). Such enhancement may be performed by the system backend 11 whenever a change in status, based on the resolved proximities of the mobile devices 16c-j, is detected.
  • Such enhancement operations be performed iteratively (that is, whenever a change is detected, that is, in real-time or substantially real-time) or it may be done after sufficient changes (change quantum), based on the resolved proximity of mobile devices 16c-j, is detected.
  • the system backend 11 can dynamically change the state (e.g. the availability) of the care team directory selectable elements 120 associated with patient care team member based on the patient care team member's location or current availability based on the resolved proximity of the patient care team member's mobile device.
  • the enhancement may be performed at any suitable timeframe to enable substantially dynamic updating and enhancing of the updated patient care team 1601.
  • the enhanced patient care team 1601 may be one which is filtered by proximity to a predetermined location or locations related to a given clinical process 105 (for example, when patient team members automatically login within the predetermined location (s) or logout within the predetermined location (s)) .
  • Mobile device 16i shown in phantom in Fig. 16A is representative of devices not included by the backend 11 as part of the enhanced patient care team 1601 (e.g. devices) not yet logged into by a patient care team member of the facility.
  • a patient care team member associated by the backend 11 with a particular patient process but not (based on resolved proximity) within the predetermined location (s) related or bound to the given patient care process (for instance, represented by mobile device 16 j) will also not be included as part of the enhanced patient care team 1601 (e.g. the respective device may be dynamically decoupled from the shared functions and data of the team and the functionality and shared information of the team member's mobile devices 16 is dynamically changed by the system backend 11 to reflect decoupling or removal of a patient care team member) . All of these changes are reflected as dynamically updated changes of state of the care team directory selectable elements 120 within a care team directory 120 maintained by the system backend 11 and presented by a mobile device 16.
  • the system may dynamically enhance the patient care team members by adding patient care team members to the given enhanced patient care team 1601 based on resolved proximity in a manner similar to, but opposite to that described above.
  • the system backend 11 is able to create an enhanced patient care team 1601 that comprises a subset of the relevant and available patient care team members to enhance the operation of a patient care proces s .
  • the enhanced patient care team 1601 is updated and enhanced by the system backend 11 based on changes related to proximity data for the mobile devices 16c-j (and Fig. 16B schematically illustrates the system with the enhanced patient care team 1601 having a different enhancement or enhanced status) .
  • the changes related to proximity data is represented as changes in the state of a care team directory selectable element 120 of a care team directory 115 generated by the system backend 11 and presented by the mobile devices 16. This may include instances where a change in resolved proximities for each of the mobile devices of the enhanced patient care team 1601 is detected (i.e. the system backend iteratively updates and enhances the patient care team 1601 based on resolved proximity data) .
  • the system backend 11 dynamically removes them from the enhanced patient care team 1601.
  • the enhanced patient care team 1601 may be incrementally updated to include the patient care team member.
  • the system backend 11 may dynamically update the enhanced patient care team 1601 to include the patient care team member associated with mobile device 16g.
  • the system backend 11 can take them into account and determine whether they are to be included as part of the enhanced patient care team 1601 based on their respective resolved proximities.
  • mobile device 16k was included as part of the enhanced patient care team 1601, but mobile device 161 was not.
  • the enhanced patient care team 1601 may be continuously updated and enhanced based on the resolved proximities of the mobile devices 16c-j .
  • the enhancement of the patient care team 1601 may occur whenever a change in a resolved proximity for a patient care team member (represented by mobile devices 16c-j) is detected by the system backend.
  • the enhanced patient care team 1601 may facilitate and enable many functionalities within a clinical process 105. By grouping patient care team members within the enhanced patient care team 1601, simplified interactions between patient care team members are possible. Instead of situations where a patient care team member must identify another patient care team member related to a patient care process, track down that other patient care team member and communicate with the other patient care team member, the enhanced patient care team 1601 greatly simplifies communications with other patient care team members by providing easy access to patient care team members associated with a clinical process 105 and within proximity to predetermined location (s) related or bound to the given patient care process. For instance, the enhanced patient care team 1601 may be leveraged for generating real-time care team directories 115.
  • the care team directories 115 serve, in one aspect, as a representation (such as may be represented on the mobile device 16 of each patient care team member) of the enhanced patient care team 1601.
  • These real-time care team directories 115 simplify communication within an enhanced patient care team 1601 by creating a directory of other patient care team members associated with the clinical process 105 and within proximity to location (s) associated with the patient care process. This allows for patient care team members to have a simplified method to find other patient care team members they are working with to effect a patient care process. This is illustrated by Fig. 16C, which shows an exemplary real-time care team directory 115' related to a particular patient care process of a given patient and represented on a mobile device 16.
  • the icons or facets 1611a-1611c of the directory 115' corresponds to the members of the patient care team or the enhanced patient care team 1601 illustrated in Figs. 16A-16B and described previously.
  • the facets embody, for example, functionalities and data shared with patient care team members.
  • the real-time care team directory 115' includes resolved proximity data 1612a-c for each patient care team member 1611a-c as well as status information for each patient care team member 1611a-c.
  • the real-time clinical directory 1610 may also include a functionality to page or contact (see page function 1613) all of the patient care team members of an enhanced patient care team 1601.
  • the directory 1610 is enhanced in accompaniment with the enhancement of the patient care team 1601 (e.g. proximity filtering patient care team members as previously described) and the corresponding links between team members, exemplified here by the contact or "page" functionality is commensurately enhanced by proximity resolution.
  • the patient care team 1601 e.g. proximity filtering patient care team members as previously described
  • the corresponding links between team members exemplified here by the contact or "page” functionality is commensurately enhanced by proximity resolution.
  • the real-time care team directory 115 is also represented in the form of a dynamically updated contact directory for an organization or subdivision of an organization.
  • a real-time clinical directory 1620 is shown listing the patient care team members for a subdivision (in this case, the 5 th Floor of a patient care facility) .
  • any suitable subdivision may be represented, including, for example, the entire patient care facility or multiple facilities.
  • the real-time clinical directory 1620 may be dynamically generated and grouped according to patient care team member functional groups in addition to location.
  • the real-time clinical directory 1620 is into different job roles/functional groups (for instance, Charge RNs 1621, MDs 1622 and RNs 1623).
  • the different job roles/functional groups 1621-1623 may include a listing of relevant patient care team members along with their resolved locations 1621a, 1622a, 1623a- c) .
  • the enhanced patient care team 1601 may also be leveraged for simplifying the sharing of patient care data based on the resolved proximities of mobile devices 16c-l. For instance, relevant patient care data associated to a patient care process may be automatically shared among the enhanced patient care team 1601 so that the patient care team members associated with a patient care process and are in proximity to location (s) associated with the patient care process will have simplified access to the patient care data as they are facilitating and effecting the patient care process.
  • the patient care data may include, for instance, patient laboratory results, patient data, patient medical histories, radiology data, prescription data or any other suitable patient data used in the patient care context.
  • the enhanced patient care team 1601 may also allow for simplified communications, notifications and alerts based on resolved the proximities of mobile devices 16c-l. These communications may include, for instance, enhanced asynchronous secure texting or messaging, enhanced paging, enhanced notifications, enhanced alerts, or enhanced voiced communications. In other aspects, any suitable means of communications which may be enhanced by proximity information may be facilitated. For example, enhanced asynchronous secure texting may be possible based on the enhanced patient care team 1601 and updated patient care team 1602. The enhanced asynchronous secure texting may not necessarily be directed to any particular patient care team member, but instead to the enhanced patient care team 1601. Thus, the asynchronous secure messaging will be routed to members of the enhanced patient care team 1601 based on their respective resolved proximities.
  • a member of the enhanced patient care team 1601 may send a communication to all of the other members of the enhanced patient care team 1601.
  • the communication will be automatically and dynamically routed by the system backend 11 to the members of the enhanced patient care team 1602 within proximity to predetermined location (s) related or bound to the given patient care process without further action by the communication sender.
  • the messages may be further dynamically routed by system backend 11 according to proximity to the message sender - that is, the parties closest in proximity will receive the messages first, before the message is propagated to members of the enhanced patient care team 1601 further away from the message sender.
  • the messages may be sent to all members of the enhanced patient care team 1601 substantially at the same time .
  • the system backend 11 may further escalate the messages based on the enhanced patient care team 1601, for example, by escalating the messages to other members of the enhanced patient care team 1601 based on their proximity to predetermined locations related or bound to the given patient care process ensuring that someone within the enhanced patient care team 1601 will be able to get crucial communications and data.
  • this dynamic routing may also be available for voice communications - for example, voice over IP (VOIP) communications.
  • VOIP voice over IP
  • the enhanced patient care team 1601 and 1602 may also help improve alerts and notifications between all parties of the enhanced patient care team 1601.
  • notifications and alerts related to a patient care process can be pushed along as it is being propagated between the members of the enhanced patient care team 1601 within proximity to the predetermined location (s) related or bound to the given patient care process. If a member of the enhanced patient care team 1601 does not respond to the alerts or notifications, the alert or notification may be pushed or escalated to additional members of the enhanced patient care team 1601 by the system backend 11. This may be accomplished by, for instance, expanding the range of the predetermined location (s) related or bound to the given patient care process to reach more patient care team members.
  • the enhanced patient care team 1601 and updated patient care team 1602 may also allow for discrimination and filtering of communication type and content according to proximity to the predetermined location (s) related or bound to the given patient care proces s .
  • the enhanced patient care team 1601 and updated patient care team 1602 may also allow for grab and go activation of mobile devices 16 for busy clinicians.
  • the system backend 11 may automatically activate mobile devices 16 for incoming patient care team members.
  • This simplified or substantially automated activation of mobile devices 16 may be based on proximity of the mobile devices 16 to a predetermined location (s) related or bound to the given patient care process. For instance, where within a predetermined location (s) related or bound to the given patient care process, the system backend 11 may update the enhanced patient care team 1601 to reflect certain patient care team members leaving or logging out of their mobile devices 16.
  • the system backend 11 may automatically activate and login mobile devices 16 for patient care team members who are arriving or starting their duty shift based on proximity information.
  • This automatic login based on proximity information may be used in conjunction with the automated login system described in Automated Login Initialization On Detection of Identifying Information (hereinafter "Quick Launch") as described in U.S. Patent Application 13/616,483 filed on 9/14/2012, the disclosure of which is incorporated by reference herein in its entirety.
  • This automated login system may facilitate a more efficient operation of patient care proces ses .
  • FIG. 16E a block diagram illustrating the enhancement of a patient care team is shown.
  • the system backend 11 is initialized and generates patient care processes.
  • the system backend determines the patient care team members associated with a patient care process.
  • the system backend determines the resolved proximities for the patient care team members associated with a patient care process. As noted above, this is accomplished by enabling the mobile devices 16c-k to resolve their respective relative proximities based on the beacons 15c-f and sending this information to the system backend 11.
  • the system backend 11 generates enhanced patient care teams 1601 based on the resolved proximities of the mobile devices 16c-k.
  • beacons 15 may also define a system for substantially real-time asset tracking for moveable assets within a patient care facility. This may be accomplished by a process known as "crowd sourcing.” Crowd sourcing allows for large tasks to be performed by leveraging a "crowd” (i.e. a group) of people to perform smaller tasks collectively to contribute to the larger task.
  • a number of mobile devices 161-n may enable a substantially realtime and passive tracking of moveable assets based on proximity information detected by mobile devices 16 without a dedicated asset tracking system.
  • This system for asset tracking feature is coincident with providing enhanced patient care team based on resolved proximities.
  • the backend 11, network 12, beacons 15f-n, mobile devices 161-n may substantially correspond to system backend 11, network 12, beacons 15 and mobile devices 16 as previously described.
  • Fig. 17 includes moveable assets 18a-n.
  • Moveable assets may be, for example, medical equipment, gurneys, IV stands or any other equipment within a patient care facility that is moveable (except for consumable supplies like bandages and syringes).
  • moveable assets 18 are often durable equipment. Patient care facilities often have many pieces of moveable assets comprising of expensive medical equipment and there is a need for a simple way to track the movement of the moveable assets 18a-n.
  • Each of the moveable assets 18a-n may also have their own low energy beacon similar to those of beacons 15.
  • Each of the beacons on the moveable assets 18a-n are differentiable and are distinct from each other to allow for identification of each moveable asset 18a-n.
  • the mobile devices 161-n are able to determine and resolve its relative proximity based on the beacons 15f- n of the low energy beacon array.
  • the system backend 11 may be able to determine a relative location within a patient care facility for each mobile devices 161-n.
  • the mobile devices 161-n may also detect proximity to beacons of moveable assets 18a-n as the moveable assets 18a-n are moved around the patient care facility.
  • moveable assets 18a-n may be further subdivided into different asset groups 190, 191, 192. These different asset groups 190, 191, 192 may be comprised of different types of moveable assets 18a-n.
  • the mobile devices 161-n may pass information related to detected moveable assets 18a-n along to the system backend 11.
  • the system backend 11 may be able to dynamically, and in substantially real time, track the movement of the moveable assets based on the detected proximities from the mobile devices 161-n. This allows for a substantially real-time and dynamic asset tracker without devoting an active tracking system for the moveable assets 18a-n.
  • system backend 11 may use the detected proximities for moveable assets 18a-n from many mobile devices 161-n to dynamically determine an accurate position for each moveable asset 18a-n. For instance, the system backend 11 may use signal triangulation from multiple mobile devices 161-n to pinpoint the relative proximity of a particular moveable asset 18a-n. The system backend 11 may also use the detected proximities of moveable assets 18a-n from multiple mobile devices 161-n to enable error correction. For instance, system backend 11 may take the detected proximities for one moveable asset 18a from multiple mobile devices 161-n to correct for a false signal, a signal reflection or floor bleed through from one of the mobile devices 161-n.
  • FIG. 17A a block diagram illustrating the asset tracking system for moveable assets 18a-n is shown.
  • the system backend 11 is initialized.
  • the mobile devices 161-n resolve their relative proximities based on low energy beacons 15f-15n.
  • the mobile devices 161-n further detects moveable assets 18a-n.
  • the mobile device 161-n sends the resolved relative proximity and detected moveable assets 18a-n to the system backend 11.
  • the system backend updates the locations for the moveable assets 18a-n based on the resolved relative proximities of the mobile devices 161-n and the detected moveable assets 18a-n.
  • the system backend 11 may return to block 1701 and repeat the process to continuously update the locations of the moveable assets 18a-n .
  • the Beacons 15 may be used in additional uses beyond merely localization.
  • the Beacons 15 may be used to facilitate a substantially one-step or simplified login procedure. This may be similar to the simplified login procedure described in U.S. Patent Application 13/616,483 filed on 9/14/2012, the disclosure of which was incorporated by reference herein in its entirety previously.
  • the proximity of a device may be used to determine which mobile device 16 to activate or complete a login procedure.
  • a mobile device 16 within a certain proximity may be logged in in a simplified manner where the login procedure is initiated in a known proximity.
  • the correlation between where the login procedure is initiated and where a mobile device 16 is may be used to simplify the action of login.
  • FIG. 8 another exemplary block illustration of the system is shown.
  • the system shown in Fig. 8 may correspond substantially with the system shown in Fig. 1.
  • a system backend 811 which may substantially correspond with to the system backend 11.
  • the system backend 811 may communicate over network 812, which may substantially correspond with network 12 in Fig. 1.
  • Network 812 further may connect with a low energy beacon array comprised of beacons 815.
  • the beacons 815 may also substantially correspond to the beacons 15 shown in Fig.
  • the beacons 815 may have a beacon transceiver 815a which may be substantially similar to the beacon transceiver 15a shown in Fig. 1.
  • Each of the beacons 815 may emit a beacon signal with the beacon transceiver 15a, the beacon signal may be periodic and may contain some identifying information which may facilitate resolving proximities or localizing a mobile device.
  • the beacon signals may also be substantially continuous instead of periodic.
  • any suitable means of transmitting the beacon signal may be implemented.
  • the beacon signals may further include additional data.
  • the beacon signals may include data regarding beacon status, such as battery percentage or other status messages for the beacon.
  • the beacon signals may include any other suitable data.
  • a number of mobile devices 816 are shown connected to the system backend 811 via the network 812 via a communications transceiver 816b.
  • the mobile devices 816 's communications transceiver 816b may communicate over any suitable communications protocol with the network 812, including an 802.11 network (i.e. WiFi), Bluetooth, Bluetooth LE, GSM, RF or any other suitable form of network.
  • the communications transceiver 816b may communicate with any other suitable means include any other suitable means of communication, including through hardwired data connections or wired networking connections.
  • the mobile devices 816 may also have a beacon signal receiver 816a.
  • the beacon signal receiver 816a may substantially correspond with the beacon signal receiver 16a shown in Fig. 1.
  • the beacon signal receiver 816a may be configured to receive a beacon signal.
  • the mobile device 816 may further have a Data Application 816c substantially similar to the Data Application 16c disclosed in Fig. 1.
  • Each mobile device 816 may further have two operational modes.
  • One mode may be an awake mode, where the mobile device's communications transceiver 816b is activated and the mobile device 816 is in a state where it is capable of receiving data from the system backend 811 - for instance, alerts, notifications or clinical processes related to a clinical task.
  • the mobile device 816 may also have a sleep mode where the mobile device's communication transceiver 816b is deactivated and the mobile device 816 is no longer in a state where it is capable of receiving data from the system backend 811. This may be, for instance, activated after a predetermined period of time, specifically during periods of inactivity by the device.
  • Certain mobile devices may have features or operating system where the device may be sent into a sleep mode to preserve battery. However, this may influence the ability of the mobile device 816 from receiving necessary data from the system backend 811 such as alerts, notifications and clinical tasks .
  • a flowchart diagram illustrating a means of preserving system readiness is shown.
  • a mobile device 816 is in an awake mode where the communications transceiver 816b is activated and the mobile device 816 is in a state to receive alerts, notifications or clinical tasks.
  • the mobile device 816 determines whether a beacon signal was received by the mobile device 816.
  • the mobile device 816 may receive this beacon signal by means of, for instance, a beacon signal receiver. In one aspect of the disclosed embodiment, this may include a Bluetooth Low Energy transceiver, but in alternate embodiments, any suitable beacon signal receiver may be used.
  • the mobile device 816 may determine whether it can resolve its proximity relative to a predetermined location based on the beacon signal at block 903. In one aspect of the disclosed embodiment, this may involve resolving the proximity of the mobile device 816 based on the beacon signal and determining whether the beacon signal indicates that the mobile device 816 is within a predetermined location.
  • the predetermined location may be a hospital or a section of a hospital in a medical context that a particular caretaker or nurse is assigned to work in. If a nurse or caretaker is assigned to ward A, a detected beacon signal that resolves proximity to a beacon in or near ward B would mean that the mobile device is not proximate to the predetermined location.
  • the mobile device 816 determines whether the last beacon signal expected before the expiration of a predetermined period of time.
  • the predetermined time in this case, may be derived from the predetermined period of time that it takes for a mobile device 816 to enter a sleep mode. Specifically, this predetermined time may be less than the sleep mode predetermined period of time so that the mobile device may be still in the awake mode. Where the mobile device 816 determines that it is the last beacon signal expected before the expiration of the predetermined period of time (i.e. because the expiration of the predetermined period of time may occur between beacon signals), the mobile device 816 may return the flow to 901, where the awake mode is maintained.
  • the flow returns to block 902 and repeats until the predetermined time is satisfied. If, in the case of either block 902 or block 903 that the beacon signal is not received or the resolved proximity is not proximate to the predetermined location, then the flow goes to block 905 where it is checked whether the predetermined period of time needed to go into sleep mode has been reached. If it has, then the flow progresses to block 906 where the mobile device 816 enters the sleep mode and the communication transceiver is deactivated. If it has not, then the flow returns to block 902 from block 905 and the query flow begins again.
  • the predetermined action may include the mobile device 816 passing the beacon status information to the system backend 811.
  • the predetermined action may further include, for instance, passing along a mobile device readiness signal to the system backend 811. For instance, this may be a "heartbeat" sent to the system backend 811 so that the system backend 811 knows the availability of the mobile device to receive data such as alerts, notifications or clinical process.
  • the predetermined action may further include passing along a status of the mobile device 816 to the system backend 811. In alternate aspects, any suitable predetermined action may be performed.
  • a mobile device's proximity to a beacon may affect or augment the built in functionalities of a mobile device or a functionality of a mobile device related to an activity or the functions and operation of a predetermined part of a mobile device.
  • a built in function or a functionality of the mobile device related to an activity may behave differently according to whether the mobile device 816 is proximate to a beacon.
  • a built in function or a functionality of the mobile device related to an activity may be substantially similar to the built in functions as described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES, U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and U.S. Patent Application 14/621,281, filed on 2/12/2015, the disclosures of which were incorporated by reference herein in their entirety previously.
  • the built in functions may relate to photographic, videographic or multi-media functions of the mobile device 816, however in other aspects, any other suitable built in functions may be used.
  • the functionality of the mobile device related to an activity may be similar to a functionality of the mobile device related to a specific clinical process as substantially described in U.S. Provisional patent application 61/939,104.
  • a predetermined part of a mobile device, and/or a built in function or functionality related to an activity on a mobile device 816 is enabled.
  • the mobile device 816 allows for certain built in functions or functionality related to an activity (i.e. a specific clinical process) or some predetermined part of a mobile device 816 to be enabled and accessible by a user of the mobile device 816.
  • the mobile device 816 may determine whether a beacon signal is detected by the mobile device 816.
  • the flow proceeds to block 1003 where the mobile device 816 may be configured to determine whether the mobile device 816 can resolve proximity to a beacon 815 according to the beacon signal and determine the proximity relative to a predetermined location. If the mobile device 816 can determine that it is in proximity to a predetermined location (for instance, a specific hospital), then the flow goes to block 1004 and the mobile device 816 may determine whether it is the last beacon signal expected before the expiration of a predetermined time.
  • the predetermined time may be derived from the sleep mode predetermined period of time that the mobile device 816 may enter into a sleep mode form an awake mode. In one aspect of the disclosed embodiment, the predetermined time may be any suitable period of time less than the sleep mode predetermined period of time. If the predetermined time was reached at block 1004, the flow returns to block 1001 and the steps of inquiry begins again.
  • the flow proceeds to block 1005, where the mobile device 816 may determine whether a sleep mode predetermined period of time is reached. If the sleep mode period of time is reached, then the mobile device may enter a sleep mode at block 106 where the predetermined part of the mobile device and/or built in functions or functionality related to an activity is disabled on the mobile device 816. This may be done, for instance, by the mobile device 816 itself, but it may also be performed by a command or other instruction from the system backend 811.
  • the mobile device 816 may report that the it no longer detects a beacon signal and may send this information to the system backend 811, whereupon, the system backend 811 may command the mobile device 816 to disable the built in functions or functionalities related to an activity being displayed on the mobile device 816.
  • the system backend 811 may also alter the information being sent to the mobile device 816 upon receiving information that the mobile device 816 does not detect a beacon signal.
  • any suitable means by which the built in function or functionality related to an activity is disabled may be used. If, however, the sleep mode predetermined period of time has not yet been reached, then the flow returns to block 1002 and the query begins again.
  • the mobile device 816 may enable all built in functions and functionalities related to an activity (for instance a clinical process related to the treatment of a patient, in a medical context) may be enabled.
  • the physician may be able to take advantage of the full functionalities and built in functions of the mobile device within the data application.
  • a physician may be able to take photos or videography of a patient for the clinical process related to that patient. This information may be used, for instance, for diagnosis or recordkeeping purposes.
  • the physician may also be able to pull up various data related to the clinical process associated with the patients - for instance, billing or clinical charts or any other suitable form of data related to the clinical process.
  • the mobile device 816 being used by the physician may be detecting the beacon signals of the various low energy beacons 815 distributed around the hospital in the low energy beacon array 815.
  • the mobile device 816 may, thus, resolve its proximity to one or more low energy beacons according to the beacon signals received by the mobile device 816 and determine that it is still in proximity to a predetermined region, in this case, the predetermined hospital.
  • the mobile device 816 may no longer detect the beacon signals from the low energy beacons 815 of the hospital's low energy beacon array. Thus, the mobile device 816 's built in functions and functionalities related to the clinical process associated with the physician may be disabled. Thus, the physician's mobile device 816 may no longer be able to access all built in functions, for instance, the ability to take photographs, videography or access the multi-media functions of the mobile device through the data application, nor would the physician's mobile device 816 be able to access the various data related to the clinical process associated with the patient. This helps protect confidentiality and lessens the ability for information to be accessed when outside of a predetermined location or premises.
  • the mobile device 816 used by the physician can determine that it is not in proximity to a predetermined region (i.e. the original predetermined hospital), the built in functions and functionality related to activities (i.e. the clinical process) may also be disabled or otherwise inaccessible to the physician through the mobile device 816 and its data application.
  • a proximity-based system may also be configured to effect a change in the user interface of a mobile device 816.
  • This may be, for instance, the user interface of the Data Application 816c shown in Fig. 8.
  • a flowchart illustrating an exemplary proximity-based control of user interface for a mobile device 816 may be shown.
  • a user interface mode related to an activity is enabled on a mobile device 816.
  • the user interface mode related to an activity i.e. clinical process
  • the predetermined characteristic may affect the display of information on the mobile device 816 's user interface mode. For instance, as substantially described in U.S.
  • the mobile device 816 may determine whether a beacon signal is detected by the mobile device 816. If there is a beacon signal detected by the mobile device 816, then the mobile device 816 may attempt to determine if the mobile device 816 may resolve its proximity to a predetermined location based on the beacon signal at block 1103.
  • the flow may proceed to block 1104, where the mobile device may be determine whether it is the last beacon signal expected before the expiration of a predetermined period of time.
  • the predetermined time may be derived from the sleep mode predetermined period of time that the mobile device 816 may enter into a sleep mode form an awake mode. In one aspect of the disclosed embodiment, the predetermined time may be derived from the sleep mode predetermined period of time, for instance any suitable period of time less than the sleep mode predetermined period of time. If it is the predetermined period of time, the flow returns to block 1101 where the process begins again. If it does not, then it returns to block 1102 and the second user interface mode related to the activity remains configured to display information related to the activity via the predetermined characteristic.
  • the flow proceeds to block 1105, the mobile device 816 is configured to determine whether it is a sleep mode predetermined period of time. If it is, then the flow progresses to block 1106 where the first user interface mode is enabled and the predetermined functionality related to the activity is displayed via a changed predetermined characteristic. If, however, it is not the sleep mode predetermined period of time, the flow returns to block 1102 and the process of checking begins again.
  • the change in user interface based on a predetermined characteristic may be performed on a system backend, the system front end or, a hybrid system.
  • the mobile device 816 may, if the inquiry fails at blocks 1103, 1104 and 1105, signal a system backend 811 as to the resolved proximity based on the beacon signal received by the mobile device 816.
  • the system backend 811 may be configured to change the predetermined characteristic of the data being sent to the mobile device 816 and visible through the mobile device 816 's user interface.
  • the entire operation may be done entirely on the front-end. For instance, where a mobile device 816 may detect a change in proximity, the mobile device may be configured to change the predetermined characteristic accepted or may only accept certain data based on a changed predetermined characteristic.
  • a hybrid system may be accomplished wherein the mobile device 816 may involve the mobile device 816 signaling a proximity change to the system backend 811, which then signals the mobile device 816 to change the predetermined characteristic accepted or only accept certain data based on a changed predetermined characteristic.
  • the changed predetermined characteristic limits the data available on the display of a mobile device 816.
  • FIG. 11A and 11B A block diagram of the system may further be shown in Figs. 11A and 11B which may further illustrate the system described in Fig. 11.
  • Figure 11A and 11B show a system backend 1111 which may be substantially similar to the system backend 11 and 811 shown in Figs. 1 and 8.
  • Figs. 11A and 11B may also show a low energy beacon 1115 which may be substantially similar to the low energy beacons 15 and 815 shown in Figs. 1 and 8, each beacon also having a beacon signal transceiver 1115a which may be similar to the beacon signal transceivers 15a and 815a shown in Figs. 1 and 8.
  • Figs. 11A and 11B show a system backend 1111 which may be substantially similar to the system backend 11 and 811 shown in Figs. 1 and 8.
  • Figs. 11A and 11B may also show a low energy beacon 1115 which may be substantially similar to the low energy beacons 15 and 815 shown in Figs. 1 and 8, each beacon
  • the 11A and 11B also show a mobile device 1116 which may substantially correspond with the mobile devices 16 and 816 shown in Figs. 1 and 8.
  • the mobile device 1116 may further have a beacon signal receiver 1116a, which may substantially correspond with the beacon signal receiver 16a and 816a shown in Figs. 1 and 8.
  • the mobile device 1116 may also have a processor 1116c, a user interface module 1116d and a display 1116e.
  • the beacon signal receiver 1116a can communicate with the mobile processor 1116c.
  • the mobile processor may also communicate with the user interface module 1116d which is able to generate a user interface shown on the display 1116e.
  • the beacon signal receiver 1116a may receive a beacon signal a received from the low energy beacon 1115 and broadcasted by the beacon signal transceiver 1115a.
  • the beacon signal receiver 1116a may pass the beacon signal a to the processor 1116c, which may resolve its proximity based on the beacon signal a received by the beacon signal receiver 1116a.
  • the processor 1116c may further communicate the proximity p a resolved by the processor 1116c based on beacon signal a.
  • the proximity p a is received by the system backend 1111 which may send a predetermined characteristic c a back to the processor 1116c.
  • the processor may receive the predetermined characteristic c a and alter some aspect of the user interface 1116d based on the predetermined characteristic c a .
  • the display d a based on the predetermined characteristic c a is then outputted and visible via the mobile device display 1116e.
  • the beacon signal receiver 1116a may receive a different beacon signal b received from the low energy beacon 1115 and broadcasted by the beacon signal transceiver 1115a.
  • the beacon signal receiver 1116a may pass the beacon signal b to the processor 1116c, which may resolve its proximity based on the beacon signal b received by the beacon signal receiver 1116a.
  • the proximity based on beacon signal b may result in a different proximity p b compared to the proximity p a shown in Fig. 11A (i.e. there was a change in the proximity resolved by the mobile device processor 1116c) .
  • the processor 1116c may further communicate the changed proximity p b resolved by the processor 1116c based on beacon signal a.
  • the changed proximity p b is received by the system backend 1111 which may send different predetermined characteristic c a back to the processor 1116c.
  • the processor may receive the changed predetermined characteristic c b and alter some aspect of the user interface 1116d based on changed predetermined characteristic c b so that the user interface 1116d may show a different set of data or a limited set of data according to the predetermined device.
  • the display d b based on the changed predetermined characteristic c b is then outputted and visible via the mobile device display 1116e .
  • Fig. 9 there may be a system wherein there is a control module which communicatively links the Beacon signal receiver 1216a of a mobile device, which may substantially correspond with the beacon signal receiver 16a and 816a of Figs. 1 and 8, to the communications transceiver 1216b, which may substantially correspond with the communication transceiver 16b, 816b of the mobile device 16, 816 of Figs. 1 and 8, via the control module 1201.
  • the control module 1201 may be configured to control the operation of the communications transceiver 1216b by performing some function - for instance, maintaining activation of the communications transceiver 1216b based on a predetermined state of the beacon signal receiver.
  • this predetermined state may include whether a beacon signal was received by the beacon signal receiver 1216a.
  • other suitable states may include whether a beacon signal was received by the beacon signal receiver 1216a at a predetermined time - for instance a time period less than the time a mobile device enters a sleep mode.
  • any other suitable states may be used.
  • Fig. 13 there may be a system wherein there is a control module which communicatively links the Beacon signal receiver 1316a of a mobile device, which may substantially correspond with the beacon signal receiver 16a and 816a of Figs. 1 and 8, a built in function, functionality related to an activity or a predetermined part of the mobile device 1316b, via the control module 1301.
  • the built in function may include, for instance, any built in function of the mobile device 16, 816. For instance, this may include photography, videography or multimedia functions, but in alternate aspects, any suitable built in functions may be available.
  • the functionality related to an activity may be any functionality related to an activity, for instance, a function related to a clinical process.
  • a built in function or a functionality of the mobile device related to an activity may be substantially similar to the built in functions as described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES, U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and U.S. Application No. 14/621,281, filed 2/12/2015, the disclosures of which were previously incorporated by reference in their entirety.
  • the predetermined part of a mobile device 16, 816 may be any predetermined part, including any suitable physical or software part of the mobile device.
  • the control module 1301 may be configured to control the operation of the built in function, functionality related to an activity or a predetermined part of the mobile device 1316b by performing some function - for instance, maintaining activation of the built in function, functionality related to an activity or a predetermined part of the mobile device 1316b based on a predetermined state of the beacon signal receiver. For instance, this predetermined state may include whether a beacon signal was received by the beacon signal receiver 1316a.
  • other suitable states may include whether a beacon signal was received by the beacon signal receiver 1316a at a predetermined time - for instance a time period less than the time a mobile device enters a sleep mode. In alternate aspects, any other suitable states may be used.
  • Fig. 14 there may be a system wherein there is a control module which communicatively links the Beacon signal receiver 1416a of a mobile device, which may substantially correspond with the beacon signal receiver 16a and 816a of Figs. 1 and 8, and predetermined functionality of the mobile application 1416b, via the control module 1401.
  • the predetermined functionality of the mobile application 1416b related to an activity may be any functionality of a mobile application, for instance, a user interface or user interface mode. This may include, for instance, data which may be presented in the mobile application. In alternate aspects, any suitable functionality may be available.
  • predetermined functionality of the mobile application 1416b may be substantially similar to the user interface modes as described in SYSTEM FOR SETTING AND CONTROLLING FUNCTIONALITIES OF MOBILE DEVICES, U.S. Provisional Patent Application 61/939,104 filed on 2/12/2014, and U.S. Application No. 14/621,281, filed 2/12/2015, the disclosures of which were previously incorporated by reference in their entirety.
  • the predetermined part of a mobile device 16, 816 may be any predetermined part, including any suitable physical or software part of the mobile device.
  • the control module 1401 may be configured to control the operation of the predetermined functionality 1416b by performing some function - for instance, maintaining activation of the built in function, functionality related to an activity or a predetermined functionality of the mobile application 1416b based on a predetermined state of the beacon signal receiver.
  • this predetermined state may include whether a beacon signal was received by the beacon signal receiver 1416a.
  • other suitable states may include whether a beacon signal was received by the beacon signal receiver 1316a at a predetermined time - for instance a time period less than the time a mobile device enters a sleep mode.
  • any other suitable states may be used .
  • the low energy beacons 15, 815 may also be incorporated or included as part of a system referred to here for description purposes.
  • the low energy beacons 15, 815 may also facilitate an automated login, for example in a "Quick Launch" system as described in Automated Login Initialization On Detection of Identifying Information as described in U.S. Patent Application 13/616,483 filed on 9/14/2012, the disclosure of which was incorporated by reference herein in its entirety.
  • a backend 11 is provided (the system described here may be generally similar to that illustrated in Fig. 1 and similar features are similarly numbered) .
  • the backend 11 may substantially correspond to the backends 11 and 811 provided in Figs. 1 and 8.
  • a network 12 is also provided which may substantially correspond to the networks 12 and 812 provided in Figs. 1 and 8.
  • a number of mobile devices 16 may be provided as well which correspond substantially to the mobile devices 16 and 816 shown in Fig. 1 and 8.
  • Each of the mobile devices may be connected to a docking station 23A-N with status indicators 24A-N.
  • the docking stations 23A-N may further be connected to reader devices 21A-N which may have processors 21CA-CN and a reader 21BA-BN.
  • Each reader device 21A-N may further have a low energy beacon 15.
  • the low energy beacons 15 may help facilitate an automated login procedure.
  • the mobile device 16 may be able to determine its relative proximity based on the low energy beacons 15 which is part of the reader device 21A. Because, as previously noted, a mobile device 16 may use also use the low energy beacon 15 to remain in an awake mode. In the system presently described, if the mobile device 16 mobile device 16 is in a sleep mode while in the docking station 23A, then no automated login may occur. Further, in the system currently described, if no proximate beacon signal is detected by the mobile device 16, there may also be no automated login action.
  • An automated login action may require the ability to detect and resolve a relative proximity based on a beacon signal from a low energy beacon 15.
  • the reader device 21A may receive credential information from the complementary identification device 22, which is communicated to the login manager 114 on the backend 11.
  • the login manager 114 may further receive information such as a resolved proximity based on the low energy beacon 15 received by a mobile device 16 which has been removed from the docking station 23A.
  • the login manager 114 may complete the automated login operation based on the combined information between the credentials received and the received resolved proximity from a mobile device 16 to automatically log the user with the complementary identification device 22 onto the mobile device 16 that was removed from the dock.
  • any suitable way where a low energy beacon may be used to facilitate an automated login operation may be employed.
  • a mobile device 16 may be automatically logged in based on a resolved proximity of a low energy beacon 15 at a predetermined location. For instance, a mobile device 16 may automatically log in when it resolves its proximity as to be near a predetermined location. This may take the form of an individual's mobile device 16 automatically logging in once it enters the individual's office or other location. In other aspects, the mobile device 16 may also automatically log out unless the mobile device 16 is able to detect a proximate beacon signal. For instance, if a mobile device 16 leaves the premises of an array space, the mobile device 16 may automatically log out when no beacon signal is detected by the mobile device 16.
  • the mobile device 16 may also automatically log out. In yet other aspects, any suitable automated login operation using a low energy beacon may be employed.
  • a first aspect of the disclosed embodiment for system for controlling process pathways having a system backend having a processor configured to manage a physical process that comprises a series of physical tasks, each with an associated physical location and at least one of which is different than another physical location of a different one of the physical tasks, each of the different physical tasks in the series corresponding to different points along an associated process pathway so that each point represents a different physical task and its location, a group of mobile devices communicably connected via a network to the system backend, each of the mobile devices having a different predetermined characteristic related to effecting at least one of the physical tasks and altering a state of the corresponding pathway point, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different physical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one physical task location and signal the device proximity to the backend processor.
  • the processor is configured to register the device proximity and initiate a predetermined action associated with
  • each of the mobile devices is configured to receive communications from the backend related to the process pathway.
  • the predetermined action is registering the real time proximity of the mobile device relative to the location represented by the process pathway point .
  • the predetermined action is selecting between sending and not sending a communication to the mobile device based on registering the mobile device real time proximity at the location represented by the process pathway point.
  • the communication is an alarm generating signal, or a signal turning off an alarm on the mobile device .
  • the predetermined action is escalating an alarm to another of the mobile devices based on the real time proximity of the mobile device and the other mobile device.
  • the beacon array is a Bluetooth ® low energy (BLE) beacon array.
  • the process pathway embodies the physical process and the processor is configured to manage the process pathway changing states of the pathway point based on the registered device proximity .
  • the action is mapping proximities of the group of mobile devices.
  • the map defines both track and real time proximity of each of mobile device with respect to the corresponding pathway point.
  • the processor initiates the predetermined action based on registering a change in proximity .
  • each mobile device has a device processor resident therein configured to resolve the proximity of the device, from the beacon array, and initiate a predetermined action based on the proximity.
  • a second aspect of the disclosed embodiment for a system for controlling process pathways having a network, a system backend communicably connected with the network, the backend having a processor configured to manage a physical process that comprises a series of physical tasks, each with an associated physical location and at least one of which is different than another physical location of a different one of the physical tasks, and to manage an associated process pathway embodying the physical process, each of the different physical tasks in the series corresponding to different points along the pathway so that each point represents a different physical task and its location, a group of mobile devices communicably connected to the system backend to receive communications related to the process pathway, each of the mobile devices having a different predetermined characteristic related to effecting at least one of the physical tasks and altering a state of the corresponding pathway point.
  • the processor is configured to determine whether each of the mobile devices is available to receive a communication related to the corresponding pathway point based on proximity signals from the mobile devices with respect to the pathway point .
  • the system further having a Bluetooth ® low energy (BLE) beacon array communicably connected to the mobile devices.
  • BLE Bluetooth ® low energy
  • the BLE beacon array is arranged to effect mobile device proximity discrimination between different physical task locations .
  • each of the mobile devices is configured to resolve its proximity with respect to the at least one physical task location with BLE beacon discrimination .
  • a third aspect of the disclosed embodiment for a system for controlling process pathways having a network, a system backend communicably connected with the network, the backend having a processor configured to manage a physical process that comprises a series of physical tasks, each with an associated physical location and at least one of which is different than another physical location of a different one of the physical tasks, and to manage an associated process pathway embodying the physical process, each of the different physical tasks in the series corresponding to different points along the pathway so that each point represents a different physical task and its location, a group of mobile devices communicably connected to the system backend, each of the mobile devices having a different predetermined characteristic related to effecting at least one of the physical tasks and altering a state of the corresponding pathway point, a BLE beacon array arranged in a predetermined relationship with and differentiating between different physical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one physical task location and signal the device proximity to the backend processor
  • the processor is configured to initiate a predetermined action associated with the state of a pathway point based on the real time proximity of at least one mobile device.
  • a fourth aspect of the disclosed embodiment for a system for controlling a mobile device having a system backend with a backend processor configured to manage an activity in a predetermined region, at least one mobile device communicably connected via a network to the backend, and having a processor and at least one built in function, or a functionality related to the activity, controlled by the processor, and a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different locations in the predetermined region, and communicably connected to the mobile device, the processor of which is configured to resolve, from the beacon array, the device's proximity to a predetermined one of the different locations.
  • the processor is further configured so that it disables the built in function or the functionality based on proximity to the predetermined location.
  • the built in function is a photograph, videography or multi-media function.
  • the processor is configured to signal the device proximity to the backend processor.
  • the backend processor registers a change of device proximity and in response changes predetermined characteristic of data, communicated to the device and related to the device functionality, that changes the device functionality.
  • the backend processor sends a communication to the processor that effects a change in the state of the functionality between disabled to enabled in response to the communication.
  • a system for controlling a mobile device having a system backend with a backend processor configured to manage an activity in a predetermined region, at least one mobile device communicably connected via a network to the backend, and a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different locations in the predetermined region, and communicably connected to the mobile device that is configured to resolve its proximity, from the beacon array, relative to a predetermined one of the different locations, and signal the device proximity to the backend processor, the mobile device having a mobile processor and a display, the mobile processor configured to provide, on the display, a user interface mode, related to the activity, via which predetermined data, with predetermined characteristic embodying information related to the activity, is available on the display from the backend processor.
  • the mobile processor is configured to signal the device proximity to the backend processor, and in response to a change in the device proximity the backend processor changes the predetermined characteristic of the data available on the display.
  • a system for maintaining system readiness having a system backend, a low energy beacon array having at least one beacon configured to transmit a beacon signal, a group of mobile devices, each communicably connected via a network to the system backend with a communications transceiver and each mobile device further configured to receive the beacon signal and resolve a proximity relative to a predetermined location, wherein each of the mobile devices further having a sleep mode and an awake mode, where the mobile device's communications transceiver is deactivated in the sleep mode and the mobile device's communication transceiver is activated in the awake mode and the mobile device is further configured to enter the sleep mode from the awake mode in a sleep mode predetermined period of time.
  • the mobile device is configured to receive the beacon signal and, in response to the received beacon signal and based on the resolved proximity relative to a predetermined location, the mobile device is further configured to maintain activation of the awake mode.
  • the mobile device is configured to receive the beacon signal at a predetermined period of time derived from the sleep mode predetermined period of time and in response to the received beacon signal, the mobile devices are further configured to maintain the activation of the awake mode based on the beacon signal received at the predetermined period of time .
  • the beacon signal further comprises a beacon status.
  • the mobile device is further configured to initiate a predetermined action in response to the received beacon signal.
  • the predetermined action further comprises at least one status data of the mobile device .
  • the predetermined action further comprises the beacon status of the at least one beacon which transmitted the received beacon signal.
  • the mobile device is configured to maintain activation of the awake mode based on the received beacon signal at a second predetermined period of time.
  • the mobile device is further configured to maintain an activation of the awake mode based on the received beacon signal at the predetermined period of time derived from the sleep mode predetermined period of time.
  • the mobile device further comprises a beacon signal receiver and a control module
  • the beacon signal receiver is communicably linked via the control module with the mobile device's communication transceiver
  • the control module is configured control the operation of the mobile device's communication transceiver based on a predetermined state of the beacon signal receiver and based on the resolved proximity relative to a predetermined location .
  • control module is further configured to control the operation of the mobile device's communication transceiver by maintaining activation of the mobile device's communication transceiver based on the predetermined state of the beacon signal receiver
  • a system for maintaining system readiness having a system backend, a low energy beacon array having at least one beacon configured to transmit a beacon signal, a group of mobile devices, at least one of the mobile devices communicably connected via a network to the system backend with a communications transceiver and the at least one mobile device further configured to receive the beacon signal and resolve a proximity relative to a predetermined location, wherein the at least one mobile device further having a sleep mode and an awake mode, where a predetermined part of the at least one mobile device and/or a built in function or functionality related to an activity of the at least one mobile device is deactivated in the sleep mode and the predetermined part of the mobile device is activated in the awake mode and the at least one mobile device is further configured to enter the sleep mode from the awake mode in a sleep mode predetermined period of time.
  • the at least one mobile device is configured to receive the beacon signal, where, in response to the received beacon signal and based on the resolved proximity relative to a predetermined location.
  • the mobile device is configured to receive the beacon signal at a predetermined period of time derived from the sleep mode predetermined period of time and in response to the received beacon signal and based on the resolved proximity relative to a predetermined location, the mobile devices are further configured to maintain the activation of the awake mode based on the beacon signal received at the predetermined period of time.
  • the mobile devices are configured to receive the beacon signal at a predetermined period of time and in response to the received beacon signal, the mobile devices are further configured to maintain the activation of the awake mode based on the beacon signal received at the predetermined period of time .
  • the beacon signal further comprises a beacon status.
  • the at least one mobile device is further configured to initiate a predetermined action in response to the received beacon signal.
  • the predetermined action further comprises at least one status data of the at least one mobile device.
  • the predetermined action further comprises the beacon status of the at least one beacon which transmitted the received beacon signal.
  • the at least one mobile device is configured to maintain activation of the awake mode based on the received beacon signal at a predetermined period of time.
  • the at least one mobile device is further configured to maintain an activation of the awake mode based on the received beacon signal at the predetermined period of time derived from the sleep mode predetermined period of time.
  • the at least one mobile device further comprises a beacon signal receiver and a control module
  • the beacon signal receiver is communicably linked via the control module with the at least one mobile device's communication transceiver
  • the control module is configured to control the operation of the predetermined part of the at least one mobile device and/or the built in function or functionality related to an activity of the at least one mobile device based on a predetermined state of the beacon signal receiver and based on the resolved proximity relative to a predetermined location.
  • control module is further configured to control the operation of the predetermined part of the at least one mobile device and/or the built in function or functionality related to an activity of the at least one mobile device by maintaining activation of the predetermined part of the at least one mobile device and/or the built in function or functionality related to an activity of the at least one mobile device based on the predetermined state of the beacon signal receiver
  • a system for maintaining system readiness having a system backend, a low energy beacon array having at least one beacon configured to transmit a beacon signal, and a group of mobile devices, at least one of the mobile devices communicably connected via a network to the system backend with a communications transceiver and the at least one mobile device further having a beacon signal receiver configured to receive the beacon signal and resolve a proximity relative to a predetermined location.
  • the at least one mobile device further comprising a mobile application having a first user interface mode and an second user interface mode, where a predetermined functionality of the mobile application is deactivated in the first user interface mode and the predetermined functionality of the mobile application is activated in the second user interface mode and the mobile application is further configured to enter the first user interface mode from the second user interface mode in a sleep mode predetermined period of time.
  • the mobile application further comprising a control module, where the beacon signal receiver is communicably connected to the predetermined functionality of the mobile application via the control module, the control module further configured to control an operation of the predetermined functionality based on a predetermined state of the beacon signal receiver and the resolved proximity relative to the predetermined location .
  • control module is configured to control the operation of the predetermined functionality when the beacon signal receiver is in the predetermined state at a predetermined period of time derived from the sleep mode predetermined period of time .
  • a system for tracking physical assets within an enclosed facility having a system backend comprising a backend processor configured to track a physical asset location of at least one physical asset within the enclosed facility, a group of mobile devices communicably connected via a network to the system backend, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different physical locations within the enclosed facility, and communicably connected to each of the mobile devices that is configured to resolve its mobile device proximity to the physical locations within the enclosed facility, from the beacon array, the at least one physical asset having a low energy (LE) beacon and detectable by each of the mobile devices, where the low energy (LE) beacon associated with each of the at least one physical asset being distinct from a different low energy (LE) beacon of another of the at least one physical asset, wherein the backend processor is configured to identify the at least one physical asset and dynamically determine its physical asset location based on the resolved mobile device proximity of the at least one mobile device
  • the backend processor determines the physical asset location of the detected at least one physical asset based on the resolved mobile device proximity of a plurality of mobile devices.
  • the backend processor dynamically updates the physical asset location of the detected at least one physical asset upon receipt of the resolved mobile device proximity and the detected at least one physical asset.
  • the backend processor is configured to receive the resolved mobile device proximity from at least one mobile device.
  • the backend processor is configured to determine and track changes in physical asset locations.
  • the backend processor is configured to dynamically update the status of the physical asset.
  • the backend processor is configured to update a characteristic of the physical asset .
  • the backend processor is configured to track inventory and availability of at least one consumable asset.
  • a system for tracking physical assets within a healthcare facility having a system backend comprising of a backend processor configured to manage a patient care process that comprises a series of patient care tasks, each with an associated location and at least one of which is different than other locations of a different one of the patient care tasks, each of the different patient care tasks in the series corresponding to different points along an associated patient care process pathway so that each point represents a different patient care task and its location; a group of mobile devices communicably connected via a network to the system backend, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different patient care task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one patient care task location and signal the device proximity to the backend processor, a group of moveable patient care assets having a low energy (LE) beacon and communicably connected to each of the mobile
  • LE low energy
  • the backend processor is configured to resolve a patient care asset location associated with the at least one patient care asset based on a resolved proximity of the at least one of the mobile devices based on the low energy beacon array.
  • the backend processor may track the patient care asset location of the detected at least one physical asset using multiple mobile devices.
  • the backend processor dynamically updates the physical asset location of the detected at least one patient care asset upon receipt of the resolved mobile device proximity and the detected at least one patient care asset.
  • the patient care asset is associated with at least one patient care task of a patient care process.
  • the backend processor is configured to update the status of the patient care process status on the patient care asset location.
  • a system for controlling patient care process in a healthcare facility having a system backend comprising a processor configured to define a patient care team associated with a patient care process comprising of a series of patient care tasks effected within the healthcare facility, each patient care task with an associated patient care task location within the healthcare facility; a group of mobile devices communicably connected via a network to a system backend, each mobile device being associated with and configured for use by at least one of the members of the patient care team; a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different patient care task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one patient care task location; wherein the processor is configured to dynamically enhance the patient care team by dynamically changing in real-time a predetermined characteristic of the patient care team based on the resolved proximity of each mobile device associated with each member of the patient care team
  • the backend processor is further configured to resolve members of the patient care team for each patient care task based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is configured to dynamically route communication links between team members and content links between patient care team members based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is configured to dynamically route asynchronous secure messaging based on the resolved proximity of each mobile device associated with each member of the patient care team .
  • the backend processor is configured to dynamically route notifications and alerts associated with a patient care process based on the resolved proximity of each mobile device associated with each member of a patient care team.
  • notification and alerts are dynamically escalated by the backend processor based on the resolved proximity of each mobile device associated with each member of the patient care team .
  • the backend processor is configured to filter access to at least one patient information associated with the patient care process based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is configured to filter access to at least one clinical information associated with the patient care pathway based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is configured to filter access to at least one laboratory information associated with the patient care process based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is further configured to generate a patient care process- specific patient care team directory based on the resolved proximity of each mobile device associated with each member of the patient care team.
  • the backend processor is further configured to group each member of the patient care team according to a functional group.
  • the predetermined characteristic is a selection of the members of the patient care team forming the patient care team.
  • the system having a system backend having a backend processor configured to define a patient clinical team associated with a patient clinical process comprising of a series of patient clinical tasks effected within the healthcare facility, each patient clinical task with an associated patient clinical task location within the healthcare facility, a group of mobile devices communicably connected via a network to the system backend, each mobile device being associated with and configured for use by at least one care member of the patient clinical team, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different patient clinical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one patient clinical task location.
  • the backend processor is configured to dynamically enhance the patient clinical team by dynamically changing in realtime a predetermined characteristic of the patient clinical team based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is further configured to resolve care members of the patient clinical team for each patient clinical task based on the resolved proximity of each mobile device associated with each care member of the patient clinical team .
  • the backend processor resolves care members of the patient clinical team by dynamically updating a care team directory associated with each patient clinical task, the care team directory comprising one or more selectable elements, presented on each mobile device, each of the one or more selectable elements associated with each care member of the patient clinical team.
  • the backend processor dynamically changes a state of at least one of the one or more selectable elements within the care team directory on each mobile device, the state of the at least one of the one or more selectable elements indicating availability of the associated care member of the patient care team, for each patient clinical task, based on the resolved proximity of each mobile device associated with each care member.
  • the backend processor is configured to dynamically route communication links between care members and content links between care members based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to dynamically route asynchronous secure messaging based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to dynamically route notifications and alerts associated with a patient clinical process based on the resolved proximity of each mobile device associated with each care member of a patient clinical team.
  • notification and alerts are dynamically escalated by the backend processor based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to filter access to at least one patient information associated with the patient clinical process based on the resolved proximity of each mobile device associated with each care member of the patient clinical team .
  • the backend processor is configured to filter access to at least one clinical information associated with the patient clinical process based on the resolved proximity of each mobile device associated with each care member of the patient clinical team .
  • the backend processor is configured to filter access to at least one laboratory information associated with the patient care process based on the resolved proximity of each mobile device associated with each care member of the patient clinical team .
  • the backend processor is further configured to generate a patient care process- specific patient care team directory based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • a system for controlling a patient clinical process in a healthcare facility having a system backend having a backend processor configured to define a patient clinical team associated with a patient clinical process comprising of a series of patient clinical tasks effected within the healthcare facility, each patient clinical task having an associated patient clinical task location within the healthcare facility, the backend processor further configured to generate a care team directory for each patient clinical task, the care team directory comprising one or more selectable elements associated with one or more care members of the patient care team, a group of mobile devices communicably connected via a network to the system backend and configured to present the one or more selectable elements associated with the care team directory for each patient clinical task, each mobile device being associated with and configured for use by the one or more care members of the patient clinical team, and a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different patient clinical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity
  • LE low energy
  • the backend processor is further configured to dynamically update and enhance the care team directory by dynamically changing a state of at least one of the one or more selectable elements within the care team directory, the state of the at least one of the one or more selectable elements reflecting the availability of each care member, of the patient care team for each patient clinical task, based on the resolved proximity of each mobile device associated with each care member.
  • the backend processor is configured to dynamically route communication links between care members and content links between care members based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to dynamically route asynchronous secure messaging based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to dynamically route notifications and alerts associated with a patient clinical process based on the resolved proximity of each mobile device associated with each care member of a patient clinical team.
  • notification and alerts are dynamically escalated by the backend processor based on the resolved proximity of each mobile device associated with each care member of the patient clinical team.
  • the backend processor is configured to filter access to at least one clinical information associated with the patient clinical process based on the resolved proximity of each mobile device associated with each care member of the patient clinical team .
  • a system for controlling clinical processes having a system backend having a backend processor configured to manage a clinical process that comprises a series of clinical tasks for care of a common patient, each clinical tasks having an associated location and at least one of associated location is different than another associated location of a different one of the clinical tasks, each of the different clinical tasks in the series corresponding to different selectable elements within a clinical process directory so that each selectable element represents a different clinical task and its location, a group of mobile devices communicably connected via a network to the system backend, each of the mobile devices having a different predetermined characteristic related to effecting at least one of the clinical tasks and altering a state of the corresponding selectable element within the clinical process directory, and a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one location and signal the device proximity to the
  • LE low energy
  • the backend processor is configured to register the device proximity and initiate a predetermined action associated with the state of the corresponding selectable element within the clinical process directory based on the resolved device proximity .
  • each of the mobile devices is configured to receive communications from the backend related to the clinical process.
  • the predetermined action is registering the real time proximity of the mobile device relative to the location associated with the clinical task and the corresponding selectable element within the clinical process directory.
  • the predetermined action is selecting between sending and not sending a communication to the mobile device based on resolving the mobile device real time proximity at the location associated with the clinical task and the corresponding selectable element within the clinical process directory
  • the communication is an alarm generating signal, or a signal turning off an alarm on the mobile device .
  • the predetermined action is escalating an alarm to another of the mobile devices based on the real time proximity of the mobile device and the other mobile device.
  • the beacon array is a Bluetooth ® low energy (BLE) beacon array.
  • the backend processor is configured to manage the clinical process by changing a state of the selectable element within the clinical process directory based on the resolved device proximity .
  • map defines both track and real time proximity of each of mobile device with respect to the corresponding selectable element within the clinical process directory.
  • each mobile device has a device processor resident therein configured to resolve the proximity of the device, from the beacon array, and initiate a predetermined action based on the proximity.
  • LE low energy
  • the processor of the at least one mobile device is configured to resolve, from the beacon array, the mobile device's proximity to a predetermined one of the different locations.
  • the processor is further configured to disable the built in function or the functionality related to effecting at least one of the clinical tasks of the clinical process, and disable the ability of the at least one mobile device to alter the state of the corresponding selectable elements within the clinical process directory, based on the mobile device's proximity to the predetermined location.
  • a sixteenth aspect of the disclosed embodiment system for maintaining system readiness having a system backend, a low energy beacon array having at least one beacon configured to transmit a beacon signal, a group of mobile devices, each communicably connected via a network to the system backend with a communications transceiver and each mobile device further configured to receive the beacon signal and resolve a proximity relative to a predetermined location.
  • Each of the mobile devices further having a sleep mode and an awake mode, where the mobile device's communications transceiver is deactivated in the sleep mode and the mobile device's communication transceiver is activated in the awake mode and the mobile device is further configured to enter the sleep mode from the awake mode in a sleep mode predetermined period of time.
  • the mobile device is configured to receive the beacon signal and, in response to the received beacon signal and based on the resolved proximity relative to a predetermined location, the mobile device is further configured to maintain activation of the awake mode.
  • a seventeenth aspect of the disclosed embodiment system for tracking physical assets within an enclosed facility having a system backend comprising a backend processor configured to track a physical asset location of at least one physical asset within the enclosed facility, a group of mobile devices communicably connected via a network to the system backend, a low energy (LE) beacon array arranged in a predetermined relationship with and differentiating between different physical locations within the enclosed facility, and communicably connected to each of the mobile devices that is configured to resolve its mobile device proximity to the physical locations within the enclosed facility, from the beacon array, the at least one physical asset having a low energy (LE) beacon and detectable by each of the mobile devices, where the low energy (LE) beacon associated with each of the at least one physical asset being distinct from a different low energy (LE) beacon of another of the at least one physical asset.
  • the backend processor is configured to identify the at least one physical asset and dynamically determine its physical asset location based on the resolved mobile device proximity of the at least one mobile device.
  • a third aspect of the disclosed embodiment for a system for controlling process pathways having a network, a system backend communicably connected with the network, the backend having a processor configured to manage a physical process that comprises a series of physical tasks, each with an associated physical location and at least one of which is different than another physical location of a different one of the physical tasks, and to manage an associated process pathway embodying the physical process, each of the different physical tasks in the series corresponding to different points along the pathway so that each point represents a different physical task and its location, a group of mobile devices communicably connected to the system backend, each of the mobile devices having a different predetermined characteristic related to effecting at least one of the physical tasks and altering a state of the corresponding pathway point, a BLE beacon array arranged in a predetermined relationship with and differentiating between different physical task locations, and communicably connected to each of the mobile devices that is configured to resolve its proximity, from the beacon array, relative to the at least one physical task location and signal the device proximity to the backend

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Biomedical Technology (AREA)
  • Theoretical Computer Science (AREA)
  • Public Health (AREA)
  • Primary Health Care (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Epidemiology (AREA)
  • Computer Security & Cryptography (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

La présente invention concerne un système présentant un système principal possédant un processeur principal configuré de manière à définir une équipe clinique de patients associée à un processus clinique de patients se composant d'une série de tâches cliniques de patients effectuées à l'intérieur de l'installation de soins de santé. Chaque tâche clinique de patients est dotée d'un emplacement associé de tâche clinique de patients à l'intérieur de l'installation de soins de santé. Un groupe de dispositifs mobiles est connecté en communication au système principal par l'intermédiaire d'un réseau. Chaque dispositif mobile est associé à au moins un membre de personnel soignant de l'équipe clinique de patients, et est configuré pour être utilisé par ledit ou lesdits éléments. Un réseau de balises à faible énergie (LE) est disposé selon une relation prédéterminée avec différents emplacements de tâches cliniques de patients en les différenciant, et est relié en communication à chaque dispositif mobile configuré pour déterminer sa proximité, à partir du réseau de balises, par rapport audit au moins un emplacement de tâches cliniques de patients.
EP15769644.4A 2014-03-28 2015-03-30 Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique Ceased EP3123438A4 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22187295.5A EP4141883A1 (fr) 2014-03-28 2015-03-30 Système de contrôles dynamiques de processus de soin des patients et de suivi dynamique d'actifs sensibles à la localisation

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201461971887P 2014-03-28 2014-03-28
US201462031089P 2014-07-30 2014-07-30
US201462032172P 2014-08-01 2014-08-01
PCT/US2015/023389 WO2015149073A1 (fr) 2014-03-28 2015-03-30 Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique

Related Child Applications (1)

Application Number Title Priority Date Filing Date
EP22187295.5A Division EP4141883A1 (fr) 2014-03-28 2015-03-30 Système de contrôles dynamiques de processus de soin des patients et de suivi dynamique d'actifs sensibles à la localisation

Publications (2)

Publication Number Publication Date
EP3123438A1 true EP3123438A1 (fr) 2017-02-01
EP3123438A4 EP3123438A4 (fr) 2017-09-20

Family

ID=57589821

Family Applications (2)

Application Number Title Priority Date Filing Date
EP15769644.4A Ceased EP3123438A4 (fr) 2014-03-28 2015-03-30 Système destiné à des contrôles de processus de soins d'un patient sensible à un emplacement dynamique et suivi d'actif sensible à un emplacement dynamique
EP22187295.5A Pending EP4141883A1 (fr) 2014-03-28 2015-03-30 Système de contrôles dynamiques de processus de soin des patients et de suivi dynamique d'actifs sensibles à la localisation

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP22187295.5A Pending EP4141883A1 (fr) 2014-03-28 2015-03-30 Système de contrôles dynamiques de processus de soin des patients et de suivi dynamique d'actifs sensibles à la localisation

Country Status (1)

Country Link
EP (2) EP3123438A4 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11328227B2 (en) 2014-03-28 2022-05-10 Mobile Heartbeat, Llc System for dynamic location-aware patient care process controls and dynamic location-aware tracking

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6608592B2 (en) * 2002-01-18 2003-08-19 Hewlett-Packard Development Company, Lp. Location system using beacon transmitters
US7751829B2 (en) * 2003-09-22 2010-07-06 Fujitsu Limited Method and apparatus for location determination using mini-beacons
CA2550812A1 (fr) * 2005-06-22 2006-12-22 Axigon Healthcare Technologies Incorporated Systeme et methode de surveillance bidirectionnelle sans fil
US20070184852A1 (en) * 2006-01-17 2007-08-09 Johnson David W Method and system for location of objects within a specified geographic area
US20110106565A1 (en) * 2009-11-04 2011-05-05 Cerner Innovation, Inc. Proximity-Based Task Lists
EP2534619A4 (fr) * 2010-02-12 2015-10-21 Service Heartbeat Llc Système de gestion des ressources et du flux de travail avec communications bidirectionnelles intégrées
US20140074667A1 (en) * 2012-09-11 2014-03-13 Michael D. Smith System and Method for Inventory Control of Mobile Assets

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11328227B2 (en) 2014-03-28 2022-05-10 Mobile Heartbeat, Llc System for dynamic location-aware patient care process controls and dynamic location-aware tracking

Also Published As

Publication number Publication date
EP4141883A1 (fr) 2023-03-01
EP3123438A4 (fr) 2017-09-20

Similar Documents

Publication Publication Date Title
US11328227B2 (en) System for dynamic location-aware patient care process controls and dynamic location-aware tracking
CN110140364B (zh) 实时定位平台信标协议系统和方法
US11363424B2 (en) Location-based resource management
US20160180045A1 (en) Wireless beacon devices used to track medical information at a hospital
US10171935B1 (en) Healthcare proximity services
US11706304B1 (en) System for setting and controlling functionalities of mobile devices
US11356848B2 (en) Inference-based detection of proximity changes
US20150379441A1 (en) Shared asset management system
US11404169B2 (en) Collaboration tool for healthcare providers
US10505910B2 (en) Patient monitor and method for monitoring a patient
US11817208B2 (en) Method and system to facilitate patient care
KR101894188B1 (ko) 병원정보 시스템 기반 임상시험 이상반응 알림 및 보고 시스템
JP6453024B2 (ja) 備品管理装置、及び備品情報提供方法
US20150379217A1 (en) Medical information display system, server, and portable terminal
EP4141883A1 (fr) Système de contrôles dynamiques de processus de soin des patients et de suivi dynamique d'actifs sensibles à la localisation
US11056231B2 (en) Utilizing IOT devices for detecting an emergency and locating a convenient parking space
KR102194992B1 (ko) 의료기관내 회진 알람 서비스 제공 방법
CN108431878A (zh) 方便经由本地无线网络传输邻近健康警报的方法和装置
US20150347692A1 (en) Method and apparatus for providing mobile apps for a healthcare facility
JP6682085B2 (ja) 患者識別端末、患者識別方法、および患者識別プログラム
EP3105735A1 (fr) Système de réglage et de commande de fonctionnalités de dispositifs mobiles
Innovations Healthcare Alarm Safety—What We Can Learn from Military Alarm Management Strategies
Rezaee Patient-Device Association and Disassociation with a Real-Time Location System
JP2015184863A (ja) メッセージ送信プログラム、メッセージ送信方法およびメッセージ送信装置

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20161020

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20170821

RIC1 Information provided on ipc code assigned before grant

Ipc: G06Q 50/00 20120101ALN20170814BHEP

Ipc: G06F 21/00 20130101ALN20170814BHEP

Ipc: G06F 19/00 20110101AFI20170814BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190228

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: MOBILE HEARTBEAT LLC

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20220512