# US 2019/0356479 A1 · Method, server and communication system for secure delivery of patient's image and consent data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0356479 A1 - Document ID: US20190356479A1 - Status: Published application - Kind: A1 - Application number: 16/415,475 - Filed: 2019-05-17 - Published: 2019-11-21 - Earliest claimed: 2018-05-17 - Assignees: Siemens Healthcare GmbH - Applicants: Siemens Healthcare GmbH - Inventors: Andreas Grimme - Web page: https://patentgrep.com/patent/US20190356479A1 ## CPC - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - G16H 10/60: for patient-specific data, e.g. for electronic patient records - H04L 9/14: using a plurality of keys or algorithms - G06Q 2220/12: Usage or charge determination - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract In methods and systems for communicating medical image data that were generated for a patient between computing entities of a hospital network, a cloud-based data store and a patient's mobile device, a QR code serves to code a data package containing a user identification and a public key, which has been generated on the patient's mobile device, to a hospital server, in order to process personal data so that the personal data may be downloaded from the data store directly to the patient's mobile device in an encrypted form, and may be visualized there in clear text by means of applying a private key stored locally on the patient's mobile device. The method and system are web based and need no special requirements on the part of the patient's mobile device. ## Claims ### Claim 1 A method for receiving access to personal medical data, said method being executed on a patient's mobile device and comprising: navigating a web client of the patient's mobile device to a web service; receiving instructions from the web service for the web client to create a user account, comprising an asymmetric key pair and a user identification (UID), which references the asymmetric key pair; storing the private key of the asymmetric key pair and the UID locally on the patient mobile device; preparing a public key of the asymmetric key pair to be filed in a data store under the UID, acting as key; generating a first code, encoding the UID; preparing the generated first code for transmission to a hospital server by using a nearfield data transmission; receiving encrypted images, being encrypted with the public key; and decrypting the received encrypted images with the private key for providing decrypted personal medical data as a result locally on the patient's mobile device. ### Claim 2 (depends on 1) A method according to claim 1, comprising executing the method as a web client with a web browser on the patient's mobile device. ### Claim 3 (depends on 1) A method according to claim 1, comprising navigating the web client of the patient's mobile device to a web service by accessing a URL link, where the web service is accessible. ### Claim 4 (depends on 1) A method according to claim 1, comprising navigating the web client of the patient's mobile device to a web service by scanning a provided second code, which directs the web client automatically to a URL link, where the web service is accessible. ### Claim 5 (depends on 1) A method according to claim 1, wherein the personal medical data comprises protected health information that are stored in the data store in encrypted form. ### Claim 6 (depends on 1) A method according to claim 1, comprising: receiving a patient consent form on the patient's mobile device, being uniquely dedicated to the patient's mobile device, based on the extracted UID; providing a completed consent form; signing the completed consent form with the private key and preparing the signed completed consent form for transmission to the data store. ### Claim 7 (depends on 1) A method according to claim 1, comprising the first code, encoding the UID so as to indirectly reference the key pair. ### Claim 8 (depends on 1) A method according to claim 1, comprising the nearfield data transmission for implementing with digital signals requiring a personal contact between the patient at the patient's mobile device and a receptionist, operating the hospital server. ### Claim 9 (depends on 8) A method according to claim 8, comprising implementing said nearfield data transmission with digital signals as an optical transmission of said first code. ### Claim 10 (depends on 8) A method according to claim 8, comprising using, as said nearfield data transmission with digital signals, a nearfield data transmission selected from the group consisting of transmission of a QR code, transmission of an NFC, and a Bluetooth connection. ### Claim 11 (depends on 1) A method according to claim 1, comprising, deploying the data store as cloud server to be accessed via an internet protocol, or within a hospital network in which the data store is operated by the hospital server. ### Claim 12 A method for providing access to personal medical data, the method being executed on a hospital server and comprising: receiving a first code, encoding a user identification (UID), wherein the UID identifies a patient's mobile device; extracting the UID from the received first code; accessing a data store with the extracted user identification in order to get an associated public key of an asymmetric key pair; using the public key for encrypting personal medical data; sending the encrypted personal medical data to the data store so as to make the encrypted personal medical data accessible by the patient's mobile device. ### Claim 13 A method for communication of personal medical data, comprising: via a patient's mobile device, navigating a web client of the patient's mobile device to a web service; receiving instructions at the patient's mobile device from the web service for the web client to create a user account, comprising an asymmetric key pair and a user identification (UID), which references the asymmetric key pair; storing the private key of the asymmetric key pair and the UID locally on the patient mobile device; at the patient's mobile device, preparing a public key of the asymmetric key pair to be filed in a data store under the UID, acting as key; at the patient's mobile device, generating a first code, encoding the UID; transmitting the generated first code from the patient's mobile device to a hospital server by using a nearfield data transmission; at the hospital server, receiving a first code, encoding a user identification (UID), wherein the UID identifies a patient's mobile device; at the hospital server, extracting the UID from the received first code; at the hospital server, accessing a data store with the extracted user identification in order to get an associated public key of the asymmetric key pair; at the hospital server, using the public key for encrypting personal medical data; at the hospital server, sending the encrypted personal medical data to the data store so as to make the encrypted personal medical data accessible by the patient's mobile device; via the patient's mobile device, accessing the data store so as to receive the encrypted personal medical data that were encrypted with the public key; and at the patient's mobile device, decrypting the received encrypted images with the private key for providing decrypted personal medical data as a result locally on the patient's mobile device. ### Claim 14 (depends on 13) A method according to claim 13, comprising, via the hospital server, accessing a Radiology Information System in order to calculate an estimated waiting time for a scheduled medical examination for the patient and transmitting said estimating waiting time in an estimated-wait-message to the patient's mobile device. ### Claim 15 A hospital server for providing access to personal medical data, said hospital server comprising: a code interface configured to receive a first code, encoding a user identification (UID), wherein the UID identifies a patient's mobile device; a processor configured to extract the user identification from the received first code; a data store interface configured to access a data store with the extracted UID in order to get an associated public key of an asymmetric key pair; the processor being further configured to use the public key for encrypting personal medical data, and to send encrypted personal medical data to the data store in order to make the encrypted personal medical data accessible by the patient's mobile device. ### Claim 16 A system for communication of personal medical data between a hospital server and a patient's mobile device comprising: a patient's mobile device with a web client for receiving instructions from a web service; a data store in which a public key of an asymmetric key pair has been filed under a patient's the user identification (UID), acting as key, and in which personal medical data of the patient are stored in an encrypted form, being encrypted with the public key of the asymmetric key pair; and p1 a hospital server comprising a code interface configured to receive a first code, encoding a user identification (UID), wherein the UID identifies a patient's mobile device, a processor configured to extract the user identification from the received first code, a data store interface configured to access a data store with the extracted UID in order to get an associated public key of an asymmetric key pair, the processor being further configured to use the public key for encrypting personal medical data, and to send encrypted personal medical data to the data store in order to make the encrypted personal medical data accessible by the patient's mobile device.