IP Library › Granted Patent US 12,360,832
Granted Patent B2
US 12,360,832 · App. 18/804,618 · Granted Jul 15, 2025

Entity relationships and versioning

Inventors: Kenton Lamar Smeltzer (Summerland Key, FL); Michael Angel Cruz (Stock Island, FL); William Tomer (Bainbridge Island, WA); Chad Garrett Waldman (Kirkland, WA); Clare Rene Mason (Seattle, WA)
Assignee: DexCare, Inc.
G06F9/546G06F16/212G06F16/288
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,360,832
App. No.
18/804,618
Granted
Jul 15, 2025
Kind
B2
Abstract

Embodiments are directed to managing data. An application may request to instantiate an entity. A schema for the entity may be determined based on an entity version. Foreign properties of the entity may be determined based on the schema. Relationships between the entity and foreign entities may be determined based on an entity relationship table such that each relationship may associate foreign entity identifiers with the foreign properties. A native object for a native environment of the application may be generated based on the schema, the entity and the foreign entities such that the native object may include members that may correspond to the foreign entities. Data associated with the entity and the foreign entities may be provided to the application based on the native object. Changes to the data by other applications may be employed to update the native object to include the changed data.

Claims (109)

1. A method for managing data in a computing environment using one or more processors to execute instructions that are configured to cause actions, comprising:

providing a request from an application to instantiate an entity, wherein the request includes an entity version;

determining a schema that corresponds to the entity based on the entity version;

determining one or more foreign properties of the entity based on a traversal of the schema, wherein each foreign property includes a foreign entity type and a foreign entity version;

determining one or more relationships between the entity and one or more foreign entities based on an entity relationship table that is separate from the schema, wherein each relationship associates one or more foreign entity identifiers with the one or more foreign properties;

generating a native object for a native environment of the application based on the schema, the entity and the one or more foreign entities, wherein the native object includes one or more members that correspond to the one or more foreign entities;

providing data associated with the entity and the one or more foreign entities to the application based on the native object;

employing changes to the data by one or more other applications to update the native object to include the changed data;

in response to the application modifying the data of the native object, performing additional further actions:

updating the entity and the one or more foreign entities based on the modified data; and

generating a message that includes the modified data, wherein the message is provided to a message queue; and

employing the message queue to provide the other message to the one or more other applications.

2. The method of claim 1 , further comprising:

determining one or more foreign entity types based on the schema and the one or more foreign properties;

generating a native object class that is compatible with the native environment of the application based on the schema and the one or more foreign entity types, wherein the native object class declares the one or more members that correspond to the one or more foreign entities; and

employing the native object class to instantiate the native object.

3. The method of claim 1 , wherein determining the one or more relationships between the entity and the one or more foreign entities, further comprises:

determining one or more relationship records from the entity relationship table based on an identifier that corresponds to the entity, wherein each relationship record declares that the entity is a parent of the one or more foreign entities, wherein each relationship record declares a foreign entity that is a child of the entity.

4. The method of claim 1 , further comprising:

generating one or more validators that are compatible with the native environment of the application, wherein each validator corresponds to a foreign entity; and

in response to the application modifying the native object, validating the modification based on the one or more validators.

5. The method of claim 1 , further comprising:

registering the application to detect one or more messages associated with one or more modifications to the entity or the one or more foreign entities, wherein the one or more modifications are performed by the one or more other applications.

6. The method of claim 1 , further comprising:

determining one or more base properties of the entity based on the traversal of the schema, wherein each base property corresponds to a concrete value associated with the entity.

7. A network computer for managing data over a network, comprising:

a memory that stores at least instructions; and

one or more processors that execute instructions that are configured to cause actions, including:

providing a request from an application to instantiate an entity, wherein the request includes an entity version;

determining a schema that corresponds to the entity based on the entity version;

determining one or more foreign properties of the entity based on a traversal of the schema, wherein each foreign property includes a foreign entity type and a foreign entity version;

determining one or more relationships between the entity and one or more foreign entities based on an entity relationship table that is separate from the schema, wherein each relationship associates one or more foreign entity identifiers with the one or more foreign properties;

generating a native object for a native environment of the application based on the schema, the entity and the one or more foreign entities, wherein the native object includes one or more members that correspond to the one or more foreign entities;

providing data associated with the entity and the one or more foreign entities to the application based on the native object;

employing changes to the data by one or more other applications to update the native object to include the changed data;

in response to the application modifying the data of the native object, performing additional further actions:

updating the entity and the one or more foreign entities based on the modified data; and

generating a message that includes the modified data, wherein the message is provided to a message queue; and

employing the message queue to provide the other message to the one or more other applications.

8. The network computer of claim 7 , wherein the one or more processors execute instructions that are configured to cause actions, further comprising:

determining one or more foreign entity types based on the schema and the one or more foreign properties;

