Embryo data management system

Abstract

The embodiment of the invention discloses an embryo data management system. According to the system, changed embryo data in a butted embryo incubator is acquired through each data acquisition module in a data acquisition layer, and the acquired embryo data is transmitted to an interface adaptation layer; responding to the received embryo data through an interface adaptation layer, mapping the embryo data to a target data structure according to a field mapping relation corresponding to the embryo incubator, and transmitting the embryo data represented by the target data structure to a data management layer; storing and managing the received embryo data through a data management layer; wherein the field mapping relationship represents a mapping relationship between each field in the target data structure and each field in an original data structure corresponding to the embryo incubator; the target data structure is a preset reference data structure or is obtained by newly adding fields in the reference data structure according to the original data structure. According to the technical scheme provided by the embodiment of the invention, efficient management of embryo data can be realized.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of data processing technology, and in particular to an embryo data management system. Background Art

[0002] The hospital's assisted reproductive department usually has multiple embryo incubators for cultivating and observing embryos.

[0003] The embryo data generated during the process of embryo culture and observation cannot currently be managed efficiently, and this problem needs to be urgently addressed. Summary of the Invention

[0004] An embodiment of the present invention provides an embryo data management system to achieve efficient management of embryo data.

[0005] According to one aspect of the present invention, there is provided an embryo data management system, which may include:

[0006] Data acquisition layer, interface adaptation layer and data management layer; wherein the data acquisition layer may include at least two data acquisition modules, each data acquisition module is connected to a different embryo incubator;

[0007] For each data acquisition module and the embryo incubator connected to the data acquisition module, the data acquisition module is used to collect the changed embryo data in the embryo incubator and transmit the collected embryo data to the interface adaptation layer;

[0008] The interface adaptation layer is used to respond to the received embryo data, map the embryo data to the target data structure according to the field mapping relationship corresponding to the embryo incubator, and transmit the embryo data represented by the target data structure to the data management layer;

[0009] Data management layer, used to store and manage received embryo data;

[0010] The field mapping relationship may represent the mapping relationship between each field in the target data structure and each field in the original data structure corresponding to the embryo incubator;

[0011] The target data structure is a preset reference data structure, or is obtained by adding fields to the reference data structure based on the original data structure.

[0012] Optionally, the data acquisition module includes a data acquisition unit and a data transmission unit; wherein,

[0013] a data acquisition unit, configured to determine and acquire changed embryo data in the embryo incubator in response to an embryo data change event monitored for the embryo incubator;

[0014] The data transmission unit is used to transmit the collected embryo data to the interface adapter layer.

[0015] On this basis, an optional data acquisition unit is specifically used to:

[0016] In response to the embryo data change event monitored for the embryo incubator, the changed embryo data in the embryo incubator is determined according to the description information of the previous data, and the embryo data is collected, wherein the previous data is the embryo data collected for the embryo incubator last time.

[0017] On this basis, optionally, the description information includes a timestamp.

[0018] Another optional data transmission unit is specifically configured to:

[0019] The collected embryo data is integrity checked, and if the integrity check passes, the embryo data is transmitted to the interface adaptation layer.

[0020] Optionally, the above embryo data management system further includes: an application layer; wherein,

[0021] The application layer is used to respond to the embryo data query instruction, determine the embryo data to be queried from the stored embryo data, and display the queried embryo data.

[0022] On this basis, optionally, the embryo data includes embryo images, and an image capturing device is provided in the embryo incubator. A plurality of embryos are placed in the embryo incubator, and the embryo images can be obtained by capturing each embryo separately through the image capturing device.

[0023] The application layer includes an embryo identification acquisition module, an embryo image determination module, and an embryo image display module; wherein,

[0024] An embryo identification acquisition module is used to respond to an embryo data query instruction, determine a target embryo to be queried from each embryo, and obtain the embryo identification of the target embryo;

[0025] An embryo image determination module is used to determine the embryo image belonging to the target embryo from the stored embryo images according to the embryo identifier;

[0026] The embryo image display module is used to display the queried embryo images.

