ARRANGEMENT FOR ENCRYPTED EXCHANGE OF PERSONAL MEDICAL AND FINANCIAL DATA

Abstract

An arrangement for encrypted exchange of personal medical and financial data comprises a mass enrollment center computing device, a subscriber computing device, a web platform server device, and a payment provider server device. The web platform server device creates a temporary link site with a temporary link site identifier and forwards the link site identifier to the mass enrollment center computing device and to the subscriber computing device. Pre-determined messages are exchanged between the mass enrollment center computing device and the subscriber computing device, using a computer memory link location for releasing health-related data to the subscriber computing device. The web platform server device, upon reception of a payment signal from the payment provider server device, automatically initiates a transmission of identity information data of at least one subject from the mass enrollment center computing device to the subscriber computing device.

Claims

1. A system for encrypted exchange of personal medical and financial data, the system comprising: a mass enrollment center computing device, operable to store health-related data and identity information data of a multitude of subjects, a subscriber computing device, operable to receive the health-related data and the identity information data via a communication interface, a web platform server device, operable to provide an encrypted communication channel between the subscriber computing device and the mass enrollment center computing device, the providing of the encrypted communication channel by the web platform server device comprising: creating a temporary link site with a temporary link site identifier and a computer memory link location, forwarding the link site identifier to the mass enrollment center computing device and to the subscriber computing device, providing, by the temporary link site, a communication interface that allows the encrypted interchange of pre-determined messages between the mass enrollment center computing device and the subscriber computing device, and using the computer memory link location for releasing the health-related data to the subscriber computing device, and a payment provider server device, operable to receive a payment information from one of the mass enrollment center computing device and/or from the subscriber computing device, and to provide a payment signal to the web platform server device, wherein the web platform server device is operable to automatically initiate a transmission of the identity information data of at least one subject from the mass enrollment center computing device to the subscriber computing device upon receipt of the payment signal from the payment provider server device.

2. The system according to claim 1, wherein the communication interface is operable to provide an automatic verification of matching of the health-related data with a predetermined message of the subscriber computing device, upon which the subscriber computing device is triggered to send a payment information to the payment provider server device.

3. The system according to claim 1, wherein the web platform server device is operable to store a first identifier of the mass enrollment center computing device and a second identifier of the subscriber computing device, and wherein the communication interface is maintained between the first identifier and the second identifier.

4. The system according to claim 1, wherein the web platform server device is operable to delete the temporary link site and the computer memory link location after transmission of the identity information data of the least one subject from the mass enrollment center computing device to the subscriber computing device.

5. The system according to claim 1, wherein the web platform server device is furthermore operable to receive identification data of a referred person from a referring subject, and award, upon registration of the referred person, gene credits to an account of the referring subject.

6. The system according to claim 1, wherein the web platform server is furthermore operable to attribute a third-party verification service to one or more registered subjects, wherein the attribution of the third-party verification service is randomized, and cause the third-party verification service to verify health-related data of the one or more registered subjects, wherein the health-related data is filtered according to exchange categories that are individually specified by the one or more subjects.

7. The system according to claim 1, wherein the web server computing device is furthermore operable to receive a health exchange category from each of one or more subjects, store the health exchange category of each of the one or more subjects, provide access to health-related data according to the stored health exchange categories, the health exchange categories being selected from genetic data relating to biochemical genetics, molecular genetics, clinical cytogenetics, preimplantation genetic screening or non-invasive prenatal testing, molecular diagnostics of infectious diseases, clinical trials, sharing of an existing specimen, providing a new specimen, radiology procedures, laboratory reports, electronic medical records and health-related data retrieved from wearable devices.

8. The system according to claim 1, wherein the web server computing device is furthermore operable to store health-related data of the at least one subject, receive a first evaluation of the health-related data based on the health-related data and based on at least one exchange category chosen by the at least one subject, and adjust, after receiving the first evaluation, the first evaluation based on a demand for the health-related data.

9. A method for encrypted exchange of personal medical and financial data, the method comprising: storing health-related data and identity information data of a multitude of subjects at a mass enrollment center computing device, receiving the health-related data and identity information data at a subscriber computing device via a communication interface, providing an encrypted communication channel between the subscriber computing device and the mass enrollment center computing device by a web platform server device, further comprising: creating a temporary link site with a temporary link site identifier and a computer memory link location; forwarding the temporary link site identifier to the mass enrollment center computing device and to the subscriber computing device; providing, by the temporary link site, a communication interface that allows the encrypted interchange of pre-determined messages between the mass enrollment center computing device and the subscriber computing device; using the computer memory link location for releasing the health-related data to the subscriber computing device; receiving a-payment information at a payment provider server device, and providing a payment signal to the web platform server device, and automatically initiating, upon receipt of the payment signal, a transmission of the identity information data of at least one subject from the mass enrollment center computing device to the subscriber computing device.

10. The method according to claim 9, further comprising providing an automatic verification of a matching of the health-related data with a predetermined message of the subscriber computing device.

11. The method according to claim 9, further comprising storing a first identifier of the mass enrollment center computing device and a second identifier of the subscriber computing device, wherein communication is maintained between the first identifier and the second identifier.

12. The method according to claim 9, further comprising deleting each of the temporary link site and the computer memory link location is deleted after the transmission of the identity information data of the least one subject from the mass enrollment center computing device to the subscriber computing device.

13. The method according to claim 9, further comprising: receiving identification data of a referred person from a referring subject, and awarding, upon registration of the referred person, gene credits memory equivalent to monetary value to an account of the referring subject.

14. The method according to claim 9, further comprising: attributing a third-party verification service to one or more registered subjects, wherein the attribution of the third-party verification service is randomized, and causing the third-party verification service to verify health-related data of the one or more registered subjects, wherein the health-related data is filtered according to either of exchange categories and digital gene assets, the either of the exchange categories and the digital gene assets being individually specified by the one or more subjects.

15. The method according to claim 9, furthermore comprising: receiving a health exchange category from each of one or more subjects, storing the health exchange category of each of the one or more subjects, provide access to health-related data according to the stored health exchange categories, the health exchange categories being selected from genetic data relating to biochemical genetics, molecular genetics, clinical cytogenetics, preimplantation genetic screening or non-invasive prenatal testing, molecular diagnostics of infectious diseases, clinical trials, sharing of an existing specimen, providing a new specimen, radiology procedures, laboratory reports, electronic medical records and health-related data retrieved from wearable devices.

16. The method according to claim 9, further comprising: storing health-related data of the at least one subject, receiving a first evaluation of the health-related data based on the health-related data and based on at least one exchange category chosen by the at least one subject, and adjusting, after receiving the first evaluation, the first evaluation based on a demand for the health-related data.

17. A computer-readable digital storage area comprising instructions which, when executed by a computer system provides the steps of a method according to claim 9.

Description

[0125] The subject matter of the present specification is now explained in further detail with respect to the following Figures in which

[0126] FIG. 1 shows a first embodiment of a medical information exchange system,

[0127] FIG. 2 shows a second embodiment of a medical information exchange system,

[0128] FIG. 3 shows a third embodiment of a medical information exchange system,

[0129] FIG. 4 shows a registration process of a subject in the medical information system,

[0130] FIG. 5 shows a method of connecting an individual subject with a third party,

[0131] FIG. 6 shows a method of linking a subscriber to a potential subject based on his query search and data indicators shows

[0132] FIG. 7 shows a method of connection between subjects and mass enrolment centers (MEC) and further on the exchange between subscriber and MEC,

[0133] FIG. 8 illustrates a method of handling a bulk communication request between a subscriber and an administrator,

[0134] FIG. 9 illustrates a configuration and a method for establishing a safe communication between to parties of the health data exchange system, and

[0135] FIG. 10 shows a communication between computer devices of communication partners shown in FIGS. 1 to 3,

[0136] FIG. 11 shows a further embodiment of a health information system,

[0137] FIG. 12 shows a flow of a recipient payment,

[0138] FIG. 13 shows a contributor registration,

[0139] FIG. 14 shows a recipient registration,

[0140] FIG. 15 shows a vendor commission program,

[0141] FIG. 16 shows a product purchase and a cashback flow,

[0142] FIG. 17 shows an allocation of discount vouchers to contributors,

[0143] FIG. 18 shows transactions following an establishment of an agreement between health data provider and vendor, and

[0144] FIG. 19 shows further transactions between health data provider and vendor.

[0145] In the following description, details are provided to describe the embodiments of the present specification. It shall be apparent to one skilled in the art, however, that the embodiments may be practised without such details. Although the above description contains much specificity, these should not be construed as limiting the scope of the embodiments but merely providing illustration of the foreseeable embodiments. Especially the above stated advantages of the embodiments should not be construed as limiting the scope of the embodiments but merely to explain possible achievements if the described embodiments are put into practise. Thus, the scope of the embodiments should be determined by the claims and their equivalents, rather than by the examples given.

[0146] The following FIGS. 1 to 8 explain a communication between individuals or communication partners which play a role in the transmission of medically relevant information. The FIGS. 9 and 10 illustrate the operation of the communication arrangement used in the health information exchange.

[0147] In a general sense, the present specification provides an arrangement for the secret and secure communication by providing a number of transmitting and receiving encryption devices that are set up in a particular manner.

[0148] The FIGS. 1 to 3 show three embodiments of an anonymous medical condition information and monetary exchange system, which are also referred to as “medical information exchange systems”, 100, 100′, 100″. The features of these embodiments can also be combined with each other.

[0149] In FIGS. 1 to 3, communication arrows are shown between the various communication parties, such as subject, subscriber, administrator, third party, payment platform, and web platform. The communication arrows refer to the communication or, in other words, the exchange of data messages between computers or devices of the communication parties.

[0150] The arrows represent communication channels 131-139, 203, 204. The communication channels can be encrypted communication channels, and in particular, the communication channel 135 between the mass enrolment center 14 and the subscriber 16 can be an encrypted communication channel 135.

[0151] Furthermore, a payment signal 3 from a payment provider server device 18 to a web platform server device 18 is indicated by an arrow 3 in FIG. 2.

[0152] For simplicity, the communication between the respective computers is illustrated in a further FIG. 10. When the specification below refers to a communication between communication parties, this refers to a communication between computers of the communication parties.

[0153] Furthermore, the mass enrolment center 14 also refers to a mass enrolment center computing device 14, the subscriber 16 also refers to a subscriber computing device 16, and the payment platform 18 also refers to a payment provider server device 18. For the purpose of showing the payment provider server device 18 and platform 20, the payment platform 18 is also shown separately in FIGS. 1-3 by a dashed line 18.

