Back to results
US 11,106,818 B2Granted
Patient identification systems and methods
AssigneeLifeMed ID, Incorporated
InventorsDavid Batchelor, Catherine Schulten, Elvar H. Olafsson
Life of this patent
Estimating the term…
Abstract
Systems and methods for managing patient information across various electronic medical record (EMR) systems, according to some examples can involve providing a patient information management system having a cloud-based application server including a database, a client application interface and a mobile security token. A one-time verification code can be sent from the cloud-based application server to the client computing device and read using the mobile security token. The mobile security token can be matched to a patient demographic record in the database to authenticate the patient using the linked mobile security token.
Claims25
A patient information management system for matching a patient with their health records, comprising:
- a cloud-based application server, comprising a database having patient demographic records stored thereon, the patient demographic records being linked to one or more electronic medical records (EMRs) on a healthcare entity's electronic medical record system (EMR system), the cloud-based application server configured to retrieve, over a network, EMRs from one or more EMR systems to a corresponding patient demographic record stored in the database;
- a client application interface provided on a healthcare entity computing device, the client application interface being configured to communicate with the cloud-based application server, the healthcare entity computing device being physically located at a client healthcare entity such that EMR systems, other than the EMR systems of the client healthcare entity, being inaccessible by healthcare entity computing device;
- and
- a mobile security token generated by the cloud-based application server and provided on a patient computing device separate and distinct from the healthcare entity computing device, the mobile security token being configured to communicate with the cloud-based application server, wherein the mobile security token is unique for each patient in the one or more EMRs, whereby, the cloud-based application server is configured to:
- link the patient computing device to the mobile security token in the patient demographic record,
- in response to receiving a request for patient authentication for a particular patient from the healthcare entity computing device, generate a one-time verification code for the particular patient, wherein the one-time verification code comprises a dynamic code that changes for each request at the healthcare entity computing device,
- send the one-time verification code generated by the cloud-based application server to the healthcare entity computing device,
- receive an indication of the one-time verification code and an indication of the mobile security token from the patient computing device, and
- in response to receiving the indication of the one-time verification code and the indication of the mobile security token from the patient computing device, determine that the one-time verification code matches the generated one-time verification code and that the mobile security token matches an expected mobile security token stored in the patient demographic record, and thereby authenticate the particular patient.
6 more elements
A method of accessing a patient's information from multiple electronic medical record (EMR) systems, comprising:
- providing a patient information management system, comprising:
- a cloud-based application server, comprising a database having patient demographic records stored thereon, the cloud-based application server being connected to one or more electronic medical record systems (EMR systems) over a network, each EMR system being inaccessible by other EMR systems,
- a client application interface provided on a healthcare entity computing device physically located at a healthcare entity, and
- a mobile security token generated by the cloud-based application server and provided on a patient computing device separate and distinct from the healthcare entity computing device, wherein the mobile security token is unique for each patient in the one or more EMRs;
- in response to receiving a request for patient authentication for a particular patient from the healthcare entity computing device, generating, by the cloud-based application server, a one-time verification code for the particular patient, wherein the one-time verification code comprises a dynamic code that changes for each request at the healthcare entity computing device;
- sending, from the cloud-based application server, the one-time verification code generated by the cloud-based application server to the healthcare entity computing device;
- using the patient computing device to read the one-time verification code sent to the healthcare entity computing device;
- receiving, by the cloud-based application server and from the patient computing device, an indication of the one-time verification code and an indication of the mobile security token;
- determining that the one-time verification code matches the generated one-time verification code and that the mobile security token matches an expected mobile security token stored in the patient demographic record;
- and
- authenticating the patient using the linked mobile security token prior to accessing and/or releasing the patient's EMR from an EMR system.
8 more elements
A method of linking a patient's demographic data stored on a cloud-based application server to an Electronic Medical Record (EMR) system of a client healthcare entity, comprising:
- capturing patient demographic data;
- providing a mobile security token, generated by the cloud-based application server, on a patient computing device, wherein the mobile security token is unique for each patient in the EMR;
- in response to receiving a request for patient authentication for a particular patient from a healthcare entity computing device separate and distinct from the patient computing device, generating, from a cloud-based application server, a one-time verification code for the particular patient, wherein the one-time verification code comprises a dynamic code that changes for each request at the healthcare entity computing device;
- sending the one-time verification code generated by the cloud-based application server to the healthcare entity computing device located at the client healthcare entity, the healthcare entity computing device being in communication with the cloud-based application server;
- generating a location and/or time of visit encoded QR code based on the one-time verification code;
- displaying the QR code using the healthcare entity computing device;
- using the patient computing device to read the single-use QR code and to send the one-time verification code and the mobile security token to the cloud-based server, thereby confirming that the patient is physically present at the same location as the healthcare entity computing device;
- performing, using the cloud-based application server, an automated matching exercise to determine if another record exists in the cloud-based application server or another EMR system in communication therewith, that matches patient data captured;
- and
- linking the mobile security token to the patient computing device and a patient record created and stored in the cloud-based application server.
7 more elements
Dependencies are inferred from the claim text.