[0027] On this basis, optionally, the image capture device is a zoom image capture device, and the controller in the embryo incubator controls the image capture device to first capture each embryo in sequence based on one focal length, and then capture each embryo in sequence based on another focal length, and after completing the capture at each focal length, perform another round of capture after a preset time interval;

[0028] The embryo image determination module includes an embryo image cluster obtaining unit and an embryo image determination unit; wherein,

[0029] An embryo image cluster obtaining unit is used to cluster each embryo image according to the shooting time points corresponding to each stored embryo image to obtain a plurality of embryo image clusters;

[0030] an embryo image determining unit, configured to determine, for each embryo image cluster in the plurality of embryo image clusters, an embryo image belonging to a target embryo from the embryo images in the embryo image cluster according to the embryo identifier, so as to obtain a plurality of focal plane image sequences;

[0031] The embryo images belonging to the same focal plane image sequence are embryo images captured at the same focal length, and the number of embryo images in the focal plane image sequence is the same as the number of embryo image clusters;

[0032] Correspondingly, the embryo image display module is specifically configured to play the embryo images in each focal plane image sequence found based on the focal length or the embryo image cluster.

[0033] On this basis, the optional embryo image display module is also used to:

[0034] Before playing the embryo images in each focal plane image sequence found, preloading a portion of the embryo images in each focal plane image sequence;

[0035] The time point of shooting the preloaded embryo image is earlier than the time point of shooting the non-preloaded embryo image.

[0036] Based on any of the above-mentioned data embryo management systems, optionally, the benchmark data structure is a nested data structure, which includes at least two layers of the embryo incubator layer, embryo belonging object layer, embryo culture record layer, embryo layer and embryo image layer that are nested in sequence.

[0037] The technical solution of the embodiment of the present invention, through each data acquisition module in the data acquisition layer, respectively collects the embryo data of the changes in the docked embryo incubator, and transmits the collected embryo data to the interface adaptation layer; then, through the interface adaptation layer, in response to the received embryo data, and according to the corresponding field mapping relationship, the embryo data is mapped to the target data structure, and then the embryo data represented by the target data structure is transmitted to the data management layer, and the target data structure is obtained based on the preset reference data structure; thus, the received embryo data can be stored and managed through the data management layer. The above technical solution, through the reference data structure, realizes unified access to the embryo data of different embryo incubators, and then realizes unified storage and management of all embryo data, thereby realizing efficient management of embryo data.

[0038] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0040] Figure 1 This is a structural block diagram of an embryo data management system provided according to an embodiment of the present invention;

[0041] Figure 2 is a structural block diagram of another embryo data management system provided according to an embodiment of the present invention;

[0042] Figure 3 This is a structural block diagram of another embryo data management system provided according to an embodiment of the present invention;

[0043] Figure 4 This is a structural block diagram of an optional example of another embryo data management system provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0044] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0045] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. The situations of "target", "original", etc. are similar and will not be repeated here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0046] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solution of the present invention all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken with respect to user personal information to prevent unauthorized access to user personal information data and maintain the security of user personal information and network security.

[0047] Before introducing the embodiment of the present invention, the specific reasons why efficient management of embryo data cannot be achieved at present are first exemplified to better understand how the embodiment of the present invention efficiently manages embryo data.

[0048] For example, the multiple embryo incubators in the assisted reproductive department are independent of each other. Relevant personnel need to learn the embryo data management systems corresponding to different embryo incubators, and then manage the corresponding embryo data through each embryo data management system. Obviously, this leads to inefficient management of embryo data, which needs to be solved urgently.

[0049] Figure 1 This is a structural block diagram of an embryo data management system provided by an embodiment of the present invention. This embodiment is applicable to the situation where embryo data of different embryo incubators are centrally managed.

[0050] See also Figure 1 The embryo data management system according to the embodiment of the present invention includes: a data acquisition layer 10, an interface adaptation layer 20 and a data management layer 30; wherein the data acquisition layer 10 includes at least two data acquisition modules 101, each data acquisition module 101 is connected to a different embryo incubator;

[0051] For each data acquisition module 101 and the embryo incubator to which the data acquisition module 101 is connected, the data acquisition module 101 is used to collect the changed embryo data in the embryo incubator and transmit the collected embryo data to the interface adaptation layer 20;

