WO2022271141A1

WO2022271141A1 - Computer-based marketplace for information

Info

Publication number: WO2022271141A1
Application number: PCT/US2021/038211
Authority: WO
Inventors: Michael E. Raynor; William L. Hunter
Original assignee: Canary Medical Inc.
Priority date: 2021-06-21
Filing date: 2021-06-21
Publication date: 2022-12-29

Abstract

At least one database is organized as a plurality of records, wherein each record contains information associated with one individual person, and a portion of the information is customizable into at least one dynamically productized dataset. When a request for a plurality of productized datasets is received, and when the request defines fields common to each of the plurality of productized information sets, the database is searched to find records that match the defined fields of the request. Information is retrieved from at least some of the found records that match the defined fields, and at least some of the retrieved information is formed into the plurality of productized datasets. The plurality of productized datasets is communicated to a source of the request.

Description

COMPUTER-BASED MARKETPLACE FOR INFORMATION

TECHNICAL FIELD

[0001] The present disclosure relates generally to devices, systems and methods for generating and creating a market for information. More particularly, but not exclusively, the present disclosure relates to devices, systems and methods which provide an electronic forum where entities (e.g., individuals, groups, or commercial organizations) can offer information (e.g., personal information, medical information, behavioral information, etc.) for transfer to third parties by sale, license, or other arrangement; and where buyers can solicit, purchase, license, or otherwise obtain permissible access to use information offered by entities.

BACKGROUND

[0002] There is already a market for some types of personal information. For example, social networks (e.g., Facebook, Twitter, Reddit, Instagram, Snapchat, WhatsApp, Tumblr, and so on), search engines (e.g., Google, Bing, Yahoo!, etc.), credit bureaus, and others, collect different types of information on various entities (typically, not but exclusively, individuals), including (but not limited to) personal information via a variety of mechanisms, and generate revenue from this information in a variety of ways. For example, by analyzing the information that has been collected, social networks and search engines can identify individuals or groups that meet certain criteria and then selling advertising to third parties that which to reach individuals or groups that meet those criteria.

[0003] The individuals on whom information is collected, however, tend to realize value from information about themselves primarily through the use of services that are provided, the use of which generates the information that social networks or search engines then use to sell advertising. There is typically no monetary payment to the provider of the information (e.g., individuals) by the provider of the service (e.g., the social network or search engine). To illustrate, users of a search engine do not pay money to the provider of the search engine for the use of the search engine. Rather, the search engine provider makes the search engine available for use without requiring monetary payment, but collects information about the user's search history, and uses this information to draw conclusions about what sorts of online advertising are most likely to elicit a purchase response if presented to the search engine user, and then solicits advertising revenue from the appropriate advertisers. Alternatively, advertisers can enlist a search engine provider for potential customers based on the analysis of the search histories of users of the search engine. The price secured by the search engine provider for direct or indirect use of the personal information collected via the use of the search engine is determined by the search engine provider in direct negotiation with the advertiser. The information provider - in this example, the individual using the search engine - is not consulted, informed consent to use/sell personal information is typically not obtained from the information provider, and the revenue generated by the sale of the information is not shared with the information provider. [0004] In contrast, some markets for information are very tightly controlled. For example, medical information that physicians, hospitals or insurance carriers generate or collect typically steward this information with great care, often bound by explicit and extensive legal requirements. Thus, although individuals are subject to a wide range of medical procedures (e.g. physician visits, medication administration, surgical procedures, diagnostic testing procedures, medical imagining procedures, etc.), the medical information generated from these procedures is generally available for use by the patient only upon a specific request, and is generally unavailable to others (outside of a treating physician, hospital, or insurance carrier).

[0005] As a consequence, the full scope of a person's medical information is not typically aggregated in a single database. Several attempts have been made to create such databases, e.g., Microsoft's HealthVault, Google Heath, and Apple Health. These efforts have met with limited success: the level of participation and the completeness of the information available have both been too low to create any real value for potential users of that information, by the individuals on whom data are held, or by other third parties.

[0006] Other types of medical information are often not collected at all. For example, when a medical device is implanted into an individual (e.g., a total hip or knee replacement, a vascular stent or graft, a cardiac pacemaker, a neuromodulation device), the performance of such devices is very often observable only through the interrogation or examination of the patient, or expensive and generally static medical imaging technology (e.g., sonograms, X-rays, MRIs).

[0007] For the reasons including, but not limited to, those described above, the creation of datasets of information (e.g., the patient's history, results of physical exams, diagnostic tests, etc.) that support more effective and efficient innovation in medical devices or medical procedures has historically been time-consuming, difficult and expensive. Specifically, those who might have the information required to create such datasets have typically needed to be identified, contacted, and solicited for the information one at a time. This has limited the scale (i.e., the number of records that can be included in a dataset), scope (i.e., the number of different fields of information included in each record), accuracy, completeness, reliability and timeliness of the information available. This, in turn, has limited the pace and extent of progress users of this information have been able to make in their respective endeavors.

[0008] The present disclosure addresses the above-noted limitations in the creation of datasets that contain relevant information (e.g., personal or medical information). In particular, the present disclosure provides for the automated collection of information (including personal or medical information), such as that generated by sensor-enabled, implantable medical devices and information reported by individuals, such as the patient's self-reported symptoms and self-assessment of physical and emotional wellbeing), as well as a computer-based market in which a variety of users and providers of such information can reach mutually acceptable terms for the access and use of that information (e.g., as compiled into datasets) and payment for such access and use. [0009] All of the subject matter discussed in the Background section is not necessarily prior art, and should not be assumed to be prior art merely as a result of its discussion in the Background section. Along these lines, any recognition of problems in the prior art discussed in the Background section or associated with such subject matter should not be treated as prior art unless expressly stated to be prior art. Instead, the discussion of any subject matter in the Background section should be treated as part of the inventor's approach to the particular problem, which in and of itself may also be inventive.

SUMMARY

[0010] Briefly stated, the present disclosure provides devices, systems and methods for collecting and analyzing information, and in preferred embodiments aggregating the information into a database, from which can be compiled one or more productized datasets. For example, within one embodiment, personal information can be obtained pertaining to the state or activity of a person or their possessions, including for example, driving records, credit score, search engine history, activity on social networks, purchasing behavior, marital and familial status, travel, internet search history, purchases and so on. Similarly, medical information can be obtained from a large number of sources such as physician and hospital visits, diagnostic procedures, medical and surgical procedures, laboratory tests, imaging studies, superficial monitoring devices, implanted medical devices, physiological testing, psychological testing, rehabilitation procedures, genomic information, subjective information (patient reported symptoms and experiences), and health and fitness monitoring, to name but a few.

[0011] Whether pertaining to an individual, a group of individuals, the average characteristics of a defined population, or some other unit of analysis, information, including personal information, has many uses to many parties, including, but not limited to, the individuals or groups described by the information, physicians, medical device companies, pharmaceutical companies, insurance companies, healthcare payers, researchers, governments, public health policy makers, consumer products companies or purchasers of advertising of any type, providers of services of many types (including, but not limited to, legal, accounting, rehabilitation, physiotherapy, renovation, travel-related services, automotive companies, and so on), are but a few of the groups that may be interested in obtaining access to information, including personal information and medical information.

[0012] For example, when producers of sensor-enabled medical devices, consumer devices, wearable monitoring devices and other devices are able to study datasets of medical information that contain accurate, reliable and timely information on patient behavior and medical device functionality, they might be better able to determine which patients are best-suited for their current devices, and what sorts of design improvements would be most beneficial to future patients. Similarly, when researchers or service providers, such as medical practitioners, are able to study datasets that contain accurate, reliable, and timely medical information, they may be better able to determine which treatment regimens are best-suited to which people, and to improve these regimens for the benefit of current and future patients. [0013] Furthermore, augmenting medical information with personal information can enhance the ability to improve the medical devices or pharmaceutical products themselves, make medical procedures and treatments more effective and safer, enhance patient compliance to prescribed treatment regimens, improve recovery and rehabilitation efforts, and determine the longer term outcomes, including the safety and efficacy of the treatment undertaken.

[0014] In general terms, prospective purchasers of personal information, including, but not limited to, medical information, can define the type and quantity of information they seek, the price they are willing to pay, and the terms of use (e.g., for how long the information will be used, and for what purpose). The operator of the market provided for in the current disclosure can then interrogate the database to determine if the requested information is available at the price specified and on the terms specified by the prospective purchaser. If the prospective purchaser's conditions can be met, a productized dataset will be compiled and the sale will be completed. If the prospective purchaser's conditions cannot be met, the operator of the market can assist prospective purchasers to modify the parameters of their request (e.g., the type of information required, the number of records required, the price offered, and the terms given) and give potential sellers of personal information the opportunity to modify their parameters (e.g., the information they will provide, at what price, and on what terms) in order to allow the market operator to compile an appropriate productized dataset and enable a transaction to take place.

[0015] In general, then, the current disclosure provides for: (1) a way for recipients or users of medical devices, including implantable medical devices and external medical devices (e.g., wearable devices, at-home monitoring devices, etc.), to generate potentially valuable medical information; (2) a database that holds this medical information and other types of personal information provided by the patient, whether generated automatically or by input directly by the patient; (3) a way for entities (e.g., individuals, groups, or commercial organizations) to generate personal information generally, automatically or by manual input, and contribute this personal information to the database; (4) a market that reveals the value of medical information and personal information, and, based on that revealed value, creates incentives to providers of information to contribute information of various types to the database and make them available for sale; (5) a system whereby an entity can provide or withhold consent for the use of personal information (such as medical information) by third parties; and (6) the compilation into productized datasets of information that has been released for such use. [0016] The following are some exemplary embodiments provided by the present disclosure:

1. A system, comprising: a database having information stored therein, at least a portion of the information corresponding to medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith; a memory; and a processor coupled to the memory and the database and configured to: receive a request from a buyer computing device, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to the respective owner of the information; determine if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the consideration specification; and ii) retrieving information from at least some of the found records; form a productized dataset comprising at least some of the retrieved information; and deliver the productized dataset to the buyer computing device.

2. The system of embodiment 1, wherein the processor is further configured to repeat the determining until at least the specified quantity of records is found.

3. The system of embodiment 1, wherein the processor is further configured to, in response to a failure to find the specified quantity of records: modify the dataset specification; and repeat the determining based on the modified dataset specification until the specified quantity of records is found.

4. The system of embodiment 3, wherein the processor modifies the dataset specification by being configured to autonomously change one or more parameters of the specified information of the dataset specification.

5. The system of embodiment 3, wherein the processor modifies the dataset specification by being configured to: solicit a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device.

6. The system of embodiment 3, wherein the processor is further configured to: present information on the records found based on the modified dataset specification; and receive a notice of acceptance of the records found based on the modified dataset specification.

7. The system of embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a failure to find the specified quantity of records: solicit a modification of one or more parameters of the consideration specification; and repeat the determining based on the modified consideration specification until the specified quantity of records is found. 8. The system of embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

9. The system of embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to: identify a plurality of records that satisfies the dataset specification but not the consideration specification; and add the identified plurality of records to an auction pool.

10. The system of embodiment 9, wherein the processor is further configured to: present, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

11. The system of embodiment 9, wherein the processor is further configured to, for one or more of the plurality of records in the auction pool: receive a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification; and repeat the determining with respect to the modified record.

12. The system of embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a quantity of found records being greater than the specified quantity of records: solicit, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and solicit, from one or more seller computing device associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification.

13. The system of embodiment 1 wherein the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

14. The system of embodiment 1, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

15. The system of embodiment 14, wherein the one or more types of medical information comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level. 16. The system of embodiment 15 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

17. The system of embodiment 1 wherein the processor forms a productized dataset comprising at least some of the retrieved information by being further configured to one or more of remove personally identifiable information from the retrieved information, obfuscate the retrieved information, prepare and/or implement a terms-of use for the retrieved information, and form the retrieved information into one or more computer-readable files.

18. A method comprising: storing information in a database, at least a portion of the information corresponding to medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith; receiving a request from a buyer computing device, the request comprising a dataset specification and a consideration specification, wherein: the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and the consideration specification specifies a compensation to be provided to the respective owner of the information; determining if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the consideration specification; and ii) retrieving information from at least some of the found records; and forming a productized dataset comprising at least some of the retrieved information; and delivering the productized dataset to the buyer computing device.

19. The method of embodiment 18, further comprising repeating the determining until at least the specified quantity of records is found.

20. The method of embodiment 19, further comprising, responsive to a failure to find the specified quantity of records: modifying the dataset specification; and repeating the determining based on the modified dataset specification until the specified quantity of records is found.

21. The method of embodiment 20, wherein modifying the dataset specification comprises autonomously changing one or more parameters of the specified information of the dataset specification. 22. The method of embodiment 20, wherein modifying the dataset specification comprises: soliciting a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device.

23. The method of embodiment 20 further comprising: presenting information on the records found based on the modified dataset specification; and receiving a notice of acceptance of the records found based on the modified dataset specification.

24. The method of embodiment 18, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of one or more parameters of the consideration specification; and repeating the determining based on the modified consideration specification until the specified quantity of records is found.

25. The method of embodiment 18, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the dataset specification: soliciting from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeating the determining with respect to the modified record.

26. The method of embodiment 18, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the dataset specification but not the consideration specification; and adding the identified plurality of records to an auction pool.

27. The method of embodiment 26, further comprising: presenting, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

28. The method of embodiment 26, further comprising, for one or more of the plurality of records in the auction pool: receiving a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification; and repeating the determining with respect to the modified record.

29. The method of embodiment 18, wherein determining if one or more records satisfy the request further comprises, in response to a quantity of found records being greater than the specified quantity of records: soliciting, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and soliciting, from one or more seller computing devices associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification.

30. The method of embodiment 18 wherein the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

31. The method of embodiment 18, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

32. The method of embodiment 31, wherein the one or more types of medical information comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

33. The method of embodiment 18 wherein the consideration specification further comprises one or more terms of use for the information in the dataset.

34. The method of embodiment 18 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

35. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a server to: store information in a database, at least a portion of the information corresponding to medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith; receive a request from a buyer computing device, the request comprising a dataset specification and a consideration specification, wherein: the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and the consideration specification specifies a compensation to be provided to the respective owner of the information; determine if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the consideration specification; and ii) retrieving information from at least some of the found records; form a productized dataset comprising at least some of the retrieved information; and deliver the productized dataset to the buyer computing device.

36. A marketplace computing server, comprising: a memory; and a processor coupled to the memory and a database and configured to: receive a request comprising a dataset specification, wherein the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset; determine if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information; and ii) retrieving information from at least some of the found records; and form a productized dataset comprising at least some of the retrieved information.

37. The marketplace computing server of embodiment 36, wherein the processor is further configured to repeat the determining until at least the specified quantity of records is found.

38. The marketplace computing server of embodiment 36, wherein the processor is further configured to, in response to a failure to find the specified quantity of records: modify the dataset specification; and repeat the determining based on the modified dataset specification until the specified quantity of records is found.

39. The marketplace computing server of embodiment 38, wherein the processor modifies the dataset specification by being configured to autonomously change one or more parameters of the specified information of the dataset specification.

40. The marketplace computing server of embodiment 38, wherein the processor modifies the dataset specification by being configured to: solicit a modification of one or more parameters of the specified information of the dataset specification.

41. The marketplace computing server of embodiment 38, wherein the processor is further configured to: present information on the records found based on the modified dataset specification; and receive a notice of acceptance of the records found based on the modified dataset specification.

42. The marketplace computing server of embodiment 36, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit, a modification of the record to include new information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

43. The marketplace computing server of embodiment 36, wherein the database includes personal information comprising medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith.

44. The marketplace computing server of embodiment 43 wherein: the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment; and the medical information obtained from a plurality of medical devices comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

45. A method comprising: receiving a request comprising a dataset specification, wherein the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset; determining if one or more records satisfy the request by: i) searching a database to find records that contain some or all of the specified information; and ii) retrieving information from at least some of the found records; and forming a productized dataset comprising at least some of the retrieved information.

46. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a server to: receive a request comprising a dataset specification, wherein the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset; determine if one or more records satisfy the request by: i) searching a database to find records that contain some or all of the specified information; and ii) retrieving information from at least some of the found records; and form a productized dataset comprising at least some of the retrieved information.

47. A buyer computing device, comprising: a memory; and a processor coupled to the memory and configured to: transmit a request to a marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification comprises a plurality of parameters including specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to a respective owner of the specified information; communicate with the marketplace computing server to reach an agreement; and receive a productized dataset comprising at least some of the specified information found in records stored in a database.

48. The buyer computing device of embodiment 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information on records found based on the dataset specification; and transmit a notice of acceptance of the records found based on the dataset specification.

49. The buyer computing device of embodiment 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the dataset specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified dataset specification comprising at least one of the one or more alternative parameters.

50. The buyer computing device of embodiment 49, wherein the processor is further configured to: receive information on the records found based on the modified dataset specification; and transmit a notice of acceptance of the records found based on the modified dataset specification.

51. The buyer computing device of embodiment 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the consideration specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified consideration specification comprising at least one of the one or more alternative parameters.

52. A method comprising: transmitting a request to a marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification comprises a plurality of parameters including specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to a respective owner of the specified information; communicating with the marketplace computing server to reach an agreement; and receiving a productized dataset comprising at least some of the specified information found in records stored in a database. 53. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a buyer computing device to: transmit a request to a marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification comprises a plurality of parameters including specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to a respective owner of the specified information; communicate with the marketplace computing server to reach an agreement; and receive a productized dataset comprising at least some of the specified information found in records stored in a database.

