<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A collaborative web-based Application for health care tasks planning</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fouzi Lezzar</string-name>
          <email>1Lezzar.fouzi@gmail.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Abdelmadjid Zidani</string-name>
          <email>2abdelmadjid.zidani@univ-batna.dz</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Atef Chorfi</string-name>
          <email>3Atefchorfi@yahoo.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Laboratoire de sciences et technologies de l'information et de la communication, University of Batna</institution>
          ,
          <country country="DZ">Algeria</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2012</year>
      </pub-date>
      <fpage>30</fpage>
      <lpage>39</lpage>
      <abstract>
        <p>Hospital emergency wards such as Gynaecology and obstetrics maternities are extremely complex to manage and pose serious health risks to patients. Related tasks which are mainly focused around patient management are basically achieved through a cooperative way that involves several health care professionals. Such team members with separate skills and roles should work together during patients' management. In this paper, we firstly discuss our study of work in-situ within an Algerian maternity ward to better understand the usual way under which tasks are effectively achieved and identify the artefacts used. Such observation allows us to highlight the vital collaborative medical tasks that need to be modelled. The following sections outline basic design concepts of our collaborative planning system, which is designed to provide a flexible group interaction support for care coordination and continuity.</p>
      </abstract>
      <kwd-group>
        <kwd>Healthcare tasks modelling</kwd>
        <kwd>cooperative work</kwd>
        <kwd>shared artefacts</kwd>
        <kwd>synchronous/asynchronous interaction</kwd>
        <kwd>social planning and coordination</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In Algeria, many healthcare institutions across the country suffer from multiple
dysfunctions. Despite the reforms initiated by the authorities to improve the quality and
effectiveness of patients care, the changes promised by the reforms initiators slow in
coming and health care wards still do not meet the expectations of the patients.
Certainly, no one can ignore the achievements made in this sensitive area that is public
health such as rehabilitation of old infrastructures and reception of new ones, opening
of new services, training of more physicians, medical specialists and skilled staff, etc.,
but problems persist and severely affect the medical activity and globally the health
system.</p>
      <p>It is here about an observation that cannot be restricted to the isolated counties
within the country like south for example, which use old medical equipment and lack
in terms of qualified personnel, but also concerns hospitals in major northern cities
which are nevertheless materially well equipped with the availability of the required
skills. Indeed, the study1 that we led on this vital question revealed various reasons
that are mainly linked to mismanagement of the related activities, equipment, human
and material resources.</p>
      <p>
        First, it is necessary to note that the artefacts used during work are essentially
restricted to paper sheets which are often not updated and sometimes even get lost
between the different services because of the infernal work load imposed on the
personnel .The observation study has also explicitly showed that most of the medical
activities we supervised were group-based. Likewise the main deficiencies in patients
monitoring precisely arose from the lack of coordination between the various members of
the involved medical team, which thus constitutes a key factor as it has been so well
confirmed several numerous studies carried out on this issue[
        <xref ref-type="bibr" rid="ref20">20</xref>
        ] [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ].
      </p>
      <p>
        Based on this observation, we believe that the task management should require
