Back to results
US 2022/0066838 A1Published application
Multi-tenant nurse call system with shared workflows
AssigneeTigerConnect, Inc.
InventorSTEPHEN GILES
Life of this patent
Estimating the term…
Abstract
A multi-tenant nurse call system (MTNCS) has functionality that operates to receive event messages having information corresponding to an event type and device identity that it uses to select a workflow comprised of a set of ordered business rules that when run is designed to respond to the event. The MTNCS can be configured so that different workflows can be triggered by the same type of event message depending upon the identity of the tenant that generated the event message, and it can be configured so that a workflow can be paused or terminated during a period of time during which the MTNCS waits to receive subsequent similar events as the one that triggered the workflow.
Claims20
A method of processing an event message by a multi-tenant nurse call system, comprising:
- configuring the multi-tenant nurse call system to select and process a workflow based upon a type of event message received and based upon an identity of a tenant that generated the event message by:
- assigning, by an individual, a unique identity to each one of a plurality of tenants, wherein each one of the plurality of the tenants is comprised of one or more hospital specialty units;
- assigning an identity to each one of a plurality of medical devices and associating each of the medical devices with different ones of the plurality of tenants;
- and
- assigning a unique identity to each one of a plurality of workflows, wherein each instance of the plurality of the workflows is comprised of one or more ordered steps stored in a database system associated with the multi-tenant nurse call system, and each one of the plurality of the workflows is selected for processing by the multi-tenant nurse call system based upon an event message type generated by any one of the medical devices assigned to one of the plurality of tenants, and based upon an identify of the tenant to which the medical device is assigned;
- receiving at the nurse call system a first event message, the multi-tenant nurse call system parsing the first event message for an event message type and medical device identity information, and determining that the first event message is of a first type and was generated by a first one of the plurality of the tenants, and receiving at the multi-tenant nurse call system a second event message, the multi-tenant nurse call system parsing the second event message for an event message type and medical device identity information, and determining that the second event message is of the first type and was generated by a second one of the plurality of the tenants;
- selecting a first workflow to be processed for the first tenant, and selecting a second workflow that is different than the first workflow to be processed for the second tenant, each workflow being selected based upon both the event message type and an identity of the tenant that generated the event message, and at least one of the selected workflows having a suspend-step;
- and
- starting and running, by the multi-tenant nurse call system, the first and the second workflows until it determines that a next step to be processed in the at least one of the workflows is a suspend step, immediately pausing the processing of the at least one workflow at the suspend step until at least one additional instance of the first type of event message is received, and immediately continuing to process the at least one of the workflows having the suspend step subsequent to receiving the at least one additional event message of the first type.
6 more elements
A method of processing an event message by a multi-tenant nurse call system, comprising:
- configuring the multi-tenant nurse call system to select and process a workflow based upon a type of event message received and based upon an identity of a tenant that generated the event message by:
- assigning, by an individual, a unique identity to each one of a plurality of tenants, wherein each one of the plurality of the tenants is comprised of one or more hospital specialty units;
- assigning an identity to each one of a plurality of medical devices and associating each of the medical devices with different ones of the plurality of tenants;
- and
- assigning a unique identity to each one of a plurality of workflows, wherein each instance of the plurality of the workflows is comprised of one or more ordered steps stored in a database system associated with the multi-tenant nurse call system, and each one of the plurality of the workflows is selected for processing by the multi-tenant nurse call system based upon an event message type, generated by any one of the medical devices assigned to one of the plurality of tenants, and based upon an identity of the tenant to which the medical device is assigned;
- receiving at the multi-tenant nurse call system a first event message, parsing the first event message for an event message type and medical device identity information, and determining that the first event message is of a first type and was generated by a first one of the plurality of the tenants, and receiving at the multi-tenant nurse call system a second event message, parsing the second event message for an event message type and medical device identity information, and determining that the second event message is of the first type and was generated by a second one of the plurality of the tenants;
- selecting a first workflow to be processed for the first tenant and selecting a second workflow, that is different from the first workflow, to be processed for the second tenant, each workflow being selected based upon both the event message type and an identity of the tenant that generated the event message;
- and
- starting and running, by the multi-tenant nurse call system, the first and the second workflows until it determines that a selected number of subsequent event messages of the same type as the first and second event messages are not received from one or the other of the first or second tenants, and immediately terminating the workflow being processed for the tenant from which subsequent event messages of the first type are not received.
6 more elements
A system for processing machine readable event messages, comprising:
- a plurality of uniquely identified tenants in communication with a network, wherein each one of the plurality of the tenants is comprised of one or more hospital specialty units;
- and
- a multi-tenant nurse call system connected to the network comprising:
- a computational device;
- a display device;
- and
- a store of tenant related information maintained in a database system associated with and accessible by the multi-tenant nurse call system;
- and
- the multi-tenant nurse call system receiving a first event message, parsing the first event message for an event message type, and determining that the first event message is of a first type and was generated by a first one of the plurality of the tenants, and receiving at the multi-tenant nurse call system a second event message, parsing the second event message for an event message type, and determining that the second event message is of the first type and was generated by a second one of the plurality of the tenants;
- and
- the multi-tenant nurse call system selecting a first workflow to be processed for the first tenant, and selecting a second workflow, that is different than the first workflow, to be processed for the second tenant, each workflow being selected based upon both the event message type and an identity of the tenant that generated the event message, and at least one of the selected workflows having a suspend-step;
- and
- the multi-tenant nurse call system starting and running the first and the second workflows until it determines that a next step to be processed in the at least one of the workflows is a suspend step, immediately pausing the processing of the at least one workflow at the suspend step until at least one additional instance of the first type of event message is received, and immediately continuing to process the at least one of the workflows having the suspend step subsequent to receiving the at least one additional event message of the first type.
10 more elements
The method of claim17, further comprising the at least one of the workflows has two or more suspend steps, and the selected number of subsequent events of the first type can be the same for each suspend step, or can be different for some or all of the suspend steps.
Dependencies are inferred from the claim text.