Method and system for laboratory sample tracking

Abstract

Scientific instrument support systems and related methods, computing devices, and computer readable media are disclosed herein. For example, in some embodiments, there is provided a method comprising: generating a sample identifier for a sample; receiving sample information of the sample; and generating a data structure ledger for the sample. The data structure ledger includes an initial ledger block having the sample identifier and the sample information. The method further includes receiving experimental data associated with the sample; experimental ledger blocks are generated in the data structure ledger. The method further includes receiving a request for a report corresponding to the sample; querying the data structure ledger to receive ledger data corresponding to the request; and generating the report based on the ledger data received in response to the query.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to co-pending U.S. Provisional Patent Application No. 63 / 629,956, filed on September 25, 2023, the entire contents of which are incorporated herein by reference. Background Art

[0003] Clinical and testing laboratories receive samples for analysis, which can be divided into aliquots. Each sample (each aliquot) can be prepared and / or analyzed by several scientific instruments, including, for example, chromatographs (e.g., gas phase, liquid phase, etc.), spectrometers, etc. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Each embodiment will be easily understood by the following detailed description in conjunction with the accompanying drawings. For ease of description, the same reference numerals indicate the same structural elements. Each embodiment is illustrated in each figure of the accompanying drawings by way of example and not limitation.

[0005] Figure 1 is a block diagram of an example scientific instrument support system for performing support operations according to various embodiments.

[0006] Figure 2 is a block diagram of an example scientific instrument support module for performing support operations according to various embodiments.

[0007] Figure 3 is an example of a graphical user interface that may be used to perform some or all of the supporting methods disclosed herein, according to various embodiments.

[0008] Figure 4 is a block diagram of an example computing device that may perform some or all of the scientific instrument support methods disclosed herein, according to various embodiments.

[0009] Figure 5 is a block diagram of an example scientific instrument support system in which some or all of the scientific instrument support methods disclosed herein may be performed, according to various embodiments.

[0010] Figure 6 is a flow diagram of an example method of performing support operations according to various embodiments.

[0011] 7A to 7D is an example of a graphical user interface that may be used to perform some or all of the supporting methods disclosed herein, according to various embodiments.

[0012] [TP386059USPRV1]

[0013] Figure 8 is an example of a graphical user interface that may be used to perform some or all of the supporting methods disclosed herein, according to various embodiments. DETAILED DESCRIPTION

[0014] In a laboratory environment, samples are processed and / or analyzed by one or more scientific instruments (e.g., via one or more aliquots), such as to determine the presence or absence of a compound in a sample, the amount of a compound in a sample, etc. Each scientific instrument that processes and / or analyzes a sample can use different software applications to analyze and generate analysis results. Therefore, in order to generate a report for a sample, a technician manually collects information from each of these scientific instruments and manually compiles the collected information. It is troublesome and error-prone to ensure that the report includes all applicable results associated with the sample, because the technician must track the sample across different aliquots and / or scientific instructions and across the results that may be generated by different software applications, and these different software applications can use different ways to identify the sample. Laboratory information management systems (LIMS) can be used to track samples by various experiments performed by one or more scientific instruments. However, LIMS may still face several of the above-mentioned problems. The entries in this LIMS are manually entered by a technician, and LIMS is not integrated with scientific instruments. The different ways that LIMS and scientific instruments generate and store data may make it difficult to map results to specific samples tracked via LIMS. Additionally, LIMS only stores a subset of the data associated with the sample. The data stored in LIMS may not be inherently associated with the sample’s metadata. Therefore, not only is report generation cumbersome and error-prone, but it often fails to efficiently utilize laboratory resources, including instrument usage, consumables usage, data processing usage, bandwidth usage, etc.

[0015] Therefore, in order to solve these and other problems of existing laboratory environments and related management technologies, scientific instrument support systems and related methods, computing devices and computer-readable media are disclosed herein. For example, in some embodiments, a method is provided, the method comprising: generating a sample identifier for a sample using a processing device; receiving sample information of the sample using the processing device; and receiving experimental data related to the sample from multiple scientific instruments using the processing device; and generating a data structure ledger for the sample using the processing device, the data structure ledger including the experimental data associated with the sample identifier and the sample information. The method also includes: receiving a request for a report corresponding to the sample; querying the data structure ledger to receive ledger data corresponding to the request; and generating the report based on the ledger data received in response to the query.

[0016] In some embodiments, a scientific instrument support system includes one or a group of processing devices, the one or a group of processing devices configured to: generate a sample identifier for a sample; receive sample information for the sample; and generate a data structure ledger for the sample. The data structure ledger includes an initial ledger block having the sample identifier and the sample information. The one or a group of processing devices are also configured to generate an experimental ledger block in the data structure ledger. The experimental ledger block includes experimental data received from a scientific instrument. The one or a group of processing devices are also configured to: receive a request for a report corresponding to the sample; query the data structure ledger to receive ledger data corresponding to the request; and generate the report based on the ledger data received in response to the query.

[0017] In some embodiments, a scientific instrument support device includes: first logic for generating a sample identifier for a sample; second logic for receiving sample information for the sample; and third logic for generating a data structure ledger for the sample. The data structure ledger includes an initial ledger block having the sample identifier and the sample information. The scientific instrument support device also includes fourth logic for generating a time-stamped experimental ledger block in the data structure ledger. The experimental ledger block includes experimental data received from a plurality of scientific instruments. The scientific instrument support device also includes: fifth logic for receiving a request for a report corresponding to the sample; sixth logic for querying the data structure ledger to receive ledger data corresponding to the request; and seventh logic for generating the report based on the ledger data received in response to the query.

[0018] The scientific instrument support embodiments disclosed herein can achieve improved performance relative to conventional methods. For example, the described sample tracking methods and systems significantly improve the storage and retrieval of sample information for report generation. Specifically, the described methods and systems allow for easy integration of data from various scientific instrument analyses performed on samples so that the data can be accessed later to generate reports. Thus, the embodiments disclosed herein provide improvements to scientific instrument technology (e.g., improvements in computer technology to support such scientific instruments, among other improvements). Entire laboratory platforms (e.g., Ardia TM Platform) can create the opportunity to ensure that result data is written to / associated with any necessary sample information to create an audit trail of the sample.

[0019] Various embodiments of the embodiments disclosed herein can improve conventional methods to achieve technical advantages of higher throughput and data validation by improving the data structure relationship between various experiments performed on samples. Such technical advantages cannot be achieved by routine and conventional methods, and all users of systems including such embodiments can benefit from these advantages (e.g., by helping users perform technical tasks, such as generating sample reports through a guided human-computer interaction process). As further discussed herein, various aspects of the embodiments disclosed herein can improve the functionality of the computer itself; for example, the speed with which sample data can be parsed and subsequently retrieved. [TP386059USPRV1] disclosed herein

[0020] The computational and user interface features not only involve the collection and comparison of information, but also apply new analyses and techniques to change the operation of scientific support devices. Thus, the present disclosure introduces functions that neither conventional computing devices nor humans can perform.