[0052] The interface adaptation layer 20 is configured to, in response to the received embryo data, map the embryo data to a target data structure according to a field mapping relationship corresponding to the embryo incubator, and transmit the embryo data represented by the target data structure to the data management layer 30, wherein the field mapping relationship represents a mapping relationship between each field in the target data structure and each field in the original data structure corresponding to the embryo incubator, and the target data structure is a preset reference data structure or is obtained by adding fields to the reference data structure based on the original data structure;

[0053] The data management layer 30 is used to store and manage the received embryo data.

[0054] Among them, the data acquisition layer 10 can be understood as the layer in the embryo data management system used to collect embryo data. This layer includes two or more data acquisition modules 101, and each data acquisition module 101 is connected to a different embryo incubator. The type of the embryo incubator can be a basic incubator, a time difference incubator, or a rotary / ultrasonic assisted incubator, etc. This is related to the actual situation and is not specifically limited here.

[0055] For each data acquisition module 101 and the embryo incubator connected to the data acquisition module 101, the data acquisition module 101 can collect the changed embryo data in the embryo incubator, which can be, for example, newly added embryo data, deleted embryo data, or modified embryo data, and then transmit the collected embryo data to the interface adaptation layer 20.

[0056] The interface adaptation layer 20 can be understood as a layer in the embryo data management system used to adapt to each embryo incubator. Specifically, it can be a layer used to adapt the original data structure corresponding to each embryo incubator. The original data structure can be understood as a data structure used to represent the embryo data in the corresponding embryo incubator, that is, the embryo data in the embryo incubator can be represented based on this data structure.

[0057] Taking into account that different embryo incubators, especially embryo incubators developed by different manufacturers and / or different models developed by the same manufacturer, may have corresponding original data structures that are significantly different, in order to effectively connect each embryo incubator, in an embodiment of the present invention, a reference data structure is pre-set, and then a target data structure is obtained based on the reference data structure. For example, corresponding target data structures can be obtained for different original data structures, thereby ensuring one-to-one correspondence; each original data structure can also be mapped to the same target data structure, thereby simplifying the operation; and so on, which are not specifically limited here.

[0058] For example, in the case where different original data structures correspond to corresponding target data structures, for each original data structure, if each field in the original data structure exists in the baseline data structure, the baseline data structure can be directly used as the corresponding target data structure; if a field in the original data structure does not exist in the baseline data structure, the field can be added to the baseline data structure to obtain the corresponding target data structure. For example, through the Schema extension mechanism, the field can be added to the baseline data structure in the form of a key-value pair, thereby achieving a balance between compatibility and scalability.

[0059] As another example, in the case where different original data structures correspond to the same target data structure, the fields that exist in any original data structure but do not exist in the baseline data structure can be added to the baseline data structure to obtain a target data structure corresponding to all original data structures. In this case, the target data structure includes all fields involved in each original data structure.

[0060] Furthermore, for each original data structure, after obtaining the corresponding target data structure, each field in the original data structure may be mapped to the target data structure to obtain a field mapping relationship.

[0061] In other words, every time a new embryo incubator is docked, the corresponding target data structure can be configured based on the baseline data structure, and then the corresponding field mapping relationship can be configured. In addition, the remaining adaptation logic is applicable to each embryo incubator, thereby reducing the development complexity of the adaptation of the new embryo incubator and having better compatibility.

[0062] On this basis, through the interface adaptation layer 20, in response to the received embryo data, the embryo data can be mapped to the target data structure according to the field mapping relationship corresponding to the embryo incubator to which the embryo data belongs, for example, mapping is performed based on a standardized mapping engine, and then the embryo data represented by the target data structure is transmitted to the data management layer 30 for management.

[0063] Thus, the embryo data received from each embryo incubator can be uniformly stored and managed through the data management layer 30. For example, a centralized database can be used to store the embryo data and manage the stored embryo data. The embryo data can be divided into structured data and unstructured data.