[0154] Specifically, in the following, a communication of the subject 12 with the payment platform 18 refers to a communication between the computer 11 of the subject 12 and the server 17 of the payment platform 18, a communication between the subject 12 and the third party 27 refers to a communication between the computer 11 of the subject 12 and the computer 26 of the third party, a communication between the third party 27 and the web platform 28 refers to a communication between the computer 26 of the third party and the server 13 of the web platform, a communication between the subject 12 and the payment platform 18 refers to a communication between the computer 11 of the subject and the server 17 of the payment platform, and a communication between the subscriber 16 and the payment platform refers to a communication between the computer 15 of the subscriber and the server 17 of the payment platform 18.

[0155] Furthermore, a communication between the subject 12 and the mass enrolment center 14 shown in FIG. 2 refers to a communication between the computer 11 of the subject and the computer 5 of the mass enrolment center 14, a communication between the mass enrolment center 14 and the payment platform refers to a communication between the server 13 of the mass enrolment center 14 and the server 17 of the payment platform 18.

[0156] Furthermore, a communication between the administrator 124 shown in FIG. 3 and the mass enrolment center 14 refers to a communication between the server 13 of the web platform 28 and the computer 5 of the mass enrolment center, a communication between the administrator 124 and the payment platform 18 refers to a communication between the server 13 of the web platform 28 and the server 17 of the payment platform 18, and a communication between the administrator 124 and the subscriber 16 refers to a communication between the server 13 of the web platform 28 and the computer 15 of the subscriber 16.

[0157] The communication between the devices takes place via a communication channel. A communication channel comprises the software infrastructure provided to enable the communication. For example, a communication channel for the communication between communication parties can be provided by the web platform 28. In a broader sense, a communication channel can also refer to the physical infrastructure provided for the communication, such as the hardware.

[0158] By way of example, the payment platform 18 can be provided by an internet service such as paypal or other credit or debit card payment services. The payment platform 18 can provide various modes of payment. In particular, the payment platform can provide gene credits 119, which are symbolized by a “$” sign in FIG. 1, and which are explained in more detail further below.

[0159] In the following, the user devices of the below mentioned communication partners, such as the user devices of the subject, the subscriber, the mass enrolment center and of the third party are also referred to as “computing devices”. The server of the payment platform and of the web platform are also referred to as “server devices”.

[0160] FIG. 1 shows a medical information exchange system 100. The medical information exchange system 100 comprises a first user device 11 of a subject 12, a second user device 15 of a subscriber 16, a third user device 26 of a third party 27, a first server device 17 of a payment platform 18 and a second server device 13 of a web platform 28, which provides services for the users 12, 16, 27 of the web platform 28.

[0161] The web platform 28 has an administrator, which is not shown in FIGS. 1 and 2, but which is shown in FIG. 3. The functions provided by the administrator can also be provided by an administrator program with preconfigured settings.

[0162] In the example of FIG. 1, the subject 12 and the subscriber 16 are represented by individuals which operate the respective user devices 11 and 15. The third party 27 provides the functions of verification and counselling that allows a large number of subjects 12 to get their health data verified or get counselling for a specific health situation.

[0163] In further embodiments, the subject 12 and/or the subscriber 16 comprise an autonomous program running on a user device 11, 15 or on the server 13 which performs its task according to predefined settings.

[0164] The respective server computers 17, 13 of the web platform 28 and of the payment platform 18 of FIG. 1 comprise computer memory on which programs and data are provided for handling tasks of the users 16, 12, 65 and of the payment platform 18, and of the web platform 28 respectively.

[0165] The server computer 13 of the web platform 28 comprise, among others, a database 19 for storing, among others, health related data 19/1 provided by the subject 12 and identification information 19/2 or identification data 19/2 of the subject 12, third party 27 and of the subscriber 16. Furthermore, the database 19 may also contain the amount and type of data previously requested by the subscriber 16 for various purposes, for example for automatically providing an offer to the subscriber 16. Similarly, the server 17 of the payment platform 18 comprises a database 20 for storing payment information.

[0166] In the following, an operation of the health information system 100 is explained by one of many possible usage scenarios. During operation, the subscriber 16 requests a pre-defined health information from the subject 12 by sending a request message 8 to the subject 12. The predefined health information can be selected from a graphical user interface (GUI) which is provided by the web platform 28. For example, the GUI can be generated dynamically using a GUI description language and based on user profile and other data stored in the database 19. By way of example, the GUI can be provided through a web application frame work such as Ruby on Rails or TurboGears, among others.

[0167] For example, in one embodiment the GUI includes an anonymous information exchange program with pre-defined selectable information which is presented to the subscriber once the subscriber has paid a contact fee to the payment platform 18.

[0168] During the course of communication, if the subscriber 16 wants the data provided by subject 12 to be verified, the subject 12 sends a verification request 9 to the third party 27.

[0169] In general, the communication between subscriber 16 and subject 12 can involve more steps than the abovementioned communication steps, for example steps for obtaining a consent of the subject or for successively determining whether the provided information of the subject 12 is relevant for the subscriber 16.

[0170] Furthermore, the communication between subscriber 16 and the subject 12 can be handled automatically with message queues. The message queues may be implemented by an application which runs on the server 13. The three parties 12, 16, 27 are prevented from viewing personal identification information which allows them to communicate outside the server 13 until the final payment is made to the payment platform 18.

[0171] Once the payment is approved by payment platform 18, the identification information is visible to the respective parties, after which they can communicate outside the server 13 for exchange of information.

[0172] In an embodiment which comprises a health provider, and which is also explained further below with respect to FIG. 2, a health provider forwards an information request message to the subject 12. If the subject 12 decides to release health related information and sends back a response message to the health data provider, which forwards the response message to the subscriber 16.

[0173] In general, the communication between subscriber 16 and a subject 12 can involve more steps than the abovementioned communication steps, for example steps for obtaining a consent of the subject or for successively determining whether the provided information of the subject 12 is relevant for the subscriber 16.

[0174] Furthermore, the communication between subscriber 16 and subject 12 can be handled automatically with message queues. The message queues may be implemented by an application which runs on the server 13 of web platform 28 or they may also be implemented using functionality provided by social media platforms. By using message queues, the messages can be exchanged when the respective party to the automated communication is responsive.

[0175] The server 13 is of the web platform 28 is used as a messaging platform to exchange messages between the subscriber 16 and the subject 12. In other words, the web platform 28 as an intermediate for a data exchange between the subscriber 16 and the subject 12. Thereby, the web platform 28 has control over the type of information which is exchanged between the two parties 12, 16. According to one embodiment, the web platform 28 does not provide personal identification data that would allow the subscriber 16 or the subject 12 to identify the respective other party 12, 16.

[0176] Furthermore, the web platform 28 allows only the exchange of pre-determined information—and not freely generated messages by the subscriber 16 or the subject 12—between the two parties 12, 16. The pre-defined information can in particular refer to predetermined messages. As a consequence, the two parties 12, 16 are prevented from exchanging identification information with each other which would allow them to contact each other without using the health data provider 14 and without making any payment to the health data provider 14. This applies to all embodiments of the specification.

[0177] The subject 12 makes payment for using the web platform server 13 to offer the subject's 12 health information to subscribers 16 by way of sending a payment message to the payment platform 18, which acknowledges the payment by sending an acknowledgement message. The payment platform 18 then informs the web platform 28 by sending a notification message to the health data provider 14.

[0178] As a further option, the subject 12 can make the payment for the use of the web platform 28 as a deposit which is reimbursed partially or in full when data of a predefined amount and quality is delivered to a subscriber.

[0179] In a simple embodiment, a monetary value of the data provided by the subjects 12 is estimated based on the content of a data input interface which is filled out by the subject. For example, an evaluation can be based on stored standard value estimates for providing information pertaining to certain types of genetic defects. Furthermore, the value of the provided information can be dynamically estimated based on the monitored demand for that type of information. Moreover, the web platform 28 can provide mechanisms to estimate a value of the data of the subjects 12 based on input data provided by a third party, such as experts or specifically trained evaluation personnel.

[0180] FIG. 2 shows a further embodiment of the health information exchange platform system 100′. The same or similar parts are indicated by the same or similar reference numerals.

[0181] In addition to the features shown in FIG. 1, the embodiment of FIG. 2 comprises a mass enrolment center 14 that acts as an intermediary between subject 12 and subscriber 16, which uses the same server 13 and database 19 as shown in the previous FIG. 1. By way of example, the mass enrolment center can be provided by a health data provider, such as a hospital. The mass enrolment center 14 has a computer or computer system 5, which carries out the exchange of data messages shown in the Figures.

[0182] The subject 12 has an option to associate with the mass enrolment center 14 by accepting a consent handing over connection and exchange process through server 13 to the mass enrolment center 14. During operation, the subscriber 16 requests a pre-defined health information from the mass enrolment center 14 by sending a request message 8 to the mass enrolment center 14.

[0183] By way of example, the predefined health information can be selected from a graphical user interface (GUI) which is provided by the mass enrolment center 14. For example, the GUI can be generated dynamically using a GUI description language and based on user profile and other data stored in the database 19.

[0184] The mass enrolment center 14 then selects from among the associated subjects 12 according to the profile sent by subscriber 16. According to one mode of operation, the mass enrolment center 14 does not provide personal identification data that would allow the subscriber 16 or the subject 12 to identify the respective other party 12, 16.

[0185] The subscriber 16 pays for the link through the payment platform 18, after which the link process takes place on server 13. For example, in one embodiment the GUI includes an anonymous information exchange program with pre-defined selectable information which is presented to the subscriber once the subscriber has paid a contact fee to the payment platform 18.

[0186] In general, the communication between the subscriber 16 and the mass enrolment center 14 can involve more steps than the abovementioned communication steps, for example steps for obtaining a consent of the mass enrolment center 14.

[0187] Once the final payment is made through payment platform 18, the contact information is displayed to the subscriber 16 of the mass enrolment center 14 and vice versa, after which they can communicate outside the server 13 for exchange of information. The transfer of money between the mass enrolment center 14 and subject 12 also takes place outside server 13 as consented.

[0188] According to a further embodiment, the web platform 28 provides a query server which is used as a proxy for the subscriber 16 for managing health data queries. The query server retrieves data from the database 19, which comprises profile information about the type and amount of information the subscribers are interested to obtain and about past queries.

[0189] During operation, the query provider receives a requirement profile from the subscriber 16 and uses the requirement profile to generate an automated data exchange between the query provider and subjects 12 or between the query provider and the database 19 of the server 13, which contains health information of subjects 12 that matches with the requirement profile. A data transfer message 7 between the respective subjects and the mass enrolment center 14 is indicated in FIG. 2, which can comprise among others an information request, the corresponding released information and consent data.

[0190] FIG. 3 shows a health information exchange platform arrangement 100″ providing bulk communication requests to subscribers 16, which allow the subscribers 16 to get into contact with multiple subjects 12. The same or similar parts are indicated by the same reference numerals. Additionally, the concept of an administrator 124 has been introduced.

