Collaborative computing and electronic records

• US 10,231,141 B2
• Filed: 09/01/2017
• Issued: 03/12/2019
• Est. Priority Date: 11/05/2010
• Status: Active Grant

• Current Assignee: Mark Cummings
• Original Assignee: Mark Cummings
• Inventors: Cummings, Mark
• Primary Examiner(s): Harris, Christopher C
• Application Number:
  US15/694,072
• Publication Number:
  US 20180077588A1
• Time in Patent Office: 557 Days
• CPC Class Codes: G06F 30/327 Logic synthesis; Behaviour synthesis, e.g. mapping logic, HDL to netlist, high-level language to RTL or netlist
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

Collaborative computing and electronic records are disclosed. An entity that may be able to help achieve an objective is discovered and a connection to the entity established. A meta-language is used to exchange with the entity a description of the objective and a description of the entity. The meta-language is used to negotiate with the entity a contract to help achieve the objective. In the event a contract to help achieve the objective is reached, performing a self-configuration in accordance with the contract.

Claims

1. A method, comprising:

storing in a data store for each of a plurality of entities an entity image data comprising metadata about an entity of the plurality of entities, wherein the data store is configured to create and support an organically changing schema, and provides a mechanism to propagate changes to the schema or data stored in the data store;

discovering, using a processor of a first entity, a second entity to help achieve an objective, wherein the second entity is a cloud-based entity;

connecting to a processor of the second entity via a communication interface device;

using a meta-language to exchange with the processor of the second entity via the communication interface a description of the objective to aggregate data from the second entity and description information associated with the second entity, wherein the descriptive information includes an identification of a proprietary data access interface associated with the second entity, wherein the proprietary data access interface associated with the second entity is different than a proprietary data access interface associated with the first entity, wherein a bridge separate from the processor of the first entity and the processor of the second entity is configured to receive the meta-language exchanged with the processor of the second entity and to use an internal standard meta-language to enable the processor of the second entity with the proprietary data access interface to understand the description of the objective;

negotiating with the processor of the second entity using the meta-language, including by exchanging one or more proposals with the processor of the second entity via the communication interface to form a contract, the contract indicates how the data will be aggregated from the second entity; and

in the event the contract to help achieve the objective is reached, performing a self-configuration in accordance with the contract.

2. The method of claim 1, further comprising initiating an operation in accordance with the contract.

3. The method of claim 2, further comprising maintaining the operation in accordance with the contract.

4. The method of claim 3, further comprising discontinuing the operation in accordance with the contract.

5. The method of claim 1, wherein the second entity comprises one or more of the following:

a cloud service, a cloud task, a cloud, and a cloud computing device associated with an end user.

6. The method of claim 1, further comprising negotiating with a third entity a contract to replace the second entity in helping to achieve the objective.

7. The method of claim 6, wherein the second entity maintains, after termination of an operation associated with helping to achieve the objective, a vestige of a configuration used to help achieve the objective.

8. The method of claim 7, wherein the second entity uses the vestige, if needed, to resume helping to achieve the objective.

9. The method of claim 1, wherein the first entity comprises one or more of the following:

an electronic record, an electronic patient record, an electronic record system, and an electronic record device associated with an end user.

10. The method of claim 1, wherein aggregating data comprises aggregating from a plurality of electronic records stores a plurality of records associated with an individual patient.

11. The method of claim 1, wherein aggregating data comprises aggregating from a plurality of electronic records stores a plurality of records associated with a class of patients.

12. The method of claim 11, further comprising anonymizing the records to protect the identity of individual patients in the class.

13. The method of claim 1, wherein the contract includes at least one of the following parameters to be used in the aggregation of data:

configurations, settings, and data formats and structures.

14. A system, comprising:

a communication interface device; and

a processor of a first entity configured to;

store in a data store for each of a plurality of entities an entity image data comprising metadata about an entity of the plurality of entities, wherein the data store is configured to create and support an organically changing schema, and provides a mechanism to propagate changes to the schema or data stored in the data store;

discover a second entity to help achieve an objective, wherein the second entity is a cloud-based entity;

connect to a processor of the second entity via the communication interface device;

use a meta-language to exchange with the second processor of the second entity via the communication interface a description of the objective to aggregate data from the second entity and descriptive information associated with the second entity, wherein the descriptive information includes an identification of a proprietary data access interface associated with the second entity, wherein the proprietary data access interface associated with the second entity is different than a proprietary data access interface associated with the first entity, wherein a bridge separate from the processor of the first entity and the processor of the second entity is configured to receive the meta-language exchanged with the processor of the second entity and to use an internal standard meta-language to enable the processor of the second entity with the proprietary data access interface to understand the description of the objective;

negotiate with the second entity using the meta-language, including by exchanging one or more proposals with the processor of the entity via the communication interface to form a contract, the contract indicates how the data will be aggregated from the second entity; and

in the event the contract is formed, perform a self-configuration in accordance with the contract; and

a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions.

15. The system of claim 14, wherein the second entity comprises one or more of the following:

a cloud service, a cloud task, a cloud, and a cloud computing device associated with an end user.

16. The system of claim 14, wherein the processor is further configured to negotiate with a third entity a contract to replace the second entity in helping to achieve the objective.

17. The system of claim 14, wherein the second entity maintains, after termination of an operation associated with helping to achieve the objective, a ghost or other vestige of a configuration used to help achieve the objective.

18. The system of claim 14, wherein the second entity comprises one or more of the following:

an electronic record, an electronic patient record, an electronic record system, and an electronic record device associated with an end user.

19. A computer program product embodied on a tangible, non-transitory computer readable storage medium and comprising computer instructions for:

storing in a data store for each of a plurality of entities an entity image data comprising metadata about an entity of the plurality of entities, wherein the data store is configured to create and support an organically changing schema, and provides a mechanism to propagate changes to the schema or data stored in the data store;

discovering a second entity to help a first entity achieve an objective, wherein the second entity is a cloud-based entity;

connecting to a processor of the second entity;

using a meta-language to exchange with the processor of the second entity via the communication interface a description of the objective to aggregate data from the second entity and descriptive information associated with the second entity, wherein the descriptive information includes an identification of a proprietary data access interface associated with the second entity, wherein the proprietary data access interface associated with the second entity is different than a proprietary data access interface associated with the first entity, wherein a bridge separate from the processor of the first entity and the processor of the second entity is configured to receive the meta-language exchanged with the processor of the second entity and to use an internal standard meta-language to enable the second entity with the proprietary data access interface to understand the description of the objective; and

negotiating with the processor of the second entity using the meta-language, including by exchanging one or more proposals with the processor of the second entity via the communication interface to form a contract, the contract indicates how the data will be aggregated from the second entity;

in the event the contract is formed, performing a self-configuration in accordance with the contract.

20. The computer program product of claim 19, further comprising computer instructions for initiating an operation in accordance with the contract.