[0064] The technical solution of the embodiment of the present invention, through each data acquisition module in the data acquisition layer, respectively collects the embryo data of the changes in the docked embryo incubator, and transmits the collected embryo data to the interface adaptation layer; then, through the interface adaptation layer, in response to the received embryo data, and according to the corresponding field mapping relationship, the embryo data is mapped to the target data structure, and then the embryo data represented by the target data structure is transmitted to the data management layer, and the target data structure is obtained based on the preset reference data structure; thus, the received embryo data can be stored and managed through the data management layer. The above technical solution, through the reference data structure, realizes unified access to the embryo data of different embryo incubators, and then realizes unified storage and management of all embryo data, thereby realizing efficient management of embryo data.

[0065] An optional technical solution is that the above-mentioned reference data structure can be a nested data structure, which can include at least two layers of the embryo incubator layer, embryo belonging object layer, embryo culture record layer, embryo layer and embryo image layer nested in sequence.

[0066] The embryo incubator layer may include fields related to the embryo incubator, such as at least one of a manufacturer identifier, a hardware version, and a data protocol type.

[0067] The embryo to which the object belongs can be understood as the object to which the embryo belongs. Therefore, the embryo to which the object layer can also be called the patient layer, which contains fields authorized by the patient to use, that is, the patient authorizes the above-mentioned embryo data management system to use the embryo data under this field. This field can be an anonymous identifier, for example.

[0068] The embryo culture record layer may include fields related to embryo culture records, such as at least one of incubator environment parameters, embryo culture position parameters, and embryo culture operation timeline events.

[0069] The embryo layer may include fields related to the embryo itself, for example, at least one of an embryo development stage mark and a multi-focal plane image index.

[0070] The embryo incubator is equipped with an image capture device that captures images of the embryos during their development. The embryo image layer may include fields related to the embryo images, such as a timestamp, pixel resolution, and image hierarchy.

[0071] The above technical solution realizes hierarchical storage of embryo data by designing a nested benchmark data structure.

[0072] Figure 21 is a block diagram of another embryo data management system provided by an embodiment of the present invention. This embodiment is optimized based on the above-mentioned technical solutions. In this embodiment, optionally, the data acquisition module may include a data acquisition unit and a data transmission unit; wherein the data acquisition unit is used to determine and collect the embryo data changed in the embryo incubator in response to the embryo data change event monitored for the embryo incubator; and the data transmission unit is used to transmit the collected embryo data to the interface adaptation layer. The explanation of the terms that are the same as or corresponding to the above-mentioned embodiments will not be repeated here.

[0073] For details, see Figure 2 The embryo data management system described in this embodiment includes: a data acquisition layer 10, an interface adaptation layer 20 and a data management layer 30; wherein the data acquisition layer 10 includes at least two data acquisition modules 101, the data acquisition module 101 includes a data acquisition unit 1011 and a data transmission unit 1012, and each data acquisition module 101 is connected to a different embryo incubator;

[0074] For each data acquisition module 101 and the embryo incubator connected to the data acquisition module 101, the data acquisition unit 1011 in the data acquisition module 101 is used to determine and acquire the changed embryo data in the embryo incubator in response to the embryo data change event monitored for the embryo incubator;

[0075] The data transmission unit 1012 in the data acquisition module 101 is used to transmit the collected embryo data to the interface adaptation layer 20;

[0076] The interface adaptation layer 20 is configured to, in response to the received embryo data, map the embryo data to a target data structure according to a field mapping relationship corresponding to the embryo incubator, and transmit the embryo data represented by the target data structure to the data management layer 30, wherein the field mapping relationship represents a mapping relationship between each field in the target data structure and each field in the original data structure corresponding to the embryo incubator, and the target data structure is a preset reference data structure or is obtained by adding fields to the reference data structure based on the original data structure;

[0077] The data management layer 30 is used to store and manage the received embryo data.

[0078] The data acquisition module 101 includes a data acquisition unit 1011 and a data transmission unit 1012. Therefore, the data acquisition unit 1011 can monitor whether there are embryo data change events in the embryo incubator. This monitoring process can be implemented through methods such as an application programming interface (API), file transfer protocol (FTP), or a software development kit (SDK). Then, in response to the monitored embryo data change events, the changed embryo data in the embryo incubator is determined and collected. Furthermore, the collected embryo data is transmitted to the interface adaptation layer 20 through the data transmission unit 1012.

