Method, medium and system for providing notification architecture

By introducing event bridges and notification services in the analytical chemical system, the problem of insufficient communication between different applications is solved, and timely delivery of notifications in the analytical chemical system is realized, ensuring that users can receive important event notifications in a timely manner, and improving the system's Reliability and scalability.

CN118922846APending Publication Date: 2024-11-08WATERS TECH IRELAND LIMITED IE
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028192.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-01-18
Filing Date
2023-01-18
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In an analytical chemistry environment, the inability to communicate effectively between different applications, resulting in the user being able to ignore important notifications when moving between different applications, and failure of asynchronous operations or other events fail to notify the user in time.

Method used

By introducing event bridges and notification services in the analytical chemical system, notification tunnels and pipelines between different applications and devices are implemented, allowing timely and consistent delivery of notifications on multiple delivery channels, including audit logs, asynchronous operation completion, acquisition Events, etc.

Benefits of technology

Ensure that users can receive notifications in a timely manner even when switching between different tasks, improve the system's processing efficiency and reliability, reduce the risk of errors, and support system expansion and upgrade.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922846A_ABST
    Figure CN118922846A_ABST
Patent Text Reader

Abstract

Exemplary embodiments provide computer-implemented methods, media, and devices that provide an architecture for supporting event notifications in an analytical chemistry system. The notification architecture allows notifications to be sent within and outside the analytical chemistry system. It supports notifications provided by different devices and applications of the analytical chemistry system and allows the notifications to be sent over a variety of different delivery channels in a unified and consistent manner. The architecture can be readily expanded to support new types of notifications and new delivery channels. The architecture supports stateful notifications, allowing the read / unread status of the notifications to be displayed. Furthermore, the architecture may utilize existing events to generate notifications, which allows events to be used for various purposes in the analytical chemistry system, and thus reduce the amount of messages and processing that needs to be performed in the system.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 300,403, filed on January 18, 2022. The entire disclosure of that application is hereby incorporated by reference herein. Background Art

[0003] Laboratory analytical instruments are devices used to qualitatively and / or quantitatively analyze samples. They are often used in a laboratory setting for scientific research or testing. Such devices can measure the chemical composition of a sample, the amount of components in a sample, and perform similar analyses. Examples include mass spectrometers, chromatographs, titrators, spectrometers, elemental analyzers, particle size analyzers, rheometers, thermal analyzers, etc.

[0004] Laboratory analytical instruments may be used in analytical chemistry systems, which may include one or more laboratory analytical instruments and / or other types of devices. The data generated on these devices may be analyzed by analytical devices and / or software, which may be operated locally or in the cloud. Data analysis in an analytical chemistry environment can be quite complex and time-consuming. Some users may want to switch back and forth between different analytical applications to perform certain tasks while other users are working on them. In addition, some tasks may take a long time to complete, during which time the analyst may be away from the workstation.

[0005] The problem is that as a user moves between different applications or moves away from a workstation, events may occur that require the user's immediate attention. For example, an application may perform changes in backend data, and the user should be aware of that. Similarly, if an asynchronous operation is performed in an application (which includes many cloud-based operations) and that operation fails, the user may want to be notified (even if the user has moved to a different application in the meantime). In addition, certain audit entries may appear in the system from time to time, and the user may want to be aware of those entries.

[0006] Unfortunately, many different applications and analytical devices are used in analytical chemistry environments. Different applications may not be able to communicate with each other and therefore may not have the ability to send notifications between them. Even if one application is able to send notifications to another application, there is usually no consistent way to display these notifications across analytical chemistry environments. Therefore, users may ignore notifications displayed in one application because these notifications do not appear in a format that the user recognizes. Summary of the invention

[0007] The exemplary embodiments provide tunnels and pipelines between different applications and devices in an analytical chemistry system, allowing notifications to be delivered in a timely and consistent manner over many different delivery channels.

[0008] Example embodiments may include a computer-implemented method, as well as a non-transitory computer-readable medium storing instructions for performing the method, a device configured to perform the method, and the like.

[0009] According to a first embodiment, a data ecosystem of an analytical chemistry system may be accessed. An event bridge in the data ecosystem may receive events from applications connected to the data ecosystem. A notification of the event may be generated and sent across multiple different delivery channels to users who have subscribed to receive notifications of the event.

[0010] The event bridge may be responsible for receiving notification events from the device autonomous service. Notification events may be added to a cloud-based user notification queue service. The notification autonomous service may retrieve notification events and send them to subscribing applications within the analytical chemistry system and / or outbound services (e.g., SMS, email, etc.) outside the analytical chemistry system. Different delivery channels may subscribe to the notification service to receive notification events from the notification autonomous service.

[0011] Notifications may include any information that a device or application is configured to draw the user's attention to. Such information may come from, for example: interesting entries in audit logs (such as notification of a failed login attempt to an administrator); completion of a long-running asynchronous operation by an application; application errors or warnings associated with an asynchronous operation; acquisition events from laboratory analytical instruments (e.g., injection / batch completion); file uploads and automated conversion of extract, transform, load (ETL) states; and operations related to analytical chemistry workflows (e.g., acquisition of a signature to move a workflow from one stage to another).

[0012] Using this architecture, notifications can be generated by devices in analytical chemistry systems and / or applications in the data ecosystem and disseminated to a variety of delivery channels. Notifications can be delivered and displayed in a consistent manner across delivery channels. Certain architectural features contribute to these and other advantages:

[0013] Multiple different channels can deliver notifications to subscribed users. This increases the chance that the user will receive the notification and be able to act on it in a timely manner.

[0014] Because the notification service is event-driven, different aspects of its operation can be separated and run as different services / data structures. This makes the process more efficient and reduces the risk of errors. In addition, different components can be upgraded or replaced individually without requiring significant downtime of the entire system.

[0015] Any event generated by the platform or application can be used as a notification. In addition, any event can have multiple uses, which increases system efficiency and reduces the number of messages that need to be exchanged.

[0016] The architecture is easily extensible. New users or applications can register to receive notifications, and new devices and applications can register to send notifications without rebuilding the architecture.

[0017] Notifications can be stateful. For some channels, the system can track whether a notification has been read based on its delivery status in a queue and / or whether the user has interacted with a particular application's UI or UI element.

[0018] According to a second embodiment, the event may be one or more of: a new audit log entry, completion of an asynchronous operation, an error or warning associated with an asynchronous operation, a collection event, a file upload, a file conversion, or a workflow related operation.

[0019] In the context of analytical chemistry systems, these types of events are particularly important to flag to the user in a timely manner, and the described architecture is well suited for delivering them.

[0020] According to a third embodiment, the plurality of different channels may include at least two of the following: a simple messaging service channel, an email channel, a web browser channel, and an application programming interface (API) channel.