generating a native object class that is compatible with the native environment of the application based on the schema and the one or more foreign entity types, wherein the native object class declares the one or more members that correspond to the one or more foreign entities; and

employing the native object class to instantiate the native object.

9. The network computer of claim 7 , wherein determining the one or more relationships between the entity and the one or more foreign entities, further comprises:

determining one or more relationship records from the entity relationship table based on an identifier that corresponds to the entity, wherein each relationship record declares that the entity is a parent of the one or more foreign entities, wherein each relationship record declares a foreign entity that is a child of the entity.

10. The network computer of claim 7 , wherein the one or more processors execute instructions that are configured to cause actions, further comprising:

generating one or more validators that are compatible with the native environment of the application, wherein each validator corresponds to a foreign entity; and

in response to the application modifying the native object, validating the modification based on the one or more validators.

11. The network computer of claim 7 , wherein the one or more processors execute instructions that are configured to cause actions, further comprising:

registering the application to detect one or more messages associated with one or more modifications to the entity or the one or more foreign entities, wherein the one or more modifications are performed by the one or more other applications.

12. The network computer of claim 7 , wherein the one or more processors execute instructions that are configured to cause actions, further comprising:

determining one or more base properties of the entity based on the traversal of the schema, wherein each base property corresponds to a concrete value associated with the entity.

13. A processor readable non-transitory storage media that includes instructions configured for managing data in a computing environment, wherein execution of the instructions by one or more processors on one or more network computers performs actions, comprising:

providing a request from an application to instantiate an entity, wherein the request includes an entity version;

determining a schema that corresponds to the entity based on the entity version;

determining one or more foreign properties of the entity based on a traversal of the schema, wherein each foreign property includes a foreign entity type and a foreign entity version;

determining one or more relationships between the entity and one or more foreign entities based on an entity relationship table that is separate from the schema, wherein each relationship associates one or more foreign entity identifiers with the one or more foreign properties;

generating a native object for a native environment of the application based on the schema, the entity and the one or more foreign entities, wherein the native object includes one or more members that correspond to the one or more foreign entities;

providing data associated with the entity and the one or more foreign entities to the application based on the native object;

employing changes to the data by one or more other applications to update the native object to include the changed data;

in response to the application modifying the data of the native object, performing additional further actions:

updating the entity and the one or more foreign entities based on the modified data; and

generating a message that includes the modified data, wherein the message is provided to a message queue; and

employing the message queue to provide the other message to the one or more other applications.

14. The media of claim 13 , further comprising:

determining one or more foreign entity types based on the schema and the one or more foreign properties;

generating a native object class that is compatible with the native environment of the application based on the schema and the one or more foreign entity types, wherein the native object class declares the one or more members that correspond to the one or more foreign entities; and

employing the native object class to instantiate the native object.

15. The media of claim 13 , wherein determining the one or more relationships between the entity and the one or more foreign entities, further comprises:

determining one or more relationship records from the entity relationship table based on an identifier that corresponds to the entity, wherein each relationship record declares that the entity is a parent of the one or more foreign entities, wherein each relationship record declares a foreign entity that is a child of the entity.

16. The media of claim 13 , further comprising:

generating one or more validators that are compatible with the native environment of the application, wherein each validator corresponds to a foreign entity; and

in response to the application modifying the native object, validating the modification based on the one or more validators.

17. The media of claim 13 , further comprising:

registering the application to detect one or more messages associated with one or more modifications to the entity or the one or more foreign entities, wherein the one or more modifications are performed by the one or more other applications.

18. The media of claim 13 , further comprising:

determining one or more base properties of the entity based on the traversal of the schema, wherein each base property corresponds to a concrete value associated with the entity.

19. A system for managing resources over a network, comprising:

a network computer, comprising:

a memory that stores at least instructions; and

one or more processors that execute instructions that are configured to cause actions, including:

providing a request from an application to instantiate an entity, wherein the request includes an entity version;

determining a schema that corresponds to the entity based on the entity version;

determining one or more foreign properties of the entity based on a traversal of the schema, wherein each foreign property includes a foreign entity type and a foreign entity version;

determining one or more relationships between the entity and one or more foreign entities based on an entity relationship table that is separate from the schema, wherein each relationship associates one or more foreign entity identifiers with the one or more foreign properties;

generating a native object for a native environment of the application based on the schema, the entity and the one or more foreign entities, wherein the native object includes one or more members that correspond to the one or more foreign entities;

providing data associated with the entity and the one or more foreign entities to the application based on the native object;

employing changes to the data by one or more other applications to update the native object to include the changed data;

in response to the application modifying the data of the native object, performing additional further actions:

updating the entity and the one or more foreign entities based on the modified data; and

generating a message that includes the modified data, wherein the message is provided to a message queue; and