[0079] The technical solution of the embodiment of the present invention monitors embryo data change events in the embryo incubator through a data acquisition unit, thereby realizing the automatic collection of embryo data in the embryo incubator; further, through a data transmission unit, the automatic transmission of the collected embryo data is realized, so that the embryo data can be transmitted to the interface adaptation layer in a timely manner for processing.

[0080] An optional technical solution, a data acquisition unit, is specifically used to:

[0081] In response to the embryo data change event monitored for the embryo incubator, the changed embryo data in the embryo incubator is determined according to the description information of the previous data, and the embryo data is collected, wherein the previous data is the embryo data collected for the embryo incubator last time.

[0082] Among them, compared with the embryo data X that needs to be collected this time, the previous data can be understood as the embryo data collected for the embryo incubator last time. The descriptive information can be understood as the information used to describe the previous data. Then, based on the descriptive information, the embryo data X can be determined, that is, the embryo data in the embryo incubator that has changed compared to the last collection can be determined. Exemplarily, the descriptive information can be a timestamp, and the embryo data after the timestamp is the embryo data X; more exemplarily, the previous data may include the embryo image collected last time, and the descriptive information can be the image identifier of the embryo image, and the image identifier is incremented in sequence. The embryo image corresponding to the image identifier that is greater than the image identifier is the embryo data X; of course, it can also be other descriptive information, and then the embryo data X is determined in a corresponding manner, which is not specifically limited here.

[0083] The above technical solution realizes the accurate determination of embryo data X (ie, the changed embryo data) through the description information of the previous data, thereby realizing the accurate collection of the embryo data X.

[0084] Another optional technical solution, the data transmission unit, is specifically used to:

[0085] The collected embryo data is integrity checked, and if the integrity check passes, the embryo data is transmitted to the interface adaptation layer.

[0086] The above technical solution takes into account that the embryo data may be damaged during the transmission process. The data transmission unit first performs an integrity check on the collected embryo data, and if it passes, the embryo data is transmitted to the interface adaptation layer, thereby ensuring the integrity of the subsequently stored embryo data.

[0087] Figure 3 1 is a block diagram of another embryo data management system provided by an embodiment of the present invention. This embodiment is optimized based on the above-mentioned technical solutions. In this embodiment, optionally, the above-mentioned embryo data management system also includes: an application layer; wherein the application layer is used to determine the embryo data to be queried from the stored embryo data in response to the embryo data query instruction, and display the queried embryo data. Among them, the explanation of the terms identical or corresponding to the above-mentioned embodiments is not repeated here.

[0088] For details, see Figure 3 The embryo data management system described in this embodiment includes: a data acquisition layer 10, an interface adaptation layer 20, a data management layer 30 and an application layer 40; wherein the data acquisition layer 10 may include at least two data acquisition modules 101, each data acquisition module 101 is connected to a different embryo incubator;

[0089] For each data acquisition module 101 and the embryo incubator to which the data acquisition module 101 is connected, the data acquisition module 101 is used to collect the changed embryo data in the embryo incubator and transmit the collected embryo data to the interface adaptation layer 20;

[0090] The interface adaptation layer 20 is configured to, in response to the received embryo data, map the embryo data to a target data structure according to a field mapping relationship corresponding to the embryo incubator, and transmit the embryo data represented by the target data structure to the data management layer 30, wherein the field mapping relationship represents a mapping relationship between each field in the target data structure and each field in the original data structure corresponding to the embryo incubator, and the target data structure is a preset reference data structure or is obtained by adding fields to the reference data structure based on the original data structure;

[0091] A data management layer 30, for storing and managing received embryo data;

[0092] The application layer 40 is used to respond to the embryo data query instruction, determine the embryo data to be queried from the stored embryo data, and display the queried embryo data.

[0093] The application layer 40 can be understood as a layer for providing applications related to the stored embryo data. The application can be, for example, at least one of a query application, a display application, and various prediction applications. This is related to actual circumstances and is not specifically limited here. Optionally, the application layer can also be referred to as an application service layer.

