# Malcolm Baracho

Malcolm Baracho writes about healthcare revenue cycle operations and technology, including ways automation, AI, analytics, and system integrations can reduce billing delays, prevent denials, and protect revenue.

- Profile: https://b2binfluencer.marketing/creators/malcolm-baracho/
- LinkedIn: https://www.linkedin.com/in/malcolm-baracho
- Topics: artificial-intelligence, healthcare
- Based on 13 dated posts, latest 2026-09-22

## Summary

Malcolm Baracho is most useful for explaining healthcare revenue cycle problems and where automation, AI, analytics, and integration may help.

- Best for: A healthcare IT services company planning a webinar on agentic AI in revenue cycle management.
- Not for: A consumer health brand seeking a paid social partnership for patient-facing personal-health messages.
- Check first: Ask for current LinkedIn audience data and documentation of healthcare job roles or seniority.

### Takeaways

- Recovering 2% of $8M monthly billing returns $160,000, linked to coding errors and delays.
- Eligibility checks across payer portals and spreadsheets keep a billing coordinator late and delay cash.
- An O typed as a zero put $47,000 at risk, caught by an automated audit trail.

## Main ideas

- **Preventable write-offs stem from quiet, repeating process failures, so automation should target revenue leaks**: Malcolm Baracho frames the revenue cycle problem through a conversation with a hospital CFO who worries less about dramatic disasters than quiet leaks: a small coding error that keeps repeating, a follow-up pushed to tomorrow, a claim sitting too long in the queue. None feels large in the moment, they write, but month after month the problems show up in reports. The argument is not that AI adoption is generally good; it is that agentic AI should target specific points where revenue is lost — catching errors before claims go out, flagging accounts most at risk, telling teams what to work on first, and shifting the culture from reactive firefighting to prevention.
- **Manual payer verification burns out billing staff and delays cash; remove work that should never have been hard**: A post about eligibility checks argues that burnout in revenue cycle operations often comes from working too hard on tasks that should not be hard in the first place. Baracho describes a billing coordinator juggling four browser windows, two spreadsheets, and a sticky note to confirm one insurance eligibility while payer portals repeatedly log her out. They link that manual hunt to claims sitting in limbo and evenings taken from family. Automating payer data retrieval, the post argues, improves both throughput and staff experience. It ends by asking readers which part of their revenue cycle still runs like a fax machine and a prayer.
- **Claim denials start in the back office, not clinical care; accuracy, credentialing, and visibility have to work together**: Baracho argues that roughly 20% of healthcare claims hit a wall before payment because of paperwork rather than bad medicine, and that clinically strong practices can still stall over billing codes that do not match documentation or lapsed credentialing. The post presents denial prevention as a systems problem: billing accuracy, credentialing continuity, and real-time financial visibility need to work as connected parts, not separate fixes. It describes cleaner claims through automation, certified coders catching errors before payers do, EMR data flowing into billing without double entry, and credentialing staying current across networks.
- **Audit readiness protects against human limits, not just compliance paperwork**: In a story set at a multi-specialty network in Phoenix, Baracho argues that revenue cycle visibility is protection, not a luxury. A routine payer audit turned up a single-character error — an 'O' typed as a '0' — and an automated audit trail flagged the mismatch in seconds, taking the room from tension to relief. The post argues that human error is constant, so automation offers more than speed: it insures against the limits of human attention. Audit preparation becomes less like a fire drill and more like routine maintenance.
- **ETL and data pipelines are strategic revenue cycle assets, not invisible plumbing**: Baracho argues that many healthcare analytics delays start in ETL, not dashboards: legacy pipelines were never designed for real-time FHIR data exchange, cloud-native Epic environments, or low-latency AI and predictive models. Add payer-provider interoperability and HIPAA compliance requirements during upgrades, the post says, and even small changes become high-risk projects. The unglamorous pipeline layer determines whether analytics and revenue cycle teams can move at all; an ownership gap — bottlenecks no one owned — often lets the problem persist.
- **EHR interoperability is framed as market coverage, and the post shifts into a direct services offer**: A post on integrating health applications with Cerner EHR/EMR systems notes that Oracle Health, formerly Cerner, supports nearly 23% of U.S. acute care hospitals, making seamless interoperability essential. Baracho outlines the pathway choices — FHIR APIs, SMART on FHIR, and HL7 interfaces — and links accurate, secure, compliant data exchange to structured planning, endpoint validation, and compliance-driven development. The benefits range from improved clinical coordination to stronger revenue cycle outcomes. Unlike the narrative posts, this one is a commercial invitation: it points readers to a document and asks them to message directly about building a custom integration.
- **Baracho tracks operational, data-driven, and interconnected priorities in healthcare finance**: From HFMA 2026 in National Harbor, Maryland, Baracho lists the pressures healthcare finance leaders are discussing: revenue cycle complexity, AI adoption in financial operations, interoperability gaps, and rising cost and compliance pressure. The post draws a market-level conclusion rather than focusing on a single practice: healthcare finance is becoming more operational, data-driven, and interconnected. It also shows Baracho engaging with this audience through conference attendance and in-person networking.

