# US 2020/0401465 A1 · Apparatuses, systems, and methods for providing healthcare integrations > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2020/0401465 A1 - Document ID: US20200401465A1 - Status: Published application - Kind: A1 - Application number: 16/907,271 - Filed: 2020-06-21 - Published: 2020-12-24 - Earliest claimed: 2019-06-21 - Applicants: The Bridgecr LLC - Inventors: Joshua Adam Douglas; Matthew Thomas Wimberley; Clinton Thomas Johnson - Web page: https://patentgrep.com/patent/US20200401465A1 ## CPC - G06F 9/541: {via adapters, e.g. between incompatible applications} - G16H 40/00: ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices - G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms - G16H 40/67: for remote operation - G16H 80/00: ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems, methods, and apparatuses for providing healthcare integrations, are provided. The system may include a network, a server communicatively coupleable to the network, the server configured to generate an interface accessible via the network, a plurality of third-party service Application Programming Interfaces (APIs) coupleable to the network, and a user device coupleable to the network, the user device configured to access the interface generated by the server to generate a connector, the connector configured to include at least one of the plurality of third-party service APIs. ## Claims ### Claim 1 A method for providing healthcare integrations, comprising: receiving a request to generate a connector; identifying a source and a destination for the connector; selecting at least one action associated with the connector; defining a parameter associated with the at least one action; and generating the connector based at least in part upon the identified source and destination, and the selected at least one action, the defined parameter. ### Claim 2 (depends on 1) The method of claim 1, further comprising: generating an interface for a user to provide at least one of the identified source and destination, the selected at least one action, or the defined parameter. ### Claim 3 (depends on 1) The method of claim 1, further comprising: implementing an artificial intelligence (AI) component; and predicting at least one connector setting based at least in part using the AI component. ### Claim 4 (depends on 3) The method of claim 3, further comprising: storing historical connector information relating to at least one connector, wherein the predicting the at least one connector setting is based at least in part upon the historical connector information. ### Claim 5 (depends on 1) The method of claim 1, further comprising: translating at least a portion of the at least one action based upon a defined data model. ### Claim 6 (depends on 1) The method of claim 1, further comprising: providing a gateway to coordinate communications with at least one third-party Application Programming Interface (API) forming at least a part of the connector. ### Claim 7 An apparatus for providing healthcare integrations, comprising: a core gateway configured to communicate with at least one third-party Application Programming Interface (API); a storage configured to store connector profile information; a server configured to generate an interface associated with at least one connector, the interface configured to permit a user to generate at least one connector; an analysis engine configured to interpret at least one communication associated with a connector and configured to store a representation of the interpreted at least one communication associated with the connector; and a connector generator, the connector generator configured to generate a connector based at least in part upon. ### Claim 8 (depends on 7) The apparatus of claim 7, wherein the analysis engine includes an artificial intelligence (AI) component configured to analyze at least a portion of the connector profile information stored at the storage and to predict information regarding at least one connector. ### Claim 9 (depends on 7) The apparatus of claim 7, further comprising: a connector generator configured to generate a connector based at least in part upon an identified source and destination, at least one action, or a defined parameter associated with the connector. ### Claim 10 A system for providing healthcare integrations, comprising: a network; a server communicatively coupleable to the network, the server configured to generate an interface accessible via the network; a plurality of third-party service Application Programming Interfaces (APIs) coupleable to the network; and a user device coupleable to the network, the user device configured to access the interface generated by the server to generate a connector, the connector configured to include at least one of the plurality of third-party service APIs. ### Claim 11 (depends on 10) The system of claim 10, further comprising: an artificial intelligence (AI) component configured to predict at least one connector setting based at least in part using the AI component. ### Claim 12 (depends on 11) The system of claim 11, further comprising: a storage configured to store historical connector information relating to at least one connector, wherein the AI component predicting the at least one connector setting is based at least in part upon the historical connector information. ### Claim 13 (depends on 12) The system of claim 12, wherein the system is configured to translate at least a portion of information relating to the at least one connector setting based upon a defined data model. ### Claim 14 (depends on 13) The system of claim 13, further comprising a core gateway configured to communicate with at least one of the plurality of third-party service APIs, the core gateway configured to coordinate the translation of the at least a portion of information relating to the at least one connector setting. ### Claim 15 (depends on 10) The system of claim 10, further comprising a core gateway configured to communicate with at least one of the plurality of third-party service APIs.