[0094] The technical solution of the embodiment of the present invention provides various applications for relevant personnel through the application layer, thereby facilitating relevant personnel to better apply the embryo data stored in the data management system.

[0095] In an optional technical solution, the embryo data includes embryo images, an image capturing device is provided in an embryo incubator, a plurality of embryos are placed in the embryo incubator, and the embryo images are obtained by capturing each embryo separately using the image capturing device;

[0096] The application layer includes an embryo identification acquisition module, an embryo image determination module, and an embryo image display module; wherein,

[0097] An embryo identification acquisition module is used to respond to an embryo data query instruction, determine a target embryo to be queried from each embryo, and obtain the embryo identification of the target embryo;

[0098] An embryo image determination module is used to determine the embryo image belonging to the target embryo from the stored embryo images according to the embryo identifier;

[0099] The embryo image display module is used to display the queried embryo images.

[0100] The embryo incubator is equipped with an image capture device that can be used to capture embryos during their development to generate embryo images. Furthermore, since multiple embryos are placed in the embryo incubator, the captured embryo images are images of multiple embryos, and further, the data management layer stores images of multiple embryos.

[0101] Further, the application layer includes an embryo identification acquisition module, an embryo image determination module, and an embryo image display module. On this basis, by the embryo identification acquisition module, in response to an embryo data query instruction, which can be understood as an instruction for querying the embryo image of a certain embryo, the target embryo to be queried is determined from each embryo, and the embryo identification of the target embryo is obtained. Then, by changing the embryo image determination module, according to the obtained embryo identification, the embryo image belonging to the target embryo is determined from each stored embryo image, and then by the embryo image display module, the queried embryo image is displayed, thereby achieving accurate query and display of the embryo image for the target embryo.

[0102] On this basis, optionally, the image capture device is a zoom image capture device, and the controller in the embryo incubator controls the image capture device to first capture each embryo in sequence based on one focal length, and then capture each embryo in sequence based on another focal length, and after completing the capture at each focal length, perform another round of capture after a preset time interval;

[0103] The embryo image determination module includes an embryo image cluster obtaining unit and an embryo image determination unit; wherein,

[0104] An embryo image cluster obtaining unit is used to cluster each embryo image according to the shooting time points corresponding to each stored embryo image to obtain a plurality of embryo image clusters;

[0105] an embryo image determining unit, configured to determine, for each embryo image cluster in the plurality of embryo image clusters, an embryo image belonging to a target embryo from the embryo images in the embryo image cluster according to the embryo identifier, so as to obtain a plurality of focal plane image sequences;

[0106] The embryo images belonging to the same focal plane image sequence are embryo images captured at the same focal length, and the number of embryo images in the focal plane image sequence is the same as the number of embryo image clusters;

[0107] Correspondingly, the embryo image display module is specifically configured to play the embryo images in each focal plane image sequence found based on the focal length or the embryo image cluster.

[0108] Among them, before introducing the above-mentioned technical solution, its application scenario is first exemplified. For example, the image capture device is a zoom image capture device, that is, the image capture device can zoom in and shoot the embryo. The reason for this setting is that the embryo is close to spherical in shape and relatively transparent. Therefore, when the image capture device zooms in and shoots the embryo, different layers of the embryo can be captured. Figuratively speaking, this is like slicing the embryo from top to bottom first, and then obtaining an embryo image by shooting the slices, which helps to analyze the embryo from different layers or different positions.

[0109] On this basis, further, it is assumed that an embryo incubator is provided with N chambers, where N is a positive integer. The culture environment and the embryos between the chambers are generally isolated. Each chamber is provided with an independent image capture device. Of course, it can be understood that when N=1, the image capture device provided in the chamber can also be considered as an image capture device directly provided in the embryo incubator. Furthermore, each image capture device can operate under the control of the same or different controllers. On this basis, optionally, for the same situation, the controller can be directly provided in the embryo incubator; for different situations, the different controllers can be uniformly provided in the embryo incubator, or can be provided in the corresponding chambers respectively; and so on. This can be set according to actual needs and is not specifically limited here.