54. A seller computing device, comprising: a memory; and a processor coupled to the memory and configured to: transmit personal information to a marketplace computing server for storage in a database record, the personal information comprising medical information obtained from at least one medical device associated with a seller; associate terms of sale with the personal information comprising an expected compensation; and communicate with the marketplace computing server to reach an agreement with a perspective buyer, wherein the perspective buyer has submitted a request to the marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and b) the consideration specification specifies a compensation to be provided to a seller of the specified information.

55. The seller computing device of embodiment 54, wherein the processor communicates with the marketplace computing server by being further configured to: receive, from the marketplace computing server, a solicitation for a modification of the database record to specify additional information for sale that results in the record satisfying the dataset specification; and transmit, to the marketplace computing server, a notice of acceptance of the modification to the record.

56. The seller computing device of embodiment 54, wherein the processor communicates with the marketplace computing server by being further configured to: receive, from the marketplace computing server, a solicitation for a modification of the database record to change the expected compensation to an amount that results in the terms of sale satisfying the consideration specification; and transmit, to the marketplace computing server, a notice of acceptance of the modification to the record.

57. The seller computing device of embodiment 54, wherein the at least one medical device comprises an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

58. The seller computing device of embodiment 54, wherein the medical information obtained from the at least one medical device comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

59. A method comprising: transmitting personal information to a marketplace computing server for storage in a database record, the personal information comprising medical information obtained from at least one medical device associated with a seller; associating terms of sale with the personal information comprising an expected compensation; and communicating with the marketplace computing server to reach an agreement with a perspective buyer, wherein the perspective buyer has submitted a request to the marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and b) the consideration specification specifies a compensation to be provided to a seller of the specified information.

60. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a seller computing device to: transmit personal information to a marketplace computing server for storage in a database record, the personal information comprising medical information obtained from at least one medical device associated with a seller; associate terms of sale with the personal information comprising an expected compensation; and communicate with the marketplace computing server to reach an agreement with a perspective buyer, wherein the perspective buyer has submitted a request to the marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and b) the consideration specification specifies a compensation to be provided to a seller of the specified information. 61. A non-transitory computer-readable medium whose stored contents configure a computing system to perform a method, the method comprising: a) maintaining at least one database having information stored therein, at least a portion of the information obtained from a plurality of implanted medical devices each implanted in a respective owner, the plurality of implanted medical devices each comprising a sensor configured to detect or measure one or more operational properties of the implanted medical device and to generate information corresponding to the one or more operational properties, said database being organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; b) receiving a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of implanted medical device, and at least one of the one or more operational properties of the type of implanted medical device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; c) determining if one or more records satisfy the request by: i) searching said database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and d) forming a productized dataset comprising at least some of the retrieved information.

62. The non-transitory computer-readable medium of embodiment 61 whose stored contents configure the computing system to perform the method, the method further comprising repeating the determining until at least the specified quantity of records is found.

63. The non-transitory computer-readable medium of embodiment 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

64. The non-transitory computer-readable medium of embodiment 63 whose stored contents configure the computing system to perform the method, the method further comprising: presenting information on the records found based on the modified specification for a dataset; and receiving a notice of acceptance of the records found based on the modified specification for a dataset. 65. The non-transitory computer-readable medium of embodiment 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

66. The non-transitory computer-readable medium of embodiment 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

67. The non-transitory computer-readable medium of embodiment 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

68. The non-transitory computer-readable medium of embodiment 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

69. The non-transitory computer-readable medium of embodiment 68 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: presenting information on discrepancies between the specification for consideration and the compensation included in the plurality of records in the auction pool.

70. The non-transitory computer-readable medium of embodiment 68 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: receiving a modification of one or more of the plurality of records in the auction pool to include a new compensation that results in the one or more records satisfying the specification for consideration.

71. The non-transitory computer-readable medium of embodiment 62, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration.

72. The non-transitory computer-readable medium of embodiment 61 wherein the type of implantable medical device specified in the request comprises an orthopedic implant and the one or more operational properties of the orthopedic implant comprises one or more measures of flexures, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, and migration.

73. The non-transitory computer-readable medium of embodiment 72 wherein the orthopedic implant comprises one of a hip prosthesis, a knee prosthesis, and a shoulder prosthesis.

74. The non-transitory computer-readable medium of embodiment 61 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor and temperature sensor.

75. The non-transitory computer-readable medium of embodiment 61 wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

76. The non-transitory computer-readable medium of embodiment 61 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

77. A marketplace computing system, comprising: a database having information stored therein, at least a portion of the information obtained from a plurality of implanted medical devices each implanted in a respective owner, the plurality of implanted medical devices each comprising a sensor configured to detect or measure one or more operational properties of the implanted medical device and to generate information corresponding to the one or more operational properties, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; a memory; and a processor coupled to the memory and the database and configured to: receive a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of implanted medical device, and at least one of the one or more operational properties of the type of implanted medical device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; determine if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and form a productized dataset comprising at least some of the retrieved information.

78. A method comprising: storing information in a database, at least a portion of the information obtained from a plurality of implanted medical devices each implanted in a respective owner, the plurality of implanted medical devices each comprising a sensor configured to detect or measure one or more operational properties of the implanted medical device and to generate information corresponding to the one or more operational properties, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; receiving a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of implanted medical device, and at least one of the one or more operational properties of the type of wearable device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; determining if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and forming a productized dataset comprising at least some of the retrieved information.

79. A non-transitory computer-readable medium whose stored contents configure a computing system to perform a method, the method comprising: a) maintaining at least one database having information stored therein, at least a portion of the information obtained from a plurality of wearable devices each associated with a respective owner, the plurality of wearable devices each comprising a sensor configured to detect or measure one or more operational properties of the wearable device and to generate information corresponding to the one or more operational properties, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; b) receiving a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of wearable device, and at least one of the one or more operational properties of the type of wearable device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; c) determining if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and d) forming a productized dataset comprising at least some of the retrieved information.

80. The non-transitory computer-readable medium of embodiment 79 whose stored contents configure the computing system to perform the method, the method further comprising repeating the determining until at least the specified quantity of records is found.

81. The non-transitory computer-readable medium of embodiment 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

82. The non-transitory computer-readable medium of embodiment 81 whose stored contents configure the computing system to perform the method, the method further comprising: presenting information on the records found based on the modified specification for a dataset; and receiving a notice of acceptance of the records found based on the modified specification for a dataset.

83. The non-transitory computer-readable medium of embodiment 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

84. The non-transitory computer-readable medium of embodiment 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

85. The non-transitory computer-readable medium of embodiment 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

86. The non-transitory computer-readable medium of embodiment 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

87. The non-transitory computer-readable medium of embodiment 86 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: presenting information on discrepancies between the specification for consideration and the compensation included in the plurality of records in the auction pool.

88. The non-transitory computer-readable medium of embodiment 86 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: receiving a modification of one or more of the plurality of records in the auction pool to include a new compensation that results in the one or more records satisfying the specification for consideration.

89. The non-transitory computer-readable medium of embodiment 80, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration. 90. The non-transitory computer-readable medium of embodiment 79 wherein the type of wearable device specified in the request comprises one of an external medical device, a garment, an accessory, and a piece of sports equipment.

91. The non-transitory computer-readable medium of embodiment 79, wherein the one or more operational properties of the wearable device comprises one or more measures of the sensor.

92. The non-transitory computer-readable medium of embodiment 91, wherein the one or more measures of the sensor comprise a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

93. The non-transitory computer-readable medium of embodiment 79 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

94. The non-transitory computer-readable medium of embodiment 79 wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

95. The non-transitory computer-readable medium of embodiment 79 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

96. A marketplace computing system, comprising: a database having information stored therein, at least a portion of the information obtained from a plurality of wearable devices each worn by a respective owner, the plurality of wearable devices each comprising a sensor configured to detect or measure one or more operational properties of the wearable device and to generate information corresponding to the one or more operational properties, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; a memory; and a processor coupled to the memory and the database and configured to: receive a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of wearable device, and at least one of the one or more operational properties of the type of wearable device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; determine if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and form a productized dataset comprising at least some of the retrieved information.

97. A method comprising: storing information in a database, at least a portion of the information obtained from a plurality of wearable devices each worn by a respective owner, the plurality of wearable devices each comprising a sensor configured to detect or measure one or more operational properties of the wearable device and to generate information corresponding to the one or more operational properties, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; receiving a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of wearable device, and at least one of the one or more operational properties of the type of wearable device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; determining if one or more records satisfy the request by: i) searching the database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and forming a productized dataset comprising at least some of the retrieved information.

[0017] This Summary has been provided to introduce certain concepts in a simplified form that are further described in detail below in the Detailed Description. Unless and except where otherwise expressly stated, this Summary does not identify key or essential features of the claimed subject matter, nor does it limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Non-limiting and non-exhaustive embodiments are described with reference to the following drawings, wherein like labels refer to like parts throughout the various views unless otherwise specified. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements are selected, enlarged, and positioned to improve drawing legibility. The particular shapes of the elements as drawn have been selected for ease of recognition in the drawings. One or more embodiments are described hereinafter with reference to the accompanying drawings in which:

[0019] FIG. 1 is a flow diagram illustrating one embodiment of a transaction, in which information contained in the database is compiled into a productized dataset;

[0020] FIG. 2A-2D are a series of diagrams illustrating various subroutines, including: an illustrative information match subroutine (FIG. 2A), an illustrative consideration match subroutine (FIG. 2B), an illustrative auction pool evaluation subroutine (FIG. 2C), and an illustrative auction execution subroutine (FIG. 2D).

[0021] FIG. 3 illustrates one embodiment of a system to collect personal information and provide a computer-based marketplace to license, sell, or otherwise grant access the collected personal information;

[0022] FIG. 4 illustrates one embodiment of an implantable medical device that can be included in the system of FIG. 3;

[0023] FIG. 5 illustrates one embodiment of an information flow diagram illustrating information communicated between a marketplace computing server and a buyer computing device;

[0024] FIG. 6 illustrates one embodiment of an implementation of screen information communicated via the computer-based marketplace;

[0025] FIG. 7 is a representative embodiment of acceptable seller terms and acceptable buyer terms for a personal information transaction;

[0026] FIGS. 8A and 8B are a flow diagrams representing one example of a personal information transaction;

[0027] FIG. 9A is a process flow diagram of a dataset transaction executed by a marketplace computing server of the system of FIG. 3.

[0028] FIG. 9B is a process flow diagram of actions executed by a seller computing device of the system of FIG. 3 during a dataset transaction.

[0029] FIG. 10A illustrates one embodiment of an implantable medical device, e.g., an artificial hip joint, that can be included in the system of FIG. 3.

[0030] FIG. 10B illustrates one embodiment of an implantable medical device, e.g., an artificial hip joint having a plurality of sensors, that can be included in the system of FIG. 3.

[0031] FIG. IOC illustrates one embodiment of an implanted medical device, e.g., an artificial hip joint having a sensor module therein, that can be included in the system of FIG. 3.

DETAILED DESCRIPTION

[0032] In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments. Flowever, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with computing systems including client and server computing systems, as well as networks have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments. Prior to setting forth the embodiments however, it may be helpful to provide an understanding thereof to first set forth definitions of certain terms that are used hereinafter.

[0033] "Individual" refers to a single entity (e.g., a living organism such as a human being), where the entity may be further characterized by specific characteristics such as male, female, baby, infant, adolescent, man, woman, person in specific age bracket such as under 18, older than 18, older than 20, older than 25, older than 30, older than 35, older than 40, older than 45, older than 50, older than 55, older than 60, older than 65, older than 70, older than 75, older than 80, older than 85, older than 90, older than 95, and older than 100. The individual may be characterized in terms of health (or by any of a number of different parameters of health), physical characteristics, genetic characteristics, ethnic background, disease state, socioeconomic considerations, geographic considerations, hobbies and activities, habits, drug use, marital status and the like. The individual may be characterized in terms of fitness and mental wellbeing. The individual may be characterized in terms of typical activities that he or she may perform.

[0034] "Information" refers generally to facts or knowledge which are gained or learned by any of a variety of mechanisms (e.g., investigation, study, self-reported, etc.). "Information" is also what is conveyed or represented by a particular arrangement or sequence of things, including for example, data.

[0035] "Personal information" can be generated through a variety of mechanisms, and includes, for example, information about an individual and that individual's possessions, including driving records and behaviors, credit histories, purchasing behavior, warranty or insurance claims, and any other activities. Personal information may include, for example, demographic information (e.g., age, sex, ethnicity, etc.), income information, geographic location information, habit information, physical trait information, and medical information.

[0036] In some circumstances, personal information can be captured or produced from a wide variety of sources. Along these lines, personal information may be generated or otherwise derived from browsing information, driving information, purchasing information, location information, social networking information (e.g., FACEBOOK, LINKEDIN, TWITTER, INSTAGRAM, SNAPCHAT, dating sites, etc.), internet of things (loT) information (e.g., sensor information from automobiles, house climate control systems, home appliances, security systems, home entertainment systems, and other electrical or electromechanical systems), financial transaction information (e.g., PAYPAL, APPLE PAY, GOOGLE PAY, QICSEND, WESTERN UNION, stock market information, etc.), climate information, weather information, travel information (e.g., UBER, airlines, hotels, etc.), media information (e.g., ITUNES, music, news, video, NETFLIX, HULU, VUDU, YOUTUBE, SPOTIFY, PANDORA, APPLE APPS STORE, GOOGLE PLAY, on-line adult content information, etc.), educational information (KHAN ACADEMY, COURSERA, university libraries, etc.), video gaming (e.g., on-line gambling, MINECRAFT, X- BOX LIVE, STEAM, gaming apps, etc.), physical activity (e.g., PELOTON, ZWIFT) and cell phone usage information are other forms of information that are applicable for use in the present disclosure. [0037] "Medical information" refers to information associated with an individual's physiology or psychology, including the individual's physical state, mental state, and emotional state. In the present disclosure, non-limiting examples of medical information may include, but is not limited to, physical and electronic medical records information, medical imaging information, prescription and non prescription medicament use information, surgical and medical procedure information, medical testing and diagnostic testing information, health and well-being information, medical history information, psychological and psychiatric information, fitness and activity information, health monitoring and physical activity monitoring information, rehabilitation information, genomic information, subjective information (patient reported symptoms and experiences), health outcomes information, and medical device (e.g., implanted medical device, external medical device, etc.) monitoring information.

[0038] In the case of an individual having an associated medical device, e.g., an implanted medical device or an external medical device, such as a wearable device, medical information also includes information obtainable through the device. Medical information may include, medical device information, medical-device reported information (e.g., physiological information sensed by a medical device, activity information sensed by a medical device), patient-reported information, physician- reported information. Medical device information may include device type information, manufacturer information, device operation information (e.g., stimulation parameters, sensor types, fault information, battery life information, power status information, device temperature information, structural integrity information), or nearly any other kind of information that is relevant to the dataset being requested. Device operation information is generally associated with operation of the medical device 104. For example, device operation information may include a count of flexures of an artificial knee or hip joint, a volume of blood passed through a stent, a number of abnormal heart signal detections and corresponding electrical impulse firings of a pacemaker, and the like. Fault information may be any improper, unexpected, or recognized errant operation of the device.

[0039] Medical information also refers to information generated by medical practitioners and equipment in hospitals, clinics, and offices during medical procedures, surgical procedures, diagnostic testing procedures, laboratory procedures, medical imagining procedures, genomic testing procedures, rehabilitation procedures, medical and psychological evaluation procedures, physical activity monitoring measures, activity and exercise monitoring measures, physiological monitoring measures, and superficial or internal monitoring device operations. Medical information may also include information generated and or self-reported by the person themselves before, during or after treatments; such as pain assessment, duration and quality of sleep, activity levels, functional abilities/disabilities and limitations, quality of life, activities of daily living, psychological and emotional wellbeing, mood, interpersonal assessments, social activities, exercise, and job performance to name a few.

[0040] A "productized dataset" consists of a specified number of records capturing specified information (e.g., medical information) to which an information buyer is granted access to for a specified use for a specified period of time for specified price. To this end, in some embodiments a productized dataset remains in a secure server and is not downloadable or otherwise deliverable to the buyer. Instead, the buyer is merely granted access to the dataset for a period of time. In other some embodiments, a productized dataset may be download or otherwise delivered to the buyer. Productized datasets are not general purpose databases: buyers cannot combine productized datasets with other information, however obtained, nor can the information in productized datasets be used to draw inferences that are not explicitly stated in the uses specified when access is granted. [0041] A "buyer" in the present disclosure is an individual or entity that performs acts to gain access to a productized dataset. A buyer may pay or promise to pay money or some other consideration in return for permission to access the productized dataset. Actions to "buy" a productized dataset, as used in the present disclosure, include acts in furtherance of a buyer gaining access to productized dataset. Accordingly, the terms "buy," "buyer," "buying," and derivative and synonymous terms are not limited to a transfer, physical or otherwise, of exclusive ownership in return for consideration. Instead, such terms are broadly interpreted to encompass the acts and means of an individual or entity to acquire exclusive or non-exclusive, perpetual or time-limited access to, and usage subject to specified terms, conditions and limitations of a particular productized dataset.

[0042] A "seller" in the present disclosure is an individual or entity that performs acts to include information they own in a productized dataset. A seller may receive money or some other consideration, or a promise thereto, in return for granting permission to include their information in a productized dataset. Actions to "sell" information, as used in the present disclosure, include acts in furtherance of a seller providing access to information that is compiled to create a productized dataset. Accordingly, the terms "sell," "seller," "selling," and derivative and synonymous terms are not limited to a transfer, physical or otherwise, of exclusive ownership in return for consideration. Instead, such terms are broadly interpreted to encompass the acts and means of an individual or entity providing exclusive or non-exclusive, perpetual or time limited access to and usage of, subject to specifiable terms, conditions and limitations, a particular productized dataset.