## Work to read

- [Agentic AI and the quiet leaks in revenue cycle](https://www.linkedin.com/posts/malcolm-baracho_healthcarefinance-rcm-aiinhealthcare-activity-7407797079739195393-LWXX)
- [Eligibility checks, billing burnout, and a 20% clean-claim jump](https://www.linkedin.com/posts/malcolm-baracho_revenuecyclemanagement-healthcareoperations-activity-7422299079482863616-5AOJ)
- [A $47,000 typo and the case for audit automation](https://www.linkedin.com/posts/malcolm-baracho_healthcare-rcm-auditreadiness-activity-7413945183693803520-YRyO)
- [ETL bottlenecks as a hidden drag on revenue cycle speed](https://www.linkedin.com/posts/malcolm-baracho_healthcareanalytics-etlstrategy-epicupgrades-activity-7435341381113470976-PnDU)
- [Why claims stall: billing accuracy, credentialing, and visibility](https://www.linkedin.com/posts/malcolm-baracho_healthcarerevenue-medicalpracticemanagement-activity-7426655087965618177-9NO_)
- [Cerner integration as a commercial offer](https://www.linkedin.com/posts/malcolm-baracho_cernerintegration-healthcareinteroperability-activity-7422665343703220224-YN1L)
- [HFMA 2026 and current industry priorities](https://www.linkedin.com/posts/malcolm-baracho_hfma2026-hfma-healthcarefinance-activity-7469760890549059587-IJ_w)

## Brand relationships

- **OSPLabs** (disclosed_partnership)
- **Oracle Health (Cerner)** (mention)
- **Healthcare Financial Management Association (HFMA)** (mention)

## Partnerships

Malcolm Baracho's posts cover revenue-cycle topics: agentic AI for preventing write-offs, automated eligibility checks, audit-readiness alerts, and data-pipeline and integration work around Epic and Cerner. One post invites readers to direct-message about building a custom Cerner integration for a health app, a service inquiry for software work rather than a published sponsorship offer. The posts include no sponsor policy, media kit, rate card, or disclosed brand partnership. Before planning a co-marketing webinar, ask for stated partnership terms, an official inquiry route, audience information used for partnership pitches, and past sponsor disclosures.

## Alternatives

- Justin Nicols: Choose Justin Nicols when the webinar should lead with an executive research-and-ROI argument rather than a practitioner walkthrough. Nicols frames the revenue cycle and finance shared services as healthcare’s highest-ROI opportunity for AI, citing McKinsey’s estimate that AI-enabled process redesign could drive up to 50% productivity gains. They make the blunt case that the revenue cycle is automating inefficiency faster than it is eliminating it: automate a broken process and you get a faster broken process. That’s a pointed opening for a services company pitching redesign before tooling. Nicols also draws three transferable points from a Stanford/Harvard healthcare AI report: access to capability is no longer the constraint, accuracy is not the same as outcomes, and the clearest ROI today lies in documentation and coding busywork—but the payoff is preventing problems (fewer denials, less rework), not processing them faster. For a partner seeking a host who can make the why-now, what-does-the-research-say, where-does-value-land case to executives, Nicols is the stronger fit.
- Chris Johnson: Choose Chris Johnson when the webinar should broaden from revenue cycle to enterprise-wide operational intelligence, or when the partner sells a platform that connects functions rather than a single point solution. The posts describe health systems moving from assembling applications one at a time to building an enterprise capability, and judging technology by whether it contributes to a connected platform where access, capacity, patient flow, staffing and care delivery reinforce one another rather than run in silos. A second post, about a family member’s fall and the many unseen roles that carry a patient journey, offers an operations-level story about how care depends on parts working together. If the campaign is about consolidating operational data and processes across a health system—with revenue cycle as one of several connected functions—Johnson speaks that language more directly than an RCM-only account.
- Matthew Guldin: Choose Matthew Guldin when the webinar doubles as a conference case-study submission or the partner wants results framing to be the draw. Both posts come from years of reviewing HIMSS proposal submissions, with a clear through-line: implementation is not an outcome—impact is. Guldin lays out what makes a health IT story credible: a specific baseline problem and who it affected; before-and-after results (length of stay, clinician minutes saved, a 15% drop in denials, $2 million in savings); a baseline that lets readers judge whether the technology made the difference; honest lessons about what proved harder than expected; and a warning against letting a provider/vendor case study become a product pitch. If the session is meant to help an audience tell and evaluate its own AI implementation stories, especially for a HIMSS-style submission, Guldin sets the standard for the results the room should expect.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/