[0110] Here taking any bin as example, a culture dish can be placed in this bin, and in each culture dish, can be provided with M slots, generally be placed with zero or an embryo in a slot.Here taking the P slots in M ​​slots as example being placed with embryo, namely coexist in this bin with P embryo (corresponding to a plurality of embryos elaborated above).Suppose that the image capture device that is arranged in this bin has 0 focal length, then corresponding controller, can control this image capture device to shoot this P embryo successively based on the 1st focal length in these 0 focal lengths, and then control this image capture device zooming, so that based on the 2nd focal length in these 0 focal lengths, shoot this P embryo successively, and the rest can be deduced, until this image capture device shoots respectively based on this 0 focal length and completes, thus completes the 1st round of shooting.At this moment each embryo in P embryo all has an embryo image under each focal length.And then, after interval preset duration, can carry out the 2nd round of shooting, cycle back and forth, thereby make each embryo all have multiple embryo images under each focal length.

[0111] On this basis, the embryo image determination module may include an embryo image cluster obtaining unit and an embryo image determination unit. Since the shooting time required to complete one round of shooting is much shorter than the preset time, i.e., there is a significant time interval between each round of shooting, the embryo image cluster obtaining unit may be used to cluster each embryo image according to the shooting time points corresponding to each stored embryo image, thereby obtaining a plurality of embryo image clusters. Each embryo image in an embryo image cluster is an embryo image obtained in the same round of shooting, and can be roughly considered as an embryo image captured at one shooting time.

[0112] Furthermore, through the embryo image determination unit, for each embryo image cluster in multiple embryo image clusters, the embryo image belonging to the target embryo can be determined from the embryo images in the embryo image cluster according to the embryo identifier. These embryo images can be considered as embryo images taken for the target embryo at different focal lengths at one shooting time point. Therefore, after all embryo image clusters are processed separately, multiple focal plane image sequences can be obtained, and each embryo image belonging to the same focal plane image sequence can be considered as an embryo image taken at the same focal length at different shooting time points. The number of embryo images in the focal plane image sequence is the same as the number of embryo image clusters.

[0113] Furthermore, through the embryo image display module, the embryo images in each focal plane image sequence queried are played based on the focal length or embryo image cluster, so that relevant personnel can view the embryo images taken at different shooting time points with the same focal length, and can also view the embryo images taken at different focal lengths at the same shooting time point, so as to facilitate the multi-dimensional analysis of the target embryo.

[0114] The above technical solution realizes the dynamic playback of multi-focal plane image sequences.

[0115] On this basis, the optional embryo image display module is also used to:

[0116] Before playing the embryo images in each focal plane image sequence found, part of the embryo images in each focal plane image sequence are preloaded; wherein the shooting time points of the preloaded embryo images are earlier than the shooting time points of the embryo images not preloaded.

[0117] The above technical solution preloads (i.e., caches) embryo images with earlier shooting time points in each focal plane image sequence, so that when relevant personnel select an embryo image to play, they can quickly switch embryo images and play them, thereby achieving a smooth playback effect.

[0118] On this basis, in order to better understand the above-mentioned technical solutions as a whole, an exemplary explanation is given below using a universal access and synchronization management system for multi-source heterogeneous embryo data as an example.

[0119] For example, see Figure 4, the above-mentioned system can include a data acquisition layer, an interface adaptation layer, a data management layer and an application layer. Wherein, the data acquisition layer includes a plurality of data acquisition modules, which are used to dock different embryo incubators to collect the changed embryo data. The embryo data collected by each data acquisition module are all transferred to the interface adaptation layer, thereby utilizing the interface adapter in the interface adaptation layer to dynamically map the embryo data to the target data structure, and then the embryo data represented by the target data structure are transferred to the data management layer. Further, the database in the data management layer can be utilized to store and manage these embryo data. On this basis, relevant personnel can utilize the various applications provided by the application layer to process and analyze these embryo data to select embryos with good developmental potential for transplantation.

[0120] The above example realizes universal access and synchronous management of multi-source heterogeneous embryo data (ie, originating from different embryo incubators), thereby achieving efficient management of embryo data.

