Patent Description:
<CIT> describes a method for providing a user interface for user specified context, which provides a collection of user interface cards based on a user's context and receiving a user's selection of a plurality of user interface cards from the collection of user interface cards.

<CIT> describes a client-server infrastructure capable of supporting a variety of asynchronous and synchronous collaboration activities in a so-called collaboration place, which include chatting, viewing and/or editing one or more data files, and/or displays.

<CIT> describes an online collaboration system comprising at least one server in communication with multiple client computing devices over a communication network, in which the at least one server executes a program to facilitate an online meeting between the users of the client computing devices in the online collaboration environment.

<CIT> describes techniques to manage a whiteboard for multimedia conference events, which allow multiple participants to communicate and share different types of media contents in a collaborative and real-time meeting over a network.

The application relates to systems that allow for communications between group members and, more particularly, to electronic systems that allow for those communications, especially within work environments, such as hospitals.

Advantageous embodiments are described in the dependent claims, the following description and the drawings.

The present invention may be thought of as a digital learning board with a display that is sub-divided into multiple display fields. The digital learning board is also configured to receive input from other electronic devices so that multiple users can collaborate using their devices to access, add to, and edit information from the digital learning board.

Additional features and advantages of the present invention are described in, and will be apparent from, the detailed description of the presently preferred embodiments and from the drawings.

Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, with emphasis instead being placed upon clearly illustrating the principles of the disclosure. Reference numerals designate corresponding parts throughout the several views.

The disclosure set forth above may encompass multiple distinct inventions with independent utility. Although each of these inventions has been disclosed in its preferred form(s), the specific embodiments thereof as disclosed and illustrated herein are not to be considered in a limiting sense, because numerous variations are possible. The subject matter of the inventions includes all novel and nonobvious combinations and subcombinations of the various elements, features, functions, and/or properties disclosed herein. The following claims particularly point out certain combinations and subcombinations regarded as novel and nonobvious. Inventions embodied in other combinations and subcombinations of features, functions, elements, and/or properties may be claimed in applications claiming priority from this or a related application. Such claims, whether directed to a different invention or to the same invention, and whether broader, narrower, equal, or different in scope to the original claims, also are regarded as included within the subject matter of the inventions of the present disclosure.

Now referring to <FIG> that illustrates a system <NUM> for the working of the invention, in accordance with an aspect of the invention. The system <NUM> includes a display module <NUM>, a local input module <NUM>, a processor <NUM> and a plural input modules 114A-114F (collectively referred to as input modules <NUM>) coupled to each other via a network <NUM>.

The display module <NUM> may further include multiple display areas 102A, 102B, or 102C. Different display areas may be configured to display different information. For e.g. 102A may display "New identified Issues" whereas 102B may display "Resolved Issues" and 102C may display "Pending Issues". It may be appreciated by a person having ordinary skill in the art that the display <NUM> may be divided into further display areas or more than three display areas. The display <NUM> may be a Light emitting diode display(LED), a liquid crystal display (LCD), a plasma display, an Organic Light Emitting display(OLED), an Active Matrix Organic Light Emitting Display (AMOLED), or a cathode ray tube (CRT) display. The display module <NUM> may be made up of a single display board or multiple display boards may be combined together to make one single display.

The local input module <NUM> may be a keyboard, a stylus, a mouse or a touch screen interface, etc. the local input module may help the local users 104A-104C, those present within the vicinity of the display module <NUM>, to enter or input information and access the information on display to just read the information.

The processor <NUM> may comprise at least one data processor for executing program components for executing user- or system-generated requests. The processor <NUM> may include a microprocessor, embedded or secure processors.

