Insert additional data blocks into the first ledger

By using the hash information and consensus mechanism of data blocks in distributed ledgers, the synchronization and revision of secure storage problems of medical data sets in healthcare applications are solved, and efficient data integrity detection and system security are achieved.

CN112055855BActive Publication Date: 2024-12-03SIEMENS HEALTHINEERS AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980028927.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-02-28
Filing Date
2019-02-25
Publication Date
2024-12-03
Estimated Expiration
2039-02-25

AI Technical Summary

Technical Problem

The prior art is difficult to achieve synchronous and revise secure distributed database storage in healthcare applications, failures of central entities can lead to data accessibility crashes, and there is a risk of errors in authenticating software programs when revising secure storage.

Method used

By using interfaces in a distributed ledger to receive medical data sets and using computing units to determine the hash information of the data blocks, insert them into the ledger, ensuring the invariance and revision security of the data blocks, using hash value detection Manipulate data blocks and improve the security of the system through consensus mechanisms and proof of stake algorithms.

Benefits of technology

The synchronization of revision secure storage of medical data sets and distributed databases is realized, which reduces the risk of system failures, improves the detection ability of data integrity, and enhances the security of data block manipulation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112055855B_ABST
    Figure CN112055855B_ABST
Patent Text Reader

Abstract

The present invention discloses a method for inserting additional data blocks into a first ledger, wherein the first ledger includes data blocks, and the method includes the following steps: receiving additional medical data sets using an interface; determining additional data blocks using a computing unit, wherein the additional data blocks include additional medical data sets and additional linking information, wherein the additional linking information includes a hash of at least one of the data blocks of the first ledger; and inserting the additional data blocks into the first ledger using the computing unit.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to inserting additional data blocks into a first ledger, and in particular, to a method, a block creation unit, and a computer-readable medium for inserting additional data blocks into a first ledger. Background Art

[0002] A prerequisite for using data-driven applications, in particular for data-driven healthcare applications, is that databases can be stored in different entities in a synchronized and revision-safe manner. Examples of such databases are electronic patient records, log files for maintenance operations of medical devices or log files for the use of medical devices.

[0003] In order to store databases at different entities in a synchronized manner, it is known to operate a central agent or central entity that is trusted by the other non-central entities and coordinates and initializes changes to the local databases of the entities, or alternatively, that stores a centralized database that can be accessed by the non-central entities. If such a central entity is used, a failure of the central entity or a failure to communicate with the central entity leads to a breakdown of synchronization or even to a breakdown of data accessibility. Furthermore, if the central entity is compromised, all non-central entities must also be considered compromised.

[0004] In order to store databases in a revision-safe manner, it is known to access these databases only with certified software programs, wherein these certified software programs do not allow retroactive changes to the databases. In this case, a central certification entity is also required, which can be compromised, and during the certification, inadvertent or intentional errors in the program code can be ignored. Summary of the invention

[0005] The problem of the present invention is therefore to provide a solution for creating a synchronized and revised secure distributed medical database.

[0006] This problem is solved by a method, a block creation unit and a computer program product according to the technical solution described herein. Other possible solutions are described in the specification.

[0007] In the following, the solution according to the invention is described with respect to a system, in particular with respect to a claimed block creation unit, and with respect to a corresponding method, in particular with respect to a method for inserting a further data block into a first ledger. Features, advantages or alternative embodiments herein may be assigned to other objects, in particular other claimed objects, and vice versa. In other words, the claims and embodiments regarding the system may be improved with features described or claimed in the context of an embodiment of the method. In this case, the functional features of the method are embodied by the target unit of the system.

[0008] In one aspect, the present invention relates to a method for inserting an additional data block into a first ledger, the method comprising the step of receiving an additional medical data set using an interface, the method further comprising the step of determining the additional data block using a computing unit, wherein the additional data block comprises the medical data set and linking information, wherein the additional linking information comprises a hash of at least one of the data blocks of the first ledger, the method further comprising the step of including the additional data block into the first ledger using the computing unit.

[0009] The inventors have realised that using the described method, a revision of a medical data set can be securely stored in a ledger database. In particular, by using link information comprising a hash value of at least one of the data blocks of a first ledger, a manipulation of at least one of the data blocks can be detected by checking the link information of the first data block. This increases the revision security of the first ledger, since: in order to manipulate at least one of the data blocks, further data blocks included in a later stage and all other possible successors of the further data blocks must also be manipulated.

[0010] In particular, the interface is an interface of the block creation unit. In particular, the computation unit is a computation unit of the block creation unit. In particular, the first ledger may be stored in a memory unit, in particular, in a memory unit of the block creation unit.

[0011] Typically, a ledger is a database of some type. In particular, a ledger is a distributed ledger, which is a decentralized database of some type. In particular, the ledger is distributed in the sense that there are several copies of the ledger (at least in part) in different memory units, wherein the memory units are spatially distributed. The ledger comprises a plurality of records, wherein a plurality of records can be identified by means of database entries. In particular, a plurality of records are organized as data blocks. In particular, the records are created by different entities, in particular by different nodes of the network, and the records are stored with the different entities, in particular, where there are records, the records are stored in different nodes. In other words, the construction and maintenance of the records are usually not performed by a central authority, but independently by the nodes of the network. In a typical case, all nodes of the network maintain a copy of the ledger.

[0012] Typically, updating the ledger is typically based on a consensus mechanism, where the consensus mechanism ensures that different copies of the distributed ledger match, even in the case of delayed communication between entities storing copies of the distributed ledger.

[0013] In general, a data block is the basic data record of a ledger. In particular, a data block is an immutable data structure, which means that a data block cannot be altered or changed. This implies that changes to the ledger can only be performed by adding or removing data blocks.

[0014] In particular, the immutability of the data block can be ensured by storing the hash value of the data block within the data block or outside the data block.

[0015] In particular, a first data block of the ledger and a second data block of the ledger may be linked. The link may be an undirected link or a directed link. In particular, a link between the first data block and the second data block exists if the first data block includes link information related to the second data block and / or if the second data block includes link information related to the first data block.

[0016] In particular, the further data block is a data block of the first ledger.

[0017] A medical data set may include data corresponding to a medical entity, where the medical entity may be a patient, a group of patients, a patient population, a medical professional, a group of medical professionals, a medical institution, a group of medical institutions, and / or the like.

[0018] Generally, a medical professional may be a person who performs or trains on or assists in the diagnosis or treatment of a patient. In addition, a medical professional may also be a person involved in the maintenance or operation of a medical device, medical equipment, or medical facility. In particular, a medical professional may be a physician, technologist, radiologist, nurse, hygienist, or technician.

[0019] A medical institution may be a hospital, a medical research facility, a medical practice, an outpatient clinic, parts of a hospital, a company that develops and / or produces medical devices and / or parts of medical devices, or any group including one or several of the examples mentioned. A medical institution may also be any other institution in a medical context.

[0020] The medical data set may include a medical data record or may be the same as a medical data record. The medical data record may include a medical image data set. Such a medical image data set is acquired from a patient using a medical imaging device, such as a magnetic resonance device, a single photon emission tomography (SPECT) device, a positron emission tomography (PET) device, a computer tomography device, an ultrasound device, an X-ray device, a C-arm device, or a combined medical imaging device formed by any combination of the aforementioned imaging modalities. The medical image data set may also include automatically, semi-automatically or manually generated processing information, such as segmented organs, contour information, registration information, etc.

[0021] The medical data record may also include medical data obtained or obtained from other medical devices that are not medical imaging devices. Such other medical devices may be, for example, therapeutic devices, such as radiotherapy devices, lithotripsy devices, laser therapy devices, infusion pumps, or interventional therapy devices. Medical data may also originate from equipment for critical care medicine, mobile monitoring devices, respiratory devices, anesthesia machines, ECG devices, EEG devices, blood pressure measurement devices, infusion devices, or dialysis devices. Medical data records may also include laboratory diagnoses or genetic information.

[0022] A medical data record may also include all or part of a patient's electronic health record. Thus, a medical data record may include information about a patient's disease history. A medical data record may also contain annotation information that describes automatically, semi-automatically, or manually generated diagnostic findings in a medical data set. A medical data record may also include demographic metadata about a patient, such as gender, age, weight, size, etc.

[0023] Other medical data that can be considered by a person skilled in the art may also be part of the medical data record.

[0024] Further examples for medical data sets and medical data records may also be found in different embodiments of the invention described in the following description.

[0025] The additional medical data set is a medical data set. In particular, the additional medical data set is a medical data set that is not yet included in the data block of the first ledger.

[0026] If the data block comprises data related to a medical data set, then the data block comprises a medical data set. In particular, the data related to the medical data set may be a link to the medical data set, wherein the medical data set is not stored in the data block but is stored at another location. In particular, the other location may be a web server or a cloud storage. In particular, the data related to the medical data set is the medical data set. In particular, the data related to the medical data set is a hash value of the medical data set.

[0027] If the further data block comprises data relating to the further medical data set, the further data block comprises the further medical data set.

[0028] For the present invention, it is not necessary that the further linking information comprises a hash of at least one of the data blocks of the first ledger. The use of the hash of at least one of the data blocks allows verification that after determining the linking information, in particular after determining the hash, the at least one of the data blocks has not been changed. In other words, within the claims and throughout the application, the term "hash of at least one of the data blocks" can be replaced by the term "data integrity information of at least one of the data blocks". In particular, by means of the data integrity information of at least one of the data blocks, manipulations and / or changes of the at least one of the data blocks can be identified or determined. For the same reasons, for linking information different from the further linking information, within the claims and throughout the application, the term "hash of at least one of the data blocks" can be replaced by the term "data integrity information of at least one of the data blocks".

[0029] The term “hash value based on the data block of the first ledger” may be used as a synonym for “hash of the data block of the first ledger”. In particular, the hash of the data block of the first ledger may be a hash of only a subset of information contained in the data block of the first ledger. In particular, the hash of another data block of the first ledger contained in another data block may be a hash of a subset of information contained in the another data block combined with a subset of information contained in the another data block.

[0030] The further linking information or another linking information is related to at least one of the data blocks of the first ledger by including a hash of at least one of the data blocks of the first ledger. Therefore, the term "the further linking information is related to the data block" may be used as a synonym for "the further linking information includes the hash information of the data block".

[0031] The additional data block may also include a number of additional linking information, each of which includes a hash of another data block of the first ledger; the additional linking information may also include a hash of several other data blocks of the ledger. Equivalently, the data block of the first ledger may also include a number of additional linking information, each of which includes a hash of another data block of the first ledger, and the linking information of the data block of the first ledger may also include a hash of several other data blocks of the ledger. The linking information contained in the data block of the first ledger may include a hash of the data block.

[0032] In particular, if the linking information comprises a hash, the linking information may be identical to the hash. In particular, if the further linking information comprises a hash, the further linking information may be identical to the hash.

[0033] Typically, a hash of a data block is the result of applying a hash function to the data block, the result of applying a hash function to a subset of information contained in the data block, or the result of applying a hash function to a combination of a first subset of information contained in the data block and a second subset of information, wherein the second subset of information is a subset of the information of the data block that contains or will contain the hash.

[0034] In general, a hash function is a function that maps data of arbitrary size to data of fixed size. In particular, the hash function is a cryptographic hash function. In particular, a cryptographic hash function is a deterministic function; in particular, the output of the hash function depends only on the input of the hash function. In particular, a cryptographic hash function can be calculated in a fast manner for all input values. In particular, a cryptographic hash function is only brute-force reversible, that is, given the output of the cryptographic hash function, the corresponding input of the cryptographic hash function can only be calculated by calculating the cryptographic hash function for a large number of input values ​​(i.e., a brute-force attack). In other words, finding an input value that corresponds to the output value of the cryptographic hash function is an intractable problem.

[0035] In particular, finding a first input value and a second input value of a cryptographic hash function that result in the same output value is an intractable problem. In particular, cryptographic hash functions are decentralized; that is, even related inputs to the cryptographic hash function result in unrelated outputs of the cryptographic hash function.

[0036] In particular, the hash function can calculate the Merkle root of the input data by calculating the hash within a Merkle tree.

[0037] In particular, if the second data block includes link information related to the first data block, the first data block is represented as a parent data block or parent of the second data block. In this case, the second data block is represented as a child data block or child of the first data block. Another term for a parent data block is "directly before the data block" or "direct predecessor". Another term for a child data block is "directly after the data block" or "direct successor".

[0038] In particular, a first data block is represented as a previous data block or predecessor of a second data block if there is a third data block such that the first data block is a parent data block or predecessor data block of the third data block and such that the third data block is a parent data block or predecessor data block of a second data block. In this case, the second data block is represented as a subsequent data block or successor of the first data block. In other words, a first data block is a predecessor of a second data block (or equivalently, a second data block is a successor of a first data block) if there is an unbroken chain of linking information from the second data block to the first data block, possibly involving other data blocks.

[0039] In particular, the ledger may be incorporated into the structure of a mathematical graph. In this case, each of the data blocks corresponds to a graph node, and the link information contained in the second data block about the first data block corresponds to a directed graph edge from the second graph node to the second graph node, wherein the first graph node corresponds to the first data block, and wherein the second graph node corresponds to the second data block.

[0040] Typically, inserting the further data block into the first ledger means storing the further data block as an additional data block of the first ledger. In particular, the further data block is stored in the same memory location where at least one of the data blocks of the first ledger has already been stored.

[0041] According to another aspect of the invention, a first ledger includes data blocks, wherein each of the data blocks includes a medical data set and linking information, wherein the linking information includes a hash of at least one of the data blocks of the first ledger. The inventors recognized that linking the data blocks of the first ledger using the hash of the data blocks allows for detecting changes to the first ledger and renders the first ledger revision-safe.

[0042] According to another aspect of the invention, a method for inserting a further block of data into a first ledger comprises the step of receiving the first ledger using an interface. The inventors have realised that by receiving the first ledger when performing the method, the first ledger does not need to be permanently stored in a memory unit.

[0043] In particular, the calculation unit is a calculation unit of the block creation unit. In particular, the step of receiving the first ledger can be performed before or after the step of receiving the further medical data set. In particular, the step of receiving the first ledger can also be performed in parallel with the step of receiving the further medical data set. In other words, the step of receiving the first ledger and the step of receiving the further medical data set are independent.

[0044] According to another aspect of the present invention, a method for inserting an additional data block into a first ledger comprises the following steps: selecting a parent data block from the data blocks of the first ledger by means of a computing unit; wherein the additional linking information comprises a hash of the parent data block. The inventors have recognized that by selecting the parent data block, the structure of the ledger can be determined flexibly, and in particular by selecting the parent data block, it can be selected that the content of its data block should be verified by the additional linking information of the additional data block.

[0045] In particular, the calculation unit is a calculation unit of the block creation unit. In particular, the step of selecting a parent data block can be performed before or after the step of receiving the further medical data set. In particular, the step of selecting a parent data block can also be performed in parallel with the step of receiving the further medical data set. In other words, the step of selecting a parent data block and the step of receiving the further medical data set are independent.

[0046] According to another aspect of the invention, there is no successor data block of the parent data block. In other words, the parent data block is selected from a subset of data blocks of the first ledger, wherein for each data block of the subset of each data block, there is no successor data block. The inventors have realized that by selecting parent data blocks from data blocks that have no successors, a longer chain of data blocks is generated within the first ledger, which makes it more difficult for an attacker to manipulate the ledger.

[0047] According to another aspect of the invention, wherein the first ledger includes a starting data block, and wherein the parent data block is selected based on the distance of the parent data block from the starting data block. In particular, the probability of selecting a data block of the first ledger as a parent data block decreases as the distance from the starting data block increases. The inventors have recognized that by selecting a parent data block based on the distance of the parent data block from the starting data block, a longer chain of data blocks is generated within the first ledger, which makes it more difficult for an attacker to manipulate the ledger.

[0048] In particular, the starting data block of the data blocks of the first ledger does not include linking information or includes linking information related to itself. In other words, the starting data block is not a successor of another data block in the first ledger. In other words, there is no parent data block of the starting data block in the first ledger.

[0049] In particular, the distance between a first data block and a second data block of a first ledger is the minimum number of links that need to be followed to obtain linking information from the first data block to the second data block. Another term for the distance between a first data block and a second data block is the number of generations between the first data block and the second data block.

[0050] In particular, the distance between a first data block and a first data block is 0. In particular, if the first data block is a parent or a child of the second data block, the distance between the first data block and the second data block is 1. In particular, if the first data block is neither a predecessor nor a successor of the second data block, the distance between the first data block and a second data block different from the first data block is infinite.

[0051] It is also possible to use a constant offset to calculate the distance between all blocks of data in the ledger.

[0052] If the distributed ledger incorporates the structure of a directed mathematical graph, the distance between a first data block and a second data block is a graph distance between a first graph node and a second graph node, wherein the first graph node corresponds to the first data block and the second graph node corresponds to the second data block.

[0053] According to another aspect of the invention, the first ledger includes exactly one starting data block. The inventors have realised that by using a first ledger having exactly one starting data block, a longer chain of data blocks is generated within the first ledger, which makes it more difficult for an attacker to manipulate the ledger.

[0054] According to another aspect of the invention, the parent data block is the data block with the largest distance to the starting data block. In particular, if there are more than one starting data block in the first ledger, the parent data block is the data block with the largest distance to one of the starting data blocks. In particular, if there are more than one starting data block in the first ledger, the parent data block is the data block with the largest sum of distances to all starting data blocks. The inventors have realized that by maximizing the distance to one or several starting data blocks, a longer chain of data blocks is generated within the first ledger, which makes it more difficult for an attacker to manipulate the ledger.

[0055] According to another aspect of the invention, each of the data blocks of the first ledger includes a weight parameter, wherein a parent data block is selected based on its weight parameter. The inventors have recognized that using the weight parameter to select a parent data block can achieve prioritization of data blocks to obtain one or more successors. Since having one or several successor data blocks means that the parent data block is more difficult to manipulate, revision-safe prioritization can also be achieved.

[0056] In general, the weight parameter may correspond to the importance and / or reliability of the data block containing the weight parameter. In particular, the weight parameter may be an integer or a floating point number, and the weight parameter may optionally be restricted to values ​​within an open, semi-open, or closed interval. In particular, the weight parameter of a data block may be based on calculations performed to perform a consensus mechanism.

[0057] In particular, if the step of determining the link information is based on a consensus algorithm, the data block may include a weight parameter. In particular, if the consensus mechanism is proof of work, the weight parameter may be based on a mathematical puzzle to be solved. In particular, if the consensus mechanism is proof of stake, the weight parameter may be based on a stake used to determine the link information. In particular, if the consensus mechanism is proof of storage, the weight parameter may be based on an amount of storage used to determine the link information.

[0058] According to another aspect of the invention, the weight parameter of a data block in the first ledger is based on the weight parameter of a previous data block of the data block. The inventors have recognized that, using cascading weights, prioritization of data blocks to obtain one or more successors can also occur for the next generation of successors, which also helps to revise the security of prioritization.

[0059] According to another aspect of the present invention, the step of selecting a parent data block is based on a Markov chain Monte Carlo algorithm, and wherein the Markov chain Monte Carlo algorithm samples the data blocks of the first ledger based on the weights of the data blocks. The inventors have recognized that using the Markov chain Monte Carlo algorithm, a parent data block can be selected based on its weight without accessing the weights of all or most of the data blocks in the data blocks of the first ledger.

[0060] Typically, a Markov Chain Monte Carlo algorithm generates a sequence of data blocks (possibly containing repetitions) by selecting the next data block in the sequence based on a transition probability. In particular, the transition probabilities are based only on the last data block in the sequence and the next data block in the sequence. In particular, the transition probabilities are selected so that the probability of a data block occurring in the sequence corresponds to a given probability distribution, in particular, to a probability distribution in terms of the weights of the data blocks. In particular, the transition probabilities are selected to satisfy a detailed balance condition.

[0061] According to another aspect of the present invention, the data blocks of the first ledger form a directed acyclic graph. The inventors have realized that by using a directed acyclic graph, a unique temporal and / or causal relationship between data blocks can be formed.

[0062] A directed acyclic graph is a finite directed graph with no direct cycles. In other words, a directed acyclic graph consists of a finite number of vertices and edges, where each edge points from a first vertex to a second vertex, such that there is no way to start at one of the graph's vertices and follow a consistent directed sequence of edges that cycles back to that vertex. In other words, a directed acyclic graph is a directed graph with a topological order.

[0063] If the blocks of the first ledger are interpreted as nodes of a graph, the first ledger or the blocks of the first ledger can be interpreted as a graph. If the link information contained in the second data block is related to the first data block, there is an edge pointing from the second data block to the first data block. In this case, the second data block is a successor of the first data block, and the first data block is a parent data block of the second data block.

[0064] According to another aspect of the invention, the further linking information is based on a further medical data set. In particular, the linking information of the data block in the data block of the first ledger is based on the medical data set comprised by the data block. The inventors have recognized that the (further) linking information based on the (further) medical data set makes the manipulation of the (further) data block more difficult.

[0065] According to another aspect of the invention, the further linking information comprises a hash of the further medical data set. In particular, the linking information of a data block in the data block of the first ledger comprises a hash of the medical data set comprised by the data block. The inventors have recognised that the (further) linking information comprising a hash of the (further) medical data set makes manipulation of the (further) data block more difficult.

[0066] According to another aspect of the invention, the further data block comprises a Merkle root of the parent data block and / or the further medical data set.The inventors have realised that using a hash function based on a Merkle root allows for faster verification of the data on which the Merkle root hash is based.

[0067] Typically, a Merkle root is based on a Merkle tree, in particular, a Merkle root is based on the root of a Merkle tree. Typically, a Merkle tree is a tree in which each leaf node comprises a hash of a data item and each non-leaf node comprises a hash of the hashes of its child nodes. An alternative name for a Merkle tree is a hash tree.

[0068] According to another aspect of the invention, determining the further link information comprises executing a consensus algorithm. The inventors have recognized that by using a consensus algorithm, synchronization of the first ledger with another ledger can be ensured, wherein the other ledger is stored in a device that is spatially separated from the block creation unit.

[0069] According to another aspect of the present invention, determining the consensus algorithm includes proof of work, proof of storage, proof of stake and / or proof of elapsed time. In particular, the consensus algorithm is equivalent to proof of work, proof of storage, proof of stake or proof of elapsed time. The inventors recognize that by using such a determination step, on the one hand, a consensus can be reached between several units storing copies of the first ledger, and on the other hand, the revision security of the first ledger can be improved.

[0070] In general, proof of work is a measure of the amount of time required for an entity to perform an action in a system - in particular, for a computer to perform an action within a network - in order to reduce the number of possible actions within a certain time interval. In general, proof of work can also be interpreted as an economic measure to prevent denial of service attacks and other abuses of services such as spam on a network by requiring some work from the system using the service. Typically, the action to be performed is an asymmetric action, meaning that the resources required to perform the action are higher than the resources required to verify that the action has actually been performed. In particular, proof of work can be a challenge-response proof of work or a solution-verification proof of work.

[0071] In particular, the proof of work is a CPU-bound proof of work, a memory-bound proof of work or a network-bound proof of work. In particular, for CPU-bound proof of work, a computing unit, in particular a processor, in particular a central processing unit (acronym “CPU”) has to perform more computational steps in order to execute an action than in order to verify that the action has actually been executed. In particular, for memory-bound proof of work, the size of the memory, in particular a random access memory (acronym “RAM”) or a hard disk (acronym “HD”) required to execute the action is larger than the size of the memory required to verify that the action has actually been executed. In particular, for network-bound proof of work, more communication actions or communication actions with higher latency have to be performed in order to execute the action than in order to verify that the action has actually been executed.

[0072] In particular, for proof of work, in particular for CPU-bound proof of work, the action to be performed is: computing the inverse of a one-way function, in particular by computing the one-way function multiple times and checking whether the result of the one-way function has the desired properties or is equal to the expected value. In general, a one-way function is a function that can be computed by a polynomial time algorithm, but any polynomial time random algorithm that attempts to compute the pseudo-inverse for a one-way function has a negligible probability of success. Examples of one-way functions are products of prime numbers (the inverse is the factorization of an integer), the Rabin function, discrete exponentials (computing exponentials modulo integers, in particular prime numbers, the inverse function is discrete logarithms), cryptographic hash functions, integer multiplication of points on an elliptic curve over a finite field, or one-way functions based on random linear codes or on the subset sum problem.

[0073] In particular, for a memory-bound proof of work, the actions to be performed include computation of a memory-bound function. In particular, for a memory-bound proof of work, the actions to be performed may include finding a cycle or subgraph of a given length in a given random graph or random structure. In particular, without storing or transmitting the entire graph, the graph may be given by giving an initial seed as input to a function, in particular a hash function, so as to efficiently define the graph.

[0074] In particular, the network-constrained proof of work may include communication with several network nodes, wherein access to one or more network nodes is delayed by network latency or by the accessed network. In particular, the network-constrained proof of work may include downloading certain data stored on different network nodes.

[0075] In particular, the proof of work may be based on one of the following methods, problems or functions: computing the square root of an integer modulo a large prime number, Weaken Fiat-Shamir signatures, Ong-Schnorr-Shamir signatures, partial hash inversion, hash sequences, Diffie-Hellman based puzzles, moderate, mbound, Hokkaido, Cuckoo Cycle, Merkle tree based and / or guided tour puzzle protocol.

[0076] A subtype of proof of work is proof of research, where a proof of research is a proof of work whose results can be used for research purposes, particularly in the fields of mathematics, computer science and physics. In particular, a proof of research may include finding a prime number with certain properties. In particular, a proof of research may also include processing a task within a scientific computing grid, such as the CERN grid or within BOINC.

[0077] Generally, proof of storage means that the ability of a block creation unit to create additional blocks or the ability of a computing unit to determine additional link information is based on the amount of data storage provided by the block creation unit. Another name for proof of storage is "proof of capacity".

[0078] In particular, proof of storage may utilize a proof of work mechanism by storing pre-computed results of the proof of work mechanism on a storage medium, wherein the storage medium must be accessed in order to determine additional linking information, and wherein the ability to determine the additional linking information is based on the amount of pre-computed results stored within the storage medium.

