Study guide

27.1 IT in Business Operations

FACHE Board of Governors Exam in Healthcare Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 About the FACHE Credential 1.2 Current Exam Facts 1.3 Eligibility, Application & Recertification

2 Healthcare Systems & Trends

2.1 Healthcare and Medical Terminology 2.2 Healthcare Trends 2.3 Continuum of Care Levels

3 Healthcare Organizations & Services

3.1 Levels of Service from a Business Perspective 3.2 Types of Healthcare Organizations 3.3 Ancillary and Support Services

4 Integration, Clinicians & Staff Perspectives

4.1 Integration, Competition & Partnerships 4.2 Clinician Roles and Qualifying Criteria 4.3 Staff Perspectives & Evidence-Based Management

5 Patient Perspective & Care Delivery

5.1 Patient vs Provider Perspective 5.2 Access, Quality, Cost & Community 5.3 Care Delivery Models and Access Points

6 Digital Health, Population Health & Prevention

6.1 Digital Health 6.2 Population Health Concepts 6.3 Social Determinants & Preventative Medicine

7 Management Planning & Organizational Systems

7.1 Implementation Planning 7.2 Emergency Preparedness & NIMS 7.3 Organizational Systems & Management Functions

8 Leadership, Teams & Change

8.1 Leadership and Communication Styles 8.2 Team-Building Techniques 8.3 Change Management & Organizational Development

9 Collaboration, DEIJ & Networks

9.1 Stakeholder Collaboration 9.2 DEIJ & Resource Allocation 9.3 Network Structures & Collective Bargaining

10 Financial Accounting & Budgeting

10.1 Financial Accounting and Ratios 10.2 Operating Budgets 10.3 Capital Budgeting

11 Reimbursement, Productivity & Controls

11.1 Reimbursement Methodologies 11.2 Productivity Measures 11.3 Financial Controls

12 Revenue, Business Cases & Capital Finance

12.1 Revenue Generation and Payer Mix 12.2 Business Cases & Financial Decision Impacts 12.3 Asset Management & Financing

13 Philanthropy, Supply Chain & Revenue Cycle

13.1 Philanthropy and Foundations 13.2 Supply Chain Management 13.3 Revenue Cycle

14 HR Laws, Recruitment & Staffing

14.1 HR Laws and Regulations 14.2 Recruitment and Retention 14.3 Staffing Methodologies

15 Performance, Engagement & Compensation

15.1 Performance Management Systems 15.2 Motivation, Development & Engagement 15.3 Compensation and Benefits

16 Workplace Safety, Conflict & Labor Relations

16.1 Employee Safety, Security & Health 16.2 Conflict, Grievances & Selection 16.3 Labor Relations & HR Decision Impacts

17 Job Design, Succession & Coaching

17.1 Job Design 17.2 Succession Planning, Mentorship & Coaching

18 Confidentiality, Compliance & Payment Rules

18.1 Confidentiality and Privacy Laws 18.2 Healthcare Compliance Laws 18.3 Medicare, Medicaid & Third-Party Payment Regulations

19 Accreditation, Patient Rights & Ownership Rules

19.1 Accreditation & Inspection Standards 19.2 Patients' Rights Laws 19.3 Nonprofit vs For-Profit Requirements

20 Regulatory Impacts, Labor Law & M&A

20.1 Regulatory Impact on Executive Decisions 20.2 Collective Bargaining Laws 20.3 Legal Implications of Mergers & Acquisitions

21 Benchmarking, Peer Review & Risk

21.1 Benchmarking & Best Practices 21.2 Medical Staff Peer Review 21.3 Risk Management Programs

22 Improvement Methods & Measurement

22.1 PDSA, Lean & Six Sigma 22.2 Clinical Performance Improvement & Pathways 22.3 Quality Measurement & HCAHPS

23 Utilization, Patient Safety & Quality Impacts

23.1 Utilization Review & Case Management 23.2 Patient Safety Tools 23.3 How Quality Impacts Operations

24 Strategic Planning, Business Planning & Contracts

24.1 Strategic Planning Process 24.2 Business Planning for Services 24.3 Business Contracts

25 Socioeconomic Context, Marketing & Media

25.1 Socioeconomic Environment 25.2 Marketing Principles 25.3 Media, Social Media & Community Relations

26 Negotiation & Business Decision Impacts

26.1 Contract Negotiation 26.2 Business Decision Impacts

27 Health IT Operations, Trends & Regulation

27.1 IT in Business Operations 27.2 Technology Trends & Clinical Applications 27.3 HIPAA Security, HITECH & Interoperability

28 Informatics, IT Impacts & Continuity