[0021] The API channel can be used to send notifications to applications in the data ecosystem of the analytical chemistry system, and the web browser channel can be used to display notifications on the system dashboard. Therefore, if a user moves from one application to another in the system, the user can still know the notification through the interface of the new application (via the API channel) or through the dashboard (via the web browser channel). Even if the user is not currently paying attention to the application or dashboard of the system, the remaining channels can be used to notify the user, such as when the user walks away during a long data processing session (or the user is an administrator and needs to be notified of events even if he is not on duty).

[0022] According to a fourth embodiment, the application may be a first application and the event may be received when a second application different from the first application is active.

[0023] Thus, users can be notified of events occurring in any of a number of different data processing paradigms through a single unified interface. This allows users to move on to new tasks while still being confident that they will be notified of important data events occurring in applications they are not currently focusing on.

[0024] According to a fifth embodiment, a notification service may retrieve a copy of an event from a notification queue in communication with an event bridge, convert the event into a notification, and send the notification on multiple channels.

[0025] Using a notification service helps with extensibility (since new notification types or subscriptions can be easily added through a single service) and provides a central point of contact for notifications (which allows notifications to be handled in a unified manner). In addition, the notification service can be configured to transform events into the appropriate notification format based on the destinations registered with the notification service. For example, the notification service can store multiple templates to help it generate notifications. When the notification is delivered as (for example) an email, the notification service can retrieve the appropriate email template and transform the content of the notification based on the template, sending the resulting email to any email subscribers.

[0026] Furthermore, not every event generated in the system needs to be sent as a notification on every possible delivery channel. Each event may include source information and type information. The notification service may be configured to receive an event, examine its source and type, and query a list of subscribers to determine which subscribers are interested in receiving notifications related to the source and type of the received event. Only the channels associated with those subscriptions need to be used to send the notification.

[0027] According to a sixth embodiment, an entry corresponding to the event may be added to an audit log maintained by the data ecosystem.

[0028] According to this embodiment, even after the event is confirmed and / or deleted by the user, the event can be reviewed. This allows the user or administrator to check previous events after a problem occurs to determine which events triggered the notification and which events were handled in a timely manner.

[0029] According to a seventh embodiment, the event bridge may communicate with one or more of: a device service configured to generate events describing the state of a laboratory analytical instrument in an analytical chemistry system, a laboratory monitoring service configured to generate events in response to the creation, editing, or removal of a subscription in the data ecosystem, or a compliance service configured to generate events in response to the assignment of a team or a change in the assignment of one or more permissions to a team by a user of the data ecosystem. This architecture allows for the identification and processing of different types of events typically associated with analytical chemistry systems.

[0030] Unless otherwise stated, it is contemplated that each embodiment can be used alone to achieve the advantages specifically noted above. It is also contemplated that the embodiments described above (and elsewhere herein) can be used in any combination to achieve further synergistic effects. Other technical features will be readily apparent to those skilled in the art from the following figures, descriptions, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure numeral that first introduces that element.

[0032] Figure 1 An exemplary interface according to one embodiment is shown.

[0033] Figure 2A An exemplary interface according to one embodiment is shown.

[0034] Figure 2B An exemplary interface according to one embodiment is shown.

[0035] Figure 3 An example of a mass spectrometry system according to an exemplary embodiment is shown.

[0036] Figure 4A A first exemplary data processing ecosystem is shown according to one embodiment.

[0037] Figure 4B A second exemplary data processing ecosystem is shown according to another embodiment.

[0038] Figure 5 An exemplary notification architecture is shown according to one embodiment.

[0039] Figure 6 An exemplary notification architecture is shown according to one embodiment.

[0040] Fig. 7A is a flow diagram depicting exemplary notification logic 700 for receiving events by an event bridge, according to one embodiment.

[0041] Figure 7B is a flow diagram depicting exemplary logic for generating notifications at a notification service according to one embodiment.

[0042] Figure 8 An exemplary computer system architecture is depicted that can be used to practice the exemplary embodiments described herein. DETAILED DESCRIPTION

[0043] To aid understanding, a series of examples will first be presented before describing a detailed description of the underlying implementation. It should be noted that these examples are merely illustrative, and the present invention is not limited to the embodiments shown.

[0044] Reference is now made to the accompanying drawings, in which like reference numerals are used to refer to like elements throughout. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding thereof. However, novel embodiments may be practiced without these specific details. In other cases, well-known structures and devices are shown in the form of block diagrams for ease of description thereof. It is intended to cover all modifications, equivalents, and substitutes consistent with the claimed subject matter.

[0045] In the drawings and accompanying description, the names "a", "b", and "c" (and similar designations) are intended to be variables representing any positive integers. Thus, for example, if an implementation sets a value of a=5, the complete set of components 122, shown as components 122-1 through 122-a, may include components 122-1, 122-2, 122-3, 122-4, and 122-5. The embodiments are not limited in this context.

[0046] These and other features will be described in more detail below with reference to the accompanying drawings.

[0047] Any device or application in the analytical chemistry system can generate a notification to be displayed to the user. For example, a laboratory analytical instrument can generate an event that triggers a notification when it completes data collection or when an error condition occurs, or an application can generate an event during or after data processing. Notifications can be sent to a variety of locations, such as an interface on the client browser 332 (see Figure 3 ), user email address or phone number (e.g., via SMS), etc.

[0048] Notifications may be sent to these various delivery channels based on a subscription list. A subscription may define a list of devices, email addresses, phone numbers, or other forms of contact information to which notifications should be sent. A subscription may also define a category of events to which the subscription applies: when an event in that category is received, a notification may be generated and sent to a delivery channel.

[0049] Figure 1 An example of an interface of the system status dashboard 100 is depicted, which may be displayed on a client browser 332 (or a suitable web page). The system status dashboard 100 may allow a user to create a subscription to notifications.

[0050] To this end, the system status dashboard 100 may include a toggleable notification element 102 that allows the user to turn notifications on or off for their user account (in this example, the user has identified their user account by entering their email address into a text field in the system status dashboard 100). The system status dashboard 100 may also include a notification device menu 104 that allows the user to select or enter a list of devices that should be provided with notifications. The list may include a list of delivery mechanisms (phone numbers, email addresses, applications, etc. to which subscriptions should be sent).

[0051] The system status dashboard 100 may also allow the user to select which categories of notifications they want to receive. For example, the interface may provide an input element that includes devices and applications accessible to the user. The user may be able to select or deselect some devices / applications in order to receive notifications of events from any selected devices / applications. The system status dashboard 100 may also provide more fine-grained options, such as allowing the user to subscribe to specific types of events only for a given device or application. For example, a user may register to receive notifications of system errors or warnings about a specific device, but may not be interested in receiving notifications when the device completes data collection. For example, a user may wish to receive notifications of the data processing status of a specific application, but may not wish to receive notifications of file ETL operations.