[0043] "Medical device" refers to an instrument, apparatus, constructed element or composition, machine, implement, or similar or related article that can be utilized to diagnose, prevent, treat or manage a disease or other condition(s), or monitor and collect physical activity information and physiological information. The medical devices provided herein may, depending on the device and the embodiment, be implanted medical devices that are either acutely or chronically implanted within an individual, or external medical devices that are worn or wearable by an individual. These medical devices may be configured to deliver a therapy to an individual, to deliver a medication or therapy to an individual, and/or to monitor the status, activity, or physiology of an individual. To these ends, a medical device may include one or more therapy components, stimulation electrodes, that deliver a therapy to the individual; and one or more sensors that detect and measure physical activity and physiological conditions of an individual. In many embodiments the medical devices provided herein are sterile, and subject to regulatory requirements relating to their sale and use.

[0044] Representative examples of implanted medical devices include, for example, cardiovascular devices and implants such as implantable cardioverter defibrillators, pacemakers, balloons, stents, stent grafts, bypass grafts, catheters and heart valves; orthopedic implants (e.g., total or partial arthroplastic joints such as hip, knee and shoulder prosthesis); spinal implants and hardware (spinal cages, screws, plates, pins, rods and artificial discs); a wide variety of medical tubes (grafts, bypass grafts, shunts, drains, endotracheal tubes), cosmetic and / or aesthetic implants [e.g., breast implants, fillers); a wide variety of polymers, bone cements, bone fillers, scaffolds, and naturally occurring materials (e.g., xenograft heart valves, and grafts from other naturally occurring sources); intrauterine devices; infusion devices (pumps, ports, vascular access devices) orthopedic hardware [e.g., casts, braces, tensor bandages, external fixation devices, tensors, slings and supports) and internal hardware [e.g., K-wires, pins, screws, plates, and intramedullary devices [e.g., rods and nails), dynamic hip screws); cochlear implants; dental implants; medical polymers (including sutures, ligatures, meshes, barriers, sealants, glues and gels), a wide variety of neurological devices (stimulation devices); and artificial intraocular eye lenses.

[0045] Representative examples of external medical devices include wearable biometric monitoring devices configured to collect one or more types of biometric data, e.g., data pertaining to physical characteristics of the human body (such as heartbeat, heart rate, perspiration levels, etc.) and/or data relating to motion and activity of that body with the environment (such as accelerometer readings, gyroscope readings, etc.). Examples of wearable biometric monitoring devices include smartwatches, disposable patches (e.g., ECG monitoring patches, glucose monitoring patches), strap devices (e.g., a Holter monitors), athletic equipment, and athletic apparel such as running shoes.

[0046] "Sensor" refers to a device that detects and or measures a physical property, and can, optionally, record, indicate and /or respond to the physical property (and include for example, "ISM"s as discussed in more detail below). Sensors can be utilized to detect and/or measure a wide variety of physical properties, including for example, movement, acceleration, velocity, location, pressure, force, biological properties, and time. Within various embodiments disclosed herein, sensors can detect and/or measure body tissue (anatomy, physiology, metabolism, and/or function) and/or one or more aspects of the medical device. Representative examples of sensors suitable for use within the present disclosure include, for example, fluid pressure sensors, fluid volume sensors, contact sensors, optical sensors, position sensors, pulse pressure sensors, blood volume sensors, blood flow sensors, chemistry sensors [e.g., for blood chemistry and/or other fluids), metabolic sensors [e.g., for blood and/or other fluids), antibodies, accelerometers, mechanical stress sensors and temperature sensors. Within certain embodiments the sensor can be a wireless sensor, or, within other embodiments, a sensor connected to a wireless microprocessor. Within further embodiments one or more (including all) of the sensors can have a Unique Sensor Identification number ("USI") which specifically identifies the sensor and/or a Unique Device Identification number ("UDI") with which the sensors can provide unique information of the associated Medical device for tracking purposes of the Medical Device manufacturer, the health care system, and regulatory requirements.

[0047] A wide variety of sensors (also referred to as Microelectromechanical Systems or "MEMS", or Nanoelectromechanical Systems or "NEMS", and BioMEMS or BioNEMS, see generally https://en.wikipedia.org/wiki/MEMS) can be utilized within the present disclosure. Representative patents and patent applications include U.S. Patent Nos. 7,383,071, 7,450,332; 7,463,997, 7,924,267 and 8,634,928, and U.S. Publication Nos. 2010/0285082, and 2013/0215979. Representative publications include "Introduction to BioMEMS" by Albert Foch, CRC Press, 2013; "From MEMS to Bio MEMS and Bio-NEMS: ManufacturingTechniques and Applications by Marc J. Madou, CRC Press 2011; "Bio-MEMS: Science and Engineering Perspectives, by Simona Badilescu, CRC Press 2011;

"Fundamentals of BioMEMS and Medical Microdevices" by Steven S. Saliterman, SPIE-The International Society of Optical Engineering, 2006; "Bio-MEMS: Technologies and Applications", edited by Wanjun Wang and Steven A. Soper, CRC Press, 2012; and "Inertial MEMS: Principles and Practice" by Volker Kempe, Cambridge University Press, 2011; Polla, D. L, et al., "Microdevices in Medicine," Ann. Rev. Biomed. Eng. 2000, 02:551-576; Yun, K. S., et al., "A Surface-Tension Driven Micropump for Low-voltage and Low-Power Operations," J. Microelectromechanical Sys., 11:5, October 2002, 454-461; Yeh, R., et al., "Single Mask, Large Force, and Large Displacement Electrostatic Linear Inchworm Motors," J. Microelectromechanical Sys., 11:4, August 2002, 330-336; and Loh, N. C., et al., "Sub-10 cm³ Interferometric Accelerometer with Nano-g Resolution," J. Microelectromechanical Sys., 11:3, June 2002, 182-187; all of the above of which are incorporated by reference in their entirety.

[0048] Within various embodiments disclosed herein, the sensors may be placed at a variety of locations and in a variety of configurations, on or within an object, on or within an individual, on the inside of a medical device, within the body of the medical device, on the outer surfaces (or inner surfaces) of the medical device, between the medical device and other medical devices or implants, and/or between the medical device and any device that might carry or deliver it ( e.g ., a delivery device, injection device, or surgical instrument). When the phrase "placed in a medical device" or "placed in a medical implant" is utilized, it should be understood to refer to any of the above embodiments (or any combination thereof) unless the context of the usage implies otherwise.

[0049] The sensors may be placed on and/or within an object in a wide variety of configurations. For example, within certain embodiments, objects are provided (e.g., wearable devices, sports equipment, an area of play, and/or a medical device) which comprise sensors at a density of greater than 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 or greater than 10 sensors per square centimeter. Within other aspects, objects are provided (e.g., wearable devices, sports equipment, an area of play, and/or a medical device) which comprise sensors at a density of greater than 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 or greater than 10 sensors per cubic centimeter. Within either of these embodiments, there can be less than 50, 75, 100, or 100 sensors per square centimeter, or per cubic centimeter. Within various embodiments, at least one or more of the sensors may be placed randomly, or at one or more specific locations within an object.

[0050] In various embodiments, the sensors may be placed within specific locations and/or randomly throughout the medical device and/or associated devices. In addition, the sensors may be placed in specific patterns (e.g., they may be arranged in the pattern of an X, as oval or concentric rings around the orthopedic implant and/or associated devices).

[0051] "Implantable Sensor Module" or "ISM" is a sensing device which is configured to be implanted into a living individual, such as a human, and is configured to sense one or more physical quantities, to generate a signal that represents the sensed quantity, and to transmit the signal to a remote receiver. The ISM may have one or more sensors as provided above. The ISM may be implanted into an individual directly, or, within one or more medical devices which are implanted within an individual. Within an embodiment, the signal may contain information encoded to represent one or more of a magnitude, phase, and type of the sensed physical quantity.

[0052] In some embodiments, the ISM is a self-contained module having one or more sensors as described herein, a sensor interface, a processor interface, battery management, a transmitter, and a wireless interface. In some embodiments the ISM will be less than 5, 4, 3, 2, or 1 cubic centimeter in size, and more preferably, less than 5.0, 4.5, 4.0, 3.5, 3.0, 2.5, 2.0, 1.5, 1.0, 0.9, 0.8. 0.7, 0.6, 0.5, 0.4, 0.3, O.2., or 0.1 cubic centimeters in size. Within various embodiments the ISM can be comprised of a solid outer core, or composed of flexible materials ( e.g ., flexible/malleable alloys, a degradable or non-degradable outer polymeric surface). Within related embodiments, the ISM can be comprised of flexible circuitry (including for example, single and double-sided flexible circuits. Within certain embodiments the ISM may be relatively square and solid, and yet with in other embodiments very thin, pliable and lengthy (as compared to its width and /or height). It can be constructed for a number of different applications [e.g., for insertion, attachment or implantation into any of the medical devices or implants provided herein).

[0053] Representative examples of various objects (e.g., implantable medical devices, including for example, wireless medical devices which can transmit a signal from inside a body to outside the body) having one or more sensors as provided herein, as well as methods for sending and receiving signals from such objects include those described in the following patent applications (all of which are hereby incorporated by reference in their entirety): U.S. Serial No. 14/654,529 and International Application No. PCT/US2013/077356, entitled STENT GRAFT MONITORING ASSEMBLY AND METHOD OF USE THEREOF; U.S. Serial No. 14/776,646 and International Application No. PCT/US2014/028323, entitled STENT MONITORING ASSEMBLY AND METHOD OF USE THEREOF; U.S. Serial No. 14/776,650 and International Application No. PCT/US2014/028381, entitled DEVICES, SYSTEMS AND METHODS FOR MONITORING HIP REPLACEMENTS; U.S. Serial No. 14/392,173 and International Application No. PCT/US2014/043736, entitled DEVICES, SYSTEMS AND METHODS FOR MONITORING KNEE REPLACEMENTS; U.S. Serial No. 15/320275 and International Application No. PCT/US2015/037823, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING TUBES IN BODY PASSAGEWAYS; U.S. Serial No. 15/320279 and International Application No. PCT/US2015/037803, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING IMPLANTS; U.S. Serial No. 15/320284 and International Application No. PCT/US2015/037825, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING SPINAL IMPLANTS; U.S. Serial No. 15/320289 and International Application No. PCT/US2015/037827, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING ORTHOPEDIC HARDWARE; U.S. Serial No. 15/320292 and International Application No. PCT/US2015/0037828, entitled POLYMERS, SYSTEMS AND METHODS FOR USING AND MONITORING POLYMERS FOR USE IN MEDICAL POLYMERS, IMPLANTS, AND PROCEDURES; U.S. Serial No. 15/320296 and International Application No. PCT/US2015/037810, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING HEART VALVES; U.S. Serial No. 15/078604 and International Application No. PCT/US2015/050789, entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING MEDICAL DEVICES; and U.S. Serial Nos. 62/312072, 62/312079, 62/312095, 62/312108, 62/312114, 62/312120, 62/312131, 62/312180, 62/312188, 62/312193, 62/312197, and 62/312205.

[0054] Other representative examples of various objects (e.g., wearable devices, sports equipment, an area of play, and/or external medical devices) having one or more sensors as provided herein include those described in the following patent applications (all of which are hereby incorporated by reference in their entirety): U.S. Serial No. 62/220,239 and U.S. Serial No. 15/268575 entitled DEVICES, SYSTEMS AND METHODS FOR USING AND MONITORING SPORTS EQUIPMENT AND SPORTS ACTIVITIES, as well as U.S. Patent Nos. 8,180,591 and 8,475,367, and U.S. Serial Nos. 2014/0275852, 2014/0142403, US2014/0197946, US2014/0180019, US2014/0164611, US2014/0135612 and US2015/0182797. Other examples of external devices include, for example, those described in U.S. Patent No. 5,363,842, and in U.S. Serial Nos. 2009/0194104, 2010/016860 and 2010/019294, 2013/0317379, 2014/0316296, and 2015/0126889.

[0055] The present disclosure may be understood more readily by reference to the following detailed description. It is to be understood that the terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting. It is further to be understood that unless specifically defined herein, the terminology used herein is to be given its traditional meaning as known in the relevant art. Any headings used within this document are only being utilized to expedite its review by the reader, and should not be construed as limiting the claims in any manner. In order to further understand the various aspects provided herein, the following sections are provided below: A. Dataset Transaction; B. Information Collection and Marketplace System; C. Example of an Implantable Medical Device; and D. General Considerations.

A. Dataset Transaction

[0056] One example of a representative dataset transaction is provided in FIG 1. The transaction may be performed by the system of FIG. 3. In this embodiment, information that is owned by an individual or an entity may be transferred to another individual or entity in exchange for consideration. The consideration can be money, a future promise, access to research or other technical information that results from use of the dataset, particular medical treatment, or some other form of compensation, and includes a specification of the terms governing the use of the information provided.

[0057] Processing of an information transaction begins at block 1 "START". At block 2 a request for a productized dataset is made. This request may be made through a computing device llla-llld. In some embodiments, a request for a productized dataset comprise two elements: 1) a "specification of the dataset" and 2) a "specification of the consideration" offered for the information in the dataset. In some embodiments, as a request for a productized dataset may only comprise a "specification of the dataset".

[0058] The specification for the dataset (also referred to as a "dataset specification") can include a variety of parameters, including for example: (i) information in specific fields of records that define the records in a database that will be searched; (ii) the number of records required to constitute the desired dataset that contain information in each of the specified fields; and (iii) an optional selection protocol by which records with information in each of the specified fields will be included in the desired dataset. A selection protocol may state that of the required number of records, a certain portion (e.g., percentage) should meet a particular selection criterion. For example, a selection protocol may specify that 50% of the records be from female individuals and 50% be from male individuals.

[0059] Regarding the specific fields of item (i), the information in these fields describe the personal information being sought by the request. This personal information may include demographic information, geographic location information, personal habit information, physical trait information, and medical information. Medical information may include, medical device information, medical- device reported information (e.g., physiological information sensed by a medical device, activity information sensed by a medical device), patient-reported information, physician-reported information. Medical device information may include device type information, manufacturer information, device operation information (e.g., stimulation parameters, sensor types, fault information, battery life information, power status information, device temperature information, structural integrity information), or nearly any other kind of information that is relevant to the dataset being requested. Device operation information is generally associated with operation of the medical device. For example, device operation information may include a count of flexures of an artificial knee or hip joint, a volume of blood passed through a stent, a number of abnormal heart signal detections and corresponding electrical impulse firings of a pacemaker, and the like. Fault information may be any improper, unexpected, or recognized errant operation of the device.

[0060] The specification of the consideration (also referred to as "consideration specification") to be provided for the information can also include a variety of parameters, including for example: (i) The terms of use for the information in the dataset, including, but not limited to, the user, usage and purpose of the collected information (e.g. Company for market research, an academic for basic science research, a device manufacturer for product performance assessment, etc.); and the time period for which the information in the dataset can be used; and (ii) the compensation to be provided to the owners of the information.

[0061] For example, if a research study is being undertaken to determine patterns or trends with a particular implantable medical device from a particular manufacturer, a researcher can determine how many individuals have had the subject device implanted in a particular location during a particular time. This number of individuals may be considered a targeted device population ("population"). The researcher can further determine how many cases within the targeted device population they wish to include in a dataset in order to reach meaningful conclusions. This number of individuals may be considered the sample of the device population ("sample"). The researcher can further determine what information is required from each individual in the sample. The researcher can also determine the price they are willing to pay for this information. Based on these determinations, the researcher can provide a request for a productized dataset at block 2.

[0062] A particular database 17 is maintained. Within the database 17, a plurality of records is stored. The records comprise a plurality of fields, which may also include subfields or some other units of information. Each record, or groups of records, can also include other information such as a pre-set price, which may include either or both of consideration to be paid for granted access to the information and the terms on which such access is granted, that an owner of the information has already agreed to.

[0063] Each record in the database can be assigned to a particular individual owner. In many cases, the individual owner is also the individual whose information is represented in the record. For example, when fields in the record store medical information, the individual owner may be the patient that generated or is the source of the medical information. For example, the patient may have an implanted medical device that senses and collects the medical information from the patient, or may have an external device, e.g., wearable device, that collects the medical information from the patient. In other cases, a particular record may have been transferred from its individual owner to another owner who may be an individual or an entity. One individual may own a plurality of records. One entity may own a plurality of records. The owner of the record, or a surrogate for the owner, is empowered to make decisions regarding the inclusion of their information within the record. Specifically, the owner of the record is empowered to determine if their information is used and for what purposes it is being used (informed consent).

[0064] Continuing with FIG. 1, at block 3 an information match process is executed in accordance with subroutine A (see FIG. 2A). To this end, a record is extracted from the database 17 and the content of the record is compared with the parameters of the dataset specification that define the request for the productized dataset provided at block 2. To this end, in subroutine A, the productized dataset request provided at block 2 is used to generate a search criteria at block 20. At block 21, a record is extracted from the database at block 17 (see FIG. 1), and then at block 22 the information contained in the record is compared with the parameters included in the request for productized dataset. If the extracted record satisfies the parameters in the request, the process passes to block 4 (see FIG. 1). If the extracted record does not satisfy the parameters, the process passes to block 14 (see FIG. 1). [0065] If Subroutine A of FIG. 2A passes processing from block 3 to block 4 in FIG. 1, a Consideration Match process is executed in accordance with subroutine B (see FIG. 2B). At block 30 compensation criteria are defined using the request for the productized dataset provided at block 2 (see FIG. 1), or using the consideration criteria arising from the outcome of an auction at block 12. At block 31, the record passed from block 3 (see FIG. 1) and subroutine A (see FIG. 2A) is fetched, and at block 32, the relevant fields from the record are compared with the compensation criteria from block 30. If the relevant fields match the compensation criteria, at block 33 processing passes to block 5 (see FIG. 1), and if not, at block 34 processing passes to block 10 (see FIG. 1). [0066] If subroutine B (see FIG. 2B) has passed processing to block 5, the record matches both the information and consideration requirements for inclusion in the productized dataset, and so the record is included in the productized dataset. Processing then passes to block 6, where the dataset compiled to this point in the process is compared with the requested productized dataset. If the dataset is complete, the transaction is completed at block 7. Completing the transaction at block 7 includes creating the productized dataset, which can include consolidating the records, transferring the productized dataset to the requestor, compensating the information owner(s) or other authorized party or parties, updating records in the database to reflect the transaction, and other tasks. Productizing the dataset, as described herein, includes formatting the information so that it conforms to the agreed-upon terms, which may include removing personally identifiable information (i.e., anonymizing the data), obfuscating (e.g., encrypting) the data for security purposes, preparing and /or implementing a terms-of use agreement corresponding to details of the transaction, forming the information into one or more computer-readable files, and the like. If the dataset is not complete, processing passes to block 8.