[0191] In the health information exchange system 100″ of FIG. 3, an administrator 124 is used as a proxy for the subscriber 16 for managing health data queries. The administrator 124 uses the web platform 28 for carrying out his tasks. As mentioned before the tasks of the administrator 124 can also be provided by a program running on the server 13 with preconfigured settings.

[0192] During operation, the administrator 124 receives a requirement profile from the subscriber 16 and uses the requirement profile to generate a search for subjects 12 or, alternatively, between the administrator 124 and the database 19 of the server 13, which contains health information of subjects 12 that matches with the requirement profile.

[0193] The administrator 124 provides a list of subjects 12 to the subscriber 16 after a connection fee payable through the payment gateway 18. Once the payment is verified the further exchange process between the subject 12 and subscriber 16 will take place as per the process of FIG. 5.

[0194] For simplicity, the administrator 124 of the web platform 28 is only shown in FIG. 3 for highlighting the functionality provided by the administrator 124 in the context of the embodiment of FIG. 3. An administrator 124 is not shown in FIGS. 1 and 2 although an administrator 124 is also present in the other embodiments.

[0195] In the following, a finance model using gene credits is explained. The account of subject 12 is auto-credited with gene credits 119, through the following mechanisms. [0196] Registration of subjects 12 on website server 13. [0197] Transaction between subject 12 and subscriber 16 on server

[0198] A percentage of transaction value is auto-allocated as gene credits 119 to the account of subject 12. [0199] Transaction between the mass enrolment center 14 and subscriber 16 on platform 18. A percentage of the transaction value is auto-allocated as gene credits 119 to subject account. [0200] A percentage of the company's profits is transferred to the account of subject 12 as gene credits 119, wherein “the company” is the company that operates or owns the web platform.

[0201] These gene credits 119 amount to a dollar value shall be exchanged and used to provide a free or discounted list of genomic tests 120.

[0202] The gene credits 119 translate to cash which shall be pushed back to the subject 12. The gene credits 119 translate at a later date to ownership of the company and shares in the company.

[0203] In the following, a finance model based on free tests is explained. This finance model is developed to have a self-sustaining construct, pay for free tests and build a database of whole genome sequence at a global level. It also provides cash benefits to Subjects in addition to potential free tests.

[0204] Gene credits 119 are used to provide a default list of genomic tests default list of genomic tests 120 to subject 12 for free or at a subsidized rate. The list of available tests is determined by the administrator 124. The list of tests includes but is not limited to whole genome sequencing. The company that operates the web platform 28 preferentially provides this default list of tests free to subjects 12. However, the subject 12 may also purchase gene credits to purchase the listed test 120.

[0205] Preferentially, the operator of the web platform 28 procures the test from its subsidiary company and or its affiliates although it may also be provided by the web platform 28. The subsidiary company shall organize testing and logistics. The free test information and data shall be posted on subject account 12. This shall be pre consented at the time of registration as a precondition to provide free test.

[0206] According to one embodiment the web platform 28 provides free tests including but not limited to whole genome sequencing (WGS) of an individual. WGS, full genome sequencing, complete genome sequencing, or entire genome sequencing) is the process of determining the complete DNA sequence of an organism's genome at a single time. This entails sequencing all of an organism's chromosomal DNA as well as DNA contained in the mitochondria and, for plants, in the chloroplast. In practice, genome sequences that are nearly complete are also called whole genome sequences.

[0207] Sequencing can generate a large amount of data. This data shall be available for research and for science through server 13. With improvements in artificial intelligence and informatics this data, if reanalysed at a later date in time, can provide new medical and health information to the subject. The company shall provide this service of data reanalysis of free tests for a fee at a subsequent period in time.

[0208] Furthermore, the health data provider can provide reanalysis packages for cancer predisposition or ancestry testing.

[0209] According to a further example, the health data provider provides free personalized genomic tests for contributors every month and subsidizes exome and tumor tests with a test provider. The test provider executes the tests. Thereby, the health provider can expand its test menu and increase and expand its geographic presence. The test provider sends the test data back to the health data provider for automatic update on the web platform. This enhances the data basis of the health provider which can be searched by the recipients, which enables the health data provider to provide more free tests and gene credits to the contributors.

[0210] In the following, a further finance model is explained, which is based on a genomic stock exchange. This is a concept based on the fact that the administrator 24 is able to create digital gene assets on server 13 and ascribe a fixed monetary value to each.

[0211] The platform 13 allows for a link between subject 12 and subscriber 16 to perform sale and purchase activity. Therefore, there is a volume of transaction and number of transactions linked to each GSC. This allows for development of a new platform called genomic stock exchange. This new platform can be realized on the web platform 28, the payment platform 18 or a separate provider not shown in FIGS. 1-3.

[0212] The web platform 28 allows for Trade of genetic stock exchange (GSC) shares as commodities. A trade transaction on platform 28 generates a revenue. A percentage of this revenue shall be passed back to the account of subject 12 as gene credits 120. Gene credits are used to provide free test and cash benefits to subjects.

[0213] FIGS. 4 to 8 show processes carried out by the medical information exchange system 100, 100′, 100″. In particular, FIGS. 4 to 8 illustrate the processes of registration of a subject, carrying out a communication between a subject and a third party, carrying out a communication between a subscriber and a subject, FIG. 4 shows a workflow for a registration process. First, the subject 12 reviews and sees the website hosted on server 13 on his user devices 11.

[0214] In a step 30, the subject 12 chooses to register on the server 13. In a step 31, all the information on the server 13 is auto populated and, in a step 32, the subject 12 chooses from default options predefined on the server 13 to populate the password encoded secure account of subject 12 which is hosted on server 13 in a step 33. There is automation to allow ease of registration.

[0215] While registering, the subject 12 provides personal demographic information including age and gender apart from other information which may be useful for the subscriber 16 in a step 34. To simplify registration, the subject 12 inputs demographic data in step 34. Then subject 12 signs on which digital gene assets he is willing to share, and then creates an account using e-mail verification, including agreeing to consent. In case of payment he pays at the time of creating an account. The account is created first, and the health and genetic information can then be updated at the same time or later by the subject after the simple registration.

[0216] The subject 12 then provides health information which is information related to health and disease in a step 35. The subject 12 may be healthy, apparently healthy, or diseased. Subjects with any kind of available health information are invited to register on the website platform hosted on server 13.

[0217] The subject 12 then proceeds to provide available genetic information which he has readily available and is willing to share on the platform 13 and with subscribers 16 in a step 36. The subject 12 then selects from default options which exchanges category he is willing to sell in a step 37. The predefined options may comprise for example willing to exchange specific genetic data, register for research trials or share a specimen. For every digital gene asset that the subject 12 is willing to opt for, the account is credited with gene credits in a step 38.

[0218] The subject 12 then provides details about the genetic data which is stored internally on the server 13 and which is linked to a rate fixed by the administrator 24 of the web platform 28 in a step 39.

[0219] All digital gene assets and data category are linked to default recommended rates fixed by the administrator 24. Only the administrator 24 is authorized to create new digital gene assets.

[0220] There is an option for mass enrolment center 14 to negotiate a rate with the administrator 24. The difference in rates is based on geographical and finance concerns of the subject 12 or mass enrolment center 14. As a further option, if data with Subject 12 does not fall into the provided digital gene assets, the subject 12 may contact administrator 24 to create a new category in an optional step 40.

[0221] To increase the data on the subject's account 12 which is used for profiling and search by subscriber 16 or mass enrolment center 14 or administrator 24, free text description of health state is permitted, though limited by number of characters used. In another unique workflow feature, the website on server platform 13 allows the subject 12 to opt for which of the data shall be made visible to subscriber 16 in a step 41. Once registration of the users 16, 12 or 14 is complete on server 13, an email verification is sent to verify these users in a step 43.

[0222] The server 17 allows for two kinds of subjects to create an account: standard subjects 12 and premium subjects 12′. A premium subject 12′ pays fees to the web platform 28 via the server 13 of the web platform 28 while registering using payment platform 18. A premium subject 12′ gets Free gene credits while registering. No real time data is posted on the server 13. Only information about the availability and willingness to share is posted on server 13.

[0223] An automated consent is obtained during registration from all the users 16, 12 and 14 agreeing to terms and conditions in a step 42.

[0224] FIG. 5 shows a workflow of connection between an individual subject 12 and a third party 27. More specifically, FIG. 5 shows a method of connecting an individual subject with a third party, such as a medical examiner, for the process of verification of reports, raw data, result or test.

[0225] In a first step 51, the subject 12 registers on the website 28 using the subject registration form, entering his personal data as well as health information.

[0226] After the registration, in a step 52, the subject adds the billable categories/data for the exchange process. For the subject 12 to get the data verified, a consent is generated at step 53 before the start of the verification process.

[0227] In a decision step 54 it is decided whether a consent has been obtained. If the consent is obtained in the decision step 54, a third party is selected in a step 55 for the verification process from a list of all the available third parties 27. The subject 12 selects the third party 27 through a filtered list of third parties based on country, state and city. The he can select any suitable third party 27 and proceed to get counselling or verification.

[0228] If it is decided in step 54 that a consent could not be obtained, the process loops back to step 53 to generate a new consent request.

[0229] In a further step 56, a payment request for a fixed amount is generated. Once the payment is successfully verified in a step 57, the subject 12 receives the contact information of the third party to send in the data to be verified in a step 58.

[0230] A verification request is displayed on the third-party portal in a step 59. The actual handoff of data occurs through email or physically outside the web platform 28, or, in other words, outside the web application provided by the web platform 28.

[0231] Once verification is complete in step 60, the third party assigns the status of “verified” or “failed” to the particular billable category on the subject side in step 61.

[0232] According to a further embodiment, a third-party verification is carried out without selection by a third party or a recipient. Instead, the system or the health data provider web site autogenerates or auto-selects a third-party verifier with whom a link is created to verify data. Thereby a selection bias can be avoided.

[0233] FIG. 6 shows a workflow of connection between an individual subject 12 and a subscriber 16. Specifically, FIG. 6 explains the method of linking a subscriber 12 to a subject 12 matching the requirements of the subscriber 12 and based on the query search and data indicators of the subject 12.

[0234] In a first step 72, a set of query items is selected. In step 73 a request is sent to the potential subjects 12. Once the request is accepted in step 74, a link is established between the potential subjects and the subscriber in step 76, respectively. Otherwise, the request is deleted from both ends in step 75.

[0235] The Subscriber pays a fixed amount for link setup in step 77, after which consent is generated in step 78. In a decision step 79, it is decided whether a signed consent has been obtained from the subject.