[0121] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. An embryo data management system, characterized in that: include: A data acquisition layer, an interface adaptation layer, and a data management layer; wherein the data acquisition layer includes at least two data acquisition modules, each of which is connected to a different embryo incubator; For each of the data acquisition modules and the embryo incubator to which the data acquisition modules are docked, the data acquisition module is configured to collect changed embryo data in the embryo incubator and transmit the collected embryo data to the interface adaptation layer; The interface adaptation layer is configured to, in response to the received embryo data, map the embryo data to a target data structure according to a field mapping relationship corresponding to the embryo incubator, and transmit the embryo data represented by the target data structure to the data management layer; The data management layer is used to store and manage the received embryo data; The field mapping relationship represents a mapping relationship between each field in the target data structure and each field in the original data structure corresponding to the embryo incubator; The target data structure is a preset reference data structure, or is obtained by adding a new field to the reference data structure according to the original data structure.

2. The system according to claim 1, wherein: The data acquisition module includes a data acquisition unit and a data transmission unit; wherein, The data acquisition unit is configured to determine and acquire changed embryo data in the embryo incubator in response to an embryo data change event monitored for the embryo incubator; The data transmission unit is used to transmit the collected embryo data to the interface adaptation layer.

3. The system according to claim 2, characterized in that The data acquisition unit is specifically used for: In response to an embryo data change event monitored for the embryo incubator, the changed embryo data in the embryo incubator is determined according to the description information of the previous data, and the embryo data is collected, wherein the previous data is the embryo data collected for the embryo incubator last time.

4. The system according to claim 3, characterized in that The description information includes a timestamp.

5. The system according to claim 2, wherein: The data transmission unit is specifically configured to: The collected embryo data is subjected to an integrity check, and if the integrity check passes, the embryo data is transmitted to the interface adaptation layer.

6. The system according to claim 1, wherein: Also includes: Application layer; The application layer is used to respond to the embryo data query instruction, determine the embryo data to be queried from the stored embryo data, and display the queried embryo data.

7. The system according to claim 6, characterized in that The embryo data includes embryo images, the embryo incubator is provided with an image capturing device, a plurality of embryos are placed in the embryo incubator, and the embryo images are obtained by capturing each of the embryos separately by the image capturing device; The application layer includes an embryo identification acquisition module, an embryo image determination module and an embryo image display module; wherein, The embryo identification acquisition module is used to determine the target embryo to be queried from each embryo in response to the embryo data query instruction, and obtain the embryo identification of the target embryo; The embryo image determination module is configured to determine the embryo image belonging to the target embryo from the stored embryo images according to the embryo identifier; The embryo image display module is used to display the queried embryo image.

8. The system according to claim 7, characterized in that The image capture device is a zoom image capture device, and a controller in the embryo incubator controls the image capture device to first capture each embryo in sequence based on one focal length, then capture each embryo in sequence based on another focal length, and after completing the capture at each focal length, perform another round of capture after a preset time interval; The embryo image determination module includes an embryo image cluster obtaining unit and an embryo image determination unit; wherein, The embryo image cluster obtaining unit is configured to cluster the embryo images according to the shooting time points corresponding to the stored embryo images to obtain a plurality of embryo image clusters; The embryo image determining unit is configured to determine, for each of the plurality of embryo image clusters, the embryo image belonging to the target embryo from the embryo images in the embryo image cluster according to the embryo identifier, so as to obtain a plurality of focal plane image sequences; The embryo images belonging to the same focal plane image sequence are the embryo images captured at the same focal length, and the number of the embryo images in the focal plane image sequence is the same as the number of the embryo image clusters; Correspondingly, the embryo image display module is specifically configured to play the embryo images in each of the queried focal plane image sequences based on the focal length or the embryo image cluster.

9. The system according to claim 8, characterized in that The embryo image display module is further used for: Before playing the embryo images in the queried focal plane image sequences, preloading a portion of the embryo images in each focal plane image sequence; The shooting time point of the preloaded embryo image is earlier than the shooting time point of the non-preloaded embryo image.

10. The system according to any one of claims 1 to 9, characterized in that The reference data structure is a nested data structure, which includes at least two layers of an embryo incubator layer, an embryo belonging object layer, an embryo culture record layer, an embryo layer, and an embryo image layer, which are nested in sequence.

Images