[0067] At block 8, it is determined whether or not all the records in the database have been compared with the information and consideration criteria. If unexamined records remain in the database, processing passes to block 9, where the next record in the database is fetched from the database at block 17, and processing passes back to block 3, which invokes subroutine A.

[0068] If a record that has been passed from subroutine B to block 10 (because it has failed to meet the compensation criteria), that record is added to the "auction pool" at block 10. The Auction pool consists of all those records that meet the search criteria defined in subroutine A but do not explicitly meet the compensation criteria in subroutine B. With each addition of a record to the auction pool, processing passes to block 11, which invokes subroutine C (see FIG. 2C).

[0069] Subroutine C imports the consideration criteria defined at block 30 in subroutine B (see FIG. 2B). At block 41, an analysis of the records contained in the auction pool, as defined at block 10 in FIG. 1, reveals the nature of the known consideration requirements of the owners of the relevant records. At block 42, a comparison of the consideration criteria with the consideration requirements of the auction pool considered as a population allows for the determination of an optimal auction algorithm at block 43; that is, an auction algorithm that comes closer than any other practical auction algorithm that can be executed within a reasonable time at reasonable cost, to maximizing the likelihood that the request for the productized dataset can be met. At block 44, the results of the optimal auction algorithm are modeled using computerized simulations. If the results of these simulations are acceptable, processing passes to block 45, which passes processing back to block 12 (see FIG. 1). If the results of the simulations are unacceptable, processing passes to block 46, which passes processing back to block 9 (see FIG. 1).

[0070] If processing passes from 11 (see FIG. 1) to block 12, the auction is conducted using the optimal algorithm identified in subroutine C, by invoking subroutine D (see FIG. 2D). At block 50, the owners of the information contained in the records included in the auction pool are informed of the discrepancies between the offered consideration and the consideration required either by themselves individually or by the auction pool as a whole, or of some subset of the auction pool, as dictated by the optimal auction algorithm, as defined in subroutine C. These discrepancies are divided into discrepancies related to terms, at block 51, and discrepancies related to compensation, at block 53. At block 52 and block 54 auction algorithms are run which create an opportunity for the requester of the productized dataset and the owners of the information contained in the relevant records to define mutually acceptable consideration forthe inclusion ofthe information in the productized dataset. The outcomes of the overall auction algorithm (whether consisting of multiple algorithms or only one) for each record included in the auction pool are passed, at block 55, to block 13 (see FIG. 1).

[0071] At block 13 (see FIG. 1), the outcomes of subroutine D are processed by executing the consideration match process in accordance with subroutine B (see FIG. 2B), described above. If a record now meets the consideration criteria, either as originally stated or as revised through auction process, processing passes to block 5. Should enough records have been added to the dataset as a result of revising the consideration criteria or revising the information owners' requirements so that the dataset is now complete, as assessed at block 6, processing passes to block 7, and the transaction is completed.

[0072] In various embodiments described above, processing may pass to block 4 by subroutine A. If, alternatively, subroutine A passes processing from block 3 to block 14, a record does not contain the information specified in the productized dataset request. At block 14, additional information is solicited from the owner of the information contained in the relevant record. This consists of informing the owner of the information contained in the relevant record of (a) what additional information is requested; (b) the consideration offered for the information; (c) the appropriate mechanism for providing the relevant information. If the information is provided, processing passes to block 3, and the revised record is processed by subroutine A. If the additional information is not supplied, processing is passed to block 9, and the next record is fetched from the database at block 17.

[0073] In other embodiments described above, processing may pass from block 8 to 9 because unexamined records remained in the database. Alternatively, if all the records in the database have been examined and the requested productized dataset remains incomplete, processing passes to block 16, which defines an alternative request for a productized database (e.g., through subroutine E). For example, if a buyer is seeking data from a single city, and an insufficient number of records were located, the system may suggest a wider geographic area such as a county that includes the city. As another example, if a buyer is seeking data associated with men between the ages of 25 and 30, and an insufficient number of records were located, the system may suggest a wider age range, or data that includes both men and women. As another example, if an insufficient number of records were located, the system may suggest a smaller number of records. As another example, an alternative, and likely higher, price may be suggested, or more lenient terms of use might be suggested, in order to entice owners of data that refused the initial offer to accept. More generally, different terms and considerations will be suggested that are likelier to result in completing a request for a productized dataset while still addressing the needs that motivated the original request. Pending acceptance, either on the basis of what is suggested by the embodiment or other means, a modified request for a productized dataset is triggered, and processing passes to block 2.

[0074] Processing proceeds to block 7 and ends with a completed dataset transaction.

B. Information Collection and Marketplace System [0075] FIG. 3 illustrates one representative system 100 configured to collect personal information and provide a computer-based marketplace to sell the collected personal information. The system 100 includes one or more medical devices 104, a marketplace computing server 110, one or more computing devices llla-llld, and a network 106 and an interface 108 that enable communication among the medical devices, the marketplace computing server, and the one or more computing devices.

[0076] As shown in FIG. 3, one or more medical devices 104 of the system 100 may be associated with an individual 102. In some embodiments a medical device 104 is an implanted medical device 103. In some embodiments a medical device 104 is an external medical device 105. In some embodiments a medical device 104 includes a first portion that is implanted inside the body of the individual 102 and a second portion that is completely or partially outside of the body of the individual 102. In FIG. 3, a first individual 102 is illustrated along with an optional plurality of other individuals 102a-102n. Within the context of this disclosure, an individual 102 is referenced. It is understood, however, that any number of other individuals having any number of same or different types of medical devices 104 are contemplated.

[0077] An implanted medical device 103 may be a mechanical device, an electromechanical device, a chemical delivery device, or some other implanted medical device as provided herein. For example, the implanted medical device 103 may be a pacemaker or another type of electromechanical device, an artificial joint, a stent or a different medical device to support an internal biological structure, an insulin pump or another pump to move a medicament into or through a patient, or some other medical device. Additional examples of medical devices include cardiovascular implants such as implantable cardioverter defibrillators, stent grafts, bypass grafts, catheters, balloons and heart valves, orthopedic replacement prosthesis such as legs and hands, orthopedic implants such as hip, shoulder and knee prosthesis, spinal implants and hardware (spinal cages, screws, plates, pins, rods and artificial discs), intrauterine devices; orthopedic hardware used to repair fractures and soft tissue injuries (casts, braces, tensor bandages, plates, screws, rods, pins and plates), cochlear implants, aesthetic implants (breast implants, fillers), dental implants, medical polymers; and artificial intraocular eye lenses.

[0078] Representative examples of external medical devices include wearable biometric monitoring devices configured to collect one or more types of biometric data, e.g., data pertaining to physical characteristics of the human body (such as heartbeat, heart rate, perspiration levels, etc.) and/or data relating to motion and activity of that body with the environment (such as accelerometer readings, gyroscope readings, etc.). Examples of wearable biometric monitoring devices include smartwatch, disposable patches, strap devices (e.g., a Holter monitors), and athletic apparel.

[0079] The medical device 104 is configured to deliver medical device information to the server 110, including medical device information and medical-device reported information. In some cases, patient-reported information such as pain, function, activity, quality of life, sleep, medication usage, emotional and psychological wellbeing, and rehabilitation efforts, may be input to the medical device 104 by the individual 102. In such cases, the information delivered by the medical device 104 to the server 110 includes the patient-reported information.

[0080] As previously described, medical-device reported information may include, for example, physiological information of the individual 102 as sensed by the medical device, such as blood pressure, heart rate, glucose levels, or activity or motion information of the individual as sensed by a medical device. Medical device information may include device type information, an identification number that uniquely identifies the medical device 104 within a particular group of other medical devices, manufacturer information, information that that associates or links the medical device 104 to the particular individual 102, and device operation information. Device operation information generally includes device diagnostics information, such as fault information and battery life information. Other types of device operation information depends on the type of medical device. For example, in the case of a pacemaker or neuromodulation device, device operation information may include stimulation parameters, number of stimulation pulse delivered, number and type of cardiac arrythmias detected, or number and type of abnormal brain activity detected. In the case of orthopedic medical devices, such as an artificial joint, the device operation may include structural integrity information indicative of a range of motion or stress regarding the artificial joint.

[0081] The medical device 104 includes a communication interface that allows data collected and stored in the device to be communicated. In some implementations, the medical device 104 communicates directly with the network 106. In other cases, the medical device 104 communicates directly with an interface 108. In the case of an implanted medical device 103, the data is communicated from inside the body of the individual 102 to outside of the body. Such communications may be facilitated by a wireless protocol, a Bluetooth protocol, or some other protocol. In the case of external medical device 105, the communication may be facilitated by a wired or wireless protocol, a universal serial bus (USB) protocol, a Bluetooth protocol, a single wire interface (SWI) protocol, or some other protocol. The communication may occur in a unidirectional or bidirectional peer-to-peer exchange, personal area network (PAN), local area network ( LAN ), or wide area network (WAN).

[0082] Network 106 may be configured to include some or all portions of personal area networks (PANs), local area networks (LANs), or wide area networks (WANs). For example, communications from the medical device 104 may be via a Bluetooth PAN connection, a Wi-Fi or wired LAN connection, a GSM or CDMA cellular WAN connection, or in some other way. [0083] Interface 108 is shown as an optional device. Interface 108 may be electromechanically coupled to an implantable medical device 103 in cases where the implanted medical device has a corresponding port accessible from outside of the body of the individual 102. In other cases the interface 108 may be a portable device placed in proximity of the medical device 104, whether it be an implanted medical device 103 or an external medical device 105. For example, if the medical device 104 is an implanted medical device 103 that includes a radio frequency identification (RFID) module, then interface 108 may be configured as an RFID terminal host located in the office of a medical practitioner. When the individual 102 visits the office of the medical practitioner, the medical practitioner uses the interface 108 during an examination of the individual 102, and interface 108 collects data from the implanted medical device 103. In yet other cases, interface 108 may include a Bluetooth transceiver configured as a master device capable of interrogating a medical device 104 to collect information. Other configurations and communication technologies are considered.

[0084] Marketplace computing server 110 illustrates portions of a non-limiting embodiment of a computing server that includes operative hardware found in a conventional computing device such as one or more processing units 114, volatile and non-volatile memory 116, and serial and parallel input/output (I/O) circuitry 112 compliant with various standards and protocols, wired and/or wireless networking circuitry ( e.g ., a communications transceiver).

[0085] As known by one skilled in the art, a computing device such as marketplace computing server 110 has one or more memories 116, and each memory comprises any combination of transitory and non-transitory, volatile and non-volatile computer-readable media for reading and writing. Volatile computer-readable media includes, for example, random access memory (RAM). Non-volatile computer-readable media includes, for example, read only memory (ROM), magnetic media such as a hard-disk, an optical disk drive, a flash memory device, a CD-ROM, and/or the like. In some cases, a particular memory is separated virtually or physically into separate areas, such as a first memory, a second memory, a third memory, etc. In these cases, it is understood that the different divisions of memory may be in different devices or embodied in a single memory. Some or all of the stored contents of a memory may include software instructions executable by a processing device to carry out one or more particular acts.

[0086] Marketplace computing server 110 further includes operative software found in a conventional computing server such as an operating system, software drivers to direct operations through the I/O circuitry 112, networking circuitry, and other peripheral component circuitry. In addition, marketplace computing server 110 includes operative application software such as network software for communicating with other computing devices, database software for building and maintaining databases, and task management software for distributing the communication and/or operational workload amongst various processing units. In some cases, marketplace computing server 110 is a single hardware machine having the hardware and software listed herein, and in other cases, marketplace computing server 110 is a networked collection of hardware and software machines working together in a distributed fashion to execute the functions of the system to collect personal information including in particular, medical information and provide a computer-based marketplace to sell the collected information. Conventional hardware and software of marketplace computing server 110 is not shown in FIG. 3.

[0087] Several other computing devices are also illustrated in FIG. 3 including a laptop computer 111a, a tablet computer 111b, a desktop computer 111c, and a smart phone mobile device llld. One of skill in the art will recognize that these other computing devices llla-llld also include components similar to I/O logic 112, processing unit 114, and memory 116, and these components are not illustrated for simplicity.

[0088] The memory 116 in FIG. 3 includes a plurality of modules including a database 118, an information input logic module 122, an information delivery logic module 124, a Web server/browser logic module 126, an optional (reverse) auction logic module 128, an acceptable buyer terms logic module 130, a buyer modification logic module 132, an acceptable seller terms logic module 134, a seller modification logic module 136, a seller pool logic module 138, a seller compensation logic module 140, an anonymizer logic module 142, an obfuscation/de-obfuscation keys module 144, and a database searching logic module 146.

[0089] The database 118 is a storage module configured as programmatic application to store raw and processed information. The database 118 may be any combination of a traditional database, one or more database systems, a file system, or any other method known in the art for storing such information using known database techniques, including an implementation using distributed computing techniques. The database 118 may include features that permit the database to expand as new information is added and to contract as information is removed. The database 118 includes an interface that permits programmatic database commands and queries, for example, commands and queries generated by information input logic module 122, information delivery logic module 124, and database search logic module 146.

[0090] Information stored in the database 118 may be stored in records or in some other format. The particular records stored in the database 118 can be archived, duplicated, deleted, edited, and the like. In some cases, entire information records or portions of information records may be protected as confidential. For example, obfuscation logic/de-obfuscation keys module 144 may stand alone or cooperate with the database 118 to encrypt, obfuscate, or otherwise to store information in a confidential way, and to permit authorized parties to access the information.

[0091] Particular information records stored in the database 118 may be electronically transferred in whole or in part, and the records may be mined for information, which may then be distributed in return for consideration.

[0092] The information input logic module 122 works cooperatively with I/O circuitry 112, the database 118, the obfuscation logic/de-obfuscation keys module 144, and other modules of the marketplace computing server 110. The information input logic module 122 receives medical information from a medical device 104 or other medical information associated with an individual 102, organizes the medical information, and stores the medical information in the database 118, together with other personal information of the individual. In some cases, the medical information is tagged, obfuscated, aggregated, categorized, modified, or adapted in some other way in association with storage in the database 118.

[0093] The information input logic module 122 also processes external requests to search or retrieve information from the database 118. For example, in some cases, information input logic module 122 will receive a request from an outside source for a plurality of productized datasets. The request includes a data specification that define fields that are common to each of the plurality of productized datasets that are sought by a particular source. In the case of medical information, for example, a particular medical device company may seek productized datasets for a particular type of medical device implanted into patients having a particular demographic profile. In this case, the information input logic module 122 will parse the request, and generate one or more queries that are passed to the database 118 in search of records that match the defined fields of the request.

[0094] The information delivery logic module 124 is configured to customize information into one or more dynamically productized datasets and deliver productized datasets to an outside source. As discussed herein for medical information, such information may be stored in the database 118, and portions of the information may be consolidated and communicated to an outside source. For example, within one embodiment, if a plurality of records are retrieved from the database 118, a portion of information in the records may be packaged as part of a sale, lease, license, or other authorized transfer of such information. The information delivery logic module 124 formats the information into one or more productized datasets. The information delivery logic module 124 also communicates the productized datasets. In cases where some or all of the information is obfuscated, the information delivery logic module 124 works cooperatively with the obfuscation logic/de obfuscation keys module 144 to also provide keys or other security information to the outside source such that the information included in the productized dataset is accessible.

[0095] The optional (reverse) auction logic module 128 module is arranged to carry out features of a traditional auction or a reverse auction for medical information. Generally speaking, traditional auctions are auctions where buyers compete to purchase a good or service, and in contrast, reverse auctions are those auctions where sellers compete for opportunities to provide a good or service. The goal of a traditional auction is to drive up a bidding price, while that of a reverse auction is to drive down the bidding price.

[0096] Various parties may want to participate in auctions targeted to the transfer of medical information in exchange for consideration based on economic and other incentives. An operator of the marketplace computing server 110 may benefit by charging a fee to provide the auction services. Individuals 102 may benefit by receiving money in exchange for access to their medical information. Buyers, e.g., medical device makers, medical practitioners, researchers, and others, may benefit by having access to a pool of medical information that may be searched or customized for their particular use. [0097] When the optional (reverse) auction logic module 128 is set up to conduct a traditional auction, an operator of the marketplace computing server 110 may recognize a need for a particular type of information. For example, medical information associated with a large number of external medical devices in the form of running shoes with motion sensors, as collected from participants in a marathon running race, may be of use to shoe designer. In this case, if the operator of the marketplace computing server 110 recognizes that access to such medical information may be valuable to running shoe designers, the marketplace computing server 110 may initiate a traditional auction that consolidates such information into a productized dataset and offer access to the information to the highest bidder. In this case, the marketplace computing server 110 may transmit auction information to a number of computing devices llla-d associated with buyers that describes the medical information and an minimum acceptable compensation for the information. Additional details on an action process implemented by the marketplace computing server 110 is describe below with reference to FIG. 5.

