Integrating and/or adding longitudinal information to a de-identified database
US-2017132372-A1 · May 11, 2017 · US
US11636927B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11636927-B2 |
| Application number | US-201815884115-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 30, 2018 |
| Priority date | Sep 29, 2017 |
| Publication date | Apr 25, 2023 |
| Grant date | Apr 25, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: a memory configured to store computer-executable instructions; and a processor in communication with the memory and configured to execute the computer-executable instructions to at least: for a plurality of organization entities, receive, from a user device operated by an authorized user of an organization entity, information about a plurality of brand entities, a plurality of location entities, and at least one gateway entity, the plurality of brand entities, the plurality of location entities, and the at least one gateway entity associated with respective entity identifiers; associate, based at least in part on the information, the plurality of brand entities with the plurality of location entities to create a first set of relationships, the plurality of brand entities being related to each other via the organization entity; associate, based at least in part on the information, the plurality of location entities with the at least one gateway entity to generate a second set of relationships, the at least one gateway entity being shared between at least two of the plurality of location entities; and store the respective entity identifiers, the first set of relationships, and the second set of relationships in a medical provider database; generate a search index representing the respective entity identifiers, the first set of relationships, and the second set of relationships stored in the medical provider database; configure the search index for searching the medical provider database based on provider name; enable a second user device to search the medical provider database, using the search index, for at least one entity of a particular organization entity, a particular brand entity, or a particular location entity; and enable the second user device to establish a first persistent data connection with a first gateway of a first medical provider identified in the medical provider database and a second persistent data connection with a second gateway of a second medical provider identified in the medical provider database, the at least one gateway entity associated with the first gateway, wherein enabling the second user device to establish the first persistent data connection with the first gateway of the first medical provider comprises enabling the second user device to obtain an access token and a refresh token from an electronic health record system corresponding to the first gateway, wherein the access token and the refresh token are useable by the second user device to establish and maintain the first persistent data connection with the first gateway. 2. The system of claim 1 , wherein the plurality of location entities comprise physical locations where users obtain medical treatment. 3. The system of claim 1 , wherein each of the first gateway and the second gateway is associated with an electronic health record system configured to maintain electronic health records for multiple users. 4. The system of claim 1 , wherein storing the respective entity identifiers, the first set of relationships, and the second set of relationships in the medical provider database comprises storing a data object that represents the organization entity, the plurality of brand entities, the plurality of location entities, the at least one gateway entity, the first set of relationships, and the second set of relationships. 5. The system of claim 1 , wherein the memory includes further computer-executable instructions and the processor is further configured to execute the further computer-executable instructions to at least: receive, from the second user device which is operated by a second user, a search request identifying at least one of the particular organization entity, the particular brand entity, or the particular location entity; determine, based on the search request and using the medical provider database, the at least one gateway entity that stores electronic health records for patients of at least one of the particular organization entity, the particular brand entity, or the particular location entity; and send, the second user device, configuration information that is useable by the second user device to establish the first persistent data connection with the first gateway to download health record data of the second user. 6. The system of claim 5 , wherein the memory includes further computer-executable instructions and the processor is further configured to execute the further computer-executable instructions to at least, responsive to receiving a different search request, send different configuration information to the second user device that is useable by the second user device to connect to different gateway entities to download different health record data of the second user to the second user device. 7. The system of claim 1 , wherein each of the first and second persistent data connection enables the second user device to download health record data and updates to the health record data from the respective first and second gateways. 8. The system of claim 1 , wherein enabling the second user device to search the medical provider database comprises sending a prepopulated set of search results to the second user device, the prepopulated set of search results having physical locations that are geographically near a current geographic location of the second user device. 9. The system of claim 1 , wherein enabling the second user device to establish the first persistent data connection with the first gateway is performed without a service provider that operates the system receiving existing first electronic health data and future first electronic health data from the first gateway or sending the existing first electronic health data and the future first electronic health data to the second user device. 10. The system of claim 1 , wherein the memory includes further computer-executable instructions and the processor is further configured to execute the further computer-executable instructions to at least: provide for presentation, at the user device operated by the authorized user of the organization entity, a plurality of user interface views of a graphical user interface, the plurality of user interface views comprising: a first user interface view configured to receive entity information relating to a type of organization entity; a second user interface view configured to receive gateway configuration information; a third user interface view configured to receive endpoint configuration information; and a fourth user interface view configured to receive test credentials for testing an endpoint connection, wherein receiving the information from the user device comprises receiving, via inputs at the plurality of user interface views presented at the user device. 11. The system of claim 1 , wherein enabling the second user device to search the medical provider database comprises, prior to receiving a search request from the second user device, sending a prepopulated set of search results to the second user device, the prepopulated set of search results identifying particular medical providers having physical locations that are geographically near a current geographic location of the second user device. 12. A computer-implemented method, comprising: receiving, from a first user device, information about a plurality of location entities and at least one gateway entity, the plurality of location entities and the at least one gateway entity associated with respective entity identifiers; associating, based at least in part on the information, the plurality of location entities with the at least one gateway entity to create
for mining of medical data, e.g. analysing previous cases of other patients · CPC title
Indexing; Data structures therefor; Storage structures · CPC title
for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms · CPC title
using location based information parameters · CPC title
for patient-specific data, e.g. for electronic patient records · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.