Abstract: Information about a medical provider's locations, brands, and gateways can be received (e.g., via an online portal). This information can be used to generate a data object that represents relationships between the locations, the brands, and the gateways. This data object can be maintained in a database base that is searchable by a user device. For example, a user of the user device may search the database to identify a medical provider where the user obtains care. Once identified, other systems can be used to connect the user device to a gateway associated with the medical provider in order to download electronic health record data associated with the user.

Abstract: A server may maintain information about entities such as medical entities. A user device can send search queries to the server to obtain information about a particular medical entity. The server and/or the user device may maintain information relating to the particular medical entity in a manner that a relationship between the particular medical entity and the user device can be obfuscated from the server. By doing so, privacy of a user of the user device can be protected.

Abstract: Prior to connecting to a gateway associated with an electronic health record system, a user device can check in with a server. The server can send configuration information useable by the user device for connecting to the gateway for downloading medical record data. The configuration information may include an update value that is useable by the user device to determine a time frame for contacting the gateway. In some examples, the user device determines when to contact the gateway without using the update value.

Abstract: A server may maintain information about entities such as medical entities. A user device can send search queries to the server to obtain information about a particular medical entity. The server and/or the user device may maintain information relating to the particular medical entity in a manner that a relationship between the particular medical entity and the user device can be obfuscated from the server. By doing so, privacy of a user of the user device can be protected.

Abstract: A server may maintain information about entities such as medical entities. A user device can send search queries to the server to obtain information about a particular medical entity. Using techniques described herein, the server and/or the user device may maintain information relating to the particular medical entity in a manner that a relationship between the particular medical entity and the user device can be obfuscated from the server. By doing so, privacy of a user of the user device can be protected.

Abstract: Prior to connecting to a gateway associated with an electronic health record system, a user device can check in with a server. The server can send configuration information useable by the user device for connecting to the gateway for downloading medical record data. The configuration information may include an update value that is useable by the user device to determine a time frame for contacting the gateway. In some examples, the user device determines when to contact the gateway without using the update value.

Abstract: Information about a medical provider's locations, brands, and gateways can be received (e.g., via an online portal). This information can be used to generate a data object that represents relationships between the locations, the brands, and the gateways. This data object can be maintained in a database base that is searchable by a user device. For example, a user of the user device may search the database to identify a medical provider where the user obtains care. Once identified, other systems can be used to connect the user device to a gateway associated with the medical provider in order to download electronic health record data associated with the user.

Abstract: A server may maintain information about entities such as medical entities. A user device can send search queries to the server to obtain information about a particular medical entity. Using techniques described herein, the server and/or the user device may maintain information relating to the particular medical entity in a manner that a relationship between the particular medical entity and the user device can be obfuscated from the server. By doing so, privacy of a user of the user device can be protected.