[0052] Subscriptions can apply to individual users or groups of users (e.g., organized into teams). When a team subscribed to receive notifications changes (e.g., in membership, in permissions, in the types of notifications it subscribes to receive, etc.), the corresponding subscription can be updated. The update can trigger an event, which itself can be used as the basis for a notification. Figure 2A An example of a rental management interface 200 is depicted in which the team was recently updated by adding a new user "Ben".

[0053] When a team (e.g., a user registered through a rental) changes membership, the team may have subscribed to receive notifications. To this end, when a user who is a member of the team (and therefore subscribed to receive notifications) logs into the rental management interface 200, they may receive notifications 204 in the interface. Notifications 204 may include descriptive text describing the event that caused the notification.

[0054] As discussed in more detail below, the notification service can be responsible for formatting the notification and sending it to the rental management interface 200 (e.g., via an API). The notification 204 can be displayed on different interfaces in a similar manner and in a similar format through the actions of the notification service. For example, the notification service can be responsible for formatting the notifications provided to different communication channels in a similar manner. Optionally, each application / web page that supports notifications can implement a common shared control or micro front end that allows a consistent notification experience across various applications.

[0055] In some cases, receiving a notification may trigger the automatic display of a list of notifications 204; alternatively, the list of notifications may remain hidden behind an icon, and the icon may update to indicate the presence of a new notification. For example, the icon may change color, flash, may emit an audible tone, or the icon may display a badge 206, potentially including a count of unread notifications. Optionally, the notification may trigger a pop-up window 202 in another portion of the interface to notify the user of the presence of a new notification. The pop-up window 202 may include the content of the notification and may persist for a predetermined, limited amount of time, after which the notification may still be available by interacting with the icon to cause the list of notifications 204 to be displayed.

[0056] Figure 2B Another example of a different type of notification is depicted, in this case, an ongoing process status 208. The ongoing process status 208 shows the status of data acquisition of one of the laboratory analytical instruments in the analytical chemistry system. When the instrument completes new data acquisition, an event can be triggered, causing the ongoing process status 208 to be updated. In this case, instead of generating a new notification in the window, the existing notification can be updated (e.g., by updating the number of completed data acquisitions and / or a progress bar).

[0057] The particular interface also shows a collection complete notification 210, which indicates that data collection by the instrument has been completed. In addition, an instrument error notification 212 is shown, indicating that there is a problem with the instrument that should be resolved. The collection complete notification 210 and the instrument error notification 212 can be displayed in different colors (different from each other and / or different from other types of notifications) so that the user can quickly be aware of specific types of notifications that may require more timely attention or indicate more important events (e.g., the completion of a long-running process, or a problem that needs to be resolved before data collection can continue). Generally, different types or categories of notifications can be distinguished in a variety of ways (by background color, font changes, by triggering different audible tones, etc.).

[0058] For illustration purposes, Figure 3 is a schematic diagram of an analytical chemistry system that can be used in conjunction with the techniques herein. Figure 3 A specific type of device is depicted in a specific liquid chromatography / mass spectrometry (LCMS) configuration, but one of ordinary skill in the art will appreciate that different types of chromatography devices (eg, MS, tandem MS, etc.) may also be used in conjunction with the present disclosure.

[0059] Sample 302 is injected into liquid chromatograph 304 via injector 306. Pump 308 may pump the sample through chromatography column 310 to separate the mixture into component parts according to retention time through the chromatography column.

[0060] The output from the chromatographic column is input into a mass spectrometer 312 for analysis. Initially, the sample is desolvated and ionized by a desolvation / ionization device 314. Desolvation can be any desolvation technique, including, for example, a heater, a gas, a heater in combination with a gas, or other desolvation techniques. Ionization can be achieved using any ionization technique, including, for example, electrospray ionization (ESI), atmospheric pressure chemical ionization (APCI), matrix-assisted laser desorption (MALDI), or other ionization techniques. The ions produced by the ionization are sent into a collision chamber 318 by a voltage gradient being applied to an ion guide 316. The collision chamber 318 can be used to transfer ions (low energy) or to fragment ions (high energy).

[0061] A different technique can be used, where an alternating voltage can be applied to the collision cell 318 to induce fragmentation. Spectra are collected of the precursor at low energy (no collision) and of the fragments at high energy (products of collision).

[0062] The output of the collision cell 318 is input to a mass analyzer 320. The mass analyzer 320 can be any mass analyzer, including a quadrupole, a time of flight (TOF), an ion trap, a magnetic sector mass analyzer, and a combination thereof. A detector 322 detects ions emitted from the mass analyzer 322. The detector 322 can be integrated with the mass analyzer 320. For example, in the case of a TOF mass analyzer, the detector 322 can be a microchannel plate detector that counts ion intensities (i.e., counts incident ions).

[0063] The raw data repository 324 can provide permanent storage for storing ion counts for analysis. For example, the raw data repository 324 can be an internal or external computer data storage device, such as a disk, a flash-based storage device, etc. The analysis device 326 analyzes the stored data. The data can also be analyzed in real time without being stored in the storage medium 324. In real-time analysis, the detector 322 passes the data to be analyzed directly to the analysis device 326, rather than first storing it in a permanent storage device.

[0064] The collision cell 318 performs fragmentation of the precursor ions. Fragmentation can be used to determine the primary sequence of the peptide and subsequently identify the origin protein. The collision cell 318 contains a gas, such as helium, argon, nitrogen, air, or methane. When the charged precursor interacts with the gas atoms, the collisions produced can fragment the precursor by decomposing the precursor into the resulting fragment ions. This fragmentation can be achieved by switching the voltage in the collision cell between a low voltage state (e.g., low energy, <5V) and a high voltage state (e.g., high energy or elevated energy, >15V). High voltage and low voltage can be referred to as high energy and low energy because high voltage or low voltage is used, respectively, to impart kinetic energy to the ions.

[0065] Various protocols may be used to determine when and how to switch voltages for such MS / MS acquisitions.After data acquisition, the resulting spectra may be extracted from the raw data repository 324 and displayed and processed by post-acquisition algorithms in the analysis device 326.

[0066] Metadata describing various parameters related to data collection can be generated with the raw data. This information can include the configuration of the liquid chromatograph 304 or mass spectrometer 312 (or other chromatographic device that collected the data), which can define the data type. An identifier (e.g., a key) of a codec configured to decode the data can also be stored as part of the metadata and / or with the raw data. The metadata can be stored in a metadata catalog 330 in the document repository 328.

[0067] The analysis device 326 can provide the analyst with visualization of data at each workflow step according to the workflow operation, and allow the analyst to generate output data by performing processing specific to the workflow step. The workflow can be generated and retrieved via the client browser 332. When the analysis device 326 performs the steps of the workflow, it can read the raw data from the data stream located in the raw data repository 324. When the analysis device 326 performs the steps of the workflow, it can generate processed data stored in the metadata directory 330 in the document repository 328; alternatively or in addition, the processed data can be stored in a different location specified by the user of the analysis device 326. It can also generate audit records that can be stored in the audit log 334.