The network <NUM> may be a wired or a wireless network. The network <NUM> may be Local Area Network (LAN) that may be implemented using a TCP/IP network and may implement voice or multimedia over Internet Protocol (IP) using a Session Initiation Protocol (SIP). The processor <NUM> may be coupled to the display module <NUM> and the plural input modules <NUM> through a network interface module (not shown in figure). The network interface may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair <NUM>/<NUM>/<NUM> Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE <NUM>. 11a/b/g/n/ac/x, etc. The communication network <NUM> may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface and the communication network <NUM>, the processor <NUM> may communicate with the input modules <NUM>. These input modules <NUM> may include, without limitation, personal computer(s), smart watches, tablet computer, desktop PCs, head mounted wearables, and various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Android-based phones, etc.) or the like. Each of the input modules <NUM> corresponds to at least one of plural remote users 112A-112F (collectively referred to as remote user <NUM>).

In some embodiments, the processor <NUM> may be disposed in communication with one or more memory devices (not shown in figure) via a storage interface (also not shown in figure). The storage interface may connect to memory devices including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-<NUM>, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc..

The processor <NUM>, receives inputs from the connected input modules <NUM>. As described above, each of the input module corresponds to each of the users <NUM>. Users may have various defined accessibility roles. Some users may have read access, some may have write access, and some may have both read and write access. The users <NUM> logon using their respective input modules <NUM>. The users may add information through their respective input modules <NUM>. This information, when received by the processor <NUM> through the network <NUM>, analyzes the information and processes it to be displayed on the display module <NUM> on any of the display areas 102A, 102B, and 102C. The local users 104A, 104B, and 104C (collectively referred to as remote users <NUM>) are those users who may be present at the vicinity of the display module <NUM>. They may cumulatively logon to the system <NUM> using remote input module <NUM>. Any information added by any type of user, be it local users <NUM> or remote users <NUM>, is analyzed and processed by the processor <NUM> to be displayed on designated display areas 102A, 102B, and 102C.

The processor decides display areas based on the context of the information received or input received from the users <NUM>, and <NUM>. Also, the processor <NUM> enables usage of various collaborative tools like conference calls including audio and video conference calls, document sharing, document editing, document collaborating, etc. By way of an example the local users <NUM> who may be present near the display module <NUM> are able to collaborate or have a team huddle with the remote users <NUM>. The remote users <NUM> thus may attend or collaborate in every team meeting or documents. Also, the remote users <NUM> and the local users <NUM> may be part of same team and may work together, even when not being present physically together, to identify key issues, problems, news, techniques etc..

Now referring to <FIG> illustrating various modules of the processor <NUM>, in accordance with an aspect of the invention. The processor <NUM> helps in collaboration of remote users <NUM> and local users <NUM> in the learning system <NUM>. The processor <NUM> includes a connection engine <NUM>, an authentication engine <NUM>, a collaboration engine <NUM>, and a display engine <NUM>.

The connection engine <NUM>, acts as a network interface and helps in connecting to the network <NUM>. The connection engine may be either a microprocessor or a combination of multiple processors. Microprocessors may be either hardware or software compilations.

The authentication engine <NUM>, connected to the connection engine <NUM>, helps in identification and authentication of user logging in. The authentication engine <NUM> helps to keep a check on user access of the system <NUM>. The authentication engine <NUM> may be coupled to a memory or a database to store the authentication details and verify the same. Also, the database may include information like which user may be provided what kind of access. The access level may be based on user hierarchy, seniority, user type etc. The access may be read access, write access or a combination of both.

The collaboration engine <NUM> helps users <NUM> and <NUM> to collaborate with each other. The collaboration engine <NUM> may include a document sharing engine <NUM>, a calendar engine <NUM>, a conference engine <NUM> and an email engine <NUM>.

The document sharing engine <NUM> helps users to share and collaborate on various documents. The documents may be text files, images, videos, presentations spreadsheets, etc. the document sharing engine <NUM> helps in identifying user who edits or accesses the document supported by time stamp of when the document was used. In this manner, the document sharing engine <NUM> is configured to trace back to a user who makes changes or uses it and when.

