what-when-how
In Depth Tutorials and Information
descriptions of each. he perspectives allow the IT system to be lexible to control
data low.
To achieve a general IT system that will work in any medical center, the system
needs to be able to integrate data from current systems. Since different hospitals
are using different systems, using one procedure to extract and transform the data
would be difficult. Different systems would use different encoding schemes to rep-
resent their data. An XML is used for internal data management, transformation,
and conversion.
In summary, Mario Beyer et al. [3] offer a solution to the many issues medi-
cal facilities are having with their current data control procedures. In it a detailed
description of a new system is given and how it can be implemented is discussed,
and a process is introduced in implementing a health IT network that has a large
potential to prevent unfavorable incidents in the medical profession.
14.5 Telemedicine[4]
Telemedicine is another example of a tool in the medical industry used to create a
point of interaction between the doctor and patient, and serves as a way to provide
access to individual care without physically connecting the patient and the doctor.
Of course, this presents a unique set of technical and social networking problems,
but it must also satisfy the same purpose as a physical encounter. hat is to say, the
results for the patient should not largely change whether the patient was seen either
in person or through technical proxy.
In one analysis, high-bandwidth visual conferencing was examined to deter-
mine the various factors that play a role in its success and to identify discreet com-
ponents of the visual interaction model that work together to create the functional
network. One way to analyze the model presented is an interconnected triangle
between the medical facility, the medical professionals who provide analysis, and
the patients who are involved. he connecting structure between each of these
three parts is the underlying technology, and the pathways between them are all
bidirectional (Figure 14.5).
Interestingly, in this approach, the information that should travel across these
pathways is largely not for the purpose of the actual technical network. Rather,
the technical network exists as an underlying entity that is mostly self-supporting
and exists to facilitate the medical information, its analysis, and various forms of
feedback between the various members of the network.
Within this framework, two particular forms of quality are reached. First is the
functional quality of the network, which deals with the ability of the network to
handle and process information. Included here are the functionality of the technol-
ogy involved (Is there a clear connection between the various clients?) as well as the
ability of the individuals to interact (Does the patient provide quality information
into the system, and are all members capable of handling the technical aspects of