[0079] Generally, proof of stake means that only one block creation unit or a small number of block creation units from a plurality of block creation units can determine link information or create blocks that are accepted as valid by other nodes of the network. The selection of one block creation unit or a small number of block creation units can depend on random selection, the amount of digital items assigned to the block creation unit (in other words, the account balance assigned to the block creation unit or associated with the block creation unit), or the age of the digital items assigned to the block creation unit.

[0080] Furthermore, there may be other protocols to select a block creation unit or a small block creation unit, for example by defining certain main block creation units or by introducing checkpoints.

[0081] In particular, a block creation unit or a small number of block creation units may be selected in a random manner based on a hash value of the stake size, for example, by accepting additional data blocks only from one block creation unit having the smallest said hash value, or by accepting additional data blocks only from a small number of block creation units having n smallest said hash values, where n is an integer. Alternatively, proof of stake may also be based on the time at which the stake size, etc., is assigned to a block creation unit or associated with a block creation unit. In particular, proof of stake may be based on a "Slasher" protocol or a "Casper" protocol.

[0082] Typically, ownership can be proven by accessing a private key of an asymmetric encryption key pair including a private key and a public key. In order to prove possession of a private key without publishing the private key, the private key can be used to generate a signature, which can then be published. In particular, if the block creation unit stores the private key, the digital item is assigned to or associated with the block creation unit.

[0083] The advantage of using proof-of-stake consensus is that the hardware cost of executing proof-of-stake can be significantly reduced relative to proof-of-work consensus, which allows the hardware to be widely distributed, thereby increasing robustness against attacks based on hardware distribution. In addition, the total power consumption of the hardware executing proof-of-stake consensus is significantly reduced for using proof-of-stake consensus compared to proof-of-work consensus. In addition, but depending on the actual implementation of the proof-of-stake protocol, the time interval between including additional blocks into the distributed ledger can be reduced compared to the proof-of-work protocol.

[0084] Generally, proof of elapsed time means that a new block is created by a block creation unit, in particular, determining additional linking information is based on the elapsed time in the block creation unit or the calculation unit. In particular, proof of elapsed time can be based on secure instruction execution. In particular, secure instruction execution can be accomplished by using a secure environment and utilizing trusted functions, in particular, a secure hardware environment. Another name for a secure environment is a "trusted execution environment"; an example of a trusted execution environment is the product feature "Software Protection Extension". In particular, a trusted execution environment includes a central processing unit (acronym "CPU") instruction code, and the trusted execution environment allows user-level code to allocate private areas of memory (sometimes referred to as enclaves) that are protected from processes running at a higher privilege level. In particular, proof of elapsed time can be based on a timer or time counting function executed in such an enclave, making it impossible for any other process to manipulate the timer. In particular, the probability for creating a new block or determining additional linking information may be proportional to the elapsed time.

[0085] According to another aspect of the invention, the further data blocks include random numbers, and wherein the consensus algorithm is based on random numbers. In particular, each of the data blocks of the first ledger includes a random number. The inventors have recognized that using a consensus algorithm based on random numbers, the execution of the consensus algorithm can be effectively verified.

[0086] Typically, the random number is a data item that can be arbitrarily selected by the creator of the further data block without affecting the actual content of the further data block. In particular, the use and / or content of the further medical data set is not affected by the choice of the random number. Typically, changing the random number will also change the hash of the further data block.

[0087] In particular, if, in order to perform the consensus algorithm, the random number has to be selected by the creator of the further data block so that the further data block meets certain requirements—in particular, so that the hash of the further data block meets certain requirements—the consensus algorithm is based on random numbers.

[0088] According to another aspect of the present invention, the method for inserting another data block into the first ledger further comprises the following steps: receiving a requirement for a hash of another data block using an interface; and determining a random number of another data block using a computing unit, wherein the hash of the another data block satisfies the requirement. The inventors recognized that by having to determine a random number so that the hash of the other data block satisfies the requirement is an effective consensus algorithm, in particular, an effective proof of work. Since the hash function is a one-way function, the only way to determine the random number is to try different random numbers, possibly a large number of random numbers, but the verification of the execution of the consensus algorithm can be completed by calculating the hash function only once.

[0089] According to another aspect of the invention, wherein the hash of the further data block is a number, wherein the requirement on the hash of the further data block is that the hash of the further data block is less than a predefined number. In particular, each hash that can be stored in the digital memory unit can be interpreted as a binary number. In particular, the requirement can be that the number in a given representation - in particular, the number in a binary representation or a hexadecimal representation - has a certain amount of leading zeros. The inventors realized that this requirement is a requirement that can be easily and quickly checked.

[0090] According to another aspect of the invention, the first ledger is a blockchain, a blocktree and / or a tangle. The inventors have recognized that by using such a ledger, software designed specifically for these types of ledgers can be used, resulting in a faster implementation of the method.

[0091] In particular, if the first ledger is a directed acyclic graph, then the first ledger is a tangle. In particular, if for each data block in the first ledger (except a single starting data block), there is exactly one parent of the data block, then the first ledger is a block tree. In particular, if for each data block in the first ledger (except a single starting data block), there is exactly one successor of the data block in the first ledger; and for each data block in the first ledger (except a block data block), there is exactly one parent of the data block in the first ledger, then the first ledger is a blockchain.

[0092] According to another aspect of the invention, the step of determining the additional link information includes proof of work, and the first ledger is a blockchain. The inventors recognized that by using a blockchain, parent data blocks can be determined quickly and efficiently, and using proof of work consensus makes it particularly difficult for an attacker to forge a distributed ledger.

[0093] According to another aspect of the invention, the step of determining the additional link information includes proof of work, and the first ledger is a block tree. The inventors have recognized that by using a block tree, the hierarchical relationship between medical data sets contained in the data blocks can be more efficiently mapped, and the use of proof of work consensus makes it particularly difficult for an attacker to forge a distributed ledger.

[0094] According to another aspect of the invention, the step of determining the further linking information comprises proof of work, and the first ledger is a tangle. The inventors have realised that by using a tangle, proof of work can be performed in parallel for different data blocks as parent data blocks (particularly if several data blocks from different block creation units are included), making the method more efficient, and using proof of work consensus makes it particularly difficult for an attacker to forge a distributed ledger.

[0095] According to another aspect of the invention, the step of determining the additional linking information includes proof of stake, and the first ledger is a blockchain. The inventors recognized that by using a blockchain, the parent data block can be determined quickly and efficiently, and the proof of stake consensus is used to speed up the calculation of the linking information, making the method faster and more efficient.

[0096] According to another aspect of the invention, the step of determining the additional link information includes proof of stake, and the first ledger is a block tree. The inventors recognized that by using a block tree, the hierarchical relationship between the medical data sets contained in the data blocks can be more efficiently mapped, and the calculation of the link information is accelerated using the proof of stake consensus, thereby making the method faster and more efficient.

[0097] According to another aspect of the invention, the step of determining further linking information comprises proof of stake, and the first ledger is a tangle. The inventors have realised that by using the tangle, the determination of proof of stake or linking information can be performed in parallel for different data blocks as parent data blocks (particularly if several data blocks from different block creation units are included), making the method more efficient, and using proof of stake consensus to speed up the calculation of linking information, making the method faster and more efficient.

[0098] According to another aspect of the invention, the step of determining the additional link information includes proof of elapsed time, and the first ledger is a blockchain. The inventors recognize that by using a blockchain, the parent data block can be determined quickly and efficiently, and by using proof of elapsed time consensus, the energy consumption of the consensus algorithm can be reduced.

[0099] According to another aspect of the present invention, the step of determining the additional link information includes proof of elapsed time, and the first ledger is a block tree. The inventors have recognized that by using a block tree, the hierarchical relationship between medical data sets contained in the data blocks can be more efficiently mapped, and by using proof of elapsed time consensus, the energy consumption of the consensus algorithm can be reduced.

[0100] According to another aspect of the invention, the step of determining the further linking information comprises a proof of elapsed time, and the first ledger is a tangle. The inventors have realised that by using a tangle, the proof of stake or determination of linking information can be performed in parallel for different data blocks as parent data blocks (particularly if several data blocks from different block creation units are included), making the method more efficient, and by using a proof of elapsed time consensus, the energy consumption of the consensus algorithm can be reduced.

[0101] According to another aspect of the invention, the first ledger includes a sidechain, wherein the sidechain is a blockchain, a block tree and / or a tangle. The inventors have recognized that by using sidechains, multiple data blocks can be included in the ledger before executing a possible consensus mechanism.

[0102] According to another aspect of the invention, the first ledger is accessible only from within a trusted network. The inventors have recognized that only allowing access from within a trusted network improves data protection. Furthermore, fraudulent manipulation of the first ledger is more difficult because the manipulating entity must have access to the trusted network.

[0103] Typically, the trusted network includes entities or network nodes authorized by a central authority to access the first ledger and / or include additional data blocks into the first ledger. The central authority does not authorize all other entities or network nodes not included in the trusted network to access the first ledger and / or include additional data blocks into the first ledger. A common name for a first ledger that is accessible only from within a trusted network is a "consortium ledger". In the case where the first ledger is a blockchain, a common name for a first ledger that is accessible only from within a trusted network is a "consortium blockchain". Other known terms are "unlicensed ledger" or "unlicensed blockchain", which are used in contrast to the terms "licensed ledger" or "licensed blockchain".

[0104] According to another aspect of the invention, the further data block and / or the further medical data set comprises a smart contract.

[0105] Typically, a smart contract comprises program elements that can be executed by a block creation unit, in particular a computing unit of the block creation unit or any other device. In particular, the program elements may comprise source code, a scripting language and / or a compiled machine code. In particular, the smart contract may be executed. In particular, the smart contract is recorded in the distributed ledger by recording additional data blocks and / or additional medical data sets in the distributed ledger. In particular, the smart contract may comprise conditions in terms of program logic and results in terms of program logic, wherein the results are activated or executed if certain conditions are met.

[0106] wherein the first account corresponds to an asymmetric key pair including a first private key and a first public key, and wherein the second account corresponds to an asymmetric key pair including a second private key and a second public key, and wherein the transaction log includes at least one of the first private key and the first public key and the second public key.

[0107] According to another aspect of the present invention, a method for inserting an additional data block into a first ledger comprises the following steps: receiving a second ledger with a block verification unit, wherein the second ledger comprises a data block; transmitting the additional data block to the block verification unit with an interface; verifying the additional linking information based on the second ledger with the block verification unit; and inserting the additional data block into the second ledger with a computing unit in the event of a positive verification. The inventors have recognized that even if the block creation unit and the block verification unit are spatially separated, the first ledger and the second ledger can be synchronized with these additional steps.

[0108] In particular, the step of receiving the second ledger is performed using an interface of the block verification unit. In particular, the step of transmitting the further data block is performed using an interface of the block creation unit and an interface of the block verification unit. In particular, the step of verifying the further linking information is performed using a calculation unit of the block verification unit. In particular, the step of inserting the further data block into the second ledger is performed using a calculation unit of the block verification unit.

[0109] According to another aspect of the present invention, each of the data blocks of the second ledger includes a medical data set and link information, wherein the link information includes a hash of at least one of the data blocks of the second ledger. The inventors recognize that through these properties of the second ledger, the integrity of the second ledger can be ensured.

[0110] According to another aspect of the invention, the second ledger comprises at least one parent data block of the further data block, wherein the step of verifying the further linking information is based on at least one parent data block of the further data block. The inventors have recognised that by using verification based on at least one parent data block of the further data block, it is ensured that a correct link between the further data block and the data block in the second ledger can be established, which ensures the integrity of the second ledger after the insertion of the further data block.

[0111] According to another aspect of the invention, in the step of verifying the further linking information, a hash of at least one parent data block is compared with a hash contained in the further linking information. The inventors have recognized that by such a comparison of hashes, the integrity of the second ledger after the insertion of the further data block can be guaranteed.

[0112] According to another aspect of the invention, determining the further linking information comprises execution of a consensus algorithm, wherein verifying the further linking information comprises verifying the actual execution of the consensus algorithm. The inventors have recognized that by verifying the actual execution of the consensus algorithm, fraudulent attacks—particularly attempts to disrupt synchronization of the first ledger and the second ledger—may be complicated or impossible.

[0113] According to another aspect of the invention, a method for inserting a further data block into a first ledger comprises the following steps: receiving a request for a hash of the further data block with a block verification unit, wherein verifying the further linking information comprises verifying that the hash of the further data block satisfies the request. In particular, the step of receiving the request is performed by an interface of the block verification unit. The inventors claim-based verification can be performed quickly and with only a low computational effort.

[0114] According to another aspect of the invention, the hash of the further data block is a number, wherein the requirement for the hash of the further data block is that the hash of the further data block is less than a predetermined number. The verification based on the requirement of less than a predetermined number can be performed quickly and with only a low computational effort.

[0115] The present invention also relates to a method for verifying an additional data block to be inserted into a second ledger, wherein the second ledger includes data blocks, the method comprising the following steps: receiving the second ledger using an interface; receiving an additional data block using an interface, wherein the additional data block includes an additional medical data set and additional linking information, wherein the additional linking information includes a hash of at least one of the data blocks of the second ledger; verifying the additional linking information based on the second ledger using a computing unit; and in the case of positive verification, inserting the additional data block into the second ledger using the computing unit. The inventors realized that the method can synchronize the second ledger with the first ledger even if the block creation unit and the block verification unit are separated in space, wherein the first ledger is stored in the block creation unit that determines the additional data block.

[0116] In particular, the interface is an interface of the block verification unit. In particular, the computation unit is a computation unit of the block verification unit.

[0117] According to another aspect of the present invention, each of the data blocks of the second ledger includes a medical data set and link information, wherein the link information includes a hash of at least one data block of the second ledger. The inventors recognize that through these properties of the second ledger, the integrity of the second ledger can be ensured.

[0118] According to another aspect of the invention, the second ledger comprises at least one parent data block of the further data block, and wherein the step of verifying the further linking information is based on at least one parent data block of the further data block. The inventors have recognised that by using verification based on at least one parent data block of the further data block, it is ensured that a correct link between the further data block and the data block in the second ledger can be established, which ensures the integrity of the second ledger after the insertion of the further data block.

[0119] According to another aspect of the invention, in the step of verifying the further linking information, a hash of at least one parent data block is compared with a hash contained in the further linking information. The inventors have recognized that by such a comparison of hashes, the integrity of the second ledger after the insertion of the further data block can be guaranteed.

[0120] According to another aspect of the invention, the further link information is based on a consensus algorithm, wherein verifying the further link information comprises verifying an actual execution of the consensus algorithm. The inventors have recognized that by verifying an actual execution of the consensus algorithm, fraudulent attacks—particularly, attempts to disrupt synchronization of the first ledger and the second ledger—may be complicated or impossible.

[0121] According to another aspect of the invention, the method for verifying a further data block to be inserted into a second ledger further comprises the step of receiving a requirement for a hash of the further data block using an interface, wherein verifying the further linking information comprises verifying that the hash of the further data block satisfies the requirement. In particular, the step of receiving the requirement is performed by an interface of the block verification unit. The inventors' verification based on the requirement can be performed quickly and with only a low computational effort.

[0122] According to another aspect of the invention, the hash of the further data block is a number, wherein the requirement for the hash of the further data block is that the hash of the further data block is less than a predetermined number. The verification based on the requirement of less than a predetermined number can be performed quickly and with only a low computational effort.

[0123] In another aspect, the invention relates to a block creation unit for inserting a further data block into a first ledger, wherein the first ledger comprises data blocks, the block creation unit comprising the following units:

[0124] - an interface configured for receiving a further medical data set,

[0125] a computing unit configured to determine a further data block, wherein the further data block comprises a further medical data set and further linking information, wherein the further linking information comprises a hash of at least one of the data blocks of the first ledger,

[0126] The computing unit is further configured to insert the further data block into the first ledger.

[0127] In particular, the block creation unit for inserting a further data block into the first ledger can be configured to: perform the method for inserting a further data block into the first ledger according to the present invention and its aspects. The block creation unit is configured to: perform the method and its aspects by means of a computing unit and an interface configured to perform the corresponding method steps.

[0128] The block creation unit may be implemented as a data processing system or a part of a data processing system. Such a data processing system may include, for example, a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The block creation unit may include hardware and / or software. The hardware may be, for example, a processor system, a memory system, and a combination thereof. The hardware may be configured and / or operated by software.

[0129] In another aspect, the invention relates to a medical device comprising a block creation unit.

[0130] In another aspect, the present invention relates to a computer program product comprising a computer program loadable into a memory unit of a block creation unit, the computer program comprising program code segments causing the block creation unit to perform a method for inserting a further data block into a first ledger according to an aspect of the present invention when the computer program is executed in the block creation unit.

[0131] In another aspect, the present invention relates to a computer-readable medium having program code segments of a computer program stored thereon, which can be loaded into a block creation unit and / or can be executed in the block creation unit to cause the block creation unit to perform a method for inserting a further data block into a first ledger according to an aspect of the present invention when the program code segments are executed in the block creation unit.

[0132] Realizing the invention by means of a computer program product and / or a computer-readable medium has the advantage that already existing block creation units can be easily adapted by means of a software update in order to function as proposed by the invention.

[0133] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0134] In another aspect, the invention relates to a block verification unit for verifying a further data block to be inserted into a second ledger, wherein the second ledger comprises the data block, the block verification unit comprising the following units:

[0135] - an interface configured to receive a second ledger,

[0136] The interface is further configured to receive a further data block, wherein the further data block comprises a further medical data set and further linking information,

[0137] wherein the further linking information comprises a hash of at least one of the data blocks of the second ledger,

[0138] - a computing unit configured to verify the further linking information based on the second ledger, the computing unit further configured to insert the further data block into the second ledger in case of positive verification.

[0139] In particular, the block verification unit for verifying the further data block to be inserted into the second ledger can be configured to: perform the method for verifying the further data block to be inserted into the second ledger according to the present invention and its aspects. The block verification unit is configured to: perform the method and its aspects by means of a computing unit and an interface configured to perform the corresponding method steps.

[0140] The block verification unit may be implemented as a data processing system or a part of a data processing system. Such a data processing system may include, for example, a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The block verification unit may include hardware and / or software. The hardware may be, for example, a processor system, a memory system, and a combination thereof. The hardware may be configured by software and / or may not be operated by software.

[0141] In another aspect, the present invention relates to a computer program product comprising a computer program, which can be loaded into a memory unit of a block verification unit, and which includes program code segments that, when the computer program is executed in the block verification unit, cause the block verification unit to perform a method according to an aspect of the present invention for verifying a further data block to be inserted into a second ledger.

[0142] In another aspect, the present invention relates to a computer-readable medium having a program code segment of a computer program stored thereon, which can be loaded into a block verification unit and / or can be executed in the block verification unit so as to cause the block verification unit to perform a method for verifying a further data block to be inserted into a second ledger according to an aspect of the present invention when the program code segment is executed in the block verification unit.

[0143] Realizing the invention by means of a computer program product and / or a computer-readable medium has the advantage that already existing block verification units can be easily adapted by means of a software update in order to function as proposed by the invention.

[0144] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0145] In another aspect, the present invention relates to a ledger synchronization system for inserting an additional data block into a first ledger and a second ledger; comprising a block creation unit according to an aspect of the present invention; and comprising a block verification unit according to an aspect of the present invention.

[0146] In particular, the ledger synchronization system for inserting a further data block into the first ledger and the second ledger may be configured to: perform the method for inserting a further data block into the first ledger and the second ledger according to the present invention and its aspects. The block verification unit is configured to: perform the method and its aspects by means of a block creation unit, in particular an interface and a computing unit of the block creation unit, and a block verification unit, in particular an interface and a computing unit of the block verification unit, configured to perform the corresponding method steps.

[0147] The ledger synchronization system may be implemented as a data processing system or part of a data processing system. Such a data processing system may include, for example, a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The ledger synchronization system may include hardware and / or software. The hardware may be, for example, a processor system, a memory system, and a combination thereof. The hardware may be configured and / or operated by software.

[0148] In another aspect, the present invention relates to a computer program product comprising a computer program loadable into a memory unit of a ledger synchronization system, the computer program comprising program code segments for causing the ledger synchronization system to perform a method for inserting a further data block into a first ledger and a second ledger according to an aspect of the present invention when the computer program is executed in the ledger synchronization system.

[0149] In another aspect, the present invention relates to a computer-readable medium having program code segments of a computer program stored thereon, the program code segments being loadable into a ledger synchronization system and / or executable in the ledger synchronization system to cause the ledger synchronization system to perform a method for inserting a further data block into a first ledger and a second ledger according to an aspect of the present invention when the program code segments are executed in the ledger synchronization system.

[0150] Implementing the invention by means of a computer program product and / or a computer readable medium has the advantage that already existing ledger synchronization systems can be easily adapted by means of a software update to work as suggested by the invention.

[0151] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0152] In the following aspects of the present invention, aspects are described that can be used to record an entity's access to a medical data record, in particular, to create a revised security audit trail of access to a medical data record within a first ledger. In other words, the first ledger is a cumulative log of an entity's access to a medical data record. In particular, such a revised security audit trail or log can be used to: prove that a certain entity has accessed a certain medical data record, and in the case of unauthorized and / or abused access, to sanction an entity that has unauthorized or abused access to a medical data record. In particular, such information can be used to prove a violation of privacy rules, for example, if a person's abuse of access to medical data is not in the patient's interest (for example, because he has a personal relationship with the patient, or if the patient is a public figure). In addition, such an access log may be valuable for insurance cases, for example, to prove that a certain entity (in particular, a physician) actually accessed a certain medical data record, but due to negligence did not identify a diagnosis in a certain medical data record or did not initiate the correct treatment.

[0153] In particular, in the described aspects, the additional data blocks and / or the data blocks contained in the first ledger may have the same structure. In other words, the features and advantageous embodiments described for the additional data blocks may also be applied to the data blocks contained in the first ledger, and vice versa.

[0154] According to another aspect of the invention, the further medical is a log of accesses to medical data records by entities, wherein the further medical data set comprises an identifier of the medical data record and an identifier of the entity accessing the medical data record. The inventors have recognized that this aspect of the invention allows for revision-secure logging of accesses to medical data records. Such a method may be used to check whether a medical professional has accessed only the medical data records that are necessary for him to perform his professional work. Furthermore, such a method may be used to prove in insurance cases that a certain entity has actually accessed a medical data record to prove that the entity has overlooked a finding in the medical data record.

[0155] The identifier of the medical data record may generally be used to unambiguously identify the medical data record. In particular, the identifier of the medical data record may be equivalent to the medical data record. Alternatively, the identifier of the medical data record may be a hash of the medical data record. The identifier of the medical data record may also include other data that allows the medical data record to be unambiguously identified, including, for example, the time when the medical data record was created, the location where the medical data record was created, and / or an identifier of a patient associated with the medical data record.

[0156] In general, an entity may directly or indirectly access data records, in particular medical data records. Thus, an entity may be a person, a group of persons, a legal entity (e.g. a company), a group of legal entities or an object, in particular an information technology object being a server, a client, a storage medium or a computer. In particular, an entity may be a medical professional, such as an employee of a hospital, a physician, a nurse or a technician of a hospital or any group thereof. In particular, an entity may be a hospital, a medical practice or any group thereof.