28.1 Health Informatics for Operational Decisions 28.2 IT Decision Impacts 28.3 Information Systems Continuity

29 IT Acquisition & Analytics

29.1 IT Selection, Acquisition & Maintenance 29.2 Healthcare Analytics & Clinical Informatics

30 ACHE Ethics, Patient Rights & Ethics Committees

30.1 ACHE Code of Ethics 30.2 Patients' Rights & Responsibilities 30.3 Ethics Committees

31 Diversity, Conflicts of Interest & Research Ethics

31.1 Cultural & Spiritual Diversity 31.2 Conflict of Interest 31.3 Unethical Actions & Human-Subject Research

32 Professional Norms, Ethical Culture & Diversity Statement

32.1 Professional Norms & Standards 32.2 Creating an Ethical Culture 32.3 ACHE Statement on Diversity

33 Governance Theory, Structure & Medical Staff

33.1 Governance Theory 33.2 Governance Structure & Operations 33.3 Medical Staff Structure

34 Board Accountability & Public Policy

34.1 Board Role, Accountability & Fiduciary Duty 34.2 Public Policy & Advocacy

27.1 IT in Business Operations

Key Takeaways Explain This Topic AI

Healthcare IT is an enterprise operating system spanning clinical care, revenue cycle, supply chain, HR, facilities, and governance—not a back-office cost center.

Core operational systems include EHR/EMR, revenue cycle (RCM), ERP/supply chain, HRIS, imaging/PACS, laboratory/LIS, pharmacy, and patient engagement platforms that must interoperate.

Business intelligence (BI) turns operational and clinical data into decision support through warehouses/lakes, semantic models, dashboards, and governed self-service analytics.

Executive IT governance balances strategic alignment, portfolio prioritization, cybersecurity, vendor management, total cost of ownership, and clinical workflow impact.

FACHE leaders evaluate IT investments by access, quality, safety, experience, workforce productivity, and financial performance—not feature lists alone.

Last updated: August 2026

IT in Business Operations

Quick Answer: Information technology is the operating backbone of modern healthcare organizations. FACHE executives must understand how IT supports clinical and administrative workflows , which major system domains exist , and how business intelligence converts data into decisions —not how to code software. The Board of Governors outline expects leaders who can resource, govern, and evaluate IT as a strategic business capability.

Healthcare Technology and Information Management on the ACHE exam treats IT as management knowledge. Items often ask whether a CEO or COO is underinvesting in data infrastructure, confusing a dashboard with a decision system, or buying technology without workflow redesign. Leaders who frame IT solely as “the CIO’s problem” fail scenarios that require cross-functional trade-offs among safety, access, cost, and workforce.

Why IT Is Business Infrastructure

Every major organizational process now depends on digital systems:

Business domain Typical systems Executive outcomes at risk if weak

Clinical care EHR/EMR, CPOE, e-prescribing, clinical decision support Safety, quality measures, documentation integrity

Revenue cycle Registration, coding, claims, denial management, patient accounting Cash flow, denial rates, compliance

  • Supply chain / ERP Purchasing, inventory, AP/AR, general ledger Cost per case, stockouts, financial reporting
  • Workforce HRIS, credentialing, scheduling, timekeeping Staffing reliability, labor cost, onboarding speed

Diagnostics LIS, PACS/VNA, cardiology and pathology systems Turnaround time, result routing, diagnostic quality

Patient access & engagement Scheduling, portals, CRM, call centers Access, no-shows, experience, loyalty

Facilities & safety Building systems, RTLS, security, biomedical device networks Environment of care, device availability, physical security

IT failures are business failures : delayed discharges from broken interfaces, lost revenue from claim-edit gaps, unsafe medication orders from poorly configured alerts, and board blind spots when operational data cannot be trusted.

Role of IT in Day-to-Day Operations

Operationally, IT enables three interlocking capabilities:

Transaction processing — capturing and routing work (orders, claims, payroll, purchase orders) with audit trails

  • Coordination — sharing status across units (bed management, care transitions, referral tracking, OR schedule)
  • Control and learning — monitoring performance, detecting exceptions, and supporting continuous improvement

Executives should insist that major clinical and administrative processes have a system of record , clear data owners , and defined escalation paths when systems or interfaces fail. Shadow IT (unsanctioned spreadsheets, consumer messaging apps, departmental databases) often signals unmet workflow needs—and creates privacy, security, and reliability risk.

Key executive responsibilities for IT in operations include:

  • Strategic alignment — portfolio of projects maps to access, quality, growth, and margin goals
  • Service reliability — uptime SLAs for clinical-critical systems; disaster recovery and downtime procedures