[0021] In the following detailed description, reference is made to the accompanying drawings, which form a part of the detailed description, wherein the same reference numerals designate the same parts throughout, and in the accompanying drawings, practicable embodiments are shown by way of example. It should be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description should not be considered to have a limiting meaning.

[0022] The various operations may be described as a plurality of discrete actions or operations in a manner that is most helpful for understanding the subject matter disclosed herein. However, the described order should not be interpreted as implying that these operations must rely on the order. Specifically, these operations may not be performed in the order presented. The described operations may be performed in an order different from the described embodiments. Various additional operations may be performed, and / or the described operations may be omitted in additional embodiments.

[0023] For purposes of this disclosure, the phrases "A and / or B" and "A or B" mean (A), (B), or (A and B). For purposes of this disclosure, the phrases "A, B, and / or C" and "A, B, or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C). Although some elements may be referred to in the singular (e.g., "processing device"), any appropriate element may be represented by multiple instances of the element, and vice versa. For example, a set of operations described as being performed by a processing device may be implemented by different ones of the operations being performed by different processing devices.

[0024] This specification uses the phrases "embodiment," "various embodiments," and "some embodiments," each of which may refer to one or more of the same or different embodiments. In addition, the terms "including," "comprising," "having," and the like as used with respect to the embodiments of the present disclosure are synonymous. When used to describe a range of sizes, the phrase "between X and Y" means a range that includes X and Y. As used herein, "device" may refer to any individual device, collection of devices, part of a device, or collection of parts of a device. The drawings are not necessarily drawn to scale.

[0025] Figure 1 is a block diagram of a scientific instrument support system 100 (hereinafter referred to as support system 100) for performing support operations according to various embodiments. Figure 1 , the support system 100 includes a plurality of instrument computing devices 104 connected via a communication network 120. Each instrument computing device 104 is communicatively connected to a scientific instrument 108 and a corresponding support device 112. The support device 112 is a physical entity that performs a certain function of sample preparation and / or sample analysis. The support device 112 may include, for example, a sensor, a detector, an actuator, a spectrometer, a sonographer, an oscilloscope, an electric meter, an interferometer, etc. The scientific instrument 108 is a logical container that includes a collection of support devices 112. For example, the support devices 112 work together to perform operations and produce results. The scientific instrument 108 (including the collection of support devices 112) prepares or analyzes inputs such as blood samples or other biological samples, semiconductors, chemical compounds, solutions, food and drug samples, etc. The scientific instrument 108 may include, for example, a liquid chromatography instrument, a gas chromatography instrument, an ion chromatography instrument, a mass spectrometry instrument, a trace element instrument (e.g., inductively coupled plasma mass spectrometry, inductively coupled plasma optical emission spectroscopy, atomic absorption, etc.), a capillary electrophoresis instrument, a spectroscopic instrument, etc.

[0026] The support system 100 includes a database 116, a server 124, and a user device 128 that are communicatively coupled to the plurality of instrument computing devices 104 (and to each other) via a communication network 120. It should be appreciated that the support system 100 may include more than one embodiment of the present invention. Figure 1 For example, the support system 100 may include fewer or more instrument computing devices 104, multiple servers 124, multiple databases 116, or a combination thereof. In some examples, the database 116 may be implemented by the server 124 or a cloud service provider. The components of the support system 100 may also be implemented by Figure 1 Communicates with one or more intermediate devices not illustrated.

[0027] The server 124 may act as a "control hub" for multiple instrument computing devices 104. For example, the server 124 may track the status of each instrument computing device 104 to track the availability of scientific instruments 108 and the experiments being performed on the scientific instruments. The server 124 may communicate with each of the instrument computing devices 104 by sending commands to the instrument computing device 104 to write experimental data to a data structure ledger, as described further below, or may be responsible for writing experimental data output by a particular instrument to a data structure ledger, as described further below. For example, the server 124 may implement a server-based platform (e.g., Ardia from Thermo Fisher Scientific) TM The server 124 can detect and register the instrument computing device 104, and can collect and adjust the information output by the instrument computing device 104. The server-based platform helps ensure that laboratory equipment and equipment store and access sample information and experimental data. The server 124 can act as a control center or facilitation center (e.g., for a centralized ledger example) for the entire platform to facilitate the audit trail of samples and ensure that the result data from the experiment is written to any necessary sample information (e.g., sample identifier), project information (e.g., project identifier), user information (e.g., user identifier), instrument information (e.g., instrument identifier), etc. and associated with these sample information to create an audit trail of samples.

[0028] [TP386059USPRV1]

[0029] Figure 2 1 is a block diagram of a scientific instrument support module 200 for performing support operations according to various embodiments. The scientific instrument support module 200 may be, for example, a server 124 and / or an instrument computing device 104. The scientific instrument support module 200 may be implemented by circuitry (e.g., including electrical and / or optical components) such as a programmed computing device. The logic of the scientific instrument support module 200 may be included in a single computing device or may be distributed across multiple computing devices that communicate with each other, as appropriate. Figure 4 Examples of computing devices that may implement the scientific instrument support module 200, either individually or in combination, are discussed in conjunction with computing device 400 and are referenced herein. Figure 5 The scientific instrument support system 500 discusses an example of a system of interconnected computing devices, wherein the scientific instrument support module 200 may be implemented across one or more of these computing devices.

[0030] The scientific instrument support module 200 may include a ledger logic 202, a block logic 204, and a report logic 206. As used herein, the term "logic" may include a device that performs a set of operations associated with the logic. For example, any of the logic elements included in the support module 200 may be implemented by one or more computing devices, which are programmed with instructions to cause one or more processing devices of the computing device to perform an associated set of operations. In a specific embodiment, the logic element may include one or more non-transient computer-readable media, which have instructions on them, which, when executed by one or more processing devices in one or more computing devices, cause the one or more computing devices to perform an associated set of operations. As used herein, the term "module" may refer to a collection of one or more logic elements, which together perform functions associated with the module. Different logic elements in the logic elements in the module may take the same form or may take different forms. For example, some logic in the module may be implemented by a programmed general-purpose processing device, while other logic in the module may be implemented by an application-specific integrated circuit (ASIC). As another example, different logic elements in the logic elements in the module may be associated with different instruction sets executed by one or more processing devices. A module may not include all of the logic elements depicted in the relevant figures; for example, when the module is to perform a subset of the operations discussed herein with reference to the module, the module may include a subset of the logic elements depicted in the associated figures.

[0031] The ledger logic 202 may create a data structure ledger for each sample received by the laboratory or for each project (including multiple samples) conducted by the laboratory. In one example, the data structure ledger may be a blockchain ledger, such as a distributed blockchain ledger (peer-to-peer, federated, public, public, permissioned, permissionless, etc.) or a centralized data ledger. In other examples, the data structure ledger may be distributed or centralized and may be based on a variety of ledger technologies and infrastructures, not limited to blockchains, such as IOTA, cache graphs, directed acyclic graphs (DAGs), distributed [TP386059USPRV1]