Also, in case a user wrongly accesses a document, the document sharing engine may stop the user by providing a warning to the user on his respective device. For this functionality, the document sharing engine <NUM> may be connected to the memory to access the document sharing permissions etc. In an implementation, the documents sharing engine may have its own cache memory for the same functioning. Sharing of documents may be done by providing access through either user IDs of the users or email addresses. Further, the documents sharing engine <NUM> may have another setting of sharing a particular document with all users that is keep the document public. Documents shared may also include report of errors, or single error reported.

The calendar engine <NUM>, provides meeting possibilities to users <NUM> and <NUM>. The calendar engine collaborates calendars of all users <NUM> and <NUM> and may initiate meeting sessions based on events found. The events may be calendar invites or calendar events received for a specific time and date. User who wants to have a meeting may send in calendar invites to other user desired on the meeting. When these users accept the invites, the events are added on the respective user's device calendar. When meeting time approaches, user is intimated about the same. In other implementation, the meeting may automatically start on specific time or in some buffer time.

The conference engine <NUM> helps users <NUM> and <NUM> to have conference calls. The conference calls may be either audio calls, video calls or a combination thereof. Conference calls may be made by inviting participants using their email IDs or user IDs. The email engine <NUM> may also help users <NUM> and <NUM> to have meetings initiated. It works similar to the calendar engine <NUM>. The email engine <NUM> may be able to automatically pick up meeting request from mails received by a user. this may be done using a semantic analysis. Also, when a user sends a meeting invite, the email engine may automatically create a meeting event. Also, the email agent <NUM> may be able to send reminders to invited users before the meeting event happens.

The display engine <NUM> is responsible for displaying the right content at the right place at the right time. The display engine is coupled with the authentication engine <NUM>. The display engine receives data from users <NUM> and <NUM> after being authenticated and displays the same at right place on the display module <NUM>. The display engine <NUM> may include a sorting engine <NUM>, a placing engine <NUM> and a highlighting engine <NUM>.

The sorting engine <NUM> helps in sorting data received as per the content written. For example, the data from a user about an error is sorted out to be an error information. Hence, it may be tagged as an error information and sorted out to be placed on specific area "Issues identified" 102A. This may be done using a semantic analysis by the sorting engine <NUM>.

The placing engine <NUM> decides positioning of the information received, as per the tag of the information sorted by the sorting engine <NUM>. The placing engine <NUM> then may also display name of user adding information and time of the information received. For placing of the information, the placing engine <NUM>, may maintain a repository of tags and their placing on the display module <NUM>, based on which placing of the text is performed.

The highlighting engine <NUM> may be used by a user to highlight a certain severe pending issue or a rectified issue. Various types of highlighting colors may be used to convey different information. The highlighting engine <NUM> may have this functionality specially to help users having read access only. In this manner, users with only read access may be able to convey information without editing the same.

Now referring to <FIG>, various user interfaces at various steps and levels of information are illustrated, in accordance with an aspect of the invention. <FIG> depicts a user interface <NUM> after the user logs on to the system <NUM>. The user interface <NUM> is similar to the display module <NUM> and will be referred interchangeably. The user interface <NUM> may depict a first landing page after the user logs in. The user interface <NUM> may include a menu input <NUM>. The menu input <NUM> may be used by a user to access various functions of the user interface <NUM>. The user interface <NUM> may also include a search input tab <NUM>. The search tab <NUM> may be utilized to search for various information like issues pending etc. Furthermore, the user interface may utilize a help tab <NUM>. The help tab <NUM> may be utilized to help a user or provide to the user various information about the user interface <NUM>.

Furthermore, the user interface <NUM> may include a dashboard <NUM> that may be further divided into multiple information areas to display multiple types of information. The user interface <NUM> may include a general information area <NUM>, an aims area <NUM>, and issues area <NUM>. The general information area <NUM> provides general important information like "A message from the CEO", or "operational status of a new wing" etc. This information may generally be information to public at large and not for some specific users. The aims area <NUM> helps providing information to users about specific aims that their organization is working towards. It may involve information about decreasing a particular type of a problem faced by users, and may get updated regularly or in real-time. The issues area <NUM> may contain information about new issues identified, in progress resolution of issues and also completely rectified issues.

