27.1 IT in Business Operations

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:

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:

1. Transaction processing — capturing and routing work (orders, claims, payroll, purchase orders) with audit trails
2. Coordination — sharing status across units (bed management, care transitions, referral tracking, OR schedule)
3. 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:

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:

1. Define the decision — what will change if the number moves (staffing, capital, pathway redesign)?
2. Specify the measure — numerator, denominator, exclusions, refresh cadence
3. Validate trust — reconcile to source systems; check for documentation or coding artifacts
4. Diagnose — process, capacity, culture, or data defect?
5. Act and resource — assign owners, remove barriers, fund workflow change
6. 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.