[0236] If it is decided in step 79 that a signed consent has been obtained, the subscriber has an option to choose from available reports (billable categories) in step 80. If it is decided, in a decision step 81, that a verification is required, step 82 is followed wherein the subject gets their data verified by the third party by branching to step 53 of FIG. 5 and completing step 53.

[0237] Once the data to be exchanged between the parties is agreed upon, an automated anonymous information exchange negotiation feature is available in step 83 for them to finalize upon the price. During an amount negotiation the subject 12 either agrees to a recommended rate or disagrees. If the subject 12 does not agree, the subject is the first person allowed to start a negotiation. He is allowed to choose a value within a fixed percentage up or down from the recommended rate, such as plus or minus 10%. The subscriber 16 either agrees or recommends a different rate, again ranging 10% up or down from the recommended rate. The subjects 12 then accepts or declines. Only this much of negotiation is allowed.

[0238] Payment is requested in step 84 and is made by the subscriber 16 through a secure payment gateway in step 85, after which contact information of the subject 12 is provided to the subscriber and the contact information of the subscriber 16 is provided to the subject 12 in step 86. The actual exchange of data happens via mail or physical hand-off outside the web platform 28.

[0239] FIG. 7 shows the establishment of a connection between subjects 12 and mass enrolment centers (MEC) 14 and furthermore an information exchange between subscriber 16 and MEC 14. The establishment of the connection, which comprises steps 87-93 of FIG. 7, is described by a first workflow below and the information exchange, which comprises steps 94-102 of FIG. 7, is explained by a second workflow below.

[0240] FIG. 7 shows a work flow of connection between subjects 12 and mass enrolment centers (MEC) 14 or a health data provider.

[0241] The MEC will register on the website through the MEC registration form in step 87. On registration, the MEC 14 will be provided with a unique identification code (UID) in step 88. This UID will be used to link the subjects 12 with the MEC 14.

[0242] While registering, in step 89 the subject 12 will enter the UID associated with MEC and will be provided with an option that gives consent to the MEC for handling all their exchange processes and receiving payments on their behalf and that the provider of the web platform 28 will not be liable for distribution of money between the MEC and subjects in step 90.

[0243] A two-tier security is inbuilt. At the first level, the identities of the subjects 12 remain hidden and can be identified by the administrator only through the unique identification code (UID). At a second level, a security password is provided to the administrator 124, who can then identify personal information, which is accessible by the username and password of the user. This access is provided to the administrator 124 in order to enable the administrator to access transaction data such as payment transfers or gene credit cashbacks. As a further security feature, an automatic logoff timer is provided for the administrator account.

[0244] Among others, the health information system 100, 100′, 100″ provides the following security features:

[0245] The health information system provides an SSL-protected connection between the communication partners and between a communication partner and the web site. Thereby connections to other sites and the server linked to the website provided by the web platform 28 can be secured.

[0246] To that end, the web server 13 provides an implementation of SSL certificate to make the website respond to https (hypertext transfer protocol—secured) queries, for example by purchasing and implementing a third-party SSL certificate for the website from a reputed certification authority. Furthermore, a testing of the strength of the certificate is carried out from the service provider's end as well as the developer's end. The SSL communication is an example of an encrypted communication channel.

[0247] Moreover, the health information system 100, 100′, 100″ provides an anti-forgery token implementation. This implementation includes among others the following features: prevention of cross site request forgery attacks, and thereby preventing forms used for login ID and passwords, throughout the website from being forged onto another dummy website, not displaying passwords in clear text. Including the anti-forgery token into the framework of the website.

[0248] Furthermore, the health information system 100, 100′, 100″ provides an advanced encryption standard, preferentially a 128 bit AES, to encrypt the data throughout the website. By using this encryption, the transferred data can be encrypted on the redirected websites as well. In particular, the AES 128 bit encryption can be implemented and tested through the SSL certificate implementation.

[0249] Moreover, the health information system 100, 100′, 100″ provides an exclusive end-to-end communication between the subscriber 16 and the subject 12 will be exclusive. In particular, the anonymous information exchange between subscriber 16 and subject 12 can make use of the AES 256 bit encryption.

[0250] A further security feature provided by the web site is payment gateway security. In particular, a payment gateway security can be implemented by reputed service providers and it can be implemented on PCI DSS standards (payment card industry data security standard).

[0251] Furthermore, the health information system 100, 100′, 100″ can provide periodic assessment of security, which may be carried out in an automated, partially automated or manual way.

[0252] According to one scheduling of the security monitoring, the security monitoring of the website takes place every month and the assessment will comprises the following elements. [0253] Vulnerability assessment—Determining if there are any web related vulnerabilities on the website. [0254] Penetration testing—Assessment of the risk caused to the website due the vulnerabilities. [0255] Patching—Implementing corrective measures for the vulnerabilities [0256] Testing of the following parameters and their corrective measures, wherein test reports for these tests can be submitted with the assessment monthly: [0257] Storage of an unknown code in the website framework—cross site scripting (XSS) [0258] Unauthorized log in to the website through a dummy website [0259] Cross Site Request Forgery (CSRF) [0260] Strength of the SSL certificate and encryption—Heartbleed vulnerability assessment. [0261] Login through arbitrary SQL query on the website—SQL injection. [0262] Denial of service attacks. [0263] Testing for server errors which can give access to website database.

[0264] If it is decided in step 91 that the consent is signed, the subject 12 will only be receiving notifications on the exchange processes happening but will have no control on handling the exchange process. The registration is completed in step 93, when it is detected in decision step 91 that a signed consent has been obtained. Otherwise, a message is sent to the subject for which no consent has been obtained to register as an individual subject in step 92.

[0265] On the other hand, the MEC will be signing a consent in step 87, saying that they are appointed on behalf of the subjects 12 and will be receiving payments for the entire exchange process. Furthermore, the consent includes a statement that the provider of the web platform 28 will not be liable for distribution of money between the MEC and subjects 12.

[0266] Furthermore, FIG. 7 shows a workflow of connection between MEC and Subscribers.

[0267] The MEC has a general profile of the type of subjects 12 associated with them according to which the subscriber 16 can send a connection request to the MEC in step 94. Once the MEC accepts the subscriber request, it sorts through the associated subjects in step 95 according to the subscriber requirements and creates a connection.

[0268] The subscriber 16 pays a fixed amount, which depends on the number of subjects 12, for the link to the web platform 28 in step 96 and then a consent is generated in step 97. After it is decided that the consent is successfully signed between the MEC 14 and the subscriber 16 in step 98, an automated anonymous information exchange feature will be provided for amount negotiation between the MEC 14 and the subscriber 16 in step 99.

[0269] Once the amount is finalized and payment requested in step 100, the subscriber 16 makes the payment in step 101 and both MEC 14 and the subscriber 16 will be able to view each other's contact information in step 102. At a later stage, the exchange of actual data will be done on a mail or by a physical handoff outside the web platform 28.

[0270] FIG. 8 shows a work flow of connection between subscriber and admin. More specifically FIG. 8 illustrates a bulk communication request between the subscriber 16 and administrator 124.

[0271] The subscribers 16 have an option to provide search and connection control to the administrator 124 of the website as query provider. The administrator account is preferentially handled by one of the members from the web platform 28.

[0272] In step 103, a bulk communication message is generated. A subscriber 16 chooses the administrator of the health information exchange system as the query provider in step 103. Next, a consent is generated in step 104. On deciding that the consent has been signed and accepting the consent in step 105, the administrator 124 takes control for subject search and sending out requests on behalf of them in step 107. The subscriber 13 for that period of time can only view the process on the portal.

[0273] If it is decided that the consent has not been signed in step 105, the control is returned to the subscriber 13 and the process loops back to step 51 of FIG. 5. The administrator 124 selects the subjects according to the filters or query items provided by the subscriber in step 108 and sends out connection requests to them in step 109.

[0274] Once it is decided that a response is received from the subjects 12 and the request is accepted in step 110, the administrator request a link payment in step 113 and sends the list of subjects 12 to the subscriber 16 after the link payment in step 112. If the request is not accepted in step 110, the request is deleted, and the process ends in step 111. Similarly, if no payment is generated in step 113, the control is returned to the administrator 124 in step 114, and the administrator decides about further steps to be taken.

[0275] The control is handed over in step 115 to the subscriber 16 for further process of signing the consent, selecting from the digital gene assets and for making the exchange payment, similar to the individual subject-subscriber connection, as described above with reference to FIG. 5.

[0276] FIG. 9 illustrates a method of providing secure information exchange in a health information exchange system 100, 100′, 100″ according to the present specification.

[0277] According to this method, the web platform 28 creates a link site with a unique identifier when a communication between two parties is required, for example a communication between a subscriber 16 wanting to obtain health or genetic information from subjects 12 and a mass enrolment center 14. The link site can use website technology, for storing and displaying information, and also communication means, such as messenger technology for exchanging message between the mass enrolment center and the subscriber.

[0278] The link site is created as a temporary link site, which implies that after an expiry condition is fulfilled the link site is no longer available or is no longer available for the intended communication for which the link site was created. The temporary link site is thereby made unavailable, which is also referred to as “deleting” the link site. For example, a provided link can point to some static information or to an error message page after deletion of the link site. By providing the link site as a temporary link site, the security can be increased.

[0279] Different from generating only a temporary link to information in the masse enrollment center computing device 14, providing a temporary link site enables collection of additional data, such as communication data or pre-determined messages. By doing so, the matching between the subscriber 12 and the subject 16 can be improved.

[0280] By way of example, an information about the subject 12 can be provided in the following data structure

TABLE-US-00001   subject { identity information; subject identifier code; health data type; genetic data type; },
in which “health data type” and “genetic data type” provide generic information about the type of health data or genetic data being provided by the subject, but not the genetic data and/or the health data itself. This “health data type” and “genetic data type” data is stored on the database 19 of the server 13. The identity information is personal data of a subject and it is—unless sent out automatically to a communication partner for concluding a transaction—only accessible to the administrator 124. The other parties, such as the third party 27, the subscriber 16 or the payment system 18 only know the identifier, here referred to as “subject identifier code”.

[0281] By way of example, the data structure or part of it can be passed over the net as part of a response to an information request, for example using JSON or an XML query. By only storing and transmitting generic data it can be prevented that any party to the communication gains direct access to the detailed identity information. As a security measure, the actual genetic data and health data is not stored on the server 13 but is only retrieved from the subject 12 and stored on the server 13 once the subject 12 has made a payment, or after the subject 12 has made the payment.

[0282] According to one example of releasing the identity information data, the web platform server 13 automatically initiates a transmission of identity information data of a subject 12 after the server 13 of the web platform 28 has received a corresponding payment signal from the server 17 of the payment platform 18 or, in other words, upon reception of the payment signal.