[0098] Alternatively, reverse auctions are those auctions where sellers compete to provide their product or service against others that also have a competing product or service to sell. In this case, a large number of individuals 102, 102a-102n may be willing to sell certain medical information, for example information associated with a particular type of medical device. If a buyer is looking for a plurality of such medical information, there may be more information available than the buyer is looking for. Alternatively, the buyer may be looking for medical information from a certain percentage of individuals 102 who are willing to provide such information. In the case of a reverse auction, the individuals 102 may provide through a computing device llla-d a price at which they are willing to provide their information. The optional (reverse) auction logic module 128 may be configured to select productized datasets from an appropriate number of individuals 102 based on the prices at which the individuals are offering to provide the information.

[0099] The acceptable buyer terms logic module 130 works cooperatively with the information input logic module 122 to parse a request for one or more productized datasets. In this case a particular party or entity may wish to buy productized datasets at a particular price, any particular quantity, from a pool of sellers having a particular number of sellers in the pool, according to particular demographics or other qualifying information, any particular price, with respect to a particular date that the information was collected or will be delivered, and according to other conditions. Particularly, the acceptable buyer terms logic module 130 receives and structures terms of a transfer of medical information that are acceptable to the party that will provide consideration in return for the transfer of the medical information.

[00100]The buyer modification logic module 132 cooperates with the information input logic module 122 to allow changes to the terms of a medical information transaction. For example, the buyer modification logic module 132 may solicit a buyer, via a computing device llla-d associated with the buyer, to change a parameter of its dataset specification or a parameter of its consideration specification in order to enable the finding of database records that satisfy the request submitted by the buyer.

[00101]The acceptable seller terms logic module 134 is similar to the acceptable buyer terms logic module 130, and the seller modification logic module 136 is similar to the buyer modification logic module 132. For example, the seller modification logic module 136 may solicit a seller, via a computing device llla-d associated with the seller, to change its database record in orderto enable the database record to satisfy the request submitted by a buyer. Such changes may include broadening the scope of medical information available for purchase from the seller, or reducing the expected compensation for the medical information.

[00102]With respect to a particular transaction wherein a plurality of productized datasets are communicated from the marketplace computing server 110 to another computing device llla-llld associated with a particular buyer, a seller of medical information may determine and modify acceptable terms of the transaction.

[00103]The seller pool logic module 139 is arranged to manage datasets that have one or more defined fields in common. For example, the database 118 may include medical information associated with tens, hundreds, thousands, or millions of individuals. A first pool of individuals may include all of the individuals that are biologically male, and a second pool of individuals may include all of the individuals that are biologically female. A third pool of individuals may include all of the individuals that are older than 25 years. It is recognized that the third pool of individuals will in all likelihood include members of both the first and second pools, but members of the first pool are in all likelihood not included as members of the second pool. By way of example above, it is recognized that medical information records in the database 118 may be parsed and pooled in any number of ways. Seller pool logic module 139 is arranged to identify and retrieve records according to requests that define one or more fields, characteristics, or other criteria.

[00104]The seller compensation logic module 140 is configured to recognize when medical information associated with a particular individual 102 is included in a productized dataset that is communicated from the marketplace computing server 110 as part of a transaction. In this case, the seller compensation logic module 140 will credit, pay, or otherwise account for compensation (i.e., consideration) on behalf of the particular individual.

[00105] Within various embodiments the anonymizer logic module 142 is configured to act on medical information during the formation of productized datasets. This may be done for security reasons, government regulation reasons, private contractual reasons, or other reasons. Due to the operations of the anonymizer logic module 142, when an outside party receives productized datasets, the outside party is not able to associate specific portions of medical information with any specific individual. For example, an individual's name, address and other confidential information may be scrubbed from the productized dataset.

[00106]The obfuscation logic/de-obfuscation keys module 144 may be arranged to encrypt, decrypt, or otherwise secure some or all of the medical information stored in the database 118. The information may be secured to fulfill obligations under contract with individuals that provide medical information, obligations under the Health Insurance Portability and Accountability Act (HIPPA), or for some other regulatory, consent, or privacy reason.

[00107]The database search logic module 146, as discussed earlier, is arranged to generate, process, or carry out specific search requests relative to the database 118. The database search logic module 146 may include error correction capabilities, voice recognition, natural language processing for the automatic generation of search inquiries, or other particular features.

[00108]Within alternative embodiments, the database 118 of FIG. 3 may be utilized to store and process a dataset transaction as described in FIG. 1 ( e.g ., the database 17 of FIG. 1).

[00109]A web server/browser logic module 126 includes operative hardware and software to support Internet-style functionality. In some cases, the web server/browser logic module 126 operates as a web server to generate and deliver webpages over network 106 to other computing devices 111a- llld. The generated webpages may include any multimedia type information including audio, video, still images, text, programmatic components executable components interpreted software code, and the like, which may collectively be known by the term, "screen information." In other cases, the web server/browser logic module 126 operates as a web browser to receive webpages and render them on a display device.

[00110]As should be readily apparent given the disclosure provided herein, the database 118 (and accompanying software and logic circuits provided in FIGS. 1 and 3) may be composed of a single central unit, or optionally, divided into one or more separate locations. For example, more than one physical database can contain the collective information that is to be processed in a dataset transaction. Similarly, the processing functions can be divided into one or more different physical locations in such a manner so as to still act with one accord.

[00111] FIG. 4 illustrates one representative implanted medical device 103 that includes one or more sensors 151, a processing unit 114a and memory 116a all associated with a functional structure. Additional sensors (not shown) of the implanted medical device 103 may be separate from the functional structure. The functional structure will typically define the implanted medical device 103. For example, considering the case when the implanted medical device 103 is an artificial cervical disc, the functional structure may include to cobalt chromium alloy and plates and an ultrahigh molecular weight polyethylene core. As another example, considering the case when the implanted medical device 103 is an artificial hip, the functional structure may include an acetabular cup, a polyethylene insert, a metal femoral head, and a femoral stem.

[00112]The processing unit 114a and memory 116a may be particularly suited to an embedded environment. The processing unit 114a and memory 116a have characteristics along the lines of the processing unit 114 and memory 116, respectively, of FIG. 3, though specific details are omitted for brevity.

[00113]The one or more sensors 151 may be any one of the sensors previously described herein that is configured to sense and detected medical information. This medical information may be stored in the memory 116a and provided to the marketplace computer server 110 for inclusion in a database record. The medical information may include medical-device reported information, including for example, physiological information or activity information sensed, for example, by one or more fluid pressure sensors, fluid volume sensors, contact sensors, optical sensors, position sensors, pulse pressure sensors, blood volume sensors, blood flow sensors, chemistry sensors ( e.g ., for blood chemistry and/or other fluids), metabolic sensors [e.g., for blood and/or other fluids), antibodies, accelerometers, mechanical stress sensors and temperature sensors. In some embodiments, the information collection interface will collect information from multiple sensors, e.g., an accelerometer and a gyroscope, which information is collected and collated along with an internal time stamp. [00114]0ne or more optional modules may be provided in an implanted medical device 103. For example, the implanted medical device 103 may include a power source 148, a wireless communications interface 150, an electromechanical communications interface 152, an information collection interface 154, and a security module 156.

[00115] Power source 148 may include a battery, a capacitor, or circuitry arranged to generate power based on externally provided stimuli. For example, in some cases, power source 148 is a nickel- cadmium battery, a zinc-mercury battery, a lithium-iodine battery, or a battery having some other chemical composition. Such a battery may be rechargeable. In other cases, power source 148 may include an electronic circuit configured to generate power when stimulated by kinetic energy, electromagnetic energy, or some other stimuli. Power generated by power source 148 is passed to processing unit 114a, memory 116a, and optionally other components of the implantable medical device 103.

[00116]The optional wireless communication interface 150, when included, is used to communicate information to, from, or to and from the implanted medical device 103. A wireless communication interface 150 may conform to a radio-frequency identification (RFID) protocol, a near field communication (NFC) protocol, and IEEE 802.11 WiFi protocol, or some other protocol. Generally speaking, such protocols permit two or more devices to establish radio communications when the devices are in close physical proximity [e.g., 10 meters or less) to each other. In these cases, the devices operate by electromagnetic induction between two loop antennas; one antenna in the implanted medical device 103 and another antenna in an external communication device. In these cases, the communications may conform to a standardized protocol provided by one or more standardization bodies.

[00117]An optional electromechanical communications interface 152, when integrated with an implanted medical device 103, is used to communicate information to, from, or to and from the implanted medical device. An implanted medical device 103 may have either or both a wireless communications interface 150 and an electromechanical communications interface 152. The electromechanical communications interface may conform to a standardized protocol provided by one or more standardization bodies, or the electromechanical communications interface 152 may operate according to a proprietary or some other protocol. The electromechanical communications interface 152 may pass information collected by the medical device 104 as a serial bit stream, a parallel set of bits, a sequence of packets, or in some other form.

[00118] In some embodiments, the electromechanical communications interface 152 is arranged as a port, housing, cable, or in some other form. In some cases, communications with the implanted medical device 103 occur via a cable plugged in or otherwise communicatively coupled to the electromechanical communications interface 152.

[00119] During normal operation, the implanted medical device 103 will collect medical information, including medical device information and medical-device reported information (e.g., physiological information sensed by one or more sensors 151, activity information sensed by one or more medical sensors, etc.). Medical device information may include device type information, manufacturer information, device operation information (e.g., stimulation parameters, sensor types, fault information, battery life information, power status information, device temperature information, structural integrity information), or nearly any other kind of information that is relevant to the dataset being requested. Device operation information is generally associated with operation of the medical device 104. For example, device operation information may include a count of flexures of an artificial knee or hip joint, a volume of blood passed through a stent, a number of abnormal heart signal detections and corresponding electrical impulse firings of a pacemaker, and the like. Fault information may be any improper, unexpected, or recognized errant operation of the device.

[00120]Wireless communications interfaces 150 and electromechanical communication interfaces 152 are controlled by processing unit 114a under direction of software instructions stored in memory 116a. Information collected by the implantable medical device 103 and information targeted toward the implanted medical device 103 may be passed between the wireless communication interface 150 or the electromechanical communications interface 152 and an external communication device such as interface 108 (FIG. 3) or a computing server 110 (FIG. 3). The information may be arranged as a serial bit stream, a sequence of packets, or in some other form.

[00121] In addition to information, energy may also be passed through the wireless communication interface 150 or the electromechanical communications interface 152 in cooperation with power source 148. The energy may be used to charge a battery, fill a storage capacitor, power the respective communication interface, power the processing unit 114a, power the memory 116a, and for other reasons.

[00122]The optional information collection interface 154 works cooperatively with the functional structure or other parts of the implantable medical device 103 to capture other medical-device reported information or medical device information. The information collection interface 154 may include electrical components, mechanical components, electromechanical components, or other components. For example, the information collection interface 154 may include electronic timers, temperature sensors, strain gauges, accelerometers, probes, electrodes, moisture sensors, and many other components. [00123]The memory 116a of the implanted medical device 103 may optionally include a security module 156. The security module 156 may be arranged to encrypt information, decrypt information, prevent tampering with software instructions stored in the memory 116a, and the like. In some cases, information that is collected by the implanted medical device 103 is encrypted. The encryption may be performed for compliance with government regulations such as the health insurance portability and accountability act (HIPAA), for security of the information from unauthorized access, or for other reasons. The security module may perform operations according to an advanced encryption standard (AES), a date encryption standard (DES), or some other security protocol.

[00124] FIG. 5 is an information flow diagram illustrating information communicated between a marketplace computing server 110 and a computing device llla-llld associated with a buyer. The acts illustrated in the flow diagram may be carried out by a processing unit 114 (FIG. 3) executing software instructions stored in a non-transitory computer-readable storage medium such as memory 116 (FIG. 3).

[00125] In FIG. 5, a first marketplace computing server 110 is communicatively coupled through a network 106 to one or more computing devices llla-llld, which may be laptop computers, desktop computers, tablet computers, mobile devices, or some other type of computing device. The marketplace computing server 110 maintains a database 118 (FIG. 3), which may be local to marketplace computing server 110 or remotely configured and accessible. In some cases, the database 118 is formed as a single information repository in a single location; in other cases, the database 118 is formed as two or more information repositories that may reside in one location or in several locations. Some portions or all portions of the database 118, marketplace computing server 110, and computing devices llla-llld may be distributed across a cloud computing structure facilitated through network 106.

[00126]The database 118 is organized as a plurality of records, each of the records having a plurality of fields. Many and in some cases all of the records stored in the database 118 are assigned an owner. In many cases, the assigned owner is selected when the record is created as the individual who is the source or subject of the information stored in the record. In other cases, the owner of a record may be re-assigned to a new individual. In some cases, some records do not have on assigned owner. [00127]Alternatively, or in addition, in some cases, one or more curators are granted permission to make decisions regarding a grant of access to the information of a plurality of owners. A particular owner and a particular curator may agree to a set of conditions under which the curator may agree to grant access to the owner's information to a particular buyer. For example, a seller may agree that a curator may agree to transfer certain information to a buyer for a selected price. The permission granted to the curator by an owner of the information may be revocable or irrevocable. The terms under which the permission is granted to the curator may be negotiated between the curator and the particular owner of the information.

[00128] Records stored in the database 118 may include a field for artificial joints. Each field for artificial joints may be associated with other fields (i.e., sub-fields) that specify information about one or more artificial joints implanted in an individual. The specified information may include a date of an associated medical procedure, a type of implanted device, the area of the individual's body with the device has been implanted, manufacturing information such as a model number and serial number of the implanted device, and the hospital and attending physician that performed the procedure. Many other types of information may be stored in fields and records in the database 118. Details on the structure and content of database records are provided below with reference to FIG. 7. [00129]Continuing with FIG. 5, and with additional reference to FIG. 3, at act 158, an offer to sell or otherwise distribute certain information stored in the database 118 is presented from marketplace computing server 110 to one or more computing devices llla-llld. At act 160, an offer to buy or otherwise access certain information stored in the database 118 is presented to marketplace computing server 110 from one or more computing devices llla-llld. In some cases, both of the offers at act 158 and act 160 respectively are made, and in other cases, only one of the two offers is made. In some cases, the offer at act 158 occurs before the offer at act 160, in other cases the offer at act 160 occurs before the offer at act 158, and in still other cases, both of the offers at act 158 and act 160 respectively are made concurrently. Generally speaking, in FIG. 5, an offer to distribute information may correspond with a request for access to information, and a request for access to information may correspond with an offer to distribute information.

[00130]When the marketplace computing server 110 provides to one or more computing devices llla-d associated with a buyer, an offer to sell or otherwise distribute certain information at act 158, the offer will define particular characteristics of the information being offered. The selected characteristics correspond to information stored in particular fields of records in the database 118. For example, an offer to sell at act 158 may include information selected only from records that are owned by individuals who have had a knee replacement using an implanted device provided by a certain medical device manufacturer. In this way, it is understood that an offer to sell certain datasets at act 158 may identify particular fields within records of the database having common ( e.g ., identical or substantially the same) information stored in the identified fields.

[00131]Correspondingly, an offer to buy information at act 160 may be received as a request for an information set defining fields common to a plurality of records in the database 118.

[00132] Prior to providing an offer to sell or otherwise distribute certain information at act 158, or after receiving an offer to buy or otherwise access certain information at act 160, the marketplace computing server 110 will search or otherwise interrogate records stored in the database 118 to determine if the records can satisfy a particular request. Searching the database 118 in this way enables the marketplace computing server 110 to find records that contain some or all of the information specified in the particular request (i.e., offer to sell at act 158 and offer to buy at act 160). When particular records are found or otherwise identified as matching the defined fields of the request, information from some or all of the records that were found is retrieved. At least some, and in some cases all, of the retrieved information is formed into a plurality of productized datasets. [00133]At act 162, the particular offers or requests made at act 158 and act 160 may be modified. The modification act at act 162 may be administered by the marketplace computing server 110, one or more computing devices llla-llld, or by a combination of computing devices. Act 158, act 160, and act 162 may be sequential in any order or concurrent. Act 158, act 160, and act 162 may also be iterative such that one or more offers to sell information and one or more offers to buy information are modified two times, three times, or many times.

[00134] In some cases, the modifications at act 162 includes a determination of whether an owner of a record will provide information stored in the record in return for consideration. In some cases, the modifications at act 162 includes the marketplace computing server 110 communicating with one or more computing devices llla-d associated with sellers to obtain an expected compensation to receive in order to grant access to the information. In some cases, the modifications act 162 incudes the marketplace computing server 110 communicating with one or more computing devices llla-d associated with buyers to obtain an expected compensation to pay in order to gain access to the information, or both a seller and a buyer specifying a price. The modifications at act 162 may include a back and forth negotiation of compensation or other terms between a seller or individual assigned owner of the information and a buyer that would like access to the information.

[00135] In some cases, the actions at act 158, act 160, and act 162 may be organized as an auction. The auction may be directed toward a plurality of buyers of information. In this case, a plurality of buyers may each use a computing device llla-llld to enter bids for certain information. The bids may include establishing a price for the information or other terms. Alternatively, the auction may be a reverse auction directed toward a plurality of sellers of information. In this case a buyer may have entered an offer to buy a certain amount of information having certain characteristics defined by fields in the individual records of the database 118. If the marketplace computing server 110 is able to access more than enough information to satisfy the request, a reverse auction may be arranged to identify record owners willing to make their information available to the buyer. In this case, the marketplace computing server 110 communicates with one or more computing devices llla-d associated with sellers to solicit seller bids. The sellers may bid against each other by lowering the price at which they are willing to grant access to their information or by agreeing to other terms more favorable to a prospective buyer of the information. This type of reverse auction may be utilized to establish a price or other terms.

