| CPC G06F 9/5088 (2013.01) [G06F 9/5038 (2013.01); G06Q 10/06311 (2013.01); G16H 40/60 (2018.01); G16H 80/00 (2018.01)] | 17 Claims |
|
1. A method of processing an event message by a multi-clinical entity group nurse call system, comprising:
a) configuring, via an event processor, the multi-clinical entity group nurse call system to select and process a workflow based upon a type of event message received and based upon an identity of a clinical entity group that generated the event message by:
i) assigning, by an individual, a unique identity to each one of a plurality of clinical entity groups, wherein each one of the plurality of the clinical entity groups consists of one or more hospital specialty units, signaling devices, and messaging devices;
ii) assigning a physical location to one or more of the plurality of clinical entity groups;
iii) assigning an identity to each one of a plurality of medical devices comprising patient monitoring devices and associating each of the medical devices with different ones of the plurality of clinical entity groups; and
iv) 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-clinical entity group nurse call system, and each one of the plurality of the workflows is selected for processing by the multi-clinical entity group nurse call system based upon an event message type generated by any one of the medical devices assigned to one of the plurality of clinical entity groups, and based upon an identity of the clinical entity group to which the medical device is assigned;
b) receiving at the multi-clinical entity group nurse call system, via a communication network, a first event message from one of the medical devices;
c) parsing, via the event processor, the first event message for an event message type and medical device identity information, and determining, via a logic, that the first event message is of a first type and was generated by a medical device associated with a first one of the plurality of the clinical entity groups;
d) receiving at the multi-clinical entity group nurse call system a second event message;
e) parsing, via the event processor, the second event message for an event message type and medical device identity information, and automatically determining, via the logic, that the second event message is of the first type and was generated by a medical device associated with a second one of the plurality of the clinical entity groups;
f) selecting a first workflow to be processed for the first clinical entity group, and selecting a second workflow that is different than the first workflow to be processed for the second clinical entity group, each workflow being selected based upon both the event message type and an identity of the clinical entity group that generated the event message, and at least one of the selected workflows having a suspend step, wherein one or more of the first workflow and second workflow result in one or more of activating a visual or audio alert at a console and transmitting a message to the one or more messaging devices associated with a staff member associated with one or more of the workflow's clinical entity groups;
g) starting and running, by the multi-clinical entity group nurse call system, the first and the second workflows until the system 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, then 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;
h) assigning the first workflow for the first clinical entity group to a first staff member tracked by a first wireless location tracking device when the first staff member is within a predetermined proximity to the physical location of a bed associated with the medical device that generated the first event message, where the bed and the medical device are each members of the first clinical entity group; and
i) terminating at least one of the workflows during the suspend step if another one or more instances of the event message of the first type are not received prior to a selected, maximum period of time elapsing.
|