Interoperability within the enterprise — interfaces and integration engines that keep departments from becoming data islands

User adoption and training — technology value appears only when clinicians and staff can use systems safely and efficiently

Vendor and contract discipline — total cost of ownership, exit clauses, data ownership, and performance remedies

  • Cyber and privacy posture — security as an operational control, not an annual checklist
  • Enterprise System Architecture (Executive View)

Leaders do not need network diagrams, but they do need a mental model of how systems connect:

  • Clinical core — EHR plus departmental systems (lab, radiology, pharmacy, perioperative)
  • Administrative core — ERP/finance, HR, supply chain
  • Revenue engine — RCM suite tightly coupled to clinical documentation and coding
  • Integration layer — HL7/FHIR interfaces, APIs, enterprise service bus or integration platform
  • Analytics layer — warehouse/lakehouse, quality registries, operational dashboards
  • Engagement layer — portals, apps, telehealth platforms, CRM

Fragmented architecture multiplies cost and error. Consolidation is not always right (best-of-breed can win for specialty services), but every exception should have a deliberate integration and support plan. FACHE scenarios often test whether a leader is adding yet another point solution without ownership, interface funding, or analytics definitions.

Business Intelligence Systems

Business intelligence (BI) is the disciplined use of data, tools, and processes to inform decisions. It is broader than “pretty charts.” Mature BI includes:

Data acquisition and integration — extracting from EHR, claims, cost accounting, HR, and external sources

Data quality and master data management — patient identity, provider directories, location and service-line hierarchies

  • Semantic / metrics layer — agreed definitions for LOS, denial rate, productivity, mortality, access metrics
  • Reporting and visualization — operational boards, executive scorecards, self-service exploration
  • Advanced analytics — forecasting, risk stratification, process mining (where maturity allows)

Governance — access controls, change control for metric definitions, and education so leaders interpret correctly

BI serves different decision horizons:

  • Horizon Example questions Typical BI products
  • Real-time / near real-time ED boarding, OR turnover, bed status Command-center dashboards, alerts
  • Tactical (daily–monthly) Productivity, denials, HAI trends, staffing Service-line and unit scorecards

Strategic (quarterly–annual) Market share, contribution margin, quality vs. peers Board dashboards, strategy maps

Executives should treat metric governance as seriously as financial controls. When finance, quality, and operations use different denominators for “readmission rate” or “OR utilization,” debates become political rather than analytic. A BI governance committee (or equivalent) should own definitions, source-of-truth designations, and publication standards.

From Data to Decision: Executive Practice

A practical cycle for leaders:

Define the decision — what will change if the number moves (staffing, capital, pathway redesign)?

  • Specify the measure — numerator, denominator, exclusions, refresh cadence
  • Validate trust — reconcile to source systems; check for documentation or coding artifacts

Diagnose — process, capacity, culture, or data defect?

  • Act and resource — assign owners, remove barriers, fund workflow change
  • Review — close the loop in operations meetings and board quality/finance committees

BI that never changes a budget line, staffing plan, or clinical standard is decoration. Conversely, acting on unvalidated data creates false confidence. High-reliability organizations pair analytics with front-line knowledge—dashboards start conversations; they do not end them.

Governance, Investment, and Value

IT portfolio management is a core executive function. Demand always exceeds capacity. Prioritization criteria typically include regulatory/safety necessity, strategic fit, ROI or cost avoidance, clinical champion readiness, technical risk, and total cost of ownership (licenses, interfaces, training, analytics, cybersecurity, replacement cycles).

Capital and operating budgets should fund implementation and optimization , not only purchase. Many failed EHR or BI programs underfunded training, super-users, interface monitoring, and post-go-live improvement. Value realization plans define baseline metrics and expected movement—throughput, documentation time, denial rates, order set adoption—before go-live hype peaks.

  • Pitfalls FACHE Leaders Avoid
  • Treating IT as a pure cost-reduction lever while ignoring safety and access benefits
  • Buying technology to “check a digital box” without workflow redesign
  • Equating data volume with insight (data lakes without definitions produce swamps)
  • Allowing every department to define its own “truth” metrics
  • Underestimating change management and physician/nursing engagement
  • Ignoring cybersecurity and downtime readiness as operational risks
  • Outsourcing strategy to vendors instead of retaining clinical and business ownership
  • Executive Decision Lens

When evaluating any IT or BI proposal, FACHE leaders ask: What operational problem or strategic opportunity does this solve? Who owns the process end-to-end? How will success be measured in clinical, operational, and financial terms? What is the integration and support model? How do privacy and security controls travel with the data? What happens when the system is down? Technology creates value only when it improves how the organization runs for patients, staff, and the communities it serves.