A healthcare integration device comprising: a processor; and a non-volatile memory coupled to the processor, the non-volatile memory storing instructions executable by the processor to provide one or more applications; wherein the processor is configured by the instructions to: operate a host application locally on the healthcare integration device; and operate a first healthcare application through a web-browser application operating on the healthcare integration device; and operate a second healthcare application locally on the healthcare integration device and outside the web-browser application environment; wherein the host application is launchable on-demand from both the first healthcare application and from the second healthcare application, the host application being launchable in response to determining, by the first healthcare application or the second healthcare application, that communication is to be provided between the first healthcare application and the second healthcare application, the host application is configured to generate, after being launched, a local communication server on the healthcare integration device, wherein the local communication server is uninstantiated prior to being generated by the host application; the host application operates outside the web-browser application environment; the host application defines a host application domain for the local communication server; and the local communication server enables two-way communication between the first healthcare application and the second healthcare application, wherein the two-way communication occurs directly on the healthcare integration device and wherein the first healthcare application includes a host reference that identifies the host application domain of the local communication server, wherein the host reference is defined in the code of the first healthcare application. a processor; and a non-volatile memory coupled to the processor, the non-volatile memory storing instructions executable by the processor to provide one or more applications; wherein the processor is configured by the instructions to: operate a host application locally on the healthcare integration device; and operate a first healthcare application through a web-browser application operating on the healthcare integration device; and operate a second healthcare application locally on the healthcare integration device and outside the web-browser application environment; wherein the host application is launchable on-demand from both the first healthcare application and from the second healthcare application, the host application being launchable in response to determining, by the first healthcare application or the second healthcare application, that communication is to be provided between the first healthcare application and the second healthcare application, the host application is configured to generate, after being launched, a local communication server on the healthcare integration device, wherein the local communication server is uninstantiated prior to being generated by the host application; the host application operates outside the web-browser application environment; the host application defines a host application domain for the local communication server; and the local communication server enables two-way communication between the first healthcare application and the second healthcare application, wherein the two-way communication occurs directly on the healthcare integration device and wherein the first healthcare application includes a host reference that identifies the host application domain of the local communication server, wherein the host reference is defined in the code of the first healthcare application. operate a host application locally on the healthcare integration device; and operate a first healthcare application through a web-browser application operating on the healthcare integration device; and operate a second healthcare application locally on the healthcare integration device and outside the web-browser application environment; wherein the host application is launchable on-demand from both the first healthcare application and from the second healthcare application, the host application being launchable in response to determining, by the first healthcare application or the second healthcare application, that communication is to be provided between the first healthcare application and the second healthcare application, the host application is configured to generate, after being launched, a local communication server on the healthcare integration device, wherein the local communication server is uninstantiated prior to being generated by the host application; the host application operates outside the web-browser application environment; the host application defines a host application domain for the local communication server; and the local communication server enables two-way communication between the first healthcare application and the second healthcare application, wherein the two-way communication occurs directly on the healthcare integration device and wherein the first healthcare application includes a host reference that identifies the host application domain of the local communication server, wherein the host reference is defined in the code of the first healthcare application.