[0157] The identifier of the entity accessing the medical data record can generally be used to unambiguously identify the entity accessing the medical data record. In particular, if the entity is a person accessing the medical data record, the identifier of the entity may include: the name of the person accessing the medical data record, the birth data of the person accessing the medical data record, the ID of the person accessing the medical data record (e.g., social security number, ID number, driver's license number or passport number) and / or the employer of the person accessing the medical data record. In particular, if the entity is an association (e.g., a hospital), the identifier of the identity may include the name of the association. In particular, the identifier of the entity accessing the medical data record may include the IP address of the computer used by the entity accessing the medical data record. In particular, the identifier of the entity accessing the medical data record may be based on a public key or a private key related to the entity accessing the medical data record.

[0158] According to another aspect of the invention, the identifier of the medical data record is a hash value of the medical data record. The inventors have recognized that the memory requirement of the hash value of the medical data record is less than the memory requirement of the medical data record itself, which results in a reduced memory requirement for the additional data blocks. Furthermore, the hash of the medical data record is sensitive even to small changes in the medical data record, which complicates the falsification and / or manipulation of the medical data record.

[0159] According to another aspect of the invention, the further medical data set further comprises a timestamp corresponding to the time of the entity's access to the medical data record. The inventors have realised that by including a timestamp, the traceability of the access log can be increased.

[0160] According to another aspect of the invention, the identifier of an entity is based on a private key assigned to the entity. Typically, the private key assigned to the entity is not included in the identifier itself, in another data block or in another medical data set. The inventors have recognized that, typically, the private key assigned to an entity is known only to the entity and not to another entity. Therefore, an identifier based on the private key assigned to the entity can only be generated by the entity itself, by a person authorized by the entity or by a technical device belonging to the entity, and cannot be manipulated by another entity.

[0161] According to another aspect of the invention, an identifier of an entity includes a signature signed with a private key assigned to the entity. The inventors recognized that using a signature signed with a private key allows other entities to verify the identifier of a person using a public key associated with the private key assigned to the entity. Furthermore, including a signature signed with a private key assigned to the entity does not expose the private key to another entity.

[0162] In particular, the signature is a digital signature. Typically, the signature relies on an asymmetric key pair, which includes a private key and a public key, which is derived from an asymmetric cryptographic system. If the private key and the public key form an asymmetric key pair, the public key corresponds to the private key or the private key corresponds to the public key.

[0163] In particular, a signature is the output of a signature algorithm, wherein the signature algorithm takes as a first input the data to be signed (also referred to as a "message") and as a second input a private key. In particular, if the private key was used as the second input to the signature algorithm when creating the signature, then the signature is signed using the private key. In particular, if the specific data was used as the first input to the signature algorithm when creating the signature, then the signature is based on specific data.

[0164] In particular, for a signature algorithm, there exists a signature verification algorithm, wherein the signature verification algorithm takes as input a data set, a signature, and a public key, and wherein the output of the signature verification algorithm determines whether a given signature is the output of the signature algorithm applied to a data set with a private key corresponding to a given public key.

[0165] In particular, the signature verification algorithm can verify the validity of the signature without knowing the private key corresponding to the public key. In particular, the private key used to sign the signature cannot be inferred from the signature.

[0166] In particular, a private key is assigned to an entity if the entity has access to the private key and / or if the entity stores the private key in one of its memory units.

[0167] According to another aspect of the invention, the signature is based on a medical data record, in particular, on a hash value of the medical data record. In particular, the signature is equivalent to a medical data record or a hash of a medical data record signed using a private key assigned to an entity. The inventors have realized that by using a signature based on a medical data record, both the entity accessing the medical data record can be identified and the actual value of the medical data record accessed by the entity can be recorded. Therefore, a signature based on a medical data set undoubtedly proves that a certain medical data record has been accessed by a certain entity.

[0168] According to another aspect of the invention, the medical data set further comprises a timestamp corresponding to the time of the entity's access to the medical data record, and wherein the signature is based on the timestamp. The inventors have recognized that the use of a timestamp-based signature unambiguously proves that the access by a certain entity has been performed at the time corresponding to the timestamp.

[0169] According to another aspect of the invention, the step of receiving the further medical data set comprises the following sub-steps: receiving an access request to the medical data record from the entity by means of the interface; and determining the further medical data set based on the access request and based on the data record by means of the computing unit. In particular, the computing unit is a computing unit of the block creation unit. In particular, the interface is an interface of the block creation unit.

[0170] According to another aspect of the invention, a method for inserting a further data block into a first ledger comprises the following steps: performing a check of the entity's authorization to access the medical data record; furthermore, in case of a positive check, granting the entity access. In particular, the method comprises the following steps: in case of a negative check, denying the entity access.

[0171] The inventors have recognised that by combining the checking of an entity's authorisation to access medical data records with the logging of the entity's access to the medical data records, the security of data access is increased.

[0172] According to another aspect of the invention, in case of a negative check, the method comprises the step of denying access to an entity, wherein the medical data set comprises a denial record. In particular, the denial record proves that an entity is denied access. The inventors have realised that by including the denial record into the medical data set, unsuccessful access attempts can be proved, which can be used to track intentional attacks on a system comprising medical data records.

[0173] In the following aspects of the invention, aspects are described that can be used to revise securely recording entity access to medical devices, including local and / or remote access to a certain medical device by a service technician. In other words, an audit trail of entity access to a medical device can be created.

[0174] Such an audit trail can be used, for example, to document the state of a medical device at certain timestamps, for example to track which subcomponents or which software versions have been used in a medical device. This type of documentation can be used to meet legal requirements and to store data relevant to regulatory processes and / or contract performance. Furthermore, such an audit trail can be used to prove that certain service actions have actually been performed, or to record changes to a medical device in order to reconstruct possible sources of errors within the medical device.

[0175] The following aspects of the invention regarding revising securely recording entity access to a medical device may be performed by the medical device or by a block creation unit that oversees the medical device. In other words, the medical device may be the same as the block creation unit, the medical device may include the block creation unit, or the medical device may be different from the block creation unit.

[0176] In particular, in the described aspects, the additional data blocks and / or the data blocks contained in the first ledger may have the same structure. In other words, the features and advantageous embodiments described for the additional data blocks may also be applied to the data blocks contained in the first ledger, and vice versa.

[0177] According to another aspect of the invention, the further medical data set records access of an entity to a medical device, wherein the further medical data set comprises an identifier of the medical device and an identifier of the entity accessing the medical device.

[0178] An entity's access to a medical device is an interaction of the entity with the medical device that may or actually changes the state, preconditions, and / or parameters of the medical device. In particular, the entity's access to the medical device is a service access to the medical device. In particular, the entity's access to the medical device is not a regular use of the medical device.

[0179] Additional medical data sets record an entity's access to a medical device by including data corresponding to the access, which can be used to track or reconstruct access to the medical device.

[0180] In particular, a subset of medical records included in a data block of the first ledger records access by multiple entities to multiple medical devices, each medical record in the subset of medical records records access by one of the multiple entities to one of the multiple medical devices, and the medical record includes an identifier of the one of the multiple medical devices and an identifier of the one of the multiple entities.

[0181] The inventors have realised that using a further medical data set recording an entity's access to medical devices, these accesses can be documented in a revision-safe manner. In particular, the first ledger can then be used as an audit trail access to one or several medical devices in order to track changes to one or several medical devices.

[0182] According to another aspect of the invention, the identifier of the medical device is based on a model number of the medical device and / or a serial number of the medical device.The inventors have realised that a medical device can be effectively identified by reference to its model number and / or serial number.

[0183] According to another aspect of the invention, the additional medical data set further comprises a timestamp corresponding to the time of the entity's access to the medical device. The inventors have realised that by including the timestamp, the traceability of the access log can be increased.

[0184] According to another aspect of the invention, an identifier of an entity is based on a private key assigned to the entity. The inventors have recognized that, in general, a private key assigned to an entity is known only to the entity and not to another entity. Therefore, an identifier based on a private key assigned to the entity can only be generated by the entity itself, a person authorized by the entity or a technical device belonging to the entity, and cannot be manipulated by another entity.

[0185] According to another aspect of the invention, an identifier of an entity includes a signature signed with a private key assigned to the entity. The inventors recognized that using a signature signed with a private key allows other entities to verify the identifier of a person using a public key associated with the private key assigned to the entity. Furthermore, including a signature signed with a private key assigned to the entity does not expose the private key to another entity.

[0186] According to another aspect of the present invention, the signature is based on an identifier of the medical device. The inventors have realized that by using a signature based on the identifier of the medical device, both the entity accessing the medical device can be identified and the actual medical device accessed by the entity can be recorded. Therefore, the signature based on the identifier of the medical device undoubtedly proves that a certain medical device has been accessed by a certain entity.

[0187] According to another aspect of the invention, the additional medical data set further comprises a timestamp corresponding to the time of the entity's access to the medical device and / or corresponding to the time of the entity's departure from the medical device, wherein the signature is based on the timestamp. The inventors have recognized that the use of a signature based on a timestamp unambiguously proves that the access and / or departure of a certain entity has been performed at the time corresponding to the timestamp.

[0188] According to another aspect of the invention, the access to the medical device is remote access.

[0189] In particular, remote access to a medical device is a connection to the medical device from a remote location, for example via a remote access service or a virtual private network, wherein the remote access service comprises a host part installed on the medical device and a remote part installed on a device of an entity accessing the medical device. In particular, the remote access service may comprise a remote desktop application.

[0190] The inventors have realised that remote access to medical devices can be effectively tracked by the method according to this aspect of the invention.

[0191] According to another aspect of the invention, the medical data set includes a time of access to a medical device by an entity, wherein the access time corresponds to a time of establishing remote access to the medical device. In particular, the establishment of remote access occurs after receiving an access request and after granting the access request. The inventors have recognized that the time of establishing remote access to the medical device is the earliest time that a change was made to the medical device remotely and is therefore particularly relevant to tracking changes to the medical device.

[0192] According to another aspect of the invention, the medical data set includes a time when an entity left a medical device, wherein the time of leaving corresponds to a time when remote access to the medical device was terminated. The inventors have recognized that the time when remote access to the medical device was terminated is the latest time when changes were made to the medical device remotely, and is therefore particularly relevant to tracking changes to the medical device.

[0193] According to another aspect of the present invention, the method comprises the following steps: using the interface to send a notification message to the owner of the medical device, wherein the notification message is based on an identifier of the medical device and an identifier of a person accessing the medical device. In particular, the notification message is an electronic message, such as an email or a pop-up window displayed on a display unit of the owner of the medical device.

[0194] In particular, the owner of the medical device may be an entity that is the legal owner of the medical device or an entity entrusted by the legal owner of the medical device. In particular, the owner of the medical device may also be an employee or contractor of the legal owner of the medical device.

[0195] The inventors have recognized that by sending a notification message to the owner of a medical device, the owner can identify remote access to their medical device and take countermeasures in the event of malicious access.

[0196] According to another aspect of the invention, the step of sending the notification message is caused by means of a smart contract. In particular, the smart contract is executed by inserting the additional data block into the first ledger. In particular, the smart contract stipulates that sending the notification message is performed before granting access to the entity or before establishing the remote connection. The inventors have realized that by sending the message by means of a smart contract, the actual sending of the message is ensured, also in the case of malicious access.

[0197] According to another aspect of the invention, access to a medical device by an entity includes a modification to the medical device, wherein the further medical data set includes a record of the modification. The inventors have recognized that by including the further medical data set with a record of the modification, a history of the state of the medical device can be revised securely, and the history of the state of the medical device can be used to reconstruct the state of the medical device at a point in time.

[0198] According to another aspect of the invention, the change comprises installing a hardware component and / or a software component within the medical device, and wherein the medical data set comprises an identifier of the hardware component and / or the software component. In particular, the identifier of the hardware component may be a model and / or a serial number of the hardware component. In particular, the identifier of the software component may be a version number, a hash value of the source code of the software component and / or a hash value of the machine code of the software component. In particular, the software component may comprise source code or binary code or executable code (another term is "machine code"). The inventors have recognized that by tracking the identifiers of the installed hardware components and / or software components, changes to the medical device may be tracked particularly effectively.

[0199] According to another aspect of the invention, the modification comprises removing a hardware component and / or a software component within the medical device, and wherein the medical data set comprises an identifier of the hardware component and / or the software component. The inventors have recognised that by tracking the identifiers of the removed hardware components and / or software components, it is possible to track modifications of the medical device particularly effectively.

[0200] According to another aspect of the invention, the modification comprises a swapping of a first hardware component with a second hardware component, and wherein the medical data set comprises an identifier of the first hardware component and an identifier of the second hardware component, and / or wherein the modification comprises a swapping of a first software component with a second software component, and wherein the medical data set comprises an identifier of the first software component and an identifier of the second software component. The inventors have recognized that by tracking the identifiers of the swapped hardware components and / or software components, modifications of medical devices can be tracked particularly effectively.

[0201] According to another aspect of the invention, the software component is a security update for a medical device. In particular, a security update is a set of changes to a medical device that fixes security vulnerabilities and / or defects. Other terms for "security update" are "patch" or "defect fix". The inventors have recognized that there is a special need in recording an audit trail of security updates because failure to apply security updates may result in an imminent threat to the medical device.

[0202] According to another aspect of the invention, the identifier of the software component comprises a software version number. In particular, the identifier of the first software component comprises the software version number of the first software component, and the identifier of the second software component comprises the software version number of the second software component. The inventors have recognized that the software version number allows for effective identification of software components.

[0203] According to another aspect of the invention, the identifier of the hardware component comprises the model and / or serial number of the hardware component. In particular, the identifier of the first hardware component comprises the model and / or serial number of the first hardware component, and the identifier of the second hardware component comprises the model and / or serial number of the second hardware component. The inventors have recognized that the model and / or serial number allows for effective identification of the hardware components.

[0204] According to another aspect of the invention, an identifier of a hardware component associated with a hardware component is stored. In particular, the identifier of the hardware component is stored on a memory unit of the hardware component. The inventors have recognized that storing the identifier of the hardware component associated with the hardware component enables the identifier of the hardware component to be quickly and easily read out by the medical device.

[0205] According to another aspect of the invention, the hardware component comprises an RFID chip, and wherein an identifier of the hardware component is stored on the RFID chip.The inventors have realised that the RFID chip can be read without a direct connection between the hardware component and a reader device.

[0206] According to another aspect of the invention, the hardware component comprises a one-dimensional or two-dimensional optical code, and wherein an identifier of the hardware component is stored in the one-dimensional or two-dimensional optical code. According to another aspect of the invention, the optical code is a barcode. According to another aspect of the invention, the optical code is a QR code or an Aztec-Code. The inventors have recognized that it is advantageous that the optical code can be read without the use of electromagnetic radiation if the optical code is contained in a shield, wherein the shield blocks electromagnetic radiation.

[0207] According to another possible aspect of the present invention, the modification of the medical device is the use of consumable materials in the medical device and / or the refilling of consumable materials at the medical device. The refilling of consumable materials may also include the replacement of consumable materials.

[0208] Typically, a consumable material of a medical device is a material that is consumed during at least one of the processes performed by the medical device. A consumable material may be completely consumed during a process, alternatively, a consumable material may be only partially consumed during a process, such that the consumable material only needs to be replaced or refilled after a certain number of processes.

[0209] Examples of consumable materials are contrast media for imaging medical devices, reagents for laboratory medical devices, or materials that come into direct contact with the patient during a procedure utilizing the medical device and need to be replaced for hygiene reasons.

[0210] In particular, in the case of refilling, the consumable material can be identified as described above for the hardware replacement section. In particular, the identifier of the consumable material can be included in the additional medical data set. In particular, this can be used to track the use of the consumable material and prevent the use of unauthorized consumable materials.

[0211] The inventors have realized that by storing the use and / or refilling of consumable materials in a distributed ledger, this data can be used to detect the need for additional consumable materials at the medical device and to automatically initiate the refilling of consumable materials to avoid exhaustion of the reserves of consumable materials. In particular, the automatic initiation of the refilling of consumable materials can be performed with the help of smart contracts. This data can additionally be used to compensate for the use of consumable materials without the possibility of manipulating the inventory of consumable materials or their usage.

[0212] According to another possible aspect of the invention, the additional medical data set does not include an identifier of the entity accessing the medical device. In other words, in particular, in the case where the change of the medical device is the use of a consumable material within the medical device and / or the refilling of a consumable material at the medical device, it is not necessary for the additional medical data set to include an identifier of the entity accessing the medical device. In other words, in particular, in the case where the change of the medical device is the use of a consumable material within the medical device and / or the refilling of a consumable material at the medical device, all features related to the identifier of the entity accessing the medical device may be deleted. In particular, these features are not necessary because, in the case of tracking consumable materials, it may be unimportant and / or impossible to detect which entity has performed an action on the consumable material.

[0213] According to another possible aspect of the invention, the further medical data set comprises an amount of consumable material used during a medical procedure with the medical device and / or wherein the further medical data set comprises an amount of consumable material refilled at the medical device.

[0214] In particular, the amount of consumable material used and / or refilled may be expressed in terms of units of consumable material, in terms of volume of consumable material and / or in terms of mass of consumable material.

[0215] The inventors have realised that by including the amount of consumable material, the need for additional consumable material can be tracked more easily. In addition, the medical material used can be accurately compensated.

[0216] According to another aspect of the invention, the step of receiving the further medical data set comprises the following steps: receiving an identifier of the medical device using an interface; receiving an identifier of a person accessing the medical device using an interface; and determining the further medical data set based on the identifier of the medical device and based on the identifier of the person accessing the medical device. In particular, the interface is an interface of the block creation unit. In particular, the calculation unit is a calculation unit of the block creation unit.

[0217] According to another aspect of the invention, an entity performs a modification of a medical device, wherein a record of the modification is created, and wherein the step of receiving a further medical data set comprises the step of receiving the record of the modification using an interface. Furthermore, the step of determining the further medical data set is based on the record of the modification.

[0218] According to another aspect of the present invention, the first ledger records the number of accesses to the medical device by the entity to implement a pay-per-use model. The inventors have recognized that by recording the number of accesses in the first ledger, the number of accesses can be recorded in a revision-safe manner. In particular, the entity accessing the medical device cannot be denied access to the medical device, which is a prerequisite for implementing a pay-per-use model based on the number of accesses to the medical device.

[0219] According to another aspect of the present invention, a first ledger records actions performed by an entity using a medical device to implement a pay-per-use model. The inventors recognized that, by recording the first ledger of actions performed by an entity, these actions can be recorded in a revision-safe manner. In particular, an entity that performs actions using a medical device cannot deny performing these actions using the medical device, which is a prerequisite for implementing a pay-per-use model based on actions performed using the medical device.

[0220] According to another aspect of the invention, the method further comprises the step of performing a check whether the additional access of the entity to the medical device and / or the additional action performed by the entity using the medical device is covered by the pay-per-use model, and in case of a positive check, granting access to the medical device to the entity accessing the medical device using the computing unit. The inventors have realized that the pay-per-use model can be circumvented by granting access to the medical device only if the pay-per-use model allows the additional access or the additional action.

[0221] According to another aspect of the invention, a method for inserting an additional data block comprises the following steps: granting access to the medical device to an entity accessing the medical device using a computing unit. In particular, the step of granting access to the medical device may comprise a check of authentication and / or authorization of the entity to access the medical device, wherein access is only granted if the check has a positive result. In particular, the step of granting access may comprise: establishing a remote connection between the medical device and the entity accessing the medical device or the entity's device accessing the medical device. The inventors have recognized that granting access within the method of inserting an additional data block into a first ledger results in an indisputable access log, also in the event of failure of certain network components.

[0222] In the following aspects of the present invention, aspects are described that can be used to record the transfer of medical data records from a first entity to a second entity, and in particular, to create a revised secure audit trail of the transfer of medical data records within a first ledger. In other words, the first ledger is a cumulative log of the transfer of medical data records from certain entities to certain other entities.

[0223] In particular, such a cumulative log can be used to detect and prove the unauthorized transmission of medical data. In addition, the consent of the patient, for example, as the subject of the medical data, can also be included in the cumulative log, so that on the one hand, the consent can also be stored in a revised and preserved manner, and on the other hand, the transmission without consent can be tracked.

[0224] In particular, in the described aspects, the additional data blocks and / or the data blocks contained in the first ledger may have the same structure. In other words, the features and advantageous embodiments described for the additional data blocks may also be applied to the data blocks contained in the first ledger, and vice versa.

[0225] According to another aspect of the invention, the further medical data set is a log of the transfer of the medical data record from the first entity to the second entity, wherein the further medical data set comprises an identifier of the medical data record and an identifier of the first entity and the second entity. The inventors realised that by using this method, the transfer of the medical data record can be recorded in a revision-safe manner.

[0226] According to another aspect of the invention, the identifier of the medical data record is a hash value of the medical data record. The inventors have recognized that the memory requirement of the hash value of the medical data record is less than the memory requirement of the medical data record itself, which results in a reduced memory requirement for the additional data blocks. Furthermore, the hash of the medical data record is sensitive even to small changes in the medical data record, which complicates the falsification and / or manipulation of the medical data record.

[0227] According to another aspect of the invention, the further medical data set further comprises a timestamp corresponding to the transmission time of the medical data record.The inventors have realised that by including a timestamp, the traceability of the transmission log can be increased.

[0228] According to another aspect of the invention, the identifier of the first entity is based on a private key assigned to the first entity, and / or wherein the identifier of the second entity is based on a private key assigned to the second entity. Typically, the private key assigned to the first entity is not included in the first identifier itself, in another data block or in another medical data set. Typically, the private key assigned to the second entity is not included in the second identifier itself, in another data block or in another medical data set. The inventors recognize that, typically, the private key assigned to the first entity or the second entity is known only to the first entity or the second entity, and not to the other entity. Therefore, an identifier based on a private key assigned to the first entity or the second entity can only be generated by the entity itself, a person authorized by the first entity or the second entity, or a technical device belonging to the first entity or the second entity, and cannot be manipulated by another entity.

[0229] According to another aspect of the invention, the identifier of the first entity includes a first signature signed with a private key assigned to the first entity, and / or the identifier of the second entity includes a second signature signed with a private key assigned to the second entity. The inventors recognized that using a signature signed with a private key allows other entities to verify the identifier of the first entity and / or the second entity using a public key associated with the private key assigned to the first entity and / or the second entity. In addition, the signature including the signature signed with the private key assigned to the first entity and / or the second entity does not expose the private key to another entity.

[0230] According to another aspect of the present invention, the first signature and / or the second signature is based on a medical data record, in particular, based on a hash value of the medical data record. In particular, the first signature and / or the second signature is equivalent to a medical data record or a hash of a medical data record signed with a private key assigned to the first entity and / or with a private key assigned to the second entity. The inventors recognized that by using a signature based on a medical data record, it is possible to identify the entities involved in the transmission of the medical data record and to record the actual value of the medical data record transmitted from the first entity to the second entity. Therefore, a signature based on a medical data set undoubtedly proves that a certain medical data record has been transmitted from the first entity to the second entity.

[0231] According to another aspect of the invention, the log data set further comprises a timestamp corresponding to a time of transmission of the medical data record, wherein the first signature and / or the second signature is based on the timestamp. The inventors have recognized that the use of the first signature and / or the second signature based on the timestamp unambiguously proves that the transmission of the medical data record from the first entity to the second entity has been performed at a time corresponding to the timestamp.

[0232] According to another aspect of the invention, the medical data record is a medical data record of a patient, and wherein the medical data set comprises consent information issued by the patient. In particular, the consent information issued by the patient describes the patient's consent to the medical data record being transferred from the first entity to the second entity. The consent information may be a signature signed using the patient's private key. In particular, the signature may be a signature of an identifier of the medical data record and an identifier of the second entity. In particular, the signature may be a signature of an identifier of the medical data record, an identifier of the first entity, and an identifier of the second entity. The inventors have recognised that by storing the consent information in a further data set, the patient's consent to sharing his medical data record may be recorded in a revision-safe manner.

[0233] According to another aspect of the invention, the step of receiving an additional medical data set comprises the following steps: receiving a transfer request related to a medical data record from a second entity via an interface; and wherein the step of receiving an additional medical data set comprises the following steps: determining an additional medical data set based on the transfer request and based on the medical data record using a computing unit.

[0234] In particular, the step of determining a further medical data set based on the medical data record is performed after the step of receiving a transfer request. In particular, the interface is an interface of the block creation unit. In particular, the calculation unit is a calculation unit of the block creation unit.

[0235] In particular, the medical data record may be stored in a memory unit of the block creation unit. In this case, the first entity is equivalent to the block creation unit, or the block creation unit is a subset of the first entity or owns the first entity. Alternatively, the medical data record may be stored in a memory unit external to the block creation unit. In this case, the first entity is not equivalent to the block creation unit.

[0236] Typically, a transfer request may be issued by the second entity and sent to the first entity in order to initiate a transfer of a medical data record from the first entity to the second entity. In particular, the transfer request may include an identifier of the medical data record to be transferred; in particular, the transfer request may include a URL associated with the medical data record to be transferred. In particular, the transfer request may also include proof of the identity of the second entity, such as a signature signed with a private key associated with the second entity. Furthermore, the transfer request may also include proof of authorization of the second entity.

[0237] According to another aspect of the invention, the method for inserting a further data block into the first ledger further comprises the step of providing the medical data record to the second entity using an interface. In particular, the interface is an interface of the block creation unit.

[0238] According to another aspect of the invention, a method for inserting a further data block into a first ledger comprises the following steps: performing a check of the authorization of the second entity to access the medical data record using a computing unit, wherein the step of providing the medical data record is performed only if the result of the check is positive.

[0239] The inventors have realised that by combining the checking of the authorization of an entity to receive medical data records with the recording of the transfer of the medical data records from a first entity to a second entity, the security of the data transfer is increased.

[0240] According to another aspect of the present invention, the method for inserting an additional data block into a first ledger further comprises the following steps: determining a changed medical data record based on the medical data record using a computing unit, wherein the changed medical data record comprises an identifier of a second entity; and providing the changed medical data record using an interface.

[0241] In particular, the altered medical data record comprises an identifier of the second entity such that the identifier of the second entity is not separated from the actual data of the altered medical data record, but rather such that the identifier of the second entity is combined with the actual data of the altered medical data record. In particular, the altered medical data record may be the result of a function which takes as input the medical data record and the identifier of the second entity and gives as output the altered medical data record. In particular, the altered medical data record may be used in the same way as the medical data record; in particular, a method, device or entity working on a medical data record may also work on the altered medical data record without changing its process.

[0242] The inventors have recognized that by providing an altered medical data record incorporating an identifier of a second entity, misuse of the altered medical data record can be detected. For example, if the second entity shares the altered medical data record without permission, a person can determine the source of the sharing without permission by inspecting the altered medical data record.

[0243] According to another aspect of the invention, a medical data record comprises a medical image, wherein the altered medical data record comprises the medical image provided with a watermark, and wherein the watermark comprises an identifier of the second entity. In other words, the altered medical data record comprises the altered medical image, wherein the altered medical image is a medical image provided with a watermark. In other words, the altered medical image comprises information of the medical image and information of the watermark.

[0244] In particular, watermarks are digital watermarks. In general, a watermark is a mark that is covertly embedded in a noise-resistant signal such as image data. Watermarks can also be used in audio data or video data. In other words, watermarks include hidden information. In particular, watermarks can be used to verify the authenticity or integrity of the images in which they are embedded, or to show the identity of their owner. In general, watermarks are only perceptible under certain conditions, i.e. after applying a certain algorithm to the image in which the watermark is contained. An image may carry several different watermarks at the same time. In particular, unlike metadata added to an image, a watermark does not change the size of the carrier signal.

[0245] The inventors have realised that using a watermark an identifier of a second entity can be encoded in a hidden manner into the medical data record and furthermore an image comprising a watermark can be processed using the same algorithms as an image without a watermark.

[0246] According to another aspect of the present invention, the medical image comprises a background area and a foreground area, and the watermark is located only in the background area of ​​the medical image. In particular, if the altered medical data record comprises an altered medical image, the altered medical image comprises a foreground area of ​​the medical image and an altered background area, wherein the altered background area is the background area of ​​the medical image provided with the watermark.

[0247] The background area of ​​a medical image is an area that is not an image of the patient itself but an image of the patient's surroundings. The foreground area of ​​a medical image is an area that is an image of the patient itself. In particular, the background area can be an image of the air around the patient or a patient positioning device such as a patient table.

[0248] The inventors have realized that equipping only the background area of ​​a medical image with a watermark does not affect the relevant information contained in the foreground area, and in particular, the relevant information of the altered medical image is the same as the relevant information of the medical image.

[0249] In the following aspects of the present invention, aspects are described that can be used to record the admission process of a medical device, in particular, to create a revised secure document of the admission process of the medical device within a first ledger. In other words, the first ledger is a cumulative document of the admission process of the medical device.

[0250] A first use example is to track the training process of an artificial intelligence algorithm for diagnostic or therapeutic purposes in order to prevent or at least document overfitting of the artificial intelligence algorithm. A second use example is to track research data corresponding to the admission process of a medical device, in particular, to exclude that certain research subjects have been used twice in the same study or in similar studies. However, the following aspects of the invention are not limited to such examples.

[0251] In particular, in the described aspects, the additional data blocks and / or the data blocks contained in the first ledger may have the same structure. In other words, the features and advantageous embodiments described for the additional data blocks may also be applied to the data blocks contained in the first ledger, and vice versa.

[0252] According to another aspect of the present invention, the further medical data set corresponds to an admission procedure of a medical device. In particular, the admission procedure of the medical device may be an admission procedure of a certain type of medical device.

[0253] In particular, if the medical data set includes information and / or data necessary for the admission process of the medical device, the medical data set corresponds to the admission process of the medical device. Typically, the information and / or data necessary for the admission process of the medical device is regulated by a state and / or government agency.

[0254] The medical device admission process corresponds to all data items and / or actions necessary for a state agency to receive admission of a medical device, maintain admission of a medical device, and / or meet requirements set by a state agency. Other actions and / or data items related to the admission of a medical device may also be considered part of the medical device admission process.

[0255] A medical device may include a physical device configured to perform and / or support a treatment and / or diagnostic procedure. A medical device may also include a non-physical entity, for example, a software or computer program product configured to perform or support a treatment or diagnostic procedure. In particular, an artificial intelligence algorithm configured to perform and / or support a treatment and / or diagnostic procedure may be considered a medical device or part of a medical device. In particular, a medical device may include an artificial intelligence algorithm configured to process medical images. If the medical device includes an artificial intelligence algorithm, the information and / or data necessary for the admission process of the medical device may include training data about the artificial intelligence algorithm.

[0256] Typically, an artificial intelligence algorithm is a function that maps input data to output data, where the internal parameters of the function are determined based on the training input data. In particular, the parameters can be determined by comparing the output of the function applied to the training input data with the known output data, which is called supervised learning. Unsupervised learning or a combination of supervised and unsupervised learning can also be used. In the case of supervised learning, the information and / or data necessary for the admission process may include pairs of training input data and associated known output data.

[0257] The inventors have realized that by recording the information and / or data necessary for the admission process of a medical device in the first ledger as an additional data block, a revision-safe documentation of the admission process is ensured. Thus, errors in the admission process of a medical device can be tracked later.

[0258] According to another aspect of the invention, the medical device comprises a trained artificial intelligence algorithm, and wherein the further medical data set is based on the training data set used to train the artificial intelligence algorithm. In particular, the training data set is used as an input to the artificial intelligence algorithm during training. In particular, in the case of supervised learning, the training data set comprises a pair of training input data and known output data, wherein during training, the artificial intelligence algorithm is applied to the training input data, and the parameters of the artificial intelligence algorithm are adjusted based on a comparison of the output of the artificial intelligence algorithm with the known output data.

[0259] In particular, the further medical dataset is based on the training dataset if the further medical dataset comprises the training dataset, if the further medical dataset comprises a link or URL to the training dataset and / or if the further medical dataset comprises an identifier of the training dataset, in particular a hash of the training dataset.

[0260] The inventors recognized that recording the training of an artificial intelligence algorithm in a distributed ledger enables verification of the correct training of the artificial intelligence algorithm.

[0261] According to another aspect of the present invention, the step of receiving an additional medical data set includes the following steps: receiving a training data set using an interface; determining a first parameter of an artificial intelligence algorithm using a computing unit; performing a training step of the artificial intelligence algorithm based on the training data set using the computing unit; determining a second parameter of the artificial intelligence algorithm using the computing unit; and determining an additional medical data set based on the training data set and based on the first parameter and the second parameter using the computing unit. The inventors recognized that recording the training data set together with the first parameter and the second parameter enables recording the actual effect of training the artificial intelligence algorithm using the training data set.

[0262] According to another aspect of the invention, the artificial intelligence algorithm comprises an artificial neural network, and wherein the first parameter comprises weights of edges of the artificial neural network before performing a training step, and wherein the second parameter comprises weights of edges after performing the training step.

[0263] Typically, an artificial neural network comprises a set of nodes and a set of (directed) edges connecting the nodes. Typically, a weight can be assigned to each edge in the set of edges. In particular, if an edge connects an output of a first node to an input of a second node, the weight of the edge corresponds to the weight of the output of the first node in the input of the second node. In particular, the second node may comprise several incoming edges connected to the outputs of several first nodes, in which case the weight may be associated with the relative weight of the outputs of several first nodes in the input of the second node.

[0264] According to another aspect of the invention, the first parameter comprises weights of all edges of the artificial neural network before performing the training step, and wherein the second parameter comprises weights of all edges of the artificial neural network after performing the training step.

[0265] The inventors have recognized that a change of the weight of one or several edges of an artificial neural network is a relevant parameter change during a training step of the artificial neural network.

[0266] According to another aspect of the present invention, the training data set includes training images. According to another aspect of the present invention, the training data set includes labels associated with the training images. The inventors recognize that the training images and associated labels used to train the artificial intelligence algorithm are relevant data that record the training process of the artificial intelligence algorithm.

[0267] According to another aspect of the invention, a medical data set comprises an identifier of a person who is a subject of a medical study. In particular, the study is related to an admission process for a medical device.

[0268] In general, and particularly in the medical sciences, medical research is research performed to verify or disprove a medical hypothesis. In particular, the medical hypothesis may relate to the effectiveness of certain diagnostic or therapeutic medical devices, medical procedures, or drugs.

[0269] A person is subjected to medical research if the medical research makes use of data from the person. In particular, the person subjected to the medical research is the subject of the diagnostic or therapeutic medical device, medical method or drug. In particular, the subject of the medical research - the person - may suffer from a certain disease, and the effectiveness of a certain diagnostic or therapeutic medical device, medical method or drug is tested on the patient.

[0270] The inventors have realised that recording people who are subjects of medical research in a distributed ledger allows recording the medical research itself and, in particular, such a distributed ledger can be used for fraud detection. For example, some types of medical research rely on so-called virgin subjects, where a virgin subject is a person who has not yet been exposed to medical treatment. Since such a person is difficult to find, fraud may be perpetrated by using a virgin subject multiple times, meaning that they are not the virgin subject for all medical research except the first subject. Recording people who have been subjected to medical research allows tracking such fraudulent virgin subjects.

[0271] According to another aspect of the invention, the identifier of a person is a physical parameter of the person that uniquely identifies the person. According to another aspect of the invention, the identifier of the person corresponds to a fingerprint of the person, a DNA sequence of the person, or a biometric parameter of the person. In particular, the biometric parameter is a geometric relationship between certain landmarks of the human body, in particular landmarks of the human face.

[0272] The inventors have recognized that using physical parameters of a unique identification allows the identity of a person to be tracked also for people who do not have any legal or data driven identity (eg, an ID number or social security number).

[0273] According to another aspect of the invention, the medical data set comprises first patient parameters corresponding to a person before the medical study, and wherein the medical data set further comprises second patient parameters corresponding to the person after the medical study. In particular, the first patient parameters correspond to the person before the elements of the medical study are applied to the patient, and the second patient parameters correspond to the person after the elements of the medical study are applied to the patient. Examples of elements applied to the person are therapeutic actions or medications.

[0274] Typically, the first patient parameter and the second patient parameter correspond to physical values ​​of a person who is the subject of the medical study, such as laboratory values ​​corresponding to the patient or diagnostic information corresponding to the patient. In particular, the difference between the first patient parameter and the second patient parameter can indicate a possible effect of an element of the medical study applied to the person, such as the effectiveness of a drug.

[0275] The inventors have realized that by recording the first patient parameter and the second patient parameter in a distributed ledger, the actions of the study can be recorded in a revision-safe manner for a single effect on the subjects of the study. In particular, by recording these patient parameters, it can be ensured that the results of the study are based on all subjects of the study.

[0276] According to another aspect of the invention, the step of receiving the further medical data set comprises the step of receiving an identifier of a person who is the subject of the medical investigation by means of an interface, and furthermore, the step of receiving the further medical data set comprises the step of determining the further medical data set based on the identifier of the person who is the subject of the medical investigation by means of a calculation unit. In particular, the calculation unit is a calculation unit of a block creation unit BCU. In particular, the interface is an interface of the block creation unit.

[0277] According to another aspect of the invention, the step of receiving the further medical data set comprises the following steps: receiving, with the interface, an identifier of a person who is the subject of the medical study; receiving, with the interface, first patient parameters corresponding to the person before the medical study; receiving, with the interface, second parameters corresponding to the person after the medical study; and determining, with the computing unit, the further medical data set based on the identifier of the person who is the subject of the medical study and based on the first parameter and the second parameter. In particular, the computing unit is a computing unit of a block creation unit BCU. In particular, the interface is an interface of the block creation unit.

[0278] According to a further aspect of the invention, the further medical data set corresponds to a commissioning process of the medical device by corresponding to a calibration of the medical device.

[0279] Typically, the calibration of a medical device is based on a comparison of an output value of the medical device, in particular a measurement value of the medical device, with a calibration standard of known accuracy. In particular, the calibration of a medical device is a process of changing one or several parameters of the medical device in order to achieve an output value of the medical device equal to a calibration standard of known accuracy. The calibration standard may be the output of another device, in particular a measurement value, the output of another device that generates an object to be measured by the medical device, or an object with known properties to be measured by the medical device. For example, if the medical device is a computed tomography device, the calibration of the medical device may include: measuring a phantom using the computed tomography device, and comparing the measurement with the known properties of the phantom. For example, if the medical device is a laboratory device that measures the properties of a fluid, the calibration may include measuring a fluid with known properties, in particular water.

[0280] In particular, the calibrated medical device may be consistent with the block creation unit.Alternatively, the block creation unit may include the calibrated medical device, or the calibrated medical device may include the block creation unit.

[0281] The inventors realised that storing a further set of medical data corresponding to the calibration of the medical device in the first ledger can be used to store in a revision-safe manner the fact that a calibration has taken place, and advantageously also the result of the calibration.

[0282] According to another aspect of the invention, the further medical data set comprises an identifier of the medical device and a timestamp, wherein the timestamp corresponds to a calibration time of the medical device. According to another aspect, the step of receiving the further medical data set comprises the following steps: receiving the identifier of the medical device using the interface; and determining the further medical data set based on the identifier of the medical device using the computing unit.

[0283] The inventors realised that by including an identifier of the medical device and a timestamp of the calibration into an otherwise medical data set, it can be documented in a revision-safe manner that a calibration has been performed at the included timestamp.

[0284] According to another aspect of the invention, the further medical data set comprises an identifier of the entity performing the calibration of the medical device. According to another aspect of the invention, the step of receiving the further medical data set comprises the following steps: receiving, with the interface, the identifier of the entity performing the calibration of the medical device; and determining, with the computing unit, the further medical data set based on the identifier of the entity performing the calibration of the medical device, in particular also based on the identifier of the medical device.

[0285] The inventors realised that by including an identifier of the entity performing the calibration of the medical device, it can be documented in a revision-safe manner which entity performed the calibration. This data can later be used to determine the entity responsible if one or several calibration processes were not performed correctly.

[0286] In particular, if the calibrated medical device is consistent with the block creation unit, or if the calibrated medical device includes the block creation unit, or if the block creation unit includes the calibrated medical device, the identifier of the entity performing the calibration can be consistent with the entity using the calibrated medical device, in particular the entity logged into the calibrated medical device.

[0287] According to another aspect of the invention, the further medical data set comprises calibration information based on a calibration of the medical device. According to another aspect of the invention, the step of receiving the further medical data set comprises the steps of: receiving the calibration information with the interface; and determining with the computing unit the further medical data set based on the calibration information, in particular also based on an identifier of the medical device and / or based on an identifier of an entity performing the calibration of the medical device.

[0288] In particular, the calibration information may be based on output and / or measured values ​​of the medical device during calibration. Furthermore, the calibration information may be based on a calibration standard of known accuracy used for calibration. Furthermore, the calibration information may include measures taken to calibrate the medical device, in particular, one or more parameters of the medical device are selected such that the output value of the medical device is equal to the calibration standard of known accuracy.

[0289] The inventors realised that by including calibration information into an additional medical data set, the calibration process can be documented in even greater detail.

[0290] According to another possible aspect of the invention, the further medical data set comprises data documenting a product development of a medical device.

[0291] In particular, the medical device may be a hardware device and / or software. Product development of the medical device may include: developing the hardware and / or writing the computer code constituting the software. Product development may additionally include quality testing, in particular, clinical validation or software testing.

[0292] The inventors have realised that by including an additional medical data set including data documenting the product development of a medical device, this data can be documented in a revision-safe manner, while potentially allowing external entities (e.g., regulatory agencies) to access the document. In particular, this can then be used to document the admission process of a medical device in a revision-safe manner.

[0293] According to another possible aspect of the invention, the further medical data set comprises data describing a certain version of software contained in the medical device.

[0294] The specific version of the software may be a version of the software used in production or an intermediate version of the software compiled during the development of the software (e.g., for testing purposes). In particular, all intermediate versions of the software may be recorded in a distributed ledger. If the medical device is software, the software contained in the medical device is the software that forms the medical device.

[0295] The inventors have realised that by recording data describing a version of the software, the development process of the software can be recorded in a revision-safe manner. In particular, it can later be checked which parts of the software were developed under what circumstances (e.g., who contributed a particular part of the software, or when a particular part of the software was created). These undeniable records may be important for retrospective considerations, but are also important for regulators to effectively record the development process.

[0296] According to another possible aspect, the data describing a version of the software describes a submission to a source code repository and / or a build within a continuous integration and / or continuous delivery system.

[0297] In particular, a commit to a source code repository may be a data set describing the differences of source code between a current version and a previous version submitted to the source code repository. In particular, a set of consecutive commits may be used to rebuild a version of the software.

[0298] In particular, a build of a software version corresponds to machine code generated based on the source code of the software version. In particular, continuous integration is the practice of merging all working copies of developers into a source code repository at least once a working day, preferably several times a working day. In particular, code is compiled and packaged (e.g., linked to libraries) in continuous delivery whenever a change is committed to the source code repository, and in particular testing is included by many different techniques, which may include manual testing and automated testing.

[0299] The inventors have recognized that recording individual steps of a continuous integration and / or continuous delivery process in a distributed ledger can ensure both agility and traceability of software development, allowing the development process to be recorded efficiently and in a revision-safe manner.

[0300] According to another possible aspect of the invention, the data describing the specific version of the software comprises a hash of a submission to a source code repository and / or a hash of a build within a continuous integration and / or continuous delivery system.

[0301] The inventors have realized that by using hashes, the actual source code or the actual build is not recorded in the distributed ledger, so that no external entity can access the actual source code or the actual build. At the same time, by storing the actual source code and / or the actual build locally, the same function as directly storing the source code and / or the build can be achieved by recording the hash in the distributed ledger.

[0302] According to another possible aspect of the invention, the further medical data set comprises at least one signature for signing data documenting product development of the medical device. In particular, the signature can be a digital signature based on a private key of an entity developing the medical device (eg, a manufacturer of the medical device).

[0303] The inventors have realised that by including a signature into a further medical data set recorded in a distributed ledger, it is possible to ensure that the data recording the development of the product is actually inserted into the further medical data set and the distributed ledger by an authorized entity, in particular by an entity developing a medical device. In particular, in this case it is not possible for unrelated entities to falsify entries in the distributed ledger.

[0304] According to another possible aspect of the invention, the further medical data set comprises a smart contract, wherein the smart contract governs the release of the medical device, in particular the release of a specific version of software comprised in the medical device.

[0305] The inventors have recognized that the use of smart contracts can automatically and reliably implement the release of a specific version of software contained in a medical device if a set of specific conditions are met. In particular, the conditions can also be recorded in a distributed ledger or another distributed ledger.

[0306] According to another possible aspect of the invention, a specific version of the software is released if the medical data set includes a predefined set of signatures for signing the data describing the specific version of the software. In particular, the signatures may be based on private keys of a specific set of entities. The specific set of entities may include many employees of the developer of the medical device, in particular, employees who need to agree on the software version to be released.

[0307] The inventors realized that by releasing software based on smart contracts, if a specific set of signatures exists, the release of software can be automated and faster than if paper signatures were used. At the same time, compared to a standard electronic database, the presence of the signatures is indisputable when the software is released.

[0308] According to another possible aspect of the invention, the further medical data set comprises a smart contract, wherein the smart contract governs access to data documenting product development of the medical device. According to another possible aspect of the invention, the smart contract grants a regulatory body access to data documenting product development of the medical device.

[0309] The inventors recognized that through such smart contracts, access may be granted to regulatory agencies and entities on the part of a company developing a medical device, wherein external entities are unable to simultaneously access potentially confidential data documenting the product development of the medical device.

[0310] The present invention may also relate to a method for using a first ledger, wherein an additional data block is included in the first ledger according to a method for inserting an additional data block into the first ledger, the method comprising the step of selecting a first medical data set included in the ledger by a computing unit, wherein the first medical data set comprises an identifier of a first person, the method further comprising the step of selecting a second medical data set included in the ledger by a computing unit, wherein the second medical data set is different from the first medical data set and wherein the second medical data set comprises an identifier of a second person, and the method further comprises the step of determining, using the computing unit, whether the first person and the second person are the same based on the identifier of the first person and the identifier of the second person.

[0311] In particular, the first person is identical to the second person if the identifier of the first person is identical to the identifier of the second person. Alternatively, the first person may be considered identical to the second person if a similarity measure of the identifier of the first person and the identifier of the second person is above a given threshold. In particular, the step of determining whether the first person and the second person are identical may comprise determining a probability that the first person and the second person are identical based on the identifier of the first person and the identifier of the second person, wherein whether the first person and the second person are identical is determined based on the probability, in particular based on whether the probability is above a given threshold.

[0312] In particular, the step of selecting a first medical data set included in the first ledger may include the following steps: selecting a first data block included in the first ledger using a computing unit, wherein the first data block includes the first medical data set; and extracting the first medical data set from the first data block using the computing unit. In particular, the step of selecting a second medical data set included in the first ledger may include the following steps: selecting a second data block included in the first ledger using a computing unit, wherein the second data block includes the second medical data set; and extracting the second medical data set from the second data block using the computing unit.

[0313] The computing unit may be a computing unit of a block creation unit. Alternatively, the computing unit may be a computing unit of a block verification unit. Alternatively, the computing unit may be a computing unit of another computing node.

[0314] The inventors have realized that based on the first ledger, it is possible to determine whether there is a medical data set or a further medical data set that includes the same person's identifier. Thus, the method can be used to determine whether certain people are the subject of the same study twice or more frequently, thereby producing distorted study results. Furthermore, by recording the original subject of the medical study, it is possible to test whether the supposed original subject is actually the original subject.

[0315] According to another aspect of the invention, in the case where the first person and the second person are identical, the method for using the first ledger comprises the step of providing an alert message using the interface. In particular, the alert message may comprise an identifier of the first person and / or an identifier of the second person. The inventors have realised that using the alert message, identical persons may be found more quickly and more reliably.

[0316] According to another aspect of the invention, a first person is a subject of a first medical study and a second person is a subject of a second medical study, wherein the first study is the same as the second study. The inventors have recognized that, through this approach, it may be possible to determine whether certain people are subjects of the same study twice or more frequently, thereby distorting study results.

[0317] According to another aspect of the invention, the step of selecting the second medical data set and the step of determining are applied multiple times. In particular, the step of selecting the second medical data set and the step of determining are performed using each medical data set of a subset of medical data sets contained in the first ledger as the second medical data set, wherein each medical data set of the subset of medical data sets includes an identifier of a second person who is undergoing a medical study of which the first person is a subject. The inventors have recognized that by using this method, it may be possible to determine whether certain persons are the subject of the same study twice or more frequently, thereby producing distorted study results.

[0318] In another aspect, the invention relates to a computing unit for determining the same person using a first ledger, wherein a further data block is included in the first ledger,

[0319] The computing unit is configured to select a first medical data set contained in a first ledger, wherein the first medical data set comprises an identifier of a first person,

[0320] The computing unit is further configured to select a second medical data set contained in the first ledger, wherein the second medical data set is different from the first medical data set, and wherein the second medical data set includes an identifier of the second person,

[0321] The computing unit is further configured to determine whether the first person and the second person are the same based on the identifier of the first person and the identifier of the second person.

[0322] In particular, the computing unit for determining the same person using the first ledger can be configured to: perform the method for determining the same person using the first ledger according to the present invention and its aspects. The computing unit is configured to: perform the method and its aspects by being configured to perform the corresponding method steps.

[0323] The computing unit may be implemented as a data processing system or part of a data processing system. Such a data processing system may, for example, include a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The computing unit may include hardware and / or software. The hardware may be, for example, a processor system, a memory system, and a combination thereof. The hardware may be configured and / or operated by software.

[0324] In another aspect, the present invention relates to a computer program product comprising a computer program, which can be loaded into a memory unit of a computing unit, and which includes program code segments that, when the computer program is executed in the computing unit, cause the computing unit to perform a method for determining the same person using a first ledger according to an aspect of the present invention.

[0325] In another aspect, the present invention relates to a computer-readable medium having a program code segment of a computer program stored thereon, the program code segment being capable of being loaded into a computing unit and / or being capable of being executed in the computing unit so as to cause the computing unit to perform a method for determining the same person using a first ledger according to an aspect of the present invention when the program code segment is executed in the computing unit.

[0326] Realizing the invention by means of a computer program product and / or a computer-readable medium has the advantage that already existing block creation units can be easily adapted by means of a software update in order to function as proposed by the invention.

[0327] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0328] In the following aspects of the present invention, aspects are described that can be used to record the educational actions of medical professionals, and in particular, to create a revised secure document of the educational actions of medical professionals within a first ledger. In other words, the first ledger is a cumulative document of the educational actions of medical professionals.