from us a special attention. We must therefore address the issue of the targeted
maternity ward under a new perspective, that of the medical staff needs, taking into account
the economic and performance constraints as well as socio-health hospitals mission
objectives of providing optimal care and well-being of patients. Providing a
technological answer through cooperation, coordination and communication facilities seems
to be the most appropriate initiative. However the past experiences reported in this
area that work in-situ [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] should be first carefully analyzed from a social point of
view [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], and through a structurally opened cooperation vision that enables users to
build their cooperation workspace structure in order to interact within it [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
Consequently, we focused our interest on collaborative practices of patient care teams [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]
as well as their organization [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] to better understand the usual manner with which
tasks are actually performed.
      </p>
      <p>
        Several collaborative medical care needs have been identified by a wide body of
researches in informatics and medical science fields. There are common processes
that are more difficult and complex in collaborative situations, because they need to
integrate many parties. Such as decision making process that needs involvement of
several persons to arrive to a decision, which can take long time [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] authors
showed that the collaborative nature of the executed process, determines the type of
information management necessary for this process [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Though, a poor structure of
information can lead to coordination and communication breakdowns [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>
        Maternity services are highly risky and still very hard to manage. They require
coordination among several teams whose tasks achievement most of the time confront
them to conflict situations [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].The exploitation of information and communication
technologies proves to be an effective approach if it is appropriately used [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. It will
enable us reduce the effects generated by the coordination problems that directly
disrupt the patient’s care chain and degrade their quality as noted Scupelli [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] through
his study. Consequently, coordination breakdowns among the medical staff members
inevitably that have an impact on the quality of care provided to patients and put them
in a potentially vulnerable and dangerous situations should be significantly reduced
with the availability of a medium of communication, cooperation, and coordination.
      </p>
      <p>
        1We led an investigation mainly based on observations and interviews with a medical staff within a
gynecology and obstetrics emergency unit.
Such an approach will provide collaborative tools that may effectively address
medical staff vital needs and improve the quality of patients’ care. Our research work falls
then within the CSCW area (Computer Supported Cooperative Work). Thus, with a
CSCW-based management strategy [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] we wish to provide an effective support of
these activities enabling by the way finer planning features of the related tasks as well
as providing real time mutual awareness around the occurring events within the
maternity unit which constitutes a priority of our work.
      </p>
      <p>The main objective of this paper is to outline basic design concepts of our
cooperative planning system CPlan. In the following sections we will first discuss our
observational study achieved within an Algerian maternity ward to better understand the
usual way under which tasks are effectively completed as well as identify the used
artefacts. We will attempt to analyze the healthcare process to highlight the
appropriate design guidelines. Section 3, exposes our conceptual methodology and discusses
the choices made as well as the software architecture designed for CPlan. We
consider the main components of the different architecture levels as well as the main
supported features. We will explicitly attempt to show that CPlan design is mainly
focused on concepts of data sharing and exchange to favour coordination between
participants. To provide details on our design approach, section4 discusses its
deployment issue. Finally, perspectives of the accomplished work are presented in the
conclusion of the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Targeted context study</title>
      <p>Our study of work in-situ led us to consider an Algerian maternity ward to better
understand the usual way under which medical staff such as
gynaecologistsobstetricians, anaesthetists, midwives, nurses, …, effectively achieve their tasks and
identify the main used artefacts to coordinate the work. The maternity targeted is
about 200 beds and comprises 4 operating rooms, 4 labour rooms, an analysis
laboratory, an imagery service, an emergency service, etc.</p>
      <p>We started, therefore, by analyzing the interactions among the medical staff
members and attempted to understand how they may interact and collaborate while dealing
with patients’ cases, and what happens when this work is done with a team of
collaborators. Such understanding will undoubtedly allow us to provide the adequate design
by addressing the following interrogations:
─ How medical staff members’ collaboration naturally takes place?
─ Which artefacts are used to coordinate work? And how?
─ Which impact has the spatiotemporal dimension on staff members’ interactions and
on the collaboration process among them?
─ What means are required to improve the care process within a maternity ward?
─ Which computer tools may provide the required assistance for the medical staff
members and get them to work collaboratively?
─ From a collaboration point of view, what are the specific characteristics of
collaborative medical activities?</p>
      <p>It is practically impossible to design a computer tool addressing all users’ needs.
Nevertheless, group work experiences provide us with pertinent information to clarify
some useful development ideas about the suitable support tools. The experimentation
of these tools, thereafter, will unveil obstacles to overcome as well as perspectives to
follow. Our approach is drawn in a direction which aims to favour collective work
and enables coordination. Therefore, as we will show it in the following sections, the
care tasks analysis will bring us an understanding to concretely increase the
commitment of participants that may have a great impact on the whole chain care process.
2.1</p>
      <sec id="sec-2-1">
        <title>Collaboration process</title>
        <p>The meticulous analysis of healthcare activities reveals that patient care chain
planning is a complex task that has an important impact on their quality and consequently
on patients’ safety. Such care process must be carefully managed since the patients’
admission to the hospital until they recover and leave it. This includes ongoing care
chain planning of a pregnant woman since her admission to the maternity until her
delivery that can occur naturally (labour room) or through a caesarean surgery
(operating room).</p>
        <p>When there is a coordination breakdown between team members, this can affect
directly the patients care activity. In this study we noticed that there are many sources
of coordination breakdowns, that have to be taken is consideration. A change in the
patient’s physical condition either for the worse or for the better can require a
changing in the schedule. For example if a doctor decides that a pregnant woman can need a
caesarean operation, this needs an immediate allocation of an operating room. Some
coordination problems can come from surgeons. Surgeons do not have often one
obligation, but many; such as carrying out a surgery, seeing their patients, or working in
other hospitals. When the amount of tasks is big, and there is a lack of awareness and
coordination; this can be a source of delays. A not experienced nurse, who is not
accustomed with the work in the maternity ward, can make some mistakes, what can
affect the schedule. Team members can affect and slow down each other, with
unexpected events and requests for information which require updating and adjustment in
the plan.</p>
        <p>When coordination breakdowns occur, schedule has to be adjusted: reallocations of
resources, update of priorities, notifying of the involved medical staff.... Negative
consequences can happen when the medical staff fails to act collaboratively to adjust
breakdowns. Our analysis has revealed that medical care is often administrated with a
delay, and unfortunately even for critical cases, what can be sometimes dangerous for
patients’ life. These coordination breakdowns, can lead to delays, what leads to more
work hours and additional costs what reduces profits. Also, trying to coordinate every
time between team members; can generate stress and workload. Sometimes delays
can oblige patients to come back another day, what disturbs their personal plans.</p>
        <p>Our study, reveals us that putting artefacts in some specific positions inside the
maternity ward can increase awareness, improve the collaboration process, reduce the
costs of sharing and gathering information and decrease coordination problems.</p>
        <p>The planning process should take into account for any task the availability of the
associated medical team members (such as gynaecologist-obstetrician, anaesthetist,
midwife, and nurse), the location, the period of time, etc. The collaborative planning
tool shows immediately the old scheduled tasks and easily allows planning new ones
while visualization provides for specific periods information on availability of current
working staff as well as locations (labour and operating rooms).
2.2</p>
      </sec>
      <sec id="sec-2-2">
        <title>Work analysis</title>
        <p>Designing group work support features requires first a better work in situ analysis,
and particularly identifying the implied participants, their roles, prerogatives as well
as the used artefacts. Such way will without doubt enable us to understand how to
satisfy both individual and group requirements within a shared environment.</p>
        <p>Our design approach is intended to enable medical staff members to cooperate and
share responsibility of a patient. We insist here on the necessity for an effective
groupware tool to take into account the procedural, intellectual and social complexity
of the cooperative care process planning. Indeed the diversity of opinions inside the
staff, often generate a great intellectual activity that should be gathered and made
available to the community rather than neglected until it becomes a source of conflicts
or misunderstandings.</p>
        <p>In addition to the obstetricians-gynaecologists, anaesthesiologist, paediatrician,
etc., the genecology unit functioning is mainly based on the chief midwife, who is in
charge of the care organization, of their quality and their ongoing as well as the
motherhood monitoring and her staff management (usually other midwives and assistant
nurses). Among the other professionals involved in the service we also distinguish the
anaesthetist nurse (a specialized nurse) who assists the anaesthesiologist and
supervises the postoperative recovery room. Finally, the staff also involves a social
assistant who mediates between patients meeting personal problems and administrative
agencies, a psychologist who offers listening, support and advice to patients and
families, a physiotherapist for functional rehabilitation and massage therapy, and a
nutritionist who tailors the appropriate diet to health problems.
2.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Used Artefacts</title>
        <p>During patients’ management, the involved team usually resorts for scheduling to a
classical plan board or paper sheets to specify who does what, and when? As well as
to coordinate the work with people who are not available, it is usual to use the
telephone, email and short messages. Such way to achieve work promotes creativity and
information sharing that suitably works and allows the group to get at an on-time
objective. Thus, the whole process requires from the team members to take part to the
planning process and do nothing else at this moment. Because the planning process
works well when under a face to face way, while the detailed tasks are discussed with
the whole team. However, because of their Ad-hoc nature and emergencies the
medical activities require not only continuous availability but also a high level of vigilance
from the medical staff which should constantly be focused on the evolution of
patients' conditions. Therefore, these meetings which are necessary to ensure
coordination should be minimized as much as possible. Just as it would be necessary to
constantly maintain mutual awareness on the occurring events, even for the busy group
members while dealing with emergencies. That is how coordination problems arise
and lead to the disruption of the balance within the group leading to tension,
nervousness, tiredness, anxiety, etc.</p>
        <p>
          The most used artefact as we said above is the paper medical record. It contains
much information about the patient (observations, plan of the day, and dosage of
drugs). There is a new paper each day that is placed on the top of the old ones. With
time, the consultant need more time to consult a patient state because of the big
number of papers added every day. The use of papers has to be reduced to minimum, to
avoid some problems such as lose of papers, the need to move to the patient’s room to
consult its state,... The use of electronic medical records (EMRs) can improve
awareness among the group members, and improve collaboration process [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. The use of
EMRs, must be coupled with the correct display device [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Because a poor
development of the ergonomic design can lead to a difficulty using [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ].
        </p>
        <p>Likewise, the strategy used by these institutions has often emphasized on a
management that attempts to deal with the massive affluence of patients rather than the
quality of their care. Furthermore, we currently see in the emergency service the
admission of more and more complex health cases, whose take-in-charge remains an
extremely hard task.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Software architecture</title>
      <p>
        The developed system is a synchronous web-based groupware accessible through a
browser that enables real-time collaboration among collocated or geographically
separated group members. The proposed architecture is illustrated on Figure 1. It is
developed under AJAX Push also known as Server Push or Comet [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>The first layer contains the system database which is mainly characterized by its
capacity to provide reliable data for long time, concurrency control management, data
storage, and security capabilities.</p>
      <p>The second layer contains all the defined software components. In the case of a
real-time groupware, sharing data and events constitutes the most important aspect.
Thus enabling data sharing requires that any event or data generated by one user has
to be immediately notified and delivered to all the other users (in real- time). For
better workspace awareness, fault tolerance, responsiveness, and replication of shared
data, objects are often used together with other operations on them like creation,
updating, deletion and reading.</p>
      <p>Some web 2.0 technologies such as AJAX and Comet, allow creation of rich
internet applications (RIAs). In an Ajax application, servers respond to each request in
sequence, just as in classical web, but in the browser only a part of the user interface
is updated, rather than updating the whole page and refresh the whole display.
However, the user must send a request to the server to see the updates.</p>
      <p>
        The problem of AJAX which is the absence of two-way communication that is
needed for synchronous groupware implementation is partially solved with a set of
technologies commonly called Comet. They allow a server to push data to the
browser (‘server push’) without requiring a new connection for each update. This
capability allows a server to notify data to clients at any moment. Comet is ideal for
collaborative and real time applications, because of its abilities for improving
responsiveness of collaborative systems, without causing any throughput problems [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ], authors carried out a study on groupware-based framework requirements to
assess the performance of different networking approaches including Comet. They
found that web-based networking approaches perform well and can support the
communication requirements of many types of real-time groupware. The results suggest
that web technologies can support a wide variety of network requirements, including
highly interactive shared workspaces and systems for large groups.
      </p>
      <p>
        The second layer defines two servers: Web-Server and Displaying-Server [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
The web server contains rich web pages that may be loaded on users’ browsers. The
Displaying Server is intended to display the schedule on eWhiteBoards (screens
disposed on the appropriate locations in the hospital). After every modification of the
schedule, all the eWhiteBoards are automatically updated. Also to significantly
reduce users’ cognitive overload such as nurses, surgeons…, the eWhiteBoard(s) can be
configured to restrict the display only for pertinent information needed by each group
[
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] and decrease the amount of data on screens.
      </p>
      <p>Finally, the third part consists of the client machines, which may be a laptop or a
desktop. However, recent years have seen a wide variety of computer devices
including mobile telephones, smartphones and tablets that can be considered as an
alternative for traditional computers.
3.1</p>
      <sec id="sec-3-1">
        <title>Software Architecture Components</title>
        <p>The following components are loaded in the browser from the Web Server. Our
architecture is composed of several modules which are important for the collaborative
scheduling task:
• Interface component: this module plays the role of a medium between the user and
the system.
• Session Manager: This component is intended to manage users’ work sessions, like
rights on the schedule list (read/write), users join/leave within the shared
workspace, latecomers...
• Collaboration: to allow users to simultaneously work together, we designed several
appropriate tools, such as the tasks shared table. Users share the same display
which instantly shows any event that may occur in consequence of a user action.
Such way provides users with real time awareness capabilities and enhances
coordination.
• Communication: CPlan supports both synchronous (instant messaging) and
asynchronous (post comments, and give valuable suggestions to their colleagues).
• Scheduling: This is the most important system component; it provides all the
necessary tools for managing resources and tasks. The list of the tasks is displayed to
the users in a table that showing all related tasks information (starting time,
priority, location…). Once a task is created, it will immediately appear on the other
participants (users) screens.
• Collaborative diagnostic: This is a component intended for diagnostics elaboration
of a given case under a collaborative way.</p>
        <p>The server extracts the required information from the database and uses an SMS
gateway to send messages to the staff members. There are two kinds of messages:
reminders, notifiers to notify new events or a new created task. To allow users to
connect to our web interface with their mobile devices, an adapted version of the web
application is developed. The developed system allows an authorized physician to
access at any location to the electronic patient record data, using a hand held device or
a desktop, and can for example remotely access the patient medical images.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Events notification</title>
        <p>
          Our system uses an event notification mechanism. When any action is executed
within the shared workspace [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], the web server notifies the other users to inform
them (XML messages) about the different actions in the shared workspace. Such
mechanism keeps the whole group member aware of their mutual actions [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ].
        </p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusions and perspectives</title>
      <p>To objectively measure the efficiency of CPlan, we have implemented a first
prototype of the collaborative tool, and the evaluation of the current version on a local
network brings rich ideas on collaboration and coordination opportunities provided.</p>
      <p>In this paper, we have discussed basic design concepts of our groupware
application CPlan. We have attempted to show that it allows several participants to
collaborate within a shared workspace. It allows the execution of individual and collective
actions on a common patient case as the elaboration of the planning. The sharing of
the planning scheduling has been widely discussed, because its use allows us to
concretely inform participants on their mutual actions. At the visual level, the simplified
and rich web interface shows explicitly the shared plan phases and significantly
reduces participants’ cognitive loads and enables them to intuitively understand what is
currently going on and get knowledge about their patients’ states evolution as well as
the next actions that should be achieved.</p>
      <p>During a work session, medical staff members may act on the shared plan under
specific role, dynamically exchange messages and interact through natural
cooperation way. Such flexibility is motivated by the necessity to enable CPlan to support the
dynamics implied by the care process.</p>
      <p>Being conscious of the great interest of CPlan experimentation in effective context
situations, we plan in the next step of our research work to collect information about
efficient activities from medical staff. It is of an extreme importance for us and
represents a double objective. First, we can validate or forsake some technical choices
among those we made for implementation. Second, we will be able to determine with
more precisions the appropriated adaptations we should apply to the supports
provided in CPlan. To this end such as any software project we designed modular and
extendable software architecture, in the sense that it allows design and integration of
new modules through an incremental way.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Craig</surname>
            ,
            <given-names>E. Kuziemsky.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>James</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Williams</surname>
          </string-name>
          .,
          <string-name>
            <surname>Jens</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <article-title>Weber-jahnke.: Towards Electronic Health Record Support for Collaborative Processes</article-title>
          .
          <source>SEHC '11 Proceedings of the 3rd Workshop on Software Engineering in Health Care</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Russell</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Comet: Low Latency Data for the Browser</article-title>
          .
          <source>Continuing Intermittent Incoherency</source>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Cecily</given-names>
            <surname>Morrison</surname>
          </string-name>
          .,
          <string-name>
            <given-names>Geraldine</given-names>
            <surname>Fitzpatrick</surname>
          </string-name>
          ., Alan Blackwell.
          <article-title>:Multi-disciplinary collaboration during ward rounds: Embodied aspects of electronic medical record usage</article-title>
          .
          <source>International Journal of Medical</source>
          Informatics Vol.
          <volume>80</volume>
          ,
          <string-name>
            <surname>Issue</surname>
            <given-names>8</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pages</surname>
          </string-name>
          e96-
          <fpage>e111</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>J.</given-names>
            <surname>Cummings</surname>
          </string-name>
          .,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kiesler</surname>
          </string-name>
          .:
          <article-title>Coordination and success in multidisciplinary scientific collaborations</article-title>
          .
          <source>International Conferenceon Information Systems (ICIS)</source>
          , Seattle, WA:
          <article-title>Association for Information Systems (</article-title>
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Wong</surname>
            ,
            <given-names>H.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Caesar</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bandali</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Agnew</surname>
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Abrams</surname>
            <given-names>H.</given-names>
          </string-name>
          :
          <article-title>Electronic inpatient whiteboards: improving multidisciplinary communication and coordination of care</article-title>
          .
          <source>Int J Med</source>
          Inform.;
          <volume>78</volume>
          (
          <issue>4</issue>
          ):
          <fpage>239</fpage>
          -
          <lpage>47</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>M.</given-names>
            <surname>Hertzum</surname>
          </string-name>
          .:
          <article-title>Electronic emergency-department whiteboards: A study of clinicians' expectations and</article-title>
          <string-name>
            <given-names>experiences. I. J.</given-names>
            <surname>Medical</surname>
          </string-name>
          <string-name>
            <surname>Informatics</surname>
          </string-name>
          , Vol.
          <volume>80</volume>
          , No.
          <issue>9</issue>
          , pp.
          <fpage>618</fpage>
          -
          <lpage>630</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>C.</given-names>
            <surname>Tang</surname>
          </string-name>
          ,
          <string-name>
            <surname>S. Carpendale.</surname>
          </string-name>
          ,
          <article-title>An observational study of information flow during nurses' shift change</article-title>
          ,
          <source>Proceedings of CHI</source>
          <year>2007</year>
          219-
          <fpage>228</fpage>
          . (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>K.</given-names>
            <surname>Schmidt.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Simone</surname>
          </string-name>
          .,:
          <article-title>Coordination mechanisms: Towards a conceptual foundation of CSCW systems design</article-title>
          .
          <source>Journal of Computer Supported Cooperative Work: The Journal of Collaborative Computing</source>
          ,
          <volume>5</volume>
          (
          <issue>2-3</issue>
          ),
          <fpage>155</fpage>
          -
          <lpage>200</lpage>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Dourish</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>What we talk about when we talk about context</article-title>
          .
          <source>Personal and Ubiquitous Computing</source>
          ,
          <volume>8</volume>
          (
          <issue>1</issue>
          ),
          <fpage>19</fpage>
          -
          <lpage>30</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Scupelli</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Xiao</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fussell</surname>
            ,
            <given-names>S. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kiesler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gross</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Supporting coordination in surgical suites: Physical aspects of common information spaces</article-title>
          .
          <source>Proceedings of the Conference on Human Factors in Computing Systems CHI10</source>
          , NY: ACM Press (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>Z.</given-names>
            <surname>Niazkhani.</surname>
          </string-name>
          , et al.:
          <article-title>Evaluating the medication process in the context of CPOE use: The significance of working around the system</article-title>
          ,
          <source>Int. J. Med</source>
          . Inform. (
          <year>2011</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Carl</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Gutwin</surname>
            , Lippold,
            <given-names>M.</given-names>
          </string-name>
          ,:
          <article-title>Real-Time Groupware in the Browser: Testing the Performance of Web-Based Networking</article-title>
          , T. C.
          <source>Nicholas Graham March 2011 CSCW '11: Proceedings of the ACM 2011 conference on Computer supported cooperative work</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Reddy</surname>
            .,
            <given-names>M.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spence</surname>
            ,
            <given-names>P.R.</given-names>
          </string-name>
          :
          <article-title>Collaborative information seeking: A field study of a multidisciplinary patient care team</article-title>
          .
          <source>Information Processing and Management;</source>
          <volume>44</volume>
          :
          <fpage>242</fpage>
          -
          <lpage>255</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Seffah</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Forbrig</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Javahery H</surname>
          </string-name>
          Multi-
          <article-title>devices “multiple” user interfaces: development models and research opportunities</article-title>
          .
          <source>J SystSoftw 73(n 2)</source>
          :
          <fpage>287</fpage>
          -
          <lpage>3001</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Kuziemsky</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varpio</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A Model of Awareness to Enhance Our Understanding of Interprofessional Collaborative Care Delivery and Health Information System Design to Support it</article-title>
          ,
          <source>International Journal of Medical Informatics</source>
          , doi:10.1016/j.ijmedinf.
          <year>2011</year>
          .
          <volume>01</volume>
          .009,
          <string-name>
            <surname>forthcoming</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>S. R.</given-names>
            <surname>Barley</surname>
          </string-name>
          .,
          <string-name>
            <given-names>W. H.</given-names>
            <surname>Dutton</surname>
          </string-name>
          .,
          <string-name>
            <surname>S. Kiesler.</surname>
          </string-name>
          ,
          <string-name>
            <surname>P. Resnick.</surname>
          </string-name>
          ,
          <string-name>
            <surname>R. E. Kraut.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Yates</surname>
          </string-name>
          .:
          <string-name>
            <surname>Does CSCW Need Organization</surname>
            <given-names>Theory ?</given-names>
          </string-name>
          ,
          <source>” Proceedings of the 2004 ACM conference on Computer supported cooperative work (CSCW'04)</source>
          , ACM Press, November 6-
          <issue>10</issue>
          ,
          <year>2004</year>
          , Chicago, Illinois, USA, pp.
          <fpage>122</fpage>
          -
          <lpage>124</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. U. K. Wiil, :
          <article-title>Using Events as Support for Data Sharing in collaborative Work,”</article-title>
          <source>Proceedings of the International Workshop on CSCW</source>
          , Berlin (
          <year>1991</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. M. Zacklad,:
          <article-title>Communities of Action: a Cognitive and Social Approach to the Design of CSCW Systems</article-title>
          ,” GROUP'03,
          <string-name>
            <surname>November</surname>
          </string-name>
          9-
          <issue>12</issue>
          ,
          <year>2003</year>
          ,
          <string-name>
            <given-names>Sanibel</given-names>
            <surname>Island</surname>
          </string-name>
          ,Florida, USA, pp.
          <fpage>190</fpage>
          -
          <lpage>197</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Ren</surname>
            , Y.,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Kiesler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Fussell</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Scupelli</surname>
            .: Multiple Group Coordination in Complex and Dynamic Task Environments: Interruptions,
            <given-names>Coping</given-names>
          </string-name>
          <string-name>
            <surname>Mechanisms</surname>
            , and
            <given-names>Technology</given-names>
          </string-name>
          <string-name>
            <surname>Recommendations</surname>
          </string-name>
          .
          <source>Journal of Management Information Systems / Summer</source>
          <year>2008</year>
          , Vol.
          <volume>25</volume>
          , No.
          <issue>1</issue>
          , pp.
          <fpage>105</fpage>
          -
          <lpage>130</lpage>
          . (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Bardram</surname>
            ,
            <given-names>J.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hansen</surname>
            ,
            <given-names>T.R</given-names>
          </string-name>
          :
          <article-title>Context-based workplace awareness concepts and technologies for supporting distributed awareness in a hospital environment</article-title>
          .
          <source>Computer Supported Cooperative Work</source>
          .
          <year>2010</year>
          ;
          <volume>19</volume>
          :
          <fpage>105</fpage>
          -
          <lpage>138</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Kuziemsky</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Varpio</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A Model of Awareness to Enhance Our Understanding of Interprofessional Collaborative Care Delivery and Health Information System Design to Support it</article-title>
          ,
          <source>International Journal of Medical Informatics</source>
          , doi:10.1016/j.ijmedinf.
          <year>2011</year>
          .
          <volume>01</volume>
          .009,
          <string-name>
            <surname>forthcoming</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>