employing the message queue to provide the other message to the one or more other applications; and

one or more other network computers, comprising:

a memory that stores at least instructions; and

one or more processors that execute instructions that are configured to cause actions, including:

hosting the application.

20. The system of claim 19 , wherein the one or more processors of the one or more network computers execute instructions that are configured to cause actions, further comprising:

determining one or more foreign entity types based on the schema and the one or more foreign properties;

generating a native object class that is compatible with the native environment of the application based on the schema and the one or more foreign entity types, wherein the native object class declares the one or more members that correspond to the one or more foreign entities; and

employing the native object class to instantiate the native object.

21. The system of claim 19 , wherein determining the one or more relationships between the entity and the one or more foreign entities, further comprises:

determining one or more relationship records from the entity relationship table based on an identifier that corresponds to the entity, wherein each relationship record declares that the entity is a parent of the one or more foreign entities, wherein each relationship record declares a foreign entity that is a child of the entity.

22. The system of claim 19 , wherein the one or more processors of the one or more network computers execute instructions that are configured to cause actions, further comprising:

generating one or more validators that are compatible with the native environment of the application, wherein each validator corresponds to a foreign entity; and

in response to the application modifying the native object, validating the modification based on the one or more validators.

23. The system of claim 19 , wherein the one or more processors of the one or more network computers execute instructions that are configured to cause actions, further comprising:

registering the application to detect one or more messages associated with one or more modifications to the entity or the one or more foreign entities, wherein the one or more modifications are performed by the one or more other applications.

24. The system of claim 19 , wherein the one or more processors of the one or more network computers execute instructions that are configured to cause actions, further comprising:

