# US 12,216,784 B1 · Systems and processes for synchronizing disparate applications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,216,784 B1 - Document ID: US12216784B1 - Status: Granted - Kind: B1 - Application number: 17/831,214 - Filed: 2022-06-02 - Granted: 2025-02-04 - Earliest claimed: 2021-06-02 - Assignees: MedTrans Go, Inc. - Applicants: MedTrans Go, Inc. - Inventors: Obinwanne Ugwonali; Dana Weeks Ugwonali - Web page: https://patentgrep.com/patent/US12216784B1 ## CPC - G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - G06F 9/547: {Remote procedure calls [RPC]; Web services} - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems and processes for synchronizing disparate applications are described herein. In various embodiments, the process includes: (1) receiving and validating a log-in request; (2) receiving a request submission comprising a plurality of data items; (3) writing the plurality of data items into a dynamic and scalable data model; (4) determining request parameters associated with the plurality of data items; (5) determining a recommended deployment strategy based on the one or more parameters and characteristic values stored in the data model; (6) generating a and transmitting one or more notifications according to the recommended deployment strategy; and (7) generating and/or modifying a display based on the notification(s). ## Claims ### Claim 1 A computing architecture comprising: a JSON document memory store comprising a collection associated with a particular entity and a particular access level of a plurality of access levels; and a processor communicably connected to the JSON document memory store and configured for: receiving a log-in request from the particular entity; based on receiving the log-in request, providing access to a portal associated with the particular access level of the particular entity; receiving a first request from the particular entity via the portal, the first request comprising a plurality of first data items, the plurality of first data items comprising an indication of one or more third-party services; writing the plurality of first data items to a first document associated with the collection; providing at least one of the plurality of first data items to the one or more third-party services via a first application programming interface (API); receiving third-party data derived from the particular entity using the one or more third-party services; writing the third-party data to the first document; transmitting a portion of the third-party data and at least one data item of the plurality of first data items to a notification system via a second API, whereby the notification system transmits a notification to the particular entity; receiving a second request from the particular entity via the portal, the second request comprising a plurality of second data items, the plurality of second data items comprising an indication of one or more partner services and a partner attribute; writing the plurality of second data items to a second document associated with the collection; and determining that a particular partner service of the one or more partner services comprises the partner attribute. ### Claim 2 (depends on 1) The computing architecture of claim 1, wherein the plurality of access levels comprise administrator, provider, and partner. ### Claim 3 (depends on 2) The computing architecture of claim 2, wherein the third-party data is associated with a request identifier. ### Claim 4 (depends on 1) The computing architecture of claim 1, wherein the processor is further configured for facilitating a notification to the particular partner service, the notification comprising at least one of the plurality of second data items. ### Claim 5 (depends on 4) The computing architecture of claim 4, wherein facilitating the notification to the particular partner service comprises transmitting the at least one second data items to a notification system via a notification API. ### Claim 6 (depends on 1) The computing architecture of claim 1, wherein the partner attribute comprises a transportation-specific attribute or a language-specific attribute. ### Claim 7 (depends on 6) The computing architecture of claim 6, wherein the transportation-specific attribute comprises wheelchair accessibility. ### Claim 8 (depends on 7) The computing architecture of claim 7, wherein the language-specific attribute comprises speaking a specific language. ### Claim 9 A computing process comprising: receiving, via at least one processor, a log-in request from a particular entity; based on receiving the log-in request, providing access to a portal associated with a particular access level of the particular entity; receiving a first request from the particular entity via the portal, the first request comprising a plurality of first data items, the plurality of first data items comprising an indication of one or more third-party services; writing the plurality of first data items to a first document associated with a collection of a JSON document memory store associated with the particular entity; providing at least one of the plurality of first data items to the one or more third-party services via a first application programming interface (API); receiving third-party data derived from the particular entity using the one or more third-party services; writing the third-party data to the first document; transmitting a portion of the third-party data and at least one data item of the plurality of first data items to a notification system via a second API, whereby the notification system transmits a notification to the particular entity; receiving a second request from the particular entity via the portal, the second request comprising a plurality of second data items, the plurality of second data items comprising an indication of one or more partner services and a partner attribute; writing the plurality of second data items to a second document associated with the collection; and determining that a particular partner service of the one or more partner services comprises the partner attribute. ### Claim 10 (depends on 9) The computing process of claim 9, wherein the plurality of access levels comprise administrator, provider, and partner. ### Claim 11 (depends on 10) The computing process of claim 10, wherein the third-party data is associated with a request identifier. ### Claim 12 (depends on 9) The computing process of claim 9, wherein the processor is further configured for facilitating a notification to the particular partner service, the notification comprising at least one of the plurality of second data items. ### Claim 13 (depends on 12) The computing process of claim 12, wherein facilitating the notification to the particular partner service comprises transmitting the at least one second data items to a notification system via a notification API. ### Claim 14 (depends on 9) The computing process of claim 9, wherein the partner attribute comprises a transportation-specific attribute or a language-specific attribute. ### Claim 15 (depends on 14) The computing process of claim 14, wherein the transportation-specific attribute comprises wheelchair accessibility. ### Claim 16 (depends on 15) The computing process of claim 15, wherein the language-specific attribute comprises speaking a specific language.