Dynamic loading of an extending application

A computer program product comprising a non-transitory computer readable medium retaining program instructions, which program instructions when read by a processor, cause the processor to:

• monitor and interact with a Document Object Model (DOM) of a page of an Electronic Health Record (EHR) system using a browser extension, wherein the browser extension is configured to be executed by a browser, wherein the browser is configured to render the page of the EHR system;
• dynamically load a runtime infrastructure in the page of the EHR system in a first iframe, wherein the runtime infrastructure lacks a Graphical User Interface (GUI) representation;
• dynamically load an EHR-specific EHR adapter in the page of the EHR system;
• and
• dynamically load an extending application in the page of the EHR system in a second iframe,
• wherein the browser extension is configured to inject the first iframe in the page of the EHR system and cause the runtime infrastructure to be loaded into the first iframe, wherein the browser extension is configured to inject the second iframe in the page of the EHR system and enable the runtime infrastructure to load the extending application into the second iframe,
• wherein the EHR-specific EHR adapter is specifically designed based on the EHR system, wherein the EHR-specific EHR adapter is configured to receive EHR-specific instructions from the browser extension and communicate converted cross-EHR instructions to the runtime infrastructure, wherein the runtime infrastructure is configured to communicate the converted cross-EHR instructions to the extending application, wherein the runtime infrastructure is configured to receive cross-EHR instructions from the extending application, wherein the EHR-specific EHR adapter is configured to obtain the cross-EHR instructions and communicate converted EHR-specific instructions to the browser extension,
• wherein said processor is configured to implement a functionality that is not provided by the EHR system at least by:
• monitoring, by the browser extension, for an event in the EHR system;
• notifying, by the browser extension, the EHR-specific EHR adapter of the event via an EHR-specific instruction;
• translating, by the EHR-specific EHR adapter, the EHR-specific instruction to a converted cross-EHR instruction that is provided to the extending application via the runtime infrastructure;
• executing, by the extending application, a cross-EHR business logic in response to the converted cross-EHR instruction to determine a cross-EHR response;
• and
• translating, by the EHR-specific EHR adapter, the cross-EHR response to a converted EHR-specific instruction that can be implemented by the browser extension over the EHR system.

A method comprising:

• monitoring and interacting with a Document Object Model (DOM) of a page of an Electronic Health Record (EHR) system using a browser extension, wherein the browser extension is configured to be executed by a browser, wherein the browser is configured to render the page of the EHR system;
• dynamically loading a runtime infrastructure in the page of the EHR system in a first iframe, wherein the runtime infrastructure lacks a Graphical User Interface (GUI) representation;
• dynamically loading an EHR-specific EHR adapter in the page of the EHR system;
• and
• dynamically loading an extending application in the page of the EHR system in a second iframe,
• wherein the browser extension is configured to inject the first iframe in the page of the EHR system and cause the runtime infrastructure to be loaded into the first iframe, wherein the browser extension is configured to inject the second iframe in the page of the EHR system and enable the runtime infrastructure to load the extending application into the second iframe,
• wherein the EHR-specific EHR adapter is specifically designed based on the EHR system, wherein the EHR-specific EHR adapter is configured to receive EHR-specific instructions from the browser extension and communicate converted cross-EHR instructions to the runtime infrastructure, wherein the runtime infrastructure is configured to communicate the converted cross-EHR instructions to the extending application, wherein the runtime infrastructure is configured to receive cross-EHR instructions from the extending application, wherein the EHR-specific EHR adapter is configured to obtain the cross-EHR instructions and communicate converted EHR-specific instructions to the browser extension,
• wherein a processor is configured to implement a functionality that is not provided by the EHR system at least by:
• monitoring, by the browser extension, for an event in the EHR system;
• notifying, by the browser extension, the EHR-specific EHR adapter of the event via an EHR-specific instruction;
• translating, by the EHR-specific EHR adapter, the EHR-specific instruction to a converted cross-EHR instruction that is provided to the extending application via the runtime infrastructure;
• executing, by the extending application, a cross-EHR business logic in response to the converted cross-EHR instruction to determine a cross-EHR response;
• and
• translating, by the EHR-specific EHR adapter, the cross-EHR response to a converted EHR-specific instruction that can be implemented by the browser extension over the EHR system.