WO2017087769A1 - Distributed systems for secure storage and retrieval of encrypted biological specimen data - Google Patents

Distributed systems for secure storage and retrieval of encrypted biological specimen data Download PDF

Info

Publication number
WO2017087769A1
WO2017087769A1 PCT/US2016/062718 US2016062718W WO2017087769A1 WO 2017087769 A1 WO2017087769 A1 WO 2017087769A1 US 2016062718 W US2016062718 W US 2016062718W WO 2017087769 A1 WO2017087769 A1 WO 2017087769A1
Authority
WO
WIPO (PCT)
Prior art keywords
patient record
patient
information
device client
submission
Prior art date
Application number
PCT/US2016/062718
Other languages
French (fr)
Inventor
Amelia Wall WARNER
Mark Anthony COLLINS
Original Assignee
Global Specimen Solutions, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Global Specimen Solutions, Inc. filed Critical Global Specimen Solutions, Inc.
Priority to AU2016355193A priority Critical patent/AU2016355193A1/en
Priority to SG11201803785RA priority patent/SG11201803785RA/en
Priority to JP2018526509A priority patent/JP2018538745A/en
Priority to CA3003885A priority patent/CA3003885A1/en
Priority to CN201680067421.3A priority patent/CN109874340B/en
Priority to EP16867203.8A priority patent/EP3378029A4/en
Publication of WO2017087769A1 publication Critical patent/WO2017087769A1/en
Priority to US15/651,302 priority patent/US10510441B2/en
Priority to US16/689,421 priority patent/US11429938B2/en
Priority to US17/880,278 priority patent/US20230015147A1/en
Priority to AU2022231751A priority patent/AU2022231751A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/14—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using a plurality of keys or algorithms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G06Q20/145—Payments according to the detected use or quantity
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography
    • G06Q2220/10—Usage protection of distributed data files
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/20—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for electronic clinical trials or questionnaires
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
    • Y02A90/00—Technologies having an indirect contribution to adaptation to climate change
    • Y02A90/10—Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation

Definitions

  • the present invention relates to distributed systems for the storage and retrieval of encrypted biological specimen data. More specifically, it relates to a system employing blockchains in a secure peer-to-peer (P2P) networks for the storage and retrieval of encrypted data relating to biological specimens and encrypted data associated with the biological specimens.
  • P2P peer-to-peer
  • Bitcoin is an on-line cryptographic based, decentralized currency network that employs a database technology known as blockchain.
  • Blockchain technology is the backbone of the bitcoin network and provides a tamper-proof data structure, providing a shared public ledger open to all users with access to the bitcoin network.
  • a blockchain is a distributed database that is secured by complex cryptography and is publically viewable, in a P2P network. Any type of data may be stored semi-publically in a blockchain. Data stored in a blockchain is signed by the user uploading the data into the blockchain. Sandra with access to the blockchain may verify that data has been uploaded by a certain user, but only the user who uploaded the data owns a private key that grants access to the data. Thus, the blockchain behaves like a database with a public header— some information is available publicly, but a specific key is required to obtain additional data from the blockchain.
  • the benefits of a blockchain are that it can store any type of data and keep it highly secure through a combination of encryption and private key access, but also provide limited public access to the data. These benefits make blockchains an ideal solution for storing highly sensitive data that must be shared.
  • the present invention employs blockchain technology in the storage of data about a biological specimen, the subject from which the specimen was obtained, healthcare data concerning the subject, and results of the analysis of the specimen, including genomic information.
  • blockchains may reside in a P2P network of computers (the exchange), managed and setup by a distributed autonomous organization (DAO).
  • the DAO may serve all the members since the members provide value to the overall DAO by virtue of their work (e.g., adding information to their blockchain, or allowing the blockchain to be inspected and the data utilized for wider analyse).
  • the P2P network may pre-mine to create a set of empty or very short blockchain.
  • the empty blockchain associated with the patient may reside in the patient's individual wallet, which may act as a patient's individual biobank.
  • a transaction may be added to the patient's blockchain for each specimen collected or analysis performed. Such transactions may secured with the patient's private key. As more transactions and data are added to the blockchain, it becomes more complex, and those without a private key must expend additional computational resources to unlock the blockchain.
  • the patient may broadcast the fact that data is available. For example, the patient may broadcast that he is a certain ethnicity, is on certain medications, has samples banked physically, or had a single-nucleotide polymorphism analysis done to all the members of the blockchain network.
  • the broadcast of the patient may be picked up by the blockchain miners— individuals within the network who have an interest in obtaining that data.
  • Miners may compete to unlock the blockchain and inspect the ledger and use the data held within it without the private key by solving the cryptographic puzzle associated with the blockchain using computational resources.
  • the miner who wins may be rewarded with access to the data.
  • This record of access may be appended to the patient' s blockchain as a new block, which increases the security of the blockchain and the difficulty of obtaining access to it.
  • Each block in a blockchain may contain multiple pieces of data. For example, during a clinical trial, multiple transactions and data could be loaded into a single block, thereby reducing the computational mining cost to unlock the block chain or add to it. During the trial, only the trial sponsor could be given access to the blockchain. At the conclusion of the trial the availability of the blockchain could be broadcast to the network members, allowing any member prepared to invest the computational power to unlock it. In some embodiments, members may simply pay a monetary fee proportional to the computing time necessary to unlock a blockchain to gain access to it.
  • specimen identifiers may all be added to a blockchain. Since blocks are added to a blockchain in a linear manner, the blockchain provides an overall transaction history which can be inspected. For example, if the specimen was analyzed before consent was given, or consent was revoked prior to the analysis, such legal or ethical problems would be evidenced in the sequence of the blockchain.
  • the specimen owner may give permission to transfer the physical specimen to a third party, and a record of that transaction may be stored in the specimen's blockchain.
  • a distributed system for secure storage and retrieval of encrypted biological specimen data may comprise a submission device client operable to send, to a patient record server device, a patient record; and receive, from the patient record server device, a confirmation of receipt of the patient record.
  • the system may further comprise a patient record server device comprising a first processor and first memory, the patient record device operable to receive, from the submission device client, the patient record; send, to the submission device client, the confirmation of receipt of the patient record; receive, from a member device client, patient profile information; determine search results based on the patient profile information; and send, to the member device client, information indicating the search results.
  • They system may yet further comprise a member device client operable to send, to the patient record server device, the patient profile information; receive, from the patient record server device, the information indicating the search results based on the patient profile information; and receive the search results based on the information indicating the search results.
  • a member device client operable to send, to the patient record server device, the patient profile information; receive, from the patient record server device, the information indicating the search results based on the patient profile information; and receive the search results based on the information indicating the search results.
  • the system may further comprise a submission device comprising a second processor and second memory, the submission device operable to execute the submission device client.
  • the system may further comprise a member device comprising a third processor and a third memory, the memory device operable to execute the member device client.
  • the submission device client of the system may be further operable to receive a first confirmation of a patient record provider credit from the patient record server device.
  • the patient record server device may be further operable to store the patient record provider credit in a next patient blockchain, send the first confirmation of the patient record provider credit to the submission device client, store a member device client debit in the next patient blockchain, send a second confirmation of the member device client debit to the member device client, and store an operator credit in the next patient blockchain.
  • the member device client may be further operable to receive the second
  • the patient record server device of the system may be further operable to receive, from the member device client, mined information; store the mined information in a next member blockchain; and send, to the member device client, a confirmation of storage of the mined information.
  • the member device client may be further operable to mine the search results to extract mined information; send, to the patient record server, the mined information; and receive, from the patient record server, confirmation of the storage of the mined information.
  • the patient record server device of the system may be further operable to assign an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
  • the submission device client of the system in order to send the patient record, may be further operable to receive first patient record information input based on a clinical trial, send the first patient record information to the patient record server device, receive second patient record information input based on a clinical trial, and send the second patient record information to the patient record server device.
  • the patient record server device in order to receive the patient record, may be further operable to receive the first patient record information from the submission device client; store the first patient record information in a next blockchain; increase, in response to storing the first patient record information, the access fee associated with the patient record; receive the second patient record from the submission device client; store the second record information in the next blockhain; and increase, in response to storing the second patient record information, the access fee associated with the patient record.
  • the patient record server device of the system in order to facilitate a clinical trial, may be further operable to receive a plurality of clinical trial patient records from a plurality of submission device clients
  • a method of securely storing and retrieving encrypted biological specimen data may comprise receiving a patient record from a submission device client, sending a confirmation of receipt of the patient record to the submission device client, receiving patient profile information from a member device client, determining search results based on the patient profile information, and sending information indicating the search results to the member device client.
  • the method may further comprise storing a patient record provider credit in a next patient blockchain, sending a first confirmation of the patient record provider credit to the submission device client, storing a member device client debit in the next patient blockchain, sending a second confirmation of the member device client debit to the member device client, and storing an operator credit in the next patient blockchain.
  • the method may further comprise receiving mined information from the member device client, storing the mined information in a next member blockchain, and sending a confirmation of storage of the mined information to the member device client.
  • the method may further comprise assigning an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
  • the method may further comprise receiving first patient record information from the submission device client; storing the first patient record information in a next blockchain; increasing, in response to storing the first patient record information, the access fee associated with the patient record; receiving second patient record from the submission device client; storing the second record information in the next blockchain; and increasing, in response to storing the second patient record information, the access fee associated with the patient record.
  • FIG. 1 is an overview system diagram illustrating an exemplary distributed system for securely storing and retrieving encrypted biological specimen data.
  • FIG. 2A is a network diagram illustrating example components and functions of a distributed system for securely storing and retrieving encrypted biological specimen data according to some embodiments of the present invention.
  • FIG. 2B is a network diagram illustrating additional example components and functions of a distributed system for securely storing and retrieving encrypted biological specimen data.
  • FIG. 3 is a block diagram of the hardware components comprising a submission device according to some embodiments of the present invention.
  • FIG. 4 is a block diagram of the hardware components comprising a member device according to some embodiments of the present invention.
  • FIG. 5 is a block diagram of the hardware components comprising a patient record server according to some embodiments of the present invention.
  • computing device should be broadly construed.
  • both the submission device 30 and member device 50 may be considered computing devices. It can include any type of mobile device, for example, a smart phone, a cell phone, a pager, a personal digital assistant (PDA, e.g., with GPRS NIC), a mobile computer with a cellular radio, or the like.
  • a typical mobile device is a wireless data access-enabled device (e.g., an iPHONE ® smart phone, a BLACKBERRY ® smart phone, a NEXUS ONETM smart phone, an iPADTM device, or the like) that is capable of sending and receiving data in a wireless manner using protocols like the Internet Protocol, or IP, and the wireless application protocol, or WAP.
  • Wireless data access is supported by many wireless networks, including, but not limited to, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex, EDGE and other 2G, 3G, 4G and LTE technologies, and it operates with many handheld device operating systems, such as PalmOS, EPOC, Windows CE, FLEXOS, OS/9, JavaOS, iOS and Android.
  • the mobile device is a cellular telephone or smart phone that operates over GPRS (General Packet Radio Services), which is a data technology for GSM networks.
  • GPRS General Packet Radio Services
  • a given mobile device can communicate with another such device via many different types of message transfer techniques, including SMS (short message service), enhanced SMS (EMS), multi-media message (MMS), email WAP, paging, or other known or later-developed wireless data formats.
  • SMS short message service
  • EMS enhanced SMS
  • MMS multi-media message
  • email WAP paging, or other known or later-developed wireless data formats.
  • the subject matter may be embodied as devices, systems, methods, and/or computer program products. Accordingly, some or all of the subject matter may be embodied in hardware and/or in software (including firmware, resident software, micro-code, state machines, gate arrays, etc.) Furthermore, the subject matter may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
  • a computer-usable or computer- readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • the computer-usable or computer-readable medium may be for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium.
  • computer- readable media may comprise computer storage media and communication media.
  • Computer storage media includes volatile and nonvolatile, removable and nonremovable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and may be accessed by an instruction execution system.
  • the computer-usable or computer-readable medium can be paper or other suitable medium upon which the program is printed, as the program can be electronically captured via, for instance, optical scanning of the paper or other suitable medium, then compiled, interpreted, of otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
  • Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
  • modulated data signal can be defined as a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
  • communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above-mentioned should also be included within the scope of computer-readable media.
  • the embodiment may comprise program modules, executed by one or more systems, computers, or other devices.
  • program modules include routines, programs, objects, components, data structures, and the like, that perform particular tasks or implement particular abstract data types.
  • functionality of the program modules may be combined or distributed as desired in various embodiments.
  • a computing such as a mobile device, is connectable to a transmission functionality that varies depending on
  • the transmission functionality comprises one or more components such as a mobile switching center (MSC) (an enhanced ISDN switch that is responsible for call handling of mobile subscribers), a visitor location register (VLR) (an intelligent database that stores on a temporary basis data required to handle calls set up or received by mobile devices registered with the VLR), a home location register (HLR) (an intelligent database responsible for management of each subscriber's records), one or more base stations (which provide radio coverage with a cell), a base station controller (BSC) (a switch that acts as a local concentrator of traffic and provides local switching to effect handover between base stations), and a packet control unit (PCU) (a device that separates data traffic coming from a mobile device).
  • MSC mobile switching center
  • VLR visitor location register
  • HLR home location register
  • BSC base station controller
  • PCU packet control unit
  • the HLR also controls certain services associated with incoming calls.
  • the mobile device is the physical equipment used by the end user, typically a subscriber to the wireless network.
  • a mobile device is a 2.5G-compliant device, 3G-compliant device, or a 4G-compliant device) that includes a subscriber identity module (SIM), which is a smart card that carries subscriber-specific information, mobile equipment (e.g., radio and associated signal processing devices), a user interface (or a man- machine interface (MMI), and one or more interfaces to external devices (e.g., computers, PDAs, and the like).
  • SIM subscriber identity module
  • MMI man- machine interface
  • the mobile device may also include a memory or data store.
  • a distributed system for storing and retrieving encrypted biological specimen data may be comprised of a plurality of submission devices 30, a plurality of member devices 50, and a plurality of patient record server devices 70.
  • the submission devices 30 may represent the devices used to perform submission of the patient records.
  • the member devices 50 may represent the devices used by members (e.g., pharmaceutical companies, medical research companies, academic organizations, etc.) to access the patient records.
  • the patient record servers 70 may represent the devices that together host the patient records in a secure and distributed manner using blockchain technology.
  • the submission device 30 may be comprised of a control system 32, UI Function
  • the private key may be stored in the key repository 40, along with the respective patient record 42 for the submission device 30.
  • the UI function may provide the user interface controls allowing a user of the system to interact with the submission device 30.
  • the communication function 36 may work with the
  • the submission function 38 may send the patient record collected at the submission device 30 to the patient record servers 70.
  • the member device 50 may be comprised of a control system 52, UI Function 54, communication function 56, and an access function 58.
  • the private key may be stored in the key repository 60, along with the respective patient records 62 for the member device 50.
  • the UI function 54 may provide the user interface controls allowing a user of the system to interact with the member device 50.
  • the communication function 56 may work with the communication interfaces 408 to provide communications for the member device 50.
  • the submission function 58 may receive the patient records collected at the patient record servers 70.
  • the patient record servers 70 may be comprised of a control system 72, UI
  • the owner repository 80 may store administrative information for the patient record servers 70.
  • the member repository 82 may store information about the member devices 50 accessing the patient record servers 70.
  • the patient record repository 84 may store the patient record information 42 received from the submission devices 30.
  • the private and public keys may be stored at in the key repository 60, along with the respective patient records 62 for the member device 50.
  • the record intake function 74 may operate to receive the patent records 42 from the submission device 30.
  • the record access function 76 may operate to receive request for and send data in response to access to patient records 42 stored in the patient record repository 84.
  • the communication function 77 may work with the communication interfaces 508 to provide communications for the patient record server 70.
  • the access key generation function 78 may provide access keys to the submission devices 30 and member devices 50.
  • the network 20 is not limited by the implementations listed above. More specifically, the network 20 may be any type of network 20 suitable to allow interaction between the submission devices 30, member devices 50, and the patient record servers 70.
  • the network 20 may be a wired network, a wireless network, or any combination thereof.
  • the network 20 may include a distributed computing network, an intranet, a local-area network (LAN) and/or a wide-area network (WAN), or any combination thereof.
  • FIG. 2 depicts the network traffic on a distributed system for storing and retrieving encrypted biological specimen data according to at least one embodiment of the present invention.
  • the submission device 30 may request 202 and receive keys 204 from the patient record servers 70.
  • Patient data may be received 206 at the submission device 30 and sent 208 to the patient record servers 70.
  • the patient record servers 70 may work together to add the patient records to the patient record repository 804 as part of the next blockchain 212.
  • a confirmation of the recordation may be provided to the submission device 30.
  • a member device 50 may receive information indicating profiles to be matched 214.
  • the member device 50 may request access to patient data for patients matching the profile 216, and access keys may be sent to the member device 50 enabling access. Data may be requested by the member device 50 from the patient record servers 70.
  • Payment from the member to the infrastructure operator(s) may be authorized 220.
  • the requested data may be received 222 at the member device 50.
  • the member device 50 may then proceed to mine the data 224.
  • the member's account may then be debited 226 for access to the data and proof of the transaction may be recorded in the next blockchain 228.
  • Confirmation of the member debit may be received 229 at the member device 50.
  • the patient's account may be credited 230 for providing the data and proof of the transaction may be recorded in the next blockchain 232.
  • Confirmation of the patient credit may be received 233 at the submission device 30.
  • the infrastructure provider's account may be credited 234 for enabling the patient/member transaction and proof of the transaction may be recorded in the next blockchain 236.
  • the submission device 30 includes a controller 304 connected to memory 306, one or more communications interfaces 308, one or more user interface components 310, one or more storage devices 312, and a location module 314 by a bus 302 or similar mechanism.
  • the controller 304 is a microprocessor, digital ASIC, FPGA, or the like.
  • the submission device 30 includes a control system 32 having associated memory 306.
  • the controller 304 is a microprocessor, and the UI function 34, communications function 36, and submission function 38 are implemented in software and stored in the memory 306 for execution by the controller 304.
  • the aforementioned functions and engine may be implemented in software, hardware, or a combination thereof.
  • the submission device 30 also includes a communication interface 308 enabling the submission device 30 to connect to the network 20.
  • the one or more user interface components 310 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof.
  • the storage device(s) 312 is a non-volatile memory.
  • the location module 314 is a hardware component, such as a GPS receiver.
  • the present invention is not limited thereto.
  • FIG. 4 is a block diagram of a member device 50 according to one embodiment of the present disclosure.
  • the member device 50 includes a controller 404 connected to memory 406, one or more communications interfaces 408, one or more user interface components 410, one or more storage devices 412 by a bus 402 or similar mechanism.
  • the controller 404 is a microprocessor, digital ASIC, FPGA, or the like.
  • the member device 50 includes a control system 52 having associated memory 406.
  • the controller 404 is a microprocessor, and the and the UI function 54, communications function 56, and access function 58 are implemented in software and stored in the memory 406 for execution by the controller 404.
  • the present disclosure is not limited thereto.
  • the aforementioned functions may be implemented in software, hardware, or a combination thereof.
  • the member device 50 also includes a communication interface 408 enabling the reference member device 50 to connect to the network 20.
  • the one or more user interface components 410 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof.
  • the storage device(s) 412 is a non- volatile memory.
  • FIG. 5 is a block diagram of a comparison server device 70 according to an embodiment of the present disclosure.
  • comparison server device 70 includes a controller 504 connected to a memory 506, one or more secondary storage devices 512, and one or more communications interfaces 508 by a bus 502 or similar mechanism.
  • the controller 504 is a microprocessor, digital Application Specific Integrated Circuit ASIC, Field Programmable Gate Array FPGA, or the like.
  • the comparison server device 70 includes a control system 72 having associated memory 506.
  • the controller 504 is a
  • the microprocessor, and the record intake function 74, record access function 76, and access key generation 78 is implemented in software and stored in the memory 506 for execution by the controller 504.
  • the aforementioned engine may be implemented in software, hardware, or a combination thereof.
  • the owner repository 80, member repository 82, and patient record repository 84 may be stored in the one or more secondary storage devices 512.
  • the secondary storage devices 512 are digital data storage devices such as, for example, one or more hard disk drives.
  • the comparison server device 70 also includes a communication interface 508 enabling the comparison server device 70 to connect to the network 20.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Accounting & Taxation (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Primary Health Care (AREA)
  • General Health & Medical Sciences (AREA)
  • Epidemiology (AREA)
  • Finance (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Biomedical Technology (AREA)
  • Databases & Information Systems (AREA)
  • Pathology (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
  • Measuring And Recording Apparatus For Diagnosis (AREA)
  • Investigating Or Analysing Biological Materials (AREA)

Abstract

The subject matter disclosed herein includes distributed systems for secure storage and retrieval of encrypted biological specimen data. According to one embodiment, the system may comprise a submission device client operable to send, to a patient record server device, a patient record; and receive, from the patient record server device, a confirmation of receipt of the patient record. The system may further comprise a patient record server device comprising a first processor and second memory, a second communications interface associated with the first processor and second memory and operable to receive, from the submission device client, the patient record; send, to the submission device client, the confirmation of receipt of the patient record; receive, from a member device client, patient profile information; determine search results based on the patient profile information; and send, to the member device client, information indicating the search results. They system may yet further comprise a member device client operable to send, to the patient record server device, the patient profile information; receive, from the patient record server device, the information indicating the search results based on the patient profile information; and receive the search results based on the information indicating the search results.

Description

DISTRIBUTED SYSTEMS FOR SECURE STORAGE AND RETRIEVAL OF ENCRYPTED
BIOLOGICAL SPECIMEN DATA
CROSS-REFERENCE TO RELATED APPLICATION
[001] This application claims the benefit of priority of U.S. provisional patent application no. 62/256,759 titled "BitSpecimen: A Secure Digital Encrypted Database Of Information About Specimens And Data Collected During The Course Of Clinical Trials, Research Studies, Patient Registries And Institutional And National Biobanks" filed on
November 18, 2015, which is incorporated herein in its entirety by this reference.
BACKGROUND OF THE INVENTION
Field of the Invention
[002] The present invention relates to distributed systems for the storage and retrieval of encrypted biological specimen data. More specifically, it relates to a system employing blockchains in a secure peer-to-peer (P2P) networks for the storage and retrieval of encrypted data relating to biological specimens and encrypted data associated with the biological specimens.
Description of Related Art
[003] Privacy and trust in healthcare data is of particular concern for patients, medical facilities, governments and pharmaceutical companies. In the course of clinical trials specimens are collected and data about specimens is also created as the results of analyses performed on the specimen and the patient. These highly annotated specimens are an extremely valuable resource for precision medicine, yet they are often locked away (both physically and logically) and rarely used beyond their original use. Often, privacy concerns from the patients, the medical and legal community, pharmaceutical companies, and other parties results in patients opting out of trials, limiting the use of their data and other unused data and specimens of high value. In addition, the rich data from these specimens is also locked away in siloed pharmaceutical company databases and electronic medical systems, which precludes analysis of this data through modern data analysis techniques such as data mining or crowdsourcing.
[004] Bitcoin is an on-line cryptographic based, decentralized currency network that employs a database technology known as blockchain. Blockchain technology is the backbone of the bitcoin network and provides a tamper-proof data structure, providing a shared public ledger open to all users with access to the bitcoin network.
[005] A blockchain is a distributed database that is secured by complex cryptography and is publically viewable, in a P2P network. Any type of data may be stored semi-publically in a blockchain. Data stored in a blockchain is signed by the user uploading the data into the blockchain. Anyone with access to the blockchain may verify that data has been uploaded by a certain user, but only the user who uploaded the data owns a private key that grants access to the data. Thus, the blockchain behaves like a database with a public header— some information is available publicly, but a specific key is required to obtain additional data from the blockchain.
[006] The benefits of a blockchain are that it can store any type of data and keep it highly secure through a combination of encryption and private key access, but also provide limited public access to the data. These benefits make blockchains an ideal solution for storing highly sensitive data that must be shared.
SUMMARY OF THE INVENTION
[007] The present invention employs blockchain technology in the storage of data about a biological specimen, the subject from which the specimen was obtained, healthcare data concerning the subject, and results of the analysis of the specimen, including genomic information. In embodiments of the present invention, blockchains may reside in a P2P network of computers (the exchange), managed and setup by a distributed autonomous organization (DAO). The DAO may serve all the members since the members provide value to the overall DAO by virtue of their work (e.g., adding information to their blockchain, or allowing the blockchain to be inspected and the data utilized for wider analyse).
[008] In certain embodiments of the present invention, when a new clinical trial starts or a member wishes to provide biological specimens, the P2P network may pre-mine to create a set of empty or very short blockchain. When a patient enrolls in the trial, the empty blockchain associated with the patient may reside in the patient's individual wallet, which may act as a patient's individual biobank. As the clinical trial proceeds and the patient consents to specimen collection and analysis of such specimens, a transaction may be added to the patient's blockchain for each specimen collected or analysis performed. Such transactions may secured with the patient's private key. As more transactions and data are added to the blockchain, it becomes more complex, and those without a private key must expend additional computational resources to unlock the blockchain.
[009] Opening up a blockchain and either adding to it, or reading it requires mining of the blockchains. When a patient wants to make his blockchain available for use by other members of the blockchain network, the patient may broadcast the fact that data is available. For example, the patient may broadcast that he is a certain ethnicity, is on certain medications, has samples banked physically, or had a single-nucleotide polymorphism analysis done to all the members of the blockchain network.
[0010] The broadcast of the patient may be picked up by the blockchain miners— individuals within the network who have an interest in obtaining that data. Miners may compete to unlock the blockchain and inspect the ledger and use the data held within it without the private key by solving the cryptographic puzzle associated with the blockchain using computational resources. The miner who wins may be rewarded with access to the data. This record of access may be appended to the patient' s blockchain as a new block, which increases the security of the blockchain and the difficulty of obtaining access to it.
[0011] Each block in a blockchain may contain multiple pieces of data. For example, during a clinical trial, multiple transactions and data could be loaded into a single block, thereby reducing the computational mining cost to unlock the block chain or add to it. During the trial, only the trial sponsor could be given access to the blockchain. At the conclusion of the trial the availability of the blockchain could be broadcast to the network members, allowing any member prepared to invest the computational power to unlock it. In some embodiments, members may simply pay a monetary fee proportional to the computing time necessary to unlock a blockchain to gain access to it.
[0012] Almost any data about the patient or specimen may be added to the blockchain.
For example, specimen identifiers, informed consent data, medical record, specimen chain of custody, what has happened to the specimen, results of analyses, etc. may all be added to a blockchain. Since blocks are added to a blockchain in a linear manner, the blockchain provides an overall transaction history which can be inspected. For example, if the specimen was analyzed before consent was given, or consent was revoked prior to the analysis, such legal or ethical problems would be evidenced in the sequence of the blockchain. In yet another example, if the physical specimen is to be used for analysis, the specimen owner may give permission to transfer the physical specimen to a third party, and a record of that transaction may be stored in the specimen's blockchain.
[0013] In some embodiments of present invention, a distributed system for secure storage and retrieval of encrypted biological specimen data may comprise a submission device client operable to send, to a patient record server device, a patient record; and receive, from the patient record server device, a confirmation of receipt of the patient record. The system may further comprise a patient record server device comprising a first processor and first memory, the patient record device operable to receive, from the submission device client, the patient record; send, to the submission device client, the confirmation of receipt of the patient record; receive, from a member device client, patient profile information; determine search results based on the patient profile information; and send, to the member device client, information indicating the search results. They system may yet further comprise a member device client operable to send, to the patient record server device, the patient profile information; receive, from the patient record server device, the information indicating the search results based on the patient profile information; and receive the search results based on the information indicating the search results.
[0014] In yet other embodiments of the present invention, the system may further comprise a submission device comprising a second processor and second memory, the submission device operable to execute the submission device client. The system may further comprise a member device comprising a third processor and a third memory, the memory device operable to execute the member device client.
[0015] In yet other embodiments of the present invention, the submission device client of the system may be further operable to receive a first confirmation of a patient record provider credit from the patient record server device. The patient record server device may be further operable to store the patient record provider credit in a next patient blockchain, send the first confirmation of the patient record provider credit to the submission device client, store a member device client debit in the next patient blockchain, send a second confirmation of the member device client debit to the member device client, and store an operator credit in the next patient blockchain. The member device client may be further operable to receive the second
confirmation of the member device client debit from the patient record server device.
[0016] In yet other embodiments of the present invention, the patient record server device of the system may be further operable to receive, from the member device client, mined information; store the mined information in a next member blockchain; and send, to the member device client, a confirmation of storage of the mined information. The member device client may be further operable to mine the search results to extract mined information; send, to the patient record server, the mined information; and receive, from the patient record server, confirmation of the storage of the mined information.
[0017] In yet other embodiments of the present invention, the patient record server device of the system may be further operable to assign an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
[0018] In yet other embodiments of the present invention, the submission device client of the system, in order to send the patient record, may be further operable to receive first patient record information input based on a clinical trial, send the first patient record information to the patient record server device, receive second patient record information input based on a clinical trial, and send the second patient record information to the patient record server device. The patient record server device, in order to receive the patient record, may be further operable to receive the first patient record information from the submission device client; store the first patient record information in a next blockchain; increase, in response to storing the first patient record information, the access fee associated with the patient record; receive the second patient record from the submission device client; store the second record information in the next blockhain; and increase, in response to storing the second patient record information, the access fee associated with the patient record.
[0019] In yet other embodiments of the present invention, the patient record server device of the system, in order to facilitate a clinical trial, may be further operable to receive a plurality of clinical trial patient records from a plurality of submission device clients
corresponding to a plurality of clinical trial patients; group the plurality of clinical trial patient records to form a clinical trial group of patient records; restrict access, to the plurality of clinical trial patient records, to all the member device clients except for member device clients identified as clinical trial sponsor member device clients; receive information signaling the end of clinical trial; and providing access to the clinical trial patient records to other member device clients.
[0020] In some embodiments of the present invention, a method of securely storing and retrieving encrypted biological specimen data may comprise receiving a patient record from a submission device client, sending a confirmation of receipt of the patient record to the submission device client, receiving patient profile information from a member device client, determining search results based on the patient profile information, and sending information indicating the search results to the member device client.
[0021] In yet other embodiments of the present invention, the method may further comprise storing a patient record provider credit in a next patient blockchain, sending a first confirmation of the patient record provider credit to the submission device client, storing a member device client debit in the next patient blockchain, sending a second confirmation of the member device client debit to the member device client, and storing an operator credit in the next patient blockchain.
[0022] In yet other embodiments of the present invention, the method may further comprise receiving mined information from the member device client, storing the mined information in a next member blockchain, and sending a confirmation of storage of the mined information to the member device client.
[0023] In yet other embodiments of the present invention, the method may further comprise assigning an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
[0024] In yet other embodiments of the present invention, the method may further comprise receiving first patient record information from the submission device client; storing the first patient record information in a next blockchain; increasing, in response to storing the first patient record information, the access fee associated with the patient record; receiving second patient record from the submission device client; storing the second record information in the next blockchain; and increasing, in response to storing the second patient record information, the access fee associated with the patient record.
[0025] In yet other embodiments of the present invention, receiving a plurality of clinical trial patient records from a plurality of submission device clients corresponding to a plurality of clinical trial patients; grouping the plurality of clinical trial patient records to form a clinical trial group of patient records; restricting access, to the plurality of clinical trial patient records, to all the member device clients except for member device clients identified as clinical trial sponsor member device clients; receiving information signaling the end of clinical trials; and providing access to the clinical trial patient records to other member device clients. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] FIG. 1 is an overview system diagram illustrating an exemplary distributed system for securely storing and retrieving encrypted biological specimen data.
[0027] FIG. 2A is a network diagram illustrating example components and functions of a distributed system for securely storing and retrieving encrypted biological specimen data according to some embodiments of the present invention.
[0028] FIG. 2B is a network diagram illustrating additional example components and functions of a distributed system for securely storing and retrieving encrypted biological specimen data.
[0029] FIG. 3 is a block diagram of the hardware components comprising a submission device according to some embodiments of the present invention.
[0030] FIG. 4 is a block diagram of the hardware components comprising a member device according to some embodiments of the present invention.
[0031] FIG. 5 is a block diagram of the hardware components comprising a patient record server according to some embodiments of the present invention.
DETAILED DESCRIPTION
[0032] The present disclosure is described with specificity to meet statutory
requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different steps or elements similar to the ones described in this document, in conjunction with other present or future technologies. Moreover, although the term "step" may be used herein to connote different aspects of methods employed, the term should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when the order of individual steps is explicitly described.
[0033] As referred to herein, the term "computing device" should be broadly construed.
In some embodiments, both the submission device 30 and member device 50 may be considered computing devices. It can include any type of mobile device, for example, a smart phone, a cell phone, a pager, a personal digital assistant (PDA, e.g., with GPRS NIC), a mobile computer with a cellular radio, or the like. A typical mobile device is a wireless data access-enabled device (e.g., an iPHONE® smart phone, a BLACKBERRY® smart phone, a NEXUS ONE™ smart phone, an iPAD™ device, or the like) that is capable of sending and receiving data in a wireless manner using protocols like the Internet Protocol, or IP, and the wireless application protocol, or WAP. This allows users to access information via wireless devices, such as smart phones, mobile phones, pagers, two-way radios, communicators, and the like. Wireless data access is supported by many wireless networks, including, but not limited to, CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, ReFLEX, iDEN, TETRA, DECT, DataTAC, Mobitex, EDGE and other 2G, 3G, 4G and LTE technologies, and it operates with many handheld device operating systems, such as PalmOS, EPOC, Windows CE, FLEXOS, OS/9, JavaOS, iOS and Android. Typically, these devices use graphical displays and can access the Internet (or other communications network) on so-called mini- or micro-browsers, which are web browsers with small file sizes that can accommodate the reduced memory constraints of wireless networks. In a representative embodiment, the mobile device is a cellular telephone or smart phone that operates over GPRS (General Packet Radio Services), which is a data technology for GSM networks. In addition to a conventional voice communication, a given mobile device can communicate with another such device via many different types of message transfer techniques, including SMS (short message service), enhanced SMS (EMS), multi-media message (MMS), email WAP, paging, or other known or later-developed wireless data formats. Although many of the examples provided herein are implemented on a mobile device, the examples may similarly be implemented on any suitable "computing device".
[0034] Throughout this specification, like reference numbers signify the same elements throughout the description of the figures.
[0035] When elements are referred to as being "connected" or "coupled," the elements can be directly connected or coupled together or one or more intervening elements may also be present. In contrast, when elements are referred to as being "directly connected" or "directly coupled," there are no intervening elements present.
[0036] The subject matter may be embodied as devices, systems, methods, and/or computer program products. Accordingly, some or all of the subject matter may be embodied in hardware and/or in software (including firmware, resident software, micro-code, state machines, gate arrays, etc.) Furthermore, the subject matter may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this document, a computer-usable or computer- readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
[0037] The computer-usable or computer-readable medium may be for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. By way of example, and not limitation, computer- readable media may comprise computer storage media and communication media.
[0038] Computer storage media includes volatile and nonvolatile, removable and nonremovable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and may be accessed by an instruction execution system. Note that the computer-usable or computer-readable medium can be paper or other suitable medium upon which the program is printed, as the program can be electronically captured via, for instance, optical scanning of the paper or other suitable medium, then compiled, interpreted, of otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
[0039] Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" can be defined as a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above-mentioned should also be included within the scope of computer-readable media.
[0040] When the subject matter is embodied in the general context of computer- executable instructions, the embodiment may comprise program modules, executed by one or more systems, computers, or other devices. Generally, program modules include routines, programs, objects, components, data structures, and the like, that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.
[0041] Operating environments in which embodiments of the present disclosure may be implemented are also well-known. In a representative embodiment, a computing, such as a mobile device, is connectable to a transmission functionality that varies depending on
implementation. Thus, for example, where the operating environment is a wide area wireless network (e.g., a 2.5G network, a 3G network, or a 4G network), the transmission functionality comprises one or more components such as a mobile switching center (MSC) (an enhanced ISDN switch that is responsible for call handling of mobile subscribers), a visitor location register (VLR) (an intelligent database that stores on a temporary basis data required to handle calls set up or received by mobile devices registered with the VLR), a home location register (HLR) (an intelligent database responsible for management of each subscriber's records), one or more base stations (which provide radio coverage with a cell), a base station controller (BSC) (a switch that acts as a local concentrator of traffic and provides local switching to effect handover between base stations), and a packet control unit (PCU) (a device that separates data traffic coming from a mobile device). The HLR also controls certain services associated with incoming calls. Of course, the present disclosure may be implemented in other and next-generation mobile networks and devices as well. The mobile device is the physical equipment used by the end user, typically a subscriber to the wireless network. Typically, a mobile device is a 2.5G-compliant device, 3G-compliant device, or a 4G-compliant device) that includes a subscriber identity module (SIM), which is a smart card that carries subscriber-specific information, mobile equipment (e.g., radio and associated signal processing devices), a user interface (or a man- machine interface (MMI), and one or more interfaces to external devices (e.g., computers, PDAs, and the like). The mobile device may also include a memory or data store. The presently disclosed subject matter is now described in more detail.
[0042] Referring now to FIG. 1, in some embodiments of the present invention, a distributed system for storing and retrieving encrypted biological specimen data may be comprised of a plurality of submission devices 30, a plurality of member devices 50, and a plurality of patient record server devices 70. The submission devices 30 may represent the devices used to perform submission of the patient records. The member devices 50 may represent the devices used by members (e.g., pharmaceutical companies, medical research companies, academic organizations, etc.) to access the patient records. The patient record servers 70 may represent the devices that together host the patient records in a secure and distributed manner using blockchain technology.
[0043] The submission device 30 may be comprised of a control system 32, UI Function
34, communication function 36, and a submission function 38. The private key may be stored in the key repository 40, along with the respective patient record 42 for the submission device 30. The UI function may provide the user interface controls allowing a user of the system to interact with the submission device 30. The communication function 36 may work with the
communication interfaces 308 to provide communications for the submission device 30. The submission function 38 may send the patient record collected at the submission device 30 to the patient record servers 70.
[0044] The member device 50 may be comprised of a control system 52, UI Function 54, communication function 56, and an access function 58. The private key may be stored in the key repository 60, along with the respective patient records 62 for the member device 50. The UI function 54 may provide the user interface controls allowing a user of the system to interact with the member device 50. The communication function 56 may work with the communication interfaces 408 to provide communications for the member device 50. The submission function 58 may receive the patient records collected at the patient record servers 70.
[0045] The patient record servers 70 may be comprised of a control system 72, UI
Function 74, communication function 76, and an access function 78. The owner repository 80 may store administrative information for the patient record servers 70. The member repository 82 may store information about the member devices 50 accessing the patient record servers 70. The patient record repository 84 may store the patient record information 42 received from the submission devices 30. The private and public keys may be stored at in the key repository 60, along with the respective patient records 62 for the member device 50. The record intake function 74 may operate to receive the patent records 42 from the submission device 30. The record access function 76 may operate to receive request for and send data in response to access to patient records 42 stored in the patient record repository 84. The communication function 77 may work with the communication interfaces 508 to provide communications for the patient record server 70. The access key generation function 78 may provide access keys to the submission devices 30 and member devices 50.
[0046] Those of ordinary skill in the art will appreciate that the network 20 is not limited by the implementations listed above. More specifically, the network 20 may be any type of network 20 suitable to allow interaction between the submission devices 30, member devices 50, and the patient record servers 70. For example, the network 20 may be a wired network, a wireless network, or any combination thereof. Further, the network 20 may include a distributed computing network, an intranet, a local-area network (LAN) and/or a wide-area network (WAN), or any combination thereof.
[0047] FIG. 2 depicts the network traffic on a distributed system for storing and retrieving encrypted biological specimen data according to at least one embodiment of the present invention. The submission device 30 may request 202 and receive keys 204 from the patient record servers 70. Patient data may be received 206 at the submission device 30 and sent 208 to the patient record servers 70. The patient record servers 70 may work together to add the patient records to the patient record repository 804 as part of the next blockchain 212. A confirmation of the recordation may be provided to the submission device 30. A member device 50 may receive information indicating profiles to be matched 214. The member device 50 may request access to patient data for patients matching the profile 216, and access keys may be sent to the member device 50 enabling access. Data may be requested by the member device 50 from the patient record servers 70. Payment from the member to the infrastructure operator(s) may be authorized 220. The requested data may be received 222 at the member device 50. The member device 50 may then proceed to mine the data 224. The member's account may then be debited 226 for access to the data and proof of the transaction may be recorded in the next blockchain 228. Confirmation of the member debit may be received 229 at the member device 50. The patient's account may be credited 230 for providing the data and proof of the transaction may be recorded in the next blockchain 232. Confirmation of the patient credit may be received 233 at the submission device 30. The infrastructure provider's account may be credited 234 for enabling the patient/member transaction and proof of the transaction may be recorded in the next blockchain 236. Confirmation of the provider credit may be received 237 at the submission device 30. The member device 50 may request storage of the mined results at the patient record servers 70. Confirmation of the storage may be received 242 at the member device 50. [0048] Referring now to FIG. 3, a block diagram of a submission device 30 according to at least one embodiment of the present invention is shown. As illustrated, the submission device 30 includes a controller 304 connected to memory 306, one or more communications interfaces 308, one or more user interface components 310, one or more storage devices 312, and a location module 314 by a bus 302 or similar mechanism. The controller 304 is a microprocessor, digital ASIC, FPGA, or the like. In general, the submission device 30 includes a control system 32 having associated memory 306. In this embodiment, the controller 304 is a microprocessor, and the UI function 34, communications function 36, and submission function 38 are implemented in software and stored in the memory 306 for execution by the controller 304. However, the present disclosure is not limited thereto. The aforementioned functions and engine may be implemented in software, hardware, or a combination thereof. The submission device 30 also includes a communication interface 308 enabling the submission device 30 to connect to the network 20. The one or more user interface components 310 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof. The storage device(s) 312 is a non-volatile memory. In this embodiment, the location module 314 is a hardware component, such as a GPS receiver. However, the present invention is not limited thereto.
[0049] FIG. 4 is a block diagram of a member device 50 according to one embodiment of the present disclosure. As illustrated, the member device 50 includes a controller 404 connected to memory 406, one or more communications interfaces 408, one or more user interface components 410, one or more storage devices 412 by a bus 402 or similar mechanism. The controller 404 is a microprocessor, digital ASIC, FPGA, or the like. In general, the member device 50 includes a control system 52 having associated memory 406. In this embodiment, the controller 404 is a microprocessor, and the and the UI function 54, communications function 56, and access function 58 are implemented in software and stored in the memory 406 for execution by the controller 404. However, the present disclosure is not limited thereto. The aforementioned functions may be implemented in software, hardware, or a combination thereof. The member device 50 also includes a communication interface 408 enabling the reference member device 50 to connect to the network 20. The one or more user interface components 410 include, for example, a touchscreen, a display, one or more user input components (e.g., a keypad), a speaker, or the like, or any combination thereof. The storage device(s) 412 is a non- volatile memory.
[0050] FIG. 5 is a block diagram of a comparison server device 70 according to an embodiment of the present disclosure. As illustrated, comparison server device 70 includes a controller 504 connected to a memory 506, one or more secondary storage devices 512, and one or more communications interfaces 508 by a bus 502 or similar mechanism. The controller 504 is a microprocessor, digital Application Specific Integrated Circuit ASIC, Field Programmable Gate Array FPGA, or the like. In general, the comparison server device 70 includes a control system 72 having associated memory 506. In this embodiment, the controller 504 is a
microprocessor, and the record intake function 74, record access function 76, and access key generation 78 is implemented in software and stored in the memory 506 for execution by the controller 504. However, the present disclosure is not limited thereto. The aforementioned engine may be implemented in software, hardware, or a combination thereof. Further, the owner repository 80, member repository 82, and patient record repository 84 may be stored in the one or more secondary storage devices 512. The secondary storage devices 512 are digital data storage devices such as, for example, one or more hard disk drives. The comparison server device 70 also includes a communication interface 508 enabling the comparison server device 70 to connect to the network 20.
[0051] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.

Claims

CLAIMS What is claimed is:
1. A distributed system for secure storage and retrieval of encrypted biological specimen data comprising:
a submission device client operable to:
send, to a patient record server device, a patient record; and
receive, from the patient record server device, a confirmation of receipt of the patient record; and
the patient record server device comprising:
a first processor and first memory, the patient record server device operable to:
receive, from the submission device client, the patient record;
send, to the submission device client, the confirmation of receipt of the patient record;
receive, from a member device client, patient profile information;
determine search results based on the patient profile information; and send, to the member device client, information indicating the search results; and the member device client operable to:
send, to the patient record server device, the patient profile information;
receive, from the patient record server device, the information indicating the search results based on the patient profile information; and
receive the search results based on the information indicating the search results.
2. The system of claim 1, further comprising:
a submission device comprising:
a second processor and second memory, the submission device operable to:
execute the submission device client; and
a member device comprising:
a third processor and third memory, the memory device operable to:
execute the member device client;
The system of claim 1, further comprising:
the submission device client further operable to:
receiving a first confirmation of a patient record provider credit from the patient record server device; and
the patient record server device further operable to:
store the patient record provider credit in a next patient blockchain;
send the first confirmation of the patient record provider credit to the submission device client;
store a member device client debit in the next patient blockchain;
send a second confirmation of the member device client debit to the member device client; and
store an operator credit in the next patient blockchain; and
the member device client further operable to:
receive the second confirmation of the member device client debit from the patient record server device.
The system of claim 1, further comprising:
the patient record server device further operable to:
receive, from the member device client, mined information;
store the mined information in a next member blockchain; and
send, to the member device client, a confirmation of storage of the mined information; and
the member device client further operable to:
mine the search results to extract mined information;
send, to the patient record server, the mined information; and
receive, from the patient record server, confirmation of the storage of the mined information.
The system of claim 1, further comprising:
the patient record server device further operable to: assign an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
The system of claim 1, further comprising:
the submission device client, in order to send the patient record, further operable to:
receive first patient record information input based on a clinical trial;
send the first patient record information to the patient record server device;
receive second patient record information input based on a clinical trial; and send the second patient record information to the patient record server device; and the patient record server device, in order to receive the patient record, further operable to: receive the first patient record information from the submission device client;
store the first patient record information in a next blockchain;
increase, in response to storing the first patient record information, the access fee associated with the patient record;
receive the second patient record information from the submission device client; store the second record information in the next blockchain; and
increase, in response to storing the second patient record information, the access fee associated with the patient record.
The system of claim 1, further comprising:
the patient record server device, in order to facilitate a clinical trial, further operable:
receive a plurality of clinical trial patient records from a plurality of submission device clients corresponding to a plurality of clinical trial patients;
group the plurality of clinical trial patient records to form a clinical trial group of patient records;
restrict access, to the plurality of clinical trial patient records, to all the member device clients except for member device clients identified as clinical trial sponsor member device clients;
receive information signaling the end of clinical trial; and
provide access to the clinical trial patient records to other member device clients.
8. A patient record server device comprising:
a processor and a memory, the patient record server device operable to:
receive, from a submission device client, a patient record;
send, to the submission device client, the confirmation of receipt of the patient record; receive, from a member device client, patient profile information;
determine search results based on the patient profile information; and
send, to the member device client, information indicating the search results.
9. The patient record server device of claim 8, wherein the patient record server device is further operable to:
store the patient record provider credit in a next patient blockchain;
send the first confirmation of the patient record provider credit to the submission device client;
store a member device client debit in a next patient blockchain;
send a second confirmation of the member device client debit to the member device client; and
store an operator credit in the next patient blockchain.
10. The patient record server device of claim 8, wherein the patient record server device is further operable to:
receive, from the member device client, mined information;
store the mined information in a next member blockchain; and
send, to the member device client, a confirmation of storage of the mined information.
11. The patient record server device of claim 8, wherein the patient record server device is further operable to:
assign an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
12. The patient record server device of claim 8, wherein the patient record server device is further operable to: receive a first patient record information from the submission device client;
store the first patient record information in a next blockchain;
increase, in response to storing the first patient record information, the access fee associated with the patient record;
receive a second patient record from the submission device client;
store the second record information in the next blockchain; and
increase, in response to storing the second patient record information, the access fee associated with the patient record.
13. The patient record server device of claim 8, wherein the patient record server device is further operable:
receive a plurality of clinical trial patient records from a plurality of submission device clients corresponding to a plurality of clinical trial patients;
group the plurality of clinical trial patient records to form a clinical trial group of patient records;
restrict access, to the plurality of clinical trial patient records, to all the member device clients except for member device clients identified as clinical trial sponsor member device clients;
receive information signaling the end of clinical trial; and
provide access to the clinical trial patient records to other member device clients.
14. A method of securely storing and retrieving encrypted biological specimen data comprising:
receiving a patient record from a submission device client,
sending a confirmation of receipt of the patient record to the submission device client, receiving patient profile information from a member device client,
determining search results based on the patient profile information, and
sending information indicating the search results to the member device client.
15. The method of claim 14, further comprising:
storing a patient record provider credit in a next patient blockchain, sending a first confirmation of the patient record provider credit to the submission device client,
storing a member device client debit in the next patient blockchain,
sending a second confirmation of the member device client debit to the member device client, and
storing an operator credit in the next patient blockchain.
16. The method of claim 14, further comprising:
receiving mined information from the member device client,
storing the mined information in a next member blockchain, and
sending a confirmation of storage of the mined information to the member device client.
17. The method of claim 14, further comprising:
assigning an access fee to the patient record, the patient record access fee being proportional to the amount of information stored in the patient record.
18. The method of claim 14, further comprising:
receiving first patient record information from the submission device client;
storing the first patient record information in a next blockchain;
increasing, in response to storing the first patient record information, the access fee associated with the patient record;
receiving second patient record from the submission device client;
storing the second record information in the next blockchain; and
increasing, in response to storing the second patient record information, the access fee associated with the patient record.
19. The method of claim 14, further comprising:
receiving a plurality of clinical trial patient records from a plurality of submission device clients corresponding to a plurality of clinical trial patients;
grouping the plurality of clinical trial patient records to form a clinical trial group of patient records; restricting access, to the plurality of clinical trial patient records, to all the member device clients except for member device clients identified as clinical trial sponsor member device clients;
receiving information signaling the end of clinical trials; and
providing access to the clinical trial patient records to other member device clients.
PCT/US2016/062718 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data WO2017087769A1 (en)

Priority Applications (10)

Application Number Priority Date Filing Date Title
AU2016355193A AU2016355193A1 (en) 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data
SG11201803785RA SG11201803785RA (en) 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data
JP2018526509A JP2018538745A (en) 2015-11-18 2016-11-18 Distributed system for secure storage and retrieval of encrypted biological sample data
CA3003885A CA3003885A1 (en) 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data
CN201680067421.3A CN109874340B (en) 2015-11-18 2016-11-18 Distributed system for secure storage and retrieval of encrypted biological specimen data
EP16867203.8A EP3378029A4 (en) 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data
US15/651,302 US10510441B2 (en) 2015-11-18 2017-07-17 Distributed systems for secure storage and retrieval of encrypted biological specimen data
US16/689,421 US11429938B2 (en) 2015-11-18 2019-11-20 Distributed systems for secure storage and retrieval of encrypted biological specimen data
US17/880,278 US20230015147A1 (en) 2015-11-18 2022-08-03 Distributed Systems for Secure Storage and Retrieval of Encrypted Biological Specimen Data
AU2022231751A AU2022231751A1 (en) 2015-11-18 2022-09-15 Distributed systems for secure storage and retrieval of encrypted biological specimen data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562256759P 2015-11-18 2015-11-18
US62/256,759 2015-11-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/651,302 Continuation US10510441B2 (en) 2015-11-18 2017-07-17 Distributed systems for secure storage and retrieval of encrypted biological specimen data

Publications (1)

Publication Number Publication Date
WO2017087769A1 true WO2017087769A1 (en) 2017-05-26

Family

ID=58717927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/062718 WO2017087769A1 (en) 2015-11-18 2016-11-18 Distributed systems for secure storage and retrieval of encrypted biological specimen data

Country Status (8)

Country Link
US (3) US10510441B2 (en)
EP (1) EP3378029A4 (en)
JP (2) JP2018538745A (en)
CN (1) CN109874340B (en)
AU (2) AU2016355193A1 (en)
CA (1) CA3003885A1 (en)
SG (1) SG11201803785RA (en)
WO (1) WO2017087769A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018225428A1 (en) * 2017-06-05 2018-12-13 Ｎｅｃソリューションイノベータ株式会社 Medical record management system, device, method and program
WO2019018776A1 (en) * 2017-07-21 2019-01-24 Patientory, Inc. Blockchain network for secure exchange of healthcare information
JP2019139750A (en) * 2018-02-13 2019-08-22 マクロジェン・インコーポレイテッドＭａｃｒｏｇｅｎ， Ｉｎｃ． Bio-information data providing method, bio-information data storing method and bio-information data transferring system based on multiple blockchains
WO2019241169A1 (en) * 2018-06-11 2019-12-19 Patientory, Inc. System and method for facilitating payment requests within a health care network
WO2020102606A1 (en) * 2018-11-15 2020-05-22 Paypal, Inc. System and method for optimizing data writing to a blockchain
JP2021513179A (en) * 2018-02-12 2021-05-20 ディーエルティー・ラブス・インコーポレイテッド Blockchain-based consent management system and method
WO2021105904A1 (en) * 2019-11-26 2021-06-03 Leica Biosystems Melbourne Pty Ltd Immutable-ledger-based workflow management for patient samples
JP2021526282A (en) * 2018-08-30 2021-09-30 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 Virtual pet information display method and devices, terminals, servers and their computer programs
JP2021530930A (en) * 2018-07-17 2021-11-11 キョン イ，ユン Methods for the storage and utilization of genomes and genomic information
US11429938B2 (en) 2015-11-18 2022-08-30 Global Specimen Solutions Distributed systems for secure storage and retrieval of encrypted biological specimen data

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3553735A4 (en) * 2017-05-02 2019-11-06 Sustainable Medicine, Inc. Security system and node device used in same
CN107770154B (en) * 2017-09-22 2019-08-27 中国科学院信息工程研究所 Block chain reliable data storage method, terminal and system based on cloud storage
KR102079554B1 (en) * 2018-01-12 2020-02-20 전북대학교산학협력단 Method and System for Resource Managing of Clinical Trial using Block Chain
US10505737B1 (en) * 2018-06-04 2019-12-10 Syniverse Technologies, Llc System and method for blockchain-based consent and campaign management
US10721069B2 (en) 2018-08-18 2020-07-21 Eygs Llp Methods and systems for enhancing privacy and efficiency on distributed ledger-based networks
KR20200034020A (en) 2018-09-12 2020-03-31 삼성전자주식회사 Electronic apparatus and control method thereof
US20210402164A1 (en) * 2018-11-20 2021-12-30 Veris Health Inc. Wireless charging, localization, and data communication for implantable vascular access devices
US11769585B2 (en) 2019-01-15 2023-09-26 Youngblood Ip Holdings, Llc Health data exchange platform
US11316691B2 (en) 2019-04-15 2022-04-26 Eygs Llp Methods and systems for enhancing network privacy of multiple party documents on distributed ledger-based networks
US11206138B2 (en) * 2019-05-02 2021-12-21 Ernst & Young U.S. Llp Biosignature-based tokenization of assets in a blockchain
US10461421B1 (en) * 2019-05-07 2019-10-29 Bao Tran Cellular system
US11232439B2 (en) 2019-08-09 2022-01-25 Eygs Llp Methods and systems for preventing transaction tracing on distributed ledger-based networks
WO2021102116A1 (en) 2019-11-20 2021-05-27 Eygs Llp Systems, apparatus and methods for identifying and securely storing distinguishing characteristics in a distributed ledger within a distributed ledger-based network based on fungible and non-fungible tokens
US12099997B1 (en) 2020-01-31 2024-09-24 Steven Mark Hoffberg Tokenized fungible liabilities
CN111462853B (en) * 2020-04-05 2021-03-26 朱礼伟 Mobile medical system and method based on block chain and 5G communication
WO2021211814A1 (en) 2020-04-15 2021-10-21 Eygs Llp Intelligent assertion tokens for authenticating and controlling network communications using a distributed ledger
US11803864B2 (en) 2020-09-28 2023-10-31 Bank Of America Corporation Distributed ledgers for enhanced chain of custody certification

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140215490A1 (en) * 2010-10-22 2014-07-31 Medicity, Inc. Managing Healthcare Information in a Distributed System
US20150205929A1 (en) 2014-01-23 2015-07-23 Dror Samuel Brama Method, System and Program Product for Transferring Genetic and Health Data
US20150220928A1 (en) * 2014-01-31 2015-08-06 Robert Allen Platform for the purchase and sale of digital currency

Family Cites Families (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100250285A1 (en) * 1998-02-18 2010-09-30 Robert Shelton System and method for recruiting subjects for research studies and clinical trials over the internet
US20130197927A1 (en) 2000-05-18 2013-08-01 Carefusion 303, Inc. Healthcare validation system
US7181017B1 (en) 2001-03-23 2007-02-20 David Felsher System and method for secure three-party communications
US7523505B2 (en) 2002-08-16 2009-04-21 Hx Technologies, Inc. Methods and systems for managing distributed digital medical data
JP4975249B2 (en) 2002-10-09 2012-07-11 ボディーメディア インコーポレイテッド Device for measuring an individual's state parameters using physiological information and / or context parameters
CN1856793A (en) * 2003-09-24 2006-11-01 西门子医疗健康服务公司 A medical device management system including a clinical system interface
WO2007014307A2 (en) 2005-07-27 2007-02-01 Medecision, Inc. System and method for health care data integration and management
US20070143148A1 (en) * 2005-12-15 2007-06-21 International Business Machines Corporation Anonymous brokering of patient health records
US10592999B2 (en) * 2006-12-21 2020-03-17 Clinphone Limited Aggregation of compartmentalized clinical trial data
WO2009035687A1 (en) * 2007-09-13 2009-03-19 Matthew Mccord Apparatus, method and system for web-based health care marketplace portal
US8645424B2 (en) * 2007-12-19 2014-02-04 Sam Stanley Miller System for electronically recording and sharing medical information
EP2246798A1 (en) * 2009-04-30 2010-11-03 TomTec Imaging Systems GmbH Method and system for managing and displaying medical data
WO2010131132A1 (en) * 2009-05-15 2010-11-18 Koninklijke Philips Electronics N.V. Clinical decision support systems with external context
US20140316793A1 (en) * 2013-03-14 2014-10-23 nPruv, Inc. Systems and methods for recruiting and matching patients for clinical trials
US20120233141A1 (en) * 2011-03-09 2012-09-13 Mckesson Financial Holdings Apparatus, method and computer-readable storage medium for searching patient studies
US8682049B2 (en) 2012-02-14 2014-03-25 Terarecon, Inc. Cloud-based medical image processing system with access control
US9876775B2 (en) 2012-11-09 2018-01-23 Ent Technologies, Inc. Generalized entity network translation (GENT)
US20140136237A1 (en) * 2012-11-13 2014-05-15 Nicholas G. Anderson Healthcare data management system
WO2014105752A1 (en) 2012-12-28 2014-07-03 Revon Systems, Llc Systems and methods for using electronic medical records in conjunction with patient apps
US20140344015A1 (en) * 2013-05-20 2014-11-20 José Antonio Puértolas-Montañés Systems and methods enabling consumers to control and monetize their personal data
US20150100347A1 (en) 2013-10-04 2015-04-09 Shivprasad Nikam Universal online healthcare marketplace
US20150193583A1 (en) 2014-01-06 2015-07-09 Cerner Innovation, Inc. Decision Support From Disparate Clinical Sources
JP2015138459A (en) * 2014-01-23 2015-07-30 キヤノン株式会社 Information processing device, information processing method, and program
US10340038B2 (en) * 2014-05-13 2019-07-02 Nant Holdings Ip, Llc Healthcare transaction validation via blockchain, systems and methods
US20150356250A1 (en) * 2014-06-04 2015-12-10 Polimeni Medical Infromation Technologies, Llc Method for an Interactive, Patient Controlled Medical Information System in a Digital, Real Time Manner which Features a Single Point of Entry for Patients, Physicians, all other Health Care Providers, Health Care Payers, Researchers and Pharmaceutical Companies
US9836908B2 (en) * 2014-07-25 2017-12-05 Blockchain Technologies Corporation System and method for securely receiving and counting votes in an election
US20160117471A1 (en) * 2014-10-22 2016-04-28 Jan Belt Medical event lifecycle management
US20160188811A1 (en) * 2014-12-31 2016-06-30 Cerner Innovation, Inc. Clinical trial management
US10664923B2 (en) * 2015-03-13 2020-05-26 Gyft, Inc. System and method for establishing a public ledger for gift card transactions
CN106296184A (en) * 2015-06-05 2017-01-04 地气股份有限公司 Electronic money management method and electronic-monetary system
US10346826B2 (en) * 2015-07-28 2019-07-09 Wesley John Boudville Blockchain and deep links for mobile apps
US10366204B2 (en) * 2015-08-03 2019-07-30 Change Healthcare Holdings, Llc System and method for decentralized autonomous healthcare economy platform
US10402792B2 (en) * 2015-08-13 2019-09-03 The Toronto-Dominion Bank Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
CA3003885A1 (en) 2015-11-18 2017-05-26 Global Specimen Solutions, Inc. Distributed systems for secure storage and retrieval of encrypted biological specimen data
US20180130034A1 (en) * 2016-11-07 2018-05-10 LedgerDomain, LLC Extended blockchains for event tracking and management
US20180225424A1 (en) * 2017-02-03 2018-08-09 Q Bio, Inc Iterative medical testing of biological samples
US11631477B2 (en) * 2017-09-07 2023-04-18 Dmitry Shvartsman System and method for authenticated exchange of biosamples

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140215490A1 (en) * 2010-10-22 2014-07-31 Medicity, Inc. Managing Healthcare Information in a Distributed System
US20150205929A1 (en) 2014-01-23 2015-07-23 Dror Samuel Brama Method, System and Program Product for Transferring Genetic and Health Data
US20150220928A1 (en) * 2014-01-31 2015-08-06 Robert Allen Platform for the purchase and sale of digital currency

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Public Disclosure of Clinical Trial Results.", WHO, 14 April 2015 (2015-04-14), XP055384576, Retrieved from the Internet <URL:http://who.int/ictrp/results/en> [retrieved on 20170216] *
See also references of EP3378029A4

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11429938B2 (en) 2015-11-18 2022-08-30 Global Specimen Solutions Distributed systems for secure storage and retrieval of encrypted biological specimen data
WO2018225428A1 (en) * 2017-06-05 2018-12-13 Ｎｅｃソリューションイノベータ株式会社 Medical record management system, device, method and program
WO2019018776A1 (en) * 2017-07-21 2019-01-24 Patientory, Inc. Blockchain network for secure exchange of healthcare information
JP2021513179A (en) * 2018-02-12 2021-05-20 ディーエルティー・ラブス・インコーポレイテッド Blockchain-based consent management system and method
US10560272B2 (en) 2018-02-13 2020-02-11 Macrogen, Inc. Bio-information data providing method, bio-information data storing method and bio-information data transferring system based on multiple blockchains
JP2019139750A (en) * 2018-02-13 2019-08-22 マクロジェン・インコーポレイテッドＭａｃｒｏｇｅｎ， Ｉｎｃ． Bio-information data providing method, bio-information data storing method and bio-information data transferring system based on multiple blockchains
WO2019241169A1 (en) * 2018-06-11 2019-12-19 Patientory, Inc. System and method for facilitating payment requests within a health care network
JP2021530930A (en) * 2018-07-17 2021-11-11 キョン イ，ユン Methods for the storage and utilization of genomes and genomic information
JP7037700B2 (en) 2018-07-17 2022-03-16 キョン イ，ユン Methods for the storage and utilization of genomes and genomic information
JP7090837B2 (en) 2018-08-30 2022-06-27 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 Virtual pet information display method and devices, terminals, servers and their computer programs
JP2021526282A (en) * 2018-08-30 2021-09-30 ▲騰▼▲訊▼科技（深▲セン▼）有限公司 Virtual pet information display method and devices, terminals, servers and their computer programs
US11826661B2 (en) 2018-08-30 2023-11-28 Tencent Technology (Shenzhen) Company Limited Information display method and apparatus for virtual object, terminal, server, and storage medium
WO2020102606A1 (en) * 2018-11-15 2020-05-22 Paypal, Inc. System and method for optimizing data writing to a blockchain
US11922414B2 (en) 2018-11-15 2024-03-05 Paypal, Inc. System and method for optimizing data writing to a blockchain
WO2021105904A1 (en) * 2019-11-26 2021-06-03 Leica Biosystems Melbourne Pty Ltd Immutable-ledger-based workflow management for patient samples
KR20220126718A (en) * 2019-11-26 2022-09-16 라이카 바이오시스템즈 멜버른 피티와이 엘티디 Immutable-ledger-based workflow management for patient samples
JP2022551013A (en) * 2019-11-26 2022-12-06 ライカ・バイオシステムズ・メルボルン・プロプライエタリー・リミテッド Immutable ledger-based workflow management for patient samples
KR102532231B1 (en) 2019-11-26 2023-05-16 라이카 바이오시스템즈 멜버른 피티와이 엘티디 Immutable-ledger-based workflow management for patient samples
JP7303385B2 (en) 2019-11-26 2023-07-04 ライカ・バイオシステムズ・メルボルン・プロプライエタリー・リミテッド Immutable ledger-based workflow management for patient samples

Also Published As

Publication number Publication date
JP2018538745A (en) 2018-12-27
US20200143918A1 (en) 2020-05-07
SG11201803785RA (en) 2018-06-28
AU2016355193A1 (en) 2018-05-24
JP6960017B2 (en) 2021-11-05
CA3003885A1 (en) 2017-05-26
AU2022231751A1 (en) 2022-10-06
EP3378029A4 (en) 2019-07-31
EP3378029A1 (en) 2018-09-26
CN109874340B (en) 2023-06-13
US11429938B2 (en) 2022-08-30
CN109874340A (en) 2019-06-11
US20170316162A1 (en) 2017-11-02
JP2020149721A (en) 2020-09-17
US20230015147A1 (en) 2023-01-19
US10510441B2 (en) 2019-12-17

Similar Documents

Publication Publication Date Title
US11429938B2 (en) Distributed systems for secure storage and retrieval of encrypted biological specimen data
CN109325870B (en) Method and system for sharing private data
US10129028B2 (en) Relational encryption for password verification
US20120303503A1 (en) Systems and Methods for Tokenizing Financial Information
EP3455996A1 (en) Block chain based resource management
WO2012037166A2 (en) Systems and methods for user interaction based on license or other identification information
KR102605710B1 (en) Personal Health Record Share Method Using Blockchain And PKI Technic
US11734257B2 (en) Variation recognition between heterogeneous computer systems
CN101176082A (en) Communication terminal, security device, and integrated circuit
Dargahi et al. Forensics analysis of Android mobile VoIP apps
EP2472819A1 (en) Systems and methods for providing and operating a secure communication network
US20200084186A1 (en) Encrypted Messaging System
WO2019027409A1 (en) Modular data processing and storage system
EP4027678A1 (en) Authorization in cellular communication systems
CN104782099B (en) Certification request accesses the method and system of at least one terminal of at least one resource
US20210240755A1 (en) Variance Detection between Heterogeneous Computer Systems
Chowdhury et al. Distributed identity for secure service interaction
KR20140135997A (en) Systems and methods for encrypted mobile voice communications
AU2014277772A1 (en) Systems and methods for secure short messaging service and multimedia messaging service
US20240080320A1 (en) Server for managing friend list of protected account and operation method of the server

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16867203

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 3003885

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 11201803785R

Country of ref document: SG

WWE Wipo information: entry into national phase

Ref document number: 2018526509

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016355193

Country of ref document: AU

Date of ref document: 20161118

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2016867203

Country of ref document: EP