Extension of user interface based software integration to near real time and single sign on
View Patent ↗A browser extension will provide an electronic health record (EHR) user with access to a button that can be clicked to launch a third-party application from the health information technology (IT) vendor. By clicking the button, the EHR user is able to directly log into the health vendor's third-party application without a need for entering credentials and also the EHR user logs into the same patient context as the patient the EHR user is accessing in the EHR system.
1 . A method of single sign-on using a browser extension application comprising:
receiving an activation event on an identity provider controlled browser extension application graphical user interface element rendered by a browser on a predetermined page on an electronic health record (EHR) web site with patient information and logged-in EHR user information;
sending the patient information and logged-in EHR user information captured from the predetermined EHR in response to the activation event to a health information technology vendor;
sending from the health information technology vendor system a successful response to an identity provider system associated with the identity provider controlled browser extension application;
sending from the identity provider system to the identity provider controlled browser extension application a Security Assertion Markup Language (SAML) authentication assertion and attribute assertion;
relaying, by the identity provider controlled browser extension application executing within the browser, the SAML authentication assertion and the attribute assertion to the health information technology vendor system; and
responding from the health information technology vendor system with requested resources.
2 . The method of claim 1 , wherein the EHR web site has a document object model (DOM) and associated scripts that control how the identity provider controlled browser extension application graphical user interface element operates.
3 . The method of claim 1 , wherein the identity provider controlled browser extension application includes javascripts that are used in the operation of the identity provider browser extension application graphical user interface element.
4 . The method of claim 1 , wherein the identity provider controlled browser extension application interacts with application programming interfaces (APIs) in the case of granted privileges to obtain the same rights as a browser.
5 . The method of claim 1 , wherein the identity provider controlled browser extension application includes a collection of files which are packaged for distribution and installation.
6 . The method of claim 1 , wherein the identity provider controlled browser extension application includes a file that declares the extensions name and permissions.
7 . The method of claim 1 , wherein the identity provider controlled browser extension application includes a background script that runs inside the browser and can access information such as web requests.
8 . The method of claim 1 , wherein the identity provider controlled browser extension application includes a content script that runs inside pages that an EHR user loads and can communicate with background scripts.
9 . The method of claim 1 , wherein the identity provider controlled browser extension application includes a popup which is opened with a toolbar button that includes of a web page loaded in the popup.
10 . The method of claim 1 , wherein the identity provider controlled browser extension application includes metadata including name, version, permissions it requires, and pointers to other files in the identity provider controlled browser extension application.
11 . The method of claim 1 , wherein the identity provider controlled browser extension application includes pointers to several other types of files including background pages which implement long-running logic icons for the identity provider controlled browser extension application.
12 . The method of claim 1 , wherein the identity provider controlled browser extension application enables detection of data change in a source area and an automatic login to an EHR system to move the data in real time.
13 . The method of claim 1 , where if there is no corresponding information for either the patient information or the logged-in EHR user information recognized by the health information technology vendor system, then creating either the patient information or the logged-in EHR user information in the health information technology vendor system before responding from the health information technology vendor system with requested resources.
14 . A method of single sign-on using an identity provider controlled browser extension application comprising:
receiving an activation event on an identity provider controlled browser extension application graphical user interface element rendered by a browser on a predetermined page on an electronic health record (EHR) web site that is concurrently displaying patient information and logged-in EHR user information;
sending the patient information and logged-in EHR user information captured from the predetermined EHR page in response to the activation event to a health information technology vendor system;
sending from the health information technology vendor system a successful response to an identity provider system associated with the identity provider controlled browser extension application;
sending from the identity provider system to the identity provider controlled browser extension application a Security Assertion Markup Language (SAML) authentication assertion and attribute assertion to the identity provider browser extension application graphical user interface element, wherein the SAML authentication assertion and attribute assertion are generated after receipt of the patient information;
relaying, by the identity provider controlled browser extension application executing within the browser, the SAML authentication assertion and the attribute assertion to the health information technology vendor system; and
responding from the health information technology vendor system with requested resources.
15 . A method of single sign-on using an identity provider controlled browser extension application comprising:
receiving an activation event on an identity provider controlled browser extension application graphical user interface element rendered by a browser on a predetermined page on an electronic health record (EHR) web site that is concurrently displaying patient information and logged-in EHR user information;
sending the patient information and logged-in EHR user information captured from the predetermined EHR page in response to the activation event to a health information technology vendor system, wherein the predetermined page is a non-login, patient-record page of the EHR system;
sending from the health information technology vendor system a successful response to an identity provider system associated with the identity provider controlled browser extension application, the identity provider controlled browser extension application being external to the EHR system;
sending from the identity provider system directly to the identity provider controlled browser extension application a Security Assertion Markup Language (SAML) authentication assertion and attribute assertion to the identity provider browser extension application graphical user interface element;
relaying, by the identity provider controlled browser extension application executing within the browser, the SAML authentication assertion and the attribute assertion to the health information technology vendor system without the EHR system participating; and
responding from the health information technology vendor system with requested resources.