[0032] A distributed hash table, a Merkle tree, an Adelson-Velsky and Landis (AVL) tree, a B-tree, a stack, a queue, a hybrid combination of different data structures and infrastructures, etc. In some examples, the data structure ledger can be a relational table, a hash table, a linked list, etc. The ledger logic 202 can automatically generate a unique sample identifier for each sample being tracked. The ledger logic 202 receives sample information related to the sample and associates the sample information with a sample identifier or other identifier, for example, using a data structure object.

[0033] The block logic 204 may generate an experiment block in a data structure ledger, the experiment block including experimental data related to the sample. The block logic 204 may receive experimental data corresponding to an experiment performed on the sample by the scientific instrument 108. The block logic 204 generates an experiment data block, which includes a reference to a data structure ledger or a node or block within the data structure ledger. For example, an experiment ledger block may include a hash with a reference to a previous block in the data structure ledger of the block. For example, an experiment block is an entry in a data structure ledger and does not need to be in the form of a block of a blockchain. The experiment block may include, for example, a table entry, a pointer data structure entry, etc. An experiment block may be created using a block object that may be similar to the data structure object discussed above.

[0034] The reporting logic 206 can generate reports from the data structure logic based on queries from users. The query can include a request for data associated with one or more experiments performed on a sample. The reporting logic 206 retrieves relevant data from the data structure ledger and automatically generates a report based on the data.

