Method and apparatus for constructing a pedigree for a specific disease based on a family tree
The method constructs a pedigree for a disease using a family tree by a genealogy service that verifies consent and uses blockchain hashing and a beacon network, addressing data sharing challenges for accurate patient diagnosis and prognosis.
Patent Information
- Application Number
- JP2020572536
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-06-29
- Filing Date
- 2019-06-24
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-06-24
AI Technical Summary
Efficiently collecting and sharing health data and records across multiple generations in a family, particularly for genetic or rare diseases, is challenging due to consent issues and data linkage difficulties, which hinders accurate patient diagnosis and prognosis.
A method and system for constructing a pedigree for a particular disease using a family tree, involving a genealogy service that requests and verifies health data consent, utilizes a Merkle tree on a blockchain for data hashing, and employs a beacon network to identify relatives, ensuring confidentiality and accuracy.
Facilitates the efficient and confidential retrieval of health data across multiple generations, enabling accurate diagnosis and prognosis by identifying affected relatives and genetic traits, and supporting genome editing for inherited diseases.
Smart Images

Figure 0007593620000001 
Figure 0007593620000002 
Figure 0007593620000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to constructing pedigrees, and more specifically, but not exclusively, to constructing pedigrees for specific diseases based on pedigrees. [Background technology]
[0002] A genetic disease is any disease caused by an abnormality in an individual's genome. Abnormalities in the genome range from discrete mutations in a single base in a single gene to chromosomal abnormalities. Some genetic diseases are inherited from parents, while others may be caused by acquired mutations in a pre-existing gene or group of genes.
[0003] In the case of genetic diseases inherited from parents, such diseases may include single gene inheritance, multifactorial inheritance, chromosomal abnormalities, and / or mitochondrial inheritance patterns. Multifactorial inheritance diseases may be caused by a combination of environmental factors and mutations in multiple genes.
[0004] Thus, because family members have many factors in common, including their genes, environment, and lifestyle, a family medical history can help identify people in a family who are more likely to carry genes for common diseases (e.g., heart disease, high blood pressure, stroke, certain cancers, and diabetes).
[0005] By recognizing patterns of disease among blood relatives, health care professionals can determine whether individuals within a family, other family members, or future generations may be at increased risk of developing a particular condition.
[0006] As a result, individuals at high risk for a particular condition can undergo frequent screening, beginning at an early age.
[0007] Individuals can also make changes to their lifestyle to lower their risk of developing some diseases (eg, healthy diet, regular exercise, quitting smoking).
[0008] Even before birth, for example, a fertilized egg can undergo genome editing to remove pre-existing defects in the fertilized egg's genome. Summary of the Invention
[0009] A brief overview of various embodiments is provided below: The embodiments address methods and apparatus for constructing a pedigree for a particular disease based on a family tree.
[0010] A brief summary of various example embodiments is presented. Although some simplifications and omissions may be made in the following summary, the summary is intended to clarify and introduce some aspects of various example embodiments and is not intended to limit the scope of the present invention.
[0011] Detailed descriptions of example embodiments suitable for enabling those skilled in the art to make and use the inventive concepts follow in later sections.
[0012] Various embodiments relate to a method and apparatus for constructing a genealogy for a disease based on a family tree, the method including steps of receiving a family health status request by a family tree service, sending the request for the family tree by the family tree service, sending a data request for the health status of relatives in the family tree by the family tree service to an access control system, verifying consent of the relatives in the family tree by the access control system, receiving the relatives' health status from a health data storage by the family tree service, and drawing a family tree for a disease based on the relatives' health status by the family tree service.
[0013] In an embodiment of the present disclosure, the method of constructing a pedigree for a disease based on a pedigree further includes sending the pedigree to the patient by a genealogy service.
[0014] In an embodiment of the present disclosure, the method of constructing a pedigree for a disease based on a family tree further includes a step of determining, by a family tree service, which of the blood relatives on the family tree are affected by the disease.
[0015] In an embodiment of the present disclosure, the method of constructing a pedigree for a disease based on a pedigree further includes identifying patterns of genetic traits by a genealogy service.
[0016] In an embodiment of the present disclosure, the method of constructing a pedigree for a disease based on a pedigree further includes identifying a risk of relatives on the pedigree for the disease by a genealogy service.
[0017] In an embodiment of the present disclosure, the access control system matches relatives on the family tree with signatures from a service that provides the family tree.
[0018] In an embodiment of the present disclosure, relatives on a family tree use a Merkle tree to hash data onto the blockchain.
[0019] In an embodiment of the present disclosure, when the genealogy service requests health data from the access control system, the genealogy service links to the blockchain.
[0020] In an embodiment of the present disclosure, the access control system validates the blockchain and sends the health status data.
[0021] In an embodiment of the present disclosure, genomic data from a patient is sent to a network that determines whether the genomic data belongs to a relative on the network.
[0022] Various embodiments relate to a genealogy service that constructs a genealogy for a disease based on a family tree, the genealogy service having a memory and a processor, the processor being configured to receive a family health request, send a request for the family tree, send a data request for the health status of relatives on the family tree to an access control system, receive the health status of the relatives from a health data storage, and draw a genealogy for the disease based on the health status of the relatives.
[0023] In an embodiment of the present disclosure, in a genealogy service that constructs a genealogy for a disease based on a family tree, the processor is further configured to send the genealogy to the patient.
[0024] In an embodiment of the present disclosure, in a genealogy service that constructs a genealogy for a disease based on a family tree, the processor is further configured to determine which of the blood relatives on the family tree are affected by the disease.
[0025] In an embodiment of the present disclosure, in a genealogy service that constructs a genealogy for a disease based on a family tree, the processor is further configured to identify patterns of genetic traits.
[0026] In an embodiment of the present disclosure, in a genealogy service that constructs a genealogy for a disease based on a family tree, the processor is further configured to identify a risk of relatives on the family tree for the disease.
[0027] In an embodiment of the present disclosure, the access control system matches relatives on the family tree with signatures from a service that provides the family tree.
[0028] In an embodiment of the present disclosure, relatives on a family tree use a Merkle tree to hash data onto the blockchain.
[0029] In an embodiment of the present disclosure, when the genealogy service requests health data from the access control system, the genealogy service links to the blockchain.
[0030] In an embodiment of the present disclosure, the access control system validates the blockchain and sends health status data.
[0031] In an embodiment of the present disclosure, genomic data from a patient is sent to a network that determines whether the genomic data belongs to a relative on the network.
[0032] In the accompanying drawings, in which like reference characters refer to the same or functionally similar elements throughout the various views, the drawings, together with the following detailed description, are incorporated in and form a part of the specification and serve to further illustrate example embodiments of the concepts found in the claims and to explain various principles and advantages of those embodiments.
[0033] These and other more detailed and specific features are more fully disclosed in the following specification, which refers to the accompanying drawings. [Brief description of the drawings]
[0034] [Figure 1] 1 illustrates a block diagram of a system architecture for constructing a pedigree for a specific disease using the pedigree of the current embodiment. [Diagram 2] 1 depicts a family tree for a particular disease in the current embodiment. [Diagram 3] 1 illustrates a block diagram of a real-time data processing system of the current embodiment; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0035] It should be understood that the figures are only schematic and not to scale, and that the same reference symbols are used throughout the figures to denote the same or similar parts.
[0036] The specification and drawings explain the principles of various exemplary embodiments. Thus, it is clear that those skilled in the art can conceive of various arrangements that embody the principles of the invention and fall within its scope, even if not explicitly described or illustrated herein. Furthermore, all examples shown herein are expressly intended for educational purposes primarily to help the reader understand the concepts and inventive principles contributed by the inventor to promote the art, and should be construed as not being limited to such specifically listed examples and conditions. Moreover, the words "or", "or" and "or" as used herein refer to non-exclusive logical or (i.e., "and / or") unless otherwise indicated (e.g., "or else" or "or in the alternative"). Also, the various embodiments described herein are not necessarily mutually exclusive, and some embodiments may be combined with one or more embodiments to form new embodiments. Descriptors such as "first," "second," and "third" are not intended to constrain the order of the elements discussed, but are used to distinguish one element from the next, and may generally be interchangeable with one another.
[0037] Sharing health data and records between close relatives is easier than sharing health data and records between more than two generations in a family, which can be difficult due to linkage and availability of health data and records.
[0038] However, even if difficult, in the case of genetic or rare diseases, the patient's doctor needs access to this health data and records of the patient's other close relatives, and even to the health data and records of the patient's extended relatives, including up to three generations and possibly more. The needed health data and records may concern relatives unknown to the patient. However, this health data and records of the relatives may help the doctor to accurately diagnose the patient and prepare for his / her prognosis.
[0039] The current embodiments are directed to automatically and efficiently collecting consent to access health data and records and / or genomic data of a patient's family members and distant relatives to ensure accuracy and efficiency of retrieval of this information for physicians to accurately diagnose the patient.
[0040] The current embodiment is a method and system for constructing a family's pedigree for a particular disease based on pedigree and / or genomic data comparison results.
[0041] FIG. 1 illustrates a block diagram of the architecture of a system 100 for constructing a pedigree for a particular disease using the pedigree of the current embodiment.
[0042] The system 100 includes a genealogy service 101, a health data database 102, and a genealogy service 103. When a patient 120 initiates a family health request to the genealogy service 101 for a particular disease or group of suspected diseases, the genealogy service 101 sends a request to the genealogy service 103 to identify relatives on the patient's family tree 108.
[0043] The genealogy service 101 may send a data request to the access control system 104 of the health data storage 102 to request health data and records of relatives on the patient's family tree 108. The health data database 102 may respond to the genealogy service 101 with the requested data. Finally, the genealogy service 101 may output the requested disease genealogy for the patient and return the results to the patient 120.
[0044] After the genealogy service 101 receives the health data and records of relatives on the pedigree 108 for a particular disease, the genealogy service 101 outputs a pedigree for the requested disease for the patient.
[0045] The genealogy output from the genealogy service 101 organizes information about relatives' medical history, shows who may be affected, identifies patterns of genetic traits, and calculates who is at risk for a patient's desired disease.
[0046] The process begins at step 106 where a patient 120 initiates a family health request to the genealogy service 101 for a particular disease or group of suspected diseases. After receiving the request from the patient 120 at step 106, the process proceeds to step 107 where the genealogy service 101 sends the request to the genealogy service 103 to identify relatives on the patient's family tree 108.
[0047] The process then proceeds to step 109 where the genealogy service 101 sends a data request to the access control system 104 of the health data storage 102 to request the health data and records of the relatives on the patient's family tree 108. The process then proceeds to step 110 where the access control system 104 verifies the relatives' consent.
[0048] If consent is given, the access control system 104 can verify that the consent policy allows the relatives' health data and records to be shared to build a particular disease tree, and the process proceeds to step 111 where the relevant health data and records are shared by the access control system 104 and the genealogy service 101. If consent is not given, the access control system 104 cannot verify that the consent policy allows the relatives' health data and records to be shared to build a particular disease tree, and the process ends and the health data and records are not shared.
[0049] The process then proceeds to step 112, which uses health records and data from the patient's relatives to perform data analysis and draw the patient's requested disease pedigree. The process then proceeds to step 113, which returns the patient's requested disease pedigree to the patient 120.
[0050] After the genealogy service 101 receives health data and records from relatives on the patient's family tree 108 for a particular disease, the genealogy service 101 draws a pedigree for the patient's claimed particular disease. The pedigree organizes information about relatives' medical history by showing which relatives are affected by a particular disease, identifies patterns of genetic traits, and calculates who is at risk for the patient's claimed disease.
[0051] FIG. 2 depicts a pedigree 200 for a particular disease in the current embodiment.
[0052] Relatives marked by arrows 201 have the required disease condition.
[0053] The family tree may be provided by a third party service (e.g., Ancestry.com, Facebook®, etc.).
[0054] When the genealogy service is requested by a patient to provide a genealogy for a particular disease, the genealogy service requests, on behalf of the patient, a list of family members on the patient's family tree from the genealogy generation service. The genealogy service provides the list of family members along with their signatures to the genealogy service.
[0055] When the genealogy service makes a request to the access control system, the health data and records for specific disease conditions, as well as the list of family members, are provided by the family tree. The access control system matches the family list and the signature.
[0056] When the genealogy service and the family list are verified, the access control system may respond to the genealogy service with the requested health status of the family list.
[0057] In other embodiments, a blockchain may be used to provide genealogy services. For example, a Merkle tree may be constructed on the blockchain, where each family member can view the data on a block and attach their data to the blockchain along with a hash value.
[0058] Thus, when a genealogy service requests the health data and records of a patient's family members from an access control system, the genealogy service may attach a genealogy blockchain link to the access control system. The identities of the patient's family members may be preserved in hash values and thus remain anonymous to the access control system for confidentiality purposes. The access control system can verify the blockchain Merkle tree and respond to the genealogy service with the health data and records.
[0059] In other embodiments, the identities of some distant relatives may not appear in the patient's family tree, but in certain rare disease cases, their data and records may need to be known.
[0060] The Beacon Network may provide genealogy information about distant relatives. For example, a patient may provide genomic data about his or her mitochondrial DNA or Y chromosome to the Beacon Network. The Beacon Network may compare the patient's genomic data about his or her mitochondrial DNA or Y chromosome with that of other users on the Beacon Network to identify if any data belongs to any other users. This may help identify such relatives. If the Beacon Network identifies the patient's relatives, the Beacon Network may return a family list to the genealogy service. The Beacon Network may preserve the anonymity of the patient's relatives by providing only relevant genetic data and not identifying information about the patient's relatives.
[0061] In other embodiments, the system may be used to identify potential genetic diseases in fertilized eggs and mark the relevant genes.
[0062] For example, if a patient knows that a genetic disease may run in their family, the patient may initiate a genealogy search for the genetic disease. The genealogy service may provide the requested genealogy for the disease. The parent's physician may perform genome editing on the parent's embryo according to the embryo's genomic data and the genealogy.
[0063] 3 depicts an example hardware diagram 300 for implementing the method of constructing a pedigree for a particular disease based on a pedigree. As depicted, device 300 includes a processor 320, memory 330, a user interface 340, a network interface 350, and storage 360, which are interconnected via one or more system buses 310. It will be appreciated that FIG. 3 constitutes an abstraction in some respects, and the actual organization of the components of device 300 may be more complex than depicted.
[0064] Processor 320 may be any hardware device capable of executing instructions or otherwise processing data stored in memory 330 or storage 360. As such, processor 320 may include a microprocessor, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other similar device.
[0065] Memory 330 may include a variety of memories, such as, for example, an L1, L2, or L3 cache, or a system memory. As such, memory 330 may include static random access memory (SRAM), dynamic RAM (DRAM), flash memory, read-only memory (ROM), or other similar memory devices.
[0066] User interface 340 may include one or more devices that enable communication with a user, such as an administrator. For example, user interface 340 may include a display, a mouse, and a keyboard to receive user commands. In some embodiments, user interface 340 may include a command line interface or a graphical user interface that may be presented to a remote terminal via network interface 350.
[0067] Network interface 350 may include one or more devices that enable communication with other hardware devices. For example, network interface 350 may include a network interface card (NIC) configured to communicate according to the Ethernet protocol. Additionally, network interface 350 may implement a TCP / IP stack for communication according to the TCP / IP protocol. Various alternative or additional hardware or configurations for network interface 350 will be apparent.
[0068] Storage 360 may include one or more machine-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, or similar storage media. In various embodiments, storage 360 may store instructions for execution by processor 320 or data on which processor 320 may act. For example, storage 360 may store a basic operating system 361 that controls various basic operations of hardware 300 and instructions 362 for implementing a method of constructing a pedigree for a particular disease based on a pedigree.
[0069] As will be apparent, various information described as being stored in storage 360 may additionally or alternatively be stored in memory 330. In this regard, memory 330 may also be considered to constitute a "storage device" and storage 360 may be considered a "memory." Various other arrangements are apparent. Furthermore, both memory 330 and storage 360 may be considered a "non-transitory machine-readable medium." As used herein, the term "non-transitory" is understood to exclude transitory signals, but to include all forms of storage, including both volatile and non-volatile memory.
[0070] Although host device 300 is shown as including one of each of the described components, various components may be duplicated in various embodiments. For example, processor 320 may include multiple microprocessors configured to independently perform the methods described herein or to perform steps or subroutines of the methods described herein, whereby the multiple processors cooperate to achieve the functionality described herein. Furthermore, when device 300 is implemented in a cloud computing system, various hardware components may belong to separate physical systems. For example, processor 320 may include a first processor in a first server and a second processor in a second server.
[0071] As is evident from the above description, various exemplary embodiments of the present invention may be implemented in hardware. Additionally, various exemplary embodiments may be implemented as instructions stored in a non-transitory machine-readable storage medium, such as a volatile or non-volatile memory, that may be read and executed by at least one processor to perform the operations detailed herein. A non-transitory machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device. Thus, a non-transitory machine-readable storage medium may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and similar storage media, excluding transitory signals.
[0072] Those skilled in the art will appreciate that any blocks and block diagrams herein represent conceptual diagrams of illustrative circuits embodying the principles of the present invention. The implementation of specific blocks may vary and may be implemented in either hardware or software domains without limiting the scope of the present invention. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudocode, and the like, may be substantially represented in a machine-readable medium and represent various processes that may be so executed by a computer or processor (whether or not such computer or processor is explicitly shown).
[0073] Therefore, it should be understood that the above description is illustrative and not limiting. Many embodiments and applications other than the examples given will be apparent upon reading the above description. The scope of application should not be determined with reference to the above description and the following summary, but instead with reference to the appended claims and the full scope of equivalents to which the claims are entitled. It is anticipated and intended that future developments will occur in the technology discussed herein, and that the systems and methods discussed will incorporate such future developments. In summary, it should be understood that the present application is capable of modification and variation.
[0074] Advantages, benefits, solutions to problems, and any elements that may provide any advantage, advantage, or solution that becomes more apparent or that should occur should not be construed as critical, necessary, or essential features or elements of any or all claims. The present invention is defined solely by the appended claims, including any amendments made during the pendency of this application, and all equivalents of those claims as issued.
[0075] All terms used in the claims, unless otherwise expressly stated herein, are intended to be given their broadest reasonable construction and their ordinary meaning as understood by one of ordinary skill in the art described herein. In particular, the use of singular articles such as "a," "the," "said," etc., should be read as reciting one or more of the indicated elements unless the claim expressly states otherwise.
[0076] The Abstract of the Disclosure is provided to enable the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Moreover, in the above Detailed Description, it can be seen that various figures are grouped together in various embodiments to simplify the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as separately claimed subject matter.
Claims
1. 1. A method for constructing a pedigree for a disease based on a pedigree, comprising: receiving a family health status request by a genealogy service; submitting a request for the genealogy with the genealogy service to obtain the genealogy as a Merkle tree constructed on a blockchain; sending, by the genealogy service, a request for health status data of the family tree relatives to an access control system; verifying, by the access control system, consent of the relatives on the family tree by verifying the Merkle tree in which the identities of the relatives on the family tree are held in hash values; receiving, by the genealogy service, a health status of the relative from a health data storage; drawing a pedigree for the disease based on the health conditions of the relatives using the genealogy service; The method according to claim 1,
2. sending the genealogy to the patient by the genealogy service. The method of claim 1.
3. determining, by the genealogy service, which of the relatives on the family tree are affected by the disease. The method of claim 1.
4. identifying patterns of genetic traits by the genealogy service. The method of claim 1.
5. identifying, by the genealogy service, a risk of the relatives on the family tree for the disease; The method of claim 1.
6. When the genealogy service requests the health status data from the access control system, the genealogy service links to the blockchain. The method of claim 1.
7. The access control system validates the blockchain and transmits the health status data. The method according to claim 6.
8. The step of sending the pedigree request includes sending genomic data from the patient to a beacon network, the beacon network configured to determine whether the genomic data belongs to a relative on the beacon network, and the pedigree includes the relative on the beacon network to which the genomic data has been identified. The method of claim 1.
9. A genealogy service that constructs a genealogy for a disease based on a family tree, comprising: Memory, Processor and having The processor, Receive a family health status request; Sending a request for the family tree and retrieving the family tree as a Merkle tree constructed on a blockchain; sending a request for health status data for said pedigree relatives to an access control system; receiving from a health data storage the health status of the relative, the consent of which is confirmed by the access control system by checking the Merkle tree in which the identity of the relative on the family tree is held in a hash value; Draw a pedigree for the disease based on the health status of the relatives A genealogy service that is configured to:
10. The processor is further configured to send the pedigree to the patient.
10. The genealogy service of claim 9.
11. The processor is further configured to determine which of the relatives on the family tree are affected by the disease.
10. The genealogy service of claim 9.
12. The processor is further configured to identify a pattern of a genetic trait.
10. The genealogy service of claim 9.
13. The processor is further configured to identify a risk of the relatives on the pedigree for the disease.
10. The genealogy service of claim 9.
14. When the genealogy service requests the health status data from the access control system, the genealogy service links to the blockchain.
10. The genealogy service of claim 9.
15. The access control system validates the blockchain and transmits the health status data.
15. The genealogy service of claim 14.
16. Sending the request for the pedigree includes sending genomic data from the patient to a beacon network, the beacon network configured to determine whether the genomic data belongs to a relative on the beacon network, and the pedigree includes the relative on the beacon network to which the genomic data is identified.
10. The genealogy service of claim 9.
Citation Information
Patent Citations
System for protecting or using gene information of blood relatives
JP2003281283A
Electronic medical chart system, medical chart information acquisition method, and medical chart information acquisition program
JP2008171133A
Medical history diagnosis system and method
JP2011253533A
Information processing device, information processing method, and program
JP2015201092A
Family tree drawing device, family tree drawing method, and program
JP2016207078A
