Health Information Management

Get Started. It's Free
or sign up with your email address
Rocket clouds
Health Information Management by Mind Map: Health Information Management

1. Clinical students

2. Information Management

2.1. General Tasks

2.1.1. Planning the information System and its archtecture

2.1.2. Directing its establishment and operation

2.1.3. Monitoring its development and operation with respect planned objectives

2.2. Definition

2.2.1. Comprises those management activities that deal with the management of information processing in an Institution, example Hospital

3. Hospital Information System

3.1. Socio-technical Subsystem

3.1.1. All information processing

3.1.2. Associated Human or technical Actors in their respective information processing roles

3.1.3. Aim: Enable the adequate execution of Hospital Functions for patient care

3.2. Components

3.2.1. Hospital Functions

3.2.1.1. Non-computer-based

3.2.1.2. computer-based information processing Tool

3.2.2. Business Process

3.2.2.1. Sequence of sub functions together with the conditions under which they are performed

3.2.3. Information Processing Tools: Application components that support Hospital Functions

3.2.3.1. Patient Administration System

3.2.3.2. Medical Documentation System

3.2.3.3. Nursing Management and Documentation System

3.2.3.4. Outpatient Management System

3.2.3.5. Provider or Physician Order Entry System - POE

3.2.3.6. Patient Data Management System - PDMS

3.2.3.7. Operation Management System

3.2.3.8. Radiology Information System - RIS

3.2.3.9. Picture Archiving and Communication System - PACS

3.2.3.10. Laboratory Information System - LIS

3.2.3.11. Enterprise Resource Planning System - ERP

3.2.3.12. Data Warehouse System

3.2.3.13. Document Archiving System

3.2.3.14. Clinical Information System and Electronic Patient Record System

3.3. Architectures

3.3.1. Describes its fundamental Organization represented by its components, their relationships to each others and to the environment

3.3.2. Styles at the logical tool layer of the computer based part are characterized by

3.3.2.1. Number of databases being used to store patient related data

3.3.2.1.1. DB1 Style

3.3.2.1.2. DBn style

3.3.2.2. Number of the application components used to support the hospital functions

3.3.2.2.1. Monolithic "AC1" Only one computer-based application component

3.3.2.2.2. Modular "Can": Several application components

3.3.2.3. Number of software products and vendors

3.3.2.3.1. All-in-one: Software from only one vendor "V1"- Homogeneus

3.3.2.3.2. Best of breed: Software from several vendors "Vn"

3.3.2.4. Communication Patterns

3.3.2.4.1. Spaghetti style "CPn": Directly connect those application components that need to exchange certain related-patient data when connecting several application components

3.3.2.4.2. Star architecture: "CP1" Interfaces are needed only between application components and communication server

3.4. Types of Integration: If application components at the logical layer are linked together through interfaces in order to cooperate, there may have different types of integration

3.4.1. Data Integration

3.4.2. Semantic Integration

3.4.3. Access Integration

3.4.4. Presentation Integration

3.4.5. Functional Integration

3.4.6. Process Integration

3.5. Communication Standards

3.5.1. Health Level 7 - HL7: Describes events and dedicated message types that are exchange between application components

3.5.2. DICOM - Digital Imaging and Communication in Medicine: Comprises file and message formats for all types of Medical Imaging Modalities

3.5.3. ISO/IEEE 11073: Defines a communication protocol for the exchange of bio-signals and vital parameters between several point of care devices

3.5.4. Standard for contextual Integration

3.5.5. Integrating the Healthcare Enterprise IHE: This Organization selects the most appropriate set of standards for a typical workflow

3.5.5.1. Facilitate interoperability

3.5.5.1.1. Definition

3.5.5.1.2. Aspects involved

3.5.5.2. Terms

3.5.5.2.1. IHE Domain

3.5.5.2.2. IHE Technical Framework

3.5.5.2.3. IHE Integration Profile

3.5.5.2.4. IHE Actor

3.5.5.2.5. IHE Transaction

3.5.6. Electronic Data Interchange for administration, commerce and Transport - EDIFACT: Is a message format for electronic data interchange in electronic commerce

3.5.7. Clinical Document Architecture - CDA

3.5.7.1. Components

3.5.7.1.1. Header

3.5.7.1.2. Body

3.5.7.2. Definition

3.5.7.2.1. Is a document markup standard that specifies the structure and semantics of "clinical documents" for its exchange

3.5.7.3. Goals