[0329] A first use example is recording educational actions of a medical professional, e.g., a number of specific intervention actions that the medical professional completed under the supervision of an educational entity, the performance of which was certified or verified by the educational entity. A second use example is providing synthetically generated data to a medical professional and receiving his or her diagnosis of the synthetically generated data, and recording deviations from the actual diagnosis. Such a method or system can be used to automatically perform educational actions and automatically record the success or failure of such educational actions.

[0330] In particular, in the described aspects, the additional data blocks and / or the data blocks contained in the first ledger may have the same structure. In other words, the features and advantageous embodiments described for the additional data blocks may also be applied to the data blocks contained in the first ledger, and vice versa.

[0331] According to another aspect of the invention, the further medical data set is associated with the educational actions of the medical professional, wherein the further medical data set comprises an identifier of the medical professional and an identifier of the educational actions. The inventors have recognised that storing the educational actions of the medical professional in the first ledger allows for a revision-secure audit trail of the educational actions of the medical professional.

[0332] Generally, a medical professional can be a person who performs or trains a diagnosis or treatment action related to a patient or assists a diagnosis or treatment action related to a patient. In addition, a medical professional can also be a person involved in the maintenance or operation of a medical device, medical equipment or medical facility. In particular, a medical professional can be a physician, a technical specialist, a radiologist, a nurse, a hygienist or a technician. In order to become a medical professional or as a medical professional, a person must, for example, prove his or her ability by obtaining a certificate (for example, a university diploma), by obtaining credit points (for example, CME credits, wherein CME is an abbreviation for "continuing medical education", in particular, by the Accreditation Committee for Continuing Medical Education ACCME and the American Osteopathic Association AOA) or by regularly performing certain tasks.

[0333] Typically, an educational action is an action performed by one or several medical professionals, which is necessary to demonstrate his or their competence. In order to obtain a diploma or to be admitted to work as a medical expert, it may be necessary to perform certain educational actions. Alternatively, an educational action may be necessary in order to remain admitted to work as a medical professional, in particular, in order to remain admitted as a medical expert. Furthermore, an educational action may also be necessary in order to demonstrate that the medical expert is familiar with a specific therapeutic or diagnostic action. In particular, an educational action may be a therapeutic or diagnostic action. Alternatively, an educational action may also be the performance of a test related to a therapeutic or diagnostic action. As a further alternative, an educational action may be a documented attendance at a meeting or participation in a classroom educational session.

[0334] According to another aspect of the invention, the educational action is supervised and / or rated by an educational entity, wherein the medical data set includes a signature of an identifier of the educational action and an identifier of the medical professional, and wherein the signature is signed by the educational entity.

[0335] The educational entity is an entity that supervises, rates and / or confirms the medical actions performed by the medical professional. In particular, the educational entity may be an experienced medical professional. Furthermore, the educational entity may also be an institution, such as a university or a hospital, which provides the medical professional with the possibility of performing educational actions. In particular, the educational entity may also be an employee or any other representative of such an institution. The educational entity may also be software that provides virtual tests to the medical professional and rates the medical professional's answers or actions.

[0336] Typically, if an educational entity oversees or grades an educational action and a medical professional performs the medical action, the educational entity monitors the medical action, evaluates the resulting medical action, and / or intervenes if the medical professional does not perform the educational action correctly.

[0337] According to another aspect of the invention, the step of receiving a medical data set comprises the following steps: providing a medical data record to a medical professional via an interface, wherein first medical information is assigned to the medical data record; receiving second medical information from the medical professional via the interface; and determining a comparison value via a calculation unit based on the first medical information and based on the second medical information; wherein the medical data set is based on the comparison value. In particular, the interface is an interface of the block creation unit. In particular, the calculation unit is a calculation unit of the block creation unit.

[0338] The inventors have realised that through this aspect, not only the fact that the medical professional has performed an educational action can be recorded, but also the result of the educational action can be recorded.

[0339] Typically, the first medical information and the second medical information are diagnostic information related to the medical data record. In particular, the first medical information is correct diagnostic information related to the medical data record, and the second medical information is diagnostic information related to the medical data record related to the medical professional.

[0340] In particular, if the comparison value is related to a difference between the first medical information and the second medical information, the comparison value is based on the first medical information and the second medical information. In particular, the comparison value measures the difference between the first medical information and the second medical information. In particular, the comparison value can be a binary value indicating whether the first medical information is equivalent to the second medical information.

