AIMe stands for Authoritative Identity Management Exchange™, providing the elemental foundation for your technology ecosystem and roadmap. "Authoritative" - AIMe acts as the source of truth for identifying a patient's record by tying a unique ID to the patient's medical record. "Identity Management" - AIMe provides a single platform for managing your patient population's identity safely and effectively. "Exchange" - AIMe enables your patient's to use one ID to access and invoke their medical record(s) at all points of care.
AIMe has a sleek and user friendly user interface (UI) that requires little to no training to use. The application has three main screens: Patient Look Up, Patient Summary, and Settings. The Patient Look Up screen is utilized as a search screen, while the Patient Summary screen displays the patient's AIMe record. From the Patient Summary screen, all of the ID token management and verification services are available.
LifeMed ID uses the term "ID" as an identity token or authenticator. It is typically a physical item, such as a smart card or smartphone, that is globally unique. AIMe leverages this item by tying it to your medical record to invoke it at each point of care. IDs are customer-defined IDs, such as Driver's License/Identification Cards, payment cards and biometrics.
Available ID's include Smart Cards, Smart Phones, BYOID™ and Biometrics. While these are the IDs that are available today, as new authenticators are identified, LifeMed ID is capable of accommodating them.
With AIMe, we created a process that makes it easier and faster for you to identify patients with accuracy, having a positive impact on reconciliation and operational cost. Only at the patient's first visit will you have to create and associate an ID token with a patient's record, taking approximately 180 seconds. All subsequent visits will require a quick read of the ID token to pull the patient's record from your EHR system, ultimately saving time and increasing accuracy.
AIMe greatly reduces the time required to on board a patient by automating the locating and retrieval of the patient's record. 180 seconds is necessary for the patient's first visit to ensure the correct record is tied to their ID token. After the first visit, all following visits can take full advantage of the saved time brought about by using the patient's ID token.
Yes, AIMe integrates with the EHR in order to automatically invoke the patient's medical record when a ID token is read. The solution works with any EHR due to the simplicity of the integration, and since AIMe has already interfaced with multiple EHR vendors, the automation is already prepared and ready for implementation.
AIMe connects directly with your EHR though the LifeMed ID cloud.
Once an ID token is presented by the patient and scanned or inserted to be read, the process of invoking the patient’s medical record happens in a matter of seconds.
There are no privacy or security concerns with utilizing AIMe. Our product facilitates HIPAA compliance. Only subscribers to AIMe are able to access the solution, keeping patient information secure and away from unwanted viewers. On the patient's end, there is no worry to be had over the theft or loss of an ID as no patient information is stored on it.
Identity, Address, and Insurance validation is achieved through use of AIMe's Verification Services. AIMe facilitates verification services through trusted 3rd party vendors that meets Federal Identity Credential and Access Management (FICAM) standards.
Directly in the AIMe application, registrars are capable of completing insurance verification to confirm if the account is active and, in addition, provides visibility to the patient's co-pay and deductible information.
AIMe maintains a uni-directional connection with your EHR to display patient information for the issuance of an ID token, so if there is no information in the EHR, then nothing will be displayed in AIMe.
If a discrepancy in information is found, for example, if a patient has moved, or their birthdate has been entered incorrectly, the registrar can easily correct this information by returning to their EHR system in use and editing the information. Once the correction has been made, however, the registrar must re-invoke the patient's AIMe record to see the reflected change(s).
Yes. When enrolling, the patient's correct medical record will be linked to AIMe and upon every return the same record will be utilized going forward. This prevents the creation and use of duplicate, mismatched and overlay records.
AIMe achieves interoperability by enabling a patient to have their identity associated with different unique records within a network, and use one ID token to invoke their medical record at each location. This removes the redundant completion of forms by the patient within a network just for them to be registered.
Once implemented, AIMe solution not require any more customization or modification in order to prepare it for continual expansion within your network.
By utilizing the Registration Patient Management (RPM) Dashboard, all activity performed within AIMe can be tracked, viewed, and analyzed. The RPM tool is a click-through display of data that showcases important operational information, such as the number of patient visits utilizing an ID token, and types of transactions that occur at the healthcare facility through the use of AIMe.
Yes. When enrolling, the patient's correct medical record will be linked to AIMe and upon every return the same record will be utilized going forward. This prevents the creation and use of duplicate, mismatched and overlay records.
While AIMe is user-friendly, registration staff will need to complete training to best understand how to utilize the solution and to properly issue an ID token. It is our goal to make sure all of the registrars are trained and educated on how their role is vital to the success of properly managing patient identity and its impact on the patient experience.
