# data[].attributes.body
To examine the same aspect twice.
Often needed when a patient is transferred from one department to another while there is no data integration so that the new department cannot see and use the results from former examinations.

# data[].attributes.body
Data integration is obtained in a hospital information system when data that have been recorded are available wherever they are needed, without having to be reentered.

# data[].attributes.body
To avoid duplicate data entry, which is inefficient
and prone to error, data should be recorded only once,
even when they are stored in different databases. Condition
where data are captured once but used for more than one task.
prerequisite data integration

# data[].attributes.body
- manual transfer of data from one volume to another,

# data[].attributes.body
Information processing, therefore, should
center on the patient (not on the institution)

# data[].attributes.headline
Leanness of Information Processing Tools

# data[].attributes.subject
Leanness of Information Processing Tools

# data[].attributes.body
for each process, there should be all the tools necessary
but as few as possible. For a given task, from the point of view of the user,
there should be as many different information processing tools as necessary,
but as few as possible.

# data[].attributes.body
provide the right information at the right time at the right place to the right people in the right form

# data[].attributes.body
Quality of the information processes that are
necessary to meet the user's needs, such as single
recording and multiple usability of data, no transcription
of data, leanness of information processing tools, efficiency of
information logistics, and patient-centred information processing.

# data[].attributes.body
Based on a description of the hospitals strategic goals (e.g., presented in a mission statement),
the strategic information management goals should be derived using the method of strategic alignment.
(chapter 9.4) The challenge of information management is to keep the balance between the different -
and possible contradicting- goals of the hospital.

# data[].attributes.headline
Fulfillment of Laws relevant to Information Management

# data[].attributes.subject
Fulfillment of Laws relevant to Information Management

# data[].attributes.body
In each country, different laws affect health information
processing, addressing, for example, organization of
health care, financing of health care, and health
statistics. Those laws must be taken into account by
information management.

# data[].attributes.body
For the hospital as an enterprise, the hospital
information system should typically contribute
to high quality patient care, efficient usage of
resources, and fulfillment of legal requirements
as general goals of all hospitals.

# data[].attributes.body
Whether the goals of information management have
been reached, or, in a broader sense, to what extent a
hospital information system contributed to the goals of t
he hospital and to the expectations of different stakeholders,
and how it fulfils information management laws.

# data[].attributes.body
model describing the arcitecture of the hospitals information system

# data[].attributes.body
Deals with information processing as a whole,
depends on hospital business strategy

# data[].attributes.body
Monitoring as part of strategic information management, continuously auditing HIS Quality as defined by strategic information management

# data[].attributes.body
-Is specialized to automatically monitor, store, and clearly present a vast amount of patient-related clinical data in intensive care units.
-supports scoring and may offer features for decision support and various statistical analyses

# data[].attributes.body
Suppors the management of analysis in a laboratory

# data[].attributes.body
A set of actually usable rules, which control data processing of certain physical data processing systems.  Rules are considered to be actually usable, if they are implemented such that they are ready to support certain enterprise functions in a certain enterprise or support communication between application components

# data[].attributes.body
As many enterprise functions as possible are supported by computer-based tools

# data[].attributes.body
Condition of an information system where an enterprise function is supported by one and only one application component

# data[].attributes.body
Systematic management of redundantly stored data within health information systems

# data[].attributes.body
HIS should be sufficiently flexible to adapt to the changing needs of the hospital.

# data[].attributes.body
Beds actually used

# data[].attributes.body
Decides on questions of fundamental importance for the hospital development (hospital goals, strategic decisions, personnel decisions and decisions about budget , investments, and key treatments)

# data[].attributes.body
Contains data which have been extracted from other application components, in order to support either hospital management or clinical research

# data[].attributes.body
Is guaranteed if different application components use the same system of concepts, i.e. they interpret data the same way

# data[].attributes.body
Is obtained in a hospital information system when data that have been recorded are available wherever they are needed, without having to be reentered.

# data[].attributes.body
Condition of an information system where the application components needed for the completion of a certain task can be used where they are needed

# data[].attributes.body
Nursing admission typically comprises the introduction of the patient to the ward and nursing history and is done by the responsible nurse. For the nursing history there may be computer-based or department-specific, (semi-)standardized data entry forms available. These may contain information about the current diagnoses and therapy, orientation, mobility etc. The information should be available during the whole stay.

# data[].attributes.headline
Nursing Management And Documentation System

# data[].attributes.subject
Nursing Management And Documentation System