[0341] According to another aspect of the invention, the first medical information is diagnostic information about a medical data record determined by another entity, and wherein the second medical information is diagnostic information about a medical data record determined by a medical professional. The inventors recognized that through this aspect, a test of the performance of the medical professional in terms of diagnosis can be recorded.

[0342] According to another aspect of the present invention, the medical data record and the first medical information are synthetically generated data. In particular, the medical data record and the first medical information are generated by an artificial intelligence algorithm. In particular, the method for including an additional data block into the first ledger may include the step of synthetically generating the medical data record and the first medical information. In particular, the step of synthetically generating the medical data record and the first medical information may be based on an artificial intelligence algorithm. In particular, the artificial intelligence algorithm may be based on a generative adversarial network. The inventors recognized that using synthetically generated medical data records and first medical information, training resources for medical professionals can be generated more cheaply. This means that different synthetically generated medical data records and first medical information can be used for different medical professionals, which makes fraud more difficult.

[0343] According to another aspect of the present invention, the medical data record corresponds to the patient, wherein the first medical information is created by an experienced medical professional. In particular, the experienced medical professional is different from the medical professional. The inventors have recognized that using the medical data record corresponding to the patient and the first medical information created by the experienced medical professional has a higher quality than the synthetically generated medical data record and the first medical information, thereby producing a better educational result.

[0344] According to another aspect of the present invention, the medical data record includes a medical image and / or a medical laboratory report. The inventors have recognized that educational actions based on medical images or medical laboratory reports can be effectively used for automated educational actions because the diagnosis of the medical image and / or medical laboratory report does not include interaction between medical professionals and other entities.

[0345] In another aspect, the present invention relates to a method for verifying the experience of a medical professional using a first ledger, the method comprising the following steps: receiving the first ledger using an interface; receiving an identifier of the medical professional using the interface; receiving an identifier of an educational action using the interface; determining a relevant data block of the first ledger using a computing unit, wherein the relevant data block is a data block of the first ledger including a relevant medical data set, and wherein the relevant medical data set is a medical data set including an identifier of the medical professional and an identifier of the educational action; and determining an educational parameter based on the relevant data block using the computing unit. An alternative wording for the method for verifying the experience of a medical professional using a first ledger is a method for determining an educational parameter using the first ledger. The inventors have recognized that based on the first ledger, it is possible to determine and / or verify that the experience or educational parameter is secure from falsification.

[0346] The interface may be an interface of a block creation unit, and the computing unit may be a computing unit of the block creation unit. Alternatively, the interface may be an interface of a block verification unit, and the computing unit may be a computing unit of the block verification unit. Alternatively, the interface may be an interface of another computing node, and the computing unit may be a computing unit of another computing node.

[0347] According to another aspect of the invention, the educational parameter is the number of relevant data blocks. In particular, the educational parameter may be the number of relevant data blocks included into the first ledger after a certain time threshold. The inventors recognized that the number of relevant data blocks corresponds to the number of educational actions performed by the medical professional under consideration and is a suitable metric for evaluating the experience of the medical professional.

[0348] According to another aspect of the present invention, a method for verifying the experience of a medical professional using a first ledger includes the following steps: receiving a minimum education requirement using an interface, wherein the education parameter is also based on the minimum education requirement. The inventors have recognized that based on the minimum education requirement, the experience of the medical professional can be quickly and efficiently evaluated.

[0349] According to another aspect of the invention, the minimum education requirement is a minimum number of education actions to be performed, and wherein the education parameter is based on a comparison of the number of relevant data blocks with the minimum number of education requirements. The inventors have recognized that by comparing said numbers, it is easy to determine whether the experience of the medical professional meets a given minimum requirement.

[0350] In another aspect, the invention relates to an experience verification unit for verifying the experience of a medical professional using a first ledger after inserting a further data block according to an aspect of the invention, the experience verification unit comprising the following units:

[0351] - an interface configured to receive a first ledger,

[0352] The interface is further configured to receive an identifier of a medical professional,

[0353] The interface is further configured to receive an identifier of the educational action,

[0354] - a computing unit configured for determining a relevant data block of the first ledger, wherein the relevant data block is a data block of the first ledger comprising a relevant medical data set, and wherein the relevant medical data set is a medical data set comprising an identifier of a medical professional and an identifier of an educational action,

[0355] The computing unit is further configured to determine educational parameters based on the relevant data blocks.

[0356] In particular, the experience verification unit can be configured to: perform the method for verifying the experience of a medical professional using the first ledger according to the present invention and its aspects. The experience verification unit is configured to: perform the method and its aspects by being a computing unit and an interface configured to perform the corresponding method steps.

[0357] The experience verification unit can be implemented as a data processing system or a part of a data processing system. Such a data processing system can, for example, include a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The experience verification unit can include hardware and / or software. The hardware can be, for example, a processor system, a memory system, and a combination thereof. The hardware can be configured and / or operated by software.

[0358] In another aspect, the present invention relates to a computer program product comprising a computer program, which can be loaded into a memory unit of an experience verification unit, and the computer program includes program code segments that, when the computer program is executed in the experience verification unit, cause the experience verification unit to perform a method for verifying the experience of a medical professional using a first ledger according to an aspect of the present invention.

[0359] In another aspect, the present invention relates to a computer-readable medium having a program code segment of a computer program stored thereon, the program code segment being capable of being loaded into an experience verification unit and / or being capable of being executed in the experience verification unit so that when the program code segment is executed in the experience verification unit, the experience verification unit performs a method for verifying the experience of a medical professional using a first ledger according to an aspect of the present invention.

[0360] Realizing the invention by means of a computer program product and / or a computer-readable medium has the advantage that already existing block creation units can be easily adapted by means of a software update in order to function as proposed by the invention.

[0361] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0362] In the following, other aspects of the present invention are described in further detail. The following other aspects of the present invention are partly the same as the various aspects of the present invention described above.

[0363] The definitions of terms used in the following other aspects of the present invention and the advantages, features and / or embodiments of the present invention described above may also be applied to the following other aspects of the present invention.

[0364] The invention is not restricted by the following other aspects, features or advantageous embodiments thereof.

[0365] In one aspect, the present invention relates to a method for inserting additional data blocks into a first ledger, wherein the first ledger includes data blocks, the method includes the step of receiving an additional medical data set using an interface, wherein the additional medical data set is a log of an entity's access to a medical device, wherein the additional medical data set includes an identifier of the medical device and an identifier of the entity accessing the medical device, the method also includes the step of determining an additional data block using a computing unit, wherein the additional data block includes the additional medical data set and additional linking information, wherein the additional linking information includes a hash of at least one of the data blocks of the first ledger, and the method also includes the step of inserting the additional data block into the first ledger using the computing unit.

[0366] For the present invention, it is not necessary that the further linking information comprises a hash of at least one of the data blocks of the first ledger. The use of the hash of at least one of the data blocks allows to verify that the at least one of the data blocks has not been changed after determining the linking information, in particular after determining the hash. In other words, within the claims and throughout the application, the term "data integrity information of at least one of the data blocks" can be used instead of the term "hash of at least one of the data blocks". In particular, by means of the data integrity information of at least one of the data blocks, manipulations and / or changes to the at least one of the data blocks can be identified or determined. For the same reasons, for linking information different from the further linking information, within the claims and throughout the application, the term "data integrity information of at least one of the data blocks" can be used instead of the term "hash of at least one of the data blocks".

[0367] It is not necessary for the present invention that the additional medical data set is a log of the entity's access to the medical device, wherein the additional medical data set comprises an identifier of the medical device and an identifier of the entity accessing the medical device. Using such a structure regarding the additional medical data set and / or the first ledger can be used to record the entity's access to the medical device. In other words, the additional medical data set may have a different purpose or different content.

[0368] The inventors recognized that by including additional blocks of data into the first ledger—including additional medical data sets containing the defined structure—entities' access to medical devices can be stored in a revision-safe or non-disputable manner, thereby allowing tracking of access to certain medical devices or access by certain entities.

[0369] According to another aspect of the invention, the identifier of the medical device is based on the model number of the medical device and / or the serial number of the medical device. The inventors have recognized that identifiers can be assigned to medical devices in an efficient and unique manner based on the medical model number and / or based on the serial number of the medical device.

[0370] According to another aspect of the invention, the identifier of the entity includes a signature signed with a private key assigned to the entity. The inventors have recognized that the signature signed with the private key assigned to the entity proves that the entity actually participated in the creation of the identifier, so that no first entity can include additional medical data sets into the first ledger containing the identifier of the second entity or cause additional medical data sets to be included into the first ledger containing the identifier of the second entity.

[0371] According to another aspect of the invention, the signature is based on an identifier of the medical device. The inventors have recognised that basing the signature on an identifier of the medical device prevents the signature from being used in several medical data sets in the first ledger, which contributes to the first ledger being tamper-proof.

[0372] According to another aspect of the invention, an entity's access to a medical device includes a change to the medical device, and wherein the additional medical data set includes a record of the change, and wherein the step of receiving the additional medical data set includes the following steps: receiving the record of the change using an interface; and determining the additional medical data set based on the record of the change using a computing unit.

[0373] The inventors have realised that, with additional medical data sets based on records of changes, an entity's access to medical devices may be more accurately documented.

[0374] According to another aspect of the invention, a method for including an additional data block into a first ledger comprises the following steps: using an interface to send a notification message to an owner of a medical device, wherein the notification message is based on an identifier of the medical device and an identifier of an entity accessing the medical device. In particular, the step of sending the notification message can be prompted by a smart contract. The inventors have recognized that by sending the notification message, the owner of the medical device can quickly detect unauthorized access to the medical device by an entity and can immediately take necessary countermeasures.

[0375] According to another aspect of the invention, a method for including an additional data block into a first ledger comprises the following steps: granting access to an entity accessing a medical device using a computing unit, wherein the step of granting access is performed after the step of inserting the additional data block into the first ledger. The inventors have recognized that by granting access after inserting the additional data block into the first ledger, it is possible to ensure that the access is recorded before the access actually occurs, which makes it more difficult for an attacker to manipulate the recording process despite access to the medical device by preventing the insertion of the additional data block into the first ledger.

[0376] According to another aspect of the invention, the medical data set comprises a time of an entity's access to a medical device, wherein the time of the access corresponds to a time when the entity established remote access to the medical device, and / or wherein the medical data set comprises a time of an entity's departure from the medical device, wherein the time of the departure corresponds to a time when the remote access to the medical device was terminated. The inventors have recognized that by including the time of the access and / or the time of the departure, the quality of the record can be improved, and in particular, by including the time of the access and / or the time of the departure, not only the fact that the entity's access to the medical device has occurred but also the actual time or time interval of the access can be stored in a revision-safe manner.

[0377] According to another aspect of the present invention, each of the data blocks of the first ledger includes a medical data set and linking information, the linking information including a hash of at least one of the data blocks of the first ledger. The inventors have recognized that by including each data block with linking information, the revision security of the first ledger can be improved.

[0378] According to another aspect of the invention, the step of determining the additional data block comprises the execution of a consensus algorithm. The inventors have recognized that by executing a consensus algorithm, the revision security of the first ledger can be improved.

[0379] According to another aspect of the invention, the first ledger is a blockchain, a block tree or a tangle. The inventors have recognized that by using the described structure of the first ledger, the revision security of the first ledger can be improved.

[0380] According to another aspect of the present invention, a method for including an additional data block into a first ledger comprises the following steps: receiving a second ledger using a block verification unit; transmitting the additional data block to the block verification unit using an interface; verifying the additional linking information based on the second ledger using the block verification unit; and in the event of a positive verification, inserting the additional data block into the second ledger using the block verification unit.

[0381] The inventors realised that by these additional steps, which are essentially verification by the block verification unit of the further data blocks created by the block creation unit, the revision security of the first ledger can be improved.

[0382] In one aspect, the invention relates to a block creation unit for inserting a further data block into a first ledger (LDG), wherein the first ledger comprises data blocks, the block creation unit comprising the following units:

[0383] - an interface configured for receiving a further medical data set, wherein the further medical data set is a log of accesses of a medical device by an entity, wherein the further medical data set comprises an identifier of the medical device and an identifier of the entity accessing the medical device,

[0384] a computing unit configured to determine a further data block, wherein the further data block comprises a further medical data set and further linking information, and wherein the further linking information comprises a hash of at least one of the data blocks of the first ledger,

[0385] The computing unit is further configured to insert the further data block into the first ledger.

[0386] The block creation unit may be implemented as a data processing system or a part of a data processing system. Such a data processing system may, for example, include a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The block creation unit may include hardware and / or software. The hardware may be, for example, a processor system, a memory system, and a combination thereof. The hardware may be configured and / or may be operated by software.

[0387] In one aspect, the present invention relates to a computer program product comprising program elements which, when loaded into a memory unit of a block creation unit, cause the block creation unit to perform the steps of the method for inserting a further data block into a first ledger according to the technical solution of the present invention.

[0388] Realizing the invention by means of a computer program product and / or a computer-readable medium has the advantage that already existing block creation units can be easily adapted by means of a software update in order to function as proposed by the invention.

[0389] A computer program product may be, for example, a computer program or may include other elements in addition to a computer program. The other elements may be hardware, such as a memory device on which the computer program is stored, a hardware key for using the computer program, etc., and / or software, such as documentation or a software key for using the computer program.

[0390] The characteristics, features and advantages of the invention, its above-mentioned aspects and embodiments and the ways to achieve them become clearer and easier to understand according to the following list of possible embodiments, some of which will be described in detail in the context of the accompanying drawings. The following list of embodiments does not limit the invention to the listed embodiments. In particular, the features of the described embodiments can always be combined or exchanged with each other without limiting or expanding the scope of the described invention, as long as such combination or exchange is meaningful in the sense of the invention.

[0391] Embodiment 1: A method for inserting an additional data block into a first ledger, wherein the first ledger includes data blocks, the method comprising the following steps:

[0392] - receiving a further medical data set using the interface,

[0393] - determining a further data block using the computing unit, wherein the further data block comprises a further medical data set and further linking information, wherein the further linking information comprises a hash of at least one of the data blocks of the first ledger,

[0394] - Inserting the further data block into the first ledger using the computing unit.

[0395] Embodiment 2: The method according to embodiment 1, wherein each of the data blocks of the first ledger includes a medical data set and link information, wherein the link information includes a hash of at least one of the data blocks of the first ledger.

[0396] Embodiment 3: The method according to embodiment 1 or 2, comprising:

[0397] - Receiving the first ledger using the interface.

[0398] Embodiment 4: The method according to any one of embodiments 1 to 3 further comprises the following steps: - selecting a parent data block from the data blocks of the first ledger using a computing unit;

[0399] Among them, the additional link information includes the hash of the parent data block.

[0400] Embodiment 5: The method according to embodiment 4, wherein the first ledger does not include a successor data block of the parent data block.

[0401] Embodiment 6: A method according to embodiment 4 or 5, wherein the first ledger includes a starting data block, and wherein the parent data block is selected based on the distance of the parent data block from the starting data block.

[0402] Embodiment 7: A method according to embodiment 6, wherein the first ledger includes exactly one starting data block.

[0403] Embodiment 8: The method according to any one of Embodiments 6 or 7, wherein the parent data block is a data block having the largest distance from the starting data block.

[0404] Embodiment 9: The method according to any one of embodiments 4 to 7, wherein each of the data blocks of the first ledger includes a weight parameter, and wherein the parent data block is selected based on the weight parameter of the parent data block.

[0405] Embodiment 10: A method according to embodiment 9, wherein the weight parameter of the data block of the first ledger is based on the weight parameter of the previous data block of the data block.

[0406] Embodiment 11: A method according to any one of embodiments 4 to 10, wherein the step of selecting a parent data block is based on a Markov Chain Monte Carlo algorithm, and wherein the Markov Chain Monte Carlo algorithm samples the data blocks of the first ledger based on the weights of the data blocks.

[0407] Embodiment 12: The method according to any one of Embodiments 2 to 11, wherein the data blocks of the first ledger form a directed acyclic graph.

[0408] Embodiment 13: The method according to one of the preceding embodiments, wherein the further linking information is based on a further medical dataset.

[0409] Embodiment 14: The method of Embodiment 13, wherein the additional linking information comprises a hash of the additional medical data set.

[0410] Embodiment 15: The method according to one of the preceding embodiments, wherein the further data chunk comprises a Merkle root of a parent data chunk and / or a further medical data set.

[0411] Embodiment 16: A method according to one of the preceding embodiments, wherein determining additional link information includes executing a consensus algorithm.

[0412] Embodiment 17: A method according to embodiment 16, wherein the consensus algorithm includes proof of work, proof of stake and / or proof of elapsed time.

[0413] Embodiment 18: A method according to embodiment 16 or 17, wherein the additional data blocks include random numbers and wherein the consensus algorithm is based on random numbers.

[0414] Embodiment 19: The method according to embodiment 18 further comprises the following steps:

[0415] - receiving, using the interface, a request for a hash of another data block,

[0416] - determining a random number for a further data block using a calculation unit,

[0417] Among them, the hash of the other data block meets the requirements.

[0418] Embodiment 20: The method of embodiment 19, wherein the hash of the additional data block is a number, wherein the requirement on the hash of the additional data block is that the hash of the additional data block is less than a predetermined number.

[0419] Embodiment 21: A method according to one of the preceding embodiments, wherein the first ledger is a blockchain, a block tree and / or a tangle.

[0420] Embodiment 22: A method as described in any one of embodiments 1 to 20, wherein determining the additional link information includes proof of work, and wherein the first ledger is a blockchain.

[0421] Embodiment 23: A method according to any one of embodiments 1 to 20, wherein determining the additional link information includes proof of work, and wherein the first ledger is a block tree.

[0422] Embodiment 24: The method of any one of embodiments 1 to 20, wherein determining the additional link information comprises proof of work, and wherein the first ledger is a tangle.

[0423] Embodiment 25: A method as in any one of embodiments 1 to 20, wherein determining the additional link information comprises proof of stake, and wherein the first ledger is a blockchain.

[0424] Embodiment 26: A method according to any one of embodiments 1 to 20, wherein determining the additional link information includes proof of stake, and wherein the first ledger is a block tree.

[0425] Embodiment 27: The method of any one of Embodiments 1 to 20, wherein determining the additional linking information comprises proof of stake, and wherein the first ledger is a tangle.

[0426] Embodiment 28: A method as in any one of embodiments 1 to 20, wherein determining the additional link information comprises proof of elapsed time, and wherein the first ledger is a blockchain.

[0427] Embodiment 29: A method according to any one of embodiments 1 to 20, wherein determining the additional link information includes proof of elapsed time, and wherein the first ledger is a block tree.

[0428] Embodiment 30: The method of any one of embodiments 1 to 20, wherein determining the additional link information comprises a proof of elapsed time, and wherein the first ledger is a tangle.

[0429] Embodiment 31: A method according to any one of embodiments 21 to 30, wherein the first ledger includes a side chain, wherein the side chain is a blockchain, a block tree and / or a tangle.

[0430] Embodiment 32: The method of any preceding embodiment, wherein the first ledger is accessible only from within the trusted network.

[0431] Embodiment 33: A method according to one of the preceding embodiments, wherein the further data blocks and / or the further medical data sets comprise smart contracts.

[0432] Embodiment 34: The method according to one of the preceding embodiments, further comprising:

[0433] - receiving, using the block validation unit, a second ledger, wherein the second ledger includes a data block,

[0434] - transferring the further data block to the block verification unit using the interface,

[0435] - verifying the additional link information based on the second ledger using the block verification unit,

[0436] - In case of positive verification, inserting a further data block into the second ledger using the block verification unit.

[0437] Embodiment 35: The method of embodiment 34, wherein each of the data blocks of the second ledger includes a medical data set and linking information, wherein the linking information includes a hash of at least one of the second ledgers.

[0438] Embodiment 36: A method according to embodiment 34 or 35, wherein the second ledger includes at least one parent data block of the additional data block, and wherein the step of verifying the additional linking information is based on at least one parent data block of the additional data block.

[0439] Embodiment 37: A method according to embodiment 36, wherein in the step of verifying the further linking information, a hash of at least one parent data block is compared with a hash contained in the further linking information.

[0440] Embodiment 38: A method according to one of embodiments 34 to 37, wherein determining additional link information includes the execution of a consensus algorithm, and wherein verifying the additional link information includes: verifying the actual execution of the consensus algorithm.

[0441] Embodiment 39: The method according to embodiment 38, further comprising:

[0442] - receiving, with the block verification unit, a request for a hash of a further block of data;

[0443] The verifying of the additional link information includes: verifying that the hash of the additional data block meets the requirement.

[0444] Embodiment 40: The method of embodiment 39, wherein the hash of the additional data block is a number, wherein the requirement on the hash of the additional data block is that the hash of the additional data block is less than a predetermined number.

[0445] Embodiment 41: A method for verifying an additional data block to be inserted into a second ledger, wherein the second ledger includes the data block, the method comprising the steps of:

[0446] - receiving the second ledger using the interface,

[0447] - receiving a further data block using the interface, wherein the further data block comprises a further medical data set and further linking information,

[0448] wherein the further linking information comprises a hash of at least one of the data blocks of the second ledger,

[0449] - verifying the further link information based on the second ledger using the computing unit,

[0450] In the event of a positive verification, a further data block is inserted into the second ledger by means of the computing unit.

[0451] Embodiment 42: The method of embodiment 41, wherein each of the data blocks of the second ledger comprises a medical data set and linking information, wherein the linking information comprises a hash of at least one data block of the second ledger.

[0452] Embodiment 43: A method according to embodiment 41 or 42, wherein the second ledger includes at least one parent data block of the additional data block, and wherein the step of verifying the additional linking information is based on at least one parent data block of the additional data block.

[0453] Embodiment 44: A method according to embodiment 43, wherein in the step of verifying the further linking information, a hash of at least one parent data block is compared with a hash contained in the further linking information.

[0454] Embodiment 45: A method according to one of embodiments 41 to 44, wherein the additional link information is based on a consensus algorithm, and wherein verifying the additional link information includes: verifying the actual execution of the consensus algorithm.

[0455] Embodiment 46: The method according to embodiment 45, further comprising:

[0456] - receiving, using the interface, a request for a hash of another data block;

[0457] The verifying of the additional link information includes: verifying that the hash of the additional data block meets the requirement.

[0458] Embodiment 47: The method of embodiment 46, wherein the hash of the additional data block is a number, wherein the requirement on the hash of the additional data block is that the hash of the additional data block is less than a predetermined number.

[0459] Embodiment 48: A block creation unit for inserting an additional data block into a first ledger, wherein the first ledger includes data blocks, and the block creation unit includes the following units:

[0460] - an interface configured for receiving a further medical data set,

[0461] a computing unit configured to determine a further data block, wherein the further data block comprises a further medical data set and further linking information, wherein the further linking information comprises a hash of at least one of the data blocks of the first ledger,

[0462] Also configured to insert an additional block of data into the first ledger.

[0463] Embodiment 49: The block creation unit according to embodiment 48 is further configured to execute the method according to one of embodiments 2 to 32.

[0464] Embodiment 50: A medical device comprising a block creation unit according to embodiment 48 or 49.

[0465] Embodiment 51: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of the method for inserting a further data block into a first ledger according to one of embodiments 1 to 32.

[0466] Embodiment 52: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 1 to 32 are performed.

[0467] Embodiment 53: A block verification unit for verifying a further data block to be inserted into a second ledger, wherein the second ledger comprises the data block, the block verification unit comprising the following units: - an interface configured to receive the second ledger,

[0468] is further configured to receive a further data block, wherein the further data block comprises a further medical data set and further linking information, wherein the further linking information comprises a hash of at least one of the data blocks of the second ledger,

[0469] A computing unit configured to verify the further linking information based on the second ledger and further configured to, in case of a positive verification, insert the further data block into the second ledger.

[0470] Embodiment 54: The block verification unit according to Embodiment 53 is further configured to execute the method according to one of Embodiments 42 to 47.

[0471] Embodiment 55: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of a method for verifying a further data block to be inserted into a second ledger according to one of embodiments 41 to 47.

[0472] Embodiment 56: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to one of embodiments 41 to 47 are performed.

[0473] Embodiment 57: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 48 or 49 and comprising a block verification unit according to embodiment 53 or 54.

[0474] Embodiment 58: The ledger synchronization system according to Embodiment 57 is further configured to perform the method according to any one of Embodiments 34 to 40.

[0475] Embodiment 59: A computer program product comprising a program element which, when loaded into a memory unit of a ledger synchronization system, causes the ledger synchronization system to perform the steps of a method for inserting an additional data block into a first ledger according to one of embodiments 34 to 40.

[0476] Embodiment 60: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a ledger synchronization system so that when the program elements are executed by the ledger synchronization system, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 34 to 40 are performed.

[0477] Embodiment 61: The method of any one of embodiments 1 to 40, wherein the further medical data set is a log of accesses to medical data records by the entity,

[0478] And wherein the further medical data set comprises an identifier of the medical data record and an identifier of an entity accessing the medical data record.

[0479] Embodiment 62: The method of Embodiment 61, wherein the identifier of the medical data record is a hash value of the medical data record.

[0480] Embodiment 63: A method according to embodiment 61 or 62, wherein the additional medical data set also includes a timestamp corresponding to the time of the entity's access to the medical data record.

[0481] Embodiment 64: A method according to any one of embodiments 61 to 63, wherein the identifier of the entity is based on a private key assigned to the entity.

[0482] Embodiment 65: A method according to embodiment 64, wherein the identifier of the entity includes a signature signed using a private key assigned to the entity.

[0483] Embodiment 66: A method according to embodiment 65, wherein the signature is based on the medical data record, in particular, based on a hash value of the medical data record.

[0484] Embodiment 67: A method according to embodiment 65 or 66, wherein the medical data set also includes a timestamp corresponding to the time of the entity's access to the medical data record, and wherein the signature is based on the timestamp.

[0485] Embodiment 68: The method of any one of Embodiments 61 to 67, wherein the step of receiving a further medical data set comprises the following steps:

[0486] - receiving, using the interface, a request for access to the medical data record from an entity, and

[0487] - determining, by means of the computing unit, the further medical data set based on the access request and based on the medical data record.