[0283] The parties to the communication, for example a subscriber 16 and a mass enrolment center 14, can only exchange information via predefined messages. This is illustrated in FIG. 9 with GUI input masks 121, 122 having GUI input elements. The GUI input masks provide an example of a communication interface 121, 122. Alternatively, the same or similar functionality can also be provided by a command line interface or another standardized exchange of messages. The last two options facilitate automated communication, for example at the end of the mass enrolment center 14, where a party to the communication can be represented by a program, a batch script or the like.

[0284] The GUI, the command line interface, and the standardized message exchange provide examples of communication interfaces. Preferentially, the messages that are exchanged using the communication interface are encrypted by one of the abovementioned methods, such as SSL, AES encryption and so forth.

[0285] A communication between the two parties is established via a communication infrastructure 123, which includes the software, hardware and data-structures required to establish and maintain the communication.

[0286] During runtime the GUI elements of the input masks 121, 122 are filled with the predefined options available from the database 19. By way of example FIG. 9 shows a combo-box with pre-defined elements, an option field with pre-defined options and a button for loading a query generator, which a party to the communication can use to generate a query using predefined elements from the database 19 according to pre-defined rules, which may be stored in the code, the database, in configuration files or elsewhere.

[0287] At the beginning of a communication request, a subject 12 checks the identity of the website provided by the web platform 28 and selects a health provider or a mass enrolment center 14 for submitting his or her data.

[0288] After that, a program of the web platform 28 and/or the administrator 124 of the web platform 28 invites the subject 12 to pay a fee. The subject 12 provides payment by interchanging communication signals with the payment gateway 18. This process in shown in FIG. 9 by a double arrow.

[0289] After receiving the payment from the subject 12, the web platform 28 creates a link site 125 with a unique identifier 126, such as a dedicated IP address 126, and permits communication over the link site with a communication partner, such as a subscriber. In particular, the link site 125 can be created on the server 13 using an available pool of IP addresses which has been obtained by the provider of the web platform 28 and which is indicated in FIG. 9 by the placeholders “yyy.xxxx”.

[0290] The temporary link site 125 and the temporary link site identifier 126 are provided stored in a computer memory link location 129, which may be provided in a read and write memory or by a read only memory. The temporary link site 125 comprises the communication interface 121, 122, among others. The communication interface 121, 122 is adapted for the exchange of predetermined messages between the mass enrolment center computing device 14 and the subscriber computing device 16.

[0291] Furthermore, the web platform 28 stores the respective IP addresses 127, 128 of the communication partners, which allows to re-establish the communication when it is interrupted and to include the IP addresses into a protocol. The protocol can be used, among others, to trace back a communication partner after the communication is terminated.

[0292] After a termination condition is satisfied, the web platform 28 terminates the link site 125, after which the link site 125 is no longer available under the earlier provided IP-address or, as an alternative possibility, the link site 125 is available but it does not display a communication dialog or interface as before but some other information.

[0293] Among others, the method shown in FIG. 9 can reduce a delay of providing the health information. This can be advantageous for example if patients die between the diagnosis and the matching between subject 12 and subscriber 16, a large amount of data can be covered, a corruption of the data can be made less likely and a data protection can be improved.

[0294] By way of example, a matching of data between the provided data of the subject 12 and the required data of the subscriber 16 can be carried out as follows. The required data of the subscriber 16 is transmitted from the computing device of the subscriber to the web platform 28 in the form of a predetermined message. The server 13 of the web platform 28 determines whether the provided data of a subject 12 or of multiple subjects 12 falls within the scope defined by the predetermined message of the subscriber 16. When this is the case, the server 13 triggers a further action, such as sending a payment request message to the computing device 15 of the subscriber 16. When the server 13 receives a message that the payment has been made, it performs further steps to enable the computing device 15 of the subscriber 16 to establish a communication with the computing device 11 of the subject 16 and to retrieve the required data. Thereby, an automatic verification of a matching of health-related data is provided. Herein, a computing device 11 of a subject 16 can also be represented by a proxy device, such as a computing device 5 of a mass enrolment center 14.

[0295] The abovementioned method of establishing a communication between communication partners of FIG. 9 further provides that the administrator 124 is not able to see the connection or communication channel between the subject 12 and the subscriber 16, which increases the degree of protection of personal data.

[0296] According to a second level of security, an operator or administrator of the web platform 28 is prevented from seeing the detailed information exchanged between the matching subject 12 and subscriber 16.

[0297] In the same way that the mass enrolment center 14 can provide a payment to the payment platform 18 and thereby trigger an action of the web platform 28, other communication partners, such as the subscriber 16 or even the web platform 28 can also provide a payment to the payment platform 18. This is symbolized by double arrows in FIG. 9. For example, the provision of the link site can be made when the mass enrolment center 14 and/or the subscriber 16 have provided a payment to the payment platform 18.

[0298] FIG. 10 shows the exchange of data, especially data pertaining to health related and payment related information between the computing devices of the various communication parties. In principle, a data change can take place between any two computing devices of the respective communication parties, which is illustrated by the arrows of FIG. 10.

[0299] In order to achieve this, the arrangement for the secret and secure communication provides a number of transmitting and receiving encryption devices that are set up in a particular manner, as described above with reference to FIGS. 1, 2, and 3.

[0300] The web platform 28 with the second server device 13 and with the database 19, the first user device 11, the second user device 15, the third user device 26, the payment platform 18 with the first server device 17 and with the payment platform database 20, and the MEC user device 5, form an arrangement for exchanging encrypted information over the a communications network, such as the Internet.

[0301] The arrows between the aforementioned devices represent communication links that transmit data and signals from one device to another device. A signal can also take the form of a data message. In particular, the signal can be an electric signal, or a signal in the form of an electromagnetic wave which carries the data.

[0302] In other words, the participants to the exchange of personal medical and financial data do not communicate directly with each other, but they communicate by providing inputs to the aforementioned devices or by reading outputs from these devices.

[0303] Some of these communications are automatic, such as the emission of a payment signal before establishment of a matching or the transmission of personal identity information upon matching.

[0304] Some of these communications can only be provided upon establishment of a link site that has been created by the web platform.

[0305] Some of the communications are based on a number of predetermined messages, such as the negotiation between the first user device 11 and the second user device 15.

[0306] None of the communications provides individually generated messages, and all communications can only take place between the pre-determined communication partners.

[0307] FIG. 11 shows a further embodiment of a health information exchange system 100′″ in which a health data provider 29 is connected to mass enrolment centers 5, consultants 27, recipients 16, associated service providers 130 or partners 130, and contributors 12 over respective communication links in a star topology. The star topology implies that communications between the parties 5, 12, 16, 27, 130 are directed over the health data provider 29, which functions as a switching center or communication broker between the respective communication partners.

[0308] The associated service providers 130 provide goods and/or services for the benefit of the other parties 5, 12, 16, 27 via the health data provider 29. For example, they can be vendors of products, insurance providers, tour operators, providers of medical tests and so forth.

[0309] In the health information exchange systems 100, 100′, 100″ of FIGS. 1-3, the health data provider 29 is represented by the web platform 28, which comprises the health provider database 19 and the first server 13. The contributors 12 of FIG. 11 correspond to the subjects 12, the recipients 16 of FIG. 11 correspond to the subscribers 16 and the consultants 27 of FIG. 11 correspond to the third parties 27.

[0310] FIG. 12 illustrates a flow of direct payment 131 from a recipient to a contributor 12, to a mass enrolment center 5, to a health data provider 29. Furthermore, FIG. 12 shows a flow of indirect payment 131 from a recipient to a contributor 12 via a mass enrolment center 5, and from a recipient to a contributor 12 via the health data provider 29.

[0311] FIG. 13 illustrates a registration of a contributor at the health data provider 29 and a mechanism to provide benefits to the contributor.

[0312] In a first step 141, a contributor enters registration data, such as personal profile data, contact information and health information. The contributor is able to update the health information at a later time after registration.

[0313] In a further step 142, the contributor pays a contributor registration fee, which is generally a small fee such as 5 USD, and which varies according to an intended subscription category. A fixed percentage of the registration fee, such as 10%, is automatically forwarded to the partners of the health data provider.

[0314] A subscription category is determined in a next step 143. According to one alternative, the subscription category is chosen depending on the paid fee. According to another alternative, the contributor first chooses the subscription category and/or the sum corresponding to the subscription category and registration proceeds only when the amount required for the subscription category has been paid.

[0315] In a next step 144, an amount of discount vouchers is allocated to the contributor according to the subscription category. In a further step 145, an amount of gene credits is allocated according to the subscription category. After registration, a contributor can purchase additional gene credits and the conversion rate into gene credits is dependent on the subscription category.

[0316] If the subscription category is determined as a “premium category” in a decision step 146, a free access to a genomic test is allocated to the contributor in step 147. Else, an option to obtain a genomic test is allocated to the contributor in step 148. Whether the contributor actually obtains the free genetic test may depend on a random factor, for example by allocating a predetermined number of test randomly to the contributor or on other conditions.

[0317] The aspect of free or subsidized tests can be realized as follows: the health data provider provides funds for free or subsidized tests, for example by electronic payment to a test provider. The tests are then channeled to the test provider. In one example, the test provider has a list on its computer system, which lists the kind of test and the person with whom the test is associated with. The entries of the list are updated when the health data provider makes a payment for the test or pays a subsidy for the test.

[0318] A person registered with the web platform of the health data provider can then request an appointment for the free or subsidized test from the test provider by way of inputting contact data in a user interface.

[0319] A contributor of information is able to fine tune the extent that the contributor is willing to share according to three digital gene assets, which the contributor provides to the web platform over a user interface. These three digital gene assets are listed below. On the one hand, the digital gene assets take into account the willingness or ability of the contributor to provide data and, on the other hand, they also affect the reward being provided to the contributor. The digital gene assets also facilitate the search in the provided data.

[0320] The user interface of the web platform allows the contributors to set the digital gene assets at the time of registration and to modify the digital gene assets after registration. In one example, the contributor is rewarded with a pre-defined amount of gene credits for selecting a digital gene asset. By way of example, there can be three digital gene assets, which are listed below.

1. “Sign-up”

[0321] Sign up as a contributor and earn gene credits

2. “Update”

[0322] Update health information on the contributor's account

3. “Manage”

[0323] Tick on willingness to exchange information.

[0324] The willingness to exchange information can be expressed by the below mentioned factors, which the contributor can choose to elect or not to elect: [0325] genetic data (provide raw data report), [0326] molecular diagnostics of infectious diseases [0327] agree to participate in a research project [0328] agree to participate in a clinical trial [0329] provide an existing specimen, such as blood, biopsy or other [0330] provide updated or new specimen (resampling) [0331] agree to answer questions from recipient, such as questions from a predetermined set of questions [0332] link with members to share existing information [0333] share radiology reports or radiology procedures, such as X-ray, CT-scan, MRI, mammography [0334] share general laboratory reports [0335] electronic medical record (EMR) [0336] EMR on the health data provider's web site [0337] other investigations [0338] link with members with or without assets. This can be provided as a premium category asset and can enable a recipient to establish a direct contact to the contributor [0339] provide data from portable or wearable devices for evaluation purposes