[0068] The example embodiments described herein may be executed at the client browser 332 and the analysis device 326, among other locations. Figure 8 Examples of devices suitable for use as analysis device 326 and / or client browser 332 as well as various data storage devices are depicted in FIG.

[0069] Figure 4A An exemplary data ecosystem 412 for storing and retrieving chromatographic data is depicted.

[0070] A spectral acquisition 428 (such as a spectrometer, chromatograph, or other device) may perform and output measurements (e.g., as a stream of readouts formatted according to data types specific to the acquisition 428 and / or settings applied to the acquisition 428). These measurements may be stored in a raw data repository 424.

[0071] In one example, acquisition 428 can use an acquisition controller service to acquire samples. The acquisition controller service can submit the samples to an acquisition data receiver autonomous service via a RESTful API call. The acquisition data receiver autonomous service can create a sample set, which represents multiple samples sent to the instrument for analysis. In other words, a sample set is an organized sequence of several injections sent to a chromatographic device.

[0072] The raw data repository 424 may include data from multiple different chromatographic devices and / or chromatographic devices operating in multiple different acquisition modes. Thus, the data processing environment acts as a single data source for applications, regardless of which device generates the data (or in which mode the data operates). Calling into any application in the ecosystem ensures that any acquired data can be accessed and processed appropriately.

[0073] The sample set may be stored in a sample set model repository, while the injected raw data blocks may be sent to a separate acquisition data raw block repository. The data may typically be stored in an oracle database as one or more models, which may represent a serialization format for storing data. The serialization format may be a proprietary format. The model may be streamed to various applications and / or requested via an interface call. One or more libraries 432 built into the data ecosystem 412 may be able to read the models and deserialize them by converting them into basic modules. The library 432 may be, for example, a dynamic link library (DLL) of the data ecosystem 412. In addition to deserializing the model, the library 432 may also describe derived channels in the data by defining how to convert the measurement data into data of different types, formats, or organizations.

[0074] The collection 428 may also generate metadata describing the configuration of the collection 428, details of the experiment being performed, decoders configured to decode the data generated for the experiment, etc. This metadata may be stored in the metadata directory 330. As with the raw data repository 424, the metadata directory 330 may store metadata associated with a plurality of different collection devices in a plurality of different configurations.

[0075] The raw data can be decoded by a set of decoders 404, each of which is associated with a specific data type. For example, a decoder can be associated with a specific type of raw data generated by a chromatographic instrument in a specific acquisition mode. The instrument can output a raw data stream, including (for example) binary data, information arrays, etc. The decoder can be programmed to parse the raw data stream generated by such an instrument so that the data stream can be meaningfully interpreted.

[0076] In some embodiments, a single decoder may be associated with multiple data types; in another embodiment, multiple versions of the same decoder may each be associated with a different data type. Decoder 404 may be embedded within data service 402, such as an autonomous service (eg, via reflection).

[0077] Each autonomous service may expose one or more endpoint interfaces. A specific decoder may be associated with each endpoint interface. The decoder may be configured to interpret the raw data associated with the endpoint interface.

[0078] For example, the endpoints may be representational state transfer (REST) ​​endpoints capable of receiving RESTful application programming interface (API) calls. The endpoint interface may receive a request for raw data collected by the chromatographic instrument. The data ecosystem 418 may expose multiple endpoint interfaces; for example, each autonomous service may be associated with at least one endpoint interface and may expose at least one endpoint interface. An application 410a, 310c configured to process raw data may use an API call to call an endpoint interface in order to retrieve data.

[0079] The autonomous service (or another configuration) can retrieve the requested raw data from the raw data repository, apply the decoder to the raw data to generate decoded data, and can return the decoded data in response to the original request. For example, the autonomous service can apply the decoder to the raw data and provide the decoded data to the requesting application, or the autonomous service can identify the decoder and provide it (or a location where it can be accessed) along with the raw data (or the location of the raw data) to the requesting application. In the latter case, the application can use the decoder to decode the data.

[0080] Returning to the above example, the autonomous service may retrieve the sample set model from the sample set model repository and / or may retrieve the original data block from the original data block repository. The data may be decoded according to the decoder, and either version of the data (original data block or sample set) may be provided to the application. The reason for providing either or both of the original data block and the sample set model is that the application may be adjusted to use one or the other representation of the data for performance reasons.

[0081] By showing the endpoint interface in this way, applications 410a, 310c can request data collected by chromatographic instruments without understanding how to interpret the data. In addition, applications 410a, 410c can store data in a central repository together with metadata in a known or universal format, and metadata indicates, for example, when data is received by applications, when data is processed by decoders, the identity of the user who captures the data, the identity of the instrument that generates the data, and other information describing how and when to collect data. Therefore, when a new type of instrument is brought online (possibly outputting data in different stream formats), it is not necessary to reprogram each application 410a, 310c that may use the data. Because each application 410a, 410c does not need to be programmed with the details of how to interpret each different type of data stream, more different types of data can be made available to applications, which allows more complex analysis. This configuration also allows multiple different types of data to be stored together in a common source structure, thereby simplifying data retrieval and storage.

[0082] In the depicted embodiment, the endpoint interface has two types. The first type serves as a directory endpoint 406, which is configured to receive a request for metadata. In response to receiving a request for metadata on the directory endpoint 406, the data service 402 can identify the corresponding metadata in the metadata directory 330. The data service 402 can then return the requested metadata to the requesting application, or can return the location of the metadata so that it can be retrieved by the application as needed.

[0083] Another type of endpoint interface may be used as a data endpoint 408. Typically, there are multiple data endpoints 408 in the data ecosystem 412 corresponding to the multiple data types that the raw data repository 424 can support. Each data endpoint 408 is characterized by a data type. When an application requests data, it can call the raw data repository or metadata directory to identify the type of data; for example, the data may be tagged with a codec key stored with the data and / or stored in the metadata. The endpoint interface can be callable based on the data type, so once the data type is known, the requesting application can identify the appropriate endpoint interface to decode the data, and can formulate an appropriate RESTful API call to communicate with the interface. This provides an efficient way for applications to identify and call autonomous services that can decode data.

[0084] Therefore, incoming requests are divided into metadata-specific requests and data-specific requests. Each is handled by a different type of endpoint. This helps isolate incoming requests and provides a known endpoint to the requesting application for the appropriate type of request.

[0085] In this example, a single autonomous service handles requests for metadata and each different data type. Although simple to implement, it may be necessary to update the entire autonomous service every time one of the data types is changed or a new data type is added. This may result in unnecessary downtime. In addition, the autonomous service needs to be able to access both the metadata catalog 330 and the raw data repository 424. These issues can be alleviated by dividing the responsibility for different tasks between different autonomous services. Next, Figure 4B Describe an example of such an environment.