The user interface <NUM>, may also include an information input area <NUM> wherein a user may enter information of interest or use. For e.g., a user may input information about issues being faced in a process etc. which, after sorting by the sorting engine <NUM>, may display it in the issues section <NUM>. The user interface may also include a tab to collaborate for e.g. <NUM> as a Google hangout tab. User can simply click on the tab <NUM> to initiate a meeting with the users invited or a general meeting with all users.

Now referring to <FIG>, there is shown second level information that is available to users accessing the general information area <NUM>. A user may be able to access more information when he touches the messages on the general information area <NUM>. For e.g., a user may touch a message <NUM> i.e. "A message from the CEO", or message <NUM> i.e. "Operational status" to see more information about the same. The messages may open a pop-up window or a completely different window <NUM> and <NUM> respectively, to display additional information.

Similarly, as depicted in <FIG>, the user may touch the issues identified at <NUM>. This input from the user may provide a new sub-user interface <NUM>. The sub-user interface <NUM> may have further bifurcation of display area into multiple parts displaying New issues identified <NUM>, In progress issues <NUM>, and Completed issues <NUM> areas. User may add a new issue or in progress issue or completed issue information through an information addition area <NUM> and hitting a submit button <NUM>. Further, the user may get into third level of information wherein, user going through the new issues identified area <NUM> may want to have more information about a message <NUM> as depicted in <FIG>. the user may give his/her input by touching the message <NUM> that may open a pop-up window <NUM> that may include an activity enter area <NUM> to add some notes about the message that may act as supporting information.

Referring to <FIG>, the user wanting to know about information in Aims area <NUM>, may provide their input by touching the area. This action may open up a new window <NUM> with a description of Aims area <NUM>.

Referring to <FIG>, a user interface <NUM>, is provided on a user device <NUM> having a display frame <NUM> and a display unit <NUM>. The user interface <NUM> may be accessed using a software application <NUM> provided on the user device <NUM>. The software application may be initiated by user's touch input. After this input, the software application may display an authentication interface or login interface having a username field <NUM> and a password field <NUM>. User may also be able to login using his other authentication details like fingerprint, or biometric scan or voice prints etc. After successful log in, user is displayed with the user interface <NUM> that may include multiple information display areas <NUM>, <NUM> and <NUM>.

<FIG> illustrates a method <NUM> for learning in accordance with another aspect of the invention. At step <NUM>, the processor <NUM>, receives inputs from the input modules <NUM> corresponding to the plural users <NUM>. As described, the input modules <NUM> may have the software application <NUM> which when activated by a user may authenticate the user by requesting the user of his username and password. The user may then input information which when received by the processor <NUM> is processed. The processing includes semantic analysis, and further analysis as to which part of the display module <NUM> should the information be displayed on is performed. Further, at step <NUM>, the processed data is then displayed in the relevant part of the display module <NUM>.

<FIG> illustrates a method <NUM> in accordance with another aspect of the invention. At step <NUM>, user may initiate the application for connecting his input module to the display module <NUM>. The application may be a software application embedded into the Operating Software or may be downloaded and installed via an application store. The application when initiated, at step <NUM>, provides an authentication interface to the user. The user may enter his log in credentials to log in. Log in may be through a username password, or other log in credentials like fingerprint, biometric scans etc. At step <NUM>, the processor <NUM> checks the log in credentials and verifies it from the memory or database. After successful login, at step <NUM>, the processor receives input from the user and identifies the information being input. Further, at step <NUM>, the processor sorts the data based on the context of the information added. The context may be extracted using semantic analysis. Further, at step <NUM>, as per the sorted data, specific area of the display module <NUM> is identified wherein the data is to be displayed.