[00136] In some cases, different owners of the information may agree to different prices or other terms from other owners of information. For example, if a buyer offers to buy ten productized datasets that each has particular characteristics, five owners of information may agree to one price, and five owners of information may agree to another price. In this type of circumstance, a buyer of information may individually negotiate with each seller, or the buyer may simply agree to a set of consolidated terms for access to the information, and the marketplace computing server 110 will manage individual agreed upon terms with individual sellers such that an aggregated dataset will meet the consolidated terms agreed to by the buyer. [00137]Additional functions may also be performed within the modifications at act 162. In some cases, the marketplace computing server 110 is unable to find a sufficient number of records having characteristics that match the characteristics of particular request. In these cases, the marketplace computing server 110 may automatically search alternative fields or records. As an example, a case is considered wherein a particular offer to buy information is received at act 160, and the request included in the offer seeks information from individuals who have had a very specific type of knee replacement surgery. In this case, the offer to buy information may narrowly characterize the type of information that is requested by specifying in its dataset specification an individual's gender, age range, dates of surgery, replacement knee manufacturer, replacement knee size, replacement knee model number, and many other characteristics. If the marketplace computing server 110 is unable to find a sufficient number of records having the matching characteristics, the marketplace computing server 110 may automatically modify parameters of the dataset specification to search multiple genders, a wider age range, different dates of surgery, different replacement knee model numbers, and the like. The marketplace computing server 110 will then communicate with a computer device llla-d associated with the buyer to present information about the modified parameters, e.g., alternative fields or records, thereby providing a prospective buyer an opportunity to agree to such alternative information or otherwise modify a request for information. As particular offers to buy are being modified, the marketplace computing server 110 may facilitate communications with individual owners of information to determine if the individual owners are willing to provide their information for an agreed-upon consideration.

[00138]0ther functions that may be performed by the marketplace computing server 110 within the modifications at act 162 include seeking information from one or more alternative databases, soliciting new information from current owners of information that have assigned records within the database 118, and seeking information from new owners that do not currently have any assigned records within the database 118.

[00139]At act 164, agreement is reached. Agreement indicates that the marketplace computing server 110 has identified a sufficient number of records that contain information that satisfies the dataset specification, and the terms of a transfer of the information have been agreed to. The terms are sufficiently defined such that the marketplace computing server 110 clearly identify and deliver the agreed-upon information at an agreed-upon time and in an agreed-upon manner, and the computing device llla-llld can receive the agreed-upon information at the agreed-upon time and in the agreed-upon manner. In addition, the computing device llla-llld can deliver the agreed- upon consideration at an agreed upon time and in an agreed-upon manner, and the marketplace computing server 110 can receive the same.

[00140] Without limitation, agreement functions at act 164 include the programmatic mechanisms to establish, confirm, maintain, and verify, price information, timing information, quantity information, security information, licensing or other qualified use of information, and the like. Table 1 sets forth a list of a non-limiting, exemplary terms of agreement. The agreement functions at act 164 may include all of the terms in Table 1, some of the terms in Table 1, or different terms than those identified in Table 1.

Table 1: Non-limiting, Exemplary Terms of Agreement

[00141]At act 166, the marketplace computing server 110 productizes the identified records retrieved from the database 118 and delivers the productized dataset to the computing device llla-llld. Productizing the information includes formatting the retrieved records in an agreed-upon manner. For example, in some cases, the records are formatted into a single productized dataset such as a spreadsheet. In other cases, one or more records are formatted into a plurality of productized datasets. A dataset may take the form of a spreadsheet, an extensible markup language (XML) document, a human readable text document, a portable document format (PDF) document, a stream of digital information bits, a set of information printed on paper, one or more information files stored on a memory device, or in some other form.

[00142] In some cases, certain information such as private information identifying a specific record owner is removed or otherwise not captured. In some cases, certain information such as information identifying a specific record owner is obfuscated such as by encryption. Other information may also be left out or obfuscated in a productized dataset. In some cases, the information that is left out or obfuscated from a productized dataset is based on the agreed-upon terms between a buyer and seller. [00143]At act 168, optional acts may be performed to transfer de-obfuscation information from the marketplace computing server 110 to a computing device llla-llld. The de-obfuscation information may include, for example, security keys that permit a known decryption algorithm to decrypt or otherwise restore obfuscated productized information.

[00144] FIG. 6 is an implementation of screen information communicated via the system 100. The screen information communicated in FIG. 6 may be associated with the information flow diagram of FIG. 5. In this way, a computer-based marketplace implemented via a marketplace computing server 110 may include web server functionality arranged to host a website. The website is accessible via computing devices llla-llld through network 106.

[00145]The website hosted by the marketplace computing server 110 is arranged to serve a plurality of interactive web pages. Four exemplary web pages are illustrated in FIG. 6 as first, second, third, and fourth sets of screen information 170-176, respectively.

[00146]The first set of screen information 170 may include one or more webpages directed to an offer to sell information, a solicitation of buyers to purchase information, a request to purchase information, or some other set of screen information that facilitates the transfer of productized datasets. The first set of screen information 170 may be associated with act 158, act 160, and act 162 in FIG. 5.

[00147]The second set of screen information 172 may include one or more web pages directed to terms of sale associated with one or more productized information sets. The second set of screen information 172 may be associated with act 158, act 160, act 162, and act 164 in FIG. 5.

[00148]The third set of screen information 174 may include one or more web pages directed to a commitment to buy one or more productized datasets. The third set of screen information 174 may be associated with act 162 and act 164 in FIG. 5.

[00149]The fourth set of screen information 176 may include one or more web pages directed to the transfer of one or more productized datasets from the marketplace computing server 110 to a computing device llla-llld. The fourth set of screen information 176 may be associated with act 166 and act 168 and FIG. 5.

[00150] FIG. 7 is a representative embodiment of acceptable seller terms and acceptable buyer terms for a personal information transaction that includes medical information. The medical information transaction may be carried out according to the information flow illustrated in FIG. 5 and in conjunction with a website delivering screen information as illustrated in FIG. 6.

[00151] In the particular medical information transaction, a computer-based marketplace maintains a database 118 formed of a plurality of records, each record associated with an individual owner. The respective individual owners may have previously expressed an interest in selling information associated with a particular medical condition.

[00152] FIG. 7 illustrates a particular record of one seller wherein individual fields in the record represent personal information ( e.g ., medical information, habit information, trait information, demographic information) exclusive to the respective seller. That is, personal information stored in the record is associated with the specific individual. For example, if the record identifies a particular date of medical treatment, the date represents the day that the specific individual was medically treated. As another example, if the record identifies a particular medical practitioner that performed a procedure, the identified medical practitioner performed the procedure on the owner of the record. Any other information may be similarly personal to an individual owner or subject of a database record. Accordingly, when information in a record is associated with, exclusive to, or in some other way linked to a particular seller, owner, patient, or the like, the information is understood to indicate an action, occurrence, description, person, place, or thing experienced by the particular individual. [00153]The record may include a particular Record ID used to distinguish the record from other records in the database 118. The record may also include private information such as a name, address, and demographic information, such as date of birth and gender. Such personally identifying information may be removed or obfuscated when information from the particular record is formulated in a productized dataset.

[00154]0ther fields in the personal information seller record are associated with one or more particular medical devices. Each medical device may be one of an implanted medical device 103 or an external medical device 105 (FIG. 3), and the associated information may include medical information, such as the type of device, the manufacturer, a model number, a serial number, a location in the body where the device is implanted, a date that medical device was implanted, one or more dates of re operation, any complications of the original implant surgery or re-operation, notes from medical personnel, communication capabilities of the device, some or all of the information retrieved from the medical device, software version information, battery information, a fault or other error information, representative information associated with use of the medical device ( e.g ., number of repetitions, load, stress, and the like), patient-reported information (pain, function, activity, quality of life, sleep, medication usage, emotional and psychological wellbeing, and rehabilitation efforts) associated with the medical device or procedure, and any other information. In some cases, particular fields are accessible and left open so that other information may be added to the field in association with a particular medical device.

[00155] Still other fields in the personal information seller record are associated with personal habits of a record owner, physical traits of a record owner, and still other information. In some cases, a personal information seller record, or a different type of database record associated with the personal information seller record has associated terms of sale for one or more packages or collections of information. For example, in FIG. 7, fields indicate a particular set of prices that an exemplary seller is willing to accept in exchange for access to certain information. In one field, for example (i.e., Price D+F+G), a price is entered that the particular seller is willing to accept for access to date of birth information and information associated with a first medical device. In another field, for example (i.e., Price D+E+L+M), a price is entered that the particular seller is willing to accept for access to date of birth information, gender information, and information associated with a different medical device. In this way, each individual record owner may prospectively set out particular acceptable terms (e.g., price, timing, and the like) for the transfer of an associated set of information.

[00156] FIG. 7 also illustrates another exemplary record associated with a particular buyer. Some or all of the fields in the exemplary record associated with the particular buyer may correspond to fields associated with a record of a particular seller. For example, the buyer record may include a particular Record ID used to distinguish the record from other records in the database 118. The buyer record may also include private information such as an address, a date of birth, and a gender, along with other information regarding one or more particular implantable medical devices, personal habits, physical traits, and other such information. These fields represent characteristics of the type of information that the particular buyer is seeking. The fields are used by the marketplace computing server 110 (FIG. 5) two search the database 118 (FIG. 5).

[00157] In some cases, a buyer record, ora different type of database record associated with the buyer record has associated terms of an offer to purchase productized datasets. For example, in FIG. 7, fields indicate a particular set of prices that an exemplary buyer is offering in order to receive access to certain information. In one field, for example (i.e., Price D+F+G), a price is entered that the particular buyer is offering for access to date of birth information and information associated with a first medical device. In this case, the marketplace computing server 110 is able to easily determine if the exemplary seller and exemplary buyer agree on the terms of a particular sale.

[00158] In correspondence with the devices and information flow operations of FIGS. 5 and 6, it is understood that particular fields of particular records in the database 118 may be dynamically modified as various buyers and sellers negotiate terms for the transfer of information.

[00159] FIGS. 8A and 8B are a flow diagram representing a medical information transaction 400. The medical information transaction is represented as a plurality of modules which include computing hardware and software as represented in other figures and described in other text of the present disclosure. In FIGS. 8A and 8B, the particular transaction is represented as a reverse auction wherein a particular buyer sets up terms for a purchase of medical information. One or more owners or curators of medical information are made aware of the reverse auction, and the one or more owners or curators are permitted to agree to the buyer's terms or counter-offer with a particular set of prospective seller terms.

[00160] Processing in FIG. 8A begins at block 402.

[00161]At block 404 a computer-based marketplace computing server 110 receives and stores a particular request comprising a set of buyer terms for a purchase of productized dataset comprising medical information. In the particular example, the buyer terms for purchase may include a dataset specification including medical information parameters, e.g., a type of medical device a type of medical-device reported information. The dataset specification may also include a size of a pool of prospective sellers and a number of datasets to be purchased. In this way, a buyer may receive assurance that a sufficient quantity of information exists from which to draw a representative sample having a predetermined size. The buyer terms for purchase may also include compensation specification that includes a price for each particular productized dataset, a price for a whole quantity of information, or a price defined according to some other term.

[00162] In some cases, the prospective buyer of the information may set up terms for the reverse auction including when the auction will begin, how long the auction will be open, and when the auction will close. Buyer terms as set forth in the dataset specification may also include demographic parameters to define particular characteristics of prospective sellers of information, geographic parameters to define location details associated with prospective sellers, and other parameters that define characteristics of acceptable medical datasets.

[00163]At block 406 a reverse auction is opened and directed to an identified pool of prospective sellers of medical information having database records that satisfy the dataset specification. To this end, the marketplace computing server 110 transmits information to computing devices llla-d associated with prospective sellers informing the sellers of the auction and relevant terms of the auction. The prospective sellers of medical information may be the individual owners of medical information or curators of a pooled collection of medical information. The reverse auction is administered by the marketplace computing server 110 (FIG. 5) and conducted across a network. The network may be a wide area network (WAN) such as the Internet, a local area network (LAN), or some other network, and the reverse auction may be carried out via one or more web pages of a website. [00164]At block 408, a plurality of terms of sale associated with one or more prospective sellers of medical information are received by the marketplace computing server 110 and evaluated to identify those having acceptable terms of sale. The prospective sellers, or curators of such medical information, may enter such terms as the particular information that will be sold or otherwise transferred, whether and how personally identifying information will be removed or obfuscated, the acceptable uses of their medical information, the acceptable buyers of their information, and when the information will be delivered. The prospective seller terms may also include terms of permissive use for the information such as a time period during which the information may be used, the type of medical study or research that the information may be used in, and other terms of use. The prospective seller terms may also include an acceptable price at which the prospective seller is willing to sell or otherwise transfer and permit use of the medical information.

[00165] In some cases, the reverse auction will close at block 412. In these cases, the auction may close because time has expired. Alternatively, the auction may close because the buyer and seller terms are in agreement. If the auction closes, processing falls to block 414; alternatively, processing advances to block 410.

[00166] At block 410, if the auction remains open, the prospective sellers of medical information may modify their acceptable terms of sale. In many cases, the modification is a reduction in price at which the prospective sellers are willing to accept. For example, if a buyer of medical information is offering to buy certain medical information from 500 individuals at a particular price, and if there are more than 500 prospective sellers of information that matches the parameters of the buyer's dataset specification, then at least some of the prospective sellers may reduce the price they are willing to accept in order to have their information included. Many prospective sellers of information would rather accept a lower price in order to earn some money than hold out for a higher price at the risk of earning no money. Processing at block 410 advances back to processing at block 408 where the marketplace computing server 110 receives and stores the updated set of acceptable seller terms. [00167]At block 414, the information that will be delivered to the buyer is selected from the pool of prospective sellers. Returning to the example of the buyer of medical information offering to buy information from 500 individuals, the reverse auction may draw more than 500 prospective sellers. If there is an available pool of more information than the buyer is offering to buy, then only some of the prospective sellers will have their information sold. The specific records that are selected from which to draw the information that is sold may be chosen based on a lowest acceptable price, the order in which authorizations for the sale are received, the most or least recently collected information, a random selection, or by some other criteria.

[00168] After the information to be sold is selected, the information will be productized and prepared for delivery to the buyer. In some cases, such as when only some of the information desired by the buyer is available or otherwise selected, the reverse auction will remain open and processing will return to block 410. In these cases, prospective sellers may be able to further modify their acceptable terms of sale.

[00169]Alternatively, the reverse auction will close at 416, and processing will pass to block 418. [00170]At block 418, compensation will be distributed to the owner's or seller of the medical information. The compensation is provided to those owners or sellers of the chosen medical information that has been productized into one or more medical information sets and delivered to the buyer.

[00171] Processing in the medical information transaction 400 of FIGS. 8A and 8B ends at block 420. [00172] FIG. 9A is a process flow diagram of a data transaction executed by the marketplace trading system of FIG. 3. The marketplace trading system includes a marketplace computing server 110 and a database 118. The database 118 may co-located with marketplace computing server 110 or it may be located remote from the marketplace computing server. In either case, the database 118 stores information. At least a portion of the information corresponds to medical information obtained from a plurality of medical devices 104 each associated with a respective owner. The database 118 is organized as a plurality of records (see FIG. 7). Each record is associated with a respective owner and has a plurality of fields having personal information therein.

[00173]At operation 502 of the process flow diagram of FIG. 9A, the marketplace computing server 110 receives a request from a buyer computing device 111a. The request comprises a dataset specification and a consideration specification. The dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset. Specified information may also include other types of personal information described earlier herein, including for example, demographic information, habit information, trait information, etc. The consideration specification specifies a compensation to be provided to the respective owner of the information. [00174]At operation 504, the marketplace computing server 110 determines if one or more records in the database 118 satisfy the request. To this end, the marketplace computing server 110 searches the database 118 to find records that contain some or all of the specified information and that satisfy the consideration specification. The marketplace computing server 110 then retrieves information from at least some of the found records. The marketplace computing server 110 repeats the determining until at least the specified quantity of records specified in the request is found.

[00175] At optional operation 506, if the marketplace computing server 110 fails to find the specified quantity of records in the database 118 due to the dataset specification, the server modifies the dataset specification; and repeats the determining based on the modified dataset specification until the specified quantity of records is found. In some embodiments, the marketplace computing server 110 modifies the dataset specification by autonomously changing one or more parameters of the specified information of the dataset specification. In some embodiments, the marketplace computing server 110 modifies the dataset specification by soliciting a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device. In either embodiment, the marketplace computing server 110 presents information on the records found based on the modified dataset specification, to the buyer computing device 111a for review and acceptance by the buyer. Assuming the buyer accepts the search results, the marketplace computing server 110 then receives a notice of acceptance of the records found based on the modified dataset specification from the buyer computing device 111a.

[00176] At optional operation 508, if the marketplace computing server 110 fails to find the specified quantity of records in the database 118 due to the consideration specification, the server solicits a modification of one or more parameters of the consideration specification, from the buyer computing device 111a; and repeats the determining based on the modified consideration specification until the specified quantity of records is found. Parameters of the consideration specification may include a maximum price the buyer is willing to pay, in which case the solicited modification from the marketplace computing server 110 may suggest an increase in maximum price that will result in more database records satisfying the consideration specification of the request. The consideration specification may further include one or more terms of use for the information in the dataset, that may require modification.

[00177]At optional operation 510, if the marketplace computing server 110 locates a record that satisfies some but not all of the parameters of the dataset specification, the server may solicit from a seller computing device 111b, a modification of the record to include additional information that results in the modified record satisfying the dataset specification. To this end, the marketplace computing server 110 informs the seller computing device 111b of the additional information needed in order for the records to completely satisfy dataset specification. Assuming the seller is willing to include the additional information in their record, the marketplace computing server 110 receives a notice of agreeing to the modification and repeats the determining with respect to the modified record.

[00178]At operation 512, once the specified quantity of records are found, the marketplace computing server 110 forms a productized dataset comprising at least some of the retrieved information. As part of forming the productized dataset, the marketplace computing server 110 may remove personally identifiable information from the retrieved information, obfuscate the retrieved information, prepare and/or implement a terms-of use for the retrieved information, and form the retrieved information into one or more computer-readable files.