determining one or more base properties of the entity based on the traversal of the schema, wherein each base property corresponds to a concrete value associated with the entity.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 14, 2024
From: SMELTZER, KENTON LAMAR; CRUZ, MICHAEL ANGEL; TOMER, WILLIAM; WALDMAN, CHAD GARRETT; MASON, CLARE RENE
To: DEXCARE, INC.
Reel/Frame 068284/0595 →
Continuity (2)
Provisional Application 63539960 · Sep 22, 2023
Related Publication 20250103405A1 · Mar 27, 2025
References Cited (84)
US 7082502B2 · Najam · 2006 [cited by examiner]
US 7383285B1 · Pal · 2008 [cited by examiner]
US 7617223B1 · Devanathan · 2009 [cited by examiner]
US 8145726B1 · Roche et al. · 2012 [cited by applicant]
US 8806431B1 · Colton · 2014 [cited by examiner]
US 9372731B1 · Marr et al. · 2016 [cited by applicant]
US 9380268B2 · Weber et al. · 2016 [cited by applicant]
US 9402054B2 · Aaron et al. · 2016 [cited by applicant]
US 9497412B1 · Rosenberg · 2016 [cited by applicant]
US 9565246B1 · Tsypliaev · 2017 [cited by examiner]
US 10055450B1 · Tansel · 2018 [cited by examiner]
US 10223150B2 · Livshits · 2019 [cited by examiner]
US 10452645B2 · Watson · 2019 [cited by examiner]
US 10545950B2 · Collins · 2020 [cited by examiner]
US 11138164B1 · Munuhur Rajagopal · 2021 [cited by examiner]
US 11416798B2 · Brannon · 2022 [cited by examiner]
US 11595221B1 · Wlodarczyk et al. · 2023 [cited by applicant]
US 11636086B1 · Goodnow · 2023 [cited by examiner]
US 11640565B1 · Pfeiler · 2023 [cited by examiner]
US 11641385B1 · Ferry et al. · 2023 [cited by applicant]
US 11838140B2 · Wlodarczyk et al. · 2023 [cited by applicant]
US 11854708B2 · Streat et al. · 2023 [cited by applicant]
US 11930060B2 · Ferry et al. · 2024 [cited by applicant]
US 12235810B2 · Cao · 2025 [cited by examiner]
US 20040185785A1 · Mir et al. · 2004 [cited by applicant]
US 20060271400A1 · Clements et al. · 2006 [cited by applicant]
US 20140180715A1 · Phillips et al. · 2014 [cited by applicant]
US 20140313282A1 · Ma et al. · 2014 [cited by applicant]
US 20160308737A1 · Liu et al. · 2016 [cited by applicant]
US 20170272485A1 · Gordon et al. · 2017 [cited by applicant]
US 20190079786A1 · Shani et al. · 2019 [cited by applicant]
US 20190122760A1 · Wang · 2019 [cited by applicant]
US 20190333613A1 · Zaidi et al. · 2019 [cited by applicant]
US 20200222813A1 · Baszucki · 2020 [cited by applicant]
US 20200357494A1 · Kadri et al. · 2020 [cited by applicant]
US 20210076001A1 · Periyannan et al. · 2021 [cited by applicant]
US 20210314526A1 · Astarabadi et al. · 2021 [cited by applicant]
US 20210319914A1 · Roh · 2021 [cited by applicant]
US 20210358618A1 · Crocker · 2021 [cited by applicant]
US 20210399911A1 · Jorasch et al. · 2021 [cited by applicant]
US 20210400142A1 · Jorasch et al. · 2021 [cited by applicant]
US 20210406841A1 · Chen et al. · 2021 [cited by applicant]
US 20220165401A1 · Levitt · 2022 [cited by applicant]
US 20220215970A1 · Trpkovski et al. · 2022 [cited by applicant]
US 20230153740A1 · Meehan et al. · 2023 [cited by applicant]
US 20230187086A1 · Streat et al. · 2023 [cited by applicant]
US 20230291592A1 · Wlodarczyk et al. · 2023 [cited by applicant]
US 20230403314A1 · Ferry et al. · 2023 [cited by applicant]
US 20240120043A1 · Kaushal et al. · 2024 [cited by applicant]
CN 113923441A · 2022 [cited by applicant]
JP 2016167676A · 2016 [cited by applicant]
WO 2014018012A1 · 2014 [cited by applicant]
WO 2016019227A1 · 2016 [cited by applicant]
WO 2023172390A1 · 2023 [cited by applicant]
Madine et al, “Fully Decentralized Multi-Party Consent Management for Secure Sharing of Patient Health Records”, IEEE, pp. 1-15 (Year: 2020). [cited by examiner]
Liu et al., “Automated Software Entity Matching Between Successive Versions”, IEEE, pp. 1615-1627 (Year: 2023). [cited by examiner]
Wang et al, “Method for Relation Extraction Based on Entity Boundary Features”, ACM, pp. 1-6 (Year: 2024). [cited by examiner]
Nie et al, “An entity relation extraction method based on the fusion of contextual information”, ACM, pp. 1-6 (Year: 2023). [cited by examiner]
Huang et al, “API Entity and Relation Joint Extraction from Text via Dynamic Prompt-tuned Language Model”, ACM, pp. 1-25 (Year: 2023). [cited by examiner]
Office Communication for U.S. Appl. No. 18/615,623 mailed Sep. 25, 2024, pp. 1-12. [cited by applicant]
International Preliminary Report on Patentability Chapter I for International Patent Application No. PCT/US2023/013531 mailed Sep. 26, 2024, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Nov. 1, 2023, pp. 1-22. [cited by applicant]
Office Communication for U.S. Appl. No. 17/837,218 mailed Mar. 9, 2023, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 17/837,218 mailed Mar. 15, 2023, pp. 1-2. [cited by applicant]
Office Communication for U.S. Appl. No. 18/114,916 mailed May 23, 2023, pp. 1-9. [cited by applicant]
Office Communication for U.S. Appl. No. 17/837,218 mailed Nov. 17, 2022, pp. 1-20. [cited by applicant]
Office Communication for U.S. Appl. No. 17/692,738 mailed Jan. 5, 2023, pp. 1-8. [cited by applicant]
Office Communication for U.S. Appl. No. 17/837,218 mailed Feb. 9, 2023, pp. 1-5. [cited by applicant]
Office Communication for U.S. Appl. No. 17/837,218 mailed Aug. 12, 2022, pp. 1-17. [cited by applicant]
Office Communication for U.S. Appl. No. 17/692,738 mailed Oct. 4, 2022, pp. 1-10. [cited by applicant]
Office Communication for U.S. Appl. No. 17/692,738 mailed Jun. 13, 2022, pp. 1-9. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed May 23, 2023, pp. 1-6. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Sep. 16, 2022, pp. 1-4. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Jul. 1, 2022, pp. 1-59. [cited by applicant]
Office Communication for U.S. Appl. No. 18/114,916 mailed Sep. 19, 2023, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Jul. 13, 2023, pp. 1-28. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Nov. 15, 2022, pp. 1-61. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Mar. 6, 2023, pp. 1-26. [cited by applicant]
Office Communication for U.S. Appl. No. 18/130,660 mailed Sep. 28, 2023, pp. 1-19. [cited by applicant]
Office Communication for U.S. Appl. No. 18/130,660 mailed Dec. 14, 2023, pp. 1-4. [cited by applicant]
Office Communication for U.S. Appl. No. 18/130,660 mailed Jan. 11, 2024, pp. 1-7. [cited by applicant]
Office Communication for U.S. Appl. No. 18/130,660 mailed Jun. 14, 2023, pp. 1-16. [cited by applicant]
Office Communication for U.S. Appl. No. 17/551,084 mailed Mar. 14, 2022, pp. 1-52. [cited by applicant]
Office Communication for U.S. Appl. No. 18/615,623 mailed Jun. 21, 2024, pp. 1-12. [cited by applicant]