Apple Inc.

Sean Robert Moore

Jorge Fernando Pozas Trevino

Sangeeth Sridharan

Mark E Pennell

Todd D Power

Pablo Antonio Gonzalez Cervantes

Mohan Singh Randhava

Eric K Kimn

Sami Shaio

Kevin M Lynch

Dongsheng Zhang

Meghan Tushar Raul

Pascal B Pfiffner

A schema is generated to establish a connection between user devices and one or more patient record servers. Generating a schema can include receiving configuration information associated with a patient record gateway, wherein the patient record gateway is associated with one or more patient record servers configured for storing electronic health records for a plurality of patients. Generating a schema can include defining, based at least in part on the configuration information, a schema configured to enable user devices to retrieve, via the patient record gateway, electronic health records from the one or more patient record servers. A schema can be requested by a user device. The schema can be sent to a user device to establish a connection with the one or more patient record servers.

Gateway conformance validation

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.

Techniques for anonymized searching of medical providers

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.

Techniques for building medical provider databases

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.

Techniques for managing access of user devices to third-party resources

A patient record gateway of an electronic health record system can be validated using a conformance statement that defines capabilities and characteristics of patient record servers associated with the gateway. Part of validating the patient record gateway includes performing a configuration test of the patient record gateway using the conformance statement.

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.

Growing community of inventors

San Francisco, CA, United States of America

Sean Robert Moore