[0340] The genetic data can refer, among others, to biochemical genetics, molecular genetics, clinical cytogenetics, preimplantation genetic screening and non-invasive prenatal testing.

[0341] An enrolment to the clinical trial is available for contributors through a web site “Clinical Trial, Enroll” and for researchers through a web site “Research, Enroll”. Subsequent arrangements can be defined by the relevant parties.

[0342] In the case of sharing an existing specimen or providing a new specimen, the web site provides a means for arranging a shipping between the different parties.

[0343] In a further step, a verification of the user registration is carried out. By way of example, this can be done by using an SMS message, such as SMS TAC or e-mail verification. Herein, a TAC refers to a “transaction authorization code”. A user enters their telephone number in a personal profile and is then able to request a TAC, which is then sent to the user via SMS.

[0344] FIG. 14 illustrates a registration of a recipient at the health data provider 29 and a mechanism to provide benefits to the recipient.

[0345] In a first step 150, the recipient enters registration data. In a further step 151, the recipient pays a recipient registration fee, which varies according to an intended subscription category. A subscription category is determined in a next step 152. According to one alternative, the subscription category is chosen depending on the paid fee. According to another alternative, a recipient first chooses the subscription category and/or the sum corresponding to the subscription category and registration proceeds only when the amount required for the subscription category has been paid.

[0346] In a further step 153, a search period, such as for example 1 month, 3 months or 1 year, is allocated according to the subscription category. In particular, the search can refer to an “unlimited search” in which all of a predefined set of search categories can be searched. For example, the recipient can have access to a database of the health data provider for a fixed time period, such as two months, one year etc.

[0347] In a further step 154, a predetermined number #L of request links is allocated to the recipient, depending on the subscription category.

[0348] Furthermore, in a further step 155 a permission to ask a predetermined number of #Q anonymous questions is allocated to the recipient. Thereby, the recipient can ask questions to contributors anonymously, for example for the purpose of a survey or a questionnaire.

[0349] The query facilities are explained in more detail below. A recipient can do anonymous data mining through filter and search options according to a subscription model or “package”. The number of links that can be sent is pre-defined at the time of payment.

[0350] The recipient or consumer of the information is provided with a database query permission to query the database provided through the enrolled participants or subjects. The extent of the query permission can vary according to a chosen subscription model of the recipient. This can include selecting data of participants for which a requested information is available, such as whole exome tests, radiology scans etc.

[0351] The anonymous data mining can include, among others a search and filter for contributor data, such as genetic data, health data and miscellaneous data, such as demographic, lifestyle and nutrition data. The contributor data is provided by the contributor over the web interface, for example as part of the abovementioned registration step 141. Furthermore, the contributor data can also be provided by other parties to which contributor data is available, such as the test provider or the mass enrolment center. In general, the retrieval of contributor data from other parties requires an authorization by the contributor.

[0352] The data of the contributors which can be searched by the recipients can include, among others: [0353] demographic profile, such as age, gender, location, profession [0354] health status: diseased or healthy [0355] diagnosed disease [0356] medical history [0357] history of allergy [0358] medications [0359] genetic report available [0360] digital gene asset willingness

[0361] The anonymous data mining ca furthermore comprise an anonymous questionnaire to search and filter contributors.

[0362] As a further feature, the anonymous data mining can comprise a facility for linking and exchanging data for the transaction of data research and trials

[0363] Depending on the subscription category or package the recipients have furthermore access to an anonymous questionnaire to search and filter contributors. Among others, this questionnaire provides a possibility to query for genetic data, such as raw genetic data and genetic data reports.

[0364] According to another feature, the recipient can ask questions to contributors anonymously, for example for a survey or a questionnaire. With this feature, the application expands to data mining for the industry.

[0365] The recipient is provided with a second query permission which allows to query the subjects. For example, the querying of the subjects can be carried out with a predefined query mask or filter using a communication mechanism provided by the web platform of the health data provider, such as a message box and notification mechanism.

[0366] Furthermore, also consultants and third-party verifiers can register with the health data provider.

[0367] The web platform provides a randomized selection of third-party verifiers. The randomized selection can provide a more objective and unbiased verification as compared to a selection of third-party verification by the contributors themselves.

[0368] At the time of registration of a consultant at the web platform, the consultant agrees to three categories: (1) Verify data, (2) On-line consultation and (3) Booking of an appointment. For the purpose of booking appointments, the profile of the consultant is made available to others, in particular to contributors.

[0369] Through the registered consultants, contributors and recipient obtain access to a global database of clinicians they can link with for consultations. The global database can provide a seamless connection across geographies. At the same time, it provides a health care service on the web portal.

[0370] The web platform can provide a direct partnership model with retailers, which is illustrated below in the flow diagrams of FIGS. 15 to 20.

[0371] The partnership model can provide the following benefits, among others: [0372] access to a large number of customers of the health data providers web platform [0373] disbursement of discount vouchers and an easy access platform. [0374] potential to enroll in a discount back program. [0375] increase sales with an easy on-line partnership [0376] recurring sales environments for the merchant where customers return to use utilize the discounts. [0377] back end integration for monitoring of sales and/or partnership through contracts.

[0378] According to a first model, a direct partnership with retailers for Products is provided or with or without discount. According to this first model, the vendors promote their products through the health data provider's account. As a partnership contribution, the vendors provide a percentage discount to the health data provider, a percentage of which is passed back to the customers while retaining the fees. The customers use equivalent value in gene credits to avail their discounts and purchase the vendor's products.

[0379] The web platform of the health provider implements a “discount back program” whereby registered users get discounts and/or gene credits with each transaction with a vendor. Furthermore, retailer promotions are offered with discounts and gene credits for each purchase.

[0380] In particular, the promotions can include retailer promotions and redemptions of gene credits for products and services such as genomic tests, wellness tests, tumor tests, whole genome and exome retrieval/sequencing, health screening tests. Gene credits can be purchased as well and the gene credits can be exchanged for discount vouchers from a list.

[0381] The web platform provides a raw genetic data report for the contributors. Furthermore, the web platform provides a feature for linking with members and share an existing profile.

[0382] The registered contributors can receive a health consultation from a database of consultants, which can be counsellors, clinicians or pathologist, among others. The web platform also provides on-line consultations by a global data base of professionals.

[0383] In a further aspect, the web platform provides an automated system to manage and keep track of contributor spending and the gene credits balance of the contributors. The automated system provides a filter and a search based on specified criteria, as well as a “select all contributors” function to distribute the gene credits to the filtered accounts.

[0384] Furthermore, the automated system can generate a statement of account for monthly reporting for all contributors or based on filter and search options.

[0385] FIG. 15 illustrates a vendor commission program method using vouchers.

[0386] In a first step 158, the health data provider acquires bulk discount vouchers from one or more vendors. In a next step 159, the health data provider allocates vouchers to registered contributors according to their subscription category and/or other criteria. Moreover, in a further step 160, the health data provider allocates gene credits, which can be used to buy discount vouchers. In a further step 161, the contributors use the discounts to buy items from the vendor. In a further step 162, the health data provider receives a commission program from the vendor. In particular, the commission program can amount to a predetermined percentage of a price of the purchased items.

[0387] FIG. 16 illustrates a product purchase from a vendor associated to the health data provider.

[0388] In a first step 164, a contributor updates a contributor health information on their personal account. In a further step 165, the contributor accesses a vendor website and, in a next step 166, uses discount vouchers received from the health data provider to purchase items from the vendor.

[0389] In a further step 167, the contributor receives a purchase discount from the vendor. Furthermore, the contributor receives gene credits in a further step 168. In a next step 169, the contributor uses gene credits to purchase a voucher.

[0390] FIG. 17 shows an allocation of discount vouchers from the health data provider to the contributors.

[0391] In a first step 172, the health data provider purchases discount voucher from a vendor. In a further step 173, the health data provider allocates discount vouchers to registered contributors. Furthermore, the health data provider also provides links to vendors in step 175.

[0392] By way of example, the web platform can provide links to the vendors as part of a “gene market”, which is a platform or web portal where contributors use their discount voucher and gene credits to make purchases. Furthermore, merchants or vendors who wish to advertise their products and services are listed in the gene market. This listing is subject to a selection. For example, the listing of vendors can be limited to those vendors who have submitted an agreement to the health data providers. Or it can be limited to vendors who have paid a fee to be displayed on the gene market and subject to approval by the health data provider.

[0393] The gene market provides access to the following good and services, among others: [0394] general merchandise. A link to a merchant or vendor platform is provided [0395] nutraceutical. A link to a health supplement merchant is provided. [0396] health and tourism. A link to a travel fair and health expo is provided. [0397] health insurance. A link to an insurance provider is provided. [0398] health tests: A list of tests is provided. [0399] personalized genomics [0400] solid tumor, clinical exome or whole exome examination [0401] health screening packages.

[0402] In a step 176, the contributors purchase items from the vendors. In a further step 177, the vendor sends a purchase report to the health data provider. By way of example, this process can be triggered automatically after a predetermined amount of sold items and/or after a predetermined time period.

[0403] In a further step 178, the health data provider automatically computes a cashback value based on the received purchase reports and, in a next step 179, allocates vouchers and gene credits to the contributors based on the previously computed cashback value.

[0404] FIG. 18 shows an establishment of an agreement between a health data provider and a vendor and a cash flow between the vendor and the health data provider resulting from the agreement.

[0405] In a first step 182, the health data provider submits an agreement to the vendor. For example, the agreement may include a condition according to which the health data provider provides a link to the vendor and allocates vouchers specific for that vendor and a proportion of the vouchers and also a cashback that the vendor provides in return for items and/or services purchased via the web platform of the health provider and/or using the vouchers of the health provider. In particular, the conditions of the agreement or contract can be evaluated automatically and/or a compliance with the agreement conditions can be evaluated automatically.

[0406] In a further step 183, the vendor provides a fixed percentage of the sales to the health data provider. Herein, “sales” refers to a monetary value that the vendor receives for purchased items or services by way of electronic transmission, wherein the items are purchased directly via the web platform of the health data provider or by means of tokes such as vouchers received from the health data provider.

[0407] In a step 184 the health data provider allocates vouchers for purchasing items from the vendor to registered users which are registered over the web platform of the health data provider. In particular, these can be allocated to users of the category “contributor” or “recipient”.

