Data services modeling and manager for transformation and contextualization of data in automated performance of workflows
A data services modeling framework provides for event contextualization from state changes in events within laboratory workflows, and for orchestrating activities in workflow cycles. The data services modeling framework forms a part of data services within an orchestrator software package that provides a set of dynamic processes within laboratory workflows, for improving and enhancing workflow performance. The data services modeling framework includes a data services model configured to analyze state changes in event data, by applying algorithms for isolating the activities producing state changes, re-creating an event state, analyzing data points defining state changes to explain the event state at relevant time periods in the workflow cycle. The data services modeling framework also enables publication of messages representing contextualized event data for subscription with the orchestrator environment.
1 . A method of contextualizing an event state in a performance of laboratory workflows, comprising:
ingesting, within an orchestrator environment for managing a plurality of laboratory workflows, event data that includes one or more of sample data, workcell and instrument data, assay requirements data, and consumables and labware data;
modeling one or more state changes in the event data, by
identifying at least one event within a workflow cycle,
recursively querying at least one node within a data structure representing the workflow cycle by searching temporal slices relative to the at least one node by activities associated with a state of the at least one event, extracting data points describing the state of the at least one event at the temporal slices, and contrasting the data points to define one or more state changes in the at least one event at each node, and
explaining the one or more state changes in the at least one event, by isolating the activities producing the one or more state changes to re-create the state of the at least one event, and adding the data points defining the one or more state changes to contextualize the state of the at least one event at one or more time periods in the workflow cycle;
publishing one or more messages having a payload representing contextualized event data for subscription to the orchestrator environment; and
automatically executing one or more laboratory activities relative to the workflow in response to the one or more messages,
wherein the one or more laboratory activities involve one or both of laboratory samples or labware and are executed in response to the one or more messages to perform at least a part of a laboratory workflow, and include actuating a robotic instrument to perform a particular physical function on materials that either handles or transfers the one or both of laboratory samples or labware in at least one workcell.
2 . The method of claim 1 , wherein the one or more messages include instructions for the automatically executing the one or more laboratory activities.
3 . The method of claim 1 , further comprising generating a schedule of additional laboratory activities in the workflow cycle, in response to the one or more messages, and automatically executing the additional laboratory activities according to the schedule.
4 . The method of claim 1 , wherein the orchestrator environment is a data management platform for integrating a performance of the plurality of laboratory workflows, the orchestrator environment including one or more of an order manager, a transportation manager, a data services manager, a scheduler, an IoT agent, and a workflow manager.
5 . The method of claim 4 , wherein the one or more messages are published within an application programming interface environment that integrates the subscription to the one or more messages and responses to the one or more messages, by processing messages published back from the orchestrator environment.
6 . The method of claim 5 , wherein the application programming interface environment includes one or more of an accessioning service API configured to provide an interface for registering events, and for creating and associating event identifiers and event types with registered events during performance of the one or more workflows, an inventory API configured to manage inventory manage inventory activities that include one or more of ordering, storage, and scheduling, a query service API configured to provide an interface for both internal systems and external systems to query event data during performance of the one or more workflows, and at least one transportation API configured to provide an interface for fulfillment of transportation requests during performance of the one or more workflows.
7 . The method of claim 1 , further comprising predicting one or more actions in additional workflow cycles based on the one or more state changes, and publishing one or more additional messages to execute the one or more actions in the additional workflow cycles.
8 . A method of contextualizing an event state in a performance of laboratory workflows, comprising:
initiating a data services model configured to analyze one or more state changes in a workflow cycle, by defining at least one event within the workflow cycle from event data received within an orchestrator environment for managing a plurality of laboratory workflows that includes one or more of sample data, workcell and instrument data, assay requirements data, and consumables and labware data;
executing the data services model by
applying a recursive algorithm to query at least one node within a data structure representing the workflow cycle by searching temporal slices relative to the at least one node by activities associated with a state of the at least one event, extracting data points describing the state of the at least one event at the temporal slices, and contrasting the data points to define the one or more state changes in the at least one event at each node, and
isolating the activities producing the one or more state changes to re-create the state of the at least one event, and adding the data points defining the one or more state changes to contextualize the state of the at least one event at one or more time periods in the workflow cycle to explain the one or more state changes in the at least one event;
wherein an event message broker publishes one or more messages having a payload representing contextualized event data for subscription to the orchestrator environment, and wherein one or more activities relative to the workflow cycle are automatically executed in response to the one or more messages, and
wherein the one or more laboratory activities involve one or both of laboratory samples or labware and are executed in response to the one or more messages to perform at least a part of a laboratory workflow, and include actuating a robotic instrument to perform a particular physical function on materials that either handles or transfers the one or both of laboratory samples or labware in at least one workcell.
9 . The method of claim 8 , wherein a schedule of one or more additional laboratory activities is generated in response to the one or more messages, and the one or more additional laboratory are automatically executed according to the schedule.
10 . The method of claim 8 , wherein the orchestrator environment is a data management platform for integrating a performance of the plurality of laboratory workflows, the orchestrator environment including one or more of an order manager, a transportation manager, a data services manager, a scheduler, an IoT agent, and a workflow manager.
11 . The method of claim 10 , wherein the one or more messages are published within an application programming interface environment that integrates the subscription to the one or more messages and responses to the one or more messages, by processing messages published back from the orchestrator environment.
12 . The method of claim 11 , wherein the application programming interface environment includes one or more of an accessioning service API configured to provide an interface for registering events, and for creating and associating event identifiers and event types with registered events during performance of the one or more workflows, an inventory API configured to manage inventory manage inventory activities that include one or more of ordering, storage, and scheduling, a query service API configured to provide an interface for both internal systems and external systems to query event data during performance of the one or more workflows, and at least one transportation API configured to provide an interface for fulfillment of transportation requests during performance of the one or more workflows.
13 . The method of claim 8 , further comprising predicting one or more actions in additional workflow cycles based on the one or more state changes, and publishing one or more additional messages to execute the one or more actions in the additional workflow cycles.
14 . A system for contextualizing an event state in a performance of laboratory workflows, comprising:
a data collection and initialization element, configured to define at least one event within a workflow cycle from event data received within an orchestrator environment for managing a plurality of laboratory workflows that includes one or more of sample data, workcell and instrument data, assay requirements data, and consumables and labware data;
a data services model configured to analyze one or more state changes in the event data, the data services model comprised of
a recursive algorithm configured to query at least one node within a data structure representing the workflow cycle by searching temporal slices relative to the at least one node by activities associated with a state of the at least one event, extracting data points describing the state of the at least one event at the temporal slices, and contrasting the data points to define the one or more state changes in the at least one event at each node, and
one or more real-time data analytics and transform elements configured to explain the one or more state changes in the at least one event, by isolating the activities producing the one or more state changes to re-create the state of the at least one event, and adding the data points defining the one or more state changes to contextualize the state of the at least one event at one or more time periods in the workflow cycle; and
an event message broker, configured at least to publish one or more messages having a payload representing contextualized event data for subscription to the orchestrator environment, wherein one or more activities in the workflow cycle are automatically executed in response to the one or more messages, and
wherein the one or more laboratory activities involve one or both of laboratory samples or labware and are executed in response to the one or more messages to perform at least a part of a laboratory workflow, and include actuating a robotic instrument to perform a particular physical function on materials that either handles or transfers the one or both of laboratory samples or labware in at least one workcell.
15 . The system of claim 14 , wherein a schedule of additional laboratory activities in the workflow cycle is generated in response to the one or more messages, and wherein the additional laboratory activities are automatically executed according to the schedule.
16 . The system of claim 14 , wherein the orchestrator environment is a data management platform for integrating a performance of the plurality of laboratory workflows, the orchestrator environment including one or more of an order manager, a transportation manager, a data services manager, a scheduler, an IoT agent, and a workflow manager.
17 . The system of claim 16 , wherein the one or more messages are published within an application programming interface environment that integrates the subscription to the one or more messages and responses to the one or more messages, by processing messages published back from the orchestrator environment.
18 . The system of claim 17 , wherein the application programming interface environment includes one or more of an accessioning service API configured to provide an interface for registering events, and for creating and associating event identifiers and event types with registered events during performance of the one or more workflows, an inventory API configured to manage inventory manage inventory activities that include one or more of ordering, storage, and scheduling, a query service API configured to provide an interface for both internal systems and external systems to query event data during performance of the one or more workflows, and at least one transportation API configured to provide an interface for fulfillment of transportation requests during performance of the one or more workflows.
19 . The system of claim 14 , wherein the data services model is further configured to predict one or more actions in additional workflow cycles based on the one or more state changes, and publishing one or more additional messages to execute the one or more actions in the additional workflow cycles.