Abstract: Techniques for storing health data can include a multi-node data structure. A data node, a category node, and an institution node of a multi-node data structure can be generated in accordance with a configuration file. The data node can include health data and can be identified by a first unique data identifier and encrypted using a first cryptographic key. The category node can include the first unique data identifier and the first cryptographic key. The category node can be identified by a second unique data identifier and encrypted using a second cryptographic key. The institution node can include the second unique data identifier and the second cryptographic key. The institution node can be identified by a third unique data identifier and encrypted using a third cryptographic key. The data node, the category node, and the institution node can be shared with a service provider.

Abstract: Techniques for storing health data can include a multi-node data structure. A data node, a category node, and an institution node of a multi-node data structure can be generated in accordance with a configuration file. The data node can include health data and can be identified by a first unique data identifier and encrypted using a first cryptographic key. The category node can include the first unique data identifier and the first cryptographic key. The category node can be identified by a second unique data identifier and encrypted using a second cryptographic key. The institution node can include the second unique data identifier and the second cryptographic key. The institution node can be identified by a third unique data identifier and encrypted using a third cryptographic key. The data node, the category node, and the institution node can be shared with a service provider.

Abstract: A term base can be used to index a raw medical term (e.g., a text string from an electronic health record) to generate a computational expression of the raw medical term. The computational expression of the raw medical term can be used to generate a uniform medical term for the raw medical term. The computational expression can be compared with other computational expressions to organize the electronic health record, filter the electronic health record, and provide a uniform presentation of raw medical terms from different events in the electronic health record.

Abstract: A user device may share encrypted health data with an electronic health record (EHR) system associated with a health institution. A unique data identifier that identifies a portion of the health data and a cryptographic key may be shared with the EHR system. The encrypted health may be shared with a service provider and a unique data identifier. To access the health data, the EHR system may query the service provider with the unique data identifier.

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: 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: 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 system implemented by a service provider may store health data of a user according to a multi-node data structure. The server system may generate transaction records based on requests to access the health data. Responsive to requests for the transaction records, the server system may query a database that includes the health data and generate a data package based on the querying. The data package may be sent to a requesting system. The data package may be usable by the requesting system to identify which patient profiles were accessed by which physicians.

Abstract: A user device may share encrypted health data with an electronic health record (EHR) system associated with a health institution. A unique data identifier that identifies a portion of the health data and a cryptographic key may be shared with the EHR system. The encrypted health may be shared with a service provider and a unique data identifier. To access the health data, the EHR system may query the service provider with the unique data identifier.

Abstract: A term base can be used to index a raw term (e.g., a text string from an electronic health record) to generate a computational expression of the raw term. As part of doing so, portions of the raw term including personally identifying information can be removed and/or replaced with de-identified information. The computational expression of the raw term can be used to generate a version of the raw term that is devoid of the personally identifying information.

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: A term base can be used to index a raw term (e.g., a text string from an electronic health record) to generate a computational expression of the raw term. As part of doing so, portions of the raw term including personally identifying information can be removed and/or replaced with de-identified information. The computational expression of the raw term can be used to generate a version of the raw term that is devoid of the personally identifying information.

Abstract: A term base can be used to index a raw medical term (e.g., a text string from an electronic health record) to generate a computational expression of the raw medical term. The computational expression of the raw medical term can be used to generate a uniform medical term for the raw medical term. The computational expression can be compared with other computational expressions to organize the electronic health record, filter the electronic health record, and provide a uniform presentation of raw medical terms from different events in the electronic health record.

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. 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: Intuitive photo grouping is accomplished utilizing photo metadata information, including photos' timestamps, GPS information, name and storage folder identity, to automatically generate logical and meaningful event photo groupings for users.

Abstract: Intuitive photo grouping is accomplished utilizing photo metadata information, including photos' timestamps, GPS information, name and storage folder identity, to automatically generate logical and meaningful event photo groupings for users.

Abstract: Intuitive photo grouping is accomplished utilizing photo metadata information, including photos' timestamps, GPS information, name and storage folder identity, to automatically generate logical and meaningful event photo groupings for users.

Abstract: Intuitive photo grouping is accomplished utilizing photo metadata information, including photos' timestamps, GPS information, name and storage folder identity, to automatically generate logical and meaningful event photo groupings for users.