[00179]At operation 514, the marketplace computing server 110 delivers the productized dataset to the buyer computing device 111a. At operation 516, the marketplace computing server 110 delivers or sends a notification of the delivery to the seller computing device 111b indicating that the compensation has been paid to the seller in accordance with a prearranged financial transaction. [00180] In some embodiments, operation 504 may implement a traditional auction (not shown). For example, if the marketplace computing server 110 identifies a plurality of records that satisfies the dataset specification but not the consideration specification, the identified plurality of records are added to an auction pool. The marketplace computing server 110 then presents auction information to one or more seller computing devices 111b associated with the identified plurality of records. The presented information may describe the discrepancies between the consideration specification and the expected or asking compensation included in the plurality of records in the auction pool. The marketplace computing server 110 may then receive a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification. The marketplace computing server 110 may then repeat the determining with respect to the modified record.

[00181] In some embodiments, operation 504 may implement a reverse auction (not shown). For example, if the marketplace computing server 110 identifies a quantity of found records greater than the specified quantity of records, the server may solicit, from a buyer computing device 111a, a modification of the consideration specification to include a revised compensation less than the original compensation. In other words, the buyer is given the opportunity to lower the price he is willing to pay for the specified information in the dataset specification. The marketplace computing server 110 may then solicit, from one or more seller computing device 111b associated with the found records, a modification of one or more found records to include a new expected or asking compensation that results in the one or more records satisfying the consideration specification.

[00182] FIG. 9B is a process flow diagram of actions executed by a seller computing device 111b of FIG. 3 during a data transaction by a marketplace trading system that includes a marketplace computing server 110 and a database 118. The database 118 may co-located with marketplace computing server 110 or it may be located remote from the marketplace computing server. In either case, the database 118 stores information.

[00183]At operation 602, the seller computing device 111b transmits personal information to the marketplace computing server 110 for storage in the database 118 as a database record. The personal information includes medical information obtained from at least one medical device 104 associated with a seller computing device 111b. In some embodiments, the medical device 104 is configured to sense and store various type of medical information as described earlier herein, and to provide the medical information to the seller computing device 111b. For example, at operation 604, the medical device 104 may be configured to periodically transmit stored medical information to the seller computing device 111b.

[00184] At operation 606, the seller computing device 111b associates terms of sale with the personal information, including in particular the medical information included in the personal information. The terms of sale include, for example, an identification of what personal information is available for purchase and an expected compensation to be received from a buyer in exchange for access to the identified personal information. The terms of sale are transmitted to the marketplace computing server 110 and included in the database record with the personal information.

[00185]At operation 608, the seller computing device 111b communicates with the marketplace computing server 110 to reach an agreement with a perspective buyer (not shown). With reference to FIG. 9A, the perspective buyer has submitted, via a buyer computing device 111a, a request to the marketplace computing server 110 that includes a dataset specification and a consideration specification. The dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device. The consideration specification specifies an expected compensation to be provided to a seller of the specified information.

[00186]At operation 608a, in some embodiments as part of the communication with the marketplace computing server 110, the seller computing device 111b receives, from the marketplace computing server, a solicitation for a modification of the terms of sale of the database record to specify additional medical information for sale that results in the record satisfying the dataset specification. The additional information may include, for example, a type of medical information that is included in the sellers database record, but that is not identified in the terms of sale. Assuming the seller agrees to the modification, the seller computing device 111b transmits to the marketplace computing server 110, a notice of acceptance of the modification to the record.

[00187]At operation 608b, in some embodiments as part of the communication with the marketplace computing server 110, the seller computing device 111b receives from the marketplace computing server, a solicitation for a modification of the database record to change the expected compensation to an amount that results in the terms of sale satisfying the consideration specification. Assuming the seller agrees to the modification, the seller computing device 111b transmits to the marketplace computing server 110, a notice of acceptance of the modification to the record.

C. Example of an Implantable Medical Device

[00188] FIG. 10A is an exploded perspective view of an implantable medical device 103 in the form of an artificial hip joint 180. In many cases, individuals facing osteoarthritis in one or both of their hips are candidates for hip replacement surgery, also called hip arthroplasty. In hip arthroplasty, the acetabulum of the pelvis and femoral head of the upper thighbone are replaced by a medical practitioner with a device such as the artificial hip joint 180 of Figure 10A.

[00189]The artificial hip joint 180 includes an acetabular cup 182, a polyethylene insert 184, a femoral head 186, a neck 188, and a femoral stem 190. The artificial hip joint 180 may include one or more information collection interface modules, e.g., two different modules such as illustrated by modules 154a and 154b. The information collection interface modules may include strain gauges, accelerometers, repetition counters, step counters, motion detectors, position sensors, migration detectors, vibration sensors, temperature sensors, and many other types of detection devices. During the surgical procedure, the femoral head of individual's upper thighbone (i.e., the femur) is removed [e.g., sawed off), and the individual's acetabulum is reamed or otherwise formed into the shape of a half-sphere. The half-sphere formed in the individual's acetabulum is sized to mate perfectly with the outer surface of the acetabular cup 182. In some cases, the acetabular cup 182 is cemented to the bone of the individual; in other cases, the acetabular cup 182 has a porous surface to which the individual's bone will attach during healing. Correspondingly, the femoral stem 190 is pressed into the interior space (marrow cavity) of the individual's femur, which is exposed when the femoral head of the upper thighbone is removed. Like the acetabular cup 182, in some cases, the femoral stem 190 is cemented in place, and in other cases the femoral stem 190 has a porous surface to allow bonding with the bone during healing.

[00190]After the acetabular cup 182 and femoral stem 190 are placed, the medical practitioner will assemble the pieces of the artificial hip joint. As illustrated in FIG. 10A, the neck 188 of the artificial hip is coupled to the femoral head 186, and the femoral head will rotationally fit within in the polyethylene insert 184. The thick muscles of the buttock and thigh provide sufficient pressure and bias to keep femoral head 186 securely located within the hollow partial sphere of the polyethylene insert 184.

[00191] It has been learned that artificial hip surgeries are generally safe and provide tangible benefits to individuals. On the other hand, it has also been learned that not every artificial hip medical procedure is completely successful. For example, just like a real hip, an artificial hip can dislocate if the ball (i.e., femoral head 186) comes out of the socket (i.e., polyethylene insert 184). As other examples, parts of the artificial hip joint 180 or the patient's bone structure can wear out, cement used to secure the acetabular cup 182 or the femoral stem 190 can break down allowing parts to loosen, parts of the artificial joint can be overstressed and break, and other complications can also arise. In order to address these and other complications with conventional artificial hips, technology- enabled artificial joints have been developed.

[00192] FIG. 10B is an implantable medical device 103 in the form of an artificial hip joint. The implantable medical device artificial hip joint embodiment of FIG. 10B may correspond to an implanted medical device 103 of FIG. 3. In addition, it is recognized that the artificial hip joint 180 of FIG. 10A forms the basis of the functional structure 103a of the implanted medical device 103. The functional structure 103a includes the acetabular cup 182, the polyethylene insert 184, the femoral head 186, the neck 188, and the femoral stem 190.

[00193]The functional structure 103a also includes various information collection interface modules. A first information collection interface module 154a includes a strain gauge physically coupled to the surface of the acetabular cup 182. The strain gauge forms one leg of a Wheatstone bridge electronic circuit configuration that includes a power source and a signal detection device V. As the acetabular cup 182 is subject to various physical stress forces, deflection in the strain gauge is represented in the signal detection device V. The amplitude of the detected signal can generally be translated into a measurement of force in one or more directions placed on the acetabular cup 182.

[00194]The functional structure 103a also includes additional information collection interface modules 154b, 154c, and 154d. More or fewer such modules may also be arranged in contact or proximity with the functional structure 103a. The information collection interface modules may include strain gauges, accelerometers, step counters, repetition counters, motion detectors, position sensors, vibration sensors, temperature sensors, migration detectors, and many other types of detection devices. The information collection interface modules may be based on micro- electromechanical systems (MEMS), electronic devices, mechanical devices, electromechanical devices, or other types of sensing technologies.

[00195]With respect to the artificial hip embodiment, one or more information collection interface modules 154a-154d may be used to generate or otherwise collect information associated with the operation of the artificial hip, and the operations to generate or otherwise collect the information may be autonomous or facilitated via a processing unit 114a. The information associated with the information collection interface modules may be stored in memory 116a.

[00196]As described in the present disclosure, information collected by the medical device 104 may be communicated via a network 106 or interface 108 to a marketplace computing server 110. The information may further be stored as described herein in one or more database records or fields and formed into one or more productized data sets.

[00197] FIG. IOC shows an implanted medical device 103 corresponding to artificial hip joint embodiment. In addition, it is recognized that the artificial hip joint 180 of FIG. 10A forms the basis of the functional structure 103a of the medical device 104. The functional structure 103a includes the acetabular cup 182, the polyethylene insert 184 (not shown), the femoral head 186, the neck 188, and the femoral stem 190. The functional structure 103a also includes one or more information collection interface modules, e.g., the module referred to as T2. Within this embodiment T2 may comprise a variety of sensors (e.g., strain gauges, accelerometers, gyroscopes, repetition counters, step counters, motion detectors, position sensors, vibration sensors, migration detectors, temperature sensors, and many other types of detection devices. Within preferred aspects of this embodiment, the sensor module T2, is placed as shown in the tibial extension of the artificial hip implant. The implantable sensor module can have a battery to power the unit, as well as other components which are helpful and/or necessary to transfer collected information to outside of the body (e.g., various controllers as provided herein, a suitable antennae, and the like).

D. General Considerations

[00198]The computer-based marketplace for medical information system discussed herein may be configured as a plurality of modules. As used herein, the term "module" refers to an electronic circuit, a processor [e.g., distributed, shared, dedicated, group, single core, multicore, or the like) and memory operative to execute one or more software or firmware programs, an application specific integrated circuit (ASIC), a combinational-logic circuit, or some other individual or cooperative coupling of suitable components (either hardware or software) that provide the functionality described with respect to the module.

[00199]As further described herein, a module may include software instructions that are executed by a computing server or a personal computing device. A computing server and a personal computing device includes operative hardware found in conventional computing apparatuses such as one or more central processing units (CPUs), volatile and nonvolatile memory, serial and parallel input/output (I/O) circuitry compliant with various standards and protocols, wired and/or wireless networking circuitry [e.g., a communications transceiver). [00200]As known by one skilled in the art, computing servers and personal computing devices have one or more memories, each memory comprising any combination of volatile and nonvolatile computer-readable media for reading and writing. Volatile computer-readable media include, for example, random access memory (RAM). Nonvolatile computer-readable media include, for example, read-only memory (ROM), magnetic media such as a hard disk, an optical disk drive, a flash memory device, a CD-ROM, and in addition or in the alternative, other information storage devices. In some cases, a particular memory is separated virtually or physically into separate areas, such as a first memory, a second memory, a third memory, etc. In these cases, it is understood that the different divisions of memory may be in different devices or embodied in a single memory.

[00201]Computing servers and personal computing devices further include operative software found in conventional computing devices such as an operating system, software drivers to direct operations through the I/O circuitry, networking circuitry, and other peripheral component circuitry. In addition, computing servers and personal computing devices include operative application software such as network software for communicating with other computing devices, database software for building and maintaining databases, and task-management software for distributing the communication and operational workload amongst various CPUs. In some cases, a computing device is a single hardware machine having the hardware and software described herein, and in other cases, a computing device is a networked collection of hardware and software machines working together ( e.g ., in a server farm) to execute the functions of the computer-based marketplace for medical information system. [00202]The following are some exemplary numbered embodiments of the present disclosure:

3. The system of embodiments 1 or 2, wherein the processor is further configured to, in response to a failure to find the specified quantity of records: modify the dataset specification; and repeat the determining based on the modified dataset specification until the specified quantity of records is found.

7. The system of any one of embodiments 1-6, e.g., embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a failure to find the specified quantity of records: solicit a modification of one or more parameters of the consideration specification; and repeat the determining based on the modified consideration specification until the specified quantity of records is found.

8. The system of any one of embodiments 1-7, e.g., embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

9. The system of any one of embodiments 1-8, e.g., embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to: identify a plurality of records that satisfies the dataset specification but not the consideration specification; and add the identified plurality of records to an auction pool. 10. The system of embodiment 9, wherein the processor is further configured to: present, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

12. The system of any one of embodiments 1-11, e.g., embodiment 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a quantity of found records being greater than the specified quantity of records: solicit, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and solicit, from one or more seller computing device associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification.

13. The system of any one of embodiments 1-12, e.g., embodiment 1, wherein the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

14. The system of any one of embodiments 1-13, e.g., embodiment 1, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

15. The system of embodiment 14, wherein the one or more types of medical information comprises a measure of at least one of flexure, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

16. The system of embodiments 14 or 15, e.g., embodiment 15, wherein the sensor comprises at least one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

17. The system of any one of embodiments 1-16, e.g., embodiment 1, wherein the processor forms a productized dataset comprising at least some of the retrieved information by being further configured to one or more of remove personally identifiable information from the retrieved information, obfuscate the retrieved information, prepare and/or implement a terms-of use for the retrieved information, and form the retrieved information into one or more computer- readable files.

20. The method of embodiments 18 or 19, e.g., embodiment 19, further comprising, responsive to a failure to find the specified quantity of records: modifying the dataset specification; and repeating the determining based on the modified dataset specification until the specified quantity of records is found.

21. The method of embodiment 20, wherein modifying the dataset specification comprises autonomously changing one or more parameters of the specified information of the dataset specification.

22. The method of embodiment 20, wherein modifying the dataset specification comprises: soliciting a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device.

23. The method of any one of embodiments 18-22, e.g., embodiment 20, further comprising: presenting information on the records found based on the modified dataset specification; and receiving a notice of acceptance of the records found based on the modified dataset specification.

24. The method of any one of embodiments 18-23, e.g., embodiment 18, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of one or more parameters of the consideration specification; and repeating the determining based on the modified consideration specification until the specified quantity of records is found.

25. The method of any one of embodiments 18-23, e.g., embodiment 18, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the dataset specification: soliciting from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeating the determining with respect to the modified record.

26. The method of any one of embodiments 18-23, e.g., embodiment 18, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the dataset specification but not the consideration specification; and adding the identified plurality of records to an auction pool.

27. The method of any one of embodiments 18-26, e.g., embodiment 26, further comprising: presenting, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

28. The method of any one of embodiments 18-26, e.g., embodiment 26, further comprising, for one or more of the plurality of records in the auction pool: receiving a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification; and repeating the determining with respect to the modified record.

29. The method of any one of embodiments 18-26, e.g., embodiment 26, wherein determining if one or more records satisfy the request further comprises, in response to a quantity of found records being greater than the specified quantity of records: soliciting, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and soliciting, from one or more seller computing devices associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification. 30. The method of any one of embodiments 18-29, e.g., embodiment 18, wherein the type of medical device specified in the request comprises one or more of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

31. The method of any one of embodiments 18-29, e.g., embodiment 18, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

32. The method of embodiment 31, wherein the one or more types of medical information comprises at least one of a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

33. The method of any one of embodiments 18-32, e.g., embodiment 18, wherein the consideration specification further comprises one or more terms of use for the information in the dataset.

34. The method of any one of embodiments 18-33, e.g., embodiment 18, wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

41. The marketplace computing server of any one of embodiments 36-40, e.g., embodiment 38, wherein the processor is further configured to: present information on the records found based on the modified dataset specification; and receive a notice of acceptance of the records found based on the modified dataset specification.

42. The marketplace computing server of any one of embodiments 36-41, e.g., embodiment 36, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit, a modification of the record to include new information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

43. The marketplace computing server of any one of embodiments 36-42, e.g., embodiment 36, wherein the database includes personal information comprising medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith.

44. The marketplace computing server of embodiment 43 wherein: the type of medical device specified in the request comprises at least one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment; and the medical information obtained from a plurality of medical devices comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

49. The buyer computing device of embodiments 47 or 48, e.g., embodiment 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the dataset specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified dataset specification comprising at least one of the one or more alternative parameters.

51. The buyer computing device of any one of embodiments 47-50, e.g., embodiment 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the consideration specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified consideration specification comprising at least one of the one or more alternative parameters.

56. The seller computing device of embodiments 54 or 55, e.g., embodiment 54, wherein the processor communicates with the marketplace computing server by being further configured to: receive, from the marketplace computing server, a solicitation for a modification of the database record to change the expected compensation to an amount that results in the terms of sale satisfying the consideration specification; and transmit, to the marketplace computing server, a notice of acceptance of the modification to the record.

57. The seller computing device of any one of embodiments 54-56, e.g., embodiment 54, wherein the at least one medical device comprises at least one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

58. The seller computing device of any one of embodiments 54-57, e.g., embodiment 54, wherein the medical information obtained from the at least one medical device comprises measure of at least one of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

60. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a seller computing device to: transmit personal information to a marketplace computing server for storage in a database record, the personal information comprising medical information obtained from at least one medical device associated with a seller; associate terms of sale with the personal information comprising an expected compensation; and communicate with the marketplace computing server to reach an agreement with a perspective buyer, wherein the perspective buyer has submitted a request to the marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification includes specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and b) the consideration specification specifies a compensation to be provided to a seller of the specified information.