[0408] In a further step 185, the health data provider provides vendor specific links to the vendor and, optionally, advertisements for the vendor. In a simple example, the advertisements can be provided by a clickable image which is associated with the web link. Furthermore, the advertisement can also comprise videos, interactive product catalogues or other interactive content.

[0409] In a step 186, the vendor sends a fixed percentage x % of the sales as sales participation to the health data provider. The sending occurs by way of electronic transmission and may involve an internet service for financial transactions such as a payment provider.

[0410] In a further step 187, the health data provider allocates gene credits based on the previous sales or purchases of the vendor. In a step 188, the health data provider also allocates discount vouchers based on the sales.

[0411] FIG. 19 shows a further cash flow between the vendor and the health data provider resulting from the agreement.

[0412] In a step 190, the vendor submits an agreement to the health data provider. In particular, the agreement can be submitted electronically using the web platform of the health data provider.

[0413] In a step 191, the vendor provides a fixed discount of x % of the sales to the health data provider, for example by way of electronic transmission of monetary units. Furthermore, in a step 192 the vendor provides y % initial discount to the health data provider. In one example, the initial discount refers to the agreement and is provided when the business agreement between the health data provider and the vendor is established. In a further example, an initial discount is provided on a per customer basis for every new customer.

[0414] In a step 193, the health data provider passes on the discount to the contributor in form of vouchers and/or gene credits.

[0415] In a further step 194, contributors purchase items from the vendor. In a step 195, the health data provider receives fees from the vendor, based on the agreement and, in a step 196, the health data provider passes on benefit to the contributor from the free received from the vendor in the form of vouchers and/or gene credits.

[0416] FIG. 20 illustrates an interaction between the health data provider and the vendor in a vendor cashback procedure.

[0417] In a step 198, the health data provider offers free tests for registered customers. This can be done for example by notifying the registered customers of the free test and sending a token to the test provider, which contains data indicative of the test paid for and the customer entitled to the test. By using the token, the test provider can verify the entitlement of the respective customer to the free test. The token can be transmitted or read optically or via a wireless connection or communication channel such as a near field connection or a WIFI connection. In a simple embodiment, the token is a text message. Furthermore, the customer is notified of the free test, for example by a status update of the customer profile or by sending a message.

[0418] In a step 199, the health data provider offers a free registration and vouchers.

[0419] Furthermore, in a step 200, the health data provider purchases free tests from a test provider. In general, the order in which the steps are performed can vary from embodiment to embodiment. For example, the step 200 of purchasing the tests can also be performed before the step 198 of offering the tests to registered customers.

[0420] A further usage of gene credits as reward comprises assigning or allocating gene credits to contributors who can refer a friend. For example, a fixed percentage of the registration fee of the referred person, such as 10%, can be awarded to the contributor.

[0421] According to one example, the contributor is awarded 10% of the registration fees as Gene credits for every new customer or “friend” referred to who then registers and pays at least a minimum sum such as USD 5 for the registration.

[0422] In general, gene credits are assigned to asset providers, such as recipients and contributors. According to one embodiment, the gene credits, or a fixed portion of them, is algorithmically associated with shares of value generated from the entirety of the assets.

[0423] Within the framework provided by the health data provider, the gene credits can be used as a kind of currency and provide the following benefits, among others:

1. Gene Credits can provide discounts, by using gene credits to avail discounts on e-shopping platforms.
2. Gene Credits can provide redemptions on products and services provided by the service provider.
3. Gene Credits can be used as cash equivalent to pay for genomic tests, such as the following types of tests:
(i) personalized genomics
(ii) clinical exome
(iii) whole exome
(iv) solid tumor

[0424] Furthermore, the gene credits in an account can be used for discounts at e-commerce merchants as a discount value on the merchant's e-shopping platform. Users which are registered at the web platform of the health data provider can redeem for product and services at a marketplace web interface. Among others, gene credits can be used to buy discount vouchers from listed sites and to get direct redemptions for various products and services.

[0425] According to a further embodiment, the mass enrolment center is the entity which receives the payments of asset users and the health data provider receives the payments from the MEC. Thereby, the health data provider becomes a second-grade trustee and the MEC a first-grade trustee.

[0426] Product items for which the health data provider provides discounts and promotions are, among others:

[0427] General merchandise, nutraceuticals, health and tourism products and services, general health care items, health insurance and health tests and genomic tests.

[0428] A discount store concept, which is of value for partner merchants and which can provide contributors with a continuous incentive to shop at partner sites or vendors, comprises the following steps:

[0429] The health data provider has a predefined monthly budget to build a discount buyback program. The monthly budget is allocated to buy merchant vouchers. The health data provider buys bulk vouchers from merchants to avail best rates for purchase of vouchers from vendors.

[0430] Every contributor has a unique and secure personal account at the health data providers web platform. The health data provider's platform provides every contributor with gene credits equivalent to cash upon registration.

[0431] In a given example, a contributor pays a small registration fee, such as USD 5, and receives USD 2 merchant discount voucher and 100 Gene Credits equivalent USD 10 in their account. In one example, the gene credits are tied to a currency or to a mix of currencies. For example, a conversion rate can be fixed as 10 gene credits=1 USD.

[0432] For the first few months upon launch the health data provider offers free Registration and an additional of USD 1 free voucher for proposed various merchant partners. Furthermore, the health data provider enrolls in a cash back program with vendors. This allows to constantly buy discount vouchers from the vendor or the vendors.

[0433] As a further feature, a mobile app is provided. This app allows contributors and recipients registered on the site to search link and filter with people. Furthermore, the app provides networking opportunities such as the creation of chat groups with people with similar interests or requests. For example, the contributors could link to a global Down syndrome society.

[0434] As a further feature, the web platform provides a personalized electronic record. Often, electronic records are controlled by hospitals of clinicians. By contrast, the web platform can provide its own personalized medical record for contributors with reminders for tests or screens, health advice etc. Even if a person travels to various places his record is uniquely maintained by him or her. It is consolidated information.

[0435] According to a further embodiment, a subscriber can appoint an administrator or the health data provider to search for a relevant subject/contributor. The admin of the health data provider searches and filters and contacts contributors and the mass enrolment center (MEC) for consent and negotiation of rate. After finalizing the list of contributors, the admin provides the recipient with the list for online payment. The MEC is also referred to as “healthcare partner.” According to a further embodiment or feature, the healthcare partner (MEC) can post information about deidentified anonymized consented data available with the healthcare partner.

[0436] The recipients can filter and search and view available such databases. If the recipient wishes to acquire this data, they send a link request to the admin who then connects with the healthcare partner to arrive at a negotiated deal.

[0437] According to a further embodiment or feature, which relates to an emergency response, a digital healthcare product for an emergency response is provided. A personal account of the health data provider has the healthcare record of each contributor. Furthermore, the digital healthcare product allows the contributor to empanel and authorize to relatives or friends who can access the contributor's healthcare information in case of an emergency.

[0438] The emergency friend registers as a new role on the site and has his/her own account. This account allows access to only the medical record of the Contributor in case of an emergency.

[0439] According to a further embodiment or feature, which relates to a personalized electronic medical record (EMR), the health data provider records a predefined amount of medical information of the Contributor. This functionality can be expanded by either adding on more features for medical history including uploading of reports. Alternatively, the health data provider can interact with a third party EMR provider who can customize a personalized EMR for each contributor. In this case the complete EMR of Contributor is stored on a third-party vault. The personalized EMR can be made active by customizing for reminders, testing, screening and other healthcare activities.

[0440] The subject matter of the present specification also comprises the following feature combinations, which can also be combined with other features of the present specification. For the sake of simplicity only, the following feature combinations are organized as an itemized list with dependencies.

[0441] When the items refer to communication parties, such as subscriber, third-party subject etc. this can also refer to the device of the communication party.

Item 1. A computer-implemented method for establishing a communication link for the automated exchange of health-related information between one or more subjects and a subscriber or between a mass enrolment center and a subscriber via a web platform, the method comprising [0442] receiving data relating to a health data type and/or a genetic data type of subjects, [0443] selecting a second communication partner, such as an information source a subject or an MEC by a first communication partner, subscriber on the basis of the received health data type and/or a genetic data type, [0444] receiving a payment from at least one of the first communication partner and the second communication partner, [0445] creating a temporary link site with a temporary site identifier, such as an IP address that can be assigned from a pool of available IP addresses, [0446] forwarding the link site identifier to the first communication partner and to the second communication partner, [0447] storing a first identifier, IP address, of the first communication partner and a second identifier, IP address, of the second communication partner, [0448] providing a communication interface which allows the interchange of pre-determined messages, related to health data and/or genetic data, between the first communication partner and the second communication partner, [0449] checking a termination condition and, when the termination condition is satisfied, terminating the link interface. Terminating means at least: no longer providing or disabling the communication interface under the link site identifier.
Item 2. Method according to item 1, comprising: [0450] releasing a personal identity of the second communication partner only after a payment has been received from at least the first communication partner or the second communication partner.

[0451] Automatic triggering of payment and commodity exchange after selecting predefined messages, hitting accept button, no individual free-text messages allowed.

Item 3. A computer-implemented method for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, the method comprising, at a site of the subscriber, [0452] identifying, selecting, predefined query items, for retrieving health related data from the one or more subjects, e.g. predefined text messages, [0453] sending an information request message to an information provider, e.g. mass enrolment center, the request message comprising a consent query and the predefined query items,
at a site of the information provider, e.g. mass enrolment center, [0454] receiving the request message, [0455] determining whether consent is granted to send, anonymized, individual health data,
if it is decided that consent is granted: [0456] sending a—preferentially encrypted—data message to the subscriber, the data message comprising the individual health data, wherein a payment request to the subscriber is automatically triggered by a predefined event and the sending of the data message to the subscriber is conditional on a payment provided by the subscriber in response to the payment request.
Item 4. The method according to item 3, wherein the step of deciding whether consent is granted comprises exchanging consent information with a user device of subject.
Item 5. The method according to items 3 or 4, wherein the step of deciding whether consent is granted comprises querying a database of the health data provider for consent related data.
Item 6. The method according to one of the items 3 to 5, wherein the predefined event that triggers the payment request comprises the selection of predefined messages, and the activation of an accept button.

[0457] In the following, a subscriber site can also be provided by a simple message receiving program on a user device to which message can be sent using a destination address and does not need to be a web site.

Item 7. The method according to one of items 3 to 6, further comprising
at a payment site [0458] sending a payment request to the subscriber site, [0459] receiving payment data from the subscriber site, [0460] confirming the payment,
if the payment is confirmed [0461] send a payment acknowledgment message to the information provider,
at the information provider [0462] receiving the payment acknowledgment message and, upon receipt of the payment acknowledgment message, sending, transmitting, the data message to the subscriber.

[0463] Successive identification of information relevant to the subscriber. A successive refining can be provided by a program providing a set of predefined questions or choices that allow to narrow down the scope of the information.