[0488] Embodiment 69: The method according to embodiment 68 further comprises the following steps:

[0489] - perform checks on entities’ authorization to access medical data records,

[0490] - In case of positive check, the entity is granted access.

[0491] Embodiment 70: The method according to embodiment 69 further comprises the following steps:

[0492] - In case of a negative check, denying access to the entity, wherein the medical data set includes a record of the denial.

[0493] Embodiment 71: A method according to any one of Embodiments 41 to 47, wherein the additional data block is determined by a method according to any one of Embodiments 61 to 70.

[0494] Embodiment 72: The block creation unit according to embodiment 48 or 49 is further configured to execute the method according to one of embodiments 61 to 70.

[0495] Embodiment 73: A medical device comprising a block creation unit according to embodiment 72.

[0496] Embodiment 74: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of the method for inserting a further data block into a first ledger according to one of embodiments 61 to 70.

[0497] Embodiment 75: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 61 to 70 are performed.

[0498] Embodiment 76: The block verification unit described in embodiment 53 is also configured to execute the method described in embodiment 71.

[0499] Embodiment 77: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of the method for verifying a further data block to be inserted into a second ledger according to embodiment 71.

[0500] Embodiment 78: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to embodiment 71 are performed.

[0501] Embodiment 79: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 72 or 73 and comprising a block verification unit according to embodiment 76.

[0502] Embodiment 80: The method of any one of embodiments 1 to 40, wherein the further medical data set is a log of the entity's access to the medical device,

[0503] Therein, the additional medical data set includes an identifier of the medical device and an identifier of an entity accessing the medical device.

[0504] Embodiment 81: A method according to embodiment 80, wherein the identifier of the medical device is based on a model number of the medical device and / or a serial number of the medical device.

[0505] Embodiment 82: A method according to one of embodiments 80 or 81, wherein the additional medical data set also includes a timestamp corresponding to the time of the entity's access to the medical device.

[0506] Embodiment 83: A method according to any one of embodiments 80 to 82, wherein the identifier of the entity is based on a private key assigned to the entity.

[0507] Embodiment 84: A method according to embodiment 83, wherein the identifier of the entity includes a signature signed using a private key assigned to the entity.

[0508] Embodiment 85: A method according to embodiment 84, wherein the signature is based on an identifier of the medical device.

[0509] Embodiment 86: A method according to embodiment 84 or 85, wherein the additional medical data set further includes a timestamp corresponding to a time of access of the entity to the medical device and / or a timestamp corresponding to a time of exit of the entity from the medical device,

[0510] And wherein the signature is based on a timestamp.

[0511] Embodiment 87: A method according to embodiments 80 to 86, wherein access to the medical device is remote access.

[0512] Embodiment 88: The method of embodiment 87, wherein the medical data set includes a time of access by an entity to a medical device, wherein the time of the access corresponds to a time when remote access to the medical device was established.

[0513] Embodiment 89: A method according to embodiment 87 or 88, wherein the medical data set includes a time when the entity leaves the medical device, wherein the time of departure corresponds to a time when remote access to the medical device is terminated.

[0514] Embodiment 90: The method according to any one of embodiments 87 to 89, further comprising the following steps:

[0515] -Sending a notification message to an owner of the medical device using the interface, wherein the notification message is based on an identifier of the medical device and an identifier of a person accessing the medical device.

[0516] Embodiment 91: A method according to embodiment 90, wherein sending the notification message is facilitated by means of a smart contract.

[0517] Embodiment 92: The method of embodiments 80 to 91, wherein the entity's access to the medical device includes changes to the medical device, and wherein the medical data set includes a record of the changes.

[0518] Embodiment 93: A method according to embodiment 92, wherein the change includes installing a hardware component and / or a software component within the medical device, and wherein the additional medical data set includes an identifier of the hardware component and / or an identifier of the software component.

[0519] Embodiment 94: The method of Embodiment 92 or 93, wherein the modification comprises removing a hardware component and / or a software component within the medical device, and wherein the medical data set comprises an identifier of the hardware component and / or the software component.

[0520] Embodiment 95: A method according to one of embodiments 92 to 94, wherein the change includes exchanging a first hardware component with a second hardware component, and wherein the medical data set includes an identifier of the first hardware component and an identifier of the second hardware component, and / or wherein the change includes exchanging a first software component with a second software component, and wherein the medical data set includes an identifier of the first software component and an identifier of the second software component.

[0521] Embodiment 96: A method according to any one of embodiments 93 to 95, wherein the software component is a security update for a medical device.

[0522] Embodiment 97: A method according to any one of embodiments 93 to 96, wherein the identifier of the software component includes a software version number.

[0523] Embodiment 98: A method according to any one of Embodiments 93 to 97, wherein the identifier of the hardware component includes a model number and / or a serial number of the hardware component.

[0524] Embodiment 99: A method according to any one of embodiments 93 to 98, wherein an identifier of a hardware component related to the hardware component is stored.

[0525] Embodiment 100: A method according to embodiment 99, wherein the hardware component includes an RFID chip, and wherein an identifier of the hardware component is stored on the RFID chip.

[0526] Embodiment 101: A method according to embodiment 99 or 100, wherein the hardware component includes a one-dimensional or two-dimensional optical code, and wherein an identifier of the hardware component is stored in the one-dimensional or two-dimensional optical code.

[0527] Embodiment 102: A method according to embodiment 101, wherein the optical code is a bar code.

[0528] Embodiment 103: A method according to embodiment 101, wherein the optical code is a QR code or an Aztec code.

[0529] Embodiment 104: The method of Embodiment 92, wherein the alteration is the use of a consumable material within the medical device and / or the refilling of a consumable material at the medical device.

[0530] Embodiment 105: The method of embodiment 104, wherein the additional medical data set does not include an identifier of an entity accessing the medical device.

[0531] Embodiment 106: A method according to embodiment 104 or 105, wherein the additional medical data set includes the amount of consumable material used during a medical procedure utilizing the medical device, and / or wherein the additional medical data set includes the amount of consumable material refilled at the medical device.

[0532] Embodiment 107: The method of any one of Embodiments 80 to 103, wherein the step of receiving an additional medical data set comprises:

[0533] - receiving, using the interface, an identifier of the medical device,

[0534] - receiving, using the interface, an identifier of a person accessing the medical device,

[0535] - Determining a further set of medical data based on an identifier of the medical device and based on an identifier of a person accessing the medical device.

[0536] Embodiment 108: The method of embodiment 107, wherein the entity performs a change in the medical device, wherein a record of the change is created, and wherein the step of receiving the additional medical data set comprises:

[0537] - Receive modified records using the interface;

[0538] Therein, the step of determining the further medical data set is based on the modified record.

[0539] Embodiment 109: The method of any one of Embodiments 80 to 108, wherein the first ledger records the number of times an entity has accessed the medical device to implement a pay-per-use model.

[0540] Embodiment 110: The method of any one of Embodiments 80 to 109, wherein the first ledger records actions performed by an entity utilizing a medical device to implement a pay-per-use model.

[0541] Embodiment 111: The method according to embodiment 109 or 110, further comprising the following steps:

[0542] - performing a check whether further access to the medical device by the entity and / or further actions performed by the entity using the medical device are covered by a pay-per-use model,

[0543] In the event of a positive check, the entity having access to the medical device is granted access to the medical device by means of the computing unit.

[0544] Embodiment 112: The method according to any one of embodiments 80 to 111, further comprising the following steps:

[0545] - Using the computing unit to grant access to the medical device to an entity having access to the medical device.

[0546] Embodiment 113: A method according to any one of Embodiments 41 to 47, wherein the further data block is determined by a method according to any one of Embodiments 80 to 112.

[0547] Embodiment 114: The block creation unit according to embodiment 48 or 49 is further configured to perform the method according to one of embodiments 80 to 112.

[0548] Embodiment 115: A medical device comprising a block creation unit according to embodiment 114.

[0549] Embodiment 116: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of the method for inserting a further data block into a first ledger according to one of embodiments 80 to 112.

[0550] Embodiment 117: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 80 to 112 are performed.

[0551] Embodiment 118: The block verification unit according to embodiment 53 is further configured to execute the method according to embodiment 113.

[0552] Embodiment 119: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of the method for verifying a further data block to be inserted into a second ledger according to embodiment 113.

[0553] Embodiment 120: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to embodiment 113 are performed.

[0554] Embodiment 121: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 114 or 115 and comprising a block verification unit according to embodiment 118.

[0555] Embodiment 122: A method according to one of embodiments 1 to 40, wherein the additional medical data set is a log of the transmission of medical data records from the first entity to the second entity, wherein the additional medical data set includes an identifier of the medical data record and an identifier of the first entity and an identifier of the second entity.

[0556] Embodiment 123: The method of Embodiment 122, wherein the identifier of the medical data record is a hash value of the medical data record.

[0557] Embodiment 124: The method of embodiment 122 or 123, wherein the additional medical data set further comprises a timestamp corresponding to the transmission time of the medical data record.

[0558] Embodiment 125: A method according to one of embodiments 122 to 124, wherein the identifier of the first entity is based on a private key assigned to the first entity and / or wherein the identifier of the second entity is based on a private key assigned to the second entity.

[0559] Embodiment 126: A method according to embodiment 125, wherein the identifier of the first entity includes a first signature signed using a private key assigned to the first entity, and / or wherein the identifier of the second entity includes a second signature signed using a private key assigned to the second entity.

[0560] Embodiment 127: A method according to embodiment 126, wherein the first signature and / or the second signature is based on a medical data record, in particular, on a hash value of the medical data record.

[0561] Embodiment 128: The method of embodiment 126 or 127, wherein the log data set further includes a timestamp corresponding to a transmission time of the medical data record,

[0562] And wherein the first signature and / or the second signature is based on a timestamp.

[0563] Embodiment 129: The method of any one of Embodiments 122 to 128, wherein the medical data record is a medical data record of a patient, and wherein the medical data set includes consent information issued by the patient.

[0564] Embodiment 130: The method of any one of Embodiments 122 to 129, wherein the step of receiving a further medical data set comprises the following steps:

[0565] - receiving a transfer request related to a medical data record from a second entity via the interface,

[0566] - determining, by means of the computing unit, a further medical data set based on the transfer request and based on the medical data record.

[0567] Embodiment 131: The method according to embodiment 130, further comprising:

[0568] - Providing the medical data record to the second entity using the interface.

[0569] Embodiment 132: The method according to embodiment 131, further comprising:

[0570] - performing a check of the authorization of the second entity to access the medical data record using the computing unit;

[0571] Therein, the step of providing the medical data record is only performed if the result of the examination is positive.

[0572] Embodiment 133: The method according to any one of embodiments 122 to 132, further comprising the following steps:

[0573] - determining, by means of a computing unit, a modified medical data record based on the medical data record, wherein the modified medical data record comprises an identifier of the second entity,

[0574] -Provide the modified medical data record using the interface.

[0575] Embodiment 134: A method according to embodiment 133, wherein the medical data record includes a medical image, wherein the altered medical data record includes the medical image provided with a watermark, and wherein the watermark includes an identifier of the second entity.

[0576] Embodiment 135: A method according to embodiment 134, wherein the medical image includes a foreground area and a background area, and wherein the watermark is located only in the background area.

[0577] Embodiment 136: A method according to any one of Embodiments 41 to 47, wherein the additional data block is determined by a method according to any one of Embodiments 122 to 135.

[0578] Embodiment 137: The block creation unit according to embodiment 48 or 49 is further configured to execute the method according to one of embodiments 122 to 135.

[0579] Embodiment 138: A medical device comprising a block creation unit according to embodiment 137.

[0580] Embodiment 139: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of the method for inserting a further data block into a first ledger according to one of embodiments 122 to 135.

[0581] Embodiment 140: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 122 to 135 are performed.

[0582] Embodiment 141: The block verification unit described in embodiment 53 is also configured to perform the method described in embodiment 136.

[0583] Embodiment 142: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of the method for verifying a further data block to be inserted into a second ledger according to embodiment 136.

[0584] Embodiment 143: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to embodiment 136 are performed.

[0585] Embodiment 144: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 137 or 138 and comprising a block verification unit according to embodiment 141.

[0586] Embodiment 145: A method according to one of embodiments 1 to 40, wherein the additional medical data set corresponds to a admittance process for the medical device.

[0587] Embodiment 146: A method according to embodiment 145, wherein the medical device includes a trained artificial intelligence algorithm, and wherein the additional medical data set is based on the training data set used to train the artificial intelligence algorithm.

[0588] Embodiment 147: The method of Embodiment 146, wherein the step of receiving the additional medical data set comprises:

[0589] - Use the interface to receive the training data set,

[0590] - determining, using the computing unit, first parameters of the artificial intelligence algorithm,

[0591] - using a computing unit to perform a training step of an artificial intelligence algorithm based on a training data set,

[0592] - determining a second parameter of the artificial intelligence algorithm using the calculation unit,

[0593] - determining, by means of the calculation unit, the further medical data set based on the training data set and based on the first parameter and the second parameter.

[0594] Embodiment 148: A method according to embodiment 147, wherein the artificial intelligence algorithm includes an artificial neural network, and wherein the first parameter includes the weights of the edges of the artificial neural network before performing the training step, and wherein the second parameter includes the weights of the edges after performing the training step.

[0595] Embodiment 149: A method according to embodiment 148, wherein the first parameter includes the weights of all edges of the artificial neural network before performing the training step, and wherein the second parameter includes the weights of all edges of the artificial neural network after performing the training step.

[0596] Embodiment 150: A method according to any one of embodiments 146 to 149, wherein the training data set includes training images.

[0597] Embodiment 151: A method according to embodiment 150, wherein the training data set includes labels associated with training images.

[0598] Embodiment 152: The method of Embodiment 145, wherein the medical data set includes an identifier of a person who is a subject of the medical research.

[0599] Embodiment 153: A method according to embodiment 152, wherein the identifier of the person is a physical parameter of the person that uniquely identifies the person.

[0600] Embodiment 154: A method according to embodiment 153, wherein the identifier of the person corresponds to a fingerprint of the person, a DNA sequence of the person, or a biometric parameter of the person.

[0601] Embodiment 155: A method according to one of embodiments 152 to 154, wherein the medical data set includes first patient parameters corresponding to the person before the medical study, and wherein the medical data set also includes second patient parameters corresponding to the person after the medical study.

[0602] Embodiment 156: The method of any one of Embodiments 151 to 155, wherein the step of receiving an additional medical data set comprises:

[0603] - receiving, using the interface, an identifier of a person who is a subject of the medical research,

[0604] - determining, with the computing unit, a further medical data set based on an identifier of a person who is a subject of the medical investigation.

[0605] Embodiment 157: The method of Embodiment 155, wherein the step of receiving an additional medical data set comprises:

[0606] - receiving, using the interface, an identifier of a person who is a subject of the medical research,

[0607] - receiving, using the interface, first patient parameters corresponding to the person prior to the medical study,

[0608] - receiving, by means of the interface, second patient parameters corresponding to the person after the medical study,

[0609] - determining, with the computing unit, a further medical data set based on an identifier of a person who is a subject of the medical investigation and based on the first patient parameter and the second patient parameter.

[0610] Embodiment 158: The method of embodiment 145, wherein the additional medical data set corresponds to an admission process of the medical device by corresponding to a calibration of the medical device.

[0611] Embodiment 159: The method of embodiment 158, wherein the additional medical data set comprises an identifier of the medical device and a timestamp, wherein the timestamp corresponds to a calibration time of the medical device.

[0612] Embodiment 160: The method of embodiment 159, wherein the step of receiving the additional medical data set comprises the following steps:

[0613] - receiving, using the interface, an identifier of the medical device,

[0614] - determining, by means of the computing unit, a further medical data set based on the identifier of the medical device.

[0615] Embodiment 161: A method according to any one of Embodiments 158 to 160, wherein the further medical data set includes an identifier of an entity performing calibration of the medical device.

[0616] Embodiment 162: The method of embodiment 161, wherein the step of receiving the additional medical data set comprises the following steps:

[0617] - receiving an identifier of an entity performing calibration of the medical device,

[0618] - determining, with the computing unit, the further medical data set based on an identifier of the entity performing the calibration of the medical device, in particular also based on an identifier of the medical device.

[0619] Embodiment 163: The method of any one of Embodiments 158 to 162, wherein the additional medical data set includes calibration information based on calibration of the medical device.

[0620] Embodiment 164: The method of Embodiment 163, wherein the step of receiving the additional medical data set comprises the following steps:

[0621] - receive calibration information using the interface,

[0622] - determining, with the calculation unit, the further medical data set based on the calibration information, in particular also based on an identifier of the medical device and / or based on an identifier of an entity performing the calibration of the medical device.

[0623] Embodiment 165: The method of Embodiment 145, wherein the additional medical data set includes data documenting product development of the medical device.

[0624] Embodiment 166: The method of embodiment 165, wherein the additional medical data set includes data describing a specific version of software included in the medical device.

[0625] Embodiment 167: A method according to embodiment 166, wherein the data describing a specific version of the software describes a submission to a source code repository and / or a build within a continuous integration and / or continuous delivery system.

[0626] Embodiment 168: The method of embodiment 167, wherein the data describing the specific version of the software includes a hash of a commit to a source code repository and / or a hash of a build within a continuous integration and / or continuous delivery system.

[0627] Embodiment 169: The method of any one of Embodiments 165 to 168, wherein the further medical data set includes at least one signature for signing data documenting product development of the medical device.

[0628] Embodiment 170: A method according to one of embodiments 165 to 169, wherein the additional medical data set includes a smart contract, wherein the smart contract regulates the release of the medical device, in particular, regulates the release of a specific version of software contained in the medical device.

[0629] Embodiment 171: The method of Embodiment 170, wherein the specific version of the software is released if the medical data set includes a predefined set of signatures that sign data describing the specific version of the software.

[0630] Embodiment 172: The method of any one of Embodiments 165 to 169, wherein the additional medical data set includes a smart contract, wherein the smart contract governs access to data documenting product development of the medical device.

[0631] Embodiment 173: The method of embodiment 172, wherein the smart contract grants a regulatory agency access to data documenting product development of the medical device.

[0632] Embodiment 174: A method for determining the same person using a first ledger, wherein the additional data block is included in the first ledger according to one of embodiments 152 to 154, the method comprising the following steps:

[0633] - selecting, by means of a computing unit, a first medical data set contained in a first ledger, wherein the first medical data set comprises an identifier of the first person,

[0634] - selecting, by means of the computing unit, a second medical data set contained in the first ledger,

[0635] The second medical data set is different from the first medical data set.

[0636] and wherein the second medical data set includes an identifier of the second person,

[0637] - determining, using a computing unit, based on the identifier of the first person and the identifier of the second person, whether the first person and the second person are the same.

[0638] Embodiment 175: The method according to embodiment 174, further comprising:

[0639] - providing an alert message using the interface in the event that the first person is the same as the second person.

[0640] Embodiment 176: The method of Embodiment 174 or 175, wherein the first individual is a subject of a first medical study, wherein the second individual is a subject of a second medical study, and wherein the first study is the same as the second study.

[0641] Embodiment 177: The method according to one of embodiments 174 to 176, wherein the step of selecting the second medical data set and the step of determining are applied multiple times.

[0642] Embodiment 178: A computing unit for determining the same person using a first ledger, wherein an additional data block is included in the first ledger according to one of embodiments 152 to 154,

[0643] The computing unit is configured to select a first medical data set contained in a first ledger, wherein the first medical data set comprises an identifier of a first person,

[0644] The computing unit is further configured to select a second medical data set contained in the first ledger, wherein the second medical data set is different from the first medical data set, and wherein the second medical data set includes an identifier of the second person,

[0645] The computing unit is further configured to determine whether the first person and the second person are the same based on the identifier of the first person and the identifier of the second person.

[0646] Embodiment 179: The computing unit according to embodiment 178 is further configured to execute the method according to one of embodiments 175 to 177.

[0647] Embodiment 180: A computer program product comprising program elements, which, when loaded into a computing unit, cause the computing unit to execute the steps of the method for determining the same person using a first ledger according to one of embodiments 174 to 177.

[0648] Embodiment 181: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a computing unit so that when the program elements are executed by the computing unit, the steps of the method for determining the same person using a first ledger according to one of embodiments 174 to 177 are performed.

[0649] Embodiment 182: A method according to any one of Embodiments 41 to 47, wherein the additional data block is determined by a method according to any one of Embodiments 145 to 173.

[0650] Embodiment 183: The block creation unit according to embodiment 48 or 49 is also configured to perform the method according to one of embodiments 145 to 173.

[0651] Embodiment 184: A medical device comprising a block creation unit according to embodiment 183.

[0652] Embodiment 185: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of a method for inserting an additional data block into a first ledger according to one of embodiments 145 to (D25).

[0653] Embodiment 186: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger as described in one of Embodiments 145 to (D25) are performed.

[0654] Embodiment 187: The block verification unit described in embodiment 53 is also configured to execute the method described in embodiment 182.

[0655] Embodiment 188: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of the method for verifying a further data block to be inserted into a second ledger according to embodiment 182.

[0656] Embodiment 189: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to embodiment 182 are performed.

[0657] Embodiment 190: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 183 or 184 and comprising a block verification unit according to embodiment 187.

[0658] Embodiment 191: The method of any one of embodiments 1 to 40, wherein the additional medical data set is related to educational activities of a medical professional,

[0659] And wherein the additional medical data set includes an identifier of the medical professional and an identifier of the educational action.

[0660] Embodiment 192: The method of embodiment 191, wherein the educational actions are supervised and / or rated by an educational entity,

[0661] The medical data set includes the signature of the identifier of the educational action and the signature of the identifier of the medical professional.

[0662] And wherein the signature is signed by an educational entity.

[0663] Embodiment 193: The method of any one of Embodiments 191 or 192, wherein the step of receiving the medical data set comprises:

[0664] - provide medical data records to medical professionals through interfaces,

[0665] wherein the first medical information is assigned to the medical data record,

[0666] - receiving second medical information from a medical professional via the interface,

[0667] - determining a comparison value by a calculation unit based on the first medical information and based on the second medical information; wherein the medical data set is based on the comparison value.

[0668] Embodiment 194: The method of Embodiment 193, wherein the first medical information is diagnostic information about a medical data record determined by another entity, and wherein the second medical information is diagnostic information about a medical data record determined by a medical professional.

[0669] Embodiment 195: A method according to embodiment 194, wherein the medical data record and the first medical information are synthetically generated data.

[0670] Embodiment 196: The method of Embodiment 194, wherein the medical data record corresponds to a patient, and wherein the first medical information was created by an experienced medical professional.

[0671] Embodiment 197: A method according to any one of embodiments 194 to 196, wherein the medical data record includes medical images and / or medical laboratory reports.

[0672] Embodiment 198: A method for verifying a medical professional's experience using a first ledger after inserting an additional data block according to one of embodiments 194 to 197, comprising the steps of:

[0673] - receiving the first ledger using the interface,

[0674] - receiving, using the interface, an identifier of the medical professional,

[0675] - using the interface to receive the identifier of the educational action,

[0676] - determining, using the computing unit, the relevant data block of the first ledger,

[0677] The relevant data block is a data block of the first ledger including the relevant medical data set,

[0678] and wherein the relevant medical dataset is a medical dataset comprising an identifier of a medical professional and an identifier of an educational action,

[0679] -Determine educational parameters based on relevant data blocks.

[0680] Embodiment 199: A method according to embodiment 198, wherein the educational parameter is the number of related data blocks.

[0681] Embodiment 200: The method according to embodiment 198 or 199, further comprising:

[0682] - Receive minimum education requirements using the interface;

[0683] Among other things, the education parameter is also based on the minimum education requirements.

[0684] Embodiment 201: A method according to embodiment 200, wherein the minimum educational requirement is a minimum number of educational actions to be performed, and wherein the educational parameter is based on a comparison of the number of relevant data blocks and the minimum number of educational requirements.

[0685] Embodiment 202: The method according to any one of embodiments 198 to 201, further comprising the following steps:

[0686] - receiving a threshold comparison value using an interface; wherein the relevant medical data set is a medical data set including the comparison value being above or below the threshold.

[0687] Embodiment 203: An experience verification unit for verifying the experience of a medical professional using a first ledger after inserting an additional data block according to one of embodiments 194 to 197, comprising:

[0688] - an interface configured to receive a first ledger,

[0689] is further configured to receive an identifier of a medical professional,

[0690] is further configured to receive an identifier of the educational action,

[0691] - a computing unit configured for determining a relevant data block of the first ledger, wherein the relevant data block is a data block of the first ledger comprising a relevant medical data set, and wherein the relevant medical data set is a medical data set comprising an identifier of a medical professional and an identifier of an educational action,

[0692] It is also configured to determine educational parameters based on the relevant data blocks.

[0693] Embodiment 204: The experience verification unit described in embodiment 203 is also configured to execute the method described in one of embodiments 199 to 202.

[0694] Embodiment 205: A computer program product comprising program elements which, when loaded into a memory unit of an experience verification unit, cause the experience verification unit to execute the steps of a method for verifying the experience of a medical professional according to one of embodiments 198 to 202.

[0695] Embodiment 206: A computer-readable medium having program elements stored thereon, wherein the program elements can be read and executed by an experience verification unit so that when the program elements are executed by the experience verification unit, the steps of the method for verifying the experience of a medical professional according to one of embodiments 198 to E41 are performed.

[0696] Embodiment 207: A method according to one of embodiments 41 to 47, wherein the additional data block is determined by a method according to one of embodiments 191 to 197.

[0697] Embodiment 208: The block creation unit according to embodiment 48 or 49 is also configured to execute the method according to one of embodiments 191 to 197.

[0698] Embodiment 209: A medical device comprising a block creation unit according to embodiment 208.

[0699] Embodiment 210: A computer program product comprising a program element which, when loaded into a memory unit of a block creation unit, causes the block creation unit to perform the steps of a method for inserting a further data block into a first ledger according to one of embodiments 191 to 197.

[0700] Embodiment 211: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block creation unit so that when the program elements are executed by the block creation unit, the steps of the method for inserting an additional data block into a first ledger according to one of embodiments 191 to 197 are performed.