61. A non-transitory computer-readable medium whose stored contents configure a computing system to perform a method, the method comprising: a) maintaining at least one database having information stored therein, at least a portion of the information obtained from a plurality of implanted medical devices each implanted in a respective owner, the plurality of implanted medical devices each comprising a sensor configured to detect or measure one or more operational properties of the implanted medical device and to generate information corresponding to the one or more operational properties, said database being organized as a plurality of records, each record associated with a respective owner and having a plurality of fields each having information associated therewith; b) receiving a request comprising: i) a specification for a dataset identifying one or more fields, specified information associated with the one or more identified fields, and a specified quantity of records to be included in the dataset, wherein the specified information comprises a type of implanted medical device, and at least one of the one or more operational properties of the type of implanted medical device, and ii) a specification for consideration specifying a compensation to be provided to the respective owner of the information; c) determining if one or more records satisfy the request by: i) searching said database to find records that contain some or all of the specified information and that satisfy the specification for consideration; and ii) retrieving information from at least some of the found records; and d) forming a productized dataset comprising at least some of the retrieved information.

63. The non-transitory computer-readable medium of embodiments 61 or 62, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

64. The non-transitory computer-readable medium of any one of embodiments 61-63, e.g., embodiment 63, whose stored contents configure the computing system to perform the method, the method further comprising: presenting information on the records found based on the modified specification for a dataset; and receiving a notice of acceptance of the records found based on the modified specification for a dataset.

65. The non-transitory computer-readable medium of any one of embodiments 61-64, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

66. The non-transitory computer-readable medium of any one of embodiments 61-65, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

67. The non-transitory computer-readable medium of any one of embodiments 61-66, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

68. The non-transitory computer-readable medium of any one of embodiments 61-67, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

71. The non-transitory computer-readable medium of any one of embodiments 61-70, e.g., embodiment 62, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration.

72. The non-transitory computer-readable medium of any one of embodiments 61-71, e.g., embodiment 61, wherein the type of implantable medical device specified in the request comprises an orthopedic implant and the one or more operational properties of the orthopedic implant comprises one or more measures of flexures, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, and migration.

73. The non-transitory computer-readable medium of any one of embodiments 61-72, e.g., embodiment 72, wherein the orthopedic implant comprises at least one of a hip prosthesis, a knee prosthesis, and a shoulder prosthesis.

74. The non-transitory computer-readable medium of any one of embodiments 61-73, e.g., embodiment 61, wherein the sensor comprises at least one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor and temperature sensor.

75. The non-transitory computer-readable medium of any one of embodiments 61-74, e.g., embodiment 61, wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

76. The non-transitory computer-readable medium of any one of embodiments 61-75, e.g., embodiment 61, wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

81. The non-transitory computer-readable medium of embodiments 79 or 80, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

83. The non-transitory computer-readable medium of any one of embodiments 79-82, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

84. The non-transitory computer-readable medium of any one embodiments 79-83, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

85. The non-transitory computer-readable medium of any one of embodiments 79-84, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

86. The non-transitory computer-readable medium of any one of embodiments 79-85, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

89. The non-transitory computer-readable medium of any one of embodiments 79-88, e.g., embodiment 80, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration.

90. The non-transitory computer-readable medium of any one of embodiments 79-89, e.g., embodiment 79, wherein the type of wearable device specified in the request comprises one or more of an external medical device, a garment, an accessory, and a piece of sports

91. The non-transitory computer-readable medium of any one of embodiments 79-90, e.g., embodiment 79, wherein the one or more operational properties of the wearable device comprises one or more measures of the sensor.

92. The non-transitory computer-readable medium of any one of embodiments 79-91, e.g., embodiment 91, wherein the one or more measures of the sensor comprise at least one of a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

93. The non-transitory computer-readable medium of any one of embodiments 79-92, e.g., embodiment 79, wherein the sensor comprises at least one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

94. The non-transitory computer-readable medium of any one of embodiments 79-93, e.g., embodiment 79, wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

95. The non-transitory computer-readable medium of any one of embodiments 79-94, e.g., embodiment 79, wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

[00203] In the foregoing description, certain specific details are set forth to provide a thorough understanding of various disclosed embodiments. However, one skilled in the relevant art will recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with electronic and computing systems including client and server computing systems, as well as networks have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.

[00204] Unless the context requires otherwise, throughout the specification and claims that follow, the word "comprise" and variations thereof, such as, "comprises" and "comprising" are to be construed in an open, inclusive sense, e.g., "including, but not limited to."

[00205] Reference throughout this specification to "one embodiment" or "an embodiment" and variations thereof means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Reference to "any one of embodiments" x-y refers to any one or more of the referenced x-y embodiments, e.g., one, or two, or three, or more than three of the listed embodiments x-y, which may be combined to provide an embodiment of the present disclosure.

[00206]As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the content and context clearly dictates otherwise. It should also be noted that the conjunctive terms, "and" and "or" are generally employed in the broadest sense to include "and/or" unless the content and context clearly dictates inclusivity or exclusivity as the case may be. In addition, the composition of "and" and "or" when recited herein as "and/or" is intended to encompass an embodiment that includes all of the associated items or ideas and one or more other alternative embodiments that include fewer than all of the associated items or ideas.

[00207]The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.

[00208]The various embodiments described herein can be combined to provide further embodiments. Aspects of the embodiments can be modified, if necessary, to employ concepts of the various patents, application, and publications to provide yet further embodiments. These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.

Claims

CLAIMS What Is Claimed Is:

2. The system of claim 1, wherein the processor is further configured to repeat the determining until at least the specified quantity of records is found.

3. The system of claim 1, wherein the processor is further configured to, in response to a failure to find the specified quantity of records: modify the dataset specification; and repeat the determining based on the modified dataset specification until the specified quantity of records is found.

4. The system of claim 3, wherein the processor modifies the dataset specification by being configured to autonomously change one or more parameters of the specified information of the dataset specification.

5. The system of claim 3, wherein the processor modifies the dataset specification by being configured to: solicit a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device.

6. The system of claim 3, wherein the processor is further configured to: present information on the records found based on the modified dataset specification; and receive a notice of acceptance of the records found based on the modified dataset specification.

7. The system of claim 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a failure to find the specified quantity of records: solicit a modification of one or more parameters of the consideration specification; and repeat the determining based on the modified consideration specification until the specified quantity of records is found.

8. The system of claim 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

9. The system of claim 1, wherein the processor determines if one or more records satisfy the request by being further configured to: identify a plurality of records that satisfies the dataset specification but not the consideration specification; and add the identified plurality of records to an auction pool.

10. The system of claim 9, wherein the processor is further configured to: present, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

11. The system of claim 9, wherein the processor is further configured to, for one or more of the plurality of records in the auction pool: receive a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification; and repeat the determining with respect to the modified record.

12. The system of claim 1, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a quantity of found records being greater than the specified quantity of records: solicit, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and solicit, from one or more seller computing device associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification.

13. The system of claim 1 wherein the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

14. The system of claim 1, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

15. The system of claim 14, wherein the one or more types of medical information comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

16. The system of claim 15 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

17. The system of claim 1 wherein the processor forms a productized dataset comprising at least some of the retrieved information by being further configured to one or more of remove personally identifiable information from the retrieved information, obfuscate the retrieved information, prepare and/or implement a terms-of use for the retrieved information, and form the retrieved information into one or more computer-readable files.

19. The method of claim 18, further comprising repeating the determining until at least the specified quantity of records is found.

20. The method of claim 19, further comprising, responsive to a failure to find the specified quantity of records: modifying the dataset specification; and repeating the determining based on the modified dataset specification until the specified quantity of records is found.

21. The method of claim 20, wherein modifying the dataset specification comprises autonomously changing one or more parameters of the specified information of the dataset specification.

22. The method of claim 20, wherein modifying the dataset specification comprises: soliciting a modification of one or more parameters of the specified information of the dataset specification from the buyer computing device.

23. The method of claim 20 further comprising: presenting information on the records found based on the modified dataset specification; and receiving a notice of acceptance of the records found based on the modified dataset specification.

24. The method of claim 18, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of one or more parameters of the consideration specification; and repeating the determining based on the modified consideration specification until the specified quantity of records is found.

25. The method of claim 18, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the dataset specification: soliciting from a seller computing device, a modification of the record to include additional information that results in the modified record satisfying the dataset specification; and repeating the determining with respect to the modified record.

26. The method of claim 18, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the dataset specification but not the consideration specification; and adding the identified plurality of records to an auction pool.

27. The method of claim 26, further comprising: presenting, to one or more seller computing devices, information on discrepancies between the consideration specification and the compensation included in the plurality of records in the auction pool.

28. The method of claim 26, further comprising, for one or more of the plurality of records in the auction pool: receiving a modification of the record to include a new compensation that results in the modified record satisfying the consideration specification; and repeating the determining with respect to the modified record.

29. The method of claim 18, wherein determining if one or more records satisfy the request further comprises, in response to a quantity of found records being greater than the specified quantity of records: soliciting, from the buyer computing device, a modification of the consideration specification to include a revised compensation less than the original compensation; and soliciting, from one or more seller computing devices associated with the found records, a modification of one or more found records to include a new compensation that results in the one or more records satisfying the consideration specification.

30. The method of claim 18 wherein the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

31. The method of claim 18, wherein each of the plurality of medical devices comprises at least one sensor configured to generate one or more types of medical information.

32. The method of claim 31, wherein the one or more types of medical information comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

33. The method of claim 18 wherein the consideration specification further comprises one or more terms of use for the information in the dataset.

34. The method of claim 18 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

37. The marketplace computing server of claim 36, wherein the processor is further configured to repeat the determining until at least the specified quantity of records is found.

38. The marketplace computing server of claim 36, wherein the processor is further configured to, in response to a failure to find the specified quantity of records: modify the dataset specification; and repeat the determining based on the modified dataset specification until the specified quantity of records is found.

39. The marketplace computing server of claim 38, wherein the processor modifies the dataset specification by being configured to autonomously change one or more parameters of the specified information of the dataset specification.

40. The marketplace computing server of claim 38, wherein the processor modifies the dataset specification by being configured to: solicit a modification of one or more parameters of the specified information of the dataset specification.

41. The marketplace computing server of claim 38, wherein the processor is further configured to: present information on the records found based on the modified dataset specification; and receive a notice of acceptance of the records found based on the modified dataset specification.

42. The marketplace computing server of claim 36, wherein the processor determines if one or more records satisfy the request by being further configured to, in response to a record failing to satisfy the dataset specification: solicit, a modification of the record to include new information that results in the modified record satisfying the dataset specification; and repeat the determining with respect to the modified record.

43. The marketplace computing server of claim 36, wherein the database includes personal information comprising medical information obtained from a plurality of medical devices each associated with a respective owner, the database organized as a plurality of records, each record associated with a respective owner and having a plurality of fields having personal information associated therewith.

44. The marketplace computing server of claim 43 wherein: the type of medical device specified in the request comprises one of an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment; and the medical information obtained from a plurality of medical devices comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

48. The buyer computing device of claim 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information on records found based on the dataset specification; and transmit a notice of acceptance of the records found based on the dataset specification.

49. The buyer computing device of claim 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the dataset specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified dataset specification comprising at least one of the one or more alternative parameters.

50. The buyer computing device of claim 49, wherein the processor is further configured to: receive information on the records found based on the modified dataset specification; and transmit a notice of acceptance of the records found based on the modified dataset specification.

51. The buyer computing device of claim 47, wherein the processor communicates with the marketplace computing server by being further configured to: receive information from the marketplace computing server on one or more alternative parameters for the consideration specification that result in the specified quantity of records being found; and transmit a notice to the marketplace computing server of acceptance of a modified consideration specification comprising at least one of the one or more alternative parameters.

52. A method comprising: transmitting a request to a marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification comprises a plurality of parameters including specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to a respective owner of the specified information; communicating with the marketplace computing server to reach an agreement; and receiving a productized dataset comprising at least some of the specified information found in records stored in a database.

53. A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a buyer computing device to: transmit a request to a marketplace computing server, the request comprising a dataset specification and a consideration specification, wherein: a) the dataset specification comprises a plurality of parameters including specified information comprising a type of medical device and a type of medical information obtainable from the type of medical device, and a specified quantity of records to be included in a dataset, and b) the consideration specification specifies a compensation to be provided to a respective owner of the specified information; communicate with the marketplace computing server to reach an agreement; and receive a productized dataset comprising at least some of the specified information found in records stored in a database.

55. The seller computing device of claim 54, wherein the processor communicates with the marketplace computing server by being further configured to: receive, from the marketplace computing server, a solicitation for a modification of the database record to specify additional information for sale that results in the record satisfying the dataset specification; and transmit, to the marketplace computing server, a notice of acceptance of the modification to the record.

56. The seller computing device of claim 54, wherein the processor communicates with the marketplace computing server by being further configured to: receive, from the marketplace computing server, a solicitation for a modification of the database record to change the expected compensation to an amount that results in the terms of sale satisfying the consideration specification; and transmit, to the marketplace computing server, a notice of acceptance of the modification to the record.

57. The seller computing device of claim 54, wherein the at least one medical device comprises an implanted medical device, an external medical device, a garment, an accessory, and a piece of sports equipment.

58. The seller computing device of claim 54, wherein the medical information obtained from the at least one medical device comprises a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

62. The non-transitory computer-readable medium of claim 61 whose stored contents configure the computing system to perform the method, the method further comprising repeating the determining until at least the specified quantity of records is found.

63. The non-transitory computer-readable medium of claim 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

64. The non-transitory computer-readable medium of claim 63 whose stored contents configure the computing system to perform the method, the method further comprising: presenting information on the records found based on the modified specification for a dataset; and receiving a notice of acceptance of the records found based on the modified specification for a dataset.

65. The non-transitory computer-readable medium of claim 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

66. The non-transitory computer-readable medium of claim 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

67. The non-transitory computer-readable medium of claim 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

68. The non-transitory computer-readable medium of claim 62 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

69. The non-transitory computer-readable medium of claim 68 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: presenting information on discrepancies between the specification for consideration and the compensation included in the plurality of records in the auction pool.

70. The non-transitory computer-readable medium of claim 68 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: receiving a modification of one or more of the plurality of records in the auction pool to include a new compensation that results in the one or more records satisfying the specification for consideration.

71. The non-transitory computer-readable medium of claim 62, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration.

72. The non-transitory computer-readable medium of claim 61 wherein the type of implantable medical device specified in the request comprises an orthopedic implant and the one or more operational properties of the orthopedic implant comprises one or more measures of flexures, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, and migration.

73. The non-transitory computer-readable medium of claim 72 wherein the orthopedic implant comprises one of a hip prosthesis, a knee prosthesis, and a shoulder prosthesis.

74. The non-transitory computer-readable medium of claim 61 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor and temperature sensor.

75. The non-transitory computer-readable medium of claim 61 wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

76. The non-transitory computer-readable medium of claim 61 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.

80. The non-transitory computer-readable medium of claim 79 whose stored contents configure the computing system to perform the method, the method further comprising repeating the determining until at least the specified quantity of records is found.

81. The non-transitory computer-readable medium of claim 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: modifying the specification for a dataset; and repeating the determining until the specified quantity of records is found.

82. The non-transitory computer-readable medium of claim 81 whose stored contents configure the computing system to perform the method, the method further comprising: presenting information on the records found based on the modified specification for a dataset; and receiving a notice of acceptance of the records found based on the modified specification for a dataset.

83. The non-transitory computer-readable medium of claim 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for a dataset; and repeating the determining based on the modified specification for a dataset until the specified quantity of records is found.

84. The non-transitory computer-readable medium of claim 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a failure to find the specified quantity of records: soliciting a modification of the specification for consideration; and repeating the determining based on the modified specification for consideration until the specified quantity of records is found.

85. The non-transitory computer-readable medium of claim 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises, responsive to a record that does not satisfy the specification for a dataset: soliciting a modification of the record to include new information that results in the record satisfying the specification for a dataset; receiving the modification of the record; and repeating the determining with respect to the modified record.

86. The non-transitory computer-readable medium of claim 80 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: identifying a plurality of records that satisfies the specification for a dataset but not the specification for consideration; and adding the plurality of records to an auction pool.

87. The non-transitory computer-readable medium of claim 86 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: presenting information on discrepancies between the specification for consideration and the compensation included in the plurality of records in the auction pool.

88. The non-transitory computer-readable medium of claim 86 whose stored contents configure the computing system to perform the method, wherein determining if one or more records satisfy the request further comprises: receiving a modification of one or more of the plurality of records in the auction pool to include a new compensation that results in the one or more records satisfying the specification for consideration.

89. The non-transitory computer-readable medium of claim 80, whose stored contents configure the computing system to perform the method, wherein responsive to the quantity of found records being greater than the specified quantity of records, the method further comprising: soliciting a modification of one or more found records to include a new compensation less than the original compensation that results in the one or more records satisfying a revised specification for consideration.

90. The non-transitory computer-readable medium of claim 79 wherein the type of wearable device specified in the request comprises one of an external medical device, a garment, an accessory, and a piece of sports equipment.

91. The non-transitory computer-readable medium of claim 79, wherein the one or more operational properties of the wearable device comprises one or more measures of the sensor.

92. The non-transitory computer-readable medium of claim 91, wherein the one or more measures of the sensor comprise a measure of flexures, pressure, force, load, stress, steps, repetitive movements, motion, position, vibration, temperature, migration, heart rate, blood pressure, temperature, and glucose level.

93. The non-transitory computer-readable medium of claim 79 wherein the sensor comprises one of a fluid pressure sensor, fluid volume sensor, contact sensor, position sensor, pulse pressure sensor, blood volume sensor, blood flow sensor, chemistry sensor, metabolic sensor, accelerometer, mechanical stress sensor, temperature sensor, mechanical pressure sensor, gyroscope, strain gauges, auditory sensor, optical system and/or sensor, and time sensor.

94. The non-transitory computer-readable medium of claim 79 wherein the specification for consideration further comprises one or more terms of use for the information in the dataset.

95. The non-transitory computer-readable medium of claim 79 wherein forming a productized dataset comprising at least some of the retrieved information comprises one or more of removing personally identifiable information from the retrieved information, obfuscating the retrieved information, preparing and/or implementing a terms-of use for the retrieved information, and forming the retrieved information into one or more computer-readable files.