Documente Academic
Documente Profesional
Documente Cultură
4-Data Management
This covers all aspects of data handling from
Collection,
Storage,
Quality-assurance and
Flow, to processing, compilation and analysis
5-Information Product
Data must be transformed into information that
will become the basis for evidence and
knowledge to shape health action.
The terminformation productis typically
associated with educational e-books (of either
Kindle, simple PDF, or e-pub variety), audio
recordings, or digital video recordings, and, in
most cases, a combination of all of the above.
Architectures of Hospital
Information System
After this lecture, you should be able to
answer the following questions:
What kind of data has to be processed in
hospitals?
What are the main hospital functions?
What are the typical information processing tools
in hospitals?
What are the different architectures of HIS?
How can integrity and integration be achieved
within HIS?
Architectures of Hospital
Information System
Hospital Information System architecture has three
main levels;
Central Government Level,
Territory Level, and
Patient Carrying Level.
Architectures of Hospital
Information System
Domain Layer: data to be processed in Hospital
Entity types related to Patient Care (examples)
Typical entity types representing certain object classes and data
related to the patient and his or her histories:
Entity type
Case
Patient
Order
Diagnosis
Architectures of Hospital
Information System
Entity types related to Resources (examples)
A hospital must guarantee that all resources needed for patient
care are available continuously. The following resources are
necessary:
Entity type
Appointment
Bed
Health care
professional
Drug
Architectures of Hospital
Information System
Entity types related to Administration (examples)
Besides information about resources, hospital administration
needs the following entity type:
Entity type
Patient record
archive
describes how and where the electronic or paper-based patient record can be
found.
Classification
Classification of
diagnoses
Cost unit
10
Architectures of Hospital
Information System
Entity types related to Management (examples)
Management relates to the hospital as a whole and, thus, needs
compressed information about the hospitals operating. The
following entity types are necessary for management:
Entity type
Business
strategy
Strategic
information
management
plan
a strategic plan, which gives directives for the construction and development
of a hospital information system
Project
Quality report
11
Architectures of Hospital
Information System
Domain layer: Hospital Functions
We will now elucidate, how and where data about these entity
types are processed in hospitals.
We use enterprise functions to summarize classes of information
processing activities.
And since we focus on hospitals, we call them hospital functions
here, which can also be considered as representatives of processes
12
Architectures of Hospital
Information System
We will present hospital functions and their interpreted and
updated entity types in greater detail, but we do not (yet) focus on
how they are typically supported by various computer-based or
non-computer-based information processing tools
We will focus on the following questions:
What are the main hospital functions that have to be supported by a
HIS?
What information is interpreted or updated by hospital functions?
Which functional aspects have to be considered when implementing
information processing tools?
13
Architectures of Hospital
Information System
Main enterprise function to be supported by a HIS:
Patient care
Supply and disposal management, scheduling and resource
allocation
Hospital administration
Hospital management
Research and education
14
Architectures of Hospital
Information System
Patient care:
Patient admission
Decision making, planning and organization of patient
treatment
Order entry
Execution of diacnostic, therapeutic and nursing procedures
Coding of diagnoses and procedures
Patient discharge
15
Architectures of Hospital
Information System
Patient admission:
Patient admission (short: admission) aims at recording and
distributing the patient demographics and insurance data as well
as medical and nursing data of the patient history
In addition, each patient must
becorrectly identified, and a
unique patient and case identifier
must be assigned
16
Architectures of Hospital
Information System
Patient admission
This hospital function can be decomposed as follows:
Appointment scheduling
Patient identification and checking for recurrent
Administrative admission
Medical admission
Nursing admission
Visitor and information service
17
Architectures of Hospital
Information System
Apointment scheduling:
The hospital must be able to schedule an appointment for a
patient's visit. In addition, unplanned patient admissions must be
possible (e.g., in case of emergencies)
18
Architectures of Hospital
Information System
Patient identification and checking for recurrent:
A unique patient identification number (PIN) must be assigned to each patient:
This PIN should be valid and unchangeable lifelong (i.e., the PIN should not be based on
changeable patients attributes such as the name)
The PIN is the main precondition for a patient-oriented combination of all information arising
during previous, recent as well as future hospitalizations
Before a PIN can be assigned, the patient must be correctly identified, usually based
on a health insurance card and on available administrative patient master
information (such as name, date of birth)
..
19
Architectures of Hospital
Information System
If the patient has already been in the hospital, she or he must be
identified as recurrent, and previously documented information
must be made available (such as previous diagnoses and
therapies).
If the patient is in the hospital for the first time, a new PIN must be
assigned.
In addition, the hospital must be able to distinguish different cases
or hospital stays of a patient. Therefore, in addition to the PIN, a
case identification number (CIN) is usually assigned (see
administrative admission).
20
Administrative admission:
Administrative admission starts following patient identification. It creates a
so-called case, being the aggregation of several contacts, clustered
according to specific clinical and/or organizational purposes of the hospital
In case of inpatient treatment, a case summarizes the hospital stay from
patient admission until discharge
Each case is uniquely identified by its CIN. Important administrative data
such as insurance data, details about special services, patient's relatives,
admitting physician, and transfer diagnoses must be recorded
..
Health Information Systems
21
Architectures of Hospital
Information System
Some of the administrative data must be available to other
hospital functions through the help of certain organization media.
Administrative data form the backbone of information processing
In case of changes, patient data must be maintained and
communicated. If the admitting physician has communicated
relevant information (e.g., previous laboratory findings), this
information must be communicated to the responsible physician in
the hospital
..
22
Architectures of Hospital
Information System
Administrative admission is usually done either in a central patient
admission area or directly on the ward (e.g., during emergencies
or on the weekend)
Even in emergencies patient admission is necessary. At least
patient identification and checking for recurrent has to be
performed in order to assign a proper PIN and CIN. In these cases
a short version of administrative admission may be applicable
If the patient is unconscious and does not bear an identity card,
only a dummy name may be recorded to provide PIN and CIN. It
will be no problem to replace the dummy name by the correct
name later
Health Information Systems
23
25
26
27
image HIS.pptx
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function patient admission, its subfunctions and interpreted
and updated entity types.
28
29
30
31
by
providing
32
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function decision making, planning and organization of
patient treatment, its subfunctions and interpreted and updated entity
types.
34
35
36
..
37
38
39
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function order entry, its subfunctions and interpreted and
updated entity types.
40
41
42
43
44
45
must be executed,
all procedures must be documented,
findings and reports must be transmitted (as quickly as necessary) back
to the ordering unit and
presented to the responsible health care professional
46
execution
execution
execution
execution
execution
execution
of
of
of
of
of
of
operations,
irradiation,
chemotherapy,
radiological examinations,
lab examinations or
prophylaxis and medication
47
48
of
diacnostic,
therapeutic
and
nursing
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function execution of diagnostic, therapeutic and nursing
procedures , its subfunctions and interpreted and updated entity types.
49
50
51
52
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function coding of diagnoses and procedures, its subfunctions
and interpreted and updated entity types.
53
54
55
56
..
important findings,
therapeutic procedures,
.....
59
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function patient discharge and referral to other institutions,
its subfunctions and interpreted and updated entity types.
61
62
management,
scheduling
and
63
64
65
66
Extract of the domain layer of the 3LGM based reference model describing
the enterprise function supply and disposal management, its subfunctions
and interpreted and updated entity type.
67
69
70
Extract of the domain layer of the 3LGM based reference model describing the
enterprise function scheduling and resource allocation, its subfunctions and interpreted
and updated entity type
71
Extract of the domain layer of the 3LGM based reference model describing the
enterprise function human resources management , its subfunctions and interpreted
and updated entity types
74
Patient care
Supply and disposal management, scheduling and resourch allocation
Hospital administration
Hospital management
Research and education
Patient administration
Archiving of patient information
Quality management
Cost accounting
Controlling
Financial accounting
Facility management
Information management
77
Patient administration
Archiving of patient information
Quality management
Cost accounting
Controlling
Financial accounting
Facility management
Information management
80
81
82
Types of
Healthcare
Information
Systems
Pharmacy
May include:
medication
package and patient bracelet to ensure
right patient, right drug, right dose, right
time, right route
E-prescribing
Home Healthcare
2. Administrative Systems
Client Registration
Financial
Payroll and Human Resource
Risk management
Quality assurance
Contract management
Materials management
Scheduling
Other Administrative Systems
Real-time information
Network database
Knowledge Representation
(Dashboard Display)
Test results
Evidence-based practice guidelines