<FIG> illustrates an exemplary computer system <NUM> for implementing various embodiments of the invention. Computer system <NUM> may comprise a central processing unit ("CPU" or "processor") <NUM>. Processor <NUM> may comprise at least one data processor for executing program components for executing user- or system-generated requests. A user may include a person, a person using a device such as such as those included in this disclosure, or such a device itself. Processor <NUM> may include specialized processing units such as integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc. Processor <NUM> may include a microprocessor, such as AMD Athlon or Sempron, Duron or Opteron, ARM's application, embedded or secure processors, IBM PowerPC, Intel's Core, Itanium, Xeon, Celeron or other line of processors, etc. Processor <NUM> may be implemented using mainframe, distributed processor, multi-core, parallel, grid, or other architectures. Some embodiments may utilize embedded technologies like application-specific integrated circuits (ASICs), digital signal processors (DSPs), Field Programmable Gate Arrays (FPGAs), etc..

Processor <NUM> may be disposed in communication with one or more input/output (I/O) devices via an I/O interface <NUM>. I/O interface <NUM> may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE-<NUM>, serial bus, universal serial bus (USB), infrared, PS/<NUM>, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE <NUM> a/b/g/n/ac/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), highspeed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc..

Using I/O interface <NUM>, computer system <NUM> may communicate with one or more I/O devices. For example, an input device <NUM> may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, sensor (e.g., accelerometer, light sensor, GPS, gyroscope, proximity sensor, or the like), stylus, scanner, storage device, transceiver, video device/source, visors, etc. An output device <NUM> may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, or the like), audio speaker, etc. In some embodiments, a transceiver <NUM> may be coupled to processor <NUM>. Transceiver <NUM> may facilitate various types of wireless transmission or reception. For example, transceiver <NUM> may include an antenna operatively connected to a transceiver chip (e.g., Texas Instruments WiLink WL1283, Broadcom BCM4760IUB8, Infineon Technologies X-Gold <NUM>-PMB9800, or the like), providing IEEE <NUM>. 11a/b/g/n/ac/x, Bluetooth, FM, global positioning system (GPS), <NUM>/<NUM> HSDPA/HSUPA communications, etc..

In some embodiments, processor <NUM> may be disposed in communication with a communication network <NUM> via a network interface <NUM>. Network interface <NUM> may communicate with communication network <NUM>. Network interface <NUM> may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair <NUM>/<NUM>/<NUM> Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE <NUM>. 11a/b/g/n/ac/x, etc. Communication network <NUM> may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using network interface <NUM> and communication network <NUM>, computer system <NUM> may communicate with devices <NUM>, <NUM>, and <NUM>. These devices may include, without limitation, personal computer(s), server(s), fax machines, printers, scanners, various mobile devices such as cellular telephones, smartphones (e.g., Apple iPhone, Android-based phones, etc.), tablet computers, eBook readers (Amazon Kindle, Nook, etc.), laptop computers, notebooks, gaming consoles (Microsoft Xbox, Nintendo DS, Sony PlayStation, etc.), or the like. In some embodiments, the computer system <NUM> may itself embody one or more of these devices.

In some embodiments, processor <NUM> may be disposed in communication with one or more memory devices (e.g., a RAM <NUM>, a ROM <NUM>, etc.) via a storage interface <NUM>. Storage interface <NUM> may connect to memory devices <NUM> including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), integrated drive electronics (IDE), IEEE-<NUM>, universal serial bus (USB), fiber channel, small computer systems interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, redundant array of independent discs (RAID), solid-state memory devices, solid-state drives, etc..

Memory devices <NUM> may store a collection of program or database components, including, without limitation, an operating system <NUM>, a user interface application <NUM>, a web browser <NUM>, a mail server <NUM>, a mail client <NUM>, a user/application data <NUM> (e.g., any data variables or data records discussed in this disclosure), etc. Operating system <NUM> may facilitate resource management and operation of computer system <NUM>. Examples of operating system <NUM> include, without limitation, Apple Macintosh OS X, Unix, Unix-like system distributions (e.g., Berkeley Software Distribution (BSD), FreeBSD, NetBSD, OpenBSD, etc.), Linux distributions (e.g., Red Hat, Ubuntu, Kubuntu, etc.), IBM OS/<NUM>, Microsoft Windows (XP, Vista/<NUM>/<NUM>/<NUM>, etc.), Apple iOS, Google Android, or the like.

