Apple Inc.

Mohan Singh Randhava

Jorge Fernando Pozas Trevino

Pablo Antonio Gonzalez Cervantes

Dongsheng Zhang

Sean Robert Moore

Sangeeth Sridharan

Todd D Power

Eric K Kimn

Yannick L Sierra

Steven Andrew Myers

Amir H Jadidi

Suhail Ahmad

Samuel A Mussell

Meghan Tushar Raul

Pascal B Pfiffner

Zhengjun Jiang

Kevin M Lynch

Mark E Pennell

Isaac Pinol Catadau

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.

Secure storage and retrieval of sensitive information

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 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.

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

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.

Growing community of inventors

Redwood City, CA, United States of America

Mohan Singh Randhava