# data[].attributes.body
The nursing management and documentation system offers similar features as the medical documentation system. Application component for nursing documentation, supporting all phases of the nursing process such as nursing patient history, nursing care planning, execution of nursing tasks, and evaluation of results.

# data[].attributes.body
An application component where the controlling rules for data processing are implemented as executable software

# data[].attributes.body
HIS architecture should ensure that the different computer-based and non-computer-based information processing tools can be smoothly and efficiently integrated, in order to provide a maximum quality of information processing.

# data[].attributes.body
Integrity, reliability, completeness, accuracy, relevancy, standardization, authenticity, availability, confidentiality, and security of data.

# data[].attributes.body
HIS quality is a matter of finding optima in a multidimensional space with myriads of restrictions. Due to this it is hardly possible to provide information managers with a simple checklist to find out whether the HIS is good or not. Several specific approaches and initiatives are dealing with this issues of HIS quality. [Anna Lörke according to Winter et al.]

# data[].attributes.body
Availability of technical or human resources needed for information processing. It comprises quality of data, quality of computer-based application components, quality of physical data processing systems, and quality of HIS architectures.

# data[].attributes.body
provides six quality characteristics for software

# data[].attributes.body
- Presentation integration is guaranteed when different application components represent data as well as user interfaces in a unified way.

- integration is guaranteed when different application components represent data as well as user interfaces in a unified way. Condition of an information system where different application components represent data as well as user interfaces in a unified way.

# data[].attributes.headline
Quality of Computer-Based Application Components and Their Integration

# data[].attributes.subject
Quality of Computer-Based Application Components and Their Integration

# data[].attributes.body
Quality characteristics for software and software ergonomics, which can be applied to computer-based application components, are provided by ISO 25000 and ISO 9241. Further quality criteria for software products that are of relevance for health care are adaptability, availability, sustainability, maturity, certification and standardized interfaces. [Anna Lörke according to Winter et al.]

# data[].attributes.body
Can a software product be easily adapted to the working context? For example, functionality of a RIS software can be adapted to the particular workflow in a specific radiology.

# data[].attributes.body
How sustainable is the overall software product? For example, a R IS software is still built on the programming language that is not further supported and developed.

# data[].attributes.body
Functionality, reliability, efficiency, maintainability, portability, and usability of a software product

# data[].attributes.body
Whether software products support different standards for integration (such as HL7) as introduced in Sect. 6.5.4 is another important aspect of quality of structures. Otherwise integration in AC n architectures is hardly reachable in an economically reasonable way.

# data[].attributes.body
Describes how messages of a certain data format are communicated when an event occurs. Within health information systems, well-known examples are HL7 and DICOM.

# data[].attributes.body
Communication standards describe how messages of a certain data format are communicated when a certain event occurs

# data[].attributes.body
- metamodel for developing health information systems
- three layers
- aim:support the systematic information management

# data[].attributes.body
- tool for modelling 3LGM

# data[].attributes.body
- of information processing supported by 3LGM

# data[].attributes.body
- continuously auditing HIS quality

# data[].attributes.body
- Gathering and aggregating financial and other data
- aim: control and optimize hospital operations

# data[].attributes.body
- data uniformly recorded
- clear rules for recording and storing data

# data[].attributes.headline
Availability of the Application Component

# data[].attributes.subject
Availability of the Application Component

# data[].attributes.body
- access integration guaranteed

# data[].attributes.body
- great benefit
- processing large amounts of data

# data[].attributes.body
- quantitative measurement for monitoring the achievement of strategic goals (of a enterprise)

# data[].attributes.body
- meet expectations of the purchaser of goods or services
- quality of structures or processes or outcome

# data[].attributes.body
- sketching the foundation for study

# data[].attributes.body
- quantitativ: e.g. time measurement
- qualitativ: e.g. interviews

# data[].attributes.body
- result of many decisions of the study
- e.g. study design, outcome measures, ...

# data[].attributes.body
-standardize observation protocols
- achieve inter-observer reliability

# data[].attributes.body
- result of the study

# data[].attributes.body
- comprises management of information processing in an institution, e.g. hospital
- plans the information system of an enterprise and its architecture, directs its establishment and its operation, and monitors its development and operation with respect to the planned objectives
- information management should contribute to fulfill strategic enterprise goals

# data[].attributes.body
- Socio-technical subsystem of a hospital
- comprises all information processing, the associated human or technical actors
- aim: adequate execution of hospital functions for patient care.