[0035] The scientific instrument support methods disclosed herein may include interaction with a human user (e.g., via the referenced Figure 5 These interactions may include providing information to the user (e.g., about scientific instruments such as Figure 5 information about the operation of a scientific instrument such as a scientific instrument 510, information about samples being analyzed or other tests or measurements being performed by the scientific instrument, information retrieved from a local or remote database, or other information) or provide the user with the option of inputting commands (e.g., controlling a scientific instrument such as Figure 5 In some embodiments, these interactions may be performed through a graphical user interface (GUI) that includes a display device (e.g., a graphical user interface such as a display device ... Figure 4 410) that provides output to a user and / or prompts a user to provide input (e.g., via a display device 410 discussed herein). Figure 4 Other I / O devices 412 discussed include one or more input devices such as a keyboard, mouse, trackpad, or touch screen). The scientific instrument support system disclosed herein may include any suitable GUI for interacting with a user.

[0036] [TP386059USPRV1]

[0037] Figure 3An example GUI 300 is depicted that can be used to perform some or all of the supporting methods disclosed herein according to various embodiments. As described above, the GUI 300 can be provided in a scientific instrument support system (e.g., as described herein with reference to Figure 5 A computing device (e.g., a scientific instrument support system 500 discussed herein) Figure 4 The computing device 400 discussed herein may include a display device (eg, Figure 4 410) and the user may use any suitable input device (e.g., Figure 4 Any input devices (including those discussed in other I / O devices 412 ) and input techniques (e.g., cursor movement, motion capture, facial recognition, gesture detection, voice recognition, button activation, etc.) interact with GUI 300 .

[0038] GUI 300 may include a data display area 302 , a data analysis area 304 , a scientific instrument control area 306 , and a settings area 308 . Figure 3 The specific number and arrangement of regions depicted in are merely exemplary, and any number and arrangement of regions may be included in GUI 300, including any desired features. FIG. 7A to FIG. 8 A representation of may be included in any appropriate area of ​​GUI 300 (eg, in data display area 302 or data analysis area 304 of GUI 300).

[0039] The data display area 302 may display data generated by a scientific instrument (e.g., Figure 5 For example, the data display area 302 can display experimental data, such as the results of an experiment, sample identifiers of samples, experimental parameters, etc.

[0040] The data analysis region 304 can display the results of the data analysis (e.g., the results of analyzing the data illustrated in the data display region 302 and / or other data). For example, the data analysis region 304 can display a report generated based on the data structure ledger of the sample. In some embodiments, the data display region 302 and the data analysis region 304 can be combined in the GUI 300 (e.g., including the data output from the scientific instrument and some analysis of the data in a common graphic or area).

[0041] The scientific instrument control area 306 may include a user-friendly interface that allows the user to control scientific instruments (e.g., Figure 5 For example, the scientific instrument control area 306 may include control features for chromatographic instruments, spectroscopy instruments, etc.

[0042] The settings area 308 may include options that allow the user to control the features and functions of the GUI 300 (and / or other GUIs), and / or to perform common computing operations with respect to the data display area 302 and the data analysis area 304 (e.g., saving data to a storage device (such as a storage device referred to herein)). Figure 4 (e.g., storing data on a storage device 404 discussed above), sending data to another user, tagging data, etc.). For example, the settings area 308 may include options regarding how to display sample information and / or query input features.

[0043] [TP386059USPRV1]

[0044] As described above, the scientific instrument support module 200 may be implemented by one or more computing devices. Figure 4 4 is a block diagram of a computing device 400 that can perform some or all of the scientific instrument support methods disclosed herein, according to various embodiments. In some embodiments, the scientific instrument support module 200 can be implemented by a single computing device 400 or multiple computing devices 400. In addition, as discussed below, the computing device 400 (or multiple computing devices 400) that implements the scientific instrument support module 200 can be Figure 5 A portion of one or more of a scientific instrument 510, a user local computing device 520, a service local computing device 530, or a remote computing device 540.

[0045] Figure 4 The computing device 400 is illustrated as having multiple components, but any one or more of these components may be omitted or repeated depending on suitability for the application and setting. In some embodiments, some or all of the components included in the computing device 400 may be attached to one or more motherboards and encapsulated in a housing (e.g., including plastic, metal, and / or other materials). In some embodiments, some of these components may be manufactured on a single system on a chip (SoC) (e.g., the SoC may include one or more processing devices 402 and one or more storage devices 404). Additionally, in various embodiments, the computing device 400 may not include Figure 4 One or more of the illustrated components, but may include interface circuitry (not shown) for coupling to one or more components using any suitable interface (e.g., a universal serial bus (USB) interface, a high-definition multimedia interface (HDMI) interface, a controller area network (CAN) interface, a serial peripheral interface (SPI) interface, an Ethernet interface, a wireless interface, or any other suitable interface). For example, computing device 400 may not include display device 410, but may include display device interface circuitry (e.g., a connector and driver circuitry) to which display device 410 may be coupled.

[0046] The computing device 400 may include a processing device 402 (e.g., one or more processing devices). As used herein, the term "processing device" may refer to any device or portion of a device that processes electronic data from registers and / or memory to convert the electronic data into other electronic data that can be stored in registers and / or memory. The processing device 402 (i.e., an electronic processing device or electronic processor) may include one or more digital signal processors (DSPs), application specific integrated circuits (ASICs), central processing units (CPUs), graphics processing units (GPUs), cryptographic processors (specialized processors that execute cryptographic algorithms in hardware), server processors, or any other suitable processing devices.

[0047] The computing device 400 may include a storage device 404 (e.g., one or more storage devices). The storage device 404 may include one or more memory devices, such as random access memory (RAM) (e.g., static RAM (SRAM) devices, magnetic RAM (MRAM) devices, dynamic [TP386059USPRV1]

[0048] In some embodiments, the storage device 404 may include a memory that shares a die with the processing device 402. In such embodiments, the memory may be used as a cache memory and may include, for example, an embedded dynamic random access memory (eDRAM) or a spin-transfer torque magnetic random access memory (STT-MRAM). In some embodiments, the storage device 404 may include a non-transitory computer-readable medium having instructions thereon that, when executed by one or more processing devices (e.g., the processing device 402), cause the computing device 400 to perform any appropriate method or portion of the methods disclosed herein.

[0049] The computing device 400 may include an interface device 406 (e.g., one or more interface devices 406). The interface device 406 may include one or more communication chips, connectors, and / or other hardware and software to manage communications between the computing device 400 and other computing devices. For example, the interface device 406 may include circuitry for managing wireless communications for transmitting data to and from the computing device 400. The term "wireless" and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communication channels, etc. that can transmit data through a non-solid medium using modulated electromagnetic radiation. The term does not imply that the associated device does not contain any wires, although in some embodiments it may not contain any wires. The circuitry included in the interface device 406 for managing wireless communications may implement any of a plurality of wireless standards or protocols, including but not limited to Institute of Electrical and Electronics Engineers (IEEE) standards, including Wi-Fi (IEEE 802.11 series), IEEE 802.16 standards (e.g., IEEE 802.16--2005 amendment), Long Term Evolution (LTE) project, and any amendments, updates, and / or revisions (e.g., Advanced LTE project, Ultra Mobile Broadband (UMB) project (also known as "3GPP2"), etc.). In some embodiments, the circuitry included in the interface device 4006 for managing wireless communications may operate according to a Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA), Evolved HSPA (E-HSPA), or LTE network. In some embodiments, the circuitry included in the interface device 4006 for managing wireless communications may operate in accordance with Enhanced Data GSM Evolution (EDGE), GSM EDGE Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), or Evolved UTRAN (E-UTRAN). In some embodiments, the circuitry included in the interface device 406 for managing wireless communications may operate in accordance with Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Evolved [TP386059USPRV1]

[0050] The interface device 406 may operate with EV-DO and its derivatives, as well as any other wireless protocols designated as 3G, 4G, 5G and higher, etc. In some embodiments, the interface device 406 may include one or more antennas (e.g., one or more antenna arrays) to receive and / or transmit wireless communications.

[0051] In some embodiments, interface device 406 may include a circuit for managing wired communication, such as electrical communication protocol, optical communication protocol or any other suitable communication protocol. For example, interface device 406 may include a circuit supporting communication according to Ethernet technology. In some embodiments, interface device 406 may support both wireless and wired communication, and / or may support multiple wired communication protocols and / or multiple wireless communication protocols. For example, a first group of circuits of interface device 406 may be dedicated to shorter range wireless communication such as Wi-Fi or Bluetooth, and a second group of circuits of interface device 406 may be dedicated to longer range wireless communication such as global positioning system (GPS), EDGE, GPRS, CDMA, WiMAX, LTE, EV-DO, etc. In some embodiments, a first group of circuits of interface device 406 may be dedicated to wireless communication, and a second group of circuits of interface device 406 may be dedicated to wired communication.

[0052] Computing device 400 may include battery / power circuitry 408. Battery / power circuitry 408 may include one or more energy storage devices (e.g., batteries or capacitors) and / or circuitry for coupling components of computing device 400 to an energy source separate from computing device 400 (e.g., AC line power).

[0053] Computing device 400 may include display device 410 (eg, multiple display devices). Display device 410 may include any visual indicator, such as a heads-up display, a computer monitor, a projector, a touch screen display, a liquid crystal display (LCD), a light emitting diode display, or a flat panel display.

[0054] The computing device 400 may include other input / output (I / O) devices 412. For example, the other I / O devices 412 may include one or more audio output devices (e.g., speakers, headphones, earbuds, alarms, etc.), one or more audio input devices (e.g., microphones or microphone arrays), a positioning device (e.g., a GPS device that communicates with a satellite-based system to receive the location of the computing device 400 as is known in the art), an audio codec, a video codec, a printer, a sensor (e.g., a thermocouple or other temperature sensor, a humidity sensor, a pressure sensor, a vibration sensor, an accelerometer, a gyroscope, etc.), an image capture device such as a camera, a keyboard, a cursor control device such as a mouse, a stylus, a trackball, or a touchpad, a barcode reader, a quick response (QR) code reader, or a radio frequency identification (RFID) reader.

[0055] The computing device 400 may have any suitable form factor suitable for its applications and settings, such as a handheld or mobile computing device (e.g., a cellular phone, a smart phone, a mobile Internet device, a tablet computer, a laptop computer, a netbook computer, an ultrabook computer, a personal digital assistant [TP386059USPRV1]

[0056] (PDA), ultra-mobile personal computer, etc.), desktop computing device or server computing device or other networked computing components.

[0057] One or more computing devices implementing any of the scientific instrument support modules or methods disclosed herein may be part of a scientific instrument support system. Figure 5 is a block diagram of an example scientific instrument support system 500 in which some or all of the scientific instrument support methods disclosed herein may be performed, according to various embodiments. The scientific instrument support modules and methods disclosed herein (e.g., Figure 1 Scientific instrument support system 100, Figure 2 The Scientific Instrument Support Module 200 and Figure 6 The method 600) may be implemented by one or more of the scientific instrument 510, the user local computing device 520, the service local computing device 530, or the remote computing device 540 of the scientific instrument support system 500.

[0058] Any of the scientific instrument 510, the user local computing device 520, the service local computing device 530, or the remote computing device 540 may include any of the devices described herein. Figure 4 Any embodiment of computing device 400 discussed herein, and any of scientific instrument 510, user local computing device 520, service local computing device 530, or remote computing device 540 may take the form of any embodiment of computing device 400 discussed herein. Figure 4 Any suitable implementation form of the discussed implementations of computing device 400 .

[0059] Scientific instrument 510, user local computing device 520, service local computing device 530, or remote computing device 540 may each include a processing device 502, a storage device 504, and an interface device 506. Processing device 502 may take any suitable form, including any suitable form herein. Figure 4 The processing device 502 discussed above may be in the form of any processing device in the processing device 402, and the processing device 502 included in different devices of the scientific instrument 510, the user local computing device 520, the service local computing device 530, or the remote computing device 540 may take the same form or different forms. The storage device 504 may take any suitable form, including those described herein. Figure 4The storage device 504 discussed above may be in the form of any storage device, and the storage device 504 included in different devices of the scientific instrument 510, the user local computing device 520, the service local computing device 530, or the remote computing device 540 may take the same form or different forms. The interface device 506 may take any suitable form, including those described herein. Figure 4 The form of any of the interface devices 406 discussed, and the interface devices 506 included in different devices of the scientific instrument 510, the user local computing device 520, the service local computing device 530, or the remote computing device 540 may take the same form or different forms.

[0060] The scientific instrument 510, the user local computing device 520, the service local computing device 530, and the remote computing device 540 can communicate with other elements of the scientific instrument support system 500 via the communication path 508. The communication path 508 can communicatively couple different elements of the elements of the scientific instrument support system 500.

[0061] The interface device 506 of the component is shown in the figure, and can be a wired or wireless communication path (for example, according to the reference Figure 4 The interface device 406 of the computing device 400 may be any of the communication technologies discussed above). Figure 5 The particular scientific instrument support system 500 depicted in FIG. 5 includes a communication path between each pair of devices in the scientific instrument 510, the user local computing device 520, the service local computing device 530, and the remote computing device 540, but this “fully connected” implementation is merely illustrative, and in various embodiments, various communication paths in the communication paths 508 may not be present. For example, in some embodiments, the service local computing device 530 may not have a direct communication path 508 between its interface device 506 and the interface device 506 of the scientific instrument 510, but may communicate with the scientific instrument 510 via the communication path 508 between the service local computing device 530 and the user local computing device 520, and the communication path 508 between the user local computing device 520 and the scientific instrument 510.

[0062] Scientific instrument 510 may include any appropriate scientific instrument, such as a liquid chromatography instrument, a gas chromatography instrument, an ion chromatography instrument, a mass spectrometry instrument, a trace element instrument (e.g., inductively coupled plasma mass spectrometry, inductively coupled plasma optical emission spectroscopy, atomic absorption, etc.), a capillary electrophoresis instrument, a spectroscopic instrument, etc.

[0063] The user-local computing device 520 can be a computing device local to the user of the scientific instrument 510 (e.g., according to any of the embodiments of the computing device 400 discussed herein). In some embodiments, the user-local computing device 520 can also be local to the scientific instrument 510, but this is not necessarily the case; for example, a user-local computing device 520 in a user's home or office can be remote from the scientific instrument 510, but in communication with the scientific instrument so that the user can use the user-local computing device 520 to control and / or access data from the scientific instrument 510. In some embodiments, the user-local computing device 520 can be a laptop, a smart phone, or a tablet device. In some embodiments, the user-local computing device 520 can be a portable computing device. In some embodiments, the user-local computing device 520 can be used for sample creation, including receiving sample information of a sample to be analyzed by a laboratory.

[0064] The service local computing device 530 can be a computing device local to the entity serving the scientific instrument 510 (e.g., according to any of the embodiments of the computing device 400 discussed herein). For example, the service local computing device 530 can be a device local to the manufacturer of the scientific instrument 510 or to a third-party service company. In some embodiments, the service local computing device 530 can communicate with the scientific instrument 510, the user local computing device 520, and / or the remote computing device 540 (e.g., via a direct communication path 508 or via multiple "indirect" communication paths 508, as described above) to receive data regarding the operation of the scientific instrument 510, the user local computing device 520, and / or the remote computing device 540 (e.g., self-test results of the scientific instrument 510, calibration coefficients used by the scientific instrument 510, measurements of sensors associated with the scientific instrument 510 [TP386059USPRV1], etc.). In some embodiments, the service local computing device 530 may communicate with the scientific instrument 510, the user local computing device 520, and / or the remote computing device 540 (e.g., via a direct communication path 508 or via multiple "indirect" communication paths 508, as described above) to send data to the scientific instrument 510, the user local computing device 520, and / or the remote computing device 540 (e.g., to update programming instructions (such as firmware) in the scientific instrument 510 to initiate execution of a test or calibration sequence in the scientific instrument 510, to update programming instructions (such as software) in the user local computing device 520 or the remote computing device 540, etc.). A user of the scientific instrument 510 may utilize the scientific instrument 510 or the user local computing device 520 to communicate with the service local computing device 530 to report problems with the scientific instrument 510 or the user local computing device 520, to request a visit by a technician to improve the operation of the scientific instrument 510, to order consumables or replacement parts associated with the scientific instrument 510, or for other purposes. The service local computing device 530 may generate a data structure ledger and generate reports based on data retrieved from the data structure ledger.

[0065] Remote computing device 540 may be a computing device remote from scientific instrument 510 and / or user local computing device 520 (e.g., according to any of the embodiments of computing device 400 discussed herein). In some embodiments, remote computing device 540 may be included in a data center or other large-scale server environment. In some embodiments, remote computing device 540 may include a network attached storage device (e.g., as part of storage device 504). Remote computing device 5040 may store data generated by scientific instrument 510, perform analysis of data generated by scientific instrument 510 (e.g., according to programming instructions), facilitate communication between user local computing device 520 and scientific instrument 510, and / or facilitate communication between service local computing device 530 and scientific instrument 510. Remote computing device 540 may be used to query the data structure ledger and generate reports based on data retrieved from the data structure ledger.

[0066] In some embodiments, there may be no Figure 5 One or more of the elements of the scientific instrument support system 500 illustrated in FIG. In addition, in some embodiments, there may be Figure 5 The scientific instrument support system 500 may include multiple elements of various elements of the elements of the scientific instrument support system 500. For example, the scientific instrument support system 500 may include multiple user-local computing devices 520 (e.g., different user-local computing devices 520 associated with different users or located in different locations). In another example, the scientific instrument support system 500 may include multiple scientific instruments 510, all of which communicate with a service local computing device 530 and / or a remote computing device 540; in such an embodiment, the service local computing device 530 may monitor these multiple scientific instruments 510, and the service local computing device 530 may cause updates or other information to be "broadcasted" to multiple scientific instruments 510 simultaneously. Scientific Instrument Support System [TP386059USPRV1]

[0067] Different scientific instruments 510 in 500 may be near each other (e.g., in the same room) or far from each other (e.g., on different floors of a building, in different buildings, in different cities, etc.). In some embodiments, the scientific instruments 510 may be connected to an Internet of Things (IoT) stack that allows the scientific instruments 510 to be commanded and controlled through web-based applications, virtual or augmented reality applications, mobile applications, and / or desktop applications. Any of these applications may be accessed by a user operating a user-local computing device 520 that communicates with the scientific instruments 510 through an intermediate remote computing device 540. In some embodiments, the scientific instruments 510 may be sold by a manufacturer along with one or more associated user-local computing devices 520 as part of a local scientific instrument computing unit 512.

[0068] In some embodiments, different scientific instruments in the scientific instruments 510 included in the scientific instrument support system 500 may be different types of scientific instruments 510; for example, one scientific instrument 510 may be a chromatography instrument, while another scientific instrument 510 may be a spectroscopic instrument. In some such embodiments, the remote computing device 540 and / or the user's local computing device 520 may combine data from different types of scientific instruments 510 included in the scientific instrument support system 500.

[0069] Figure 6 is a flow chart of a method 600 of performing support operations according to various embodiments. Although reference may be made to specific embodiments disclosed herein (e.g., Figure 2 The scientific instrument support module 200 discussed in this article is referenced Figure 3 GUI300 discussed, this article references Figure 4 The computing device 400 discussed herein and / or referenced herein Figure 5 The operation of method 600 is illustrated using the scientific instrument support system 500 discussed above, but method 600 can be used in any suitable setting to perform any suitable support operation. Figure 6 The operations are each illustrated once in a particular order, but the operations may be reordered and / or repeated as needed and appropriate (eg, different operations may be performed in parallel where appropriate).

[0070] At 602, method 600 includes automatically generating a sample identifier for a sample. A sample is a substance received at a laboratory for chemical and / or biological analysis. For example, a soil sample may be received for analysis to detect the presence or amount of a nutrient or chemical, a wine sample may be received for analysis to detect the presence or amount of a chemical, etc. The ledger logic 202 may generate one or more graphical user interfaces (GUIs) to facilitate creation of a sample record and for collecting information related to the sample (e.g., when the sample was collected, where the sample was collected, how the sample was collected, etc.). An example of a sample creation GUI generated by the ledger logic 202 is shown in FIG. 7A to 7D Example in. like Fig. 7A , an application screen GUI 704 is illustrated that allows a user to select a sample management application. The application screen GUI 704 includes an open icon 708 that is configured to be selected by, for example, clicking on the open icon 708.

[0071] [TP386059USPRV1]

[0072] In response to receiving a selection of the open icon 708, the ledger logic 202 generates a sample creation GUI 712 (in Figure 7B ). Figure 7B , the sample creation GUI 712 includes a create sample icon 716 and an import sample icon 720. Similar to the open icon 708, the create sample icon 716 and the import sample icon 720 are configured to be selected, for example, by clicking on the create sample icon 716 and the import sample icon 720, respectively. In response to receiving the selection of the create sample icon 716, the ledger logic 202 generates a sample information GUI 724 (in Figure 7C In response to receiving a selection of the import sample icon 720, the ledger logic 202 imports a previously created sample, for example, from a different application or from a previously created sample. Figure 7C The sample information GUI 724 includes one or more fields for receiving sample information. The sample information received via the GUI 724 may include, for example, the sample name, sample type, total weight of the sample, project name of the sample, notes of the sample, user who processed the sample, etc. Fig.7D Another sample information GUI 728 is illustrated that may be generated in response to receiving a selection of the create sample icon 716. The sample information GUI 728 includes one or more fields for receiving sample information. The sample information received via the GUI 728 may include information that may be received on the sample information GUI 724, and also includes, for example, an expiration date for the sample, a safety label for the sample (e.g., a controlled substance hazard health warning), an expiration date for the sample, a sampling technique for the sample, a sampling entity for the sample, and the like.

[0073] like Figure 7C and Fig.7D As shown, the ledger logic 202 automatically generates a sample identifier, for example, in response to receiving a selection to create a sample icon 716. In other examples, the ledger logic 202 generates a sample identifier in response to other triggers (such as other inputs from a user). The sample identifier can be a numeric or alphanumeric identifier. In some examples, in addition to the numeric or alphanumeric identifier and / or encoding the numeric and alphanumeric identifier, a barcode, a QR code, etc. are also generated. In some examples, the sample identifier is a hash value generated randomly or semi-randomly and is unique to the sample. In some examples, the generated barcode, QR code, etc. can be printed on a label, for example, using a label printer, and applied to a sample container containing each sample (or aliquot). A scanning device (e.g., a barcode / QR code scanner) can be used to quickly identify a sample by scanning a barcode, a QR code, etc. attached to a sample container.

[0074] At 604, method 600 includes receiving sample information for a sample. Figure 7C and Fig.7D As shown, the ledger logic 202 may receive sample information via one of the GUIs 724 , 728 .

[0075] At 606, method 600 includes generating a data structure ledger for the sample. Generating a data structure ledger for the sample may include generating a data structure ledger for a project including the sample. The project may include an attached sample. The data structure ledger includes an initial ledger having a sample identifier and sample information [TP386059USPRV1]

[0076] Block (e.g., initial ledger entry). Ledger logic 202 generates a data structure ledger, wherein the initial ledger block serves as, for example, a genesis block of the data structure ledger. In one example, the data structure ledger is a centralized ledger, such that the data structure ledger of the sample can be stored in database 116. In other examples, the data structure ledger is a distributed ledger, such that each instrument computing device 104, database 116, server 124, and / or user device 128 can each store a copy of the data structure ledger. In one example, the sample identifier can be used as an index to retrieve the data structure ledger from database 116. In other examples, a different index (e.g., a hash of the initial block, a hash of the sample identifier, etc.) can be used as an index to retrieve the data structure ledger from database 116. In one example, a genesis block is generated by ledger logic 202 using a data structure object. The data structure object may include a sample identifier field and a sample information field, such that the sample identifier is associated with the sample information in the genesis block. The genesis block is an instance of a data structure object for a particular sample.

[0077] At 608, method 600 includes receiving experimental data related to the sample from scientific instrument 510, such as during the process of the scientific instrument performing the analysis workflow of the sample in real time and / or in response to the scientific instrument completing the analysis workflow of the sample. The experimental data may include a sample identifier. The analysis workflow performed by the scientific instrument on the sample may include, for example, preparing the sample for the experiment (e.g., dissolving the sample in a solution, injecting the solution into another scientific instrument, etc.), completing the analysis or experiment on the sample, etc. The experimental data may be received by block logic 204. The experimental data includes information related to the analysis workflow, such as the analysis method performed, the instrument used, the identity of the user performing the experiment (e.g., one or more user identifiers), the location of the experiment, the time of the experiment, one or more project identifiers, the results of the experiment, the identifier of the scientific instrument, the identifier of the experiment performed on the sample, etc.

[0078] At 610, method 600 includes generating an experiment ledger block in a data structure ledger. The experiment ledger block includes at least some of the received experiment data and / or data generated based on the experiment data. The block logic 204 generates the experiment ledger block using, for example, a block object. The block object may be similar to the data structure object described above, and may include a sample identifier field and an experiment data field so that the sample identifier and other identifiers (e.g., project, user, instrument, etc.) are associated with the experiment data in the experiment ledger block. The experiment ledger block is an instance of a block object. In some examples, the experiment ledger block may be similar to an initial ledger block, where the sample information is replaced by the experiment data. In some examples, if the experiment ledger block has not been previously created, the newly created experiment ledger block may include a pointer to the initial ledger block, or if one or more experiment ledger blocks have been previously created, the newly created experiment ledger block may include a pointer to the last experiment ledger block entered. Therefore, [TP386059USPRV1]

[0079] The experiment ledger block is added to the end of the blockchain, a linked list, etc. In some examples, the newly created experiment ledger block may include a pointer to the initial ledger block, regardless of whether a previous experiment ledger was created. In other examples, different pointer structures may be used in the experiment ledger block to create different forms of data structures. In some examples, method 600 receives experimental data related to a sample from a plurality of scientific instruments. The data structure ledger generated for the sample includes experimental data linked to a sample identifier and sample information. In at least one instance, the data structure ledger includes a blockchain structure.

[0080] In some examples, a separate data structure ledger is created for each sample, as described above. In other examples, all sample data is stored in a single data structure ledger. In these examples, the genesis block may be unique to a laboratory (or an organization running multiple laboratories) or a project. The information of each sample (including sample information and experimental data) may be included in a data structure block or entry of the laboratory's data structure ledger. As discussed above, the data structure ledger may be, for example, a centralized ledger stored in a database 116. In this example, each requesting computing entity (i.e., server 124, user device 128, instrument computing device 104, etc.) accesses the centralized ledger from the database 116 and edits or queries accordingly. In other examples, the data structure ledger may be a decentralized ledger, so that a copy of the data structure ledger of each sample is stored in each (or one or more) of the instrument computing device 104, the database 116, the server 124, and the user device 128. Each computing entity edits a locally stored copy of the data structure ledger to add a corresponding block (or entry) for the sample. All copies of the data structure ledger can be coordinated at regular intervals or on a transaction basis. Each block of the data structure ledger can be encrypted using, for example, a cryptographic hash function and a digital signature. Additionally, each block of the data structure ledger is immutable, so that once created, the block cannot be changed. Compared with other types of data structures, decentralized ledgers have additional advantages such as security and additional audit and control functions because the ledger blocks are immutable. In some examples, data can only be changed by "privileged users". Privileged users can be laboratory administrators or other users with special privileges to calibrate records stored in the laboratory. Corrections performed by privileged users can also be recorded to provide a secure audit trail. The data structure ledger can be exported to other systems, such as LIMS, external data management systems, etc.

[0081] At 612, method 600 includes receiving a request for a report corresponding to the sample. Report logic 206 may receive the request for the report via a graphical user interface for querying database 116. The request may be in the form of, for example, a structured query language (SQL) query, a NoSQL query, etc. In some examples, the request may be received from a smartphone application running on a mobile phone (e.g., user device 128) [TP386059USPRV1]

[0082] Receive a request for a report. In some embodiments, a report may be requested based on other criteria. For example, a request (e.g., a second request) may be received corresponding to a scientific instrument, an experiment, a user, a laboratory, a group of instruments, a group of users, etc.

[0083] At 614, method 600 includes querying the data structure ledger to receive ledger data corresponding to the request. Report logic 206 queries database 116 based on the request for the report to retrieve ledger data corresponding to the request. The ledger data includes relevant data from the data structure ledger for generating the requested report. The query may specify one or more sample identifiers to retrieve ledger data corresponding to the one or more sample identifiers. In some examples, the query may be for multiple data structure ledgers associated with multiple samples. Report logic 206 may parse data from multiple data structure ledgers with data corresponding to the queried standard (e.g., scientific instrument, experiment, etc.). For example, data may be parsed based on multiple blocks including identifiers of standards (e.g., identifiers of scientific instruments, identifiers of experiments, etc.).

[0084] At 616, method 600 includes generating a report based on the ledger data received in response to the query. Report logic 206 generates a report, such as a predefined template. The report can be generated based on data of a project including multiple samples. Reports can also be generated separately for each sample or separately for each experiment. Since the experimental data is associated with the identifier, the report can be easily generated by using any of the identifiers (e.g., sample identifier, project identifier, user identifier, instrument identifier, etc.). Figure 8 An example of a report 800 generated by the reporting logic 206 is illustrated. The report 800 relates to the quantity tracking of the sample, which relates to the distribution of the sample between aliquots. In some examples, the report can be generated and displayed on the graphical user interface of the smart phone application discussed above.

[0085] The following paragraphs provide various examples of the embodiments disclosed herein.

[0086] Embodiment 1 is a method, the method comprising: generating a sample identifier for a sample using a processing device; receiving sample information of the sample using the processing device; and receiving experimental data related to the sample from a plurality of scientific instruments using the processing device; and generating a data structure ledger for the sample using the processing device, the data structure ledger including the experimental data associated with the sample identifier and the sample information. The method also comprises: receiving a request for a report corresponding to the sample; querying the data structure ledger to receive ledger data corresponding to the request; and generating the report based on the ledger data received in response to the query.

[0087] [TP386059USPRV1]

[0088] Embodiment 2 may include the subject matter of Embodiment 1, and may further provide that the data structure ledger is a distributed ledger using a blockchain structure.

[0089] Embodiment 3 may include the subject matter described in embodiment 1 or 2, and may further provide that the sample information includes one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technology used to retrieve the sample, and an image of the sample.

[0090] Embodiment 4 may include the subject matter of embodiments 1 to 3, and may further provide that the experimental data includes one or more selected from the group consisting of: the weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, an identifier of an experiment performed on the sample.

[0091] Embodiment 5 may include the subject matter of Embodiments 1 to 4, and may further provide that the report is generated on a smartphone application.

[0092] Embodiment 6 may include the subject matter of embodiments 1 to 5, and may further provide that the method includes: generating a barcode including the sample identifier; and providing the barcode to a label printer. Printing a label including the barcode using the label printer for use with the sample.

[0093] Embodiment 7 may include the subject matter of Embodiments 1 to 6, and may further provide that the method comprises: after generating the data structure ledger, receiving sample data corresponding to changes in the sample; and in response to receiving the sample data, appending a timestamped sample data block to the data structure ledger.

[0094] Embodiment 8 is a scientific instrument support system, the scientific instrument support system comprising one or a group of processing devices, the one or a group of processing devices being configured to: generate a sample identifier for a sample; receive sample information of the sample; and generate a data structure ledger for the sample. The data structure ledger includes an initial ledger block having the sample identifier and the sample information. The one or a group of processing devices are also configured to generate an experimental ledger block in the data structure ledger. The experimental ledger block includes experimental data received from a scientific instrument. The one or a group of processing devices are also configured to: receive a request for a report corresponding to the sample; query the data structure ledger to receive ledger data corresponding to the request; and generate the report based on the ledger data received in response to the query.

[0095] Embodiment 9 may include the subject matter of Embodiment 8, and may further provide that the data structure ledger is a distributed ledger using a blockchain structure.

[0096] [TP386059USPRV1]

[0097] Embodiment 10 may include the subject matter described in embodiment 8 or 9, and may further provide that the sample information includes one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technique used to retrieve the sample, and an image of the sample.

[0098] Embodiment 11 may include the subject matter described in embodiments 8 to 10, and may further provide that the experimental data includes one or more selected from the group consisting of: the weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, an identifier of an experiment performed on the sample.

[0099] Embodiment 12 may include the subject matter of Embodiments 8 to 11, and may further provide that the report is generated on a smartphone application.

[0100] Embodiment 13 may include the subject matter of embodiments 8 to 12, and may further provide that the one or group of processing devices is configured to: generate a barcode including the sample identifier; and provide the barcode to a label printer. Use the label printer to print a label including the barcode for use with the sample.

[0101] Embodiment 14 may include the subject matter of Embodiments 8-13, and may further provide that the one or group of processing devices are further configured to: receive a second request for a second report corresponding to the scientific instrument; and query a plurality of data structure ledgers corresponding to a plurality of samples to receive second ledger data corresponding to the scientific instrument. The second ledger data includes data from a plurality of blocks of the plurality of data structure ledgers, the plurality of blocks including an identifier of the scientific instrument. The one or group of processing devices is further configured to generate the second report based on the second ledger data received in response to the query.

[0102] Embodiment 15 is a scientific instrument support device, the scientific instrument support device comprising: a first logic for generating a sample identifier for a sample; a second logic for receiving sample information of the sample; and a third logic for generating a data structure ledger for the sample. The data structure ledger comprises an initial ledger block having the sample identifier and the sample information. The scientific instrument support device further comprises a fourth logic for generating a timestamped experimental ledger block in the data structure ledger. The experimental ledger block comprises experimental data received from a plurality of scientific instruments. The scientific instrument support device further comprises: a fifth logic for receiving a request for a report corresponding to the sample; and a fifth logic for querying the data structure ledger to receive a report corresponding to the [TP386059USPRV1]

[0103] sixth logic for requesting ledger data; and seventh logic for generating the report based on the ledger data received in response to the query.

[0104] Embodiment 16 may include the subject matter of Embodiment 15, and may further provide that the data structure ledger is a distributed ledger using a blockchain structure.

[0105] Embodiment 17 may include the subject matter of Embodiment 15 or 16, and may further provide that the sample information includes one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technique used to retrieve the sample, and an image of the sample.

[0106] Embodiment 18 may include the subject matter of embodiments 15 to 17, and may further provide that the experimental data includes one or more selected from the group consisting of: the weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, an identifier of an experiment performed on the sample.

[0107] Embodiment 19 may include the subject matter of Embodiments 15 to 18, and may further provide that the report is generated on a smartphone application.

[0108] Embodiment 20 may include the subject matter of embodiments 15 to 19, and may further provide that the one or group of processing devices are configured to: generate a barcode including the sample identifier; and provide the barcode to a label printer. Use the label printer to print a label including the barcode for use with the sample.

Claims

1. A method for scientific instrument support, comprising: generating a sample identifier for the sample using a processing device; receiving sample information of the sample using the processing device; receiving, using the processing device, experimental data associated with the sample from a plurality of scientific instruments; generating, using the processing device, a data structure ledger for the sample, the data structure ledger including the experimental data associated with the sample identifier and the sample information; receiving a request for a report corresponding to the sample; querying the data structure ledger to receive ledger data corresponding to the request; as well as The report is generated based on the ledger data received in response to the query.

2. The method of claim 1, wherein the data structure ledger is a distributed ledger using a blockchain structure.

3. The method of claim 1, wherein the sample information comprises one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technique used to retrieve the sample, and an image of the sample.

4. A method according to claim 1, wherein the experimental data includes one or more selected from the group consisting of: the weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, and an identifier of an experiment performed on the sample.

5. The method of claim 1, wherein the report is generated on a smartphone application.

6. The method according to claim 1, further comprising: generating a barcode representing the sample identifier; [TP386059USPRV1] The barcode is provided to a label printer, wherein a label including the barcode is printed using the label printer for use with the sample.

7. The method according to claim 1, further comprising: After generating the data structure ledger, receiving sample data corresponding to changes in the sample; as well as In response to receiving the sample data, appending a timestamped chunk of the sample data to the data structure ledger.

8. A scientific instrument support system comprising: A processing device or a group of processing devices, the processing device or the group of processing devices being configured to: generating a sample identifier for the sample; receiving sample information of the sample; generating a data structure ledger for the sample, the data structure ledger comprising an initial ledger block having the sample identifier and the sample information; generating an experiment ledger block in the data structure ledger, the experiment ledger block including the experiment data received from the scientific instrument; receiving a request for a report corresponding to the sample; querying the data structure ledger to receive ledger data corresponding to the request; as well as The report is generated based on the ledger data received in response to the query.

9. The scientific instrument support system according to claim 8, wherein the data structure ledger is a distributed ledger using a blockchain structure.

10. The scientific instrument support system of claim 8, wherein the sample information comprises one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technique used to retrieve the sample, and an image of the sample.

11. The scientific instrument support system of claim 8, wherein the experimental data comprises one or more selected from the group consisting of: the weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, an identifier of an experiment performed on the sample.

12. The scientific instrument support system of claim 8, wherein the report is generated on a smartphone application.

13. The scientific instrument support system of claim 8, wherein the one or a group of processing devices are further configured to: generating a barcode including the sample identifier; and The barcode is provided to a label printer, wherein a label including the barcode is printed using the label printer for use with the sample.

14. The scientific instrument support system of claim 8, wherein the one or a group of processing devices are further configured to: receiving a second request for a second report corresponding to the scientific instrument; querying a plurality of data structure ledgers corresponding to a plurality of samples to receive second ledger data corresponding to the scientific instrument, wherein the second ledger data comprises data from a plurality of blocks from the plurality of data structure ledgers, the plurality of blocks comprising an identifier of the scientific instrument; and The second report is generated based on the second ledger data received in response to the query.

15. A scientific instrument support device comprising: first logic for generating a sample identifier for the sample; second logic for receiving sample information for the sample; third logic for generating a data structure ledger for the sample, the data structure ledger comprising an initial ledger block having the sample identifier and the sample information; fourth logic for generating a time-stamped experiment ledger block in the data structure ledger, the experiment ledger block comprising experiment data received from a plurality of scientific instruments; fifth logic for receiving a request for a report corresponding to the sample; sixth logic for querying the data structure ledger to receive ledger data corresponding to the request; and Seventh logic is provided for generating the report based on the ledger data received in response to the query.

16. The scientific instrument support device of claim 15, wherein the data structure ledger is a distributed ledger.

17. The scientific instrument support device of claim 15, wherein the sample information comprises one or more selected from the group consisting of: the time when the sample was collected, the date when the sample was collected, the weather at the time and location when the sample was collected, the coordinates of the location when the sample was collected, the sampling technique used to retrieve the sample, and an image of the sample.

18. The scientific instrument support device of claim 15, wherein the experimental data comprises one or more selected from the group consisting of: weight of the sample, one or more user identifiers, one or more project identifiers, experimental results, an identifier of a scientific instrument, an identifier of an experiment performed on the sample.

19. The scientific instrument support device of claim 15, wherein the report is generated on a smartphone application.

20. The scientific instrument support device according to claim 15, wherein the one or a group of processing devices are further configured to: generating a barcode including the sample identifier; and The barcode is provided to a label printer, wherein a label including the barcode is printed using the label printer for use with the sample.

Images