Blockchain-based distribution of medical data records
By including authorization tokens in the unified resource locator of medical data records and recording licensing information in the distributed ledger, the security and privacy issues of distributed medical data records are solved, and the security of medical data records is achieved. and reliable access.
Patent Information
- Application Number
- CN201980051804.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-08-03
- Filing Date
- 2019-06-07
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2039-06-07
AI Technical Summary
The prior art is difficult to effectively manage and access distributed stored medical data records, especially the problem of allowing authorized entities to access this data while ensuring data privacy and security.
By providing a Uniform Resource Locator (URI), the URI contains authorization tokens for identifying and accessing medical data records and documenting licensing and ownership information in a distributed ledger to ensure that only authorized entities can access and use These data.
Secure, reliable and private access to medical data records is achieved, ensuring that only authorized entities can access and use data, improving data protection and privacy.
Smart Images

Figure CN112534433B_ABST
Abstract
Description
[0001] Medical data records, such as medical images, medical diagnoses or laboratory reports, are usually stored in the system of the medical institution (eg, hospital) that created the corresponding medical data record, which makes it difficult to access the medical data records of patients stored in different medical institutions in a distributed manner.
[0002] A common solution for better access to such medical data records is to store them, for example, in a cloud storage or a web server, so that they can be accessed from outside the medical institution where the corresponding medical data records have been generated. In this case, it must be ensured that the medical data records can only be accessed by authorized entities, in particular, only by entities authorized by the patient to whom the medical data records relate.
[0003] The problem underlying the present invention is therefore to provide a system for regulating access to medical data records, advantageously allowing compensation to the patient to whom the medical data record relates.
[0004] This problem is solved by providing a uniform resource locator, a method of providing a system, a computer program product and a computer readable medium according to the independent claims. Advantageous features and embodiments are contained in the dependent claims and the description.
[0005] Hereinafter, the solution according to the present invention is described with respect to systems, units and devices and with respect to methods. Features, advantages or alternative embodiments herein may be assigned to other corresponding objects, and vice versa. In other words, the features described or claimed in the context of the corresponding methods may be utilized to improve systems, units and devices. In this case, the functional features of the method are embodied by the target units of the systems, units and devices.
[0006] In addition, the present invention is described in the context of different methods, systems, units and devices corresponding to different possible aspects of the present invention. It is to be understood that the advantageous embodiments and features of any object described in the context of one method, system, unit or device may also be the advantageous embodiments and features of the same object of other methods, systems, units and devices.
[0007] In particular, the present invention is described in the context of methods and systems for providing uniform resource locators, for providing location information, and for storing consent. It is to be understood that advantageous embodiments and features of these methods and systems may also be advantageous embodiments and features of other methods and systems.
[0008] In particular, the present invention is further described in the context of methods and systems for using uniform resource locators, for providing location information, and for using permission information. It is to be understood that advantageous embodiments and features of these methods and systems may also be advantageous embodiments and features of other methods and systems.
[0009] In addition, it is to be understood that the method and system for using an object provided or created by another method or system can always be extended using the steps and / or components of the other method or system. In other words, the method or system for providing and / or creating an object and the method or system for using the object can always be combined into a joint method or system for creating and using the object.
[0010] In one aspect, the present invention relates to a method for providing a uniform resource locator, comprising the following steps: receiving a medical data record using an interface, wherein the medical data record is associated with a patient; determining a uniform resource locator associated with the medical data record using a computing unit, wherein the uniform resource locator includes an authorization token based on the medical data record, and wherein the medical data record can be accessed by following the uniform resource locator; and providing the uniform resource locator to the patient using the interface.
[0011] Specifically, the interface may be an interface of a providing system. Specifically, the computing unit may be a computing unit of the providing system. Specifically, the providing system may further include a storage unit. Specifically, the providing system may include a patient client and / or a server, wherein the interface may be an interface of the patient client and / or an interface of the server, wherein the computing unit may be a computing unit of the patient client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the patient client and / or a storage unit of the server.
[0012] Typically, a medical data record includes medical data associated with a patient. 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 (acronym "MR") device, a single photon emission tomography (acronym "SPECT") device, a positron emission tomography (acronym "PET") device, a computed tomography (acronym "CT") device, an ultrasound device, an X-ray device, a C-arm device, or a combined medical imaging device formed by any combination of the above 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, and the like.
[0013] 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 (acronym for electrocardiogram) devices, EEG (acronym for electroencephalogram) devices, blood pressure measurement devices, infusion devices, or dialysis devices. Medical data records may also include laboratory diagnoses or genetic information.
[0014] 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 medical 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 associated with a patient, such as gender, age, weight, size, etc.
[0015] Other medical data that can be considered by those skilled in the art can also be part of the medical data record. Specifically, a link to the medical data record or a hash value of the medical data record can also be considered as a medical data record.
[0016] In general, a uniform resource locator (acronym "URL") is a reference to a resource that specifies the location of the resource on a computer network and a mechanism for retrieving the resource. Specifically, a uniform resource locator is a reference to a medical data record. The terms "uniform resource locator" and "web address" may be used as synonyms.
[0017] The use of a uniform resource locator is not essential to the present invention, and in particular, any type of string for identifying and / or locating an abstract resource or a physical resource may be used, such as a uniform resource identifier (acronym "URI") or an international resource identifier (acronym "IRI"). In particular, throughout the specification and claims, the term "uniform resource identifier" or "international resource identifier" may replace the term "uniform resource locator".
[0018] In particular, the uniform resource locator can be used to access the medical data record. In particular, the uniform resource locator can be contained in a hyperlink of an electronic document, in particular in a hyperlink of an email or in a hyperlink of a website, wherein both emails and websites can be defined in the form of text documents using the HTML (acronym for “Hypertext Markup Language”) standard, for example. If the uniform resource locator is contained in a hyperlink, the medical data record can be accessed by following the hyperlink.
[0019] The term "uniform resource locator" in this application can also be understood as a request based on a uniform resource locator. Specifically, the term "uniform resource locator" can be replaced by "a request based on a uniform resource locator / the uniform resource locator". Such a request based on a uniform resource locator may include additional data, wherein in particular, the additional data is sent to a server characterized and / or identified by the uniform resource locator. Specifically, the request is a request based on a communication protocol of the application layer, such as the Internet protocol suite or the OSI model. Specifically, a request based on a uniform resource locator is an HTTP request (the acronym for "hypertext transfer protocol"), an HTTPS request (the acronym for "secure hypertext transfer protocol") or an FTP request including a uniform resource locator.
[0020] Typically, the authorization token is a component of a uniform resource locator, wherein the presence of the authorization token in the URL and / or the submission of the authorization token with the URL is a necessary condition for accessing the medical data record. Specifically, the authorization token can be a string contained in the URL, particularly a string within the path portion or query portion of the URL.
[0021] If the uniform resource locator is understood as a request based on the uniform resource locator, the authorization token can be part of other data sent to the server characterized and / or identified by the uniform resource locator. Specifically, if the uniform resource locator is understood as an HTTP POST request, the authorization token can be included in the data submitted by the HTTP POST request.
[0022] Typically, the authorization token can be specific to the medical data record, which means that everyone who has access to the uniform resource locator can access the medical data record. For example, the authorization token can include the location of the medical data record within the server. Specifically, if the server does not provide a list of medical data records stored in the server, access to the medical data record requires knowledge of the authorization token. Alternatively, the authorization token can also be specific to the authorized entity that has access to the medical data record. Specifically, different authorization tokens can be used for different authorized entities that have access to the medical data record. This can be used to track access to the medical data record. Alternatively, combining the advantages of both methods, the authorization token can also be specific to the medical data record and specific to the authorized entity that has access to the medical data record.
[0023] Instead of the term “authorized entity”, the term “access entity” may be used, the term “access entity” indicating that the authorized entity is allowed or has the right to access the corresponding medical data record.
[0024] The inventors recognized that by providing a uniform resource locator that includes an authorization token, such as by a patient forwarding the uniform resource locator to another entity (e.g., a physician), access to medical data records can be quickly and efficiently authorized while at the same time, unauthorized entities are unable to access the medical data records due to their lack of a suitable authorization token.
[0025] According to another aspect of the present invention, a method for providing a uniform resource locator comprises the following steps: using a storage unit to store medical data records, wherein the uniform resource locator includes the location of the medical data records in the storage unit. Specifically, the storage unit can be a web server or a web storage (particularly a cloud storage). Specifically, the medical data records are stored in a repository within the storage unit. Specifically, the repository is part of the storage unit of the providing system, or is stored in the storage unit of the providing system, and specifically, the repository is part of the storage unit of the server of the providing system, or is stored in the storage unit of the providing system.
[0026] In particular, the location of the medical data record is contained in the path part of the URL, and in particular the storage unit and / or server and / or repository is contained in the host part of the URL. Alternatively, the uniform resource locator may include the location of the medical data record as a query parameter.
[0027] If the term Uniform Resource Locator is understood to refer to a Uniform Resource Locator-based request, particularly an HTTP POST request, it should be understood that the Uniform Resource Locator also includes the location of the medical data record if the location of the medical data record is contained in additional data sent to the server represented and / or identified by the Uniform Resource Locator.
[0028] The location of the medical data record may correspond to the location of the medical data record in the file system of the storage unit, or to the location of the medical data record in the file system of the server, or to the location of the medical data record in the file system of the server's repository. Alternatively, the location of the medical data record may be a number or a string, which may be mapped to the location of the medical data record in the file system of the storage unit, or to the location of the medical data record in the file system of the server, or to the location of the medical data record in the file system of the server's repository by means of a table (e.g., a hash table). Specifically, the mapping is performed by the server.
[0029] In particular, the location of the medical data record may include the authentication token, or the authentication token may include the location of the medical data record. In particular, the location of the medical data record may be the same as the authentication token.
[0030] The inventors have recognized that the availability of medical data records can be increased by storing the medical data records in a storage unit, in particular in a server or in a repository.
[0031] According to another aspect of the present invention, a method for providing a uniform resource locator comprises the following steps: using an interface to receive an identifier of an authorized entity, wherein the authorized entity is allowed to access a medical data record, and wherein the uniform resource locator is based on the identifier of the authorized entity. Specifically, the uniform resource locator is based on the identifier of the authorized entity through an authorization token based on the identifier of the authorized entity.
[0032] In general, an entity may be a person, a group of persons, a legal entity (such as a company), a group of legal entities or an object (particularly an information technology object such as 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 doctor, a nurse or a technician of a hospital or any group thereof. In particular, an entity may be a hospital, a medical institution or any group thereof. In addition, an entity may also be a medical research facility or a medical researcher. An authorized entity is an entity that is authorized to access medical data records.
[0033] The identifier of the authorized entity can generally be used to clearly identify the authorized entity. Specifically, 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 date of birth 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. Specifically, if the entity is a company (e.g., a hospital), the identifier of the entity may include the company name. Specifically, 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. Specifically, the identifier of the entity accessing the medical data record may be based on a public key or a private key associated with the entity accessing the medical data record. Specifically, the identifier of the authorized entity may also be a shared secret or a token, which is known to both the authorized entity and the system authorized to access the medical data record.
[0034] In particular, the uniform resource locator and / or the authentication token may be based on an identifier of an authorized entity of the uniform resource locator and / or the authentication token may include the identifier of the authorized entity as a substring.
[0035] The inventors have realized that by including the identifier of the authorized entity in the uniform resource locator, it is possible to track which entity has accessed the medical data record based on the uniform resource locator. In addition, for example, by granting a first authorized entity access rights for a longer time span than a second authorized entity, access by multiple authorized entities can be distinguished.
[0036] According to another aspect of the present invention, the identifier of the authorized entity is based on a digital certificate. Specifically, the identifier of the authorized entity is a digital certificate or a part of a digital certificate. Specifically, the digital certificate is signed by a certification authority.
[0037] Other terms for "digital certificate" are "public key certificate" or "identity certificate". A digital certificate can be an electronic document related to the ownership of a public key, in particular to the ownership of an authorized entity. Therefore, an access certificate usually contains information about the public key and the authorized entity associated with the public key. In addition, an access certificate usually contains a digital signature, which verifies the contents of the certificate. Specifically, the digital signature is based on a private key associated with a parent digital certificate. A digital certificate is said to be signed by a certification authority if the certification authority uses the certification authority's private key (usually the private key of the parent digital certificate) to issue a digital signature. The validity of the certificate can be proved using the public key corresponding to the certification authority's private key (or equivalently, based on another digital certificate that proves the certification authority).
[0038] The inventors have recognised that, because a digital certificate is proof of the identity of an authorised entity, the security of access to medical data records may be increased by using a digital certificate as an identifier for the authorised entity.
[0039] According to another aspect of the present invention, a method for providing a uniform resource locator comprises: a step of determining permission information using a computing unit, wherein the permission information is related to the patient's permission for the use of a medical data record by an authorized entity, wherein the permission information is based on the medical data record and / or on an identifier of the authorized entity; and a step of recording the permission information in a distributed permission ledger using a computing unit.
[0040] A distributed permissioned ledger is a distributed ledger. In general, a distributed ledger is some type of decentralized database. In particular, the distribution of a distributed ledger means that there are multiple copies of (at least part of) the distributed ledger in different storage units, wherein the storage units are spatially distributed. A distributed ledger comprises a plurality of records, wherein the plurality of records can be identified by a database entry. In particular, the plurality of records are organized as data blocks. In particular, the records are created by different entities, in particular different nodes of a network, and in particular, if the records are in different nodes, they are stored with different entities. 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 distributed ledger.
[0041] Typically, updating a distributed ledger is typically based on a consensus mechanism, where the consensus mechanism can also ensure that different copies of the distributed ledger match in the event of communication delays between the entities storing copies of the distributed ledger.
[0042] Specifically, recording the permission information in the distributed permission ledger is performed by storing the permission information, a link to the permission information, and / or a hash of the permission information in the distributed permission ledger.
[0043] Specifically, storing the data in the distributed ledger may include: appending an additional data block to the distributed ledger, wherein the additional data block includes the data to be stored. Appending the additional data block to the distributed ledger may include executing a consensus mechanism, wherein executing the consensus mechanism may include proof of work, proof of storage, proof of stake, and / or proof of elapsed time. The proof of work may be a computationally limited proof of work, a network limited proof of work, and / or a memory limited proof of work.
[0044] In particular, the permission information may be based on a medical data record and an identifier of an authorized entity, in which case the permission information may use the medical data record to encode the patient's permission to the authorized entity. In particular, the permission information may be based on a medical data record rather than an identifier of an authorized entity, in which case the permission information may use the medical data record to encode the patient's permission to any entity. In particular, the permission information may be based on an identifier of an authorized entity rather than an identifier of a medical data record, in which case the permission information may use all medical data records related to the patient to encode the patient's permission to the authorized entity. In particular, the permission information may include a smart contract.
[0045] The inventors have recognized that by recording permission information in a distributed permissioned ledger, a patient's permission for use of medical data records by authorized entities can be stored in a revision-secure and manipulation-secure manner.
[0046] According to another aspect of the invention, a method for providing a uniform resource locator includes receiving a first identifier of a patient using an interface, wherein the permission information is also based on the first identifier of the patient.
[0047] Specifically, the first identifier of the patient is an identifier of the patient. Specifically, there may be a second identifier of the patient as an identifier of the patient, wherein the second identifier of the patient may be the same as the first identifier of the patient, or wherein the second identifier of the patient may be different from the first identifier of the patient.
[0048] Specifically, the patient's identifier is based on a key pair of the patient, the key pair comprising a public key and a private key. The patient's identifier may comprise a public key and / or a private key. Specifically, if the identifier comprises a public key, and / or if the identifier comprises a private key associated with a public key, the identifier is represented as being associated with the public key. Specifically, if the identifier comprises a private key, and / or if the identifier comprises a public key associated with a private key, the identifier is represented as being associated with a private key. The patient's identifier may be used to sign a data set, specifically, a private key contained in the patient's identifier or a private key associated with the patient's identifier may be used to sign a data set.
[0049] Typically, a patient's identifier can be transferred from the patient to another entity if the patient's identifier includes a public key rather than an associated private key. The patient's identifier can also be transferred to another entity if the patient's identifier includes a private key, in which case the patient's identifier should no longer be used thereafter.
[0050] The inventors have realised that by basing the consent information on the patient's first identifier, manipulation of the consent information can be made more difficult and, in particular, it can be ensured that the consent information is actually issued by the patient himself.
[0051] According to another aspect of the present invention, the permission information includes a permission signature based on the medical data record and / or a permission signature based on the identifier of the authorized entity, wherein the permission signature is signed based on the first identifier of the patient. Specifically, the first identifier of the patient includes a first private key associated with the patient, and the permission signature is signed based on the first identifier of the patient signed by using the first private key included in the first identifier of the patient.
[0052] Specifically, the license signature is a digital signature. Typically, a digital signature relies on an asymmetric key pair comprising a private key and a public key 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 vice versa.
[0053] Specifically, a digital signature is the output of a signature algorithm, wherein the signature algorithm takes as a first input the data to be signed (also denoted as a "message") and as a second input signature information. Specifically, the signature information is a private key. Specifically, if the private key is used as the second input to the signature algorithm when creating the signature, then the private key is used to sign the signature. Specifically, if the certain data is used as the first input to the signature algorithm when creating the signature, then the signature is based on certain data.
[0054] Specifically, 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 having a private key corresponding to a given public key.
[0055] Specifically, the signature verification algorithm can verify the validity of the signature without knowing the private key corresponding to the public key. Specifically, the private key used to sign the signature cannot be derived from the signature.
[0056] The inventors have realized that by using a signature signed based on the patient's first identifier, it is possible to undeniably record that the patient has issued and / or confirmed the permission information, thereby improving the level of data protection.
[0057] According to another aspect of the present invention, a method for providing a uniform resource locator includes the following steps: receiving usage information using an interface, wherein the permission information is further based on the usage information.
[0058] Typically, the usage information is related to the kind of use of the medical data record that the patient has permitted. In other words, the usage information is related to the kind of use of the medical data record that the patient has permitted. In general, the usage information describes how the medical data record may be used.
[0059] The inventors have realised that by including usage information in the consent information, the possible uses of a patient's data which they have consented to can be documented in a revision-safe manner.
[0060] According to another aspect of the present invention, a method for providing a uniform resource locator includes the following steps: receiving a second identifier of a patient using an interface; determining ownership information using a computing unit, wherein the ownership information includes an ownership signature based on a medical data record, wherein the ownership signature is signed based on the second identifier of the patient; and recording the ownership information in a distributed ownership ledger using the computing unit. Specifically, the second identifier of the patient includes a second private key associated with the patient, and the ownership signature is signed based on the second identifier of the patient signed using the second private key included in the second identifier of the patient.
[0061] Specifically, the second identifier of the patient is an identifier of the patient. Specifically, the second identifier of the patient may be the same as the first identifier of the patient, alternatively, the second identifier of the patient may include the first identifier of the patient, alternatively, the first identifier of the patient may include the second identifier of the patient. Specifically, the distributed ownership ledger may be the same as the distributed permission ledger, alternatively, one of the two distributed ledgers may include the other of the two distributed ledgers.
[0062] The inventors have recognized that by recording ownership information in a distributed ownership ledger, it is possible to undeniably record that certain medical data records are associated with a patient, for example, to allocate royalties to a patient. Specifically, if the patient's first identifier and the patient's second identifier are different (e.g., if the patient's first identifier and the patient's second identifier are based on a first asymmetric key pair and a different second asymmetric key pair), there is no correlation between the licensing information and the ownership information, which makes it more difficult for an external entity to associate the medical data record with the patient.
[0063] According to another possible aspect of the present invention, the permission information includes a first hash of the medical data record, and the ownership information includes a second hash of the medical data record, wherein the first hash of the medical data record and the second hash of the medical data record are different. Specifically, the first hash of the medical data record can be calculated using a first hash function, and the second hash of the medical data record can be calculated using a second hash function, wherein the first hash function and the second hash function are different. Specifically, the first hash of the medical data record can be based on a hash function with a first seed, and the second hash of the medical data record can be based on a hash function with a second seed, wherein the first seed and the second seed are different.
[0064] The inventors have recognised that by using different hashes in the licensing information and the ownership information, the licensing information and the ownership information cannot be associated with each other by an outside party, thereby increasing data privacy as the accumulation of metadata becomes more difficult.
[0065] According to another possible aspect of the present invention, the permission information includes a first hash of the medical data record, and the ownership information includes a second hash of the medical data record, wherein the second hash is based on a combination of the medical data record and other data. Specifically, the other data may be the patient's protected health information (acronym "PHI"). Specifically, the other data is data known only to the patient.
[0066] The inventors have realized that by using different hashes in the licensing information and the ownership information, the licensing information and the ownership information cannot be associated with each other by an outside party, thereby increasing data privacy because the accumulation of metadata becomes more difficult. In addition, by using other data known only to the patient, the patient can use the other data to prove their ownership.
[0067] According to another possible aspect of the present invention, the method for providing a uniform resource locator includes the step of unlocking access to a medical data record using a computing unit, wherein the step of unlocking access to the medical data record is performed after the following steps: recording permission information in a distributed permission ledger, and / or recording ownership information in a distributed ownership ledger.
[0068] The inventors recognized that by allowing access to medical data records only after permission information and / or ownership information is recorded in the corresponding distributed ledger, fraudulent permission information and / or ownership information recorded in the corresponding ledger by another entity can be detected due to the existence of earlier permission information and / or ownership information.
[0069] According to another aspect of the invention, the permission information comprises a smart contract.The first account is associated with an entity using the medical data record, and wherein the second account is associated with the first identifier of the patient and / or with the second identifier of the patient.
[0070] Specifically, an account corresponds to an asymmetric key pair including a private key and a public key. Specifically, an account can be identified by a public key.
[0071] Typically, a smart contract includes a program element that can be executed by a server, a client, or any other computing node. In particular, the program element may include program logic, source code, a scripting language, and / or compiled machine code. Specifically, the smart contract is recorded in a distributed ledger, in particular in a distributed ownership ledger or a distributed permission ledger. In particular, the smart contract may include conditions in terms of program logic and results in terms of program logic, wherein if certain conditions are met, the results are activated or executed.
[0072] Typically, the method also includes: creating a log, 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 log includes at least one of the first private key and the first public key and the second public key.
[0073] The inventors realised that an efficient payment process for the use of a medical data record may be initiated without disclosing the identity of the patient associated with the medical data record.According to further possible aspects of the invention, the distributed permission ledger and / or the distributed ownership ledger comprises a data block.
[0074] In general, a data block is the basic data record of a ledger. Specifically, a data block is an immutable data structure, which means that a data block cannot be changed or modified. This means that changes to the ledger can only be performed by adding or removing data blocks. Specifically, the immutability of a data block can be ensured by storing a hash value of the data block inside or outside the data block.
[0075] The inventors have recognized that using a distributed permission ledger and / or distributed ownership ledger comprising data blocks can more efficiently synchronize different copies of the distributed permission ledger and / or distributed ownership ledger. Specifically, using immutable data blocks can make it more difficult for someone to manipulate the distributed permission ledger and / or distributed ownership ledger.
[0076] According to another possible aspect of the present invention, a first data block of the distributed permission ledger includes link information associated with a second data block of the distributed permission ledger, and / or a first data block of the distributed ownership ledger includes link information associated with a second data block of the distributed ownership ledger. Specifically, the first data block and the second data block may be identical. Specifically, each data block of the distributed permission ledger includes a link to a data block of the distributed permission ledger, and / or each data block of the distributed ownership ledger includes a link to a data block of the distributed ownership ledger.
[0077] Specifically, a first data block of the distributed permission ledger and a second data block of the distributed permission ledger may be linked, and / or a first data block of the distributed ownership ledger and a second data block of the distributed ownership ledger may be linked. The link may be an undirected link or a directed link. Specifically, 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, then there is a link between the first data block and the second data block. Specifically, the link information may be data integrity information. Specifically, by checking the data integrity information related to the first data block, manipulation and / or change of the first data block may be identified or determined.
[0078] A common example of linking information related to the first data block is a hash of (at least a part of) the first data block, in particular, the hash of (at least a part of) the first data block may be stored in the second data block. If it can be assumed that the hash contained in the second data block has not changed, storing the hash of the first data block in the second data block allows verifying that the at least one data block has not been changed after determining the hash.
[0079] The data blocks of the distributed permission ledger and / or the distributed ownership ledger may further include some linking information, in particular, each additional linking information may be a hash of another data block of the respective distributed ledger. The linking information included in the data blocks of the distributed permission ledger and / or the distributed ownership ledger may be related to the data blocks, in particular, the linking information in the data blocks may be the same as the hash of (at least a part of) the data blocks.
[0080] The inventors have recognised that by using linking information in data blocks, the structure of a distributed permission ledger and / or a distributed ownership ledger may be incorporated into the data blocks, so that the structure of the distributed ledger does not need to be stored in external data items and / or separate data items.
[0081] According to another possible aspect of the present invention, the link information associated with the second data block includes a hash of the second data block.
[0082] 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 second subset of information and a first subset of information contained in the data block, wherein the second subset of information is the subset of information of the data block that contains or will contain the hash.
[0083] In general, a hash function is a function that maps data of arbitrary size to data of fixed size. Specifically, the hash function is a cryptographic hash function. Specifically, a cryptographic hash function is a deterministic function; specifically, the output of the hash function depends only on the input of the hash function. Specifically, the cryptographic hash function can be calculated in a fast manner for all input values. Specifically, the cryptographic hash function is only brute-force invertible, 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., brute force attack). In other words, finding an input value corresponding to the output value of the cryptographic hash function is a thorny problem. Specifically, finding a first input value and a second input value of a cryptographic hash function that result in the same output value is a thorny problem. Specifically, the cryptographic hash function is decentralized; that is, even the related inputs of the cryptographic hash function result in unrelated outputs of the cryptographic hash function.
[0084] Specifically, the hash function may compute a Merkle root of the input data, in particular by computing a hash within a Merkle tree.
[0085] The inventors realized that using the hash of the second data block as linking information included in the first data block makes the second data block immutable, or at least changes or manipulations of the second data block can be determined by inspecting the first data block, in particular by comparing the hash calculated based on the second data block with the hash of the second data block stored in the first data block.
[0086] In another aspect, the present invention relates to a method for using a uniform resource locator provided by a method for providing a uniform resource locator, the method comprising the step of receiving an access request for a requested medical data record through an interface, wherein the requested medical data record is stored in a storage unit, wherein the access request is based on the uniform resource locator, and the method further comprises the step of providing the requested medical data record based on the access request using the interface. Providing the medical data record is not essential to the present invention, and it is not essential to the present invention that the access request is based on the uniform resource locator.
[0087] Specifically, the interface may be an interface of a usage system. Specifically, the usage system may further include a computing unit. Specifically, the usage system may further include a storage unit. Specifically, the storage unit includes a repository, and specifically, the requested medical data record is stored in the repository. Specifically, the usage system may include a user client and / or a server, wherein the interface may be an interface of the user client and / or an interface of the server, wherein the computing unit may be a computing unit of the user client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the user client and / or a storage unit of the server.
[0088] Specifically, the requested medical data record is a medical data record. Specifically, the requested medical data record is one of the medical data records stored in the storage unit.
[0089] Specifically, the interface for receiving the access request is an interface of the server. Specifically, the access request is sent to the interface of the server via the interface of the client, in particular via the interface of the user client. Specifically, the medical data record is provided to the interface of the client, in particular to the interface of the user client. Specifically, the client or user client is a client or user client of an authorized entity and / or a requesting entity.
[0090] If the access request specifies the requested medical data record as the medical data record to be retrieved, the access request is directed to the requested medical data record. Specifically, the access request is directed to the requested medical data record through a uniform resource locator, which includes the location of the requested medical data record in a repository, especially in a repository of a server. Specifically, the access request can be based on the uniform resource locator through the following items: the access request is the same as the uniform resource locator, the uniform resource locator including the access request, or the access request including the uniform resource locator.
[0091] The inventors have realised that by means of the proposed method requested medical data records may be provided to an authorised entity or individual in an efficient yet still secure manner.
[0092] According to another possible aspect of the present invention, the step of providing the requested medical data record using the interface includes: sending the requested medical data record to the user client using the interface. The inventors have recognized that by sending the requested medical data record directly to the user client, the user client can use (e.g., view or manipulate) the medical data record very efficiently without any further interaction with the server.
[0093] According to another possible aspect of the present invention, in the step of providing the requested medical data record, the requested medical data record is provided to the user client in a secure environment. For example, the requested medical data record is provided as a read-only object within a website. Specifically, only a portion of the requested medical data record is provided to the user client (for example, only a rendered image is provided without providing raw imaging data). The inventors have recognized that by not sending the requested medical data record directly to the user client, it can be ensured that the requested medical data record is only used by the user client and / or the requesting entity in a permitted manner. Specifically, it is impossible for the user client and / or the requesting entity to store or distribute the requested medical data record. This enhances the data privacy of the proposed method.
[0094] According to another possible aspect of the present invention, the step of providing the requested medical data record includes: a sub-step of receiving a trainable algorithm through an interface, a step of executing a training step of the trainable algorithm based on the requested medical data record by a computing unit, and a step of providing the trainable algorithm through an interface.
[0095] Typically, a trainable algorithm is an algorithm that maps input data to output data based on internal parameters, wherein the internal parameters can be adjusted or modified by a training step. In particular, the trainable algorithm is a neural network (e.g. a deep neural network or a convolutional neural network), wherein the internal parameters of the neural network are edge weights. In particular, the adaptation or modification of the internal parameters of the neural network can be performed by means of back propagation.
[0096] The inventors have recognized that by training a trainable algorithm based on requested medical data records on a server, the requested medical data records do not need to be transmitted to the user client and thus the user client and / or requesting entity cannot distribute the requested medical data records without authorization.
[0097] According to another aspect of the invention, the access request is initiated by a requesting entity, wherein permission information based on the medical data record and based on an identifier of the authorized entity is recorded in a distributed permission ledger, the method further comprising the steps of: receiving the identifier of the requesting entity using an interface, and performing a first check using a computing unit as follows, whether the distributed permission ledger records permission information based on the requested medical data record and based on the identifier of the requesting entity, wherein the providing step is performed only if the first check is positive. Specifically, the computing unit is a computing unit of the use system, and specifically, the computing unit is a computing unit of the server.
[0098] Specifically, if the distributed permission ledger includes permission information, the distributed permission ledger records the permission information. Specifically, if one of the data blocks of the distributed permission ledger includes permission information, the distributed permission ledger includes permission information. Specifically, if the permission information includes the requested medical data record and / or if the permission information includes a hash of the requested medical data record, the permission information is based on the requested medical data record. Specifically, if the permission information includes an identifier of the requesting entity, the permission information is based on the identifier of the requesting entity.
[0099] In the case where the permission information is based on the requested medical data record by including a hash of the medical data record, the method may further include the step of determining the hash of the requested medical data record, the method may further include the step of selecting permission information recorded in the distributed permission ledger including the hash of the requested medical data record. Specifically, the step of performing the first check may then be based on the selected permission information.
[0100] The inventors have realised that by performing the described first check it can be ensured that a requested medical data record is only provided to a requesting entity if the patient (to whom the medical data record is associated) has given permission for the requested medical data record to be shared with the requesting entity.
[0101] According to another possible aspect of the present invention, the permission information recorded in the distributed permission ledger includes a permission signature based on the respective medical data record and / or a permission signature based on the respective identifier of the authorized entity, wherein the permission signature is signed based on the first identifier of the patient involved in the corresponding medical data record, and the method for using the uniform resource locator also includes the following step of performing a second check: whether the permission signature is validly signed based on the first identifier of the patient, wherein the providing step is only performed if the second check is affirmative.
[0102] Specifically, if the permission signature is signed using a private key of the patient's second identifier, the second check may be based on an associated public key of the patient's second identifier. Specifically, the second check may include execution of a signature verification algorithm with the permission signature and the associated public key of the patient's second identifier as input.
[0103] The inventors have realised that by performing the described second check it can be ensured that the permission information was actually issued and / or confirmed by the patient associated with the medical data record.
[0104] According to another possible aspect of the invention, the identifier of the requesting entity is based on a digital certificate. Specifically, the identifier of the requesting entity is a digital certificate. Specifically, the digital certificate is signed by a certification authority. Specifically, the step of performing a first check may be based on a comparison of the identifier of the requesting entity with an identifier of an authorized entity, both identifiers being digital certificates. Specifically, the step of performing a check may include: checking the validity of the digital certificate as the identifier of the requesting entity.
[0105] The inventors have realised that the security of the method may be improved by using a digital certificate as an identifier of the requesting entity, since the use of a digital certificate enables the identity of the requesting entity to be proven.
[0106] According to another possible aspect of the present invention, the identifier of the requesting entity is a digital certificate, and the access request includes a signature signed with a private key associated with the digital certificate. The inventors recognize that by using the signature, it can be proved that the requesting entity possesses the private key associated with the digital certificate, which indicates that the requesting entity is the owner of the digital certificate without exposing the private key to the server or a third party. Specifically, the server can use a signature verification algorithm based on the public key of the digital certificate to prove the validity of the signature. Specifically, the server and the user client can perform a challenge-response method, and specifically, the server can provide the user client with data based on which the signature is to be created.
[0107] According to another possible aspect of the present invention, the access request includes expected usage information, and the method further includes the following steps: determining the stored usage information based on the distributed permission ledger, wherein the stored usage information is recorded in the distributed permission ledger associated with the medical data record, and the method further includes the step of performing the following third check: whether the expected usage information and the stored usage information match.
[0108] Generally, the expected use information and the stored use information match if the expected use information specifies that the medical data record will be used in accordance with the stored use information. Specifically, if both the expected use information and the stored use information include one or more items describing the expected use or permitted uses of the medical data record, the expected use information and the stored use information match when the items of the expected use information are a subset of the items of the stored use information.
[0109] The inventors have realised that by performing a third check in relation to the use of the medical data record, it can be ensured that the medical data record is only used in accordance with the permission of the patient to whom the medical data record is associated.
[0110] According to another aspect of the present invention, ownership information is recorded in a distributed ownership ledger, wherein each ownership information includes an ownership signature based on the medical data record, wherein the ownership signature is signed based on a second identifier of the patient, and the method for using a uniform resource locator further comprises the step of determining, using a computing unit, based on the distributed ownership ledger, the ownership second identifier of the patient as the owner of the requested medical data record. The second account is associated with the ownership second identifier of the patient.
[0111] Specifically, if the distributed ownership ledger includes ownership information, the distributed ownership ledger records the ownership information. Specifically, if one of the data blocks of the distributed ownership ledger includes ownership information, the distributed ownership ledger includes the ownership information. Specifically, if the ownership signature is the result of a signature algorithm applied to a medical data record and / or a hash of a medical data record, the ownership signature is based on a medical data record. Specifically, the ownership information including the ownership signature may also include the medical data record and / or the hash of the medical data on which the ownership signature is based. Specifically, the ownership information including the ownership signature may also include: a second identifier based on which the ownership information is signed, or a portion of the second identifier based on which the ownership information is signed.
[0112] Specifically, the ownership second identifier is one of the second identifiers included in the distributed ownership ledger, wherein the second identifier is included in the distributed ownership ledger if there is ownership information including an ownership signature signed based on the second identifier.
[0113] Specifically, if the permission information is recorded in the distributed permission ledger, and if the distributed permission ledger records the permission information based on the requested medical data record, and if the recorded permission information also includes a permission signature signed based on the first identifier of the patient, then the second identifier and the first identifier are not the same. Specifically, the private key included in the first identifier is not equal to the private key included in the second identifier, and the public key included in the first identifier is not equal to the public key included in the second identifier.
[0114] The inventors have recognized that, through the proposed additional steps, the requesting entity can be prompted to pay the patient for the use of the requested medical data record. According to another aspect of the present invention, the method of using a uniform resource locator also includes: a step of receiving, by a trusted entity, account information of a patient who is the owner of the requested medical data record; and a step of initiating, by the trusted entity, payment from the trusted entity to the patient. The third account is associated with the trusted entity.
[0115] Specifically, the account information is sent from the user client to a trusted entity, in particular to a payment server owned by the trusted entity, and in particular the account information is sent from an interface of the user client to an interface of the payment server.
[0116] Specifically, the account information is a private key associated with the patient. Specifically, the account information is a private key included in the second identifier of the patient.
[0117] The payment initiated may include the transfer of standard currencies.
[0118] The inventors have realised that, by means of the proposed further steps, the patient can receive payment for the use of the medical data record associated with the patient. In another aspect, the present invention relates to a providing system for providing a uniform resource locator, comprising:
[0119] - an interface configured to receive a medical data record, wherein the medical data record is related to a patient, the interface further configured to provide a uniform resource locator to the patient,
[0120] - a computing unit configured for determining a uniform resource locator associated with a medical data record, wherein the uniform resource locator comprises an authorization token based on the medical data record, and wherein the medical data record can be accessed by following the uniform resource locator.
[0121] Specifically, the providing system for providing a uniform resource locator can be configured to: execute the method for providing a uniform resource locator according to the present invention and its various aspects. The providing system is configured to: execute the method and its various aspects through its interface and its computing unit, and its computing unit is configured to execute the corresponding method steps.
[0122] The providing system 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 providing 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.
[0123] The providing system may be implemented as a server or a part of a server, alternatively, the providing system may be implemented as a patient client or a part of a patient client, alternatively, the providing system may be implemented as a combination of a server and a patient client.
[0124] In another aspect, the present invention relates to a computer program product comprising a computer program which can be loaded into a storage unit of a providing system, the computer program comprising a program code portion which causes the providing system to perform a method for providing a uniform resource locator according to an aspect of the present invention when the computer program is executed in the providing system.
[0125] In another possible aspect, the present invention relates to a computer-readable medium having a program code portion of a computer program stored thereon, which can be loaded into a providing system and / or can be executed in the providing system so that when the program code portion is executed in the access system, the providing system performs a method for providing a uniform resource locator according to an aspect of the present invention.
[0126] An advantage of implementing the invention by means of a computer program product and / or a computer-readable medium is that already existing provisioning systems can be easily adapted by means of a software update to operate as proposed by the invention.
[0127] In another possible aspect, the present invention relates to a system for using a uniform resource locator, the uniform resource locator being provided by a method for providing a uniform resource locator according to the present invention or one of its aspects, the system comprising:
[0128] - an interface configured to receive an access request directed to a requested medical data record, wherein the requested medical data record is stored in a repository, wherein the access request is based on a uniform resource locator,
[0129] The interface is further configured to provide the requested medical data record based on the access request,
[0130] - Computational unit.
[0131] Specifically, the use system for using the uniform resource locator can be configured to perform the method for using the uniform resource locator according to the present invention and its various aspects. The use system is configured to perform the method and its various aspects through its interface and its computing unit, and its computing unit is configured to perform corresponding method steps.
[0132] The use system can be implemented as a data processing system or a part of a data processing system. Such a data processing system can include, for example, a cloud computing system, a computer network, a computer, a tablet computer, a smart phone, etc. The use system 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.
[0133] The usage system may be implemented as a server or a part of a server, alternatively, the usage system may be implemented as a user client or a part of a user client, alternatively, the usage system may be implemented as a combination of a server and a user client.
[0134] In another possible aspect, the present invention relates to a computer program product comprising a computer program, which can be loaded into a storage unit of a usage system, and the computer program includes the following program code parts: when the computer program is executed in the usage system, the program code parts cause the usage system to perform the method for using a uniform resource locator according to an aspect of the present invention.
[0135] In another possible aspect, the present invention relates to a computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a usage system and / or can be executed in the usage system so that when the program code portion is executed in the usage system, the usage system performs a method for using a uniform resource locator according to an aspect of the present invention.
[0136] An advantage of implementing the invention by means of a computer program product and / or a computer-readable medium is that already existing access systems can be easily adapted by means of a software update to function as proposed by the invention.
[0137] According to another possible aspect, the present invention relates to a method for providing location information associated with a medical data record. The method comprises receiving a medical data record using an interface, wherein the medical data record is associated with a patient. Furthermore, the method comprises storing the medical data record in a repository using a computing unit. Furthermore, the method comprises determining location information associated with the medical data record stored in the repository using the computing unit, wherein the medical data set can be accessed based on the location information. Furthermore, the method comprises providing the location information to the patient using an interface. Specifically, the location information can be a uniform resource locator.
[0138] Specifically, the interface is an interface of the providing system. Specifically, the computing unit is a computing unit of the providing system. Specifically, the storage unit is a storage unit of the providing system. Specifically, the providing system may include a patient client and / or a server, wherein the interface may be an interface of the patient client and / or an interface of the server, wherein the computing unit may be a computing unit of the patient client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the patient client and / or a storage unit of the server. Specifically, the medical data records are stored in a repository within the storage unit. Specifically, the repository is part of the storage unit of the providing system, or is stored in the storage unit of the providing system, and specifically, the repository is part of the storage unit of the server of the providing system, or is stored in the storage unit of the server of the providing system.
[0139] The inventors realize that, through this method, medical data records related to a patient can be accessed and used by the patient, including forwarding the medical data records to a doctor. Specifically, the patient can decide which subset of medical data records related to the patient can be accessed by the doctor based on forwarding only selected links.
[0140] According to another possible aspect of the invention, the method for providing location information further comprises: receiving an identifier of an authorized entity using an interface, wherein the authorized entity is allowed to access the medical data records stored in the storage unit, and wherein the location information is based on the identifier of the authorized entity.
[0141] The inventors have recognized that location information based on an identifier of an authorized entity can be used to allow only authorized entities to access medical data records using the location information. Specifically, if the authorized entity forwards the location information to an unauthorized entity, the unauthorized entity cannot access the medical data records based on the location information.
[0142] According to another possible aspect of the present invention, the method for providing location information further includes: recording the medical data record and the identifier of the authorized entity in a distributed ledger using a computing unit. Specifically, the medical data record can be recorded in the distributed ledger by recording a hash of the medical data record in the distributed ledger. Specifically, the identifier of the authorized entity can be recorded in the distributed ledger by recording a hash of the identifier of the authorized entity in the distributed ledger. Specifically, the medical data record and the identifier of the authorized entity can be recorded in the distributed ledger by recording a hash of the data set in the distributed ledger, wherein the data set is based on the medical data record and the identifier of the authorized entity. Specifically, the data set can be based on the medical data record by including the medical data record, and the data set can be based on the identifier of the authorized entity by including the identifier of the authorized entity.
[0143] The inventors have recognized that by recording medical data records and identifiers of authorized entities in a distributed ledger, the process by which a patient authorizes an authorized entity to access the medical data record can be recorded in a revision-safe manner, resulting in better system data protection.
[0144] According to another possible aspect of the present invention, the step of recording the medical data record and the identifier of the authorized entity in the distributed ledger includes: creating a signature based on the medical data record and / or based on the identifier of the authorized entity, wherein the signature is signed using a private key associated with the patient.
[0145] The inventors have recognized that by creating a signature based on a medical data record signed using a private key associated with the patient and / or based on an identifier of an authorized entity, it is possible to document the patient's own intent or intention to share the medical data record with the authorized entity.
[0146] According to another possible aspect of the present invention, the method for providing location information further comprises: sending the location information to an authorized entity using an interface.
[0147] In particular, the location information may be provided to the authorized entity by creating an electronic message and sending the electronic message to the authorized entity. Examples of electronic messages are emails, short message services (acronym "SMS"), messages according to the Extensible Messaging and Presence Protocol (acronym "XMPP") or other electronic messages. Alternatively, the location information may also be displayed on the patient device, for example as text information or a one-dimensional or two-dimensional code, such as a barcode, a QR code, a matrix code or an Aztec-Code. The displayed location information may then be entered into the user device manually or by taking a picture of the displayed code.
[0148] The inventors have realised that by providing location information to an authorized entity, the authorized entity can immediately access the medical data record without having to search a database of medical data records or a database of location information for the correct medical data record or the correct location information.
[0149] According to another possible aspect, the present invention relates to a method for using location information provided by a method for providing location information, the method comprising: receiving an access request to a medical data record via an interface, wherein the medical data record is stored in a storage unit, and wherein the access request is based on the location information. In addition, the method for using location information comprises: providing the medical data record using the interface.
[0150] Specifically, the interface is an interface of the use system. Specifically, the use system may further include a computing unit. Specifically, the storage unit is a storage unit of the use system. Specifically, the providing system may include a user client and / or a server, wherein the interface may be an interface of the user client and / or an interface of the server, wherein the computing unit may be a computing unit of the user client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the user client and / or a storage unit of the server. Specifically, the medical data records are stored in a repository within the storage unit. Specifically, the repository is part of the storage unit of the use system, or is stored in the storage unit of the use system, and specifically, the repository is part of the storage unit of the server of the use system, or is stored in the storage unit of the server of the use system.
[0151] In particular, the medical data record may be encrypted before being provided. In particular, the medical data record may be encrypted using asymmetric encryption (which uses a public key of the entity receiving the medical data record).
[0152] The inventors realised that by this method, medical data records can be provided in an efficient and straightforward manner without the need to search for the correct medical data record in a repository.
[0153] According to another possible aspect of the invention, a method for using location information provided by a method for providing location information comprises: receiving an identifier of a requesting entity using an interface, wherein the access request is initiated by the requesting entity. The method further comprises performing, using a computing unit, a check as follows: whether a pair comprising a medical data record and an identifier of the requesting entity is recorded in a distributed ledger, wherein the providing step is performed only in the case of a positive check.
[0154] The inventors have realised that by performing a check and providing the medical data record only in the event of a positive check, it can be ensured that the medical data record is only provided to authorized entities and not to unauthorized entities.
[0155] According to another possible aspect, the present invention relates to a system for providing location information associated with a medical data record, comprising:
[0156] - an interface configured for receiving a medical data record, wherein the medical data record is related to a patient, the interface being further configured for providing the location information to the patient using the interface,
[0157] - a computing unit configured to store the medical data record in a storage unit,
[0158] The computing unit is further configured for determining location information associated with the medical data record stored in the storage unit, wherein the medical data set can be accessed based on the location information.
[0159] According to another possible aspect, the invention relates to a computer program product comprising a program element which, when loaded into a storage unit of a providing system, causes the providing system to perform the steps of the method for providing location information according to an aspect of the invention.
[0160] According to another possible aspect, the present invention relates to a computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a providing system and / or can be executed in the providing system so that when the program code portion is executed in the providing system, the providing system performs a method for providing location information according to an aspect of the present invention.
[0161] According to another possible aspect, the present invention relates to a system of use, which is configured to receive an access request to a medical data record, wherein the medical data record is stored in the system of use, in particular in a storage unit of the system of use, wherein the access request is based on location information provided by the method for providing location information according to the present invention, and the system of use is also configured to provide medical data.
[0162] According to another possible aspect, the invention relates to a computer program product comprising a program element which, when loaded into a storage unit of a using system, causes the using system to perform the steps of the method for using location information according to an aspect of the invention.
[0163] According to another possible aspect, the present invention relates to a computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a usage system and / or can be executed in the usage system so that when the program code portion is executed in the usage system, the usage system performs a method for using location information according to aspects of the present invention.
[0164] According to another possible aspect, the present invention relates to a method for storing permissions, the method comprising receiving a medical data record using an interface, wherein the medical data record is associated with a patient. The method further comprises receiving an identifier of an authorized entity using the interface. The method further comprises determining permission information using a computing unit, wherein the permission information is based on the medical data record and the identifier of the authorized entity. The method further comprises recording the permission information in a distributed permission ledger using the computing unit.
[0165] Specifically, the interface is an interface of the providing system. Specifically, the computing unit is a computing unit of the providing system. Specifically, the providing system may include a storage unit. Specifically, the providing system may include a patient client and / or a server, wherein the interface may be an interface of the patient client and / or an interface of the server, wherein the computing unit may be a computing unit of the patient client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the patient client and / or a storage unit of the server. Specifically, the medical data records are stored in a repository within the storage unit. Specifically, the repository is part of the storage unit of the providing system, or is stored in the storage unit of the providing system, and specifically, the repository is part of the storage unit of the server of the providing system, or is stored in the storage unit of the server of the providing system.
[0166] In particular, the permission information is based on the medical data record by including a hash of the medical data record. In particular, the permission information is based on the identifier of the authorized entity by including the identifier of the authorized entity or a hash of the identifier of the authorized entity. In particular, the permission information is based on the medical data record and the identifier of the authorized entity by including a hash of a combination of the medical data record and the identifier of the authorized entity. In particular, the identifier of the authorized entity may be based on a private key and / or a public key associated with the authorized entity. In particular, the identifier of the authorized entity may include a public key associated with the authorized entity.
[0167] The inventors have recognised that by storing licensing information in a distributed permissioned ledger, licensing information can be stored in a revision-safe and non-disputable manner.
[0168] According to another possible aspect of the present invention, the method for storing permission information includes: receiving a first identifier of the patient using an interface, wherein the permission information is also based on the first identifier of the patient. Specifically, the first identifier of the patient can be based on a private key and / or a public key associated with the patient.
[0169] The inventors have realised that by basing consent information on a patient's first identifier, consent information which was actually issued by the patient, or which was given permission by the patient to use the data, can be stored in a redaction-safe and non-disputable manner.
[0170] According to another possible aspect of the method for storing permission information, the permission information comprises a permission signature based on the medical data record and on an identifier of the authorized entity, wherein the permission signature is signed using the first identifier of the patient.
[0171] The inventors have realized that by including the permission information with a permission signature, the fact that the patient actually permits the use of the medical data record can be easily checked by performing a check on the permission signature based on the private key of the corresponding patient.
[0172] According to another possible aspect of the present invention, a method for storing permission information includes: receiving a second identifier of a patient using an interface. In addition, the method includes: determining ownership information using a computing unit, wherein the ownership information includes an ownership signature based on the medical data record, wherein the ownership signature is signed using the second identifier of the patient. In addition, the method includes: recording the ownership information in a distributed ownership ledger.
[0173] Specifically, the second identifier of the patient may be the same as the first identifier of the patient; alternatively, the first identifier of the patient and the second identifier of the patient may be different. Specifically, the distributed ownership ledger may be the same as the distributed permission ledger; alternatively, the distributed ownership ledger and the distributed permission ledger may be different.
[0174] The inventors recognized that by signing the ownership signature using the patient's second identifier and signing the permission signature using the patient's first identifier, the ownership of the medical data record can be recorded separately from the permission to use the medical data record, thereby improving the anonymity of the system and making it more difficult to collect information about the patient using metadata.
[0175] According to another possible aspect of the present invention, a method for storing licensing information includes: receiving usage information using an interface, wherein the licensing information is further based on the usage information.
[0176] The inventors have realized that by including usage information in the permission information, the use of patient permission can be stored in a revision-safe manner. Specifically, the use of medical data in an unauthorized manner can be documented and / or prevented.
[0177] According to another possible aspect of the present invention, in a method for storing licensing information, the licensing information includes a smart contract.
[0178] The inventors recognized that by including smart contracts in the permission information, it is possible to ensure that medical data records are only used in the manner permitted by the patient.
[0179] The first account is associated with an entity using the medical data record, and wherein the second account is associated with a first identifier of the patient and / or with a second identifier of the patient.
[0180] The inventors have recognised that an efficient payment process for the use of a medical data record may be initiated without disclosing the identity of the patient associated with the medical data record.
[0181] According to another possible aspect, the present invention relates to a method for using permission information stored in a distributed permission ledger according to a method for storing permission information and various aspects thereof, the method comprising: receiving an access request pointing to a requested medical data record through an interface, wherein the requested medical data record is stored in a storage unit, and wherein the requested medical data record is related to a patient, the method further comprising: using a computing unit to search for permission information in a distributed permission ledger, wherein the permission information is related to the requested medical data record; based on the permission information, using the computing unit to perform the following check, whether the patient permits the use of the requested medical data record, the method further comprising: if the first check is positive, using the computing unit to process the requested medical data record.
[0182] Specifically, the interface is an interface of the use system. Specifically, the computing unit is a computing unit of the use system. Specifically, the storage unit is a storage unit of the use system. Specifically, the providing system may include a user client and / or a server, wherein the interface may be an interface of the user client and / or an interface of the server, wherein the computing unit may be a computing unit of the user client and / or a computing unit of the server, and wherein the storage unit may be a storage unit of the user client and / or a storage unit of the server. Specifically, the medical data records are stored in a repository within the storage unit. Specifically, the repository is part of the storage unit of the use system, or is stored in the storage unit of the use system, and specifically, the repository is part of the storage unit of the server of the use system, or is stored in the storage unit of the server of the use system.
[0183] Specifically, if the permission information includes the requested medical data record, and / or if the permission information includes a hash of the requested medical data record, and / or if the permission information includes a link to the requested medical data record (in particular, a uniform resource locator pointing to the medical data record), then the permission information is related to the requested medical data record.
[0184] Specifically, whether the patient permits the use of the requested medical data record can be determined by whether the permission information based on the requested medical data record is included in the distributed permission ledger. Alternatively, whether the patient permits the use of the requested medical data record can be encoded in the permission information.
[0185] Specifically, the interface is an interface of a server and / or a repository. Specifically, the computing unit is a computing unit of a server.
[0186] The inventors have realised that by means of this method of using permission information, the processing of a medical data record can be linked to the permission given by a patient who is the subject of the medical data record.
[0187] According to another possible aspect of the invention, in a method for using license information stored in a distributed licensed ledger, an access request is initiated by a requesting entity, and the method further comprises receiving an identifier of the requesting entity using an interface. In addition, the license information comprises an identifier of an authorized entity, and the check is also based on a comparison of the identifier of the requesting entity with the identifier of the authorized entity. Specifically, if the identifier of the requesting entity is equal to the identifier of the authorized entity, the check is positive. Specifically, if the identifier of the requesting entity is obtained from the identifier of the authorized entity, the check may also be positive. Specifically, the license information comprises multiple identifiers of authorized entities.
[0188] The inventors have recognised that by comparing the identifier of an authorised entity with the identifier of the requesting entity, it can be ensured that the requested medical data record is only processed by or for entities that the patient has given permission to do so.
[0189] According to another possible aspect of the present invention, in a method for using permission information stored in a distributed permission ledger, the permission information includes a smart contract. In addition, processing the requested medical data record includes executing the smart contract.
[0190] The inventors have recognized that by executing a smart contract included in the permission information during the processing of the requested medical data record, the result of processing the requested medical data record can occur as a direct result of the processing. Examples of such a result may be sending a message notifying about the processing of the requested medical data record, or a fee associated with the processing of the requested medical data record.
[0191] According to another possible aspect of the present invention, in a method for using permission information stored in a distributed permissioned ledger, an access request includes a trainable function, wherein processing the requested medical data record includes: training the trainable function based on the requested medical data record, and optionally, providing the trainable function after training the trainable function based on the requested medical data record.
[0192] Typically, a trainable function is a function that maps input data to output data, wherein the output data also depends on at least one parameter of the trainable function. Specifically, training the trainable function comprises adapting at least one parameter based on the training data. Specifically, the parameters of the trainable function can be adapted by applying the trainable function to the input data to the calculated output data, and by comparing the output data with known output data corresponding to the input data (supervised learning). Other forms of adapting the parameters are also known, for example, semi-supervised learning or unsupervised learning. Examples of trainable functions are artificial neural networks (particularly convolutional artificial neural networks, in particular deep convolutional artificial neural networks) and support vector machines.
[0193] The inventors have realized that by training the trainable function based on the requested medical data records on a server and / or repository, the requested medical data records do not need to be sent outside of the server and / or repository. In particular, the requested medical entity cannot be sent from the requesting entity to an unauthorized entity, either accidentally or intentionally. Furthermore, the number of training steps performed based on the requested medical data records can be controlled; in particular, each training step can be billed separately.
[0194] According to another possible aspect of the present invention, in a method for using permission information stored in a distributed permission ledger, processing the requested medical data record includes: displaying the requested medical data record in a non-copyable manner.
[0195] Specifically, the requested medical data record may be displayed in a web interface, wherein by using server-side code or client-side code (such as JavaScript), making a copy of the requested medical data record may be prevented or even made impossible. In addition, local viewer software may be used on a user client that does not allow copying of the displayed requested medical data record, and the processing may include sending the requested medical data record to the local software viewer.
[0196] The inventors have realized that by displaying the requested medical data record in a non-copyable manner, the user can use the requested medical data record as a reference value or reference case without being able to store the requested medical data record or distribute the requested medical data record to unauthorized entities. Specifically, each use of the requested medical data record as a reference value or reference case can be billed separately.
[0197] According to another possible aspect of the present invention, in a method for using permission information stored in a distributed permission ledger, ownership information is recorded in the distributed ownership ledger, wherein each ownership information includes an ownership signature based on the medical data record, wherein the ownership signature is signed based on a second identifier of the patient, and the method further comprises: using a computing unit to determine the second identifier of the patient as the owner of the requested medical data record based on the distributed ownership ledger. The first account is associated with the identifier of the requesting entity, and the second account is associated with the second identifier of the patient.
[0198] The inventors have recognized that by the proposed additional steps, payment for the use of the requested medical data record from the requesting entity to the patient can be facilitated. According to another possible aspect of the invention, a method of using permission information stored in a distributed permissioned ledger includes: receiving, by a trusted entity, account information of a patient who is the owner of the medical data record; and initiating payment from the trusted entity to the patient. A third account is associated with the trusted entity.
[0199] The inventors have realised that, through the proposed further steps, the patient may receive payment for the use of medical data records related to the patient.
[0200] According to another possible aspect, the present invention relates to a license storage system for storing licenses, the system comprising:
[0201] - an interface configured for receiving a medical data record using the interface, wherein the medical data record is related to a patient,
[0202] The interface is further configured to receive an identifier of an authorized entity using the interface,
[0203] a computing unit configured for determining permission information using the computing unit, wherein the permission information is based on the medical data record and an identifier of the authorized entity,
[0204] The computing unit is further configured to record the permission information in a distributed permission ledger using the computing unit.
[0205] Specifically, the license storage system for storing licenses can be configured to perform the method for storing licenses according to the present invention and its various aspects. The license storage system is configured to: perform the method and its various aspects through its interface and its computing unit, and its computing unit is configured to perform the corresponding method steps.
[0206] The license storage system 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 license storage 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.
[0207] The permission storage system may be implemented as a server or a part of a server, alternatively, the permission storage system may be implemented as a patient client or a part of a patient client, alternatively, the permission storage system may be implemented as a combination of a server and a patient client. In particular, the permission storage system may be the same as the providing system.
[0208] According to another possible aspect, the invention relates to a computer program product comprising a program element which, when loaded into a storage unit of a license storage system, causes the license storage system to perform the method steps of the method for storing licenses of an aspect of the invention.
[0209] According to another possible aspect, the present invention relates to a computer-readable medium on which a program code portion of a computer program is stored, which program code portion can be loaded into a license storage system and / or can be executed in the license storage system so that when the program code portion is executed in the license storage system, the license storage system performs a method for storing licenses according to aspects of the present invention.
[0210] An advantage of implementing the invention by means of a computer program product and / or a computer-readable medium is that already existing provisioning systems can be easily adapted by means of a software update to operate as proposed by the invention.
[0211] According to another possible aspect, the present invention relates to a license use system for using license information stored in a distributed license ledger according to a method for storing licenses, the license use system comprising:
[0212] - an interface configured for receiving, via the interface, an access request directed to a requested medical data record, wherein the requested medical data record is stored in a repository, and wherein the requested medical data record is related to a patient,
[0213] - a computing unit configured to use the computing unit to look up permission information in a distributed permissioned ledger, wherein the permission information is related to the requested medical data record,
[0214] The computing unit is further configured to use the computing unit to perform a check (CHK) based on the permission information whether the patient has permission to use the requested medical data record and to use the computing unit to process the requested medical data record if the first check is positive.
[0215] Specifically, a license use system for using license information stored in a distributed license ledger can be configured to perform a method for using license information stored in a distributed license ledger according to the present invention and its various aspects. The license use system is configured to perform the method and its various aspects through its interface and its computing unit, and its computing unit is configured to perform the corresponding method steps.
[0216] The permission use system 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 permission use 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.
[0217] The license use system can be implemented as a server or a part of a server, alternatively, the license use system can be implemented as a user client or a part of a user client, alternatively, the license use system can be implemented as a combination of a server and a user client. Specifically, the license use system can be the same as the use system.
[0218] According to another possible aspect, the present invention relates to a computer program product comprising a program element which, when loaded into a storage unit of a license utilization system, causes the license utilization system to perform the steps of the method according to an aspect of the invention for using license information stored in a distributed license ledger.
[0219] According to another possible aspect, the present invention relates to a computer-readable medium having stored thereon program code portions of a computer program, which program code portions can be loaded into a license usage system and / or can be executed in a license usage system to cause the license usage system to perform a method for using license information stored in a distributed license ledger according to an aspect of the invention when the program code portions are executed in the usage system.
[0220] An advantage of implementing the invention by means of a computer program product and / or a computer-readable medium is that already existing provisioning systems can be easily adapted by means of a software update to operate as proposed by the invention.
[0221] The characteristics, features and advantages of the present invention described above and the manner in which they are achieved become clearer and easier to understand in view of 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 drawings, the same components or parts may be marked with the same reference numerals. The space and file location in the uniform resource locator are not relevant and are only for better readability. In general, the drawings are not to scale. In the following:
[0222] Figure 1 A first embodiment of a method for providing a uniform resource locator is shown.
[0223] Figure 2 A second embodiment of the method for providing a uniform resource locator is shown.
[0224] Figure 3 An implementation of a data block of a distributed permissioned ledger is shown,
[0225] Figure 4 An implementation of a data block of a distributed ownership ledger is shown,
[0226] Figure 5 A flow chart illustrating an embodiment of a method for storing medical data records in a repository,
[0227] Figure 6 A first embodiment of the data flow between the patient client, the server and the user client is shown,
[0228] Figure 7 A second embodiment of the data flow between the patient client, the server and the user client is shown,
[0229] Figure 8 shows the detailed data flow between the server and the patient client for creating a signature,
[0230] Fig. 9A first embodiment of a method for using a uniform resource locator is shown,
[0231] Fig.10 A second embodiment of a method for using a uniform resource locator is shown,
[0232] Fig.11 shows an implementation of the data flow between a user client, a server and a trusted entity,
[0233] Fig.12 shows implementations of a patient client, a server, and a user client,
[0234] Fig.13 A first embodiment of providing a system is shown,
[0235] Fig.14 A second embodiment of the providing system is shown,
[0236] Fig.15 A first embodiment of using the system is shown,
[0237] Fig.16 A second embodiment of using the system is shown,
[0238] Fig.17 An embodiment of a method for providing location information is shown.
[0239] Fig.18 An embodiment of a method for storing permissions is shown.
[0240] Figure 1 A flow chart of a first embodiment of a method for providing a PROV-URL uniform resource locator URL is shown. The first step of the embodiment shown is to receive a REC-MDR medical data record MDR, MDR.j, MDR.k, MDR.l using an interface PS.IF, wherein the medical data record MDR, MDR.j, MDR.k, MDR.l is related to a patient PAT. In particular, the interface PS.IF is an interface PS.IF of a providing system PS. In this embodiment, the providing system PS comprises a server S as a network server connected to the Internet.
[0241] In this embodiment, the medical data record MDR, MDR.j, MDR.k, MDR.1 comprises a medical imaging data set. Alternatively, the medical data record MDR, MDR.j, MDR.k, MDR.1 may also comprise other medical data, such as personal health information, laboratory reports, electronic medical records, diagnostic information or other medical data.
[0242] The second step of the embodiment shown is to store the STR-MDR medical data records MDR, MDR.j, MDR.k, MDR.l using the storage unit PS.MU of the providing system PS. In particular, the storage unit PS.MU of the providing system PS comprises a repository located in the server S, wherein the medical data records MDR, MDR.j, MDR.k, MDR.l are stored in the repository of the server S. In this embodiment, the medical data records MDR, MDR.j, MDR.k, MDR.l are stored as files in folders of the folder structure of the repository. In particular, file names are assigned to the medical data records MDR, MDR.j, MDR.k, MDR.l.
[0243] The second step of using the storage unit PS.MU to store the STR.MDR medical data records MDR, MDR.j, MDR.k, MDR.l is optional. Alternatively, the storage unit may be used to store the medical data records MDR, MDR.j, MDR.k, MDR.l before performing the method for providing the PROV-URL uniform resource locator URL. In this case, the step of receiving the REC-MDR medical data records MDR, MDR.j, MDR.k, MDR.l using the interface PS.IF may include receiving the file name and / or location of the medical data records MDR, MDR.j, MDR.k, MDR.l already stored in the repository.
[0244] In this embodiment, the medical data records MDR, MDR.j, MDR.k, MDR.l are stored, for example, in the folder “data / ct / ” and have the file name “mdr_1.dat.” The server S is accessible as a web server by the uniform resource locator “cloud-storage.com”.
[0245] The third step of the embodiment shown is to determine, using the computing unit PS.CU, a uniform resource locator URL associated with the medical data record MDR, MDR.j, MDR.k, MDR.l by DET-URL, wherein the uniform resource locator URL comprises an authorization token based on the medical data record MDR, MDR.j, MDR.k, MDR.l, wherein the uniform resource locator URL comprises the location of the medical data record MDR, MDR.j, MDR.k, MDR.l in the repository, and wherein the medical data record MDR, MDR.j, MDR.k, MDR.l can be accessed by the following uniform resource locator URL. Specifically, the computing unit PS.CU is a computing unit PS.CU of the providing system PS; specifically, the computing unit PS.CU is a computing unit S.CU of the server.
[0246] In this embodiment, the uniform resource locator URL is "http: / / cloud-storage.com / data / ct / mdr_1.dat?auth=7597655124", where "cloud-storage.com / data / ct / mdr_1.dat" is the location of the medical data records MDR, MDR.j, MDR.k, MDR.l, and "7597655124" is the authorization token. Instead of the "http" (abbreviation for "hypertext transfer protocol") scheme, other schemes can be used, for example, the "https" (abbreviation for "hypertext transfer protocol secure") scheme or the "ftp" (abbreviation for "file transfer protocol") scheme can be used.
[0247] Alternatively, the uniform resource locator URL may be "http: / / cloud-storage.com?mdr=3694721586&auth=7597655124", wherein "3694721586" is the location of the medical data record MDR, MDR.j, MDR.k, MDR.l and "7597655124" is the authorization token. In this case, the location of the medical data record MDR, MDR.j, MDR.k, MDR.l is not equal to the location of the medical data record MDR, MDR.j, MDR.k, MDR.l in the file system of the repository or storage unit PS.MU, but is a string (in particular a hash) that must be mapped by the storage unit PS.MU or the repository to the location of the medical data record MDR, MDR.j, MDR.k, MDR.l in the file system of the repository or storage unit PS.MU if the medical data record MDR, MDR.j, MDR.k, MDR.l should be accessed. This mapping may be accomplished with the aid of a list that stores associations between strings or hashes and corresponding locations in the file system.
[0248] In this embodiment, the authorization token is based on the medical data record MDR, MDR.j, MDR.k, MDR.l by being specific to the medical data record MDR, MDR.j, MDR.k, MDR.l, which means that the authorization token can only be used to access exactly one medical data record MDR, MDR.j, MDR.k, MDR.l and not the other medical data records MDR, MDR.j, MDR.k, MDR.l. For example, the authorization token may be associated with a hash H(MDR), H(MDR) of the medical data record MDR, MDR.j, MDR.k, MDR.l. 1 / 2 (MDR.j), H 1 / 2 (MDR.k), H 1 / 2(MDR.1) is the same. Alternatively, the correspondence between the medical data records MDR, MDR.j, MDR.k, MDR.1 (or the location of the medical data records MDR, MDR.j, MDR.k, MDR.1) and the authorization token can be stored in a database or in a list in the storage unit PS.MU or repository. In the latter case, the step of storing the STR-MDR medical data records MDR, MDR.j, MDR.k, MDR.1 or the step of determining the DET-URL uniform resource locator URL includes determining the authorization token and storing the authorization token in the list.
[0249] Alternatively, the authorization token may also be identical to the file name or the file name and the path of the medical data record MDR, MDR.j, MDR.k, MDR.l in the repository. In the example case, the authorization token would be "mdr_1.dat" or "data / ct / mdr_1.dat". In other words, there is no list of medical data records MDR, MDR.j, MDR.k, MDR.l stored in the storage unit PS.MU and / or the repository, and in order to access a specific medical data record MDR, MDR.j, MDR.k, MDR.l, its file name and / or its path as well as its file name must be known.
[0250] Alternatively, the uniform resource locator URL may be an HTTP GET request or an HTTP POST request. For example, the uniform resource locator URL may be the following HTTP GET request:
[0251] GET / get_data.php? mdr=3694721586&auth=7597655124HTTP / 1.1
[0252] Host: cloud-storage.com
[0253] Here, "3694721586" is the location of the medical data records MDR, MDR.j, MDR.k, MDR.l, and "7597655124" is the authorization token. The same location of the medical data records MDR, MDR.j, MDR.k, MDR.l and the same authorization token are included in the following HTTP POST request:
[0254] POST / get_data.php HTTP / 1.1
[0255] Host: cloud-storage.com
[0256] Content-Type: application / x-www-form-urlencoded
[0257] Content-Length: 30
[0258] mdr=3694721586&auth=7597655124
[0259] The fourth step of the embodiment shown is to provide the PROV-URL uniform resource locator URL to the patient PAT using the interface PS.IF. Specifically, the uniform resource locator URL is sent from the interface S.IF of the server to the patient client PC, in particular to the interface PC.IF of the patient client PC.
[0260] In this embodiment, the server S is a web server and the patient client PC is a mobile device of the patient PAT, in particular a smartphone. The smartphone hosts an application (app) that can be used to process different uniform resource locator URLs of different medical data records MDR, MDR.j, MDR.k, MDR.l of the patient PAT. The server S uses push messages to include the additional uniform resource locator URLs into the application, alternatively, the server S can send a message, such as SMS (abbreviation for "Short Message Service"), MMS (abbreviation for "Multimedia Message Service") or email, containing the uniform resource locator URL to the smartphone. A method for providing the uniform resource locator URL can also be used, for example, by displaying the uniform resource locator URL as a one-dimensional or two-dimensional code (e.g., barcode, QR code, matrix code, Aztec code) on a display device of the server S, so that the uniform resource locator URL can be retrieved by capturing an image of the one-dimensional or two-dimensional code and by decoding the one-dimensional or two-dimensional code contained in the image.
[0261] Figure 2 A flow chart showing a second embodiment of a method for providing a PROV-URL uniform resource locator URL is shown. Optional steps are marked using dashed lines.
[0262] The second embodiment of the method for providing a PROV-URL uniform resource locator URL includes all the steps of the first embodiment of the method for providing a PROV-URL uniform resource locator URL. Specifically, the steps of receiving REC-MDR medical data records MDR, MDR.j, MDR.k, MDR.l, storing STR.MDR medical data records MDR, MDR.j, MDR.k, MDR.l, determining a DET-URL uniform resource locator URL, and providing a PROV-URL uniform resource locator URL may include the steps of the first embodiment and / or Figure 1 All features and alternative embodiments described.
[0263] The second embodiment comprises the following steps: receiving the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE REC-AEID via the interface PS.IF, wherein the authorized entity AE is allowed to access the medical data records MDR, MDR.j, MDR.k, MDR.1, wherein the uniform resource locator URL is based on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. Specifically, the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE can be sent by the patient client PC to the server S, in particular to the interface of the server S.
[0264] In this embodiment, the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE is a string variable identifying the authorized entity AE. The string variables related to the medical data records MDR, MDR.j, MDR.k, MDR.1 can be stored in a database of the storage unit PS.MU, in particular in the repository. In particular, the storage unit PS.MU can store a list of medical data records MDR, MDR.j, MDR.k, MDR.1 stored in the storage unit PS.MU and / or the repository, and for each medical data record MDR, MDR.j, MDR.k, MDR.1, one or more string variables are used for one or more authorized entities AE.
[0265] For example, the first authorized entity AE may have an identifier "57458415", and the second authorized entity AE may have an identifier "71497388". Then, the uniform resource locator URL of the first authorized entity AE may be "http: / / cloud-storage.com / data / ct / mdr_1.dat?auth=7597655124&eid=57458415", and the uniform resource locator URL of the second authorized entity AE may be "http: / / cloud-storage.com / data / ct / mdr_1.dat?auth=7597655124&eid=71497388". By including the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entities AE in the uniform resource locator URL, it can be determined which authorized entity AE has accessed the medical data record.
[0266] In this embodiment, the same identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE can be used for different medical data records MDR, MDR.j, MDR.k, MDR.1. Alternatively, different identifiers AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE can also be used for different medical data records MDR, MDR.j, MDR.k, MDR.1. In particular, it is not necessary for the present invention that the uniform resource locator URL comprises the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE or that the uniform resource locator URL is based on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE.
[0267] Alternatively, the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE may also be based on a digital certificate. Specifically, the digital certificate may be signed by a certification authority. Specifically, the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE may include a digital certificate.
[0268] The second embodiment further comprises the step of determining DET-CI permission information CI, CI.j, CI.k, CI.1, wherein the permission information CI, CI.j, CI.k, CI.1 relates to the permission of the patient PAT to the authorized entity AE to use the medical data record MDR, MDR.j, MDR.k, MDR.1, and wherein the permission information CI, CI.j, CI.k, CI.1 is based on the medical data record MDR, MDR.j, MDR.k, MDR.1 and / or on an identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. The second embodiment further comprises the step of receiving REC-PI1 a first identifier PID1 of the patient PAT using the interface PS.IF, wherein the permission information CI, CI.j, CI.k, CI.1 is also based on the first identifier PID1 of the patient PAT. The second embodiment further comprises the following steps: using the interface PS.IF to receive REC-UI usage information UI, UI.j, UI.k, UI.1, wherein the license information CI, CI.j, CI.k, CI.1 is also based on the usage information UI, UI.j, UI.k, UI.1.
[0269] In this embodiment, the permission information CI, CI.j, CI.k, CI.1 includes the hashes H(MDR), H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data records MDR, MDR.j, MDR.k, MDR.l and the signatures SGN(H(MDR)&AEID, PRK) of the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, and is signed using the first identifier PID1 which is the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT, and the signatures are represented as permission signatures CSGN, CSGN.j, CSGN.k, CSGN.l. In this case, the authorization information CI, CI.j, CI.k, CI.1 is based on both the medical data record MDR, MDR.j, MDR.k, MDR.l and the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE. The operator "&" represents the concatenation of the hash H(MDR), H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data record MDR, MDR.j, MDR.k, MDR.l and the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, and if both are given as strings, the operator "&" can be interpreted as the concatenation of strings, alternatively, if both are given as numbers, the operator "&" can be interpreted as the addition of numbers. Alternatively, the authorization information CI, CI.j, CI.k, CI.1 may also comprise a hash H(MDR), H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data records MDR, MDR.j, MDR.k, MDR.l and a separate signature of the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE. Alternatively, the permission information CI, CI.j, CI.k, CI.1 may include a (permission) signature SGN(H(MDR), PRK) based only on the medical data record MDR, MDR.j, MDR.k, MDR.l, which signature SGN(H(MDR), PRK) is, for example, a signature of a hash H(MDR), H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data record MDR, MDR.j, MDR.k, MDR.l signed using the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT. This situation can be interpreted as the patient PAT giving permission to each entity to use the medical data record MDR, MDR.j, MDR.k, MDR.l.Alternatively, the permission information CI, CI.j, CI.k, CI.1 may include a (permission) signature SGN(AEID, PRK) based only on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. This situation may be interpreted as the patient PAT granting the authorized entity AE permission to access each medical data record MDR, MDR.j, MDR.k, MDR.1 related to the patient PAT.
[0270] In this embodiment, the first identifier PID1 of the patient PAT is the first public key PAT.PBK1, PAT.j.PBK1, PAT.k.PBK1, PAT.1.PBK1 associated with the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1, and the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 is used to sign the medical data record MDR, MDR.j, MDR.k, MDR.l, and / or to sign on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. The license information CI, CI.j, CI.k, CI.1 then comprises the license signature CSGN, CSGN.j, CSGN.k, CSGN.1 and the first public key PAT.PBK1, PAT.j.PBK1, PAT.k.PBK1, PAT.1.PBK1. Alternatively, the first identifier PID1 of the patient PAT receiving the REC-PI1 is the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT. Alternatively, the license information CI, CI.j, CI.k, CI.1 can also be determined on the patient client PC, in which case the first identifier PID1 of the patient PAT can be identified using the license information CI, CI.j, CI.k, CI.1 itself.
[0271] In this embodiment, the usage information UI, UI.j, UI.k, UI.l includes both the usage type and the usage compensation. The usage type can take the exemplary values or labels "diagnosis", "reference" or "training" or any combination of these labels. If the label "diagnosis" is set, the patient PAT gives its permission: the medical data records MDR, MDR.j, MDR.k, MDR.1 are used for diagnostic purposes. If the label "reference" is used, the patient PAT gives its permission: the medical data records MDR, MDR.j, MDR.k, MDR.1 can be used as a reference case for the doctor. If the label "training" is used, the patient PAT gives its permission: the medical data records MDR, MDR.j, MDR.k, MDR.1 are used for training in the machine learning algorithm. In particular, there can be different usage compensations for different usage types.
[0272] In this embodiment, the usage information UI, UI.j, UI.k, UI.1 may be a smart contract. The first account is associated with an entity using the medical data record MDR, MDR.j, MDR.k, MDR.1, and wherein the second account is associated with a first identifier PID1 of the patient PAT and / or with a second identifier PID2 of the patient PAT.
[0273] The second embodiment further comprises the step of recording the DOC-CI license information CI, CI.j, CI.k, CI.1 in the distributed licensed ledger CLDG by the computing unit PS.CU. In this embodiment, the step of recording the DOC-CI license information CI, CI.j, CI.k, CI.1 is performed by inserting further data blocks CDB.i, ..., CDB.1 into the distributed licensed ledger CLDG, wherein the further data blocks CDB.i, ..., CDB.1 comprise the license information CI, CI.j, CI.k, CI.1. The further data blocks CDB.i, ..., CDB.1 may indeed contain a plurality of license information CI, CI.j, CI.k, CI.1 or other data in addition to the license information CI, CI.j, CI.k, CI.1. The computing unit PS.CU may also record the DOC-CI license information CI, CI.j, CI.k, CI.1 in the distributed license ledger CLDG by sending the license information CI, CI.j, CI.k, CI.1 to another computing unit which creates further data blocks CDB.i, ..., CDB.1 and inserts the further data blocks CDB.i, ..., CDB.1 into the distributed license ledger CLDG and by verifying that the further data blocks CDB.i, ..., CDB.1 containing the license information CI, CI.j, CI.k, CI.1 are validly inserted into the distributed license ledger CLDG.
[0274] The second embodiment also includes the following steps: using the interface PS.IF to receive the second identifier PID2 of the REC-PI2 patient PAT; using the computing unit PS.CU to determine the DET-OI ownership information OI, OI.j, OI.k, OI.1, wherein the ownership information OI, OI.j, OI.k, OI.1 includes ownership signatures OSGN, OSGN.j, OSGN.1, OSGN.l based on the medical data records MDR, MDR.j, MDR.k, MDR.1, wherein the ownership signatures OSGN, OSGN.j, OSGN.1, OSGN.l are signed using the second identifier PID2 of the patient PAT; and using the computing unit PS.CU to record the DOC-OI ownership information OI, OI.j, OI.k, OI.1 in the distributed ownership ledger OLDG.
[0275] In this embodiment, the second identifier PID2 of the patient PAT comprises a pair of second private keys PAT.PRK1, PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 and a second public key PAT.PBK2, PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2, and the ownership information OI, OI.j, OI.k, OI.1 comprises a hash H(MDR), H2(MDR.j), H2(MDR.j), H2(MDR.1) of the medical data records MDR, MDR.j, MDR.k, MDR.l. (MDR.j) and ownership signatures OSGN, OSGN.j, OSGN.1, OSGN.l, wherein the ownership signatures OSGN, OSGN.j, OSGN.l, OSGN.l are signatures of the hashes H(MDR), H2(MDR.j), H2(MDR.j), H2(MDR.j) of the medical data records MDR, MDR.j, MDR.k, MDR.1 with the second private key PAT.PRK2, PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 of the second identifier PID2 of the patient PAT.
[0276] In this embodiment, the first identifier PID1 of the patient PAT is a first public key PAT.PBK1, PAT.j.PBK1, PAT.k.PBK1, PAT.1.PBK1 associated with a first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1, and the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 is used to sign the medical data record MDR, MDR.j, MDR.k, MDR.l and / or to sign the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. The license information CI, CI.j, CI.k, CI.1 then comprises the license signatures CSGN, CSGN.j, CSGN.k, CSGN.1 and the first public keys PAT.PBK2, PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2. Alternatively, the first identifier PID1 of the patient PAT for which REC-PI1 is received is the first private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT. Alternatively, the license information CI, CI.j, CI.k, CI.1 can also be determined on the patient client PC, in which case the first identifier PID1 of the patient PAT can be identified using the license information CI, CI.j, CI.k, CI.1 itself.
[0277] In this embodiment, the step of recording the DOC-OI ownership information OI.j, OI.k, OI.l is performed by inserting further data blocks ODB.i, ..., ODB.l into the distributed ownership ledger OLDG, wherein the further data blocks ODB.i, ..., ODB.l include the ownership information OI.j, OI.k, OI.l. The further data blocks ODB.i, ..., ODB.l may indeed contain a plurality of ownership information OI.j, OI.k, OI.l or other data in addition to the ownership information OI.j, OI.k, OI.l. The computing unit S.CU may also record the DOC-OI ownership information OI.j, OI.k, OI.l in the distributed ownership ledger OLDG by sending the ownership information OI.j, OI.k, OI.l to another computing unit which creates further data blocks ODB.i, ..., ODB.l and inserts the further data blocks ODB.i, ..., ODB.l into the distributed ownership ledger OLDG and by verifying that the further data blocks ODB.i, ..., ODB.l containing the ownership information OI.j, OI.k, OI.l are validly inserted into the distributed ownership ledger OLDG.
[0278] Figure 3 Data blocks CDB.i, ..., CDB.1, showing an implementation of a distributed permissioned ledger CLDG Figure 4 Data blocks ODB.i, ..., ODB.1 of an embodiment of a distributed ownership ledger OLDG are shown. In these embodiments, both the distributed permission ledger CLDG and the distributed ownership ledger OLDG are blockchains. Alternatively, the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG may have a tree structure or a directed acyclic graph structure (another name is "tangle"). The distributed permission ledger CLDG and the distributed ownership ledger OLDG do not have to have the same structure. In particular, the distributed permission ledger CLDG and the distributed ownership ledger OLDG may be the same. In addition, both the distributed permission ledger CLDG and the distributed ownership ledger OLDG may contain other data blocks that do not store permission information CI.j, CI.k, CI.l or ownership information OI.j, OI.k, OI.l.
[0279] The data blocks CDB.j, ..., CDB.1 of the distributed permission ledger CLDG include permission information CI.j, ..., CI.1 of the previous data blocks CDB.j, ..., CDB.1 of the distributed permission ledger CLDG, timestamps CTS.j, ..., CTS.1, random numbers CRN.j, ..., CRN.1, and hashes H(CDB.i), ..., H(CDB.k). The data blocks ODB.j, ..., ODB.1 of the distributed ownership ledger OLDG include ownership information OI, OI.j, ..., OI.1 of the previous data blocks ODB.j, ..., ODB.1 of the distributed ownership ledger OLDG, timestamps OTS.j, ..., OTS.1, random numbers ORN.j, ..., ORN.1, and hashes H(ODB.i), ..., H(ODB.k).
[0280] Specifically, the data blocks CDB.j, ..., CDB.1 of the distributed permission ledger CLDG may include multiple permission information CI.j, ..., CI.1 related to different medical data records MDR.j, MDR.k, MDR.1. Different medical data records MDR.j, MDR.k, MDR.1 may be related to different patient PATs, but different medical data records MDR.j, MDR.k, MDR.1 may also be related to the same patient PAT. In particular, the data blocks ODB.j, ..., ODB.1 of the distributed ownership ledger OLDG may include multiple ownership information OI.j, ..., OI.1 related to different medical data records MDR.j, MDR.k, MDR.1. Different medical data records MDR.j, MDR.k, MDR.l may be related to different patient PATs, but different medical data records MDR.j, MDR.k, MDR.l may also be related to the same patient PAT.
[0281] In this embodiment of the distributed permission ledger CLDG, the permission information CI.j, CI.k, CI.1 comprises: the hash H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data record MDR.j, MDR.k, MDR.l, the usage information UI.j, UI.k, UI.l and the permission signature CSGN.j, CSGN.k, CSGN.l. In addition, the permission information CI.j, CI.k, CI.1 comprises the first public key PAT.j.PBK1, ..., PAT.1.PBK1 of the patient PAT which is the subject of the respective medical data record MDR.j, MDR.k, MDR.l. In this embodiment, the permission signature is calculated as follows:
[0282] CSGN.j=SGN(H1(MDR.j)&AEID.j、PAT.j.PRK1)
[0283] CSGN.k=SGN(H1(MDR.k)&AEID.k、PAT.k.PRK1)
[0284] CSGN.1=SGN(H1(MDR.l)&AEID.l、PAT.1.PRK1)
[0285] In other words, the permission signatures CSGN.j, CSGN.k, CSGN.l are based on the cascade of the hashes H1(MDR.j), H1(MDR.j), H1(MDR.j) of the medical data records MDR.j, MDR.k, MDR.l and the identifiers AEID.j, AEID.k, AEID.l of the corresponding authorized entities AE; and the permission signatures CSGN.j, CSGN.k, CSGN.1 are signed using the first private key PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT related to the medical data records MDR.j, MDR.k, MDR.1 (which corresponds to the first public key PAT.j.PBK1,..., PAT.1.PBK1 of the patient PAT). Alternatively, the permission signatures CSGN.j, CSGN.k, CSGN.1 may be based on a concatenation of the hashes H1(MDR.j), H1(MDR.k), H1(MDR.1) of the medical data records MDR.j, MDR.k, MDR.1, the identifiers AEID.j, AEID.k, AEID.1 of the respective authorized entities AE and the usage information:
[0286] CSGN.j=SGN(H1(MDR.j)&AEID.j&UI.j、PAT.j.PRK1)
[0287] CSGN.k=SGN(H1(MDR.k)&AEID.k&UI.k、PAT.k.PRK1)
[0288] CSGN.1=SGN(H1(MDR.l)&AEID.l&UI.l、PAT.1.PRK1)
[0289] Furthermore, the permission signatures CSGN.j, CSGN.k, CSGN.1 can also be based on a concatenation with the first public key PAT.j.PBK1, . . . , PAT.1.PBK1 of the patient PAT which is the subject of the respective medical data record MDR.j, MDR.k, MDR.1.
[0290] Specifically, the usage information UI.j, UI.k, UI.1 may include the use of the medical data records MDR.j, MDR.k, MDR.1 permitted by the patient PAT. For example, the usage information UI.j, UI.k, UI.l may include an array of strings or other variables indicating the permitted usage types, for example, ["train_ai", "reference"], which is used to indicate that the medical data records MDR.j, MDR.k, MDR.1 can be used to train artificial intelligence algorithms, or can be used as reference cases for similar cases. Alternatively, the usage information UI.j, UI.k, UI.l may also be a string, such as "train_ai / reference". Alternatively, the usage information UI.j, UI.k, UI.l may be an integer representing a specific use (for example, 0 for no use, 1 for "train_ai", 2 for "reference", and 3 for "train_ai" / reference").
[0291] In this embodiment of the ownership permission ledger OLDG, the ownership information OI.j, OI.k, OI.1 includes the hashes H2(MDR.j), H2(MDR.k), H2(MDR.1) of the medical data records MDR.j, MDR.k, MDR.1 and the ownership signatures OSGN.j, OSGN.k, OSGN.1. In this embodiment, the ownership signatures OSGN.j, OSGN.1, OSGN.1 are calculated as follows:
[0292] OSGN.j=SGN(H2(MDR.j),PAT.j.PRK2)
[0293] OSGN.k=SGN(H2(MDR.k),PAT.k.PRK2)
[0294] OSGN.1=SGN(H2(MDR.l),PAT.1.PRK2)
[0295] In other words, the ownership signatures OSGN.j, OSGN.k, OSGN.1 are based on the hashes H2(MDR.j), H2(MDR.k), H2(MDR.l) of the medical data records MDR.j, MDR.k, MDR.l; and the ownership signatures OSGN.j, OSGN.k, OSGN.1 are signed using the second private keys PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 of the patient PAT associated with the medical data records MDR.j, MDR.k, MDR.l. In a preferred embodiment, the ownership information OI.j, OI.k, OI.1 may also include a second public key PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2 of the patient PAT, wherein the second public key PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2 and the second private key PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 form an asymmetric key pair. The account of the patient PAT is identified by the second public key PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2. In addition, the second public key PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2 may also be included in the ownership signature OSGN.j, OSGN.k, OSGN.1.
[0296] It must be understood that Figure 3 and Figure 4 The permission information CI.j, CI.k, CI.l and ownership information OI.j, OI.k, OI.l shown in are only some implementations of the permission information CI.j, CI.k, CI.l and ownership information OI.j, OI.k, OI.1 contained in the distributed permission ledger CLDG and the distributed ownership ledger OLDG. Figure 3 and Figure 4 Compared with the license information CI.j, CI.k, CI.l and the ownership information OI.j, OI.k, OI.l shown in , both the license information CI.j, CI.k, CI.l and the ownership information OI.j, OI.k, OI.l may contain additional data or less data.
[0297] In these embodiments of the distributed permission ledger CLDG and the distributed ownership ledger OLDG, the hashes H1(MDR.j), H1(MDR.k), H1(MDR.l) contained in the permission information CI.j, CI.k, CI.l (which are equal to the hashes H1(MDR.j), H1(MDR.k), H1(MDR.l) on which the permission signatures CSGN.j, CSGN.k, CSGN.l are based) are equal to the hashes H2(MDR.j), H2(MDR.k), H2(MDR.l) contained in the ownership information OI.j, OI.k, OI.l (which are equal to the hashes H2(MDR.j), H2(MDR.k), H2(MDR.l) on which the ownership signatures OSGN.j, OSGN.k, OSGN.1 are based). Alternatively, the hashes H1(MDR.j), H1(MDR.k), H1(MDR.1) contained in the license information CI.j, CI.k, CI.1 may be different from the hashes H2(MDR.j), H2(MDR.k), H2(MDR.l) contained in the ownership information OI.j, OI.k, OI.l. Specifically, different seeds or different hash functions may be used to calculate the hashes H1(MDR.j), H1(MDR.k), H1(MDR.1) and the hashes H2(MDR.j), H2(MDR.k), H2(MDR.l).
[0298] In these embodiments of the distributed permission ledger CLDG and the distributed ownership ledger OLDG, the first private key PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT and the second private key PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 of the patient PAT are different. Alternatively, the first private key PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 of the patient PAT and the second private key PAT.j.PRK2, PAT.k.PRK2, PAT.1.PRK2 of the patient PAT may be the same.
[0299] In this embodiment, the timestamps CTS.j, ..., CTS.1, OTS.j, ..., OTS.1 of the data blocks CDB.j., ..., CDB.1, ODB.j, ..., ODB.1 are the creation times of the data blocks CDB., ..., CDB.1, ODB.j, ..., ODB.1. Alternatively, the timestamps CTS.j, ..., CTS.1, OTS.j, ..., OTS.1 of CDB.j., ..., CDB.1, ODB.j, ..., ODB.1 may be the creation times of the license information CI.j, ..., CI.1 or the ownership information OI.j, ..., OI.1 contained in the data blocks CDB.j., ..., CDB.1, ODB.j, ..., ODB.1.
[0300] In general, the random numbers CRN.j, ..., CRN.1, ORN.j, ..., ORN.1 are data items that can be arbitrarily selected by the creator of the data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.j without affecting the actual content of the data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.j. In particular, the use and / or content of the license information CI.j, ..., CI.1 and the use and / or content of the ownership information OI.j, ..., OI.1 are not affected by the selection of the random numbers CRN.j, ..., CRN.1, ORN.j, ..., ORN.1. Typically, changing the random numbers CRN.j, ..., CRN.1, ORN.j, ..., ORN.l also changes the hashes H(CDB.i), ..., H(CDB.k), H(ODB.i), ..., H(ODB.k) of the data blocks CDB.i, ..., CDB.l, ODB.i, ..., ODB.j.
[0301] In these embodiments of the distributed permission ledger CLDG and the distributed ownership ledger OLDG, for each data block CDB.j, ..., CDB.1 of the distributed permission ledger CLDG associated with the medical data record MDR.j, MDR.k, MDR.1, there is a corresponding data block ODB.i, ..., ODB.j of the distributed ownership ledger OLDG associated with the same medical data record MDR.j, MDR.k, MDR.1. In general, there may be data blocks CDB.j, ..., CDB.1 of the distributed permission ledger CLDG associated with the medical data record MDR.j, MDR.k, MDR.1, but there may not be corresponding data blocks ODB.i, ..., ODB.j of the distributed ownership ledger OLDG associated with the same medical data record MDR.j, MDR.k, MDR.1, or there may be two or more corresponding data blocks ODB.i, ..., ODB.j of the distributed ownership ledger OLDG associated with the same medical data record MDR.j, MDR.k, MDR.1. Typically, there may be data blocks ODB.i, ..., ODB.j of a distributed ownership ledger OLDG associated with medical data records MDR.j, MDR.k, MDR.l, but there may not be corresponding data blocks CDB.j, ..., CDB.l of a distributed permission ledger CLDG associated with the same medical data record MDR.j, MDR.k, MDR.l, or there may be two or more corresponding data blocks CDB.j, ..., CDB.l of a distributed permission ledger CLDG associated with the same medical data record MDR.j, MDR.k, MDR.l.
[0302] In particular, in order to insert data blocks CDB.i, ..., CDB.l, ODB.i, ..., ODB.l into the distributed permission ledger CLDG or the distributed ownership ledger OLDG, a consensus algorithm (e.g., proof of work, proof of storage, proof of collateral, proof of elapsed time) must be executed, wherein the consensus algorithm can be based on random numbers CRN.j, ..., CRN.l, ORN.j, ..., ORN.1 of the data blocks CDB.i, ..., CDB.l, ODB.i, ..., ODB.l to be inserted. In this embodiment, the creator of the data blocks CDB.j, ..., CDB.1, ODB.j, ..., ODB.1 must select random numbers CRN.j, ..., CRN.1, ORN.j, ..., ORN.1 so that the hashes H(CDB.j), ..., H(CDB.1), H(ODB.j), ..., H(ODB.1) of the data blocks CDB.j, ..., CDB.1, ODB.j, ..., ODB.1 meet a certain condition. In this embodiment, the condition is that the hashes H(CDB.j), ..., H(CDB.1), H(ODB.j), ..., H(ODB.1) of the data blocks CDB.j, ..., CDB.1, ODB.j, ..., ODB.1 are less than a given threshold.
[0303] In this embodiment, the hashes H(CDB.j) and H(CDB.k) of the data blocks CDB.j and CDB.k of the distributed permissioned ledger CLDG are calculated as follows:
[0304] H(CDB.j)=SHA256(H(CI.j)&H(CDB.i)&CRN.j)
[0305] H(CDB.k)=SHA256(H(CI.k)&H(CDB.j)&CRN.k),
[0306] The SHA256 hash function can be replaced by any other suitable hash function. The operator "&" can be understood as arithmetic addition of numbers or concatenation of strings (by converting numbers into strings before concatenation). In this embodiment, the hash of the license information CI.j, CI.k is calculated as follows:
[0307] H(CI.j)=SHA256[(MDR.j)&H(UI.j)&SGN((MDR.j)&AEID.j,PAT.j.PRK1)]bzw,
[0308] H(CI.k)=SHA256[(MDR.k)&H(UI.k)&SGN((MDR.k)&AEID.k,PAT.k.PRK1)],
[0309] Among them, the SHA256 hash function can be replaced by any other suitable hash function. Specifically, the hashes H1(MDR.j), H1(MDR.k) of the medical data records MDR.j, MDR.k can be the Merkle roots of the medical data records MDR.j, MDR.k. Alternatively, the hashes H(CDB.j), H(CDB.k) of the data blocks CDB.j, CDB.k can also be based on other data items contained in the data blocks CDB.j, CDB.k, in particular based on the timestamps CTS.j, CTS.k of the data blocks CDB.j, CDB.k. Alternatively, the hashes H(CDB.j), H(CDB.k) of the data blocks CDB.j, CDB.k can be based on other items contained in the data blocks CDB.j, CDB.k.
[0310] In this embodiment, the hashes H(ODB.j) and H(ODB.k) of the data blocks ODB.j and ODB.k of the distributed ownership ledger OLDG are calculated as follows:
[0311] H(ODB.j)=SHA256(H(OI.j)&H(ODB.i)&ORN.j)bzw,
[0312] H(ODB.k)=SHA256(H(OI.k)&H(ODB.j)&ORN.k),
[0313] The SHA256 hash function can be replaced by any other suitable hash function. The operator "&" can be understood as arithmetic addition of numbers or concatenation of strings (by converting numbers into strings before concatenation). In this embodiment, the hash of ownership information OI.j, OI.k is calculated as follows:
[0314] H(OI.j)=SHA256[(MDR.j)&SGN((MDR.j),PAT.j.PRK2)],
[0315] H(OI.k)=SHA256[(MDR.k)&SGN((MDR.k),PAT.k.PRK2)],
[0316] Among them, the SHA256 hash function can be replaced by any other suitable hash function. Specifically, the hashes H2(MDR.j), H2(MDR.k) of the medical data records MDR.j, MDR.k can be the Merkle roots of the medical data records MDR.j, MDR.k. Alternatively, the hashes H(ODB.j), H(ODB.k) of the data blocks ODB.j, ODB.k can also be based on other data items contained in the data blocks ODB.j, ODB.k, in particular based on the timestamps OTS.j, OTS.k of the data blocks ODB.j, ODB.k. Alternatively, the hashes H(ODB.j), H(ODB.k) of the data blocks ODB.j, ODB.k can be based on other items contained in the data blocks ODB.j, ODB.k.
[0317] exist Figure 3 and Figure 4 In the figure, only a subset of data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.1 of the distributed permission ledger CLDG and the distributed ownership ledger OLDG are shown, and in addition, the contents of data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.1 are only shown for a subset of data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.1. In general, the distributed permission ledger CLDG and the distributed ownership ledger OLDG may contain additional data blocks and additional items of data blocks, and the data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.1 may be linked to these additional data blocks.
[0318] In addition, the distributed permission ledger CLDG and the distributed ownership ledger OLDG are Figure 3 and Figure 4Alternatively, the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG may be implemented as a tree of blocks, which means that there may be several data blocks CDB.i, ..., CDB.1, ODB.i, ..., ODB.1 containing hashes H(CDB.i), ..., H(CDB.k), H(ODB.i), ..., H(ODB.k) of certain data blocks CDB.i, ..., CDB.k, ODB.i, ..., ODB.k. Alternatively, the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG can be implemented as a tangle, which means that each data block CDB.i, ..., CDB.1, ODB.i, ..., ODB.l can contain an arbitrary number of hashes H(CDB.i), ..., H(CDB.k), H(ODB.i), ..., H(ODB.k) of certain other data blocks CDB.i, ..., CDB.k, ODB.i, ..., ODB.k. In other words, the tangle has the structure of a directed acyclic graph. Specifically, each data block CDB.i, ..., CDB.1, ODB.i, ..., ODB.l can contain a fixed number of hashes H(CDB.i), ..., H(CDB.k), H(ODB.i), ..., H(ODB.k) of certain other data blocks CDB.i, ..., CDB.k, ODB.i, ..., ODB.k, in particular, the fixed number can be 2.
[0319] Figure 5 A flow chart showing an embodiment of a method for storing STR-MDR medical data records MDR, MDR.j, MDR.k, MDR.l using a storage unit PS.MU is shown. In addition to the steps of determining a DET-URL and providing a PROV-URL uniform resource locator URL, the embodiment shown includes a method for providing a PROV-URL Figure 2 All steps of the second embodiment of the method for uniform resource locator URL shown in . The remaining steps may include all advantageous and / or alternative features and / or embodiments of the various steps of the second embodiment. Figure 2 Steps marked as optional in FIG. 1 are also optional in this embodiment.
[0320] The method shown for storing STR-MDR medical data records MDR, MDR.j, MDR.k, MDR.l can be used to store STR-MDR medical data records MDR, MDR.j, MDR.k, MDR.l and authorize access to medical data records MDR, MDR.j, MDR.k, MDR.l without requiring necessary interaction by the user. Specifically, in this embodiment, the step of providing a PROV-URL uniform resource locator URL is not performed.
[0321] Figure 6 A first embodiment of the entire data flow between the patient client PC, the server S and the user client UC is shown. Specifically, the patient client PC and the server S may be included in the providing system PS, and the server S and / or the user client UC may be included in the using system US.
[0322] In this embodiment, the medical data record MDR may be sent from the patient client PC to the server S, and / or the medical data record MDR may be sent from the server S to the patient client PC. Alternatively, a hash H(MDR) of the medical data record MDR may be sent from the patient client PC to the server S, and / or a hash H(MDR) of the medical data record MDR may be sent from the server S to the patient client PC.
[0323] The uniform resource locator URL is based on the medical data record MDR and is sent from the server S to the patient client PC. Specifically, the uniform resource locator URL can be used to access the medical data record MDR stored in the server S.
[0324] Now, the patient PAT can share access to the medical data record MDR by providing the uniform resource locator URL to the requesting entity RE, in particular by sending the uniform resource locator URL from the patient client PC to the user client UC associated with the requesting entity RE. In particular, the requesting entity RE can be a doctor of the patient PAT who can use the medical data record MDR for diagnostic purposes.
[0325] The requesting entity RE may access the medical data record MDR by issuing an access request AR (which is based on a uniform resource locator URL) and sending the access request AR to a server S. The server S then identifies the medical data record MDR based on the access request AR and provides the medical data record MDR to the requesting entity RE, in particular to a user client UC of the requesting entity RE.
[0326] Figure 7 The second embodiment of the entire data flow between the patient client PC, the server S and the user client UC is shown. The second embodiment is based on the first embodiment of the entire data flow, and further includes a distributed ownership ledger OLDG and a distributed permission ledger CLDG, wherein both the patient client PC and the server S can access the distributed permission ledger CLDG and the distributed ownership ledger OLDG, or interact with the distributed permission ledger CLDG and the distributed ownership ledger OLDG.
[0327] In this second embodiment, there is a first identifier PID1 of the patient PAT comprising a first private key PAT.PRK1 and an associated first public key PAT.PBK1, and there is a second identifier PID2 comprising a second private key PAT.PRK2 and an associated second public key PAT.PBK2.
[0328] In this embodiment, the patient client PC receives the medical data record MDR from the server S, wherein the medical data record MDR is uploaded to the server S by the entity that created the medical data record MDR. Alternatively, the patient client PC may also directly receive the medical data record MDR without the intervention of the server S. Alternatively, the patient client PC may receive a hash H(MDR) of the medical data record MDR from the server S.
[0329] In this embodiment, the patient client PC determines DET-CI, DET-OI permission information CI and / or ownership information OI by optionally calculating a hash H(MDR) of the medical data record MDR (if the patient client PC receives the medical data record MDR instead of the hash H(MDR) of the medical data record MDR) and optionally creating a signature by signing with its first private key PAT.PRK1 and / or its second private key PAT.PRK2, wherein the signature is included in the permission information CI and / or the ownership information OI. In addition, the patient client PC directly records DOC-CI, DOC-OI ownership information OI in the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG.
[0330] If the patient client PC does not receive the medical data record MDR from the server S, the patient client PC also sends the medical data record MDR to the server S.
[0331] In this second embodiment, the server S may perform checks CHK-1, CHK-2, CHK-3 based on the access request AR (requesting whether the server S is allowed to provide the medical data record MDR to the user client UC). The check may be based on the interaction of the server S with the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG.
[0332] Figure 8 A detailed embodiment of the data exchange between a patient client PC and a server S is shown. The patient client PC and the server S may be part of a provision system PS. In particular, in this embodiment, the permission information CI and the ownership information OI may be created without the server S having access to one of the private keys PAT.PRK1, PAT.PRK2 of the patient PAT and without the need to transfer the medical data record MDR from the server S to the patient client PC.
[0333] In this embodiment, the server S receives the medical data record MDR from a data source (e.g., from a medical device) and calculates a hash H(MDR) of the medical data record MDR. Subsequently, the server S sends the hash H(MDR) of the medical data record MDR to the patient client PC. Optionally, the server Scan additionally sends metadata related to the medical data record MDR to the patient client PC.
[0334] Using the patient client PC, the patient PAT can specify an authorized entity AE that should have access to the medical data record MDR. Specifically, the patient client PC can determine the identifier AEID of the authorized entity AE and send the identifier AEID of the authorized entity to the server S. In addition, optionally, the patient PAT can specify usage information UI for managing the use of the medical data record MDR and send the usage information UI from the patient client PC to the server S.
[0335] In addition, the patient client PC can create a permission signature CSGN and / or an ownership signature OSGN. In this embodiment, the permission signature CSGN is calculated as follows:
[0336] CSGN=SGN(H(MDR)&AEID,PAT.PRK1),
[0337] Specifically, the first private key PAT.PRK1 of the patient PAT is used for signing, and the ownership signature OSGN is calculated as follows:
[0338] OSGN=SGN(H(MDR),PAT.PRK2),
[0339] Specifically, the second private key PAT.PRK2 of the patient PAT is used for signing. In addition, the patient client PC may also provide the first public key PAT.PBK1 and / or the second public key PAT.PBK2 to the server S. The server S determines the license information CI and / or the ownership information OI based on the license signature CSGN and / or the ownership signature OSGN, and records the license information CI and / or the ownership information OI in the distributed license ledger CLDG and / or the distributed ownership ledger OLDG.
[0340] Where not explicitly described, the individual embodiments described with respect to the figures or their various aspects and features may be combined or exchanged with one another without limiting or expanding the scope of the described invention, whenever such a combination or exchange makes sense and is within the meaning of the invention. Where applicable, the advantages described with respect to one embodiment of the invention or with respect to one figure are also advantages of the other embodiments of the invention.
[0341] Fig. 9 A first embodiment of a method for using a uniform resource locator URL provided by a method for providing a uniform resource locator URL is shown.
[0342] The first step of the first embodiment shown is to receive an access request AR from REC-AR pointing to a requested medical data record RMDR through an interface US.IF, wherein the requested medical data record RMDR is stored in a storage unit US.MU, and wherein the access request AR is based on a uniform resource locator URL. In this embodiment, the interface US.IF is an interface of the usage system US, specifically, the interface US.IF can be the same as the interface S.IF of the server S. In addition, the storage unit US.MU is a storage unit US.MU of the usage system, specifically, the storage unit US.MU can be the same as the storage unit S.MU of the server S. Specifically, the storage unit S.MU of the server S can include a repository. Specifically, the usage system US can be the same as the server S.
[0343] In this embodiment, the access request AR is an HTTP GET request or an HTTP POST request based on the uniform resource locator URL. For example, the uniform resource locator URL may be "http: / / cloud-storage.com / data / ct / mdr_1.dat?auth=7597655124", and the access request AR may be the following HTTP GET request:
[0344] GET / data / ct / mdr_1.dat? auth=7597655124HTTP / 1.1
[0345] Host: cloud-storage.com
[0346] Alternatively, the access request AR may be the following HTTP POST request:
[0347] POST / data / ct / mdr_1.dat HTTP / 1.1
[0348] Host:cloud-storage.com
[0349] Content-Type:application / x-www-form-urlencoded
[0350] Content-Length:15
[0351] auth=7597655124
[0352] The second step of the second embodiment shown is to provide the medical data record RMDR requested by the PROV-MDR based on the access request AR using the interface US.IF.
[0353] In this embodiment, the requested medical data record RMDR is provided to the user client UC via an HTTP response as a response to an HTTP GET request or an HTTP POST request. The header of the HTTP response may be, for example:
[0354] HTTP / 1.1 200OK
[0355] Server:Apache / 1.3.29(Unix)PHP / 4.3.4
[0356] Content-Length:123456
[0357] Connection:close
[0358] Content-Type:application / x-tar
[0359] The requested medical data record RMDR is then included in the body of the HTTP response.
[0360] Alternatively, the location of the requested medical data record RMDR may also be included as a query parameter in the uniform resource locator URL. For example, in the uniform resource locator URL "http: / / cloud-storage.com?mdr=3694721586&auth=7597655124", the location of the requested medical data record RMDR is given by the query parameter "mdr=3694721586", and the storage unit US.MU maps the given parameter to the location of the medical data records MDR, MDR.j, MDR.k, MDR.1 in the file system of the storage unit US.MU and / or the repository of the server S. Specifically, in this case, there may be an intermediate HTTP request and response. For example, there may be an HTTP GET request from the user client UC to the storage unit US.MU containing the following data:
[0361] GET / get_data.php? mdr=3694721586&auth=7597655124HTTP / 1.1
[0362] Host:cloud-storage.com
[0363] Server S may answer with the following HTTP response, which resolves the location given as a query parameter to a location in the file system of server S or the repository:
[0364] HTTP / 1.0 302 Found
[0365] Date:Wed,04Apr 2011 15:12:44GMT
[0366] Location:http: / / cloud-storage.com / data / ct / mdr_1.dat
[0367] The user client UC can then initiate another HTTP GET request or HTTP POST request including the authorization token as already described before. Alternatively, the server S can already check the authorization token after the first request and respond with a location in the file system of the storage unit US.MU or repository in case of correct authorization.
[0368] In this embodiment, the access request AR is an HTTP request, and the requested medical data record RMDR is provided by an HTTP response. Alternatively, other protocols may be used to send the access request AR from the user client UC to the server S and / or the storage unit US.MU, and to provide the medical data record RMDR requested by the PROV-MDR to the user client UC via the server S and / or the storage unit US.MU. Examples of such protocols are HTTPS, WebDAV, FTP or other data transmission protocols known to those skilled in the art.
[0369] Fig.10 A second embodiment of a method for using a uniform resource locator URL provided by the method for providing a uniform resource locator URL is shown.
[0370] The second embodiment comprises the steps of receiving a REC-AR access request AR and providing a medical data record RMDR requested by a PROV-MDR, both of which have been described in the context of the first embodiment. The second embodiment may also comprise Fig.10 All advantageous features and embodiments described in the description. All other steps may be considered optional.
[0371] The second step of the second implementation mode is to use the interface MU.IF to receive the identifier of the REC-REID requesting entity RE. Specifically, the identifier of the requesting entity RE is sent by the user client UC.
[0372] In this second embodiment, the identifier of the requesting entity RE is included in the access request AR. Alternatively, the identifier of the requesting entity RE may also be received independently of the access request AR. Specifically, the identifier of the requesting entity RE may be part of a uniform resource locator URL or part of an HTTP request based on a uniform resource locator URL.
[0373] In this second embodiment, the identifier of the requesting entity RE is based on access credentials, in particular, the identifier of the requesting entity RE comprises a shared secret and / or a digital certificate. Alternatively, the identifier of the requesting entity RE may be any data that identifies (in particular uniquely identifies) the requesting entity RE.
[0374] In particular, the identifier of the requesting entity RE may be the same as the authorization token included in the uniform resource locator URL. Specifically, the authorization token may be the same as the shared secret or the result of a function (particularly a hash function) applied to the shared secret. By applying a hash function or other function to the shared secret, an eavesdropper cannot obtain the shared secret by intercepting the communication between the user client UC and the usage system US and / or the server S.
[0375] In the second embodiment shown, the permission information CI, CI.j, ..., CI.k based on the medical data record MDR, MDR.j, MDR.k, MDR.l and based on the identifier of the authorized entity is recorded in the distributed permission ledger CLDG. A further step of the second embodiment shown is to perform a first check CHK-1 using the computing unit US.CU as follows: whether the distributed permission ledger CLDG records the permission information CI, CI.j, ..., CI.k based on the requested medical data record RMDR and based on the identifier of the requesting entity RE.
[0376] In this embodiment, the distributed license ledger CLDG includes license information CI, CI.j, ..., CI.k, wherein each license information CI, CI.j, ..., CI.k includes: a hash H(MDR), H1(MDR.j), ..., H1(MDR.l) of the medical data record MDR, MDR.j, MDR.k, MDR.l, usage information UI, UI.j, ..., UI.l and a license signature CSGN, CSGN.j, ..., CSGN.1, wherein the license signature CSGN, CSGN.j, ..., CSGN.1 is in accordance with the Figure 3 The calculations were performed as described.
[0377] In this embodiment, if there is permission information CI, CI.j, ..., CI.k including hashes H(MDR), H1(MDR.j), H1(MDR.k), H1(MDR.l) of medical data records MDR, MDR.j, MDR.k, MDR.1 and license signatures CSGN, CSGN.j, ..., CSGN.l based on a combination of the hashes H(MDR), H1(MDR.j), H1(MDR.k), H1(MDR.l) of the medical data records MDR, MDR.j, MDR.k, MDR.1 and the identifier of the requesting entity RE, then the permission ledger CLDG records the permission information CI, CI.j, ..., CI.k based on the requested medical data record RMDR and based on the identifier of the requesting entity RE.
[0378] Specifically, in order to perform the first check CHK-1, the system US and / or server S is used to calculate the hash H(RMDR) of the requested medical data record RMDR, and determine all the permission information CI, CI.j,..., CI.1 of the distributed permission ledger CLDG including the hash H(RMDR) of the requested medical data record RMDR.
[0379] In particular, the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE may include: a public key associated with the authorized entity AE, and a signature based on the public key associated with the authorized entity, wherein the signature is signed using the private key of the certification authority. The identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE may alternatively or additionally also include a signature of a data item with a private key associated with the authorized entity (wherein the private key associated with the authorized entity AE and the public key associated with the authorized entity AE form an asymmetric key pair). Specifically, the data item may be created by the use system US and / or the server S and sent to the authorized entity AE, signed by the authorized entity, and sent back to the use system US and / or the server S.
[0380] Specifically, the distributed permission ledger CLDG includes permission information CI, CI.j, ..., CI.k, wherein each permission information CI, CI.j, ..., CI.k includes a permission signature CSGN, CSGN.j, ..., CSGN.1, wherein each permission signature CSGN, CSGN.j, ..., CSGN.1 is based on the corresponding medical data record MDR, MDR.j, ..., MDR.1, and / or based on the corresponding identifier AEID, AEID.j, ..., AEID.k of the authorized entity AE. Specifically, the permission signature CSGN, CSGN.j, ..., CSGN.1 is signed based on the first identifier PID1 of the patient PAT and the corresponding medical data record MDR, MDR.j, ..., MDR.1. Specifically, the first identifier PID1 of the patient includes the first private key PAT.PRK1, PAT.j.PRK1, ..., PAT.1.PRK1 of the patient PAT. A further step of the second embodiment is then to perform a second check CHK-2 as follows: whether the permission signatures CSGN, CSGN.j, ..., CSGN.1 are validly signed based on the first identifier PID1 of the patient PAT, wherein the step of providing PROV-MDR is only performed if the second check is positive.
[0381] In this embodiment, the license signatures CSGN, CSGN.j, ..., CSGN.1 are calculated as follows:
[0382] CSGN.j=SGN(H1(MDR.j)&AEID.j,PAT.j.PRK1)
[0383] CSGN.k=SGN(H1(MDR.k)&AEID.k,PAT.k.PRK1)
[0384] CSGN.l=SGN(H1(MDR.l)&AEID.l,PAT.l.PRK1)
[0385] The license signatures CSGN, CSGN.j, ..., CSGN.1 may then be verified using the signature verification function VRF and the first public key PAT.j.PBK1, ..., PAT.1.PBK1 of the patient PAT.
[0386] VRF(CSGN.j,H1(MDR.j)&AEID.j,PAT.j.PBK1)
[0387] VRF(CSGN.k,H1(MDR.k)&AEID.k,PAT.k.PBK1)
[0388] VRF(CSGN.l,H1(MDR.l)&AEID.l,PAT.l.PBK1)
[0389] The result of the signature verification function is true or false, depending on whether the license signatures CSGN, CSGN.j, ..., CSGN.1 are valid. If the output of the signature verification function is true, the result of the second check is considered positive.
[0390] In this embodiment, in order to calculate the result of the signature verification function, the hashes H(MDR), H1(MDR.j), ..., H1(MDR.j) of the medical data records MDR, MDR.j, ..., MDR.1 and the identifiers AEID, AEID.j, ..., AEID.1 of the authorized entity AE must be known. Both quantities may be contained in the permission information CI.j, ..., CI.1 or may be contained in the access request AR. In particular, the identifiers AEID, AEID.j, ..., AEID.1 of the authorized entity AE may be replaced by the identifiers of the requesting entity RE, so that it is possible to simultaneously check whether the requesting entity RE is the authorized entity AE.
[0391] In this embodiment, there is a step of performing a third check CHK-3 using the computing unit US.CU. Specifically, the access request AR includes the expected usage information, and in performing the third check CHK-3, the stored usage information UI, UI.j, UI.k, UI.l is determined based on the distributed permission ledger CLDG. Specifically, the usage information UI.j, UI.k, UI.l is recorded in the distributed permission ledger CLDG associated with the medical data record MDR, MDR.j, MDR.k, MDR.l, in particular by being included in the same permission information CI, CI.j, CI.k, CI.l as the relevant medical data record MDR, MDR.j, MDR.k, MDR.l, and the determined stored usage information UI, UI.j, UI.k, UI.1 is the usage information UI, UI.j, UI.k, UI.l associated with the requested medical data record RMDR. Specifically, performing the third check CHK-3 includes: determining whether the expected usage information matches the stored usage information UI, UI.j, UI.k, UI.l. Specifically, if the expected usage information is equal to the stored usage information UI, UI.j, UI.k, UI.1, or if the expected usage information is a subset of the stored usage information UI, UI.j, UI.k, UI.1, the expected usage information matches the stored usage information UI, UI.j, UI.k, UI.1.
[0392] For example, the stored usage information UI, UI.j, UI.k, UI.1 may be "train_ai", indicating that the corresponding medical data records MDR, MDR.j, MDR.k, MDR.l have been authorized to be used for training the artificial intelligence algorithm, and the expected usage information may also be "train_ai", so that the stored usage information UI, UI.j, UI.k, UI.l matches the expected usage information. In contrast, if the expected usage information is "reference", indicating that the requested medical data record RMDR should be used as a reference case, the expected usage information will not match the stored usage information UI, UI.j, UI.k, UI.1 "train_ai", and the result of the third check is negative. This will also be the case if the expected usage information is "reference / train_ai", indicating that the requested medical data record RMDR should all be used as a reference for training the artificial intelligence algorithm.
[0393] In another example, if the stored usage information UI, UI.j, UI.k, UI.l is "train_ai / reference", the expected usage information "train_ai", "reference", "reference / train_ai" and "train_ai / reference" will match the stored usage information UI, UI.j, UI.k, UI.l, and the result of the third check is true.
[0394] In the embodiment shown, there is a step of performing a first check CHK-1, a step of performing a second check CHK-2, and a step of performing a third check CHK-3. Only if all three checks are positive, the requested medical data record RMDR will be provided PROV-MDR to the requesting entity RE and / or the user client UC. If one of the three checks produces a negative result, the step of denying access to DNY-ACC is performed, for example, by sending an HTTP response specifying an HTTP status code 400 ("bad request"), 401 ("unauthorized"), 403 ("forbidden"), 404 ("not found") or 451 ("not available for legal reasons") by the server and / or the use system S.
[0395] Alternatively, no check may be performed at all. Alternatively, only one check may be performed, specifically, only the first check CHK-1 may be performed, or only the second check CHK-2 may be performed, or only the third check CHK-3 may be performed. Alternatively, only two checks may be performed, specifically, only the first check CHK-1 and the second check CHK-2 may be performed, or only the first check CHK-1 and the third check CHK-3 may be performed, or only the second check CHK-2 and the third check CHK-3 may be performed.
[0396] In this embodiment, all performed examinations must produce positive results in order to provide the medical data record RMDR requested by the PROV-MDR using the system US and / or the server S, and if one or more examinations produce negative results, the access will be denied by the use system US and / or the server S. There may also be other prerequisites for the medical data record RMDR requested by the PROB-MDR to be provided by the use system US and / or the server S, for example, at least two of the three examinations produce positive results, or one examination or a group of other examinations produce positive results.
[0397] Another optional step of the embodiment shown is to determine, using the computing unit US.CU, DET-PI2 as the second identifier PID2 of the patient PAT of the owner of the requested medical data record RMDR based on the distributed ownership ledger OLDG. Specifically, the second identifier PID2 of the patient PAT may include the patient's second public key PAT.j.PBK2, ..., PAT.1.PBK2. Specifically, the second identifier PID2 of the patient PAT may be determined by searching the hashes H(MDR), H2(MDR.j), H2(MDR.k), H2(MDR.l) of the medical data records MDR, MDR.j, MDR.k, MDR.l in the distributed ownership ledger OLDG.
[0398] In the embodiment shown, the second identifier PID2 of the patient PAT is the second public key PAT.PBK2, PAT.j.PBK2, PAT.k.PBK2, PAT.1.PBK2 of the asymmetric key pair, wherein the patient PAT (in particular, only the patient PAT) can access the corresponding second private key PAT.PRK2, PAT.j.PRK2, ..., PAT.1.PRK2.
[0399] The first account is associated with an identifier of the requesting entity RE, and the second account is associated with a second identifier PID2 of the patient's PAT.The smart contract is recorded in the distributed permission ledger CLDG and / or the distributed ownership ledger OLDG.
[0400] Another step of the embodiment shown is to provide the medical data record RMDR requested by PROV-MDR based on the access request AR using the interface US.IF. Specifically, if the requested medical data record RMDR is the medical data record pointed to by the access request AR, the medical data record RMDR requested by PROF-MDR is provided based on the access request AR. In this embodiment, the requested medical data record RMDR is included in the HTTP response sent from ... to ... Alternatively, other formats, standards and / or protocols may be used, for example, HTTPS, WebDAV, FTP or other data transmission protocols known to those skilled in the art.
[0401] Another optional step of the embodiment shown is that the trusted entity TE receives the account information ACCI of the patient PAT of which REC-AI is the owner of the requested medical data record RMDR. Specifically, the account information ACCI can be a second private key PAT.PRK2, PAT.j.PRK2, ..., PAT.1.PRK2 associated with the second identifier PID2 of the patient PAT, wherein the second identifier PID is a second public key PAT.PBK2, PAT.j.PBK2, ..., PAT.1.PBK2 corresponding to the second private key PAT.PRK2, PAT.j.PRK2, ..., PAT.1.PRK2.
[0402] Here, another term for "real money" is "legal money", such as US dollars or euros. The trusted entity TE may expose the identity of the recipient to the regulatory authority based on legal requirements. In this embodiment, the recipient is the patient PAT who is the owner of the requested medical data record RMDR.
[0403] The third account is associated with the trusted entity TE.A payment may be initiated from the trusted entity TE to the patient PAT, wherein the payment is made in legal tender.
[0404] Through this mechanism, the patient PAT is able to withdraw legal tender from the second account of the patient PAT only through the trusted entity TE and not the public who can associate the second account with their real identity.
[0405] Fig.11 FIG. 4 shows an implementation of the entire data flow between the user client UC, the server S and the trusted entity TE. Figure 6 or Figure 7 The data flows shown and described are the same between the user client UC and the server S. Specifically, the server S and / or the user client UC may be included in the usage system US.
[0406] In addition, in this embodiment, the system US and / or the server S are used to record a log TLOG in the distributed ledger MLDG. The first account is the account of the receiving entity RE using the requested medical data record RMDR, and the second account is the account of the patient PAT. Specifically, the log includes the first account and the second account. In this case, the smart contract can be stored in the distributed ledger MLDG or the distributed permission ledger CLDG.
[0407] Specifically, the distributed permission ledger CLDG and the distributed ledger MLDG may be the same; alternatively, the distributed permission ledger CLDG and the distributed ledger MLDG may be two different distributed ledgers.
[0408] Furthermore, in this embodiment, the patient PAT provides the account information ACCI to the trusted entity TE. Specifically, in this embodiment, the account information ACCI is a private key corresponding to the public key as the address of the second account. The third account is associated with the trusted entity TE.
[0409] Fig.12 A patient client PC, a server S and a user client UC are shown. The patient client PC, the server S and / or the user client UC may be a (personal) computer, a workstation, a virtual machine running on host hardware, a microcontroller or an integrated circuit. Specifically, the patient client PC, the server S and / or the user client UC may be a mobile device, such as a smart phone, a tablet computer or a device implanted in the patient's PAT. Alternatively, the patient client PC, the server S and / or the user client UC 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"). Specifically, the patient client PC, the server S and / or the user client UC may be integrated into a common device.
[0410] In the embodiment shown, the user client UC comprises an interface UC.IF, a computing unit UC.CU and a storage unit UC.MU, the server S comprises an interface S.IF, a computing unit S.CU and a storage unit S.MU, and / or the patient client PC comprises an interface PC.IF, a computing unit PC.CU and a storage unit PC.MU.
[0411] The patient client PC and the server S are connected via a first network NETW1, and the server S and the user client UC are connected via a second network NETW2. The first network NETW1 and the second network NETW2 may be the same; alternatively, the first network NETW1 and the second network NETW2 may be different. In addition, the connection between the patient client PC and the server S via the first network NETW1 is optional, and the connection between the user client UC and the server S via the first network NETW2 is optional. The patient client PC and the user client UC may also be connected via the first network NET1, the second network NET2 and / or another network.
[0412] The interfaces PC.IF, S.IF, UC.IF can be embodied as hardware interfaces or software interfaces (e.g. PCIBus, USB or Firewire). Typically, the computing units PC.CU, S.CU, UC.CU may include hardware units and software units, such as a microprocessor, a CPU (abbreviation for “central processing unit”), a GPU (abbreviation for “graphics processing unit”), a field programmable gate array (acronym “FPGA”) or an ASIC (abbreviation for “application-specific integrated circuit”). The computing units PC.CU, S.CU, UC.CU, SERV.CU may be configured as multi-threaded, i.e., the computing units PC.CU, S.CU, UC.CU may host different computing processes at the same time, and may be configured to execute any one of the different computing processes in parallel or to switch between active computing processes and passive computing processes. The storage units PC.MU, S.MU, UC.MU may be, for example, a non-permanent main memory (e.g. a random access memory) or a permanent mass storage (e.g. a hard disk, a USB memory stick, an SD card, a solid-state disk).
[0413] The first network NETW1 and / or the second network NETW2 can be implemented as a LAN (abbreviation for "Local Area Network"), in particular a WiFi network or any other local connection, for example via Bluetooth or USB (abbreviation for "Universal Serial Bus"). Optionally, the network NET can also be implemented as a VPN (abbreviation for "Virtual Private Network").
[0414] Fig.13 A first embodiment of a providing system PS is shown, Fig.14 A second embodiment of the providing system PS is shown. Fig.15 A first embodiment of using the system US is shown, and Fig.16A second embodiment of using the system US is shown. The providing system PS and / or using the system US may be a (personal) computer, a workstation, a virtual machine running on host hardware, a microcontroller or an integrated circuit. Specifically, the providing system PS and / or using the system US may be, for example, a smart phone, a tablet computer or a device implanted in a patient's PAT. Alternatively, the providing system PS and / or using the system US 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").
[0415] The provision system PS comprises an interface PS.IF, a computing unit PS.CU and a storage unit PS.MU, and / or the use system US comprises an interface US.IF, a computing unit US.CU and a storage unit US.MU. The interfaces PS.IF, US.IF, computing units PS.CU, US.CU and storage units PS.MU, US.MU may have the same Fig.12 The same advantageous embodiments as described.
[0416] exist Fig.13 In the first embodiment of the provisioning system PS shown, the interface PS.IF, the calculation unit PS.CU and the memory unit PS.MU are independent units. Fig.14 In the second embodiment of the providing system PS shown, the providing system PS includes a patient client PC and / or a server S, the interface PS.IF of the providing system PS includes an interface PC.IF of the patient client PC and / or an interface S.IF of the server S, the computing unit PS.CU of the providing system PS includes a computing unit PC.CU of the patient client PC and / or a computing unit S.CU of the server S, and the storage unit PS.MU of the providing system PS includes a storage unit PC.MU of the patient client PC and / or a storage unit S.MU of the server S.
[0417] exist Fig.13 In the first embodiment of the use system US shown, the interface US.IF, the calculation unit US.CU and the memory unit US.MU are independent units. Fig.14 In the second embodiment of the using system US shown, the using system US includes a user client UC and / or a server S, the interface US.IF of the using system US includes an interface UC.IF of the user client UC and / or an interface S.IF of the server S, the computing unit US.CU of the using system US includes a computing unit UC.CU of the using client UC and / or a computing unit S.CU of the server S, and the storage unit US.MU of the using system US includes a storage unit UC.MU of the using client UC and / or a storage unit S.MU of the server S.
[0418] Fig.17 Flowcharts of an embodiment of a method for providing location information and an embodiment of a method for using location information are shown. In the flowcharts shown, the flowcharts of the two embodiments are executed sequentially, but it should be understood that the two embodiments of the method can also be executed independently of each other. Both embodiments can be executed on a server S and / or a providing system PS and / or a using system US. The repository can be identical to the storage unit S.MU of the server S and / or the storage unit PS.MU of the providing system PS and / or the storage unit US.MU of the using system US, or the repository can be included in the corresponding storage units US.MU, PS.MU, S.MU.
[0419] The first step of the illustrated embodiment of the method for providing location information is to receive a REC-MDR medical data record MDR, MDR.j, MDR.k, MDR.1 using an interface PS.IF, wherein the medical data record MDR, MDR.j, MDR.k, MDR.1 is associated with a patient PAT. The next step is to store the medical data record MDR, MDR.j, MDR.k, MDR.1 in a repository STR-MDR using a computing unit US.CU. Specifically, the medical data record MDR, MDR.j, MDR.k, MDR.1 is stored in the file system of the repository, for example at the file location "data / ct / mdr_1.dat". Furthermore, in this embodiment, the providing system PS and / or the server S can be accessed via a uniform resource locator URL (resolved to an IP address with the aid of a DNS server), for example "http: / / cloud-storage.com".
[0420] The next step of the illustrated implementation of the method for providing location information is receiving REC-AEID the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE using the interface PS.IF, wherein the authorized entity AE is allowed to access the medical data records MDR, MDR.j, MDR.k, MDR.1 stored in the repository, and wherein the location information is based on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE.
[0421] In this embodiment, the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE is a string that can be contained in the location information, and the string is additionally stored in a repository associated with the medical data records MDR, MDR.j, MDR.k, MDR.l, for example in a list of a set of identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entities AE that are allowed to access the corresponding medical data records MDR, MDR.j, MDR.k, MDR.l.
[0422] Specifically, the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE may be: a random number or a random string, and a public key related to the authorized entity AE, or data signed using a private key related to the authorized entity AE.
[0423] A further step of the illustrated embodiment for providing location information is recording the DOC-LDG medical data records MDR, MDR.j, MDR.k, MDR.l and the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entities AE in the distributed ledger CLDG using the computing unit PS.CU. Specifically, the distributed ledger CLDG may be a distributed consensus ledger CLDG.
[0424] In this embodiment, medical data records MDR, MDR.j, MDR.k, MDR.l and identifiers AEID, AEID.j, AEID.k, AEID.l of authorized entities AE are recorded in a distributed consensus ledger by storing a signature based on a hash of a combination of medical data records MDR, MDR.j, MDR.k, MDR.l and identifiers AEID, AEID.j, AEID.k, AEID.l of authorized entities AE in a distributed consensus ledger, wherein the signature is signed using private keys PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 associated with the patient PAT.
[0425] A further step of the illustrated embodiment for providing location information is to determine, using the computing unit US.CU, location information of DET-LI in relation to the medical data records MDR, MDR.j, MDR.k, MDR.l stored in the repository, wherein the medical data set can be accessed based on the location information. In this embodiment, the location information is a combination of the address of the repository, the location of the medical data records MDR, MDR.j, MDR.k, MDR.l within the repository and the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE. In particular, the location information is a uniform resource locator URL such as given by "http: / / cloud-storage.com / data / ct / mdr_1.dat&auth=7597655124", wherein "7597655124" is the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE.
[0426] The next steps of the illustrated embodiment for providing location information are to provide PROV-LI location information to the patient PAT using interface PS.IF and to send FWD-LI the location information to the authorized entity AE using interface PS.IF. In both steps, the location information may include the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, or the location identifier AEID, AEID.j, AEID.k, AEID.l may not include the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE. In the latter case, the location information provided to the patient PAT or the authorized entity AE would be "http: / / cloud-storage.com / data / ct / mdr_1.dat".
[0427] The first step of the illustrated embodiment for using the location information shown in the flow chart is to receive an access request AR from REC-AR to the medical data records MDR, MDR.j, MDR.k, MDR.l, via the repository or by using the interface US.IF of the system US, in particular, via the interface S.IF of the server S, wherein the medical data records MDR, MDR.j, MDR.k, MDR.l are stored in the repository, and wherein the access request AR is based on the location information. In particular, the access request AR comprises the location information, wherein the location information comprises the location of the medical data records MDR, MDR.j, MDR.k, MDR.l within the repository. In this embodiment, the access request AR is initiated by a requesting entity RE, wherein the requesting entity RE may be equal to the authorized entity AE, or wherein the requesting entity RE may not be equal to the authorized entity AE.
[0428] Another step of the implementation method for using location information is: using the interface US.IF to receive the identifier REID of the REC-REID requesting entity RE, and using the calculation unit US.CU to perform the following check CHK: whether the pair including the medical data record MDR, MDR.j, MDR.k, MDR.l and the identifier of the requesting entity RE is recorded in the distributed ledger CLDG. In this embodiment, the access request AR includes the identifier REID of the requesting entity RE, for example "http: / / cloud-storage.com / data / ct / mdr_1.dat&auth=7597655124", where "7597655124" is the identifier REID of the requesting entity RE, and at the same time is the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, "7597655124" is recorded in the distributed ledger CLDG. Therefore, the result of the check is positive. If the identifier REID of the requesting entity RE does not match the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE associated with the medical data record MDR, MDR.j, MDR.k, MDR.l recorded in the distributed ledger CLDG, the check result will be negative.
[0429] In the case of a positive check, a further step of an embodiment for using the location information is to provide the PROV-MDR medical data records MDR, MDR.j, MDR.k, MDR.l using the repository, in particular to send the medical data records MDR, MDR.j, MDR.k, MDR.l to the user client UC. In the case of a negative check, a further step of an embodiment for using the location information is to deny DNY-ACC access to the medical data records MDR, MDR.j, MDR.k, MDR.l.
[0430] Fig.18 An embodiment of a method for storing a license in a distributed permission ledger CLDG and an embodiment of a method for using license information CI, CI.j, CI.k, CI.1 stored in the distributed permission ledger CLDG are shown. Specifically, the license is stored in the form of license information CI, CI.j, CI.k, CI.1.
[0431] The illustrated embodiment of the method for storing permissions comprises the following steps: Receiving a REC-MDR medical data record MDR, MDR.j, MDR.k, MDR.1 using an interface PS.IF, wherein the medical data record MDR, MDR.j, MDR.k, MDR.1 relates to a patient PAT.
[0432] The illustrated implementation of the method for storing permissions also includes the following steps: receiving the identifiers AEID, AEID.j, AEID.k, AEID.l of the REC-AEID authorized entity AE using the interface PS.IF; receiving the first identifier PID1 of the REC-PI1 patient PAT using the interface PS.IF; and receiving the REC-UI usage information UI, UI.j, UI.k, UI.1 using the interface PS.IF.
[0433] The illustrated embodiment of the method for storing permissions further comprises the following steps: Determining DET-CI permission information CI, CI.j, CI.k, CI.l using a computing unit PS.CU, wherein the permission information CI, CI.j, CI.k, CI.l is based on the medical data record MDR, MDR.j, MDR.k, MDR.1 and the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE. Specifically, the permission information CI, CI.j, CI.k, CI.l is also based on the first identifier PID1 of the patient PAT. Specifically, the permission information CI, CI.j, CI.k, CI.l is also based on the usage information UI, UI.j, UI.k, UI.l.
[0434] In the illustrated embodiment of the method for storing permissions, the permission information CI, CI.j, CI.k, CI.l includes permission signatures CSGN, CSGN.j, CSGN.k, CSGN.l based on the medical data records MDR, MDR.j, MDR.k, MDR.l and based on the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, wherein the permission signatures CSGN, CSGN.j, CSGN.k, CSGN.1 are signed using the first identifier PID1 of the patient PAT.
[0435] The illustrated embodiment of the method for storing licenses further comprises the following step: using the computing unit PS.CU to record the license information CI, CI.j, CI.k, CI.1 DOC-CI in the distributed license ledger CLDG.
[0436] In the illustrated embodiment, the method for storing permission information CI, CI.j, CI.k, CI.1 further comprises the following optional steps: receiving the second identifier PID2 of the REC-PI2 patient PAT using the interface PS.IF; determining the DET-OI ownership information OI, OI.j, OI.k, OI.l using the computing unit PS.CU, wherein the ownership information OI, OI.j, OI.k, OI.l comprises ownership signatures OSGN, OSGN.j, OSGN.k, OSGN.l based on the medical data records MDR, MDR.j, MDR.k, MDR.l, wherein the ownership signatures OSGN, OSGN.j, OSGN.k, OSGN.l are signed using the second identifier PID2 of the patient PAT; and recording the DOC-OI ownership information OI, OI.j, OI.k, OI.l in the distributed ownership ledger OLDG using the computing unit PS.CU. Specifically, the second identifier PID2 of the patient PAT may include the patient's second public keys PAT.PBK2, PAT.j.PBK2, . . . , PAT.1.PBK2.
[0437] Specifically, in this embodiment of the method for storing permissions, the permission information CI, CI.j, CI.k, CI.1 comprises a smart contract. A first account is associated with an entity using the medical data record MDR, MDR.j, MDR.k, MDR.1, and a second account is associated with a first identifier PID1 of the patient PAT and / or with a second identifier PID2 of the patient PAT.
[0438] The steps of the embodiments of the method for storing license information CI, CI.j, CI.k, CI.1 described so far may additionally include all the advantageous features and embodiments described previously, in particular with respect to Figure 1 , Figure 2 and Figure 5 The same steps as described herein are advantageous features and embodiments.
[0439] The illustrated embodiment of the method for using the license information CI, CI.j, CI.k, CI.1 stored in the distributed licensed ledger CLDG comprises the following steps: receiving an access request AR from REC-AR pointing to a requested medical data record RMDR via an interface US.IF, wherein the requested medical data record RMDR is stored in a storage unit US.MU, and wherein the requested medical data record RMDR is related to a patient PAT. Specifically, the access request AR is initiated by a requesting entity RE.
[0440] The illustrated implementation of the method for using the license information CI, CI.j, CI.k, CI.1 stored in the distributed license ledger CLDG further comprises the following steps: using the computing unit PS.CU to search for DET-CI license information CI, CI.j, CI.k, CI.1 in the distributed license ledger CLDG, wherein the license information CI, CI.j, CI.k, CI.1 is related to the requested medical data record RMDR.
[0441] The illustrated embodiment of the method for using the license information CI, CI.j, CI.k, CI.1 stored in the distributed license ledger CLDG further comprises the following step: receiving an identifier REID of the REC-REID requesting entity RE using the interface US.IF.
[0442] The illustrated embodiment of the method for using the permission information CI, CI.j, CI.k, CI.1 stored in the distributed permission ledger CLDG further comprises the following step: Using the computing unit US.CU, based on the permission information CI, CI.j, CI.k, CI.1, a check CHK is performed as follows: whether the patient PAT has permission to use the requested medical data record RMDR. In this embodiment, the check is also based on a comparison of the identifier REID of the requesting entity RE with the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE.
[0443] In the event that the check is positive, the illustrated embodiment of the method for using the license information CI, CI.j, CI.k, CI.1 stored in the distributed licensed ledger CLDG further comprises the following step: processing the medical data record RMDR requested by the PRC using the computing unit US.CU. In this embodiment, the license information CI, CI.j, CI.k, CI.1 comprises a smart contract, and wherein processing the medical data record RMDR requested by the PRC comprises executing the smart contract.
[0444] In the illustrated embodiment, the access request AR includes a trainable function, wherein processing the medical data record RMDR requested by the PRC includes: training the trainable function based on the requested medical data record RMDR, and optionally providing the trainable function after training the trainable function based on the requested medical data record RMDR. Alternatively, processing the medical data record RMDR requested by the PRC may include: displaying the requested medical data record RMDR in a non-reproducible manner.
[0445] In this embodiment, the trainable function is an artificial neural network including edge weights, wherein the edge weights are adjusted by means of training. Specifically, in order to train and adjust the edge weights, the requested medical data record RMDR is used as the input of the neural network. In this embodiment, the requested medical data record RMDR includes imaging data and annotations of the imaging data, for example, segmentation of the imaging data or diagnostic information related to the imaging data. Specifically, the imaging data is used as the input of the neural network, and the output of the neural network is the calculated annotations of the imaging data, which can be compared with the actual annotations of the imaging data contained in the requested medical data record RMDR. Based on the comparison of the output of the artificial neural network with the actual annotations of the imaging data contained in the requested medical data record RMDR, the parameters of the trainable function, i.e. the edge weights of the artificial neural network, can be adjusted, for example, based on a back-propagation algorithm by minimizing the distance between the output of the artificial neural network and the actual annotations of the imaging data contained in the requested medical data record RMDR.
[0446] In order to display the requested medical data record RMDR in a non-copyable manner, the requested medical data record RMDR can be provided to the user client UC in a web browser, and the copying of the requested medical data record RMDR can be prevented by not allowing right-clicking on the requested medical data record RMDR using Javascript. In addition, if the requested medical data record RMDR includes text information, the text information can be presented as an image, and only the image can be provided to the user client UC. In addition, it is possible to install a dedicated application on the user client UC, which does not allow copying of the data displayed therein, and use the dedicated application to display the requested medical data record RMDR. Specifically, the requested medical data record RMDR can be encrypted and / or encoded so that only the dedicated application can decrypt and / or decode the requested medical data record RMDR.
[0447] In addition, the embodiment shown may also include the following steps: using the computing unit US.PU to determine DET-PI2 as the second identifier PID2 of the patient PAT of the owner of the requested medical data record RMDR based on the distributed ownership ledger OLDG. The first account is associated with the identifier REID of the requesting entity RE, and the second account is associated with the second identifier PID2 of the patient PAT. These steps may include the following steps: Fig.10 Specifically, the patient's second identifier PID2 may include the patient's second public key PAT.PBK2, PAT.j.PBK2, ..., PAT.l.PBK2.
[0448] In addition, the embodiment shown may also include the following steps: receiving, by the trusted entity TE, account information ACCI of the patient PAT as the owner of the requested medical data record RMDR, wherein the third account is associated with the trusted entity TE; and initiating payment from the trusted entity TE to the patient PAT. These steps may include regarding Fig.10 All advantageous features and embodiments described in the corresponding steps.
[0449] In view of the following list of possible embodiments, the characteristics, features and advantages of the invention, the various aspects and embodiments of the invention described above and their implementation become clearer and easier to understand. 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, whenever such a combination or exchange is meaningful and within the meaning of the invention.
[0450] Embodiment 1: A method for providing a location information URL associated with a medical data record MDR, MDR.j, MDR.k, MDR.l, comprising:
[0451] - receiving the medical data records MDR, MDR.j, MDR.k, MDR.l described in REC-MDR using the interface PS.IF,
[0452] Wherein, the medical data records MDR, MDR.j, MDR.k, MDR.l are related to the patient's PAT,
[0453] - storing the medical data records MDR, MDR.j, MDR.k, MDR.l STR-MDR in the storage unit PS.MU using the computing unit PS.CU,
[0454] - using the calculation unit PS.CU to determine DET-LI the location information URL associated with the medical data records MDR, MDR.j, MDR.k, MDR.l stored in the storage unit PS.MU,
[0455] Wherein, the medical data sets MDR, MDR.j, MDR.k, MDR.l can be accessed based on the location information URL,
[0456] - Providing PROV-LI the location information URL to the patient PAT using the interface PS.IF.
[0457] Embodiment 2: The method according to embodiment 1 further includes:
[0458] - receiving, using said interface PS.IF, REC-AEID the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE,
[0459] wherein the authorized entity AE is allowed to access the medical data records MDR, MDR.j, MDR.k, MDR.l stored in the storage unit PS.MU,
[0460] The location information URL is based on the identifiers AEID, AEID.j, AEID.k, and AEID.l of the authorized entity AE.
[0461] Embodiment 3: The method according to embodiment 2 further includes:
[0462] - Recording DOC-LDG the medical data records MDR, MDR.j, MDR.k, MDR.l and the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entities AE in the distributed ledger CLDG using the computing unit PS.CU.
[0463] Embodiment 4: A method according to embodiment 3, wherein the step of recording DOC-LDG includes: creating a signature based on the medical data records MDR, MDR.j, MDR.k, MDR.1 and / or based on the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE, wherein the signature is signed using the private key PAT.PRK1, PAT.j.PRK1, PAT.k.PRK1, PAT.1.PRK1 associated with the patient.
[0464] Embodiment 5: The method according to one of embodiments 2 to 4, further comprising:
[0465] - Sending FWD-LI said location information URL to said authorized entity AE using said interface PS.IF.
[0466] Embodiment 6: A method for using a location information URL provided by a method according to one of embodiments 1 to 5, comprising:
[0467] - receiving, via the interface US.IF, an access request AR from REC-AR for the requested medical data record RMDR,
[0468] wherein the requested medical data record RMDR is stored in the storage unit US.MU,
[0469] Wherein, the access request AR is based on the location information URL,
[0470] - Providing the requested medical data record RMDR PROV-MDR using the interface US.IF.
[0471] Embodiment 7: The method according to embodiment 6, wherein the access request AR is initiated by a requesting entity RE, wherein the medical data records MDR, MDR.j, MDR.k, MDR.l and the identifiers AEID.j, AEID.k, AEID.1 of the relevant authorized entities AE are recorded in the distributed ledger CLDG, and the method further comprises:
[0472] - receiving, using said interface US.IF, REC-REID the identifier REID of said requesting entity RE,
[0473] - using a computing unit US.CU, a check CHK is performed as follows: whether the pair of the medical data record RMDR containing the request and the identifier REID of the requesting entity RE is recorded in the distributed ledger CLDG,
[0474] Therein, the step of providing PROV-MDR is performed only if the check is positive.
[0475] Embodiment 8: A system PS for providing location information URLs associated with medical data records MDR, MDR.j, MDR.k, MDR.l, comprising:
[0476] - an interface PS.IF configured to receive the medical data records MDR, MDR.j, MDR.k, MDR.l of REC-MDR, wherein the medical data records MDR, MDR.j, MDR.k, MDR.l are related to the patient PAT, and configured to provide the location information URL of PROV-LI to the patient PAT,
[0477] - A computing unit PS.CU, which is configured to store the medical data records MDR, MDR.j, MDR.k, MDR.l STR-MDR in a storage unit PS.MU, and the computing unit is also configured to determine DET-LI a location information URL related to the medical data records MDR, MDR.j, MDR.k, MDR.l stored in the storage unit PS.MU, wherein the medical data set MDR, MDR.j, MDR.k, MDR.l can be accessed based on the location information URL.
[0478] Embodiment 9: A computer program product comprises a program element, which, when loaded into the storage unit PS.MU of the providing system PS, causes the providing system PS to execute the steps of the method for providing location information URL according to one of embodiments 1 to 5.
[0479] Embodiment 10: A computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a providing system PS and / or can be executed in the providing system PS, so that when the program code portion is executed in the providing system PS, the providing system PS performs the method for providing a location information URL according to one of embodiments 1 to 5.
[0480] Embodiment 11: A usage system US, which is configured to receive an access request AR from REC-AR for a requested medical data record RMDR, wherein the requested medical data record RMDR is stored within the usage system US, wherein the access request AR is based on a location information URL provided by a method according to one of embodiments 1 to 5, and the usage system is also configured to provide the requested medical data record RMDR from PROV-MDR.
[0481] Embodiment 12: A computer program product comprising a program element, which, when loaded into the storage unit US.MU of the using system US, causes the using system US to execute the steps of the method for using location information URL according to embodiment 6 or 7.
[0482] Embodiment 13: A computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a usage system US and / or can be executed in the usage system US, so that when the program code portion is executed in the usage system US, the usage system US performs the method for using location information URL according to embodiment 6 or 7.
[0483] Embodiment 14: A method for storing a license, comprising the following steps:
[0484] - Receive REC-MDR medical data records MDR, MDR.j, MDR.k, MDR.l using interface PS.IF,
[0485] Wherein, the medical data records MDR, MDR.j, MDR.k, MDR.l are related to the patient's PAT,
[0486] - receiving, using said interface PS.IF, REC-AEID the identifiers AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE,
[0487] - using the calculation unit PS.CU to determine the DET-CI license information CI, CI.j, CI.k, CI.l,
[0488] wherein the authorization information CI, CI.j, CI.k, CI.l is based on the medical data record MDR, MDR.j, MDR.k, MDR.1 and the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE,
[0489] - Use the computing unit PS.CU to record the license information CI, CI.j, CI.k, CI.1 described in DOC-CI in the distributed license ledger CLDG.
[0490] Embodiment 15: The method according to embodiment 14 further includes:
[0491] - receiving, using said interface PS.IF, REC-PI1, said first identifier PID1 of said patient PAT,
[0492] Therein, the permission information CI, CI.j, CI.k, CI.1 is also based on the first identifier PID1 of the patient PAT.
[0493] Embodiment 16: The method according to claim 15, wherein the permission information CI, CI.j, CI.k, CI.1 comprises a permission signature CSGN, CSGN.j, CSGN.k, CSGN.1 based on the medical data record MDR, MDR.j, MDR.k, MDR.1 and on the identifier AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE,
[0494] Therein, the permission signatures CSGN, CSGN.j, CSGN.k, and CSGN.1 are signed using the first identifier PID1 of the patient PAT.
[0495] Embodiment 17: The method according to one of embodiments 14 to 16, further comprising:
[0496] - receiving, using said interface PS.IF, REC-PI2, said second identifier PID2 of said patient PAT,
[0497] - determining the DET-OI ownership information OI, OI.j, OI.k, OI.l using said calculation unit PS.CU,
[0498] wherein the ownership information OI.j, OI.k, OI.1 comprises ownership signatures OSGN, OSGN.j, OSGN.k, OSGN.l based on the medical data records MDR, MDR.j, MDR.k, MDR.1, wherein the ownership signatures OSGN, OSGN.j, OSGN.k, OSGN.l are signed using the second identifier PID2 of the patient PAT,
[0499] - Use the computing unit PS.CU to record the ownership information OI, OI.j, OI.k, OI.1 of DOC-OI in the distributed ownership ledger OLDG.
[0500] Embodiment 18: The method according to one of embodiments 14 to 17, further comprising:
[0501] - using the interface PS.IF to receive REC-UI usage information UI, UI.j, UI.k, UI.l,
[0502] Among them, the permission information CI, CI.j, CI.k, CI.1 is also based on the usage information UI, UI.j, UI.k, UI.l.
[0503] Embodiment 19: A method according to one of embodiments 14 to 18, wherein the license information CI, CI.j, CI.k, CI.1 includes a smart contract.
[0504] Embodiment 20: A method according to embodiment 19, wherein the first account is associated with an entity using the medical data records MDR, MDR.j, MDR.k, MDR.l,
[0505] And wherein the second account is associated with the first identifier PID1 of the patient PAT and / or is associated with the second identifier PID2 of the patient PAT. Embodiment 21: A method of using the license information CI, CI.j, CI.k, CI.l stored in a distributed license ledger CLDG according to the method according to one of embodiments 14 to 20, comprising:
[0506] - receiving, via the interface US.IF, an access request AR directed to the requested medical data record RMDR from REC-UR,
[0507] wherein the requested medical data record RMDR is stored in a storage unit US.MU, and wherein the requested medical data record RMDR is associated with a patient PAT,
[0508] - using the computing unit PS.CU to search for DET-CI license information CI, CI.j, CI.k, CI.l in the distributed license ledger CLDG,
[0509] wherein the permission information CI, CI.j, CI.k, CI.l are related to the requested medical data record RMDR,
[0510] - using the calculation unit US.CU to perform the following check CHK based on the permission information CI, CI.j, CI.k, CI.l: whether the patient PAT has permission to use the requested medical data record RMDR,
[0511] - In the event of a positive check, processing the requested medical data record RMDR by PRC using the computing unit US.CU.
[0512] Embodiment 22: The method according to embodiment 21, wherein the access request AR is initiated by a requesting entity RE, and the method further comprises:
[0513] - receiving, using said interface US.IF, REC-REID the identifier REID of said requesting entity RE;
[0514] The authorization information CI, CI.j, CI.k, CI.1 include the identifiers AEID.j, AEID.k, AEID.1 of the authorized entities AE.
[0515] Therein, the check is also based on a comparison of the identifier REID of the requesting entity RE with the identifiers AEID, AEID.j, AEID.k, AEID.1 of the authorized entity AE.
[0516] Embodiment 23: A method according to embodiment 21 or 22, wherein the permission information CI, CI.j, CI.k, CI.1 includes a smart contract, and wherein processing the medical data record RMDR requested by the PRC includes executing the smart contract.
[0517] Embodiment 24: A method according to one of Embodiments 21 to 23, wherein the access request AR includes a trainable function, wherein processing the medical data record RMDR requested by the PRC includes: training the trainable function based on the requested medical data record RMDR, and optionally providing the trainable function after training the trainable function based on the requested medical data record RMDR.
[0518] Embodiment 25: A method according to one of Embodiments 21 to 24, wherein processing the requested medical data record RMDR of the PRC includes: displaying the requested medical data record RMDR in a non-copyable manner.
[0519] Embodiment 26: The method according to one of claims 21 to 25,
[0520] Among them, ownership information OI, OI.j, OI.k, OI.l are recorded in the distributed ownership ledger OLDG.
[0521] Each piece of ownership information OI, OI.j, OI.k, OI.l comprises an ownership signature OSGN, OSGN.j, OSGN.k, OSGN.l based on the medical data record MDR, MDR.j, MDR.k, MDR.1,
[0522] The ownership signatures OSGN, OSGN.j, OSGN.k and OSGN.1 are signed based on the second identifier PID2 of the patient PAT.
[0523] The method further comprises:
[0524] - determining, using the computing unit US.PU based on the distributed ownership ledger OLDG, DET-PI2 as a second identifier PID2 of the patient PAT of the owner of the requested medical data record RMDR, wherein a first account is associated with the identifier REID of the requesting entity RE,
[0525] And wherein the second account is associated with the second identifier PID2 of the patient PAT.
[0526] Embodiment 27: The method according to claim 26, further comprising:
[0527] - receiving by the trusted entity TE REC-AI the account information ACCI of the patient PAT as the owner of the requested medical data record RMDR, wherein a third account is associated with the trusted entity TE, - initiating a payment from the trusted entity TE to the patient PAT.
[0528] Embodiment 28: A license storage system PS for storing licenses, comprising:
[0529] - an interface PS.IF configured for receiving a REC-MDR medical data record MDR, MDR.j, MDR.k, MDR.l, wherein the medical data record MDR, MDR.j, MDR.k, MDR.l is related to a patient PAT,
[0530] The interface is also configured to receive the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE via the REC-AEID,
[0531] a computing unit PS.CU configured to determine DET-CI permission information CI, CI.j, CI.k, CI.l, wherein the permission information CI, CI.j, CI.k, CI.l is based on the medical data record MDR, MDR.j, MDR.k, MDR.l and the identifier AEID, AEID.j, AEID.k, AEID.l of the authorized entity AE,
[0532] The computing unit is further configured to record the license information CI, CI.j, CI.k, CI.l of DOC-CI in the distributed license ledger CLDG using the computing unit PS.CU.
[0533] Embodiment 29: The permission storage system PS according to embodiment 28 is further configured to perform the method according to one of embodiments 14 to 20.
[0534] Embodiment 30: A computer program product comprising a program element which, when loaded into a storage unit PS.MU of the license storage system PS, causes the license storage system PS to execute the steps of the method for storing licenses according to one of embodiments 14 to 20.
[0535] Embodiment 31: A computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a license storage system PS and / or can be executed in the license storage system PS, so that when the program code portion is executed in the license storage system PS, the license storage system PS performs the method for storing licenses according to one of embodiments 14 to 20.
[0536] Embodiment 32: A license use system US for using license information CI, CI.j, CI.k, CI.l stored in a distributed license ledger CLDG according to a method according to one of embodiments 14 to 20, comprising:
[0537] an interface US.IF configured to receive an access request AR directed by REC-UR to a requested medical data record RMDR, wherein the requested medical data record RMDR is stored in a storage unit US.MU and wherein the requested medical data record RMDR is related to a patient PAT,
[0538] a computing unit US.CU configured to look up DET-CI permission information CI, CI.j, CI.k, CI.l in the distributed permission ledger CLDG, wherein the permission information CI, CI.j, CI.k, CI.l is related to the requested medical data record RMDR,
[0539] The calculation unit is further configured to perform the following check CHK based on the permission information CI, CI.j, CI.k, CI.l: whether the patient PAT has permission to use the requested medical data record RMDR,
[0540] Furthermore, the computing unit is further configured to, in the event of a positive check, process the requested medical data record RMDR of the PRC.
[0541] Embodiment 33: The permission use system US according to Embodiment 32 is further configured to execute the method according to one of Embodiments 21 to 27.
[0542] Embodiment 34: A computer program product comprising a program element, which, when loaded into the storage unit US.MU of the license use system US, causes the license use system US to execute the steps of the method for using a license according to one of embodiments 21 to 27.
[0543] Embodiment 35: A computer-readable medium having a program code portion of a computer program stored thereon, wherein the program code portion can be loaded into a license use system US and / or can be executed in the license use system US, so that when the program code portion is executed in the license use system US, the license use system US performs a method for storing a license according to one of embodiments 21 to 27.
[0544] Individual embodiments or their various aspects and features may be combined or exchanged with one another without limiting or extending the scope of the described invention, without limiting or extending the scope of the described invention, where such a combination or exchange makes sense and is within the meaning of the invention. Where applicable, the advantages described with respect to one embodiment of the invention are also advantages of the other embodiments of the invention.
Claims
1. A method for providing a uniform resource locator (URL), comprising: - receiving (REC-MDR) a medical data record (MDR, MDR.j, MDR.k, MDR.l) using an interface (PS.IF), wherein the medical data record (MDR, MDR.j, MDR.k, MDR.l) is related to a patient (PAT), - receiving (REC-AEID) using said interface (PS.IF) an identifier (AEID.j, AEID.k, AEID.l) of an authorized entity (AE), wherein said authorized entity (AE) is allowed to access said medical data record (MDR, MDR.j, MDR.k, MDR.l), - determining (DET-URL) using a computing unit (PS.CU) said uniform resource locator (URL) associated with said medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the uniform resource locator (URL) is based on an identifier (AEID.j, AEID.k, AEID.l) of the authorized entity (AE), wherein the uniform resource locator (URL) includes an authorization token based on the medical data record (MDR, MDR.j, MDR.k, MDR.l), and wherein said medical data record (MDR, MDR.j, MDR.k, MDR.l) is accessible by following said uniform resource locator (URL), - determining (DET-CI) permission information (CI, CI.j, CI.k, CI.l) using the computing unit (PS.CU), wherein the permission information (CI, CI.j, CI.k, CI.l) relates to the permission of the patient (PAT) for the authorized entity (AE) to use the medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the authorization information (CI, CI.j, CI.k, CI.1) is based on the medical data record (MDR, MDR.j, MDR.k, MDR.1) and / or on an identifier (AEID.j, AEID.k, AEID.1) of the authorized entity (AE), - using the computing unit (PS.CU) to record (DOC-CI) the license information (CI, CI.j, CI.k, CI.1) in a distributed license ledger (CLDG), - providing (PROV-URL) said uniform resource locator (URL) to said patient (PAT) using said interface (PS.IF).
2. The method according to claim 1, further comprising: - Using a storage unit (PS.MU) to store (STR-MDR) the medical data records (MDR, MDR.j, MDR.k, MDR.l), wherein the uniform resource locator (URL) includes the location of the medical data records (MDR, MDR.j, MDR.k, MDR.l) in the storage unit (PS.MU).
3. The method according to claim 1 or 2, further comprising: - receiving (REC-PI1) a first identifier (PID1) of said patient (PAT) using said interface (PS.IF), Therein, the permission information (CI, CI.j, CI.k, CI.1) is also based on the first identifier (PID1) of the patient (PAT).
4. The method according to claim 3, wherein: the authorization information (CI, CI.j, CI.k, CI.l) comprises an authorization signature (CSGN, CSGN.j, CSGN.k, CSGN.l) based on the medical data record (MDR, MDR.j, MDR.k, MDR.l) and / or based on an identifier (AEID.j, AEID.k, AEID.l) of the authorized entity (AE), Therein, the permission signature (CSGN, CSGN.j, CSGN.k, CSGN.1) is signed based on the first identifier (PID1) of the patient (PAT).
5. The method according to one of claims 1, 2 and 4, further comprising: - receiving (REC-UI) usage information (UI, UI.j, UI.k, UI.l) using said interface (PS.IF), Wherein, the licensing information (CI, CI.j, CI.k, CI.l) is also based on the usage information (UI, UI.j, UI.k, UI.l).
6. The method according to claim 3, further comprising: - receiving (REC-PI2) a second identifier (PID2) of said patient (PAT) using said interface (PS.IF), - determining (DET-OI) ownership information (OI, OI.j, OI.k, OI.l) using the computing unit (PS.CU), wherein the ownership information (OI, OI.j, OI.k, OI.l) comprises an ownership signature (OSGN, OSGN.j, OSGN.k, OSGN.l) based on the medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the ownership signature (OSGN, OSGN.j, OSGN.k, OSGN.l) is signed based on a second identifier (PID2) of the patient (PAT), - Using the computing unit (PS.CU) to record (DOC-OI) the ownership information (OI, OI.j, OI.k, OI.1) in a distributed ownership ledger (OLDG).
7. The method according to claim 6, in, The licensing information (CI, CI.j, CI.k, CI.l) includes a smart contract.
8. A method of using a uniform resource locator (URL) provided by a method according to one of claims 2 to 7, comprising: - receiving (REC-AR) via the interface (US.IF) an access request (AR) directed to a requested medical data record (RMDR), wherein the requested medical data record (RMDR) is stored in a storage unit (US.MU), wherein the access request (AR) is based on the uniform resource locator (URL), - providing (PROV-MDR) the requested medical data record (RMDR) based on the access request (AR) using the interface (US.IF).
9. The method according to claim 8, wherein: The access request (AR) is initiated by the requesting entity (RE), Wherein, permission information (CI, CI.j, CI.k, CI.l) based on medical data records (MDR, MDR.j, MDR.k, MDR.l) and based on identifiers (AEID.j, AEID.k, AEID.1) of authorized entities (AE) is recorded in a distributed permission ledger (CLDG), and the method further includes: - receiving (REC-REID) an identifier (REID) of said requesting entity (RE) using said interface (US.IF), - performing, using a computing unit (US.CU), a first check (CHK-1) whether the distributed permission ledger (CLDG) records permission information (CI, CI.j, CI.k, CI.l) based on the requested medical data record (RMDR) and based on an identifier (REID) of the requesting entity (RE), Therein, the step of providing (PROV-MDR) is only performed if the first check is positive.
10. The method according to claim 8 or 9, in, Ownership information (OI, OI.j, OI.k, OI.l) is recorded in the distributed ownership ledger (OLDG). Each ownership information (OI, OI.j, OI.k, OI.l) includes an ownership signature (OSGN, OSGN.j, OSGN.k, OSGN.1) based on a medical data record (MDR, MDR.j, MDR.k, MDR.l). wherein the ownership signatures (OSGN, OSGN.j, OSGN.k, OSGN.l) are signed based on a second identifier (PID2) of the patient (PAT), The method further comprises: - determining (DET-PI2) an ownership second identifier of the patient (PAT) as the owner of the requested medical data record (RMDR) based on the distributed ownership ledger (OLDG) using the computing unit (PS.CU).
11. The method according to claim 10, further comprising: - receiving (REC-AI) by the trusted entity (TE) the account information (ACCI) of said patient (PAT) as owner of the requested medical data record (RMDR), - Payment from said trusted entity (TE) to said patient (PAT) is initiated by said trusted entity (TE).
12. A providing system (PS) for providing a uniform resource locator (URL), comprising: an interface (PS.IF) configured for receiving (REC-MDR) a medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the medical data record (MDR, MDR.j, MDR.k, MDR.l) is related to a patient (PAT), is further configured for receiving (REC-AEID) an identifier (AEID.j, AEID.k, AEID.l) of an authorized entity (AE), wherein the authorized entity (AE) is allowed to access the medical data record (MDR, MDR.j, MDR.k, MDR.l), is further configured to provide (PROV-URL) the uniform resource locator (URL) to the patient (PAT) using the interface, a computing unit (PS.CU) configured for determining (DET-URL) a uniform resource locator (URL) associated with the medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the uniform resource locator (URL) is based on an identifier (AEID.j, AEID.k, AEID.l) of the authorized entity (AE), wherein the uniform resource locator (URL) comprises an authorization token based on the medical data record (MDR, MDR.j, MDR.k, MDR.l), and wherein the medical data record (MDR, MDR.j, MDR.k, MDR.l) is accessible by following the uniform resource locator (URL), is further configured for determining (DET-CI) permission information (CI, CI.j, CI.k, CI.l), wherein the permission information (CI, CI.j, CI.k, CI.l) relates to permission of the patient (PAT) for the authorized entity (AE) to use the medical data record (MDR, MDR.j, MDR.k, MDR.l), wherein the authorization information (CI, CI.j, CI.k, CI.1) is based on the medical data record (MDR, MDR.j, MDR.k, MDR.1) and / or on an identifier (AEID.j, AEID.k, AEID.1) of the authorized entity (AE), - is also configured to record (DOC-CI) the license information (CI, CI.j, CI.k, CI.1) in a distributed license ledger (CLDG).
13. A computer program product comprising a program element which, when loaded into a storage unit (PS.MU) of a providing system (PS), causes the providing system (PS) to perform the steps of the method for providing a uniform resource locator (URL) according to one of claims 1 to 7.
Citation Information
Patent Citations
System and method for block-chain verification of goods
US20160098723A1
Distributed blockchain-based method for saving the location of a file
WO2018115992A1