[0701] Embodiment 212: The block verification unit according to embodiment 53 is also configured to execute the method according to embodiment 207.

[0702] Embodiment 213: A computer program product comprising program elements which, when loaded into a memory unit of a block verification unit, cause the block verification unit to perform the steps of the method for verifying a further data block to be inserted into a second ledger according to embodiment 207.

[0703] Embodiment 214: A computer-readable medium having program elements stored thereon, the program elements being readable and executable by a block verification unit so that when the program elements are executed by the block verification unit, the steps of the method for verifying another data block to be inserted into a second ledger according to embodiment 207 are performed.

[0704] Embodiment 215: A ledger synchronization system for inserting an additional data block into a first ledger and a second ledger, comprising a block creation unit according to embodiment 208 or 209 and comprising a block verification unit according to embodiment 212. BRIEF DESCRIPTION OF THE DRAWINGS

[0705] The nature, features and advantages of the present invention, its above-mentioned embodiments and aspects, and the manner in which they are achieved become clearer and more easily understood from the following description and embodiments which will be described in detail in the context of the accompanying drawings. The following description does not limit the present invention to the embodiments included. In different figures, the same reference numerals may be used to mark the same components or parts. Generally, the figures are not to scale. In the following:

[0706] Figure 1 A flow chart showing a first embodiment of a method for inserting an additional data block into a first ledger;

[0707] Figure 2 A flow chart showing an embodiment of a method for validating a further block of data to be inserted into a second ledger;

[0708] Figure 3 A flow chart showing a second embodiment of a method for inserting an additional data block into a first ledger;

[0709] Figure 4 An embodiment of a ledger synchronization system including a block creation unit and a block verification unit is shown;

[0710] Figure 5 A first embodiment of a ledger is shown, wherein the ledger is a blockchain;

[0711] Figure 6 A second embodiment of the ledger is shown, wherein the ledger is a tree of blocks;

[0712] Figure 7 A third implementation of a ledger is shown, wherein the ledger is a tangle;

[0713] Figure 8 A third embodiment of a ledger is shown, wherein the ledger includes a sidechain;

[0714] Fig. 9 A first implementation of a data block is shown;

[0715] Fig.10 A second implementation of the data block is shown;

[0716] Fig.11 A third implementation of a data block is shown;

[0717] Fig.12 An embodiment of a method for inserting an additional block of data into a first ledger that may be used to record access to a medical data record is shown;

[0718] Fig.13 Another embodiment of a method for inserting an additional data block into a first ledger that can be used to record access to a medical data record is shown;

[0719] Fig.14 An embodiment of a first ledger for recording access to a medical data record is shown;

[0720] Fig.15 An embodiment of a method for inserting an additional block of data into a first ledger that can be used to record access to a medical device is shown;

[0721] Fig.16 An embodiment of a first ledger for recording access to a medical device is shown;

[0722] Fig.17 Another embodiment of a method for inserting an additional block of data into a first ledger that can be used to record access to a medical device is shown;

[0723] Fig.18Another embodiment of a first ledger for recording access to a medical device is shown;

[0724] Fig.19 An embodiment of a method for inserting an additional data block into a first ledger that can be used to record the transfer of a medical data record is shown;

[0725] Fig. 20 Another embodiment of a method for inserting an additional data block into a first ledger that can be used to record the transfer of a medical data record is shown;

[0726] Fig.21 Another embodiment of a method for inserting an additional data block into a first ledger that can be used to record the transfer of a medical data record is shown;

[0727] Fig. 22 An embodiment of a first ledger for recording the transfer of medical data records is shown;

[0728] Fig.23 An embodiment of a method for inserting an additional data block into a first ledger related to an admission process for a medical device is shown;

[0729] Fig.24 An implementation of a first ledger related to an admission process for a medical device is shown;

[0730] Fig.25 Another embodiment of a method for inserting an additional data block into a first ledger, the first ledger being related to an admission process for a medical device, is shown;

[0731] Fig.26 Another embodiment of a first ledger related to an admission process for a medical device is shown;

[0732] Fig. 27 A flow chart showing a method for using a first ledger in connection with an admission process for a medical device;

[0733] Fig.28 An embodiment of a method for inserting an additional block of data into a first ledger that can be used to record educational actions of a medical professional is shown;

[0734] Fig.29 An embodiment of a first ledger for recording educational actions of a medical professional is shown;

[0735] Fig.30Another embodiment of a method for inserting an additional block of data into a first ledger that can be used to record educational actions of a medical professional is shown;

[0736] Fig.31 Another embodiment of a first ledger for recording educational actions of a medical professional is shown;

[0737] Fig.32 A flow chart of an embodiment of a method for verifying a medical professional's experience using a first ledger is shown. DETAILED DESCRIPTION

[0738] Figure 1 A flow chart of an embodiment of a method for inserting a further data block FDB into a first ledger LDG, wherein the first ledger comprises data blocks DB.i, DB.j, DB.k. The method is performed by a block creation unit BCU, in particular by an interface BCU.IF of the block creation unit and by a calculation unit BCU.CU of the block creation unit.

[0739] The first step of the embodiment shown is to receive the REC-FDS further medical data set FDS using the interface BCU.IF. The optional second step of the embodiment shown is to receive the REC-LDG-1 first ledger LDG using the interface BCU.IF. Alternatively, the step of receiving the REC-LDG-1 first ledger LDG can be performed before the step of receiving the REC-FDS further medical data set FDS, or the step of receiving the REC-LDG-1 first ledger LDG can be performed in parallel with the step of receiving the REC-FDS further medical data set FDS. In other words, both steps are independent of each other.

[0740] In this embodiment, the first ledger LDG is a blockchain, which means that each of the data blocks DB.i, DB.j, DB.k (except for the single starting data block) contained in the first ledger LDG has exactly one parent data block DB.i, DB.j, DB.k, and each of the data blocks DB.i, DB.j, DB.k (except for the single last data block) has exactly one direct successor data block. Figure 5 An example of a blockchain can be found in , consisting of a single starting data block DB.1 and a single last data block DB.7.

[0741] Each of the data blocks DB.i, DB.j, DB.k included in the first ledger includes link information that associates the data blocks DB.i, DB.j, DB.k with their parent data blocks. In particular, each of the data blocks DB.i, DB.j, DB.k includes a hash based on its parent data block. In this embodiment, the hash is the result of applying the SHA256 hash function to the data of the parent data block. In addition, each of the data blocks DB.i, DB.j, DB.k includes a medical data set MDS.j, MDS.k. Alternatively, it is also possible that the blockchain includes the following blocks DB.i, DB.j, DB.k, which do not include medical data sets MDS.j, MDS.k but include non-medical data sets.

[0742] Furthermore, each of the data blocks DB.i, DB.j, DB.k included in the first ledger comprises a random number RN.j, RN.k selected so that the hash H(DB.i), H(DB.j), H(DB.k) of said data block DB.i, DB.j, DB.k satisfies a certain condition. In the embodiment shown, the condition is that the hash H(DB.i), H(DB.j), H(DB.k) of said data block DB.i, DB.j, DB.k is less than a given threshold.

[0743] In this embodiment, the hash H(DB.j) of the data block DB.j is calculated as H(DB.j)=SHA256(H(MDS.j)+H(DB.i)+RN.j), where the SHA256 hash function may be replaced by any other suitable hash function. The operation "+" may be understood as arithmetic addition of numbers or concatenation of strings (by converting the numbers into strings before concatenation). In particular, the hash H(MDS.j) of the medical dataset MDS.j may be the Merkle root of the medical dataset MDS.j. Alternatively, the hash H(DB.j) of the data block DB.j may also be based on other data items contained in the data block.

[0744] The next optional step of the embodiment shown is to select the SEL-PDB parent data block from the data blocks of the first ledger using the calculation unit BCU.CU. In the embodiment shown, the parent data block is a single data block DB.i, DB.j, DB.k of the first ledger LDG that has no direct successor. Figure 5In the blockchain shown in , the parent data block is data block DB.7. Alternatively, there may be a fork in the first ledger LDG as a blockchain, which means that there are several data blocks DB.i, DB.j, DB.k of the first ledger LDG that have no direct successors. In this case, the parent data block is the data block from the set of data blocks DB.i, DB.j, DB.k that have no direct successors that has the largest distance from the starting data block.

[0745] The next step of the shown embodiment is to determine a further data block FDB of the DET-FDB using the computing unit BCU.CU, wherein the further data block FDB comprises a further medical data set FDS and further link information, wherein the further link information comprises a hash H(DB.i), H(DB.j), H(DB.k) of at least one of the data blocks DB.i, DB.j, DB.k of the first ledger LDG.

[0746] In particular, the step of determining the further data blocks FDB of the DET-FDB comprises the execution of a consensus algorithm. In this embodiment, the consensus algorithm is a computationally or CPU-bound proof of work, in particular the proof of work involves a computing unit BCU.CU of the block creation unit BCU. Alternatively, the consensus algorithm may be a memory-bound proof of work (in particular, in order to determine the further data blocks of the DET-FDB, a certain amount of memory needs to be allocated in the memory unit BCU.MU of the block creation unit), a network-bound proof of work (in particular, in order to determine the further data blocks of the DET-FDB, many network nodes or difficult-to-reach network nodes need to be accessed), proof of stake, proof of elapsed time or proof of storage or any other consensus algorithm.

[0747] In particular, for the proof of the computational limit, the number or the number of steps f(n) for determining the additional data block of the DET-FDB has a higher asymptotic behavior in terms of the problem complexity n than the number or the number of computational steps g(n) for verifying the additional data block FDB of the VERF in the block verification unit BVU. In other words, it is not possible to find a constant M such that the formula |g(n)|<M·|f(n)| is valid for all n>n0.

[0748] An example of a proof of work with computational constraints is to find arguments to a hash function such that the result of the hash function satisfies a certain criterion (e.g., is less than a given number or has a given structure). Since hash functions are one-way functions, the only possibility is to try many arguments by brute force. In particular, the certain criterion may be that the result of the hash function as a binary number must include n leading zeros (so that n in this case is the problem complexity), which results in the number of hash functions to be calculated being f(n)→2 for determining the new link information NLI for DET-NLI n And g(n)=1 for verifying VERF link information.

[0749] Known cryptographic hash functions are “Snefru”, “N-hash”, “FFT-hash”, “MD4”, “MD5”, “SHA” (in particular “SHA-0”, “SHA-1”, “SHA-256”, “SHA-384” and “SHA-512”), “RIPEMD”, “HAVAL”, “TIGER”, “PANAMA”, “WHIRLPOOL”, “SMASH”, “FORK-256”, “SHA-3”, “BLAKE” or other hash functions based on the Merkle-Damgard construction or the Sponge construction.

[0750] In the embodiment shown, determining the further data block FDB of the DET-FDB comprises: determining the random number RN.1 of the further data block FDB such that the hash H(FDB) of the further data block satisfies a certain condition, in this embodiment such that the hash H(FDB) of the further data block FDB is less than a given threshold T. Since the hash function is a one-way function, in order to determine the random number RN.1 of the further data block FDB, several random numbers must be tested by the following operations: test-calculating the hash H(FDB) of the further data block FDB and checking whether the hash H(FDB) of the further data block FDB is below a threshold. The hash H(FDB) of the further data block FDB is defined as the hashes H(DB.i), H(DB.j), H(DB.k) of the other data blocks DB.i, DB.j, DB.k.

[0751] In addition to the computation-limited proof of work, a memory-limited proof of work can also be used. In particular, for the memory-limited proof, the number of values f(n) to be temporarily stored (in the memory unit BCU.MU of the block creation unit) to determine additional data blocks FDB for DET-FDB has a higher asymptotic behavior in terms of the problem complexity n than the number of values g(n) to be temporarily stored (in the memory unit BVU.MU of the block verification unit) to verify additional data blocks FDB for VERF. In other words, a constant M may not be found such that for all n > n0, the expression |g(n)| < M·|f(n)| is valid.

[0752] An example of a memory-limited proof of work is finding a cycle of a given length l in a random graph with n nodes, where the number of nodes n is the problem complexity. In this example, the number of values to be stored is f(n) → n for finding the cycle of length l to determine new link information for DET-NLI and g(n) → l for verifying the cycle for VERF to verify new link information NLI.

[0753] The next step of the illustrated embodiment is to include additional data blocks FDB including INS-FDB-1 into the first ledger LDG using the computing unit BCU.CU. In this embodiment, the additional data blocks FDB are included into the first ledger LDG by storing the additional data blocks FDB in the memory unit BCU.MU, where the memory unit BCU.MU stores at least some blocks of the first ledger LDG. In particular, the identifier of the additional data blocks FDB - in particular, the hash H(FDB) of the additional data blocks FDB - can be stored in an array or list of all data blocks of the first ledger LDG, where the array or list is stored in association with the data blocks of the first ledger.

[0754] Another optional step of the illustrated embodiment is to provide the additional data blocks FDB of PROV-FDB using the interface BCU.IF. In particular, the additional data blocks FDB can be sent to the block verification unit BVU. In particular, the additional data blocks FDB can also be made publicly available by uploading the additional data blocks FDB to a web server.

[0755] Figure 2 A flowchart of an embodiment of a method for verifying additional data blocks FDB to be inserted into a second ledger is shown, where the second ledger includes data blocks DB.i, DB.j, DB.k. The method is performed by the block verification unit BVU - in particular, by the interface BVU.IF of the block verification unit BVU and by the computing unit BVU.CU of the block verification unit BVU.

[0756] The first step of the embodiment shown is to receive the REC-FDB further data block FDB using the interface BVU.IF, wherein the further data block FDB includes a further medical data set FDS and further link information, wherein the further link information includes a hash of at least one of the data blocks DB.i, DB.j, DB.k of the second ledger. The second step of the embodiment shown is to receive the REC-LDG-2 second ledger using the block verification unit BVU, in particular using the interface BVU.IF of the block verification unit BVU. Alternatively, the step of receiving the REC-LDG-2 second ledger LDG can be performed before the step of receiving the REC-FDB further data block FDB, or the step of receiving the REC-LDG-2 second ledger can be performed in parallel with the step of receiving the REC-FDB further data block FDB. In other words, the two steps are independent of each other.

[0757] In this embodiment, the second ledger is a blockchain comprising data blocks DB.i, DB.j, DB.k also contained in the first ledger. In particular, the second ledger may also include all data blocks DB.i, DB.j, DB.k of the first ledger LDG in addition to the further data block FDB. In particular, the second ledger includes the parent data block of the further data block FDB.

[0758] The next step of the embodiment shown is to verify the VERF further linking information based on the second ledger using the block verification unit BVU, in particular using the calculation unit BVU.CU of the block verification unit BVU. In this embodiment, the further data block FDB comprises a hash value of at least one of the data blocks DB.i, DB.j, DB.k of the second ledger, here the hash value H(DB.k) of the data block DB.k and a random number RN.1. Furthermore, in order to be a valid block, the hash H(FDB) of the further data block FDB must satisfy a given condition, for example, the H(FDB) of the further data block FDB must be below a given threshold. Therefore, in this embodiment, in order to verify the VERF further linking information, the hash H(FDB) of the further data block FDB must be calculated as H(FDB)=SHA256(H(FDS)+H(DB.k)+RN.1), and it must be verified that H(FDB) is below the threshold.

[0759] The last step of the embodiment shown is that in the case of a positive verification, the further data block FDB is inserted into the second ledger INS-FDB-2 by means of the block verification unit BVU, in particular by means of the calculation unit BVU.CU of the block verification unit. In this embodiment, the further data block FDB is included in the second ledger by storing the further data block FDB in a memory unit BVU.MU of the block verification unit BVU, wherein the memory unit BCU.MU stores at least some blocks of the second ledger LDG. In particular, the identifier of the further data block FDB, in particular the hash H(FDB) of the further data block FDB, can be stored in an array or list of all data blocks of the second ledger, wherein the array or list is stored in association with the data blocks of the second ledger.

[0760] Figure 3 A second embodiment of the method for inserting a further data block FDB into the first ledger LDG is shown, which is Figure 1 A first embodiment of the method for inserting a further data block FDB into a first ledger LDG as shown in Figure 2 The embodiments of the method shown in for verifying a further data block FDB to be inserted into a second ledger are executed sequentially.

[0761] In particular, the embodiment shown comprises the step of transmitting a TRM-FDB further data block FDB from the block creation unit BCU to the block verification unit BVU, in particular from the interface BCU.IF of the block creation unit BCU to the interface BVU.IF of the block verification unit BVU. This step is equivalent to the execution of the steps of providing a PROV-FDB further data block FDB using the interface BCU.IF of the block creation unit BCU and receiving a REC-FDB further data block FDB using the block verification unit BVU.

[0762] Figure 4 An embodiment of a block creation unit BCU and an embodiment of a block verification unit BVU are shown. The block creation unit BCU is connected to the block verification unit BVU via a network NETW, and furthermore, the block creation unit BCU and the block verification unit BVU are connected to a set of computing nodes CN1, CN2 via the network NETW.

[0763] The block creation unit BCU, the block verification unit BVU or the computing nodes CN1, CN2 may be a (personal) computer, a workstation, a virtual machine running on host hardware, a microcontroller or an integrated circuit. As an alternative, the block creation unit BCU, the block verification unit BVU or the computing nodes CN1, CN2 may be a real or virtual computer group (the technical term for a real computer group is a "cluster" and the technical term for a virtual computer group is a "cloud"). Each of the block creation units BCU, the block verification unit BVU or the computing nodes CN1, CN2 comprises interfaces BCU.IF, BVU.IF, CN1.IF, CN2.IF, computing units BCU.CU, BVU.CU, CN1.CU, CN2.CU and memory units BCU.MU, BVU.MU, CN1.MU, CN2.MU.

[0764] The interfaces BCU.IF, BVU.IF, CN1.IF, CN2.IF may be embodied as hardware interfaces or software interfaces (e.g. PCI-bus, USB or FireWire). Typically, the computing units BCU.CU, BVU.CU, CN1.CU, CN2.CU may comprise hardware elements and software elements, e.g. a microprocessor, a field programmable gate array (acronym “FPGA”) or an application specific integrated circuit (acronym “ASIC”). The memory units BCU.MU, BVU.MU, CN1.MU, CN2.MU may be embodied as a non-permanent main memory (e.g. random access memory) or a permanent mass storage device (e.g. hard disk, USB stick, SD card, solid state disk).

[0765] The network NETW can be implemented as a LAN (acronym for "Local Area Network"), for example, via Bluetooth or USB (acronym for "Universal Serial Bus"), in particular, the network NETW can be implemented as a WiFi network or any other local connection. The network NETW can also be implemented as a WAN (acronym for "Wide Area Network"), in particular, the network NETW can be identical to the Internet. Alternatively, the network NETW can also be implemented as a VPN (acronym for "Virtual Private Network").

[0766] In the embodiment shown, the block creation unit BCU is connected to the medical device MA. The connection of the block creation unit BCU to the medical device MA is optional. Alternatively, the block creation unit BCU may also be identical to the medical device MA. Alternatively, the medical device MA may also include the block creation unit BCU. Alternatively, the medical device may be connected to the block verification unit BVU and / or one of the computing nodes CN1, CN2, the medical device may be identical to the block verification unit BVU and / or one of the computing nodes CN1, CN2 or include the block verification unit BVU and / or one of the computing nodes CN1, CN2, and the medical device may communicate with the block creation unit BCU by means of the network NETW.

[0767] In the embodiment shown, there are further computing nodes CN1, CN2 connected to the block verification unit BVU and the block creation unit BCU. The block verification unit BVU, the block creation unit BCU and the further computing nodes CN1, CN2 form a peer-to-peer network. Generally, the block verification unit BVU, the block creation unit BCU and the further computing nodes CN1, CN2 can be regarded as equivalent, in other ways, the block verification unit BVU and / or one of the computing nodes CN1, CN2 can also be a block creation unit BCU for another further data block, and the block creation unit BCU and / or one of the computing nodes CN1, CN2 can be a block verification unit BVU for another further data block.

[0768] In a preferred embodiment, the medical device MA is not permanently connected to the block creation unit BCU. In particular, the connection between the medical device MA and the block creation unit BCU may be an indirect connection in order to isolate the medical device MA from other units for safety reasons. For example, the medical device MA may communicate with the block creation unit via a one-way communication channel, for example by displaying a one-dimensional or two-dimensional barcode such as a QR code which can be read directly or indirectly by the block creation unit. Alternatively, the connection between the block creation unit BCU and the medical device MA may also be established via the network NETW.

[0769] Figure 5 A first embodiment of a local database comprising data blocks is shown, Figure 6 A second embodiment of a local database comprising data blocks is shown, Figure 7 A third embodiment of a local database comprising data blocks is shown.

[0770] In all three embodiments of the local database, an arrow from a first data block to a second data block means that the first data block includes link information based on the second data block. Each of the three embodiments includes an origin data block DB.1 that does not include link information to another data block. An alternative name for the origin data block DB.1 is a root data block.

[0771] In the first and second embodiments, each data block except the origin data block DB.1 includes one link information, in other words, there is exactly one outgoing arrow for each data block except the origin data block DB.1. In the third embodiment, each data block except the origin data block DB.1 includes two link information, in other words, there are exactly two outgoing arrows for each data block except the origin data block DB.1. The two outgoing arrows may point to the same other data block. Figure 7 In the figure, it is shown for data block DB.3, in other words, both link information of data block DB.3 are based on data block DB.1. Another integer number of outgoing arrows or link information can also be used, which can be the same number for all data blocks except the originating data block, or alternatively, the number can be different for different data blocks.

[0772] In all embodiments, there are data blocks without arrows entering, which are called barren data blocks. In other words, in the local database, there are no data blocks with link information based on barren data blocks. In the first embodiment, there is exactly one barren data block DB.7; in the second embodiment, there are three barren data blocks DB.3, DB.6, DB.7; in the third embodiment, there are also three barren data blocks DB.10, DB.11, DB.12.

[0773] Fig. 9 A first embodiment of data blocks DB.j, DB.k included in a first ledger LDG is shown. In particular, one of the data blocks DB.j, DB.k may be identical to the other data block FDB. Data block DB.j is the parent data block of data block DB.k, and data block DB.j is the direct successor of data block DB.i, which is not shown in the figure. Data blocks DB.j, DB.k may also have several parents or several direct successors.

[0774] In this embodiment, the data blocks DB.j, DB.k include the medical data records MDR.j, MDR.k and the hashes H(DB.i), H(DB.j) of the parent data blocks. In particular, the hashes H(DB.i), H(DB.j) of the parent data blocks are the Merkle roots of the parent data blocks.

[0775] Fig.10A first embodiment of data blocks DB.j, DB.k included in a first ledger LDG is shown. In particular, one of the data blocks DB.j, DB.k may be identical to the other data block FDB. Data block DB.j is the parent data block of data block DB.k, and data block DB.j is the direct successor of data block DB.i, which is not shown in the figure. Data blocks DB.j, DB.k may also have several parents or several direct successors.

[0776] In this embodiment, the data blocks DB.j, DB.k include the hashes H(DB.i), H(DB.j) of the medical data records MDR.j, MDR.k and the parent data blocks. Furthermore, in this embodiment, the data blocks DB.j, DB.k include the hashes H(MDR.j), H(MDR.k) of the medical data records MDR.j, MDR.k contained in the corresponding data blocks DB.j, DB.k. The use of the hashes H(MDR.j), H(MDR.k) is optional and ensures the integrity of the medical data records contained in the data blocks DB.j, DB.k. In particular, the hashes H(MDR.j), H(MDR.k) are based on a Merkle root or Merkle tree of the medical data records MDR.j, MDR.k.

[0777] In addition and optionally, in this embodiment, the data blocks DB.j, DB.k include random numbers RN.j, RN.k, wherein the random numbers RN.j, RN.k are selected such that a hash based on the medical data records MDR.j, MDR.k and based on the random numbers RN.j, RN.k meets certain requirements, whereby the hash is less than a given number. Typically, the random numbers RN.j, RN.k must be determined by calculating a hash based on the medical data records MDR.j, MDR.k and based on the random numbers RN.j, RN.k for different values ​​of the random numbers RN.j, RN.k, thus creating a proof of work.

[0778] In particular, the hash H(DB.i), H(DB.j) of the parent data block is not based on the medical data record MDR.i, MDR.j of the parent data block, but is based on the hash H(MDR.i), H(MDR.j) of the medical data record MDR.i, MDR.j of the parent data block, the hash H(DB.i) of the parent data block and / or the random number RN.i, RN.j of the parent data block. This has the advantage of verifying the hash H(DB.i), H(DB.j) of the parent data block in the first ledger LDG (in other words, verifying the integrity of the first ledger LDG), and it may not be necessary to consider large medical data records MDR.i, MDR.j, but only their hashes H(MDR.i), H(MDR.j), which reduces the number of computational steps required to verify the integrity of the first ledger LDG.

[0779] Fig.11 A first embodiment of data blocks DB.j, DB.k included in a first ledger LDG is shown. In particular, one of the data blocks DB.j, DB.k may be identical to the other data block FDB. Data block DB.j is the parent data block of data block DB.k, and data block DB.j is the direct successor of data block DB.i, which is not shown in the figure. Data blocks DB.j, DB.k may also have several parents or several direct successors.

[0780] In this embodiment, the data blocks DB.j, DB.k include the medical data records MDR.j, MDR.k and the hashes H(DB.i), H(DB.j) of the parent data blocks. In particular, the hashes H(DB.i), H(DB.j) of the parent data blocks are the Merkle roots of the parent data blocks. In addition, in this embodiment, as described with respect to Fig.10 As described, the data blocks DB.j, DB.k include random numbers RN.j, RN.k.

[0781] Furthermore, each of the data blocks DB.j, DB.k comprises a weight Wj, Wk. In particular, the weight Wk of the data block DB.k may be based on the weight Wj of at least one of its parent data blocks DB.j. In particular, the step of determining the DET-PDB may be based on the weights Wj, Wk of the data blocks DB.j, DB.k included in the first ledger LDG. In particular, the weights Wj, Wk of the data blocks DB.j, DB.k may be based on the weights Wj, Wk of the data blocks DB.j, DB.k. i , W i+1 The weight may also be proportional to the work used to determine the linking information based on the consensus algorithm used when creating the data block, such as in a proof-of-work consensus algorithm. For example, if the random numbers RN.j, RN.k are selected so that the hash of the random numbers RN.j, RN.k based on the medical data records MDR.j, MDR.k and based on the data blocks DB.j, DB.k is below a certain threshold number, the weights Wj, Wk of the data blocks DB.j, DB.k may be based on the threshold number.