User interface <NUM> may facilitate display, execution, interaction, manipulation, or operation of program components through textual or graphical facilities. For example, user interfaces may provide computer interaction interface elements on a display system operatively connected to computer system <NUM>, such as cursors, icons, check boxes, menus, scrollers, windows, widgets, etc. Graphical user interfaces (GUIs) may be employed, including, without limitation, Apple Macintosh operating systems' Aqua, IBM OS/<NUM>, Microsoft Windows (e.g., Aero, Metro, etc.), Unix X-Windows, web interface libraries (e.g., ActiveX, Java, Javascript, AJAX, HTML, Adobe Flash, etc.), or the like.

In some embodiments, computer system <NUM> may implement web browser <NUM> stored program component. Web browser <NUM> may be a hypertext viewing application, such as Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, Apple Safari, etc. Secure web browsing may be provided using HTTPS (secure hypertext transport protocol), secure sockets layer (SSL), Transport Layer Security (TLS), etc. Web browsers may utilize facilities such as AJAX, DHTML, Adobe Flash, JavaScript, Java, application programming interfaces (APIs), etc. In some embodiments, computer system <NUM> may implement mail server <NUM> stored program component. Mail server <NUM> may be an Internet mail server such as Microsoft Exchange, or the like. Mail server <NUM> may utilize facilities such as ASP, ActiveX, ANSI C++/C#, Microsoft. NET, CGI scripts, Java, JavaScript, PERL, PHP, Python, WebObjects, etc. Mail server <NUM> may utilize communication protocols such as internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), or the like. In some embodiments, computer system <NUM> may implement mail client <NUM> stored program component. Mail client <NUM> may be a mail viewing application, such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Mozilla Thunderbird, etc..

The above description has described embodiments of the invention with different functional units and processors. However, any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. References to specific functional units are only intended as examples of suitable means or mechanisms for providing the described functionality, rather than being indicative of a strict logical or physical structure or organization.

Various embodiments of the invention provide systems and methods for enabling effective communications among several groups within an organization. One exemplary organization is a hospital, and using the system and method of the invention in that setting enables effective communication among various groups of healthcare service providers and administrators. The above described method enables generation of a personalized and contextual summary of a multimedia communication session that may also be thought of as a conference session or a webinar. The summary is generated based on individual needs, topics, roles, or participants by dynamically generating relevant meta-data along with content time stamp by using a semantic analyzer and a voice analyzer.

The specification has also described systems and methods for building contextual highlights for conferencing or communication systems. The illustrated steps are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development may change how particular functions are performed. Such alternatives fall within the scope and spirit of the disclosed embodiments.

Claim 1:
A healthcare environment communication system for communication between plural remote users of the healthcare environment , comprising;
a memory;
a network;
a display device configured to display information in a plurality of designated information areas;
user interface devices connected to the network, each including an input interface configured to obtain user inputs from individuals, including issues information about rendering services to patients in a healthcare facility; and
a processor, connected to the user interface devices via the network and to the display device, configured to process the user inputs in real-time and enable the users to collaborate, by the processor being configured to
maintain in the memory a repository comprising a plurality of tags, each of the plurality of tags corresponding to a respective one of a plurality of designated information areas;
receive the user inputs,
identify issues information by adding tags to the user inputs, including semantically analyzing the issues information input by each of the users to identify one of the plurality of designated information areas to which the issues information relates, and adding one of the plurality of tags to the issues information input by each of the users based on the tag that corresponds to the identified one of the plurality of designated information areas to which the issues information relates,
compile and organize the user inputs, including sort the user inputs by the tag added to the issues information input by each of the users, and
output the issues information input by each of the users to the display device in different ones of the plurality of designated information areas depending upon the tag added to the issues information input by each of the users.