Item 8. The method according to one of the preceding items 3 to 7, further comprising [0464] retrieving predefined criteria for successively refining a type of information to be queried from a subject, [0465] displaying the predefined criteria to the subscriber through elements of a graphical user interface, wherein the predefined event comprises a matching of the predefined criteria with a requirement provided by the subscriber.
(alternative: the query message can also be sent to the information provider directly and payment provider will only be notified once the consent is obtained. Furthermore: payment can be made in advance, in which case there would be a request message whether payment has been made/subscription is currently active.
Item 9. A system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, the system comprising: [0466] a subscriber user device which is operative [0467] to identify, selecting, predefined query items, for retrieving health related data from the one or more subjects, e.g. predefined text messages, [0468] to send an information request message to an information provider, e.g. a mass enrolment center or a web platform, the request message comprising a consent query and the predefined query items,
a data provider server device which is operative [0469] to receive the request message, [0470] to determining whether consent is granted to send, anonymized, individual health data, and, if it is decided that consent is granted: [0471] to send an, encrypted, data message to the subscriber, the data message comprising the individual health data, wherein a payment request to the subscriber is automatically triggered by a predefined event and the sending of the data message to the subscriber is conditional on a payment provided by the subscriber in response to the payment request.
Item 10. A computer-readable storage medium, which can include multiple physical carriers or cloud storage, comprising instructions which, when executed by a system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, cause respective computers of the computer system at a site of the subscriber [0472] to identify, selecting, predefined query items, for retrieving health related data from the one or more subjects, e.g. predefined text messages, [0473] to send an information request message to an information provider, e.g. mass enrolment center, the request message comprising a consent query and the predefined query items, at a site of the information provider, e.g. mass enrolment center [0474] to receive the request message, [0475] to determine whether consent is granted to send, anonymized, individual health data, and, if it is decided that consent is granted: [0476] to send an, encrypted, data message to the subscriber, the data message comprising the individual health data, wherein a payment request to the subscriber is automatically triggered by a predefined event and the sending of the data message to the subscriber is conditional on a payment provided by the subscriber in response to the payment request.

[0477] The transaction involving: consent proxy for mass enrolment center, which enables communication with several selected information exchange channels at the same time. There is a one-to-one relationship between subjects and subscribers. Subjects or individuals could be identified at subscriber site or at information provider site.

Item 11. A computer-implemented method for the exchange of health-related information between one or more subjects and a subscriber via an information provider, the method comprising at a subscriber site [0478] identifying health information criteria, [0479] identifying a set of subject identifiers based on the health information criteria, [0480] sending an information request message for obtaining medical information from the one or more subjects corresponding to the subject identifiers, e.g. bulk information exchange, at a proxy server site [0481] receiving the information request message, [0482] obtaining consent information for individual health data of the one or more subjects identified by the information request message,
e.g. by matching the provided information in a database against stored consent criteria of the individuals, which is faster than obtaining the consent from each individual, which may not be online,
after a pre-defined information release event [0483] retrieving health information from the one or more subjects, [0484] sending a health information message to the subscriber, the health information message comprising health data that matches to the consent data, e.g. the health information message may comprise only information for a subset of the individuals or only limited information and the message may indicate this explicitly.
Item 12. The method of item 11, comprising [0485] verifying payment data for the information request message, [0486] if the payment verification is positive triggering the predefined information release event.
Item 13. The method of item 11 or item 12, wherein the retrieval of health information from the one or more subjects comprises [0487] initiating separate information exchange services with the one or more subjects, at the health information providing for the exchange of health information, the information exchange services comprising [0488] providing pre-defined selectable data, [0489] presenting the pre-defined selectable data to the one or more subjects.

[0490] Payment can be obtained at the moment of transaction or payment can be provided in advance. Data can be provided as anonymized individual data sets or in the form of aggregated data. If the information is too different between individuals and therefore cannot be aggregated, it is provided as anonymized individual data sets. The subscriber must agree to refrain from attempting to trace back the anonymized information. Resources can be provided a dedicated hardware, or it can be provided by cloud computing, which can involve sharing across the web or across different servers or across other resources. The identified group of individuals can be stored for later use to enable follow up information, e.g. how long does the hip prosthesis last.

Item 14. A system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, the system comprising: [0491] a subscriber user device which is operative [0492] to identify health information criteria, [0493] identifying a set of subject identifiers based on the health information criteria, [0494] to send an information request message for obtaining medical information from the one or more subjects corresponding to the subject identifiers, e.g. bulk information exchange, [0495] a proxy server device which is operative [0496] to receive the information request message, [0497] to obtain consent information for individual health data of the one or more subjects identified by the information request message,
e.g. by matching the provided information in a database against stored consent criteria of the individuals, which is faster than obtaining the consent from each individual, which may not be online,
after a pre-defined information release event [0498] to retrieve health information from the one or more subjects, [0499] to send a health information message to the subscriber, the health information message comprising health data that matches to the consent data, e.g. the health information message may comprise only information for a subset of the individuals or only limited information and the message may indicate this explicitly.
Item 15. A computer-readable storage medium, which can include multiple physical carriers/cloud storage, comprising instructions which, when executed by a system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, cause respective computers of the computer system
at a subscriber site [0500] to identify health information criteria, [0501] to identify a set of subject identifiers based on the health information criteria, [0502] to send an information request message for obtaining medical information from the one or more subjects corresponding to the subject identifiers, e.g. bulk information exchange, at a proxy server site [0503] to receive the information request message, [0504] to obtain consent information for individual health data of the one or more subjects identified by the information request message,
e.g. by matching the provided information in a database against stored consent criteria of the individuals, which is faster than obtaining the consent from each individual, which may not be online, [0505] after a pre-defined information release event [0506] to retrieve health information from the one or more subjects, [0507] to send a health information message to the subscriber, the health information message comprising health data that matches [0508] to the consent data, e.g. the health information message may comprise only information for a subset of the individuals or only limited information and the message may indicate this explicitly.

[0509] A robot for doing “the information exchange” for the subscriber.

Item 16. A method for the exchange of health-related information between one or more subjects and a subscriber via an information provider, the method comprising [0510] initiating an information exchange with a subject, querying repeatedly until a subject is available/requesting a time when the subject is available, [0511] exchanging consent data with the subject, repeating the steps of [0512] sending a pre-defined information request to the subject, [0513] waiting for a pre-defined response message, which includes no free-text, to the information request,
if the pre-defined response message is received [0514] storing the content of the pre-defined response message for later use.
Item 17. A system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, the system comprising: [0515] a proxy server device, the proxy server device being operative [0516] to initiate an information exchange with a subject, querying repeatedly until a subject is available or requesting a time when the subject is available, [0517] to exchange consent data with the subject, to repeat the steps of [0518] sending a pre-defined information request to the subject, [0519] waiting for a pre-defined response message, no free-text, to the information request,
and, if the pre-defined response message is received [0520] to store the content of the pre-defined response message for later use.
Item 18. A computer-readable storage medium, which can include multiple physical carriers/cloud storage, comprising instructions which, when executed by a system for the automated exchange of health-related information between one or more subjects and a subscriber via an information provider, cause respective computers of the computer system [0521] to initiate an information exchange with a subject, querying repeatedly until a subject is available/requesting a time when the subject is available, [0522] to exchange consent data with the subject, to repeat the steps of [0523] sending a pre-defined information request to the subject, [0524] waiting for a pre-defined response message, no free-text, to the information request,
and, if the pre-defined response message is received [0525] to store the content of the pre-defined response message for later use.
Item 19—An arrangement for encrypted exchange of personal medical and financial data, the arrangement comprising [0526] a subscriber computing device, operable to receive the health-related data and the identity information data via a communication interface, [0527] a web platform server device, operable to store health related data and identity information data of a multitude of subjects and operable to provide an encrypted communication channel between the subscriber computing device and web platform server device, [0528] a payment provider server device, operable to receive a payment information from the web platform server device and/or from the subscriber computing device, and to provide a payment signal 3 to the web platform server device 28, wherein the providing of the encrypted communication channel by the web platform server device comprises:
creating a temporary link site with a temporary link site identifier and a computer memory link location, forwarding the link site identifier to the web platform server device and to the subscriber computing device, [0529] the temporary link site providing a communication interface which allows the encrypted interchange of pre-determined messages between the web platform server device and the subscriber computing device, using the computer memory link location for releasing the health-related data to the subscriber computing device,
wherein the web platform server device, upon reception of the payment signal from the payment provider server device, automatically initiates a transmission of the identity information data of at least one subject from the web platform server device to the subscriber computing device.

REFERENCE

[0530] 3 payment signal [0531] 5 MEC computer [0532] 7 data transfer message [0533] 8 request message [0534] 9 request message [0535] 10 Medical information exchange system [0536] 11 first user device [0537] 12 subject [0538] 13 first server device [0539] 14 mass enrolment center/health data provider/mass enrolment center computing device [0540] 15 second user device [0541] 16 subscriber/subscriber computing device [0542] 17 second server device [0543] 18 payment platform/payment provider server device [0544] 19 health provider database [0545] 19/1 health related data [0546] 19/2 identity information [0547] 20 payment platform database [0548] 21 information request message [0549] 22 response message [0550] 23 query server [0551] 24 query provider [0552] 25 database [0553] 26 third-party device [0554] 27 third party [0555] 28 web platform [0556] 29 health data provider [0557] 30-43 method steps of FIG. 4 [0558] 51-61 method steps of FIG. 5 [0559] 72-86 method steps of FIG. 6 [0560] 87-102 method steps of FIG. 7 [0561] 103-115 method steps of FIG. 8 [0562] 100, 100′, 100″ health information exchange system [0563] 119 gene credits [0564] 120 gene tests [0565] 121 GUI input mask [0566] 122 GUI input mask [0567] 123 communication infrastructure [0568] 124 admin [0569] 125 link site [0570] 126 IP address link site [0571] 127 IP address first communication partner [0572] 128 IP address second communication partner [0573] 129 computer memory link location [0574] 130 associated service provider [0575] 131 communication channel [0576] 132 communication channel [0577] 133 communication channel [0578] 134 communication channel [0579] 135 communication channel [0580] 136 communication channel [0581] 137 communication channel [0582] 138 communication channel [0583] 139 communication channel [0584] 140-148 method steps FIG. 13 [0585] 150-155 method steps of FIG. 14 [0586] 158-162 method steps of FIG. 15 [0587] 164-169 method steps of FIG. 16 [0588] 172-179 method steps of FIG. 17 [0589] 182-188 method steps of FIG. 18 [0590] 190-196 method steps of FIG. 19 [0591] 198-202 method steps of FIG. 20 [0592] 203 communication channel [0593] 204 communication channel