[0782] Fig.12 and Fig.13 An embodiment of a method for inserting a further data block FDB into a first ledger LDG is shown, wherein the method can be used to record access to medical data records MDR.j, MDR.k, in particular to record access to medical data records MDR.j, MDR.k by an entity. The embodiment of the method shown for inserting a further data block FDB into a first ledger LDG comprises Figure 1 All steps of the method for inserting a further data block FDB into the first ledger LDG shown in . Optionally, these embodiments may also include Figure 3 All method steps included in these embodiments may include the additional steps shown in Figure 1 Description or Figure 3 All advantageous enhancements and alternatives described in the description of .

[0783] Fig.14 Shown in Fig.12 and Fig.13 In one of the methods shown in , the data blocks DB.j, DB.k contained in the first ledger LDG are used. In particular, the further data block FDB has the same structure as the data blocks DB.j, DB.k shown, and in particular, the further data block FDB can be the same as one of the data blocks DB.j, DB.k shown.

[0784] Each of the displayed data blocks DB.j, DB.k comprises a medical data set MDS.j, MDS.k, a random number RN.j, RN.k and a hash H(DB.i), H(DB.j) of the respective parent data block DB.i, DB.j.

[0785] Medical data sets MDS.j and MDS.k record the entity's access to medical data records MDR.j and MDR.k. Therefore, in Fig.14 In the implementation shown, the medical data sets MDS.j, MDS.k include: hashes H(MDR.j), H(MDR.k) of the accessed medical data records MDR.j, MDR.k; identifiers PID.j, PID.k of the entities accessing the medical data records MDR.j, MDR.k; and timestamps TS.j, TS.k corresponding to the time of the entity's access to the medical data records MDR.j, MDR.k.

[0786] In this embodiment, the entity accessing the medical data record MDR.j, MDR.k is a person accessing the medical data record MDR.j, MDR.k, and the identifier PID.j, PID.k of the person accessing the medical data record MDR.j, MDR.k is the ID of the person in the central database (e.g., a social security number). Alternatively, the identifier PID.j, PID.k of the person accessing the medical data record MDR.j, MDR.k may include personal data of the person accessing the medical data record MDR.j, MDR.k, such as the name and / or date of birth of the person. Alternatively, the identifier PID.j, PID.k of the general entity or person accessing the medical data record MDR.j, MDR.k may include a public key associated with the person. Alternatively, the identifier PID.j, PID.k of the general entity or person accessing the medical data records MDR.j, MDR.k may be a signature signed using a private key associated with said person or said general entity, in particular, the signature may be created based on the medical data records MDR.j, MDR.k, the hash H(MDR.j), H(MDR.k) of the medical data records MDR.j, MDR.k and / or based on a timestamp TS.j, TS.k corresponding to the time of access of the medical data records MDR.j, MDR.k by said person or said general entity.

[0787] exist Fig.12 and Fig.13 In the embodiment shown, the step of receiving an additional medical data set REC-FDS includes the following steps: using the interface BCU.IF to receive an access request from the entity REC-AR for the medical data record MDR.1; and using the computing unit BCU.CU to determine an additional medical data set FDS based on the access request and based on the medical data record MDR.1.

[0788] In the embodiment shown, the access request includes an identifier PID.1 of the entity accessing the medical data record MDR.1 and information about the medical data record MDR.1 to be accessed. In this embodiment, the information about the medical data record MDR.1 to be accessed is a hash H(MDR.1) of the medical data record MDR.1 to be accessed. Alternatively, the information about the medical data record MDR.1 to be accessed is a link to the medical data record MDR.1 to be accessed, in particular, the information about the medical data record MDR.1 to be accessed is a uniform resource locator (acronym "URL") pointing to the medical data record MDR.1 to be accessed. In particular, the URL of the medical data record MDR.1 to be accessed may include the hash H(MDR.1) of the medical data record MDR.1 to be accessed.

[0789] In these embodiments, the medical data record MDR.1 to be accessed is the diagnostic data related to the patient. The diagnostic data may include one or more medical images of the patient (e.g., derived from X-ray fluoroscopy, angiography, computed tomography, magnetic resonance imaging, positron emission tomography, ultrasound imaging), the diagnostic data may also include laboratory data (e.g., derived from laboratory diagnosis of the patient's blood, the patient's urine, the patient's liquid or the patient's feces), and the diagnostic data may also include a medical diagnosis in a structured or unstructured format. Alternatively, the diagnostic data may also include a combination of several of the alternatives mentioned.

[0790] In the step of determining the DET-FDS further medical data set FDS based on the access request and based on the medical data record MDR.1, the further medical data set FDS is determined such that the further medical data set FDS comprises: a hash H(MDR.1) of the accessed medical data record MDR.1, an identifier PID.1 of the entity accessing the medical data record MDR.1 and a timestamp TS.1 corresponding to the time of the access to the medical data record MDR.1. In particular, the step of determining the further medical data set FDS may comprise: calculating the hash H(MDR.1) of the accessed medical data record MDR.1 by applying a hash function on said medical data record MDR.1.

[0791] Alternatively, the additional medical data set FDS may also include personal data related to the patient (e.g., the patient's name, the patient's gender, the patient's age, the patient's size, the patient's weight, or any combination thereof). The additional medical data set FDS may also be defined in relation to multiple access requests to medical data records from an entity or from different entities; in this case, the additional medical data set FDS includes corresponding data in relation to all access requests.

[0792] In particular, the step of determining the additional medical data set FDS of the DET-FDS is performed so that the additional medical data set FDS conforms to the format of the medical data sets MDS.j, MDS.k already contained in the data blocks DB.i, DB.j, DB.k already existing in the first ledger LDG. In particular, the medical data sets MDS.j, MDS.k also include: the hash H(MDR.j), H(MDR.k) of the medical data records MDR.j, MDR.k that have been accessed; the identifier PID.j, PID.k of the entity that has accessed the corresponding medical data record MDR.j, MDR.k; and the timestamp TS.j, TS.k corresponding to the time of access to the medical data records MDR.j, MDR.k.

[0793] Fig.12The method shown in also comprises the following step: providing PROV-FDB additional data blocks FDB using the interface BCU.IF of the block creation unit BCU. In this embodiment, the step of providing PROV-FDB additional data blocks FDB is performed after the step of inserting the additional data blocks INS-FDB-1 into the first ledger LDG. Alternatively, the step of providing PROV-FDB additional data blocks FDB can also be performed before the step of inserting the additional data blocks FDB into the first ledger LDG. Alternatively, the step of providing PROV-FDB additional data blocks FDB can also be performed in parallel with the step of inserting the additional data blocks FDB into the first ledger LDG. In other words, the step of providing PROV-FDB additional data blocks FDB is independent of the step of inserting the additional data blocks FDB into the first ledger LDG.

[0794] exist Fig.13 An implementation of the method shown in the for inserting a further data block FDB into the first ledger LDG also includes the following steps: performing a check by CHK on the entity's authorization to access the medical data record MDR.j; in the case of a positive check, granting the entity access to GRNT-ACC; and in the case of a negative check, denying the entity access to DNY-ACC.

[0795] exist Fig.13 In the embodiment shown, the step of performing a check CHK is performed after the step of receiving the REC-FDS further medical data set FDS. Alternatively, the step of performing a check CHK can also be performed after the step of determining the DET-FDB further data block FDB, after the step of inserting the further data block FDB into the first ledger INS-FDB-1, or after the step of providing the further data block FDB.

[0796] exist Fig.13 In the embodiment shown, the step of granting the entity access to GRNT-ACC is performed after the step of checking CHK and before the step of determining the additional data block of DET-FDB. Alternatively, the step of granting the entity access to GRNT-ACC may be performed after the step of determining the additional data block FDB of DET-FDB, after the step of inserting the additional data block FDB into INS-FDB-1 in the first ledger, or after the step of providing the additional data block FDB.

[0797] The step of performing a check CHK may include determining whether the entity is allowed to access the medical data record MDR.1. In particular, the step of performing a check CHK may include determining whether the entity is part of an entity group, wherein the entity group is allowed to access the medical data record MDR.1. The entity or entity group allowed to access the medical data record MDR.1 may be stored in a database, so that the step of performing a check CHK includes accessing a database of entities allowed to access the medical data record. The step of performing a check CHK may also include verifying the identity of the entity requesting access to the medical data record MDR.1, for example by relying on a shared secret and / or a digital certificate of the entity requesting access to the medical data record, wherein the shared secret and / or the digital certificate of the entity is included in the access request.

[0798] exist Fig.13 In the embodiment shown, if the result of the check is negative, a step of denying the entity access to DNY-ACC is performed. In particular, in the case of a negative check, the further medical data set FDS may also include a denial record. The denial record includes information about the reason why access was denied, for example, an error code indicating the reason why the entity is not allowed to access the medical data record MDR.j. In the case of a negative check, in this embodiment, the step of determining the further data block FDB of the DET-FDB and the step of inserting the further data block FDB into the INS-FDB-1 into the first ledger LDG are not performed.

[0799] In particular, the step of performing a check CHK can also be performed after the step of inserting the further data block FDB into the ledger LDG, wherein the step of performing a check CHK comprises determining whether the further data block FDB has actually been entered into the first ledger LDG. This has the advantage that it can ensure that each access request is actually registered in the first ledger LDG.

[0800] Fig.15 An embodiment of a method for inserting a further data block FDB into a first ledger LDG is shown, wherein the method can be used to record remote access to a medical device MA, in particular to record remote access to a medical device MA by an entity. The embodiment of the method shown for inserting a further data block FDB into a first ledger LDG comprises Figure 1 All steps of the method for inserting a further data block FDB into the first ledger LDG shown in . Optionally, these embodiments may also include Figure 3 All method steps included in these embodiments may include the additional steps shown in Figure 1 In the description or Figure 3 All advantageous enhancements and alternatives described in the description of .

[0801] Fig.16 Shown in Fig.16 In particular, the further data block FDB has the same structure as the data blocks DB.j and DB.k shown, and in particular, the further data block FDB can be the same as one of the data blocks DB.j and DB.k shown.

[0802] Each of the displayed data blocks DB.j, DB.k comprises a medical data set MDS.j, MDS.k, a random number RN.j, RN.k and a hash H(DB.i), H(DB.j) of the respective parent data block DB.i, DB.j.

[0803] The medical data sets MDS.j and MDS.k record the entity's access to the medical device MA. Fig.16 In the implementation shown, the medical data sets MDS.j, MDS.k include: identifiers AID.j, AID.k of the accessed medical device; identifiers PID.j, PID.k of the entities accessing the medical device MA; access times TSA.j, TSA.k corresponding to the time of the entity's access to the medical device MA; departure times TSE.j, TSE.k corresponding to the time when the entity leaves the medical device MA; and action logs ACTL.j, ACTL.k of the actions performed by the entity when accessing the medical device MA.

[0804] In this embodiment, the entity accessing the medical device MA is a person accessing the medical device MA, and the identifier PID.j, PID.k of the person accessing the device is the ID of the person in the central database (e.g., a social security number). Alternatively, the identifier PID.j, PID.k of the person accessing the medical device MA may include personal data of the person accessing the medical device MA, for example, the name and / or date of birth of the person. Alternatively, the identifier PID.j, PID.k of the person or general entity accessing the medical device MA may include a public key associated with the person. Alternatively, the identifier PID.j, PID.k of the person or general entity accessing the medical device MA may be a signature signed using a private key associated with the person or the general entity, in particular, the signature may be created based on the identifier AID.j, AID.k of the medical device MA, the access time TSA.j, TSA.k, the departure time TSE.j, TSE.k and / or the action log ACTL.j, ACTL.k.

[0805] exist Fig.15In the embodiment shown in , the step of receiving the additional medical data set of REC-FDS includes the following steps: receiving the identifier AID.1 of the medical device MA accessed by REC-AID using the interface BCU.IF; and receiving the identifier PID.1 of the entity accessing the medical device MA by REC-PID. In this embodiment, the entity accessing the medical device MA can issue an access request to the medical device MA (for example, by initiating an SSH, VNC or remote desktop connection), wherein the access request includes the identifier AID.1 of the medical device MA and the identifier PID.1 of the entity accessing the medical device MA.

[0806] Fig.15 The embodiment shown in may also include the (optional and not shown) following step: checking the authorization for the entity to access the medical device MA based on the identifier AID.1 of the medical device MA and the identifier PID.1 of the entity accessing the medical device MA.

[0807] also, Fig.15 The embodiment shown in comprises the following steps: opening a remote service connection between an entity accessing the medical device MA through OPN-RSC and the medical device MA. In the described case, the block verification unit BVU is identical to the accessed medical device MA. Alternatively, the block verification unit BVU may be different from the accessed medical device MA, in which case the step of opening the OPN-RSC remote service connection may comprise: sending a message to the medical device MA for opening the remote service connection. Furthermore, in this embodiment, the step of opening the OPN-RSC remote service connection comprises a record of the access time TSA.1.

[0808] Fig.15 The embodiment shown in also includes the step of recording a REC-ACTL action log ACTL.1, wherein the action log ACTL.1 includes a subset or all actions performed by the entity on the medical device MA by using the remote service connection. The action log ACTL.1 may include a list of commands sent from the entity to the medical device MA through the remote service connection, for example, the entity's keystrokes and mouse movements may be recorded. Alternatively, actions at the medical device MA may also be recorded, for example, which buttons the entity pressed and which inputs were completed using the remote service connection.

[0809] Fig.15 The embodiment shown also comprises a step of closing the CLS-RSC teleservice connection. In particular, the step of closing the CLS-RSC teleservice connection comprises recording the time of departure TSE.1. Fig.15The embodiment shown in comprises the following steps: determining the DET-FDS additional medical data set FDS based on the identifier PID.1 of the entity accessing the medical device MA, based on the identifier AID.1 of the medical device MA, based on the access time TSA.1, based on the departure time TSE.1 and based on the action log ACTL.1. It may include: storing the recorded actions at the web server; and determining the action log ACTL.1, which includes a link to the recorded actions in the web server and a hash of the recorded actions in the web server.

[0810] In particular, the step of determining the additional medical data set FDS of DET-FDS is performed so that the additional medical data set FDS conforms to the format of the medical data sets MDS.j, MDS.k already contained in the data blocks DB.i, DB.j, DB.k already existing in the first ledger LDG.

[0811] Fig.17 An embodiment of a method for inserting a further data block FDB into a first ledger LDG is shown, wherein the method can be used to record access to a medical device MA while performing a local service, in particular to record the installation of a component by an entity on the medical device MA, the removal of a component by an entity from the medical device MA, and / or the exchange of a first component with a second component by an entity at the medical device MA. The component, the first component and the second component can be hardware components and / or software components. The embodiment of the method for inserting a further data block FDB into the first ledger LDG shown comprises Figure 1 All steps of the method for inserting a further data block FDB into the first ledger LDG shown in . Optionally, these embodiments may also include Figure 3 All method steps included in these embodiments may be included in Figure 1 In the description or Figure 3 All advantageous enhancements and alternatives described in the description of .

[0812] Fig.18 Shown in Fig.16 In particular, the further data block FDB has the same structure as the data blocks DB.j and DB.k shown, and in particular, the further data block FDB can be the same as one of the data blocks DB.j and DB.k shown.

[0813] Each of the displayed data blocks DB.j, DB.k comprises a medical data set MDS.j, MDS.k, a random number RN.j, RN.k and a hash H(DB.i), H(DB.j) of the respective parent data block DB.i, DB.j.

[0814] Medical data sets MDS.j and MDS.k record the entity's access to, installation, removal and / or replacement of parts of medical equipment MA. Fig.18 In the embodiment shown, the medical data sets MDS.j, MDS.k include: identifiers AID.j, AID.k of the accessed medical device; identifiers PID.j, PID.k of the entity accessing the medical device MA; times TS.j, TS.k corresponding to the time of the entity's access to the medical device MA; identifiers ICID.j, ICID.k of components installed to the medical device; and identifier RCID.j of components removed from the medical device MA.

[0815] In this embodiment, the entity accessing the medical device MA is a person accessing the medical device MA, and the identifier PID.j, PID.k of the person accessing the device is the ID of the person in the central database (e.g., a social security number). Alternatively, the identifier PID.j, PID.k of the person accessing the medical device MA may include personal data of the person accessing the medical device MA, for example, the name and / or date of birth of the person. Alternatively, the identifier PID.j, PID.k of the person or general entity accessing the medical device MA may include a public key associated with the person. Alternatively, the identifier PID.j, PID.k of the person or general entity accessing the medical device MA may be a signature signed using a private key associated with the person or the general entity, and in particular, the signature may be created based on the identifier AID.j, AID.k of the medical device MA, the time TS.j, TS.k corresponding to the time of the entity's access to the medical device MA, the identifier ICID.j, ICID.k of the component installed to the medical device, and / or the identifier RCID.j of the component removed from the medical device MA.

[0816] In this embodiment, the components installed to or removed from the medical device MA may be hardware components and / or software components. Alternatively, the installation and removal of only hardware components or only software components may also be recorded. The identifiers ICID.j, ICID.k of the hardware components installed to the medical device MA and / or the identifiers RCID.j, RCID.k of the hardware components removed from the medical device MA include the model of the component and / or the serial number of the hardware component. The identifiers ICID.j, ICID.k of the software components installed to the medical device MA and / or the identifiers RCID.j, RCID.k of the software components removed from the medical device MA include the version numbers of the software components.

[0817] In particular, if the action performed by the entity is the installation of a component, the identifiers ICID.j, ICID.k of the component installed to the medical device MA are non-empty, while the identifiers RCID.j, RCID.k of the component removed from the medical device MA are empty. In particular, if the action performed by the entity is the removal of a component, the identifiers ICID.j, ICID.k of the component installed to the medical device MA are empty, while the identifiers RCID.j, RCID.k of the component removed from the medical device MA are non-empty. In particular, if the action performed by the entity is the replacement of a component, both the identifiers ICID.j, ICID.k of the component installed to the medical device MA and the identifiers RCID.j, RCID.k of the component removed from the medical device MA are non-empty.

[0818] exist Fig.18 In the embodiment shown in , the step of receiving the additional medical data set of REC-FDS comprises the following steps: receiving the identifier AID.1 of the medical device MA accessed by REC-AID using the interface BCU.IF; and receiving the identifier PID.1 of the entity accessing the medical device MA by REC-PID. In this embodiment, the entity accessing the medical device MA and installing, removing or exchanging components logs into the medical device MA using some login credentials, and the identifier PID.1 of the entity accessing the medical device MA can be determined based on the login credentials.

[0819] Fig.17The embodiment shown in also includes the following steps: determining a change of the medical device MA DET-CHG, wherein the change may be the installation of a component of the medical device MA, the removal of a component and / or the exchange of a component. For example, the computing unit BCU.CU may periodically create a list of components of the medical device MA and compare the current list with a previous version of the list to detect changes. Alternatively, the installation and / or removal of a component may initiate a software routine that determines a change of the medical device MA. In particular, if the component is a hardware component, the hardware component may include a memory (e.g., an EPROM) that can be read by the medical device MA, the memory storing the model and serial number of the corresponding hardware component. In particular, if the component is a software component, the software component may include a configuration file that includes a version number of the software. Alternatively, a software component executed by the medical device MA may output its version number if called with specific command line parameters or execution parameters.

[0820] also, Fig.17 The embodiment shown in comprises the step of determining a DET-TS timestamp TS.1, wherein the timestamp corresponds to the time of installation, removal or exchange of a component.

[0821] Fig.17 The embodiment shown in FIG. 1 further comprises the step of determining a further data block FDB of DET-FDB, the further data block FDB being Fig.17 In particular, the step of determining the additional medical data set FDS of DET-FDS is performed so that the additional medical data set FDS conforms to the format of the medical data sets MDS.j, MDS.k already contained in the data blocks DB.i, DB.j...

Claims

1. A method for inserting a further data block (FDB) into a first ledger (LDG), wherein: The first ledger (LDG) includes data blocks (DB.i, DB.j, DB.k), and the method includes the following steps: - receiving (REC-FDS) a further medical data set (FDS) by means of an interface (BCU.IF), wherein the further medical data set (FDS) is a log of accesses of an entity to a medical device (MA), wherein the further medical data set (FDS) comprises an identifier (AID.j, AID.k, AID.l) of the medical device (MA) and an identifier (PID.j, PID.k, PID.l) of an entity accessing the medical device (MA), - determining (DET-FDB) the further data block (FDB) by means of a computing unit (BCU.CU), wherein the further data block (FDB) comprises the further medical data set (FDS) and further linking information, wherein the further linking information comprises a hash (H(DB.i), H(DB.j), H(DB.k)) of at least one of the data blocks (DB.i, DB.j, DB.k) of the first ledger (LDG), - inserting (INS-FDB-1) said further data block (FDB) into said first ledger (LDG) by means of said computing unit (BCU.CU), - using the computing unit (BCU.CU) to grant access (GRNT-ACC) to an entity having access to the medical device (MA), - selecting a parent data block from the data blocks of the first ledger using the computing unit, wherein the step of granting access (GRNT-ACC) is performed after the step of inserting (INS-FDB-1) said further data block (FDB) into said first ledger (LDG), wherein the additional link information comprises a hash of the parent data block, wherein the first ledger does not include a successor data block of the parent data block, and wherein the first ledger includes a starting data block, and wherein the parent data block is selected based on a distance of the parent data block from the starting data block.

2. The method according to claim 1, wherein: The identifier (AID.j, AID.k, AID.1) of the medical device (MA) is based on a model of the medical device (MA) and / or on a serial number of the medical device (MA).

3. The method according to claim 1 or 2, wherein: The identifier of the entity (PID.j, PID.k, PID.l) comprises a signature signed with a private key assigned to the entity.

4. The method according to claim 3, wherein: The signature is based on the identifier (AID.j, AID.k, AID.l) of the medical device (MA).

5. The method according to claim 4, wherein: The access of the entity to the medical device (MA) comprises a modification of the medical device (MA), and wherein the further medical data set (FDS) comprises a record of the modification, and wherein the step of receiving (REC-FDS) the further medical data set (FDS) comprises: - receiving a record of said changes using said interface (BCU.IF), - using the computer unit (BCU.CU) to determine the further medical data set (FDS) based on the modified protocol.

6. The method according to claim 1 or 2, further comprising: - sending (SND-MSG) a notification message to the owner of the medical device (MA) using the interface (BCU.IF), Therein, the notification message is based on the identifier (AID.j, AID.k, AID.l) of the medical device (MA) and the identifier (PID.j, PID.k, PID.l) of the entity accessing the medical device (MA).

7. The method according to claim 1 or 2, wherein: The medical data set includes the time of the entity's access to the medical device (MA), wherein the time of the access corresponds to the time when the remote access to the medical device (MA) was established by the entity, and / or wherein the medical data set includes the time when the entity left the medical device, wherein the time of the departure corresponds to the time when the remote access to the medical device (MA) was terminated.

8. The method according to claim 1 or 2, wherein: Each of the data blocks (DB.i, DB.j, DB.k) of the first ledger includes a medical data set (MDS.j, MDS.k) and link information, and the link information includes a hash (H(DB.i), H(DB.j), H(DB.k)) of at least one of the data blocks (DB.i, DB.j, DB.k) of the first ledger (LDG).

9. The method according to claim 1 or 2, wherein: Determining (DET-FDB) that the further data block (FDB) comprises an execution of a consensus algorithm.

10. The method according to claim 1 or 2, wherein: The first ledger (LDG) is a blockchain, a block tree and / or a tangle.

11. The method according to claim 1 or 2, further comprising: - receiving (REC-LDG-2) the second ledger using a Block Verification Unit (BVU), - transmitting (TRM-FDB) the further data block (FDB) to the block verification unit (BVU) using the interface (BCU.IF), - verifying (VREF) said further linking information based on said second ledger using said block verification unit (BVU), - In case of positive verification, inserting (INS-FDB-2) the further data block (FDB) into the second ledger using the block verification unit (BVU).

12. A block creation unit (BCU) for inserting a further data block (FDB) into a first ledger (LDG), wherein: The first ledger (LDG) includes data blocks (DB.i, DB.j, DB.k), and the block creation unit (BCU) includes the following units: - an interface (BCU.IF) configured for receiving (REC-FDS) a further medical data set (FDS), wherein the further medical data set (FDS) is a log of accesses of an entity to a medical device (MA), wherein the further medical data set (FDS) comprises an identifier (AID.j, AID.k, AID.l) of the medical device (MA) and an identifier (PID.j, PID.k, PID.l) of an entity accessing the medical device (MA), a computing unit configured to determine (DET-FDB) the further data block (FDB), wherein the further data block (FDB) comprises the further medical data set (FDS) and further linking information, and wherein the further linking information comprises a hash (H(DB.i), H(DB.j), H(DB.k)) of at least one of the data blocks (DB.i, DB.j, DB.k) of the first ledger (LDG), The computing unit is further configured to insert (INS-FDB-1) said further data block (FDB) into said first ledger (LDG), The computing unit is further configured to grant access (GRNT-ACC) to an entity accessing the medical device (MA), The computing unit is further configured to select a parent data block from the data blocks of the first ledger, wherein granting access (GRNT-ACC) is performed after inserting (INS-FDB-1) said further data block (FDB) into said first ledger (LDG), wherein the additional link information comprises a hash of the parent data block, wherein the first ledger does not include a successor data block of the parent data block, and wherein the first ledger includes a starting data block, and wherein the parent data block is selected based on a distance of the parent data block from the starting data block.

13. A computer-readable medium comprising a program unit which, when loaded into a memory unit (BCU.MU) of a block creation unit (BCU), causes the block creation unit (BCU) to perform the steps of the method for inserting a further data block (FDB) into a first ledger (LDG) according to one of claims 1 to 11.