HMGT Exam 1 Topics
Lecture 1: Health Information Systems and Informatics in Healthcare
I. Why Managing Information and Technology Matters in Healthcare
Healthcare is unique because medical care has many complexities and many complex needs. Traditional approaches are no longer able to meet the complex needs of medical care, and traditional processes no longer are able to meet the new models of healthcare delivery that are constantly emerging. It used to be that doctors or a few personnel could manage healthcare organizations, but administrative tasks have become so complex and so vast over time that you cannot rely on traditional processes.
Healthcare is urgently seeking improved cost and quality performance by using information systems in innovative ways. Using information technology innovation and introducing innovations to improve performance in healthcare is necessary for two purposes: providing relief from mundane manual tasks, and using new technologies as they become available—mobile computing, internet of things, telemedicine, genomic data, secure networks—to improve care, improve quality, improve efficiency, and make administrative tasks much more efficient.
As students of healthcare and future healthcare workers, you need to understand the basics to work in healthcare today in any capacity.
II. Building Blocks: Information Technology, Information Systems, and Applications
A. Information Technology
Information technology is a broad term describing the combination of computers and electronic devices, hardware and software, local and internet network infrastructures, and data including images, videos, and voice across all industries.
B. Information System
An information system is an arrangement of data, processes, people, and information technology that interact to collect, process, store, and provide as output the information needed to support the organization.
Information technology is a component of every information system, but the term includes technologies within and outside of an organization.
C. Applications as Components of Information Systems
From an organizational perspective, computer applications are components of information systems needed to support specific processes.
In this course segment, the main focus is managing information, information systems, and data. Although there are many types of information systems, the primary focus is on two types:
Administrative applications
Clinical applications
III. Why Automate Healthcare Using Health Information Systems
A. The Core Justification for Automation
There are three major reasons to automate healthcare using health information systems:
Improve the quality of care
Improve the efficiency of care
Improve administrative processes
Health information systems should be aligned with these goals.
B. Healthcare Has Many Stakeholders
When you think about a healthcare organization and the stakeholders involved in the delivery of care, there are many: patients, clinicians, administrative personnel, government, public health organizations, quality improvement organizations, payers, insurance, and many others.
Because healthcare includes many participants and complex needs, information exchange and coordination become essential, and information systems become necessary to manage that complexity.
IV. The Big Picture: Challenges Driving the Need for Better Information Systems
To understand the need for better information systems, it helps to describe the current challenges healthcare is facing.
A common way to think about improving medical care is the so-called triple aim:
Improving outcomes
Reducing costs
Ensuring quality
You may also see different wording for these goals, such as improving population health or improving patient experience.
The challenges that tie to information systems management include cost, access, quality, evidence-based medicine, and broad organizational changes.
V. Cost: Why Healthcare Spending Forces System Change
United States per capita healthcare spending is more than twice the average of other developed countries. Total healthcare spending, public and private, is projected to rise to about one-fifth of the economy.
Healthcare experts estimate about 30% of total healthcare spending is unnecessary, leading to ineffective, inefficient, overpriced, and wasteful services. These costs are projected to keep rising faster than inflation, wages, or the overall economy.
A. Why Costs Rise
The rise in healthcare costs originates from several factors:
Shift toward an older population
This is a function of rising life expectancy, rising from the 1970s to about 80 after the 2000s. Older patients will need healthcare, will get ill, will need treatments, and treatments will be more expensive.Chronic illnesses such as obesity and diabetes
Chronic diseases increase the risk of other conditions. Patients with chronic conditions are harder to treat and account for the vast majority of healthcare expenditures.Misaligned incentives
Misaligned incentives and provider reimbursement contribute to unnecessary and inefficient spending.Advancing technology
As the cost of equipment for expensive tests like MRI and CT scans has increased, the portion of healthcare expenditure due to advanced technology has risen.
VI. Access: Why Coverage and Care Delivery Require Better Information Exchange
A. Insurance as a Measure of Access
When we say access, the immediate thing to think of is insurance. Insurance is one measure for access to care. It has changed tremendously over the years, going down in a positive direction and stabilizing in the last few years at around 8%, though it is expected to rise.
B. Public and Private Insurance Structure
There are two major components:
Private insurance companies
Public insurance companies
Public insurance includes Medicare, Medicaid, and the VA. Public and private are close to one another in how much is paid, but private plans take a big chunk of insured people, and many private plans are employment-based.
C. Access Creates System Strain Without Better Systems
Information systems can assist in providing better access to care. But if access problems are solved, that will strain the system by adding care demands for additional millions of people.
That requires better information exchange and coordination of care.
Disparities exist across demographics and across states, including differences between Medicaid expansion and non-expansion states.
VII. Quality: Why Outcomes Don’t Match Spending
There is evidence of quality and value issues in the US healthcare system.
Excess preventable deaths were demonstrated by the Institute of Medicine in 1999. The report To Err Is Human identified that close to hundreds of thousands of people are dying as a result of preventable medical errors.
Although the United States spends more on healthcare than any other developed countries, health outcomes are generally no better. Comparisons include major categories such as health status, quality of primary care, and quality of acute care, with metrics like life expectancy, mortality, unmanaged chronic conditions, and childbirth safety.
VIII. Evidence-Based Medicine: Why Information Must Reach the Point of Care
Evidence-based medicine is an information management and learning strategy that seeks to integrate clinical expertise with the best evidence available to make effective clinical decisions that ultimately improve patient care.
Standards and practice guidelines need to be incorporated into day-to-day operations, so the use of information is essential.
However, achieving evidence-based medicine is difficult. You need the right information and the right guideline presented to the provider at the point of care. You need a process and workflow. You must ensure clinicians adhere to protocols, and if they override protocols, you need to understand why they are overriding and using non-standard care actions.
Information systems play a big role in achieving evidence-based medicine.
IX. Organizational Change: Government, Markets, and Delivery Models
There are powerful influences on how health information systems are used, including government and market forces, and sometimes these are in different directions.
Government regulates and passes laws governing implementation and use of health information systems. The free market encourages commercialization of health information system products and services. As a student of health information systems, you need to understand how the business of healthcare works.
A major challenge is broad organizational change, especially in publicly financed healthcare systems. Market-oriented reforms aim to make resource allocation more efficient, more innovative, and more responsive to consumer preferences while maintaining equity.
In a market-oriented system, the preferences and values of patients, combined with information about how they can fulfill their preferences, drive decision making.
Managed care is a system in which patients agree to visit only certain doctors and hospitals and the cost of treatment is monitored. Managed care was a solution in the 1990s, but in the last decade newer delivery models have grown, including accountable care organizations and patient-centered medical homes.
These incentives, delivery changes, and organizational requirements tie directly to information systems.
X. What You Need to Know as a Health Information Student
If you’re wondering where to start, ask: what are these systems used for inside healthcare organizations?
You do not need to know how to program. What you need to understand is how to evaluate, choose, and use health information systems to solve problems in clinical operations, patient engagement, and strategic planning.
Whether it’s an electronic health record, imaging system, or enterprise dashboard, the job is to match the right tool to the right purpose and help the organization use it effectively.
XI. Crossing the Quality Chasm: Four Reasons Quality Struggles
The report Crossing the Quality Chasm identified four major reasons why the US healthcare system struggles with quality:
A gap between innovation and implementation
The system was built around acute illness, but now faces a growing burden of chronic diseases
Inadequate use of information technology—data exists, but is not used to improve care delivery
Conflicting incentives in the payment system, rewarding volume instead of value
Health informatics addresses these by closing implementation gaps, supporting chronic care coordination, improving IT use, and enabling performance-based models.
XII. Policies That Shaped Health Information Systems
A. HIPAA (1996)
Health Insurance Portability and Accountability Act of 1996. When you hear HIPAA, think privacy and security of protected health information.
B. Medicare Prescription Drug Improvement and Modernization Act (2003)
Critical for introducing standards for electronic prescribing as an early step toward electronic health records. During this time, the Office of the National Coordinator of Health IT (within HHS) was established.
C. ARRA / HITECH (2009)
Provided stimulus money for electronic health record adoption: $25 billion of incentives for hospitals and physicians who adopt and meaningfully use EHRs.
Meaningful use criteria served as certification criteria for EHR features, functions, reporting, and interoperability capabilities within standards.
These legislations have had a huge influence on how health information systems have been shaped over the years.
XIII. Patient Engagement and Public Health: Two Stakeholders That Change Everything
A. Patient Engagement as Co-Production of Care
Healthcare is unique because care is not only delivered by providers. If a patient does not adhere to recommendations or does not watch their health, outcomes may not be as intended.
Care is co-production: the provider is not the only contributor. The patient or consumer has an important role.
Engaging patients across the continuum of care is critical, and technologies like internet, email, smartphones, mobile devices, and social media have a place in health information systems. At the same time, they create demands for security, privacy, and confidentiality.
B. Public Policy and Public Health
Public policy and public health are key stakeholders.
Public health can provide alerts for disease outbreaks, study effectiveness of treatments, improve quality of health services, and maintain population health status.
XIV. Why the Terminology Feels Confusing
Terms like medical informatics, nursing informatics, clinical informatics, and healthcare IT often overlap. The terminology is not always used consistently and there is no standard definition.
For this course, health informatics is the practical and organizational use of information systems to improve care. It is not just about building technology; it is about solving healthcare problems using data systems and smart design.
XV. The Three Pillars: IT, Informatics, Analytics
For the purpose of this course, there are three pillars:
A. Health IT
Health IT is about managing information technology:
Disaster recovery
How data flows in an organization
Servers
B. Analytics
Analytics is about using the information created by these systems.
C. Informatics
Healthcare informatics sits between IT and analytics.
It is about managing data: how to keep it, manage it, organize it.
This is where IT-based interventions are designed to improve care and operations.
XVI. The DIKW Model: How Informatics Turns Data Into Better Care
The goal of health informatics is not just to collect data, but to transform it into something meaningful and actionable.
Data: raw facts like measurements, orders, clicks, time stamps
Information: cleaned and structured data, like a list of abnormal labs
Knowledge: actionable information with context, like rising creatinine indicating kidney injury
Wisdom: when actionable information becomes part of operations through interventions like clinical decision support alerts or automated protocols
In today’s environment, interventions might involve machine learning models, FHIR APIs, or automated alerts, but the principle stays the same: using technology to improve decisions and outcomes.
XVII. DIKW Examples: Clinical and Operational
A. CHF Patient Portal Example
Data: 87,000 patient portal users
Information: identify which users have CHF and whether they use the portal
Knowledge: CHF patients are frequently readmitted, and portal use can be measured
Wisdom: CHF patients who use the portal are readmitted less often, creating a rationale for encouraging portal use during discharge or follow-up
B. Bandwidth Example
Data: 1 GB internet minimum for normal hospital operations
Information: visitors consume bandwidth needed for clinical use
Knowledge: Wednesdays have a spike in volume and network performance suffers
Wisdom: usage correlates with admissions, so bandwidth should be adjusted dynamically through traffic shaping or added capacity
XVIII. How Emerging Technologies Mature: The Hype Cycle
Technological innovations follow a predictable path from early development to widespread adoption.
Expectations rise, realities are discovered, and then things stabilize.
This model helps decision makers evaluate whether technology is experimental, ready for early adoption, or becoming a standard—rather than going by market hype.
XIX. A Short History of Health IT: Why Today Looks the Way It Does
1950s: mainframes used for administrative purposes like processing claims
1960s: minicomputers enabled organizations to process information inside the organization
MUMPS: database and programming language still used as underlying structure in Epic
1969: TCP/IP developed, enabling internet communication layers
1970s: relational databases introduced (think Excel sheets connected to one another)
1981: IBM PC release, enabling smaller-scale organizational computation
HL7 introduced as a standard for machine communication and interoperability
2007–2008: Conficker virus brought security to the national stage
2009 onward: HITECH and later reforms influenced EHR adoption, interoperability, and payment model shifts
XX. Five Domains of the Health IT Environment: Where Data Comes From
Data comes from five domains:
Workload and applications (clinical/admin operations, EHRs, instrumentation)
Data communication (wired/wireless/cellular, enabling secure flow)
IT analytics (integration, governance, business rules, turning raw data into insights)
Operations platform (servers, cloud, virtualization, disaster recovery)
Information security (access controls, audit trails, encryption, compliance across all domains)
Understanding how these interact is critical for managing, securing, and analyzing data in any informatics initiative.
XXI. Why Interoperability Is Still Hard: Fragmented Systems and Interfaces
Healthcare has a vendor-driven ecosystem with fragmented architecture.
Many departments adopt separate systems (“best of breed”), but pressure exists to consolidate.
Interfaces and integration are not the same. Systems can be connected but not truly interoperable.
Point-to-point interfaces require translation when systems define things differently (like gender as male/female vs 0/1). In an example, one order required nine separate interfaces, creating complexity, fragility, and high maintenance cost.
XXII. HL7 and FHIR: Moving Toward Modern Exchange
HL7 version 2 became the backbone of hospital data exchange, but vendor customization limits true interoperability, making it more like a guideline in practice.
FHIR (“FIRE”) introduced in 2012 supports modern API-based exchange and is preferred for new apps and AI integrations.
Together, HL7v2 and FHIR show the evolution from legacy interfaces to flexible API-based architecture.
XXIII. Security, Mobility, Analytics, and Operations: The Modern Pressures
A. Security as Patient Safety
Cybersecurity is shaped by major events (Conficker, WannaCry, ransomware). It is not just an IT issue; it is a patient safety issue.
B. Mobility and “Five Nines” Reliability
Mobility drives connectivity expectations, and EHRs need 99.999% uptime. Mobility adds costs and vulnerabilities through device management, network upgrades, depreciation cycles, BYOD, and cloud adoption.
C. Analytics and AI Growth
Value-based care drives demand for analytics, requiring integration across systems and governance. AI becomes a powerful tool within analytics but requires clean data, governance, and monitoring.
D. Operations as Strategic
Operations includes infrastructure, redundancy tiers, cloud migration choices, disaster recovery, and big data workloads. Downtime is dangerous, making operations strategic.
XXIV. Ending Question That Frames the Whole Topic
The big question is whether IT investments are making care better, safer, and smarter—or just more complex.
I. Why Managing Information and Technology Matters in Healthcare
Healthcare is unique because medical care has many complexities and many complex needs. Traditional approaches are no longer able to meet the complex needs of medical care, and traditional processes no longer are able to meet the new models of healthcare delivery that are constantly emerging. It used to be that doctors or a few personnel could manage healthcare organizations, but administrative tasks have become so complex and so vast over time that you cannot rely on traditional processes.
Healthcare is urgently seeking improved cost and quality performance by using information systems in innovative ways. Using information technology innovation and introducing innovations to improve performance in healthcare is necessary for two purposes: providing relief from mundane manual tasks, and using new technologies as they become available—mobile computing, internet of things, telemedicine, genomic data, secure networks—to improve care, improve quality, improve efficiency, and make administrative tasks much more efficient.
As students of healthcare and future healthcare workers, you need to understand the basics to work in healthcare today in any capacity.
II. Building Blocks: Information Technology, Information Systems, and Applications
A. Information Technology
Information technology is a broad term describing the combination of computers and electronic devices, hardware and software, local and internet network infrastructures, and data including images, videos, and voice across all industries.
B. Information System
An information system is an arrangement of data, processes, people, and information technology that interact to collect, process, store, and provide as output the information needed to support the organization.
Information technology is a component of every information system, but the term includes technologies within and outside of an organization.
C. Applications as Components of Information Systems
From an organizational perspective, computer applications are components of information systems needed to support specific processes.
In this course segment, the main focus is managing information, information systems, and data. Although there are many types of information systems, the primary focus is on two types:
Administrative applications
Clinical applications
III. Why Automate Healthcare Using Health Information Systems
A. The Core Justification for Automation
There are three major reasons to automate healthcare using health information systems:
Improve the quality of care
Improve the efficiency of care
Improve administrative processes
Health information systems should be aligned with these goals.
B. Healthcare Has Many Stakeholders
When you think about a healthcare organization and the stakeholders involved in the delivery of care, there are many: patients, clinicians, administrative personnel, government, public health organizations, quality improvement organizations, payers, insurance, and many others.
Because healthcare includes many participants and complex needs, information exchange and coordination become essential, and information systems become necessary to manage that complexity.
IV. The Big Picture: Challenges Driving the Need for Better Information Systems
To understand the need for better information systems, it helps to describe the current challenges healthcare is facing.
A common way to think about improving medical care is the so-called triple aim:
Improving outcomes
Reducing costs
Ensuring quality
You may also see different wording for these goals, such as improving population health or improving patient experience.
The challenges that tie to information systems management include cost, access, quality, evidence-based medicine, and broad organizational changes.
V. Cost: Why Healthcare Spending Forces System Change
United States per capita healthcare spending is more than twice the average of other developed countries. Total healthcare spending, public and private, is projected to rise to about one-fifth of the economy.
Healthcare experts estimate about 30% of total healthcare spending is unnecessary, leading to ineffective, inefficient, overpriced, and wasteful services. These costs are projected to keep rising faster than inflation, wages, or the overall economy.
A. Why Costs Rise
The rise in healthcare costs originates from several factors:
Shift toward an older population
This is a function of rising life expectancy, rising from the 1970s to about 80 after the 2000s. Older patients will need healthcare, will get ill, will need treatments, and treatments will be more expensive.Chronic illnesses such as obesity and diabetes
Chronic diseases increase the risk of other conditions. Patients with chronic conditions are harder to treat and account for the vast majority of healthcare expenditures.Misaligned incentives
Misaligned incentives and provider reimbursement contribute to unnecessary and inefficient spending.Advancing technology
As the cost of equipment for expensive tests like MRI and CT scans has increased, the portion of healthcare expenditure due to advanced technology has risen.
VI. Access: Why Coverage and Care Delivery Require Better Information Exchange
A. Insurance as a Measure of Access
When we say access, the immediate thing to think of is insurance. Insurance is one measure for access to care. It has changed tremendously over the years, going down in a positive direction and stabilizing in the last few years at around 8%, though it is expected to rise.
B. Public and Private Insurance Structure
There are two major components:
Private insurance companies
Public insurance companies
Public insurance includes Medicare, Medicaid, and the VA. Public and private are close to one another in how much is paid, but private plans take a big chunk of insured people, and many private plans are employment-based.
C. Access Creates System Strain Without Better Systems
Information systems can assist in providing better access to care. But if access problems are solved, that will strain the system by adding care demands for additional millions of people.
That requires better information exchange and coordination of care.
Disparities exist across demographics and across states, including differences between Medicaid expansion and non-expansion states.
VII. Quality: Why Outcomes Don’t Match Spending
There is evidence of quality and value issues in the US healthcare system.
Excess preventable deaths were demonstrated by the Institute of Medicine in 1999. The report To Err Is Human identified that close to hundreds of thousands of people are dying as a result of preventable medical errors.
Although the United States spends more on healthcare than any other developed countries, health outcomes are generally no better. Comparisons include major categories such as health status, quality of primary care, and quality of acute care, with metrics like life expectancy, mortality, unmanaged chronic conditions, and childbirth safety.
VIII. Evidence-Based Medicine: Why Information Must Reach the Point of Care
Evidence-based medicine is an information management and learning strategy that seeks to integrate clinical expertise with the best evidence available to make effective clinical decisions that ultimately improve patient care.
Standards and practice guidelines need to be incorporated into day-to-day operations, so the use of information is essential.
However, achieving evidence-based medicine is difficult. You need the right information and the right guideline presented to the provider at the point of care. You need a process and workflow. You must ensure clinicians adhere to protocols, and if they override protocols, you need to understand why they are overriding and using non-standard care actions.
Information systems play a big role in achieving evidence-based medicine.
IX. Organizational Change: Government, Markets, and Delivery Models
There are powerful influences on how health information systems are used, including government and market forces, and sometimes these are in different directions.
Government regulates and passes laws governing implementation and use of health information systems. The free market encourages commercialization of health information system products and services. As a student of health information systems, you need to understand how the business of healthcare works.
A major challenge is broad organizational change, especially in publicly financed healthcare systems. Market-oriented reforms aim to make resource allocation more efficient, more innovative, and more responsive to consumer preferences while maintaining equity.
In a market-oriented system, the preferences and values of patients, combined with information about how they can fulfill their preferences, drive decision making.
Managed care is a system in which patients agree to visit only certain doctors and hospitals and the cost of treatment is monitored. Managed care was a solution in the 1990s, but in the last decade newer delivery models have grown, including accountable care organizations and patient-centered medical homes.
These incentives, delivery changes, and organizational requirements tie directly to information systems.
X. What You Need to Know as a Health Information Student
If you’re wondering where to start, ask: what are these systems used for inside healthcare organizations?
You do not need to know how to program. What you need to understand is how to evaluate, choose, and use health information systems to solve problems in clinical operations, patient engagement, and strategic planning.
Whether it’s an electronic health record, imaging system, or enterprise dashboard, the job is to match the right tool to the right purpose and help the organization use it effectively.
XI. Crossing the Quality Chasm: Four Reasons Quality Struggles
The report Crossing the Quality Chasm identified four major reasons why the US healthcare system struggles with quality:
A gap between innovation and implementation
The system was built around acute illness, but now faces a growing burden of chronic diseases
Inadequate use of information technology—data exists, but is not used to improve care delivery
Conflicting incentives in the payment system, rewarding volume instead of value
Health informatics addresses these by closing implementation gaps, supporting chronic care coordination, improving IT use, and enabling performance-based models.
XII. Policies That Shaped Health Information Systems
A. HIPAA (1996)
Health Insurance Portability and Accountability Act of 1996. When you hear HIPAA, think privacy and security of protected health information.
B. Medicare Prescription Drug Improvement and Modernization Act (2003)
Critical for introducing standards for electronic prescribing as an early step toward electronic health records. During this time, the Office of the National Coordinator of Health IT (within HHS) was established.
C. ARRA / HITECH (2009)
Provided stimulus money for electronic health record adoption: $25 billion of incentives for hospitals and physicians who adopt and meaningfully use EHRs.
Meaningful use criteria served as certification criteria for EHR features, functions, reporting, and interoperability capabilities within standards.
These legislations have had a huge influence on how health information systems have been shaped over the years.
XIII. Patient Engagement and Public Health: Two Stakeholders That Change Everything
A. Patient Engagement as Co-Production of Care
Healthcare is unique because care is not only delivered by providers. If a patient does not adhere to recommendations or does not watch their health, outcomes may not be as intended.
Care is co-production: the provider is not the only contributor. The patient or consumer has an important role.
Engaging patients across the continuum of care is critical, and technologies like internet, email, smartphones, mobile devices, and social media have a place in health information systems. At the same time, they create demands for security, privacy, and confidentiality.
B. Public Policy and Public Health
Public policy and public health are key stakeholders.
Public health can provide alerts for disease outbreaks, study effectiveness of treatments, improve quality of health services, and maintain population health status.
I. Why Managing Information and Technology Matters in Healthcare
Healthcare is unique because medical care has many complexities and many complex needs. Traditional approaches are no longer able to meet the complex needs of medical care, and traditional processes no longer are able to meet the new models of healthcare delivery that are constantly emerging. It used to be that doctors or a few personnel could manage healthcare organizations, but administrative tasks have become so complex and so vast over time that you cannot rely on traditional processes.
Healthcare is urgently seeking improved cost and quality performance by using information systems in innovative ways. Using information technology innovation and introducing innovations to improve performance in healthcare is necessary for two purposes: providing relief from mundane manual tasks, and using new technologies as they become available—mobile computing, internet of things, telemedicine, genomic data, secure networks—to improve care, improve quality, improve efficiency, and make administrative tasks much more efficient.
As students of healthcare and future healthcare workers, you need to understand the basics to work in healthcare today in any capacity.
II. Building Blocks: Information Technology, Information Systems, and Applications
A. Information Technology
Information technology is a broad term describing the combination of computers and electronic devices, hardware and software, local and internet network infrastructures, and data including images, videos, and voice across all industries.
B. Information System
An information system is an arrangement of data, processes, people, and information technology that interact to collect, process, store, and provide as output the information needed to support the organization.
Information technology is a component of every information system, but the term includes technologies within and outside of an organization.
C. Applications as Components of Information Systems
From an organizational perspective, computer applications are components of information systems needed to support specific processes.
In this course segment, the main focus is managing information, information systems, and data. Although there are many types of information systems, the primary focus is on two types:
Administrative applications
Clinical applications
III. Why Automate Healthcare Using Health Information Systems
A. The Core Justification for Automation
There are three major reasons to automate healthcare using health information systems:
Improve the quality of care
Improve the efficiency of care
Improve administrative processes
Health information systems should be aligned with these goals.
B. Healthcare Has Many Stakeholders
When you think about a healthcare organization and the stakeholders involved in the delivery of care, there are many: patients, clinicians, administrative personnel, government, public health organizations, quality improvement organizations, payers, insurance, and many others.
Because healthcare includes many participants and complex needs, information exchange and coordination become essential, and information systems become necessary to manage that complexity.
IV. The Big Picture: Challenges Driving the Need for Better Information Systems
To understand the need for better information systems, it helps to describe the current challenges healthcare is facing.
A common way to think about improving medical care is the so-called triple aim:
Improving outcomes
Reducing costs
Ensuring quality
You may also see different wording for these goals, such as improving population health or improving patient experience.
The challenges that tie to information systems management include cost, access, quality, evidence-based medicine, and broad organizational changes.
V. Cost: Why Healthcare Spending Forces System Change
United States per capita healthcare spending is more than twice the average of other developed countries. Total healthcare spending, public and private, is projected to rise to about one-fifth of the economy.
Healthcare experts estimate about 30% of total healthcare spending is unnecessary, leading to ineffective, inefficient, overpriced, and wasteful services. These costs are projected to keep rising faster than inflation, wages, or the overall economy.
A. Why Costs Rise
The rise in healthcare costs originates from several factors:
Shift toward an older population
This is a function of rising life expectancy, rising from the 1970s to about 80 after the 2000s. Older patients will need healthcare, will get ill, will need treatments, and treatments will be more expensive.Chronic illnesses such as obesity and diabetes
Chronic diseases increase the risk of other conditions. Patients with chronic conditions are harder to treat and account for the vast majority of healthcare expenditures.Misaligned incentives
Misaligned incentives and provider reimbursement contribute to unnecessary and inefficient spending.Advancing technology
As the cost of equipment for expensive tests like MRI and CT scans has increased, the portion of healthcare expenditure due to advanced technology has risen.
VI. Access: Why Coverage and Care Delivery Require Better Information Exchange
A. Insurance as a Measure of Access
When we say access, the immediate thing to think of is insurance. Insurance is one measure for access to care. It has changed tremendously over the years, going down in a positive direction and stabilizing in the last few years at around 8%, though it is expected to rise.
B. Public and Private Insurance Structure
There are two major components:
Private insurance companies
Public insurance companies
Public insurance includes Medicare, Medicaid, and the VA. Public and private are close to one another in how much is paid, but private plans take a big chunk of insured people, and many private plans are employment-based.
C. Access Creates System Strain Without Better Systems
Information systems can assist in providing better access to care. But if access problems are solved, that will strain the system by adding care demands for additional millions of people.
That requires better information exchange and coordination of care.
Disparities exist across demographics and across states, including differences between Medicaid expansion and non-expansion states.
VII. Quality: Why Outcomes Don’t Match Spending
There is evidence of quality and value issues in the US healthcare system.
Excess preventable deaths were demonstrated by the Institute of Medicine in 1999. The report To Err Is Human identified that close to hundreds of thousands of people are dying as a result of preventable medical errors.
Although the United States spends more on healthcare than any other developed countries, health outcomes are generally no better. Comparisons include major categories such as health status, quality of primary care, and quality of acute care, with metrics like life expectancy, mortality, unmanaged chronic conditions, and childbirth safety.
VIII. Evidence-Based Medicine: Why Information Must Reach the Point of Care
Evidence-based medicine is an information management and learning strategy that seeks to integrate clinical expertise with the best evidence available to make effective clinical decisions that ultimately improve patient care.
Standards and practice guidelines need to be incorporated into day-to-day operations, so the use of information is essential.
However, achieving evidence-based medicine is difficult. You need the right information and the right guideline presented to the provider at the point of care. You need a process and workflow. You must ensure clinicians adhere to protocols, and if they override protocols, you need to understand why they are overriding and using non-standard care actions.
Information systems play a big role in achieving evidence-based medicine.
IX. Organizational Change: Government, Markets, and Delivery Models
There are powerful influences on how health information systems are used, including government and market forces, and sometimes these are in different directions.
Government regulates and passes laws governing implementation and use of health information systems. The free market encourages commercialization of health information system products and services. As a student of health information systems, you need to understand how the business of healthcare works.
A major challenge is broad organizational change, especially in publicly financed healthcare systems. Market-oriented reforms aim to make resource allocation more efficient, more innovative, and more responsive to consumer preferences while maintaining equity.
In a market-oriented system, the preferences and values of patients, combined with information about how they can fulfill their preferences, drive decision making.
Managed care is a system in which patients agree to visit only certain doctors and hospitals and the cost of treatment is monitored. Managed care was a solution in the 1990s, but in the last decade newer delivery models have grown, including accountable care organizations and patient-centered medical homes.
These incentives, delivery changes, and organizational requirements tie directly to information systems.
X. What You Need to Know as a Health Information Student
If you’re wondering where to start, ask: what are these systems used for inside healthcare organizations?
You do not need to know how to program. What you need to understand is how to evaluate, choose, and use health information systems to solve problems in clinical operations, patient engagement, and strategic planning.
Whether it’s an electronic health record, imaging system, or enterprise dashboard, the job is to match the right tool to the right purpose and help the organization use it effectively.
XI. Crossing the Quality Chasm: Four Reasons Quality Struggles
The report Crossing the Quality Chasm identified four major reasons why the US healthcare system struggles with quality:
A gap between innovation and implementation
The system was built around acute illness, but now faces a growing burden of chronic diseases
Inadequate use of information technology—data exists, but is not used to improve care delivery
Conflicting incentives in the payment system, rewarding volume instead of value
Health informatics addresses these by closing implementation gaps, supporting chronic care coordination, improving IT use, and enabling performance-based models.
XII. Policies That Shaped Health Information Systems
A. HIPAA (1996)
Health Insurance Portability and Accountability Act of 1996. When you hear HIPAA, think privacy and security of protected health information.
B. Medicare Prescription Drug Improvement and Modernization Act (2003)
Critical for introducing standards for electronic prescribing as an early step toward electronic health records. During this time, the Office of the National Coordinator of Health IT (within HHS) was established.
C. ARRA / HITECH (2009)
Provided stimulus money for electronic health record adoption: $25 billion of incentives for hospitals and physicians who adopt and meaningfully use EHRs.
Meaningful use criteria served as certification criteria for EHR features, functions, reporting, and interoperability capabilities within standards.
These legislations have had a huge influence on how health information systems have been shaped over the years.
XIII. Patient Engagement and Public Health: Two Stakeholders That Change Everything
A. Patient Engagement as Co-Production of Care
Healthcare is unique because care is not only delivered by providers. If a patient does not adhere to recommendations or does not watch their health, outcomes may not be as intended.
Care is co-production: the provider is not the only contributor. The patient or consumer has an important role.
Engaging patients across the continuum of care is critical, and technologies like internet, email, smartphones, mobile devices, and social media have a place in health information systems. At the same time, they create demands for security, privacy, and confidentiality.
B. Public Policy and Public Health
Public policy and public health are key stakeholders.
Public health can provide alerts for disease outbreaks, study effectiveness of treatments, improve quality of health services, and maintain population health status.
XIV. Why the Terminology Feels Confusing
Terms like medical informatics, nursing informatics, clinical informatics, and healthcare IT often overlap. The terminology is not always used consistently and there is no standard definition.
For this course, health informatics is the practical and organizational use of information systems to improve care. It is not just about building technology; it is about solving healthcare problems using data systems and smart design.
XV. The Three Pillars: IT, Informatics, Analytics
For the purpose of this course, there are three pillars:
A. Health IT
Health IT is about managing information technology:
Disaster recovery
How data flows in an organization
Servers
B. Analytics
Analytics is about using the information created by these systems.
C. Informatics
Healthcare informatics sits between IT and analytics.
It is about managing data: how to keep it, manage it, organize it.
This is where IT-based interventions are designed to improve care and operations.
XVI. The DIKW Model: How Informatics Turns Data Into Better Care
The goal of health informatics is not just to collect data, but to transform it into something meaningful and actionable.
Data: raw facts like measurements, orders, clicks, time stamps
Information: cleaned and structured data, like a list of abnormal labs
Knowledge: actionable information with context, like rising creatinine indicating kidney injury
Wisdom: when actionable information becomes part of operations through interventions like clinical decision support alerts or automated protocols
In today’s environment, interventions might involve machine learning models, FHIR APIs, or automated alerts, but the principle stays the same: using technology to improve decisions and outcomes.
XVII. DIKW Examples: Clinical and Operational
A. CHF Patient Portal Example
Data: 87,000 patient portal users
Information: identify which users have CHF and whether they use the portal
Knowledge: CHF patients are frequently readmitted, and portal use can be measured
Wisdom: CHF patients who use the portal are readmitted less often, creating a rationale for encouraging portal use during discharge or follow-up
B. Bandwidth Example
Data: 1 GB internet minimum for normal hospital operations
Information: visitors consume bandwidth needed for clinical use
Knowledge: Wednesdays have a spike in volume and network performance suffers
Wisdom: usage correlates with admissions, so bandwidth should be adjusted dynamically through traffic shaping or added capacity
XVIII. How Emerging Technologies Mature: The Hype Cycle
Technological innovations follow a predictable path from early development to widespread adoption.
Expectations rise, realities are discovered, and then things stabilize.
This model helps decision makers evaluate whether technology is experimental, ready for early adoption, or becoming a standard—rather than going by market hype.
XIX. A Short History of Health IT: Why Today Looks the Way It Does
1950s: mainframes used for administrative purposes like processing claims
1960s: minicomputers enabled organizations to process information inside the organization
MUMPS: database and programming language still used as underlying structure in Epic
1969: TCP/IP developed, enabling internet communication layers
1970s: relational databases introduced (think Excel sheets connected to one another)
1981: IBM PC release, enabling smaller-scale organizational computation
HL7 introduced as a standard for machine communication and interoperability
2007–2008: Conficker virus brought security to the national stage
2009 onward: HITECH and later reforms influenced EHR adoption, interoperability, and payment model shifts
XX. Five Domains of the Health IT Environment: Where Data Comes From
Data comes from five domains:
Workload and applications (clinical/admin operations, EHRs, instrumentation)
Data communication (wired/wireless/cellular, enabling secure flow)
IT analytics (integration, governance, business rules, turning raw data into insights)
Operations platform (servers, cloud, virtualization, disaster recovery)
Information security (access controls, audit trails, encryption, compliance across all domains)
Understanding how these interact is critical for managing, securing, and analyzing data in any informatics initiative.
XXI. Why Interoperability Is Still Hard: Fragmented Systems and Interfaces
Healthcare has a vendor-driven ecosystem with fragmented architecture.
Many departments adopt separate systems (“best of breed”), but pressure exists to consolidate.
Interfaces and integration are not the same. Systems can be connected but not truly interoperable.
Point-to-point interfaces require translation when systems define things differently (like gender as male/female vs 0/1). In an example, one order required nine separate interfaces, creating complexity, fragility, and high maintenance cost.
XXII. HL7 and FHIR: Moving Toward Modern Exchange
HL7 version 2 became the backbone of hospital data exchange, but vendor customization limits true interoperability, making it more like a guideline in practice.
FHIR (“FIRE”) introduced in 2012 supports modern API-based exchange and is preferred for new apps and AI integrations.
Together, HL7v2 and FHIR show the evolution from legacy interfaces to flexible API-based architecture.
XXIII. Security, Mobility, Analytics, and Operations: The Modern Pressures
A. Security as Patient Safety
Cybersecurity is shaped by major events (Conficker, WannaCry, ransomware). It is not just an IT issue; it is a patient safety issue.
B. Mobility and “Five Nines” Reliability
Mobility drives connectivity expectations, and EHRs need 99.999% uptime. Mobility adds costs and vulnerabilities through device management, network upgrades, depreciation cycles, BYOD, and cloud adoption.
C. Analytics and AI Growth
Value-based care drives demand for analytics, requiring integration across systems and governance. AI becomes a powerful tool within analytics but requires clean data, governance, and monitoring.
D. Operations as Strategic
Operations includes infrastructure, redundancy tiers, cloud migration choices, disaster recovery, and big data workloads. Downtime is dangerous, making operations strategic.
XXIV. Ending Question That Frames the Whole Topic
The big question is whether IT investments are making care better, safer, and smarter—or just more complex.
Lecture 2: Healthcare Informatics: How Healthcare Data Moves Through the Healthcare System and Creates Value
I. Healthcare Functions as an Information System
Healthcare should be understood not only as a clinical service but as a large information system.
Every action that occurs inside healthcare generates data. When a patient schedules an appointment, reports symptoms, undergoes testing, receives treatment, or makes a payment, information is created. That information must move correctly between people, departments, and organizations for care to succeed.
Clinical decisions depend on accurate information. Administrative operations depend on accurate information. Financial sustainability depends on accurate information. Because of this, healthcare becomes one of the most information-intensive industries in existence.
Modern healthcare organizations are not attempting merely to store records. The real objective is transforming collected data into value. Value appears when information improves outcomes, supports clinician reasoning, enables coordination among providers, strengthens operational efficiency, and allows organizations to plan strategically.
Understanding healthcare informatics therefore begins with understanding how information moves, who uses it, and how it influences decisions across the entire system.
II. Data, Information, and Knowledge
A. What Healthcare Data Represents
Healthcare data consists of raw observations recorded during care delivery.
These observations include:
measurements such as blood pressure,
laboratory values,
diagnosis codes,
medication entries,
clinical notes,
administrative identifiers.
At this stage, data represents isolated facts. A number such as a laboratory result does not communicate meaning by itself. Without context, interpretation is impossible.
Healthcare professionals continuously generate enormous amounts of these raw elements during routine care activities.
B. How Data Becomes Information
Data becomes useful only after structure is applied.
When healthcare data is organized, categorized, and interpreted within clinical or operational context, it becomes information. For example, a laboratory value gains meaning when compared with normal ranges, previous measurements, or patient history.
Information answers questions such as:
Is the patient improving?
Is a condition worsening?
Does intervention need adjustment?
This step transforms disconnected facts into meaningful understanding.
C. Knowledge and Decision Making
When information guides action, it becomes knowledge.
Knowledge allows clinicians to diagnose conditions, managers to allocate resources, and organizations to improve processes. Healthcare informatics exists to ensure that the transformation from data to knowledge happens reliably and efficiently.
The progression can be understood as:
Data → Structured Information → Knowledge → Clinical or Organizational Action
Failures at any stage weaken decision making and ultimately affect patient outcomes.
D. Using Data to Evaluate Healthcare Performance
Healthcare quality cannot be evaluated without measurable information.
An organization may appear admirable because it demonstrates empathy, consistent performance, or effective resource management. However, these qualities must be supported by measurable evidence.
This requires determining:
which data should be collected,
which metrics represent performance,
whether collected data is accurate,
and whether resulting insights are valid.
These questions form the basis of strategic healthcare management and explain why informatics plays a central role in leadership and organizational improvement.
III. Medicine as Information Management
Medicine fundamentally involves managing information under uncertainty.
Clinicians continuously gather information from multiple sources:
patient-reported symptoms,
physical examinations,
laboratory testing,
imaging studies,
prior medical history.
All of this information must be synthesized rapidly.
Historically, physicians relied on relatively small datasets. Modern healthcare dramatically increases informational complexity. A single patient encounter may now involve hundreds or thousands of data elements.
Technology introduces risk when poorly designed systems interfere with thinking processes. Excessive clicking, navigation complexity, or fragmented displays may interrupt clinical reasoning and weaken patient interaction.
The objective of health information technology is therefore not automation for its own sake. The objective is supporting clinical reasoning so that improved information management produces improved care.
IV. Early Digitization of Healthcare Information
A. Computerized Hospital Systems in the 1960s
Efforts to digitize healthcare information began decades ago.
Hospitals installed computer terminals in admitting departments and nursing stations. When patients were admitted, identifying information was entered electronically and transmitted throughout the hospital.
Physicians and nurses entered medication and diagnostic orders directly into terminals. Central computers distributed these orders automatically to ancillary departments such as laboratories or pharmacies.
Medication reminders ensured drugs were administered at correct times and dosages.
B. Early Recognition of Informatics Value
Even these early systems demonstrated critical advantages:
reduction of paperwork burden,
improved coordination across departments,
correlation of disease information,
reduction of harmful medication errors.
The essential insight already existed: structured information access improves patient safety and clinical efficiency.
C. Persistence of the Central Challenge
Technological capability has expanded dramatically since that time. Healthcare now manages massive datasets, numerous software systems, and expectations for real-time interoperability.
However, the fundamental challenge remains unchanged:
How can systems provide enough information to support clinicians without overwhelming or distracting them?
Designing effective health IT continues to revolve around balancing information availability with cognitive usability.
V. Technology and the Human Relationship in Medicine
Healthcare technology often creates concern that care may become impersonal.
Images depicting clinicians interacting primarily with computers highlight fears that technology could weaken patient relationships. These concerns reflect workflow design problems rather than resistance to innovation.
Clinicians typically adapt quickly when technology supports their work. Difficulties arise when systems fail to align with real clinical needs.
Handwritten records filled with abbreviations and informal notes demonstrate adaptation when tools are inadequate. Adoption success therefore depends on whether systems genuinely improve thinking, efficiency, and care delivery.
Technology must enhance—not replace—the human side of medicine.
VI. Paper Records and Digital Trade-Offs
A. Why Paper Records Feel Effective
Paper records provide flexibility. Providers can write freely, annotate margins, sketch diagrams, and navigate information quickly through physical interaction.
These characteristics make paper workflows feel natural.
B. Limitations of Paper Systems
Despite familiarity, paper introduces serious limitations:
information cannot be searched efficiently,
sharing across providers becomes difficult,
duplication and loss occur easily,
analytics and decision support are impossible,
coordination across teams slows significantly.
Understanding both advantages and limitations helps guide better digital system design.
VII. Viewing Healthcare Through Patient Journeys
A. Chronic Disease from the Patient Perspective
A patient with COPD may begin with a minor symptom such as chronic cough. Over time, care expands into physician visits, diagnostic testing, medication management, home therapy, and acute complications.
The journey is not linear.
Information may be lost during transitions, misunderstood during communication, or ignored when follow-up fails. Medication non-adherence often results from informational gaps rather than intentional behavior.
Informatics systems must therefore maintain continuity and ensure that patients remain connected to care throughout complex journeys.
B. Healthcare System Perspective
Heart failure care illustrates how patients move between home monitoring, emergency treatment, hospitalization, and follow-up care.
Each transition requires new information:
weight trends,
laboratory markers,
imaging findings,
symptom reporting.
Care quality depends on whether systems successfully capture and share this information across settings.
Informatics connects otherwise fragmented healthcare environments.
C. Process Perspective of Surgical Care
Surgical care highlights healthcare as a coordinated process involving preparation, hospitalization, and recovery.
Patients experience anxiety and administrative burden during this process. Informatics identifies opportunities to digitize workflows, improve communication, and reduce friction.
Journey mapping allows organizations to improve both operational efficiency and patient experience simultaneously.
VIII. Fundamental Healthcare Information Structures
A. Healthcare Data and Protected Information
Healthcare data becomes healthcare information once structured and interpreted. When identifiable information relates to treatment or payment, it becomes Protected Health Information requiring controlled access and privacy protection.
B. Types of Digital Health Records
Electronic Medical Records (EMR)
Digital charts maintained within one organization supporting diagnosis and treatment tracking.
Electronic Health Records (EHR)
Records designed to follow patients across multiple care settings, integrating information from laboratories, specialists, and hospitals while enabling decision support and reporting.
Personal Health Records (PHR)
Patient-managed systems allowing individuals to store and manage information from multiple providers.
C. Scope of Care
Healthcare analysis occurs at multiple levels:
Episode of care focuses on specific treatment periods.
Continuum of care spans services across time and settings.
Population health examines outcomes affecting groups and includes social determinants such as housing and environment.
IX. Purpose and Structure of Patient Records
Patient records simultaneously support clinical care, provider communication, legal accountability, billing processes, research activities, and population health monitoring.
Records accumulate layered information including demographics, problem lists, medications, examinations, progress notes, orders, laboratory results, imaging reports, operative findings, and discharge summaries.
Each layer contributes to informed decision making throughout care delivery.
X. Clinical vs Administrative Information
A. Clinical Information
Supports diagnosis and treatment decisions through observations, tests, and clinical documentation.
B. Administrative Information
Supports operations through registration data, insurance information, consent forms, and billing codes.
C. Aggregate Information
Combining information across patients allows organizations to track trends, manage quality, allocate resources, and plan strategically.
Healthcare informatics therefore connects individual care with organizational management.
XI. Documentation Organization and Clinical Reasoning
A. Source-Oriented Records
Information grouped by origin such as laboratory reports or physician notes.
B. Problem-Oriented Records and SOAP
Subjective
Patient-reported experiences.
Objective
Measured findings.
Assessment
Clinical interpretation.
Plan
Next clinical actions.
SOAP documentation structures clinical reasoning and tracks patient status over time.
XII. Modern Electronic Health Record Capabilities
Electronic health records capture patient information, manage results, enable electronic ordering, provide decision support, support communication, engage patients, manage administrative workflows, and generate reporting for quality improvement and population health management.
EHR systems therefore integrate bedside care with organizational operations.
XIII. Clinical Decision Support and Interoperability
A. Clinical Decision Support Systems
Combine patient data, medical knowledge, and algorithms to generate alerts, reminders, and recommendations that reduce errors and improve care quality.
B. Health Information Exchange
Allows secure sharing of information through directed exchange, query-based retrieval, and patient-controlled exchange, enabling coordinated care across organizations.
XIV. What Electronic Health Records Have Achieved in Healthcare
Electronic Health Records have now been widely adopted across healthcare systems. Because they are deeply integrated into everyday clinical work, it becomes important to understand what organizations have actually gained from their implementation.
Research consistently shows that the impact of electronic health records appears across three major areas: quality and safety, efficiency and financial performance, and provider and patient experience.
A. Improvement of Quality Outcomes and Patient Safety
Electronic health records help healthcare organizations follow evidence-based care more consistently.
Because patient information is continuously available and updated over time, clinicians can monitor disease progression instead of relying only on isolated visits. Trends become visible. Changes in laboratory values, medications, or symptoms can be tracked longitudinally rather than reconstructed from memory or fragmented records.
Decision support tools embedded within EHR systems reinforce clinical standards directly at the point of care. Alerts may identify medication conflicts, missing screenings, or abnormal findings requiring attention.
This continuous visibility reduces medication errors and adverse clinical events. Patient monitoring improves because clinicians can recognize deterioration earlier and intervene sooner.
The key idea is that structured information improves clinical awareness, and improved awareness improves safety.
B. Efficiency and Cost Performance
Electronic health records streamline workflows that were historically manual.
Before digital systems, providers repeatedly documented the same information across departments. Tests were duplicated because prior results were unavailable. Administrative communication required physical transfer of documents.
EHR systems reduce duplication by allowing shared access to information. Documentation entered once becomes available throughout the organization.
Improved documentation also strengthens billing accuracy. When services are clearly documented, organizations can appropriately capture reimbursement for care already delivered.
In this sense, electronic health records function not only as clinical tools but also as operational and financial management tools. Better documentation leads to improved revenue flow and organizational sustainability.
C. Provider and Patient Satisfaction
When electronic systems align with clinical workflows, communication improves among providers and between providers and patients.
Care coordination becomes smoother because teams share access to the same information. Patients gain better understanding of their care through improved communication and engagement tools.
However, satisfaction depends heavily on system design. Surveys show that poorly designed systems may frustrate clinicians, particularly when documentation requirements interfere with clinical interaction.
Benefits therefore depend on implementation quality rather than technology alone.
XV. Challenges Introduced by Electronic Health Records
While electronic health records provide significant benefits, they also introduce new problems that healthcare organizations must address.
A. Problem Lists Becoming Unreliable
The problem list is intended to summarize a patient’s major medical conditions.
Over time, however, entries may become outdated or incomplete. Conditions may remain listed after resolution, or new problems may not be added consistently.
When accuracy declines, clinicians lose trust in the list and may ignore it entirely. This reduces its intended value as a quick clinical summary.
Maintaining accurate shared information becomes an ongoing organizational responsibility.
B. Documentation or “Note” Bloat
Electronic documentation frequently relies on templates and copy-paste functionality.
Although these practices save time, studies show that more than half of EHR text may consist of duplicated material. Excessive documentation can obscure important clinical reasoning.
A patient record may grow extremely long, making it difficult for clinicians to quickly identify meaningful information.
Efficiency gained in documentation can therefore unintentionally reduce clarity.
C. Disruption of Clinical Cognitive Flow
Clinicians must often navigate multiple screens, enter structured data, and complete electronic workflows while simultaneously evaluating patients.
These activities may interrupt concentration and shift attention away from clinical reasoning.
Instead of thinking continuously about diagnosis or treatment, clinicians divide attention between patient interaction and system navigation.
This creates concern that technology may interfere with judgment if workflow design is not carefully managed.
D. Risk of Over-Reliance on Systems
Another concern involves dependence on structured systems.
If clinicians rely excessively on automated prompts or checklists, synthesis and independent reasoning may weaken over time.
The challenge is not abandoning electronic records but designing systems that support reasoning rather than replace it.
Training and thoughtful design remain essential.
XVI. Future Direction of Health Records: The IRIS Example
To understand future possibilities, consider the conceptual electronic medical record system called IRIS — Information Retrieval and Interaction Support.
This example demonstrates how technology can remain present in clinical care without distracting from patient interaction.
A. Pre-Visit Intelligence
Before entering the examination room, the system summarizes relevant patient information:
recent encounters,
chronic conditions,
prior visits,
home monitoring data submitted through patient portals.
The clinician begins the visit already informed rather than searching through records.
B. Continuous Context Awareness
During the encounter, the system highlights clinically important findings.
For example, it may identify declining laboratory values or missed follow-up communications and remind the clinician if attention shifts away from these issues.
Information becomes available exactly when needed rather than requiring manual retrieval.
C. Medication and Insurance Integration
Medication lists update dynamically during conversation.
Discontinued medications are removed, prescriptions renewed, and insurance coverage verified automatically. If insurance changes prevent coverage, the system recommends appropriate alternatives.
Clinical decision making and administrative requirements occur simultaneously.
D. Patient Engagement Beyond the Visit
Patients transmit home measurements such as blood pressure readings through portals.
The system schedules reminders automatically and tracks adherence over time. Care therefore extends beyond physical clinic encounters.
E. Retrieval of External Medical Records
When prior procedures are mentioned, interoperable systems retrieve outside medical records automatically.
Missed follow-ups caused by fragmented information become less likely because historical data remains accessible across organizations.
F. Clinical Decision Support in Diagnosis
Symptoms, family history, laboratory findings, and prior encounters combine to guide clinical reasoning.
In the example, symptoms and anemia prompt further investigation leading to colonoscopy scheduling and appropriate follow-up care.
The system supports—not replaces—the clinician’s reasoning process.
G. Automated Documentation and Billing
After the visit, documentation finalizes automatically and suggested billing codes appear.
Clinical care, documentation, and reimbursement become integrated components of a single workflow.
The central vision demonstrated here is technology that allows clinicians to remain focused on patients while maintaining full informational awareness.
XVII. Patient-Facing Technologies
Healthcare informatics increasingly extends beyond providers to patients themselves.
A. Personal Health Records (PHRs)
Personal Health Records are controlled by patients rather than healthcare organizations.
A PHR allows individuals to securely store and manage their own health information collected from multiple providers.
Although not legal medical records, they typically include diagnoses, medications, and immunizations.
When combined with mobile applications and wellness devices, patients begin generating their own health data.
PHRs shift ownership awareness toward patients and increase engagement in health management.
B. Patient Portals
Patient portals provide secure online access to healthcare information.
Through portals, patients can:
review test results,
view medication lists,
access visit summaries,
schedule appointments,
request refills,
message providers,
pay bills.
Administrative friction decreases while engagement increases.
C. Patient Portals as Decision Support Tools
Patient portals function as decision aids through three mechanisms.
First, patients gain access to the same information clinicians use, improving understanding.
Second, viewing results and progress increases patient activation. Activated patients are more likely to follow treatment plans, addressing the major problem of non-adherence.
Third, integration with personal health records allows patients to update information and participate collaboratively in decision making.
D. Co-Production of Care
Healthcare delivery depends on both provider effort and patient effort.
Providers prescribe treatments and design care plans, but outcomes ultimately depend on whether patients follow recommendations.
If medications are not taken or instructions ignored, treatment effectiveness declines.
Patient portals help bridge this gap by supporting participation and accountability.
XVIII. Revenue Cycle Management: Connecting Care to Payment
Healthcare organizations must sustain operations financially. The revenue cycle connects clinical services to reimbursement.
A. Registration
Care begins with patient registration where demographic and insurance information is collected.
Errors at this stage frequently lead to denied claims later.
B. Charge Capture
Clinical documentation recorded in the EHR converts services into billable activities.
Documentation directly drives financial outcomes.
C. Claims Submission
Claims representing provided services are submitted to insurance companies.
D. Claims Adjudication
Insurance companies review claims and determine approval or denial based on coverage rules.
E. Follow-Up and Patient Collection
Denied claims require correction. Remaining balances become patient responsibility.
The revenue cycle serves as the financial engine linking frontline care with organizational sustainability.
Perfect — continuing and completing the fully expanded master notes in the same teaching structure and flow.
XIX. How Clinical Documentation Becomes Billable Data: Coding Systems
After care is delivered and documented, healthcare organizations must translate clinical activity into standardized language that insurers understand. This translation process converts medical documentation into coded data, allowing reimbursement, analysis, and system-wide comparison.
Coding systems form the foundation connecting clinical care, administration, finance, and national healthcare analytics.
A. Purpose of Coding Systems
Clinical documentation describes what happened to a patient using narrative language. Insurance companies, regulators, and analysts cannot process narrative descriptions efficiently.
Coding systems solve this problem by converting documentation into standardized representations that answer three essential questions:
What condition did the patient have?
What services were performed?
Why was the service medically necessary?
Without standardized coding, reimbursement and large-scale healthcare analysis would not be possible.
B. ICD-10: Classification of Diseases
ICD-10 stands for International Classification of Diseases.
This system classifies diagnoses and health conditions. Every disease, injury, or health condition corresponds to a specific code.
ICD-10 replaced ICD-9 in the United States in 2015 and introduced significantly greater detail and specificity.
Two major components exist:
ICD-10-CM
Used to code diagnoses in both inpatient and outpatient settings.
This identifies what is wrong with the patient.
ICD-10-PCS
Used only for inpatient procedures performed during hospitalization, particularly surgeries.
Each procedure is described across multiple dimensions such as body region, approach, and method, allowing detailed clinical representation.
Every diagnosis encountered in healthcare must map to an ICD code.
C. CPT Codes: Describing Services Performed
CPT stands for Current Procedural Terminology, maintained by the American Medical Association.
While ICD codes describe conditions, CPT codes describe what providers actually did.
Examples include:
office visits,
laboratory tests,
imaging procedures,
outpatient treatments,
minor procedures.
For example, a moderately complex established patient office visit corresponds to CPT code 99213.
Together:
ICD explains the medical problem,
CPT explains the service delivered.
Insurance reimbursement depends on alignment between these two.
D. Diagnosis Related Groups (DRGs)
For inpatient hospital care, procedures and diagnoses combine into Diagnosis Related Groups (DRGs).
DRGs categorize hospital stays into standardized payment groups. Instead of paying separately for every activity, insurers reimburse hospitals based on the overall case classification.
This system links reimbursement to expected resource use rather than individual services.
E. From Documentation to Payment
Once codes are assigned:
Codes convert into dollar amounts using the hospital charge master.
Claims are submitted using standardized forms.
Insurance payers reimburse according to negotiated contracts rather than listed prices.
Pricing varies depending on:
payer type,
inpatient versus outpatient care,
contractual payment mechanisms.
Clinical documentation therefore directly determines organizational revenue.
XX. Administrative Data and Standardized Healthcare Datasets
Administrative data supports reimbursement, regulation, benchmarking, and national healthcare oversight.
A. Standard Billing Forms
Healthcare organizations submit claims using standardized datasets.
UB-04 / CMS-1450
Used for facility-based services such as hospitals.
CMS-1500
Used for individual providers and physician services.
These forms structure healthcare information so that payment systems and analytics platforms can process data consistently nationwide.
They are not simply paperwork. They represent structured national healthcare data infrastructure.
B. Uniform Healthcare Data Sets
Healthcare settings collect standardized administrative datasets including:
UHDDS (Uniform Hospital Discharge Data Set) for inpatient care,
ACDS (Ambulatory Care Data Set) for outpatient services,
MDS (Minimum Data Set) for long-term care facilities.
Each dataset captures consistent information across organizations.
C. Example: UHDDS
The Uniform Hospital Discharge Data Set includes:
patient demographics,
diagnoses,
procedures,
attending physicians,
admission and discharge dates,
discharge disposition,
expected payer.
This information supports billing but also feeds national statistics, benchmarking systems, and public health reporting.
Administrative data therefore extends far beyond reimbursement.
XXI. Aggregate Administrative Data and Organizational Management
When administrative data from many patients is combined, organizations generate aggregate insights.
Hospitals analyze:
average length of stay,
cost patterns,
reimbursement trends,
patient volumes,
discharge outcomes.
Managers use these reports for planning, compliance monitoring, and financial management.
Aggregate data enables organizations to produce unlimited analytical reports supporting operational improvement.
XXII. Comparative Data and Benchmarking
Healthcare organizations must evaluate performance relative to peers.
Comparative datasets allow benchmarking across regions and institutions.
A. Patient Satisfaction Measurement
Patient satisfaction is measured nationally using surveys such as HCAHPS.
Private organizations also provide comparative reporting.
These comparisons allow hospitals to evaluate patient experience performance relative to national standards.
B. Practice Pattern Comparison
Resources such as the Dartmouth Atlas reveal variation in care delivery across geographic regions.
Organizations identify:
overuse,
underuse,
variation in treatment patterns.
Comparative analysis supports quality improvement and alignment with value-based care models.
C. External Quality Reporting Organizations
Comparative data also comes from:
NCQA performance measures,
Joint Commission quality indicators,
CMS Hospital Compare,
CDC and AHRQ population health datasets.
These sources support transparency, accountability, and informed decision making.
XXIII. The Healthcare Data Explosion
Healthcare has become one of the most data-intensive industries in the world.
Data generation now occurs continuously rather than only during clinical visits.
Major contributors include:
electronic health records,
imaging systems producing large digital files,
wearable and mobile monitoring devices,
administrative and payer systems,
population health platforms.
Healthcare generates massive quantities of data daily, and growth continues accelerating.
XXIV. Major Pools of Healthcare Data
Healthcare data originates from multiple ecosystems.
A. Clinical Data
Generated by providers through EHRs, laboratory systems, and imaging.
B. Activity and Cost Data
Generated through claims and utilization tracking describing when care occurs and how much it costs.
C. Pharmaceutical and Research Data
Produced through clinical trials and biomedical research activities.
D. Patient Behavior and Sentiment Data
Generated outside traditional healthcare through wearable devices, retail interactions, fitness applications, and patient-reported experiences.
The greatest opportunities arise when these previously separate datasets connect.
XXV. Importance of Non-Clinical Data
Non-clinical data includes factors such as:
housing stability,
education,
food access,
transportation,
environmental conditions.
Although not traditionally captured in medical records, these factors strongly influence health outcomes.
Integrating clinical and non-clinical data shifts healthcare from reactive treatment toward proactive population strategy.
XXVI. Big Data in Healthcare
Healthcare exemplifies Big Data, defined by three characteristics:
Volume — massive quantities of information,
Velocity — continuous data generation,
Variety — diverse formats including structured and unstructured data.
Healthcare systems must manage all three simultaneously.
The challenge is not simply large data volume but fragmented, duplicative, and disconnected information.
XXVII. Core Data Management Challenges
Healthcare organizations face several structural challenges.
A. Data Ownership
Multiple stakeholders claim authority over data including clinicians, IT departments, and administrators.
B. Translation Across Systems
Data collected in one system must remain interpretable elsewhere.
C. Storage and Retrieval
Managing data involves structuring, archiving, and retrieving meaningful information rather than simply storing files.
D. Terminology Differences
Systems may label identical concepts differently, limiting interoperability.
E. System Interfacing
Connecting systems without data loss or error requires significant resources.
Turning data into actionable insight therefore remains difficult despite technological advances.
XXVIII. Privacy, Security, and Trust
Managing healthcare data requires protecting it.
HIPAA establishes rules governing storage, access, and sharing of patient information.
Organizations must:
control permissions,
maintain audit trails,
monitor access activity.
Security protects not only against unauthorized access but also patient trust. Without trust, patients may withhold information, weakening the healthcare system itself.
XXIX. The Central Reality of Modern Healthcare Informatics
Healthcare today is not merely data rich — it is data overwhelmed.
Data originates from clinical systems, administrative operations, mobile technologies, behavioral sources, and government programs.
The primary challenge is not collecting data but connecting fragmented systems and converting information into meaningful action.
The future of healthcare depends on the ability to:
connect data across stakeholders,
protect information responsibly,
interpret insights effectively,
and apply knowledge to improve care.
Informatics, analytics, and policy together enable this transformation.
Lecture 3: Healthcare IT Architecture and Interoperability in Healthcare Informatics
I. Foundations of Healthcare IT Architecture
A. The Central Question: Why IT Architecture Matters
Healthcare organizations depend on many technology systems to support clinical care, operations, billing, analytics, and decision-making. The fundamental issue is not simply having technology, but understanding how all technology systems fit together and function as one coordinated environment.
IT architecture represents the high-level blueprint of this environment. Just as a house blueprint reveals how rooms connect and what purpose the space serves before construction begins, IT architecture shows how healthcare systems are organized and how they support organizational goals.
Architecture is not infrastructure. Infrastructure refers to wiring, hardware, or networks. Architecture focuses on the overall structure — how systems are arranged, connected, and designed to meet organizational needs.
Because architecture determines how systems interact, it directly influences:
cost and efficiency,
quality of care,
patient safety,
operational performance,
and innovation capability.
A health system prioritizing patient safety may design architecture around redundancy and clinical decision support. Another focused on billing efficiency may structure systems to optimize coding and financial workflows. The architectural blueprint shapes everything that follows.
B. Architecture as Alignment Between Technology and Organizational Goals
Architecture is ultimately about aligning technology with organizational priorities. When organizations introduce new services such as telehealth platforms or analytics tools, architecture determines whether integration is smooth or difficult.
A well-designed architecture supports adaptation and growth. A poorly designed architecture makes every change costly and slow.
Architecture also affects:
security,
compliance,
disaster recovery,
and information flow across systems.
Technology therefore becomes either an organizational enabler or a barrier depending on architectural design.
II. Evolution of Healthcare IT Architecture
A. Competing Needs Driving Architectural Change
Healthcare IT architecture evolved as organizations attempted to balance two competing needs:
Specialized functionality for departments
Enterprise-wide data integration
Over time, three dominant architectural approaches emerged:
Monolithic architecture
Best of breed architecture
Best of cluster architecture
Each represents a response to limitations of the previous model.
III. Monolithic Architecture
A. Structure and Historical Context
Monolithic architecture represents the earliest computing model. All applications operated within a single centralized computing environment, typically supported by one vendor and one hardware platform. Systems such as the IBM 370 were housed in centralized data centers often called the glass house.
Everything ran through one system with tightly controlled operations and minimal software layering.
This approach marked the birth of commercial computing and shaped early organizational thinking about IT systems.
B. Advantages of Monolithic Systems
Centralization produced several benefits:
predictable cost control,
easier enforcement of standards,
simplified staffing and training,
straightforward disaster recovery planning,
simpler information integration since all data existed in one location.
With only one system, integration occurred naturally.
C. Limitations and Decline
Healthcare organizations proved too complex for a single system to support all functions effectively. Departments lost flexibility because specialized workflow tools could not be adopted.
Additional limitations included:
difficulty upgrading systems, often requiring complete replacement (“lift upgrades”),
poor negotiating power with vendors,
organizational vulnerability if the single system failed.
Because hospitals contain diverse clinical and operational needs, monolithic systems never became the dominant healthcare model and are now extremely rare.
IV. Best of Breed Architecture
A. Emergence of Department-Level Computing
During the 1980s and 1990s, personal computing became widely available. Departments gained the ability to select systems tailored to their own workflows.
Examples included:
laboratory systems using Cerner,
radiology selecting GE or Agfa imaging,
pharmacy adopting McKesson,
outpatient clinics running Allscripts,
billing departments maintaining standalone systems.
Business units gained significant influence over technology decisions.
B. Benefits of Departmental Freedom
Best of breed architecture allowed each department to obtain optimal functionality for its operations. This improved functional performance, accelerated adoption, and reduced organizational disruption when changes occurred locally.
Risk was also compartmentalized. Failure of one system did not necessarily shut down the entire hospital.
C. Integration Challenges
The downside emerged quickly. Organizations accumulated multiple hardware platforms, software environments, and communication protocols.
Common consequences included:
duplication of patient data,
need for highly specialized IT staff,
complex vendor management,
difficulty tracking costs,
expensive and fragile system integration.
For example, one system may record a patient as Robert Smith, another as Bob Smith, and another as R. Smith. When data is combined for analytics or clinical decisions, mismatches occur, sometimes resulting in duplicate testing or misinformation.
Healthcare CIOs often manage hundreds or thousands of systems under this model, creating substantial complexity.
V. Best of Cluster Architecture
A. Motivation for a Middle Ground
After experiencing integration difficulties with best of breed environments, organizations sought a balance between flexibility and integration.
Best of cluster architecture groups related functions into coordinated ecosystems such as:
clinical systems,
financial systems,
analytics platforms,
marketing or CRM systems.
B. Operational Advantages
Clustering allows strong integration within functional groups while reducing the number of independent vendors.
Benefits include:
improved integration compared to best of breed,
better enterprise cost control,
structured workflow management,
manageable vendor environments.
Organizations maintain some flexibility without managing dozens of disconnected systems.
C. Trade-Offs and Vendor Dependency
Departments may sacrifice perfect functional fit. Flexibility becomes limited, and dependence on large vendors increases.
Once organizations commit to a large cluster ecosystem, switching becomes difficult. This resembles entering a technology ecosystem such as Apple devices — seamless internally but difficult to leave.
VI. Real Hospital Operations and Architectural Complexity
A. A Single Patient Encounter Across Systems
Hospital IT complexity becomes clear when following one patient encounter.
When a patient arrives at the emergency department:
registration systems create records,
ED systems capture clinical documentation,
bed management systems activate,
laboratory orders initiate,
imaging requests occur,
pharmacy systems prepare medications.
If inpatient procedures are required, operating room scheduling, materials management, imaging, transcription, and additional systems become involved.
The EMR attempts to tie these activities together.
One encounter can activate more than a dozen systems, each potentially from different vendors. Every system handoff introduces a potential failure point if architecture is poorly designed.
B. Vendor Cluster Reality
Large vendors such as Epic and Cerner promote cluster-based ecosystems where modules such as radiology, pharmacy, surgery, and oncology integrate around a central EMR.
While marketed as seamless integration with fewer HL7 interfaces, many hospitals still experience patchwork environments. A system may appear clustered but still behave like best of breed if integration is not thoughtfully designed.
Architecture must therefore be guided strategically rather than shaped solely by vendor offerings.
VII. Guiding Principles for Architecture Decisions
A. Purpose of Guiding Principles
Guiding principles ensure architecture supports organizational strategy instead of short-term solutions or vendor influence.
They typically fall into three categories:
IT principles (standardization, build vs. buy decisions),
business drivers (service improvement, cost reduction, speed),
operational goals (security, privacy, service reliability).
B. Actionable Guiding Principles
Effective principles must lead to actionable decisions.
Examples include:
delivering inexpensive and reliable EMRs to small practices through centralized hosting,
reducing local server management,
combining practices into shared systems,
building redundancy to support continuous 24/7 operations.
Statements such as “systems should be easy to support” are not actionable and therefore do not function as true guiding principles.
VIII. Developing Healthcare IT Architecture
A. Step-by-Step Methodology
Organizations typically follow five steps:
Establish the baseline — identify existing systems.
Identify gaps — determine unmet needs.
Develop conceptual architecture aligned with guiding principles.
Determine cost and implementation sequencing.
Develop implementation and spending plans.
Strategy is converted into executable action through this process.
IX. IT Application Mapping and Gap Analysis
A. Establishing the Baseline
Organizations map systems against the healthcare value chain and operational entities such as hospitals and outpatient clinics.
This reveals:
strong coverage areas,
redundancies,
unsupported activities.
The mapping becomes the foundation for gap analysis.
B. Evaluating Systems: Technical vs Functional Quality
Applications are evaluated along two dimensions:
Technical quality (reliability, security, maintainability)
Functional quality (ability to meet user needs)
Decision outcomes include:
replace systems low in both areas,
enhance systems technically sound but functionally weak,
retain systems strong in both,
monitor systems functionally strong but technically aging.
Gap analysis exposes misalignment between IT portfolios and organizational needs.
X. Planning the Future Architecture State
A. Transitioning from Fragmentation to Integration
Future-state planning identifies:
systems to retain,
systems requiring replacement,
new systems to introduce.
Integrated EMRs such as Epic often serve as architectural anchors, creating unified patient records and workflow backbones.
Healthcare organizations must decide whether filling gaps or replacing legacy systems presents the greater challenge.
XI. Integration: From Connected Systems to Intelligent Data
A. Integration → Integrity → Intelligence
The ultimate purpose of integration is transforming data into value.
The progression occurs in three stages:
Integration — connecting systems and moving data
Integrity — validating and governing reliable data
Intelligence — enabling analytics and decision support
The goal is moving from scattered data toward actionable intelligence.
XII. Why Integration Is Difficult in Healthcare
A. Distributed and Heterogeneous Data
Healthcare data exists across hospitals, clinics, rehabilitation centers, home devices, pharmacies, and external organizations. Each environment may use different EMRs or enterprise systems.
Consequences include:
patient matching errors,
billing problems,
delayed care,
productivity loss,
increased cost.
B. Coding and Standardization Problems
Even simple fields such as gender or marital status use inconsistent coding across systems. Integration therefore requires validation, harmonization, normalization, and standardization.
If simple demographic data varies significantly, clinical terminology presents far greater challenges.
C. Terminology and Semantic Complexity
Healthcare relies on multiple coding systems such as ICD, CPT, SNOMED, LOINC, and RxNorm. These standards serve different purposes and require constant mapping between versions and systems.
Technical connectivity alone is insufficient. Semantic integration ensures data meaning is preserved.
XIII. Methods of System Integration
A. User Multitasking
Users manually combine information by viewing multiple systems simultaneously.
B. Interfacing
Data is copied between systems using standards such as HL7, creating duplicated sources of truth.
C. API-Based Integration
Systems retrieve needed data dynamically through services such as FHIR, creating virtual integration.
D. True Integration
All systems share a single logical structure and unified data source.
Each approach involves trade-offs between cost, flexibility, and reliability.
XIV. HL7 and Interface Architecture
A. HL7 Messaging
HL7 is a standardized data exchange method allowing healthcare systems to share structured information such as demographics and diagnoses.
Messages package data so receiving systems interpret it consistently, similar to how barcode scanners interpret boarding passes.
B. Point-to-Point Interfaces
Direct system-to-system connections grow exponentially as systems increase, creating the N × (N − 1) problem and high maintenance costs.
C. Interface Engines
Interface engines route communication through a central hub, reducing complexity, improving scalability, and enabling monitoring.
Although implementation costs may reach mid-six figures with ongoing maintenance expenses, engines significantly improve reliability and manageability.
XV. Modern Interoperability Standards
A. CCDA Documents
CCDA represents standardized patient summaries built using XML structures, allowing clinical information exchange between organizations.
B. Vocabulary and Content Standards
Key interoperability components include:
vocabulary standards (SNOMED, LOINC),
content standards,
identifiers,
transport standards.
Together they form interoperability foundations.
C. FHIR
FHIR operationalizes HL7 using APIs. EMRs expose standardized data resources such as allergies or lab results that applications retrieve securely.
FHIR supports both XML and JSON formats and simplifies modern healthcare data exchange.
XVI. Persistent Interoperability Barriers
A. Data Variation and Normalization Issues
Organizations record clinical information differently. Examples include dozens of ways to record pulse oximetry or glucose values across institutions.
Even discharge destinations may be categorized differently, preventing reliable comparison.
B. Patient Identification Challenges
The United States lacks a universal patient identifier. Providers assign independent medical record numbers, producing duplicate records that increase cost and patient safety risk.
Misidentification occurs in roughly 10% of cases.
XVII. Master Patient Index and Enterprise Matching
A. MPI and EMPI Concepts
Master Patient Index systems link patient data within an EHR and detect duplicates.
Enterprise Master Patient Index systems extend matching across multiple organizations and systems using global identifiers.
B. Matching Algorithms
Two approaches are used:
deterministic matching (exact matches),
probabilistic matching (statistical likelihood thresholds).
Most systems combine both approaches.
C. Active vs Passive EMPI
Active EMPI prevents duplicates during registration but is costly.
Passive EMPI detects duplicates afterward and requires manual correction.
Organizations balance cost against accuracy.
D. Regional Overlay EMPI Example
In the Dallas–Fort Worth region, over 80 hospitals contribute to an overlay EMPI linking records across institutions. This enables regional analysis of patient movement, readmissions, and healthcare utilization patterns beyond individual hospitals.
XVIII. Overall Conceptual Takeaway
Healthcare IT architecture and interoperability decisions determine how effectively information flows across organizations.
There is no universally best architecture. Success depends on aligning:
organizational goals,
operational constraints,
cost structures,
and integration strategy.
Effective healthcare IT is not defined by individual systems, but by how well those systems work together to support care delivery, operations, and future growth.
Lecture 4: Value-Based Care, Bundled Payments, ACOs, PCMH, Population Health, and Informatics
I. Why the U.S. System Is Changing
A. Healthcare Is Purchased in Fragmented Pieces
To understand value-based healthcare, begin with how healthcare is currently purchased and delivered in the United States.
Healthcare today operates in fragments rather than as one coordinated system. Care occurs in separate locations that function independently. If someone develops a kidney infection, they go to one place. If surgery becomes necessary, they go somewhere else. Rehabilitation occurs in another facility, and follow-up care may involve entirely different physicians.
Each organization manages its own services, records, and decisions.
The critical issue is that information does not really follow the patient. Medical history, imaging, medications, and treatment decisions remain inside individual organizations. Patients are therefore left to find physicians themselves and connect their own care experiences together.
Healthcare becomes organized around encounters instead of around the patient’s overall health journey.
Fragmentation immediately creates coordination problems. Providers cannot always see what others have already done, which leads to duplication. A patient may receive the same imaging study twice simply because hospitals and specialists do not share records. Insurance companies frequently pay for those duplicates, so the incentive structure does not prevent repetition.
B. Healthcare Costs Rising Faster Than Wages
When healthcare costs are compared with wages, the underlying problem becomes clear.
Healthcare spending increases much faster than worker earnings. Federal healthcare spending grows far beyond GDP growth. At the same time, premiums and deductibles rise faster than income, meaning patients pay increasingly larger portions out of pocket.
This widening gap creates pressure across the entire system:
patients struggle with affordability,
employers struggle to maintain benefits,
government programs face sustainability challenges.
Healthcare already accounts for about 18% of GDP, and projections show it exceeding 20% within the next decade. That equals roughly one out of every five dollars in the economy and more than $24,000 per person annually.
These dramatic expenses create a major societal burden, especially for uninsured and underinsured populations.
II. Fee-for-Service Shows the Incentive Problem Clearly
A. How Fee-for-Service Payment Works
For decades, healthcare operated under fee-for-service payment.
Under this model, providers bill separately for every service delivered. Payment depends entirely on the number of services performed rather than the outcome achieved.
B. Detailed Walkthrough: Brainstem Lesion Hospitalization
A 55-year-old patient presents with a brainstem lesion and requires hospitalization for ten days.
Initial hospitalization generates payment for admission, physician evaluation, monitoring, imaging, and treatment.
Complications then occur.
Hospital-acquired infection:
The patient develops meningitis while hospitalized. Treating this infection requires diagnostic testing, specialist consultation, antibiotics, and extended hospitalization. Each additional intervention produces reimbursement.
Medication error:
A medication mistake occurs, requiring the patient to return for further treatment and monitoring. Corrective care generates additional billable services.
Second surgery:
The infection worsens and requires surgical intervention. This introduces operating room charges, surgeon fees, anesthesia services, and recovery care.
Long-term complications:
The patient leaves the hospital with impaired vision and mobility problems, requiring rehabilitation and follow-up treatment.
Every step produces payment.
C. The Incentive Misalignment
In a fee-for-service world, every step gets paid—even the errors.
The system rewards volume of services rather than quality of outcomes. Complications increase activity, and activity increases reimbursement.
The payment structure does not distinguish between efficient care and preventable harm. The result raises a central question:
Was this good care—or simply more billable care?
III. Waste and Inefficiency Across the Healthcare System
A. Duplication and Poor Coordination
Fragmentation combined with volume incentives produces inefficiency throughout healthcare delivery.
Patients may undergo duplicate imaging because providers cannot access prior records. Specialists repeat testing when information is unavailable. Administrative processes introduce further complexity.
B. Sources of Healthcare Waste
Major contributors to waste include:
failure of care delivery,
poor coordination,
overtreatment,
pricing failures,
fraud,
administrative complexity.
Combined estimates place waste between $760 and $935 billion annually.
Inefficiency exists across nearly every part of the system rather than arising from one isolated issue.
Neither market competition nor malpractice litigation corrects these problems because payment incentives still reward additional services.
IV. Why Healthcare Does Not Behave Like a Normal Market
A. Limits of Traditional Market Economics
Traditional markets assume informed consumers making rational purchasing decisions.
Healthcare differs fundamentally:
everyone eventually needs care,
patients lack medical expertise,
emergencies eliminate comparison shopping,
insurance separates care decisions from direct payment.
B. Perverse Incentives
Because payment follows service delivery, complications may unintentionally increase financial return.
The larger the complication, the more services are delivered. The more services delivered, the greater the reimbursement.
These are perverse incentives, meaning incentives encourage outcomes opposite to what society intends.
Value-based medicine emerges specifically to realign incentives toward quality and outcomes instead of volume.
V. National Quality Improvement and Measurement
A. Measurement as the First Step Toward Improvement
Healthcare organizations begin tracking:
patient safety events,
incidents causing harm,
near misses,
unsafe conditions.
The reasoning is straightforward:
You cannot improve what you do not measure.
B. The National Quality Strategy
The Affordable Care Act establishes a national framework pursuing three goals simultaneously:
better care for individuals,
healthier communities,
more affordable healthcare.
Quality therefore expands beyond hospital performance to include population outcomes and cost management.
VI. Payment Reform: Moving From Volume to Value
A. Fundamental Change in Payment Logic
Fee-for-service asks how much care was delivered.
Value-based care asks how well care was delivered.
Providers receive financial rewards when performance improves—for example, when readmissions decline or safety improves.
B. Major Programs Driving Change
Hospital Value-Based Purchasing (HVBP):
Hospitals earn incentive payments for delivering higher quality care to Medicare patients.
Hospital Readmission Reduction Program (HRRP):
Hospitals with higher-than-expected readmissions receive penalties.
Although penalties range from 1–3%, hospital profit margins often average around 3%. Even small penalties therefore represent major financial impact and drive leadership attention toward care improvement.
VII. Payment Models as a Spectrum of Risk
A. Fee-for-Service to Capitation Continuum
Healthcare payment models distribute financial risk differently.
Fee-for-service: providers bear little financial risk.
Care coordination and pay-for-performance: partial risk sharing.
Bundled payments and shared savings: increased provider responsibility.
Capitation: fixed payment per patient regardless of utilization.
B. Why Shared Risk Models Emerged
Capitation historically created concerns because providers struggled managing full financial risk and worried about limiting care to remain profitable.
Modern payment reform therefore centers in the middle of the spectrum, where risk is shared between payers and providers.
Population health management operates within this shared-risk region.
VIII. Population Health: The Conceptual Turning Point
A. Definition of Population Health
Population health focuses on health outcomes of groups of people and how outcomes are distributed within those groups.
Modern population health becomes proactive rather than reactive.
Organizations apply interventions to keep defined populations—such as diabetes or congestive heart failure patients—healthier at lower cost.
Responsibility extends across the entire continuum:
primary care,
hospitalization,
post-acute care,
long-term monitoring.
If patients are attributed to an organization, that organization becomes responsible for their health, not just their visits.
B. Population Health Management (PHM)
Population Health Management is not a payment model.
It represents techniques and data systems used to manage populations with similar health conditions.
The major transition occurs from managing episodes of care to managing continuous care across settings.
Accountable Care Organizations represent one implementation of PHM.
IX. Fragmentation Across the Continuum of Care
A. Example: Congestive Heart Failure
A patient receives CHF treatment at one hospital. When symptoms worsen later, emergency services transport the patient to the nearest hospital rather than the original provider.
Care continuity breaks.
No single organization manages the full patient journey.
Bundled payment models attempt to reconnect these fragmented stages.
X. Bundled Payments: Reconnecting the Episode of Care
A. Knee Replacement Episode Walkthrough
Bundled payments group all services into one payment covering an entire episode.
Included services:
consultation,
surgery,
implants,
hospitalization,
therapy,
rehabilitation.
Episode timeframe:
30 days before surgery,
180 days after surgery,
for a total of 210 days.
If negotiated payment equals $30,000 and total cost equals $26,384, providers retain savings.
If complications increase cost beyond payment, providers absorb the loss.
Financial accountability encourages coordination, prevention of complications, and careful discharge planning.
B. Complex Example: Stage III Colorectal Cancer
Treatment involves multiple participants:
primary care physician,
gastroenterologist,
pathologist,
surgeon,
oncologist,
nurses,
social workers.
Care extends across months from colonoscopy and biopsy through surgery, chemotherapy, and long-term management.
Bundled payment places responsibility for coordination across the entire treatment continuum.
XI. Congestive Heart Failure as Population Health in Practice
A. Why CHF Matters
Managing CHF costs approximately $40 billion annually in the United States, with more than half resulting from hospitalizations.
Patients frequently cycle between home and hospital.
B. Population Health Intervention
Population health management focuses on:
monitoring patients outside hospitals,
coordinating outpatient care,
supporting home management,
lowering risk before deterioration occurs.
Reducing hospitalizations improves both patient outcomes and system cost performance.
XII. Accountable Care Organizations (ACOs)
A. Core Design Principles
ACOs bring providers together to manage cost and quality collectively through:
accountability for outcomes,
transparent performance measurement,
payment reform tied to results.
Providers share savings when outcomes improve and share losses when costs rise.
B. Organizational Example
Partnerships such as UT Southwestern and Texas Health Resources combine strengths without merging organizations. One contributes advanced inpatient expertise, while the other provides strong outpatient care coordination.
Together they manage populations across the continuum while sharing financial risk.
XIII. Patient-Centered Medical Home (PCMH): Operationalizing Care Coordination
A. Why ACOs Need a Coordination Hub
Once providers form an Accountable Care Organization and accept responsibility for both cost and quality, a practical question immediately arises:
Who actually coordinates patient care on a daily basis?
Managing population health requires continuous oversight across multiple providers and settings. Without a central organizing structure, fragmentation simply continues inside the ACO.
The Patient-Centered Medical Home (PCMH) serves as this coordination hub.
A PCMH is not a physical home. Instead, it represents a model of organizing care around a primary care team that becomes the central access point for the patient.
The primary care physician leads a coordinated team responsible for managing:
medical records,
specialist referrals,
chronic disease monitoring,
follow-up care,
communication across providers,
supportive and community services.
Rather than patients navigating healthcare independently, the PCMH organizes care around a structured plan.
B. Example: Managing Congestive Heart Failure Through PCMH
Consider a patient with congestive heart failure.
Effective management requires coordination among:
primary care physicians,
cardiologists,
home health nurses,
rehabilitation providers,
medication management services.
Without coordination, each provider treats only part of the problem. Information gaps appear, treatment plans conflict, and deterioration occurs unnoticed until hospitalization becomes necessary.
Within a PCMH structure, the care team continuously monitors the patient and ensures that treatment decisions remain aligned.
Care becomes continuous rather than episodic.
C. The Real-World Challenge: Multiple Chronic Conditions
Although PCMH works conceptually for managing a single disease population, real patients rarely have only one condition.
A CHF patient may also have:
diabetes,
hypertension,
obesity,
kidney disease.
Multiple chronic conditions create overlapping care plans involving different specialists.
This complicates coordination and represents one of the major operational hurdles in implementing PCMH models within ACOs.
Healthcare must coordinate care for complex individuals rather than isolated diseases.
XIV. How Value-Based Models Align Providers, Payers, and Patients
A. Shared Responsibility Across Stakeholders
Value-based healthcare changes how providers, payers, and patients interact.
Providers collaborate across disciplines to deliver coordinated, evidence-based care.
Payers, such as Medicare, commercial insurers, or large employers, establish contracts defining performance expectations and financial risk-sharing arrangements.
Patients also participate actively in care through adherence, follow-up participation, and engagement with treatment plans.
Unlike fee-for-service, where more visits automatically generate revenue, payment now depends on outcomes and efficiency.
If performance targets are achieved:
providers share savings.
If costs rise or quality declines:
providers share losses.
The objective becomes aligning incentives across all participants.
XV. Why Informatics Becomes Essential
A. Managing Populations Requires New Information Capabilities
After payment reform shifts responsibility toward population outcomes, organizations must answer entirely new questions:
Which patients are at risk of readmission?
Who is likely to deteriorate soon?
Which interventions improve outcomes?
Where are costs increasing?
Which patients leave the network?
Traditional healthcare IT systems were designed mainly for billing individual encounters.
Population health management requires systems capable of integrating data across providers and tracking patients over time.
Informatics becomes essential because managing population health is fundamentally a data problem.
B. Transition From Encounter Management to Population Management
Healthcare organizations must now monitor health trajectories rather than isolated visits.
Systems must support:
longitudinal tracking,
predictive monitoring,
coordinated workflows,
performance measurement.
Without informatics infrastructure, value-based care cannot function operationally.
XVI. Core Processes That Enable Population Health Management
A. Risk Stratification
Risk stratification identifies patients or cohorts likely to experience adverse outcomes.
The focus shifts from asking who is sick today to predicting who will become high risk in the future.
For example, a CHF patient visiting the emergency department three times within six months may be flagged by predictive models as high risk.
Once identified, care teams intervene early through monitoring, follow-up, or treatment adjustments.
Prediction enables prevention.
B. Care Management
Care management coordinates patient-centered care across providers and settings.
High-risk patients receive structured management plans linking:
primary care,
specialty care,
home health,
rehabilitation services.
The goal is preventing patients from falling through gaps between organizations.
C. Performance and Financial Management
Organizations operating under shared-risk contracts must continuously monitor performance.
They evaluate:
cost trends,
quality outcomes,
utilization patterns,
readmission rates.
Improved performance generates rewards, while poor performance generates penalties.
Clinical management and financial management become interconnected.
D. Automation and Workflow Support
Population health cannot be managed manually.
Information systems automate:
alerts,
reminders,
reporting,
workflow coordination.
Automation enables scalable population oversight.
XVII. Technology Challenges in Multi-Organization ACOs
A. Independent Organizations, Independent Systems
ACOs typically represent partnerships rather than mergers.
This means participating organizations retain:
separate IT departments,
different electronic medical record systems,
different vendors,
legacy infrastructure.
Multiple systems often cannot communicate effectively.
New workflows must cross organizational boundaries despite the absence of unified governance.
The challenge becomes integrating fragmented data and processes across independent entities.
XVIII. The Role of the HITECH Act in Enabling Value-Based Care
A. Why Digital Infrastructure Came First
Before population health management could exist, healthcare required widespread electronic health record adoption.
Earlier efforts encouraging EHR adoption failed due to lack of incentives.
The Health Information Technology for Economic and Clinical Health (HITECH) Act introduced financial incentives for adopting certified EHR systems and penalties for failing to adopt them.
B. Standardization of Health Data
HITECH did more than digitize records.
By requiring certified systems, it established national standards for storing and exchanging healthcare data.
Electronic data exchange became possible across organizations.
Digitization provided the foundation upon which value-based care and population health management could later develop.
XIX. New Information Infrastructure Requirements
A. Need for Common Infrastructure Across Organizations
Physicians frequently practice in multiple hospitals and clinics.
Data must therefore move seamlessly between systems.
Traditional EMRs often remain siloed, and continuity-of-care summaries provide only limited information.
Value-based care shifts focus from patient-centric documentation toward plan-centric coordination.
Healthcare organizations must ensure patients follow coordinated care plans within networks.
B. Integration With Post-Acute Care
Post-acute providers such as rehabilitation centers and home health agencies operate on separate platforms.
Integrating these settings becomes especially challenging yet essential for managing the continuum of care.
Patient engagement tools become necessary because patients leaving the network undermine coordination and financial performance.
XX. Patient Identification and Enterprise Master Patient Index (EMPI)
A. Absence of a National Patient Identifier
The United States does not maintain a universal patient identifier.
Each organization must determine whether records belong to the same individual.
Privacy concerns prevent widespread use of Social Security numbers, and biometric solutions raise cultural concerns.
B. EMPI as a Locator System
Enterprise Master Patient Index systems use probabilistic matching algorithms comparing demographic information to reconcile patient identities across systems.
The EMPI functions as a locator service connecting patient records across organizations.
Accurate identification is essential for coordinated population management.
XXI. Health Information Exchange (HIE)
A. Vendor-Based Exchange
Vendor-based exchanges, such as Epic Care Everywhere, enable record sharing among participating organizations.
Strengths include widespread adoption and large-scale data exchange.
Limitations include:
summary-level information,
limited imaging exchange,
one-to-one data sharing,
restricted population analytics capability.
B. Vendor-Agnostic Exchange
Vendor-neutral Health Information Exchanges allow participation regardless of EMR vendor.
These systems aggregate data regionally and support:
population health analytics,
quality reporting,
public health surveillance.
Effectiveness depends on organizational willingness to share data.
XXII. Referral Management and Network Integrity
Patients sometimes receive care outside coordinated networks due to:
unavailable services,
geographic barriers,
communication gaps,
dissatisfaction.
Analytics identifies referral leakage patterns.
Referral management ensures patients receive appropriate care while protecting coordinated value networks.
XXIII. Post-Acute Care Coordination
Approximately 35% of Medicare patients transition from acute hospitals into post-acute care.
These patients represent some of the highest-cost populations.
Post-acute care includes:
skilled nursing facilities,
rehabilitation centers,
home health,
hospice.
Effective coordination reduces readmissions and improves outcomes.
XXIV. Patient Engagement
Patients spend most of their time outside healthcare facilities.
Engagement technologies include:
patient portals,
messaging platforms,
wearable devices,
automated reminders.
Mobile accessibility becomes essential.
Engaged patients actively participate in managing their health rather than remaining passive recipients of care.
XXV. Analytics as the Core Engine of Population Health
Analytics aggregates data across fragmented systems to support:
patient registries,
outcome tracking,
provider evaluation,
predictive risk modeling.
Predictive analytics identifies patients likely to require emergency care or readmission, enabling early intervention.
The primary challenge remains integrating fragmented data into unified insight.
XXVI. Performance Measurement in Value-Based Care
Performance evaluation relies on four measure categories:
Structure: available systems and resources
Process: whether correct care steps occurred
Outcome: patient health results
Patient Experience: perception of care received
Measurement enables continuous improvement rather than simple compliance.
XXVII. Precision Health and Population Health Together
Population health manages groups collectively.
Precision health focuses on individualized prediction and prevention through:
wearable monitoring,
genetic testing,
tumor profiling,
pharmacogenomics,
continuous glucose monitoring.
Population health operates broadly, while precision health operates deeply.
Together they improve prevention and personalization.
XXVIII. Final Integration: The Complete Transformation
Healthcare transformation connects payment reform, care delivery redesign, and information technology.
Healthcare shifts from:
volume-driven care → outcome-driven care
fragmented delivery → coordinated systems
reactive treatment → proactive prevention
encounter responsibility → population responsibility
Population health management becomes the operational infrastructure.
Informatics becomes the enabling foundation.
Value-based care ultimately represents not just payment reform, but a transformation of how healthcare is organized, delivered, measured, and managed.
Lecture 5: Federal Health IT Policy: A Full, Smooth-Flow Explanation (Adoption → Meaningful Use → Interoperability → Safety → New Risks)
I. The lecture’s core storyline: why federal policy shaped health IT the way it did
The lecture is built around a connected storyline. Federal policy did not treat health IT as something that would spread naturally on its own. Instead, policy used national incentives, national standards, and later penalties to push the system through several phases:
Get EHRs adopted across hospitals and physician practices.
Define what “using an EHR” must mean, so providers cannot just buy software and keep doing paper workflows inside a digital shell.
After adoption becomes widespread, shift the policy focus to interoperability—making systems share data across settings—and to patient access to that data.
Connect technology and data flow to patient safety, since health IT is now part of the care process itself.
Recognize that a more digital, more connected healthcare system creates new threats—especially cybersecurity and privacy risks—that policy and regulation then have to manage.
Throughout the lecture, the “why” is consistent: policy is trying to move healthcare toward better quality, lower cost, and improved outcomes, and to do that at scale it needs standardized, structured data that can be measured, exchanged, and analyzed. This is the logic behind pushing the system toward a conformed data model.
II. Clearing up the timeline: where Meaningful Use actually came from
A. Why the “Meaningful Use = Obamacare” idea breaks the flow
The lecture emphasizes that a common misunderstanding disrupts how people interpret the entire policy timeline: the belief that Meaningful Use was part of Obamacare. The lecture states that this is not correct.
B. The correct origin: HITECH inside ARRA (Recovery Act, 2009)
Meaningful Use came from the HITECH Act—Health Information Technology for Economic and Clinical Health Act. HITECH passed in 2009 as part of the Recovery Act (ARRA).
ARRA was passed after the 2008 financial crisis and was designed to induce the economy. HITECH was part of that broader stimulus effort. That is why the Meaningful Use incentive structure is not “Obamacare policy,” but rather stimulus-era federal policy designed to accelerate adoption of digital systems.
C. Why this matters for the bigger political point later
Because Meaningful Use and the major EHR incentives come through HITECH (Recovery Act), not through the Affordable Care Act, the digital health trajectory did not depend on what happened to Obamacare debates later. That becomes important later in the lecture when explaining why changes in the political environment did not derail the overall push toward digital health.
III. What HITECH did: a massive adoption push, but with a specific purpose
A. HITECH as one of the biggest drivers of digital health
HITECH created billions of dollars in incentives for EHR adoption. The lecture frames it as one of the biggest policy drivers of digital health.
B. The goal was not “paper becomes a PDF”
HITECH’s goal was not just to digitize records. The lecture says the purpose was to ensure EHRs are used to improve:
quality
safety
transparency of care
So the policy intent is “adoption + meaningful use,” not adoption alone.
C. Why this was such a big change compared to earlier “EHR” concepts
The lecture contrasts today with what “EHR” meant earlier. Twenty years ago, an “EHR” in some small practices could mean typing a note in Word and saving it on a computer. That is digital storage, but not structured, exchangeable, measurable clinical information.
The lecture also points out that the idea of national digital health records had been pushed earlier (in 2004). Later, after the financial crisis, the federal approach expanded the effort by setting standards and requiring effective use through policy levers.
This explains the scale of adoption today. The lecture notes that more than 9 out of 10 office-based physicians now have an EHR. It frames this as an almost complete transformation compared to the early 2000s.
IV. Why adoption alone fails: the “technical use vs meaningful use” problem
A. The reason HITECH needed more than purchase incentives
The lecture stresses that HITECH did more than pay people to buy EHRs. It created incentives and disincentives to ensure the systems are used the “right way.”
This is a response to a predictable problem: when people adopt a new technology, they often keep the old workflow and just wrap it in the new tool.
B. The email analogy: a clear model of the problem
The lecture uses an email analogy:
When companies first adopted email, some employees typed a memo in Word, printed it, signed it, scanned it, and then emailed it. They were “using email,” but they were still doing the paper memo workflow.
Healthcare did the same thing:
A provider could buy an EHR but just scan paper charts into it.
That is digital storage, but it is not meaningful use of the system.
C. What Meaningful Use required: structured electronic documentation
The policy wanted EHRs to capture data in structured form. Meaningful Use required documenting things like:
demographics
diagnoses
prescriptions
histories
in structured electronic form so the data could actually be used to improve care.
The key point is that structured data can be counted, reported, exchanged, and analyzed. Scanned paper cannot do that in the same way.
V. How policy forced this shift: the “carrot and stick” model and national standards
A. The incentive phase: payments for meeting requirements
Early on, providers received financial incentives if they met specific EHR use requirements.
B. The penalty phase: financial consequences for not using EHRs meaningfully
Later, incentives went away and penalties appeared, including reduced Medicare payments if providers were not using systems meaningfully.
C. The bottom line logic of the program
The lecture frames the bottom line as:
It was not enough to own an EHR.
Providers had to use it in ways that met national standards.
If they did not, there were financial consequences.
This is why Meaningful Use is structured around measurable requirements rather than general encouragement.
D. How HITECH and Meaningful Use relate
Meaningful Use is the name of the program. HITECH is the legislation that created it. The program ensured providers were not just buying EHRs, but using them meaningfully to improve care.
VI. The Meaningful Use stages: a staged escalation that explains the program’s flow
Meaningful Use is presented as a program that escalates what it expects providers to do, in three stages. The schedule changed over time, but the lecture emphasizes the stage logic.
A. Stage 1: capturing and sharing (starting around 2011)
Stage 1 focused on electronically capturing and sharing health information. The goal was to get the basics in place. The system had to be used so the essential information exists electronically and can be shared.
B. Stage 2: care coordination and clinical decision support
Stage 2 added requirements for:
care coordination
clinical decision support
The lecture explains the significance: EHRs are no longer just storage systems. They are tools that improve how care is delivered, because coordination and decision support are part of the care process.
C. Stage 3: demonstrating measurable outcomes
Stage 3 emphasized outcomes. Providers had to show the system made measurable improvements in:
quality
safety
efficiency
This is the “prove it makes a difference” stage.
D. The progression as a single connected concept
The lecture explicitly describes the progression:
get the data in
use it to coordinate and support care with advanced EHR tools
prove it improves outcomes
This progression is the simplest way to keep the stages straight because it explains why the policy escalates expectations.
VII. Certified EHRs: why certification existed and what it actually set
A. Certification as a precursor to participating
To meaningful use, organizations had to use a certified EHR. Certification is described as a precursor: it creates a baseline set of expectations for technology.
B. What certification ensures (baseline requirements)
A certified EHR meets a minimal set of requirements, but those requirements are important. Certification ensures:
security safeguards
data integrity
ability to exchange information in a standardized way (the lecture gives continuity of care documents / CCDs as an example)
Certification also requires core functions like:
electronic prescribing
computerized provider order entry (CPOE)
lab ordering
These create a consistency baseline across systems.
C. What certification does not ensure: usability and clinician satisfaction
The lecture emphasizes certification does not guarantee a perfect user experience. Even with certification, tools like CPOE can frustrate clinicians. The key point is that certification sets a baseline standard; it does not mean systems will match real-world clinical workflow smoothly.
VIII. “Show you’re using it”: how incentive eligibility was proven through measures
A. Installation is not what triggers payment
The lecture is clear: it is not enough to install a certified system. Adoption or installation alone does not qualify for incentive payments.
Providers must show they are using the system in specific ways.
B. Examples of required use measures (what got measured)
Examples the lecture gives include:
recording structured demographics for more than half of patients
capturing vital signs like height, weight, blood pressure
documenting problems
maintaining medication lists
using the system for e-prescribing
The lecture notes these are only examples. In reality, there were dozens of measures.
Organizations had to:
meet all requirements in a core set
select additional requirements from a menu set
C. Why this approach mattered: the quality feedback loop
The lecture explains that these measures create a giant quality feedback loop.
When structured data is collected in everyday practice, it can feed:
registries
reporting systems
national benchmarks
That means routine documentation supports:
individual patient care in the moment
and also supports:system-level quality improvement by generating evidence and benchmarks
This is a major reason policy insisted on structured data and measurable use.
IX. A detailed example that ties everything together: the problem list requirement
A. The requirement (what had to be true)
One Stage 1 requirement example is reviewing and recording items on a patient’s problem list for at least 80% of patients.
B. What that required in a system like Epic (what clinicians had to do)
The lecture describes how this plays out practically:
For established patients:
review the problem list at each visit
update it as needed
confirm it has been reviewed
mark it as reviewed in the system
For new patients:
add relevant problems
mark them as reviewed in the system
The lecture notes that sometimes the system lets you pull the visit diagnosis directly into the problem list.
C. What vendors had to build “behind the scenes” (tracking compliance)
The lecture emphasizes that vendors had to ensure these actions could be tracked and reported as numerator and denominator values to prove compliance:
numerator: number of patients where the action occurred
denominator: number of patients eligible
This required extra customization for vendors and increased documentation tasks for providers.
D. Why this illustrates workflow change and “extra clicks”
On the surface it seems simple, but multiplied across every patient and every visit it becomes significant. It shows how meaningful use requirements drive structured documentation that helps reporting but often feels like extra clicks in daily practice.
X. Workflow and culture change: why meaningful use felt disruptive
A. Why the workflow change was “dramatic” from paper charts
If a practice was moving from paper charts to EHRs, the shift was dramatic. Suddenly every visit required structured documentation, including:
demographics
vitals
problems
medications
allergies
lab orders
and more.
B. Why it became a cultural change
Physicians, nurses, and staff had to adapt their routines. Paper workflows were flexible and fast. EHR workflows required structured steps and consistent documentation.
The lecture describes that for many providers it felt like the system was shaping how they practice medicine rather than supporting it. This is part of the “unintended consequences” of rapid policy-driven adoption.
XI. The 2018 evolution: Meaningful Use becomes Promoting Interoperability
A. Why the change happened
In 2018, CMS renamed the Meaningful Use Program as the Promoting Interoperability program.
The lecture explains the context:
Stage 1 was done
Stage 2 was done with hiccups
Stage 3 was difficult and people struggled
CMS changed the program and changed priorities.
B. Why it was not just a rebrand: the new focus
The lecture explicitly says it was not just a rebrand. It reflected a shift in priorities.
Instead of focusing on proving you were using an EHR, the program shifted emphasis toward:
interoperability
reducing reporting burden
empowering patients to use their own health information
C. The financial stick continues
Hospitals and critical access hospitals still face payment adjustments for not demonstrating compliance.
For hospitals:
reduction in Medicare’s annual payment increase
For critical access hospitals:
reimbursement drops from 101% to 100% of reasonable cost
So the carrot-and-stick model continues, with stronger emphasis on sharing and patient access.
XII. What Promoting Interoperability requires: objectives, scoring, and MIPS connection
A. The four hospital objectives
Hospitals report on four main objectives:
e-prescribing
health information exchange
provider-to-patient access
public health or clinical data exchange
B. The rising scoring thresholds
The lecture gives the thresholds:
60 points today
rising to 70 by 2025
80 by 2026
C. Clinicians and MIPS
For clinicians, Promoting Interoperability counts as 25% of the yearly MIPS score.
MIPS is the Merit-based Incentive Payment System. It ties Medicare reimbursement to performance across:
quality
cost
improvement activities
technology use
So Promoting Interoperability is directly tied into Medicare payment adjustment through MIPS.
D. The message of where policy is now
The lecture emphasizes the policy message: it is no longer enough to show you use an EHR. Now the priority is making sure systems work together, exchange information, and improve care and outcomes.
XIII. Why digital health continued even when ACA politics changed
Because HITECH came from the Recovery Act of 2009, and many digital health incentives are independent of the Affordable Care Act, political shifts around Obamacare did not derail the digital health trajectory.
The lecture notes that even while there were efforts to repeal or scale back Obamacare, incentives for EHRs and value-based programs continued. It also notes that leaders supported value-based care and measurement. This helps explain why the push toward interoperability and risk-sharing models stayed intact across administrations.
The lecture frames this as momentum bigger than any single administration—more like a grand experiment aligning incentives and market forces.
XIV. The results: near universal adoption—but adoption is only half the story
A. National adoption trend
The lecture describes adoption trends:
early 2000s: only about 10–20% of hospitals had electronic systems
after more than a decade of incentives and penalties: by around 2015 adoption stabilized
This is described as one of the most rapid technology transformations in healthcare history.
B. Why adoption is only half the story
Once nearly everyone has an EHR, the key question becomes: how mature are these systems? Are they being used in advanced ways that improve safety, outcomes, and efficiency?
That leads into maturity models like HIMSS EMRAM.
C. Improvements but uneven distribution
EHR adoption brought measurable improvements such as:
better access to patient information
stronger communication across providers
reduction in medication errors
But adoption is uneven across hospital types. The lecture gives numbers:
86% of non-federal general acute care hospitals adopted a certified EHR (by 2019–2021)
only about 40% of rehabilitation hospitals
only about 23% of specialty hospitals
So progress is clear, but unevenness remains.
XV. Maturity measurement: HIMSS, EMRAM, and the continuum of care model
A. HIMSS and HIMSS Analytics
HIMSS is the Healthcare Information and Management Systems Society, described as the largest professional or trade group for health IT. It has a research arm called HIMSS Analytics.
B. EMRAM: the hospital-level maturity ladder
HIMSS Analytics created the EMR Adoption Model (EMRAM) in 2005 and it remains active.
EMRAM has 8 stages from 0 to 7:
Stage 0: no meaningful digital systems installed
Stage 7: highly advanced electronic patient record environment, using:
external HIE
data warehouses
robust analytics
C. Continuum of Care Maturity Model: cross-organization maturity
The lecture describes a related framework called the Continuum of Care Maturity Model.
EMRAM looks at how deeply a single hospital has implemented technology. The continuum model looks at how well organizations coordinate care across systems. Stage 7 means knowledge-driven engagement across multiple vendors and organizations—true interoperability in support of population health.
D. EMRAM stages are not Meaningful Use stages
Meaningful Use has 3 stages and is about compliance and reporting. EMRAM has 0–7 and is about adoption sophistication and maturity.
XVI. EMRAM stages explained as an escalation of sophistication
The lecture goes deeper into EMRAM and what each stage represents:
Stage 0: nothing installed.
Stage 1: three ancillaries online:
lab
radiology
pharmacy
Stage 2: clinical data repository (CDR) in place, bringing results together.
Stage 3: electronic clinical documentation and medication administration records come online.
Stage 4: CPOE introduced as decision support at the point of care.
It standardizes how providers order treatment, diagnostics, and care.
Stage 5: radiology images and reports fully integrated via PACS.
Stage 6: medication tracking and stronger documentation and clinical decision support, plus closed-loop medication administration.
Stage 7: analytics, data warehousing, and external HIE connections to support advanced population health and safety.
The lecture says the expectation is not memorizing each stage perfectly, but understanding what the stages represent and what maturity looks like.
Stage 7 is recognized by HIMSS, but only a small percentage reach it. Most hospitals are in middle stages like 4, 5, 6.
XVII. Why Stage 7 is hard: interoperability across vendors remains difficult
Stage 7 is not just having a digital patient record. It requires structured, discrete data that can be exchanged, analyzed, and used across settings.
The lecture highlights the challenge: sharing across different vendors remains very difficult and sometimes not possible. This is why interoperability remains a major policy and technical issue.
XVIII. The roadmap over time: how the focus shifts by decade
The lecture describes a roadmap:
2000–2010: defining what an EHR should look like
2010–2020: getting practices to adopt EHRs and use them meaningfully
current decade: leveraging EHRs for improving health through:
preventive care
chronic disease management
remote patient monitoring
value-based care
This is tied to moving away from fee-for-service and toward rewarding providers for keeping patients healthy.
Meaningful Use drove adoption; EMRAM measures how mature and effective those systems are.
XIX. Why maturity matters: projections and quality differences
The lecture references a study that projected many hospitals will not reach EMRAM Stage 7 until around 2035 unless major policy shifts or big leaps in technology occur. Even today, most hospitals remain stuck at Stage 6.
The lecture also describes a quality association:
Hospitals with higher digital maturity performed better in terms of quality. Stage 7 hospitals had:
stronger Leapfrog safety grades
21% lower hospital-acquired infection rates
more robust safety culture
So maturity is connected to measurable improvements.
XX. Vendor market consolidation: why the EHR market looks the way it does now
The lecture uses the vendor landscape to show how rapidly markets changed, especially around early Meaningful Use years.
In the 2012–2014 period, vendors were aggressively selling new EHR products and it was described as a crazy market. Looking back further, older dominant companies were later acquired or disappeared, showing consolidation and shakeout.
Today the market is highly consolidated:
Epic and Oracle Cerner together control more than half the inpatient market.
Epic: nearly 40% and over 2,700 installations, a leap from about 5% in 2009.
Oracle Cerner: about 23% and more than 1,500 installations; Oracle acquisition in 2022 strengthened its position.
Meditech: about 13% of the U.S. market, dominates Canada, expanding internationally.
Smaller vendors still exist, especially in rural and critical access hospitals, but overall it is a “big three” environment.
Outpatient EHRs are described as simpler and more siloed, while inpatient systems focus heavily on interoperability across departments. Market share is described as fluid, with significant shifts even in 2024.
XXI. Usability: adoption succeeded, but day-to-day experience became a major problem
A. Why usability is a central concern now
Many EHRs have:
confusing displays
inconsistent icons
workflows that do not match how clinicians think
EHRs were also stretched to serve many purposes:
billing systems
legal records
communication tools
clinical support
The result is frustration, extra clicks, and sometimes burnout.
B. Texas example: usability problems show up in the exam room
The Texas Medical Association Health IT Survey (2025) shows:
91% of Texas physicians use EHRs
69% say EHRs interfere with attentiveness to patients
24% find clinical decision support tools helpful
many cite irrelevant alerts and alert fatigue
Additional survey findings:
8 out of 10 say too many clicks
60% say not intuitive
near half say lacking needed functions
more than half say data entry disrupts diagnostic thought process and communication
These numbers show usability affects care, not just convenience.
C. Benefits exist, but usability limits the promise
Despite frustrations, the lecture notes benefits:
better access to patient information
improved coordination among providers
reduction in medication errors
The challenge is keeping these benefits while addressing usability problems.
D. Why usability stayed unresolved
Usability remained unresolved because:
it was not a historical priority
certification testing was minimal and didn’t reflect real-world workflows
early change management relied on “build it and they will come,” which did not work
systems were asked to do too many jobs at once, making it hard to create cognition-friendly design
E. ISO definition of usability and “goals”
Usability is defined as the extent to which a product can be used by specified users to achieve specified goals in a specified context of use. The goals include effectiveness, efficiency, satisfaction, and certification. Certification did not ensure real workflow fit, which explains persistent problems.
XXII. Part 2 begins: interoperability, safety, and emerging challenges
The lecture then shifts: after adoption, the next challenge is making systems work together safely and effectively.
Part 2 focuses on:
interoperability challenges and how the 21st Century Cures Act addressed them
safety priorities tied to clinical decision support, patient identification, and usability
emerging challenges like cybersecurity and regulatory responses shaping the future
XXIII. Interoperability fundamentals: HIE/HIN, levels, and exchange types
A. HIE vs HIN
HIE means:
as a verb: the ability to electronically move clinical information between systems
as a noun: the organizations that provide exchange technology and services
HIN is:
the broader infrastructure, regional or national networks allowing exchanges
B. Levels of interoperability (from basic to broad)
Foundational: secure movement of information (like embedded secure webmail), without deeper context.
Structural: field-level structured sharing so data can be searched and queried.
Semantic: consistent meaning across systems (glucose example), enabling integration into another record.
Organizational: governance, policies, contracts, and trust agreements enabling real exchange.
Interoperability is as much about rules and relationships as it is about technology.
C. Three exchange models
Directed exchange: push model (sending referral summary).
Query-based exchange: pull model (search network for a patient record).
Consumer-mediated exchange: patient controls access and shares through apps or portals.
XXIV. What exchange looks like in reality: progress and limits
Hospitals are increasingly able to send and receive data, but integration and querying lag behind. Hospitals may move information around but struggle to pull it into workflows and make it usable at the point of care.
Fax is still common and remains the largest exchange method though declining. A HISP (health information service provider) acts as a secure pipe transmitting documents between endpoints. Other approaches include vendor-based exchange (Epic-to-Epic) and regional/state HIE participation. Reliance on fax and intermediaries shows interoperability still often depends on workarounds rather than seamless connection.
Barriers remain:
sending side: inability to package/transmit data usefully
receiving side: patient identification and lack of technical capacity
system-wide: incompatible platforms, high interface costs, custom solutions
XXV. Information blocking: why interoperability didn’t happen naturally
The lecture explains why data stayed siloed for years:
vendors had disincentives to make exchange easy across competitors because it could lead to customer loss
providers had disincentives because sharing data could lead to patient loss
This led to systems designed to keep information siloed, called information blocking.
XXVI. The 21st Century Cures Act: patient rights, blocking prohibition, and standardized data
A. Information blocking prohibition and the new default
The Cures Act prohibits clinicians, developers, and health information networks from preventing patients from accessing their data or sending it where they want.
By 2022, blocking protected health information became prohibited. The default shifts: patients own their data and systems must enable movement.
B. Immediate electronic access, including clinical notes
Patients have a right to immediate electronic access to:
notes
labs
imaging
other health information
without delays and at no cost.
Clinical notes included:
discharge summaries
history and physicals
progress notes
consults
imaging and lab reports
pathology and procedure notes
There are limited exceptions such as harm prevention, privacy/security protection, or technical infeasibility.
This represents a cultural shift: notes used to be for clinicians; now patients can read them regularly, often in real time.
C. FHIR and APIs: making access real
The Cures Act requires modern standards, especially:
FHIR to support data-field level exchange
standardized APIs to allow secure smartphone app access
The goal is moving away from static documents to real-time structured exchange so patients can pull information like online banking.
D. USCDI: defining what core data EHRs must support
USCDI is the standardized federal set of data elements certified EHRs must support. The lecture notes:
first version approved 2020
version 3 in 2026
version 4 in 2028
Each version expands required elements such as allergies, immunizations, lab results. Only about half have full standards currently, so variation still exists, but USCDI pushes toward a common foundation.
E. Actors covered and exceptions/fees
Actors include clinicians, health systems, health IT developers, and health information networks.
Exceptions include harm, privacy/security compromise, downtime, infeasibility, psychotherapy notes, and legal proceeding data.
Fees must be reasonable and cost-based; licensing fees might apply to proprietary risk scores, but not basic patient access.
XXVII. Patient empowerment and the consumer health IT marketplace
The lecture frames digital access as patient empowerment:
easier access to records
ability to compare costs and outcomes
ability to shop for care and make more informed choices
Smartphone apps make it possible to carry the record in your pocket. An app economy emerges, creating opportunities for patients and for providers, payers, employers to innovate.
Patient behaviors are changing: viewing notes, viewing results, making appointments, messaging providers.
XXVIII. Safety priorities and how policy links safety to health IT
Policy emphasizes safety across the health IT lifecycle through four priorities:
clinical decision support
interoperability so information flows reliably
patient identification
user-centric design, testing, evaluation, simulation
Toolkits exist to help improve usability. The lecture’s point is that safety must be built into technology.
Interoperability alone is not the end goal. The goal is to use access to empower patients and design systems that reduce errors and improve outcomes.
XXIX. Closed-loop medication administration: the policy-driven safety example
Closed-loop medication administration traces every dose from prescribing to dispensing to administration to discard.
It requires:
CPOE to enter orders electronically
pharmacy verification to check accuracy
barcode scanning to confirm the five rights (right patient, drug, dose, route, time), often using patient ID bracelets
It is not cheap, but powerful, tied to CMS and Joint Commission requirements, reducing adverse drug events.
XXX. ICD-10 transition: structured data expansion for documentation and analytics
The ICD-10 transition happened around 2015–2016 and was required by CMS, not Meaningful Use.
ICD-9 had about 13,000 codes; ICD-10 expanded to about 68,000. Some codes are extremely detailed, but the detail matters because it supports:
more precise documentation
reimbursement
richer analytics and research
The U.S. adopted it later than many developed countries, missing analytic power earlier. Once implemented, it strengthened evidence-based practice and population health. ICD-11 is the next logical step with digital-friendly design and global harmonization, but U.S. adoption is still on the horizon.
XXXI. Cybersecurity: the emerging risk after digitization and interoperability
Healthcare data breaches are rising. 2024 is described as among the highest on record. Patient records are valuable because they contain medical history plus identifiers and financial information.
Hacking dominates, accounting for more than three-quarters of incidents. Motives include fraud, medical theft, ideology, and state-sponsored attacks. Increased interoperability and structured data can increase the value of healthcare data to attackers.
XXXII. The regulatory “patchwork” for cybersecurity compliance
Cybersecurity is governed by multiple rules and frameworks:
HIPAA and HITECH set privacy/security standards
HITECH expanded HIPAA to include vendors and third parties
HIPAA Security Rule includes 36 required and 21 addressable safeguards
state laws like Texas Medical Records Privacy Act
NIST Cybersecurity Framework
HHS Cybersecurity Performance Goals
HITRUST
FDA oversight for medical devices
Cybersecurity is a compliance issue as much as a technical issue, requiring navigation of many layers.
XXXIII. The epoch framework: the lecture’s “big map” of health IT policy evolution
The lecture uses an epoch framework to connect the entire story:
Paper epoch (up to ~1990): patient story mattered; structured data value not recognized.
Pre-federal epoch (1990–2009): early EHRs existed but didn’t spread widely due to misaligned incentives.
Federal incentives epoch (2010–2017): $32 billion in incentives rapidly digitized medicine, created unintended consequences and missed interoperability; Cures Act tried to address.
Post-incentive epoch (since 2018): finding value in widespread data while managing privacy and cybersecurity risks, driven by the Cures Act.
XXXIV. The ultimate goal and the conformed data model
Health IT policy was never only about forcing EMRs. The goal is better quality, lower cost, improved outcomes.
HITECH and later value-based programs like MACRA and MIPS tie incentives to those broader aims, not just checking boxes.
A major change described is the existence of a conformed data model in U.S. healthcare. That model makes large-scale measurement, reporting, and analytics possible, linking policy, technology, and outcomes.
XXXV. The lecture’s final connected wrap-up
The lecture ends by linking everything:
HITECH created Meaningful Use incentives and penalties, driving rapid EHR adoption.
The program evolved into Promoting Interoperability, focusing on exchange, patient access, and outcomes.
The 21st Century Cures Act targeted information blocking, created USCDI, reinforced patient rights, and required standards like FHIR and APIs.
Policy shaped safety initiatives like closed-loop medication administration and structured data transitions like ICD-10.
As systems became more digital and connected, cybersecurity became a major emerging challenge, governed by layered regulation.
The bigger picture is a cycle: incentives drive adoption, problems emerge, policy adapts, and the system moves toward shared, analyzable data that supports better care outcomes at lower cost.
If you want, I can also turn this into a quiz-prep “what to know + how they’ll ask it” sheet using only these same lecture points (definitions, contrasts, timelines, and the policy-to-practice examples).