The rationale is that always increasing CPU and memory power is usually unused on personal computers by web browsers. The task can be executed on a web server and the results (can be) sent back to a web browser, or the web browser can load data from the web server or from user input, and execute JavaScript code on the data. Web apps can be both thin and thick clients. The main differences are that the program code for web application resists on a web server, can be managed remotely for all the clients, and is executed by the web browser or web server rather than the operating system itself. They are not meant for sole presentation of web resources but aimed to accomplish some task and to provide similar user experience as in the native applications.

Web applications (web apps) are task-oriented web pages. JavaScript DICOM network library, DICOM to WebSocket proxy and a proof-of-concept web application that qualifies as a DICOM 3.0 device were developed. It presents a different approach of using HTML5 features of the web browsers through the JavaScript language and the WebSocket protocol by enabling real-time communication with DICOM repositories. This paper provides an overview of the current state of development of the web access technology to the DICOM repositories. The DICOM standard officials accepted those subsequently as tools of alternative access. Ever-increasing utilization of the web browsers, laptops and handheld devices, as opposed to desktop applications and static organizational computers, lead to development of different web technologies. The development of Internet and various communication media initiated demand for non-DICOM access to PACS systems. Digital imaging and communications in medicine (DICOM) 3.0 standard provides the baseline for the picture archiving and communication systems (PACS).

Osirix md server