3.5.7.3.1. Give priority to delivery of patient care

3.5.7.3.2. Support exchange of human-readable documents between users

3.5.7.3.3. Promote longevity of all information encoded according to this architecture

3.5.7.3.4. Enable a wide range of post-exchange processing applications

3.5.7.3.5. Be compatible with a wide range of document applications

3.5.7.3.6. Prepare the design quickly

3.5.7.4. Levels

3.5.7.4.1. Definition

3.5.7.4.2. Narrative, sections and entry codes

3.5.7.4.3. The Narrative block contains the human readable content to be represented

4. Modeling Health Information System

4.1. 3LGM - Three layer graph-based Metamodel : Developed for describing, evaluating and planning Health Information System over three layers

4.1.1. Domain layer: Enterprise Functions and Entity types (implementation- independent)

4.1.2. Logical tool layer: Application components (support enterprise functions)

4.1.3. Physical tool layer: Physical data processing systems (support application components)

5. Tasks of Information Management in Hospitals

5.1. Planning the Hospital information system and its architectures

5.2. Directing its establishment and its operation

5.3. Monitoring its development and operation in relation with the planned objectives

5.4. Deals with activities in 3 levels

5.4.1. Strategic Information Management

5.4.1.1. Deals with the Hospital's Information processing as a whole

5.4.1.2. Depends on the hospital´s business strategy and strategic goals and has to translate these in an adequate information stragtegy

5.4.1.3. The planning activities result in a strategic Information Management Plan

5.4.2. Tactical information Management

5.4.2.1. Deals with particular enterprise functions

5.4.2.2. Planning at this level means planning projects and all the resources needed for them

5.4.2.3. Directing at this level means the execution of information management projects

5.4.3. Operational Information Management

5.4.3.1. Responsible for operating the components of the Hospital Information system

6. KPI

6.1. COBIT Developed by IT Governance Institute; Defines 34 KPI in 4 domains

6.1.1. Plan and Organize

6.1.1.1. % of strategic IT objectives that are aligned to the strategic hospital plan

6.1.1.2. % of redundant data elements in the IT Architecture

6.1.1.3. Number of Business process that are not yet supported by IT

6.1.1.4. % of stakeholders that are satisfied with IT quality

6.1.1.5. % of IT projects that are on time and within budget

6.1.2. Acquire and Implement

6.1.2.1. % of users satisfied with the functionality of new IT system

6.1.2.2. Number of IT problems that lead to non operation periods

6.1.2.3. % of IT systems that do not conform to the defined technical standards

6.1.2.4. % of IT systems where adequate user training is provided

6.1.3. Deliver and Support

6.1.3.1. % od stakeholders that are satisfied with IT support

6.1.3.2. Number of user complaints with regard an IT Support

6.1.3.3. % of satisfactory response times of an IT system

6.1.3.4. Number of lost hours due to unplanned IT downtimes

6.1.4. Monitor and Evaluate

6.1.4.1. Frequency of Reporting from IT Management to enterprise management

6.1.4.2. Satisfaction of management with IT performance reporting

6.1.4.3. Number of independent IT reviews

6.2. CCHIT Functional requirement criteria. CCHIT is a non profit organization that offer certification for inpatient EHR, ambulatory EHR and other application components

6.3. HIS Benchmarking Report: uses HIS benchmarking criteria that have been agreed to a regional group of hospitals´ CIOs

6.3.1. KPI for HIS Organization

6.3.2. KPI for HIS costs

6.3.3. KPI for HIS mamanagement

6.3.4. KPI for HIS functionality

6.3.4.1. % of all documents available electronically

6.3.4.2. % of all diagnosis coded electronically

6.3.5. KPI for HIS architecture

6.3.5.1. Number of computer based application components

6.3.5.2. % of standard interfaces between applications

6.3.5.3. Functional redundancy rate

7. EHR - Electronic Health Record

7.1. Trans-institutional digital repository of information regarding the health status of a subject of care

7.2. PHIR - Personal Helath Record

7.2.1. If the EHR allows the patient to actively manage his data

7.2.2. Types

7.2.2.1. Off line personal Health records, generally paper-based and comprise copies of clinical documents

7.2.2.2. web-based personal health records

7.2.2.3. Provider-based personal health records where hospitals and other providers make some of patient health information available for the patient

7.3. According to the Institute of Medicine it has 5 core functions

7.3.1. Health Information

7.3.2. Data storage