[0086] Figure 4B An alternative configuration is shown in which (1) metadata requests are all directed to a specific data service 414 that interfaces with a document repository 430 rather than a raw data repository 424, and (2) data requests are submitted to any one of a number of additional autonomous services, each of which has a specific decoder or set of decoders embedded and handles requests for data types specific to its embedded decoder.

[0087] In this configuration, multiple data services 420, 322, etc. service incoming requests for data. In addition, at least one data service 414 is specifically configured to respond to requests for metadata. Data services 414 that respond to metadata requests do not respond to requests for data, and therefore do not need to implement any functionality related to decoders. Similarly, data services 420, 322, etc. that respond to data requests do not need to implement any functionality for querying the metadata directory. When new data types are added, new autonomous services that implement decoders for the new data types can be added, or existing autonomous services can be updated with the new functionality. At the same time, most autonomous services can remain unchanged. Similarly, if the metadata directory API is ever changed, only the metadata processing autonomous service needs to be updated.

[0088] The original data repository 424 includes data of multiple different data types. Collectively, autonomous services can be configured to decode each of the multiple different data types. For example, multiple different data types can be included in an interface specification, which can describe how to decode various different types. The interface specification can be implemented at least in part by each of the autonomous services by implementing the corresponding data endpoint 408 and decoders 416, 324. Each data service 420, 322 can be associated with a different group of decoders 416, 324, although there may be some overlap in the decoders supported by different data services. However, no single data service implements all decoders, so the functions for decoding different types of data are distributed on multiple data services. Therefore, different parts of the interface specification can be divided between multiple different autonomous services, so that each autonomous service implements a part of the interface specification, but not all. Each part of the interface specification can be implemented by at least one autonomous service, so that the interface service group implements the interface specification together.

[0089] Because each autonomous service is tasked with implementing only a portion of the interface specification, each autonomous service can be simpler (since it does not need to be concerned with providing decoders and endpoint interfaces for the portions of the interface specification that it does not implement). New autonomous services can be easily added to handle new capabilities, and there is no need to shut down all autonomous services when one decoder needs to be updated.

[0090] Figure 5 and Figure 6 Depicts an exemplary architecture suitable for use with the exemplary embodiments. Note that Figure 5 and Figure 6 Involving a number of services, these services may be autonomous services in a cloud computing environment. However, the embodiments are not limited to this example, and the described services may be implemented by any suitable computing process.

[0091] A user 502 may interact with an analytical chemistry system (which may include one or more laboratory analytical instruments and / or a data ecosystem) using a user interface 520. For example, the user interface 520 may be displayed on a web page that can access information from the instrument and / or ecosystem, an information kiosk connected to the analytical chemistry system, or any other suitable device. The user may also interact with a mobile device 510 and / or a computer 508 that may be independent of the analytical chemistry system. The user may also interact with any other suitable type of device that may be registered to receive notifications.