7.3.3. Order Entry

7.3.4. Results Management

7.3.5. Decision suport

8. ehealth

8.1. Definition

8.1.1. Is an emerging field of Medical Informatics referring to the organization and delivery of health services and information using internet and related technologies to improve health care locally, regional and globally

8.2. Evaluation

8.2.1. Act to assess whether an ehealth system is working and producing the effects as expected

8.2.2. In this context ehealth system refers not only the technical TIC artifact but also the socio-organizational and environmental factors and process that influences its behaviors

8.2.3. Scope

8.2.3.1. Planning

8.2.3.1.1. Example: If the intended system is aligned with the organization strategy

8.2.3.2. Design

8.2.3.2.1. Example: If the specifications of the system have been met in terms of its features and behaviors

8.2.3.3. Implementation

8.2.3.3.1. Example if the implementation is under scope and budget

8.2.3.4. Use

8.2.3.4.1. Example: evaluate the extent to which the system is used and its impact on health outcome

8.2.3.5. Maintenance

8.2.3.5.1. Example: Evaluate how well the system has been supported and adapted to changing needs

8.3. stakeholders

8.3.1. Service Providers

8.3.1.1. Organizations

8.3.1.1.1. Hospitals

8.3.1.1.2. Medical Providers

8.3.1.1.3. Community Healthcare centers

8.3.1.1.4. Medical Centers in Universities

8.3.1.1.5. Prison care centers

8.3.1.2. Individuals

8.3.1.2.1. Clinicians

8.3.1.2.2. Nurses

8.3.1.2.3. Physiotherapists

8.3.1.2.4. Volunteers

8.3.2. Consumers

8.3.2.1. Organizations

8.3.2.1.1. Private companies

8.3.2.1.2. Day care baby centers

8.3.2.1.3. Airport

8.3.2.1.4. Armed forces

8.3.2.1.5. Government

8.3.2.2. Individuals

8.3.2.2.1. Patients

8.3.2.2.2. Patients families

8.3.2.2.3. Researchers

8.3.2.2.4. Citizens

8.3.2.2.5. Employees

8.3.3. Supporters

8.3.3.1. Organizations

8.3.3.1.1. Technology Vendors

8.3.3.1.2. Health Insurance companies

8.3.3.1.3. Clinical Specialty Departments

8.3.3.1.4. Rehabilitation Centers

8.3.3.1.5. Technical Support Centers

8.3.3.2. Individuals

8.3.3.2.1. Engineers

8.3.3.2.2. Administrators

8.3.3.2.3. Application specialists

8.3.3.2.4. Care givers

8.4. OID

8.4.1. Object Identifier Domain

8.4.2. Identifier mechanism standardized by the International Telecommunication Union and ISO/IEC for naming any object, concept or thing with a globally unambiguous persistent name

8.4.3. Has a nod in the "OID tree" or Hierarchy

8.4.3.1. The format of each node in the tree is represented by a series of numbers separated by periods

9. Medical Documentation

9.1. Objectives in Patient care

9.1.1. Makes patient care more effective and appropiate

9.2. Objectives in Administration

9.2.1. Forms the basis for refunding, process planning and control

9.3. Objectives in Quality Management and Education

9.3.1. Supports critical reflection and Systematic Monitoring

9.4. Objectives in Clinical Research

9.4.1. Allows patient selection and statistical analysis

9.5. Multiple use of patient data

9.5.1. computer-based data Management systems offer the possibility of the multiple use of data recorded once to be used for different objectives and tasks

9.5.2. Patient-group analysis

9.5.3. Patient-oriented analysis

9.6. Clinical Data Management systems

9.6.1. Distinction by content

9.6.1.1. Clinical Information

9.6.1.1.1. Is general based on patient-related data

9.6.1.2. Medical knowledge

9.6.1.2.1. Abstracts from individual patient and describes general insights

9.6.1.3. Healthcare system

9.6.1.3.1. Provide statistical information about healthcare system's infrastructure

9.6.2. Distiction by utilization

9.6.2.1. Patient -group analysis

9.6.2.2. Patient-oriented analysis

9.6.3. Distinction by level of standarization

9.6.3.1. Not standarized

9.6.3.1.1. It is useful to specify all the details or characteristics of a situation

9.6.3.2. Partly standarized

9.6.3.3. Mainly standarized

9.6.3.4. Fully standarized

9.6.3.4.1. It allows comparability of data objects at 2 levels