[0092] To send notifications to the computer 508, mobile device 510, user interface 520, or other device, the notification service 514 may access the user notification queue service 616 (see Figure 6When an event is added to the user notification queue service 616, the notification service 514 may receive a notification (e.g., the user notification queue service 616 pushes the event to the notification service 514, the notification service 514 periodically pulls events from the user notification queue service 616, the notification service 514 establishes a listening program for listening to new events added to the user notification queue service 616, etc.).

[0093] Notification service 514 may identify the type or classification of the event, which may be stored in metadata in the event. Notification service 514 may provide notifications to the user via subscription service 602 ( Figure 6 ) searches a list of subscribers that have subscribed to receive notifications of events of the type just accessed. The list of subscribers may include individual subscriber identifiers and / or identifiers of a team of subscribers. Subscription service 602 may look up the team members associated with the subscription and return a list of subscribers to notification service 514. Optionally, subscription service 602 identifies the distribution channels associated with each subscribing user and provides notification service 514 with a list of distribution channels that the application uses to send notifications (and optionally, the type of channel, such as SMS, email, interface notification accessible through an API call, etc.).

[0094] The notification service 514 is connected to an in-memory data store 518 that includes notification templates, one for each distribution channel with which 514 can interact. For example, the in-memory data store 518 may include templates for emails that can be generated for different types of events, SMS templates, interface templates for different types of API calls, etc. An example of the in-memory data store 518 is ELASTICACHE provided by AMAZON WEB SERVICES.

[0095] When notification service 514 uses the template to generate notifications based on events received from user notification queuing service 616, notification service 514 can send notifications on the distribution channel identified by subscription service 602. For example, notification service 514 can issue an API call to update user interface 520. Figure 5 Only a single user interface 520 is depicted in FIG. 5 , but it should be understood that user interface 520 may include interfaces for more than one application. In some embodiments, active (e.g., foreground) and / or inactive (e.g., background) applications may receive notifications. A user may receive notifications of events generated by a first application while the user is interacting with the interface of a second, different application, even if the first application is operating in the background or is not operating on the device with which the user is currently interacting.

[0096] The application with user interface 520 can be part of an analytical chemistry system (notification service 514 can also be part of the analytical chemistry system). It can be relatively straightforward for notification service 514 to interact with local devices and applications that are part of the analytical chemistry system because the analytical chemistry system and local devices / applications can be hosted on the same cloud computing service.

[0097] However, the exemplary embodiment is also capable of interacting with devices and applications (such as computers 508 and mobile devices 510) outside the scope of analytical chemistry services. To this end, notification service 514 can add outbound notifications to outbound notification queuing service 512. When notifications are received in outbound notification queuing service 512, serverless computing service 522 can retrieve notifications and deliver them to their intended recipients. For example, when a notification is added to outbound notification queuing service 512, an event that calls serverless computing service 522 can be triggered. An example of a suitable serverless computing service 522 is the AWS LAMBDA service provided by AMAZON WEBSERVICES. Through serverless computing service 522, notification service 514 can send push notifications, such as simple email service notifications via email notification service 506 and / or simple message service notifications via SMS notification service 504. An example of email notification service 506 is AMAZON SIMPLE EMAIL SERVICE provided by AMAZON WEB SERVICES, and an example of 504 is AMAZON SIMPLEMESSAGE SERVICE provided by AMAZON WEB SERVICES.

[0098] Notification service 514 may store notifications and / or information about notifications in notification database 516. For example, notification service 514 may store the read / unread status of each notification (or each notification that supports such status updates) in notification database 516. The information in notification database 516 may be used to update the status of notifications on user interface 520 and / or other devices / applications, such as by updating a count of unread notifications, changing the visual status of read notifications, etc.

[0099] The status update of notifications can be supported by having the notification service 514 expose a status API that the user interface 520, computer 508, mobile device 510, etc. can call when the notification is read. Different devices can determine the read status of each notification according to the situation of the delivery channel, for example, when a user opens a conversation including an SMS message, the SMS message can be considered read; when a user opens or previews an email, the email can be considered read, and when a user interacts with a notification icon and the notification icon indicates that there are unread messages, the notification in the user interface 520 can be considered read. In some cases, the user can be allowed to manually switch the read / unread status of the notification in a manner suitable for the delivery channel.

[0100] Figure 6 The portion of the architecture responsible for managing subscriptions and adding event notifications to the user notification queue service 616 is depicted.

[0101] Subscription interface 614 can receive changes to subscriptions via a dashboard, web page, or other suitable interface. Users of the analytical chemistry system can be organized into teams (or can be represented as individuals). Teams or individuals can be associated with assigned access rights and permissions, and different teams or individuals can register to receive notifications of different types of events through subscription interface 614.

[0102] Subscription interface 614 may generate events corresponding to any changes in a subscription (e.g., creating a new team, removing a team, adding or removing a user from a team, changing permissions for a team, changing the types of events a team or individual subscribes to receive, etc.). The event may be sent from subscription interface 614 to lab monitoring service 606, which is configured to monitor changes to subscriptions. Lab monitor service 606 may then send the event to event bridge 618.

[0103] The event bridge 618 may be an event bus configured to route events to appropriate services (eg, based on routing rules). An example of an event bridge 618 suitable for use with the exemplary embodiment is the AMAZONEVENTBRIDGE of AMAZON WEB SERVICES.

[0104] When event bridge 618 receives a subscription-related event, the change indicated by the event may be recorded in audit log queuing service 624 for later use by audit log service 610. Audit log service 610 may be configured to retrieve events from audit log queuing service 624 and use them to construct an appropriate audit log 334 (see Figure 3 ).

[0105] Subscription-related events may also cause the event bridge 618 to send a user / team change event to a subscription queuing service 622. The subscription queuing service 622 may then provide the event to the subscription service 602, which updates the currently active subscription based on the event. The currently active subscription may be stored in a subscription database 620, which the subscription service 602 may query when the notification service 514 requests a list of subscribers for a particular notification. The subscription database 620 may include a list of subscribers, the event types for which the subscriber receives notifications, and other relevant subscription-related information. The subscription service 602 may query the subscription database 620 and display current information about the subscription via a call to a read-only / query subscription API 612, which may be accessed via a suitable interface (e.g., a web page or kiosk associated with an analytical chemistry system).

[0106] Similarly, the compliance service 608 can be configured to generate events when user / team assignments change. This can change subscription-related information, and these events can be routed in a similar manner to the subscription-related events described above.

[0107] In addition, one or more device services 604 can coordinate the interaction with laboratory analytical instruments, data analysis devices, and applications in the analytical chemistry system. When one of these devices meets a predefined condition (e.g., completes data acquisition, is placed in an error state, generates a warning, completes data processing or a data processing sub-step, receives a user's sign-off on a method step or an audit record, etc.), the device service 604 can be configured to generate a corresponding event. The event can be directed by the device service 604 to the event bridge 618.

[0108] Upon receiving the event, the event bridge 618 may generate an audit entry for the audit log queue service 624. The event bridge 618 may also send the event to the user notification queue service 616, which triggers the above-mentioned combination of Figure 5 The sequence of events described.

[0109] Fig. 7A 700 is a flowchart depicting an exemplary notification logic for performing a computer-implemented method according to an exemplary embodiment. The logic may be embodied as instructions stored on a computer-readable medium, the instructions being configured to be executed by a processor. The logic may be implemented by a suitable computing system configured to perform the actions described below. Fig. 7A The logic may be executed, for example, by the event bridge 618.

[0110] Processing begins at start block 702, which may be triggered, for example, when event bridge 618 is started.

[0111] In block 704, event bridge 618 may access a data ecosystem, such as an ecosystem of an analytical chemistry system. For example, event bridge 618 may announce its presence to device service 604, laboratory monitoring service 606, compliance service 608, and other suitable services and processes of the analytical chemistry system. Event bridge 618 may also create or access subscription queue service 622, user notification queue service 616, and / or audit log queue service 624.

[0112] In decision block 706, event bridge 618 may receive a communication in the form of an event. If the event is a device or application event (e.g., an event received from device service 604), processing may proceed to block 708 and event bridge 618 may store the event in a notification queue (such as user notification queuing service 616). The event may include category information that is added to the event by device service 604 or determined by event bridge 618. Notification service 514 and / or subscription service 602 may use the category information to determine which subscribers should receive notifications for the event.

[0113] In block 712, event bridge 618 may create an audit record. This may involve, for example, sending the event to audit log queuing service 624 so that audit log service 610 may take appropriate action to add the event to the audit log.

[0114] If it is determined at decision block 706 that the communication is a user, team, or subscription change event (e.g., an event received from lab monitor service 606 or compliance service 608), processing may proceed to block 710, where the event bridge may update the subscription queue. This may involve sending the event to subscription queuing service 622 so that subscription database 620 may take appropriate action as described above. Processing may then proceed to block 712, where the event bridge 618 creates an audit record as already described.

[0115] After the audit record is created in block 712, processing may return to decision block 706, whereupon the event bridge 618 awaits the next event from the analytical chemistry system.

[0116] although Fig. 7A Specific actions are depicted as being performed in a specific order, but the embodiments are not limited to Fig. 7A It is contemplated that more, fewer, or different logic blocks may be implemented. Similarly, it is contemplated that Fig. 7A The actions may be performed in a different order than shown.

[0117] Figure 7B700 is a flowchart depicting an exemplary notification logic for performing a computer-implemented method according to an exemplary embodiment. The logic may be embodied as instructions stored on a computer-readable medium, the instructions being configured to be executed by a processor. The logic may be implemented by a suitable computing system configured to perform the actions described below. Figure 7B The logic may be executed, for example, by notification service 514.

[0118] Processing may begin at start block 714, which may be performed when notification service 514 is initially started. Notification service 514 may connect to (or create) user notification queuing service 616, notification database 516, in-memory data store 518, outbound notification queuing service 512, and the like.

[0119] In block 716, notification service 514 may retrieve the next event from user notification queuing service 616. Based on the event and / or metadata associated with the event (e.g., the type or category of the event, or the service from which the event originated), notification service 514 may determine which subscribers should receive notification of the event.

[0120] To this end, the notification service 514 may obtain a list of event subscribers in block 718. This may be accomplished, for example, by querying the subscription service 602 based on the event or its type / category. The subscription service 602 may query the subscription database 620 and return a subscription identifier, a list of subscribers, and / or a list of delivery channels to which notifications should be delivered.

[0121] Based on the information returned from the subscription service 602, the notification service 514 may generate a notification to be delivered on each delivery channel associated with the subscription in block 720. This may involve formatting the notification according to each type of delivery channel, such as by applying one or more templates retrieved from the in-memory data store 518.

[0122] In block 722, notification service 514 may send the generated notification on a delivery channel associated with the relevant subscription. For example, notification service 514 may call an appropriate user interface 520 API and / or utilize SMS notification service 504 or email notification service 506, etc. Processing may then return to block 716, at which point notification service 514 may wait for the next event.

[0123] although Figure 7B Specific actions are depicted as being performed in a specific order, but the embodiments are not limited to Figure 7B It is contemplated that more, fewer, or different logic blocks may be implemented. Similarly, it is contemplated that Figure 7B The actions may be performed in a different order than shown.

[0124] Figure 8An example of a system architecture and data processing device that can be used to implement one or more illustrative aspects described herein in a standalone and / or networked environment is shown. Various network nodes such as data server 810, web server 806, computer 804, and laptop computer 802 can be interconnected via a wide area network (WAN) 808 such as the Internet. Other networks can also or alternatively be used, including a private intranet, a company network, a LAN, a metropolitan area network (MAN), a wireless network, a personal network (PAN), etc. Network 808 is for illustrative purposes and can be replaced by fewer or more computer networks. A local area network (LAN) can have one or more topologies in any known LAN topology, and can use one or more protocols in a variety of different protocols, such as Ethernet. Device data server 810, web server 806, computer 804, laptop computer 802 and other devices (not shown) can be connected to one or more networks in the network via twisted pair, coaxial cable, optical fiber, radio waves or other communication media.

[0125] The computer software, hardware, and networks may be used in a variety of different system environments, including stand-alone, networked, remote access (also known as remote desktop), virtualized, and / or cloud-based environments, among others.

[0126] The term "network" as used herein and depicted in the accompanying drawings refers not only to a system in which remote storage devices are coupled together via one or more communication paths, but also to independent devices that may be coupled to such a system from time to time having storage capabilities. Thus, the term "network" includes not only a "physical network" but also a "content network" consisting of data residing on all physical networks that can be attributed to a single entity.

[0127] Components may include a data server 810, a web server 806, a client computer 804, and a laptop computer 802. The data server 810 provides overall access, control, and management of databases and control software for performing one or more illustrative aspects described herein. The data server 810 may be connected to a web server 806, through which a user interacts with the requested data and obtains the data. Alternatively, the data server 810 itself may act as a web server and be directly connected to the Internet. The data server 810 may be connected to the web server 806 via a network 808 (e.g., the Internet), via a direct or indirect connection, or via some other network. A user may interact with the data server 810 using a remote computer 804, a laptop computer 802, such as using a web browser to connect to the data server 810 via one or more external public web sites hosted by the web server 806. The client computer 804, the laptop computer 802 may be used together with the data server 810 to access the data stored therein, or may be used for other purposes. For example, a user may access web server 806 from client computer 804 using an Internet browser (as is known in the art) or by executing a software application that communicates with web server 806 and / or data server 810 via a computer network (such as the Internet).

[0128] The server and application can be combined on the same physical machine and retain separate virtual or logical addresses, or can reside on separate physical machines. Figure 8 Only one example of a network architecture that may be used is shown, and those skilled in the art will appreciate that the specific network architecture and data processing devices used may vary and are secondary to the functionality they provide, as further described herein. For example, the services provided by web server 806 and data server 810 may be combined on a single server.

[0129] Each component data server 810, web server 806, computer 804, laptop computer 802 can be any type of known computer, server or data processing device. The data server 810 can include, for example, a processor 812 that controls the overall operation of the data server 810. The data server 810 can also include a RAM 816, a ROM 818, a network interface 814, an input / output interface 820 (e.g., a keyboard, a mouse, a display, a printer, etc.) and a memory 822. The input / output interface 820 can include various interface units and drivers for reading, writing, displaying and / or printing data or files. The memory 822 can also store operating system software 824 for controlling the overall operation of the data server 810, control logic 826 for instructing the data server 810 to perform various aspects described herein, and other application software 828 that provides auxiliary, support and / or other functions that can be used in conjunction with or without the various aspects described herein. The control logic may also be referred to as data server software control logic 826 in this article. The functionality of the data server software may refer to a combination of operations or decisions made automatically based on rules encoded into the control logic, manually by a user providing input to the system, and / or automatic processing based on user input (e.g., queries, data updates, etc.).

[0130] The memory 1222 (deleted) may also store data for performing one or more aspects described herein, including a first database 832 and a second database 830. In some embodiments, the first database may include the second database (e.g., as a separate table, report, etc.). That is, the information may be stored in a single database, or divided into different logical, virtual or physical databases, depending on the system design. The web server 806, computer 804, laptop computer 802 may have an architecture similar to or different from that described with respect to the data server 810. Those skilled in the art will appreciate that the functionality of the data server 810 (or web server 806, computer 804, laptop computer 802) as described herein may be distributed across multiple data processing devices, for example, to distribute processing loads across multiple computers, to separate transactions based on geographic location, user access level, quality of service (QoS), etc.

[0131] One or more aspects may be embodied in computer-usable or readable data and / or computer-executable instructions, such as embodied in one or more program modules executed by one or more computers or other devices as described herein. Typically, program modules include routines, programs, objects, components, data structures, etc., which perform specific tasks or implement specific abstract data types when executed by a processor in a computer or other device. These modules can be written in source code programming languages, which are then compiled for execution, or these modules can be written in scripting languages ​​such as (but not limited to) HTML or XML. Computer executable instructions can be stored on a computer-readable medium such as a non-volatile storage device. Any suitable computer-readable storage medium can be used, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and / or any combination thereof. In addition, various transmission (non-storage) media representing data or events as described herein can be transmitted between a source and a destination in the form of electromagnetic waves propagated through a signal-conducting medium (such as a metal wire, an optical fiber, and / or a wireless transmission medium). The various aspects described herein can be embodied as a method, a data processing system, or a computer program product. Thus, the various functions may be embodied in whole or in part in software, firmware, and / or hardware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGAs), etc. Certain data structures may be used to more efficiently implement one or more aspects described herein, and such data structures are contemplated to be within the scope of the computer-executable instructions and computer-usable data described herein.

[0132] The components and features of the devices described above may be implemented using any combination of discrete circuit systems, application specific integrated circuits (ASICs), logic gates, and / or single chip architectures. In addition, where appropriate, the features of these devices may be implemented using microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the foregoing. It should be noted that hardware, firmware, and / or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

[0133] It should be understood that the exemplary devices shown in the above block diagrams may represent a functional descriptive example of many possible specific implementations. Therefore, the division, omission or inclusion of block functions depicted in the drawings does not mean that the hardware components, circuits, software and / or elements used to implement these functions will necessarily be divided, omitted or included in the implementation.

[0134] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.

[0135] Some embodiments may be described using the expression "one embodiment" or "an embodiment" and their derivatives. These terms mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearance of the phrase "in one embodiment" in different places in the specification does not necessarily refer to the same embodiment. In addition, unless otherwise stated, the above-mentioned features are considered to be usable together in any combination. Therefore, any features discussed separately can be used in combination with each other, unless it is stated that these features are incompatible with each other.

[0136] The detailed description herein may be presented in terms of program processes executed on a computer or computer network with general reference to the notations and nomenclature used herein. These program descriptions and representations are used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art.

[0137] A process is generally considered to be a self-consistent sequence of operations that brings about a desired result. These operations are those requiring physical manipulation of physical quantities. Although not required, these quantities usually take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. In practice, it has proven convenient at times to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for common reasons. It should be noted, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.

[0138] In addition, the manipulations performed are often referred to by terms such as adding or comparing, which are often associated with mental operations performed by a human operator. In any of the operations described herein that form a part of one or more embodiments, in most cases, such capabilities of a human operator are not necessary or desirable. Instead, these operations are machine operations. Useful machines for performing the operations of the various embodiments include general purpose digital computers or similar devices.

[0139] The expressions "coupled" and "connected," as well as their derivatives, may be used to describe some embodiments. These terms are not necessarily intended to be synonymous with each other. For example, some embodiments may be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

[0140] Various embodiments also relate to devices or systems for performing these operations. The device may be specially constructed for the desired purpose, or it may include a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. The processes presented herein are not inherently related to a particular computer or other device. Various general-purpose machines may be used with programs written according to the teachings of this article, or it may prove convenient to construct more specialized devices to perform the desired method steps. The desired structures of various of these machines will appear in the description given.

[0141] It should be emphasized that the abstract of the present disclosure is provided so as to allow the reader to quickly determine the essence of the technical disclosure. It should be understood that the submitted abstract will not be used to interpret or limit the scope or meaning of the claims. In addition, in the aforementioned specific embodiments, it can be seen that various features can be grouped together in a single embodiment for the purpose of simplifying the present disclosure. This method of the present disclosure should not be interpreted as reflecting the intention that the claimed embodiment requires more features than the features explicitly stated in each claim. On the contrary, as reflected in the following claims, the subject matter of the present invention is less than all the features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the specific embodiments, wherein each claim exists independently as a separate embodiment. In the attached claims, the terms "including" and "in which" are used as the plain English equivalents of the corresponding terms "comprising" and "wherein", respectively. In addition, the terms "first", "second", "third", etc. are used only as labels and are not intended to impose numerical requirements on their objects.

[0142] What has been described above includes examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and / or methods, but one of ordinary skill in the art will recognize that many further combinations and permutations are possible. Therefore, the novel architecture is intended to encompass all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A computer-implemented method, the computer-implemented method comprising: Access to the data ecosystem for analytical chemistry systems; receiving, at an event bridge in the data ecosystem, events from applications connected to the data ecosystem; generating a notification of the event; as well as The notification is sent across a plurality of different delivery channels to users who have subscribed to receive notification of the event.

2. The computer-implemented method of claim 1, wherein the event is one or more of: a new audit log entry, completion of an asynchronous operation, an error or warning associated with the asynchronous operation, a collection event, a file upload, a file conversion, or a workflow-related operation.

3. The computer-implemented method of claim 1, wherein the plurality of different channels include at least two of the following: a simple messaging service channel, an email channel, a web browser channel, and an application programming interface (API) channel. 4 . The computer-implemented method of claim 1 , wherein the application is a first application and the event is received when a second application different from the first application is active.

5. The computer-implemented method of claim 1, wherein a notification service retrieves a copy of the event from a notification queue in communication with the event bridge, converts the event into the notification, and sends the notification on the plurality of channels.

6. The computer-implemented method of claim 5, wherein the event bridge communicates with one or more of: a device service configured to generate events describing a status of a laboratory analytical instrument in the analytical chemistry system; a laboratory monitoring service configured to generate an event in response to creation, editing, or removal of a subscription in the data ecosystem; or A compliance service configured to generate an event in response to an assignment of a team by a user of the data ecosystem or a change in the assignment of one or more permissions to the team.

7. The computer-implemented method of claim 1 , further comprising adding an entry corresponding to the event to an audit log maintained by the data ecosystem.

8. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: Access to the data ecosystem for analytical chemistry systems; receiving, at an event bridge in the data ecosystem, events from applications connected to the data ecosystem; generating a notification of the event; as well as The notification is sent across a plurality of different delivery channels to users who have subscribed to receive notification of the event.

9. The computer-readable storage medium of claim 8, wherein the event is one or more of: a new audit log entry, completion of an asynchronous operation, an error or warning associated with the asynchronous operation, a collection event, a file upload, a file conversion, or a workflow-related operation.

10. The computer-readable storage medium of claim 8, wherein the plurality of different channels include at least two of the following: a simple messaging service channel, an email channel, a web browser channel, and an application program interface (API) channel.

11. The computer-readable storage medium of claim 8, wherein the application is a first application and the event is received when a second application different from the first application is active.

12. The computer-readable storage medium of claim 8, wherein a notification service retrieves a copy of the event from a notification queue in communication with the event bridge, converts the event into the notification, and sends the notification on the plurality of channels.

13. The computer-readable storage medium of claim 12, wherein the event bridge communicates with one or more of: a device service configured to generate events describing a status of a laboratory analytical instrument in the analytical chemistry system; a laboratory monitoring service configured to generate an event in response to creation, editing, or removal of a subscription in the data ecosystem; or A compliance service configured to generate an event in response to an assignment of a team by a user of the data ecosystem or a change in the assignment of one or more permissions to the team.

14. The computer-readable storage medium of claim 8, wherein the instructions further configure the computer to add an entry corresponding to the event to an audit log maintained by the data ecosystem.

15. A computing device, the computing device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the device to: Access to the data ecosystem for analytical chemistry systems; receiving, at an event bridge in the data ecosystem, events from applications connected to the data ecosystem; generating a notification of the event; as well as The notification is sent across a plurality of different delivery channels to users who have subscribed to receive notification of the event.

16. A computing device according to claim 15, wherein the event is one or more of the following: a new audit log entry, completion of an asynchronous operation, an error or warning associated with the asynchronous operation, a collection event, a file upload, a file conversion, or a workflow-related operation.

17. A computing device according to claim 15, wherein the plurality of different channels include at least two of the following: a simple messaging service channel, an email channel, a web browser channel, and an application program interface (API) channel.

18. The computing device of claim 15, wherein the application is a first application and the event is received when a second application different from the first application is active.

19. A computing device according to claim 15, wherein a notification service retrieves a copy of the event from a notification queue in communication with the event bridge, converts the event into the notification, and sends the notification on the plurality of channels.

20. The computing device of claim 19, wherein the event bridge is in communication with one or more of: a device service configured to generate events describing a status of a laboratory analytical instrument in the analytical chemistry system; a laboratory monitoring service configured to generate an event in response to creation, editing, or removal of a subscription in the data ecosystem; or A compliance service configured to generate an event in response to an assignment of a team by a user of the data ecosystem or a change in the assignment of one or more permissions to the team.