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.
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.
Key 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.
Check first: Ask for current LinkedIn audience data and documentation of healthcare job roles or seniority.
Main ideas
Preventable write-offs stem from quiet, repeating process failures, so automation should target revenue leaks · Manual payer verification burns out billing staff and delays cash; remove work that should never have been hard · Claim denials start in the back office, not clinical care; accuracy, credentialing, and visibility have to work together
Malcolm Baracho writes about healthcare revenue cycle management and the technology behind it.
Recurring subjects in their posts include billing delays, claim denials, audit readiness, automation, analytics, and system integration.
The posts are useful to follow for their practical framing of back-office problems: a claim stuck in a queue, an eligibility check spread across payer portals, or a small claim error that puts revenue at risk.
Baracho connects operational details to their financial and human consequences, then points to a specific process or technology that could address them.
In one post, they link coding errors, delayed follow-up, and claims sitting in queues to the potential recovery of $160,000 from 2% of $8 million in monthly billing, before describing ways agentic AI might help teams prioritize work.
Other posts make the same theme concrete through an eligibility-checking process that keeps a billing coordinator late, an audit story about a one-character claim error, and an argument that ETL bottlenecks can hold back analytics and revenue-cycle speed.
The set is not all narrative: the Cerner integration post is a direct service-oriented promotion, while the HFMA post is a short snapshot of industry concerns.
Together, these examples show how they frame revenue-cycle technology as an operational problem, not just a software purchase.
Malcolm Baracho's posts return to one diagnosis of healthcare revenue problems: lost money and time usually stem not from dramatic failures or bad clinical care but from small, repeating operational defects — a coding error that recurs, a follow-up pushed to tomorrow, a claim parked too long, an eligibility check spread across four browser windows.
Read more
The priority is to put automation, analytics, and integration to work where revenue leaks, and treat data pipelines and audit visibility as revenue infrastructure rather than back-office plumbing. Their posts mix first-person problem scenes, dollar arithmetic, and technical vocabulary like FHIR, SMART on FHIR, HL7, and ETL, and occasionally shift into a direct services pitch.
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.
Read more
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.
Baracho does the arithmetic: recovering just 2% on $8M in monthly billing returns $160K, enough to fund a care program, avoid another year of delayed technology upgrades, and recognise staff.
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.
Read more
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.
The post describes a named billing coordinator, Sarah, joking about living her best life with Blue Cross, Aetna, and whichever portal logged her out that day.
An automated eligibility checker pulls real-time payer data.
The post reports a clean claim rate that jumped by over 20%, fewer denials, better cash flow, and Sarah leaving at five.
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.
Read more
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.
The post quotes a dermatology practice owner: 'I can diagnose melanoma in minutes.
But fighting a claim denial?
That takes weeks.' Baracho uses the line to show the gap between clinical skill and back-office friction, then lists an integrated workflow and its payoff: fewer denials, faster payments, and revenue that reflects the work being done.
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.
Read more
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.
The post puts $47,000 at risk from a single-character claim typo and quotes the CFO's reframing of the technology: 'It's not automation.
It's insurance against human limits.' Baracho reports no major compliance scare in months and an end to weekend spreadsheet marathons.
They ask whether readers would know about a $47K typo before the auditor does.
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.
Read more
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.
The post cites organisations improving revenue cycle speed by up to 25% simply by removing ETL bottlenecks no one previously owned. It calls ETL a strategic advantage rather than infrastructure and asks which part of a data pipeline everyone avoids touching.
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.
Read more
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.
The post carries the OSPLabs hashtag and several tagged names, and closes with an invitation to start a discussion on a custom Cerner integration solution for a health app. The hashtag and tags show how the post is packaged; they are not by themselves evidence of a paid client relationship, and no payment should be inferred.
This post shifts from the storytelling voice used for revenue cycle problems to a document-and-direct-message services pitch, a commercial register that distinguishes it from the more anecdotal posts.
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.
Read more
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.
The post invites anyone attending HFMA 2026 to connect during the conference and names four pressures shaping the field.
This post offers a clear answer to what Malcolm Baracho means by agentic AI in revenue cycle management.
Read more
Newcomers can see the concrete problem, the dollar math, and the specific tasks AI is meant to perform.
Malcolm Baracho opens with a hospital CFO who is less worried about a dramatic disaster than about quiet leaks: a small coding error that keeps repeating, a follow-up pushed to tomorrow, a claim sitting too long in the queue.
The post puts a number on the problem: recovering just 2% on $8M in monthly billing returns $160K.
It then frames agentic AI as a way to spot errors before claims go out, flag at-risk accounts, guide teams on what to work on first, and shift the culture from reactive to proactive.
For brands planning a campaign
For a webinar on agentic AI in RCM, this post offers a ready-made hook: the 2%/160K arithmetic and the quiet-leaks list. A healthcare IT services company can build the opening around those elements and invite Malcolm Baracho to explain how agentic AI catches errors before claims go out.
This post makes RCM automation tangible through a named coworker's evening, not just a product claim.
Read more
Readers interested in the human side of the automation argument should start here.
Malcolm Baracho tells the story of billing coordinator Sarah, who had four browser windows, two Excel sheets, and a sticky pad open to confirm one insurance eligibility.
The evening scene includes Sarah's joke about payer portals logging her out.
An automated eligibility checker pulls real-time payer data; the clean claim rate jumped by over 20%, denials dropped, and Sarah leaves at 5.
The post ends by asking what in a revenue cycle still feels like it runs on a fax machine and a prayer.
For brands planning a campaign
Useful for a webinar segment on adoption and staff experience. The line that burnout does not always come from working too much can anchor the human-impact argument, while Sarah's scene offers a relatable example of the problem the technology solves.
This is the set's most concrete story about audit readiness.
Read more
Readers can see why small data errors matter and how automated checks change the compliance experience.
At a multi-specialty network in Phoenix, a routine payer audit found a single character error: an O typed as a 0 in a claim, putting $47,000 at risk.
Malcolm Baracho describes the room going quiet, the billing lead's face going pale, and then an automated audit trail popping up a bright-red alert: mismatch found, corrected, risk eliminated in seconds.
The post quotes the CFO saying, It is not automation.
It is insurance against human limits.
For brands planning a campaign
A strong narrative for a webinar or case-study segment on audit readiness and compliance. It turns a compliance issue into a specific, memorable story for an audience of healthcare finance leaders.
This post connects data infrastructure to revenue cycle outcomes, an angle that can get lost when the conversation stays on AI models or dashboards.
Read more
It shows how Malcolm Baracho frames ETL as a strategic advantage.
Malcolm Baracho argues that most healthcare analytics delays start not in dashboards but in ETL.
The post lists what legacy pipelines were not designed for: real-time FHIR data exchange, cloud-native Epic environments, low-latency AI and predictive models, payer-provider interoperability, and HIPAA compliance during upgrades.
Fixing ETL bottlenecks can improve revenue cycle speed by up to 25%.
The post closes by asking what part of a data pipeline everyone avoids touching.
For brands planning a campaign
A useful supporting angle for a webinar on agentic AI in RCM: before AI can act, the data pipeline has to carry the signal. A services company can use this post to broaden the webinar beyond the AI model and discuss the ETL and interoperability groundwork.
This post frames denial prevention as a systems problem rather than a single fix.
Read more
It shows the range of back-office issues Malcolm Baracho connects.
Malcolm Baracho opens with the claim that nearly 20% of healthcare claims hit a wall before payment because of paperwork, not bad medicine.
The post quotes a dermatology practice owner: I can diagnose melanoma in minutes.
But fighting a claim denial?
That takes weeks.
It then connects billing accuracy, credentialing continuity, and real-time financial visibility, and describes modern integration, with EMR data flowing directly into billing and credentialing kept current.
For brands planning a campaign
Useful for a webinar discussion of integration and credentialing alongside AI. The dermatology quote offers a short, audience-facing example of the cost of paperwork failures.
Open this to see Malcolm Baracho's commercial and inbound side and how they package a specific integration offer.
Read more
Its tone differs from the narrative posts and shows the services context.
This post takes a more promotional tone.
Malcolm Baracho notes that Oracle Health, formerly Cerner, supports nearly 23% of U.S. acute care hospitals and discusses FHIR APIs, SMART on FHIR, and HL7 interfaces.
It points readers to a document and ends with an invitation to start a discussion on building a custom Cerner integration solution for a health app, along with the OSPLabs hashtag and several tagged people.
For brands planning a campaign
A partner company can see how Malcolm Baracho presents a Cerner integration offer and the audience they address. For a co-marketing webinar, this may indicate an existing commercial angle that overlaps with an Epic or Cerner integration audience.
This short post snapshots the priorities Malcolm Baracho is tracking in 2026 and shows they are present at a major healthcare finance event.
Read more
It provides conference context for the other posts.
Malcolm Baracho reports attending HFMA 2026 in National Harbor, Maryland, and lists challenges heard from healthcare finance leaders: revenue cycle complexity, AI adoption in financial operations, interoperability gaps, and rising cost and compliance pressure. The post says the agenda makes one thing clear: healthcare finance is becoming more operational, more data-driven, and more interconnected.
For brands planning a campaign
Useful for timing and audience relevance: a co-marketing webinar on agentic AI in RCM can position itself against the same list of industry pressures Malcolm Baracho names here.
Malcolm Baracho frames preventable write-offs as the core problem in healthcare revenue cycle management.
Read more
The post opens with a conversation with a hospital CFO who was less worried about a dramatic failure than quiet leaks: a recurring coding error, follow-up pushed to tomorrow, or a claim left too long in the queue.
They do the arithmetic — recovering 2% on $8M in monthly billing returns $160K — and connect that figure to recognisable outcomes, including funding a care program, avoiding a delayed technology upgrade, and recognising staff.
The post names specific areas where agentic AI helps: catching errors before claims leave, flagging at-risk accounts, prioritising work, and shifting from firefighting to prevention.
The closing question asks not whether an organisation uses AI, but whether it applies AI where revenue is actually lost.
Opens with a conversation with a finance leader, quantifies the loss, then turns the recovered money into decisions a hospital already cares about.
For brands planning a campaign
Strong material for a webinar or co-marketing piece built around revenue recovery rather than general AI adoption. The 2%-of-monthly-billing framing gives a host or partner a concrete opening and use cases to shape the agenda.
Eligibility verification and billing-staff burnout
A post on revenue cycle operations describes a billing coordinator working across four browser windows, two spreadsheets, and a sticky note to confirm a single insurance eligibility, while payer portals repeatedly log her out.
Read more
Baracho connects the manual work to claims stuck in limbo and evenings lost with family, arguing that burnout often comes from working too hard on tasks that should not be hard.
The post reports an automated eligibility checker pulling real-time payer data, with quoted results including a clean-claim rate improvement above 20%, fewer denials, better cash flow, and staff leaving at five.
It ends by asking readers which part of their revenue cycle still runs like a fax machine and a prayer.
Opens with a workplace scene, moves to vendor-style outcomes, then closes with a question inviting readers to name their own manual bottleneck in the comments.
For brands planning a campaign
Useful for eligibility, payer-connectivity, or workflow automation vendors. The burnout angle offers a human entry point for a case study or webinar, while the closing question can prompt audience discussion during a live session.
Denials begin in the back office, not in clinical care
Baracho argues that roughly 20% of healthcare claims hit a wall before payment because of paperwork rather than bad medicine.
Read more
The post illustrates the point with a dermatology practice owner's observation that diagnosing melanoma takes minutes while fighting a denial takes weeks.
It names three linked requirements — billing accuracy, credentialing continuity, and real-time financial visibility — and describes an integrated back office: automation for cleaner claims, certified coders catching errors before payers do, EMR data flowing into billing without double entry, current credentialing across networks, and staff freed from chasing paperwork.
The payoff: fewer denials, faster payments, and revenue that reflects the work being done.
Opens with a quoted practitioner line, states the irony plainly, then lists the operational links and outcomes in short, parallel points.
For brands planning a campaign
Supports a message about connecting back-office systems rather than selling one tool. Credentialing, coding, and practice-management vendors can use the three-dot framing to position a joint offer for practices that are clinically strong but revenue-operationally weak.
A post set in a conference room at a multi-specialty network in Phoenix describes a routine payer audit that uncovered a single-character error — an “O” typed as a “0” — putting $47,000 at risk.
Read more
Baracho builds the scene to the moment an automated audit trail flags the mismatch and clears the risk in seconds, then quotes the CFO's reframing: not automation, but insurance against human limits.
The post reports no major compliance scare since, an end to weekend spreadsheet marathons, and audit preparation that feels like routine maintenance rather than a fire drill.
It closes on visibility as protection and asks whether readers would know about a $47K typo before the auditor does.
Builds tension around a small error with large exposure, resolves it with automated detection, then uses a quoted line from the client side to redefine what the product buys.
The $47,000 figure and the surrounding scene come from the post itself and are not independently verified; treat them as the author's illustrative framing rather than a documented audit outcome.
For brands planning a campaign
A concrete compliance-risk opener for audit-readiness or revenue-integrity software. The before-and-after structure — near-miss, automated catch, calmer audit cycle — translates well to a webinar narrative or short case-study video.
ETL and data pipelines as revenue cycle infrastructure
Baracho argues that most healthcare analytics delays start in ETL, not dashboards, because legacy pipelines were never designed for real-time FHIR data exchange, cloud-native Epic environments, or low-latency AI models.
Read more
Payer-provider interoperability and HIPAA compliance during upgrades make even small changes high-risk.
The post says the right pipelines keep data flowing cleanly between systems, preserve analytics through migrations, and help revenue cycle teams move faster.
It cites organisations improving revenue cycle speed by up to 25% simply by removing ETL bottlenecks no one owned.
The conclusion is blunt: ETL is no longer infrastructure but a strategic advantage.
The post then asks which pipeline component everyone avoids touching.
Reframes a technical subject as an executive concern, using an ownership gap to explain why the problem persists.
For brands planning a campaign
Relevant to data-platform, integration, and cloud vendors selling to health systems. The ownership angle gives a technical webinar a business case, and the closing question works as a live poll or discussion prompt.
EHR interoperability and Cerner/Oracle Health integration
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.
Read more
Baracho lays out 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 stated benefits include improved clinical coordination and stronger revenue cycle outcomes.
The post points readers to a document for details, credits OSPLabs among its tags, and invites them to message directly about building a custom integration.
Frames a technical integration decision as a market-coverage issue, then directs readers to a document and a direct conversation.
The post references OSPLabs and invites direct messages about custom integration work. It shows how a service conversation is framed in Baracho's own material, but does not establish a paid client relationship.
For brands planning a campaign
Shows which integration topics Baracho treats as commercially live, including FHIR, SMART on FHIR, and HL7 pathways. A platform vendor partnering on an interoperability webinar can align with this vocabulary; the document-plus-conversation pattern suggests Baracho favours a takeaway asset paired with a direct follow-up path.
Conference-floor view of healthcare finance priorities
A post from HFMA 2026 in National Harbor, Maryland, lists the challenges Baracho heard from healthcare finance leaders: revenue cycle complexity, AI adoption in financial operations, interoperability gaps, and rising cost and compliance pressure.
Read more
It says healthcare finance is becoming more operational, data-driven, and interconnected. The post invites conference attendees to connect during the event.
Uses a live industry event to frame market-level claims rather than tell a single-practice story, then turns attendance into an in-person networking invitation.
For brands planning a campaign
Evidence of conference presence and an audience of healthcare finance leaders makes an event-based collaboration plausible—a conference recap, booth session, or webinar timed to HFMA themes. Aligning messaging with the four named pressures gives partners a shared vocabulary for the pitch.
A post frames Cerner EHR/EMR integration as a strategic step for health applications, notes Oracle Health's reach across roughly 23% of U.S. acute care hospitals, and points to FHIR APIs, SMART on FHIR, and HL7 interfaces as pathways to use.
Read more
Oracle Health is presented as the system an app would integrate with, not as a partner paying for the post.
Healthcare Financial Management Association (HFMA)
Mention
A post says they were at HFMA 2026 in National Harbor, Maryland, connecting with healthcare finance leaders on revenue cycle complexity, AI adoption in financial operations, interoperability gaps, and cost and compliance pressure, and invites others at the conference to connect.
Read more
Ask whether they had a sponsorship or speaking role.
Malcolm Baracho writes about the operational side of healthcare money: the small, repeating defects — a coding error that keeps recurring, a claim parked too long in the queue, an eligibility check spread across four browser windows — that drain revenue before anyone notices.
Read more
Start with the posts that narrate one specific problem and then do the arithmetic; they set up the argument that automation belongs where revenue actually leaks rather than everywhere at once.
Another thread is the back-office plumbing that determines whether analytics and revenue teams can move at all, including ETL pipelines and EHR integration.
A third is the effect on staff, shown through a billing coordinator fighting payer portals rather than abstract efficiency claims.
The register shifts between first-person problem scenes with dollar figures and a document-plus-direct-message services post.
For the analytical voice, lead with the narrative posts and treat the services post as a signal of how a commercial conversation is framed, not as a client engagement.
Writes about the same corner of healthcare as Baracho: AI and workflow redesign applied to the revenue cycle, finance, and shared services, where the work is high-volume and rules-heavy.
Read more
Both argue that the value depends on what you automate, not whether you automate. Nicols makes the case that revenue cycle is automating inefficiency faster than it is eliminating it; Baracho makes a parallel point by directing agentic AI at the points where revenue leaks rather than at AI adoption in general.
Nicols reasons from industry reports and executive strategy, quoting McKinsey on productivity gains and the ARISE healthcare AI research.
Their emphasis is on organisational decision-making and where AI can reshape an operating model.
Baracho stays closer to the floor, building arguments from named client conversations, dollar arithmetic, and a billing coordinator's evening, then turning to specific technical pathways such as FHIR and HL7.
Read Nicols after Baracho's narrative posts for the strategic frame; read Baracho first for concrete implementation vocabulary.
Both write for people running the operational machinery of a health system rather than for clinicians, and both treat technology investment as an operational capability question rather than a product purchase.
Read more
Johnson argues that health systems assembled technology one point solution at a time and now need those capabilities to work together. Baracho makes a comparable argument by describing billing accuracy, credentialing continuity, and financial visibility as connected dots rather than separate fixes.
Johnson's subject is care delivery and patient flow — beds, transport, environmental services, discharge coordination, staffing, and capacity — and their recurring theme is connecting operational intelligence across an enterprise.
Baracho's subject is money: denials, write-offs, audits, eligibility, and the data pipelines feeding revenue cycle teams.
Johnson also sets out to humanise the roles a patient never sees, while Baracho's human detail focuses on the cost of manual work.
Read Johnson for the patient-journey side of operations and Baracho for the finance side.
Both are interested in what actually makes health IT work after a platform goes in, and both push back on product-led storytelling.
Read more
Reviewing HIMSS conference proposals, Guldin argues that implementation is not an outcome and that impact is.
Baracho makes the same move in miniature by measuring an automated eligibility check by clean claim rate and staff leaving at five rather than by the tool being installed.
Both consistently ask for a baseline, a result, and the lessons learned.
Guldin writes as an evaluator and reviewer, focused on how a case study or conference session should be argued and measured, for healthcare conference submitters and attendees.
Baracho writes as a practitioner describing revenue cycle work, including a commercial services post among the narrative ones.
Guldin's material offers criteria for judging an implementation story; Baracho's offers the implementation story itself.
If comparing their practical guidance, ask Baracho for revenue cycle specifics and Guldin for conference review criteria.
Malcolm Baracho’s posts cover AI for preventing claim errors, prioritizing accounts, and reducing avoidable write-offs, making them relevant to a webinar about agentic AI in revenue cycle management.
Read more
Before booking, ask for current LinkedIn audience data and, if the campaign requires healthcare job roles or seniority, a documented audience survey or other documentation of those professional attributes.
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.
Read more
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.
A healthcare IT services company looking to co-host a webinar on agentic AI in revenue cycle management has a credible partner in Malcolm Baracho.
Read more
Their posts provide the topic, framing and arithmetic for an agenda.
The write-off post is the centrepiece: Baracho opens with a hospital CFO worried less about a dramatic failure than about quiet leaks — a coding error that keeps repeating, a follow-up pushed to tomorrow, a claim sitting too long in the queue — then puts a number on the loss: recovering 2% on $8M in monthly billing returns $160K.
They identify where agentic AI is meant to work: catching errors before claims go out, flagging at-risk accounts, telling teams what to work on first, and shifting a culture from reactive to proactive.
The webinar outline is already half-built.
The fit holds because Baracho's posts cover more than one topic.
An eligibility-automation story about a billing coordinator working four browser windows and two spreadsheets provides the human opening and reports a clean-claim gain above 20%.
A payer-audit scene — an O typed as a zero putting $47,000 at risk, caught by an automated audit trail — gives an audit-readiness segment its near-miss narrative.
An ETL post widens the conversation from the AI model to the data plumbing beneath it, citing up to 25% faster revenue cycle work from clearing pipeline bottlenecks.
A Cerner/Oracle Health integration post shows the vocabulary and commercial services angle the partner would be selling alongside.
And the HFMA 2026 post aligns with four pressures the audience feels: revenue cycle complexity, AI adoption in financial operations, interoperability gaps, and cost and compliance pressure.
Two gaps affect what the partner can promise.
The posts don't document audience demographics: the account has about 6,810 followers, but that count says nothing about composition, so no reach, job-role mix or seniority claim can be made before booking.
The posts also show no media kit, rate card, sponsor policy or disclosed past brand partnership.
Request current audience data and any past sponsor disclosures before signing a contract.
When to choose a specialist
A consumer health brand — for example, a patient-facing wellness or care-navigation app — seeking a paid social partnership to reach patients with a personal-health message is a poor fit for Baracho's posts.
Read more
All seven address a B2B operations and finance audience: a hospital CFO, a billing coordinator, a multi-specialty network's audit team, a dermatology practice owner, and healthcare finance leaders at a conference.
The subject matter is revenue cycle management — claims, denials, eligibility, credentialing, ETL pipelines and EHR integration — not personal health, patient behaviour or consumer lifestyle topics.
The posts don't address patients or show consumer reach or consumer-facing formats.
A consumer campaign's message and mechanics can't be planned without audience data and a documented sponsorship offer.
A worked campaign example
A healthcare IT services company wants to propose a co-marketing webinar on agentic AI in revenue cycle management. Angle: 'The quiet leaks — finding the revenue your cycle loses before a claim goes out.'
Structure.
Open with the CFO's quiet-leaks list and the 2%-on-$8M math: it gives the audience a concrete number in the first minutes and frames the session as revenue protection rather than AI adoption for its own sake.
Run a live poll using the closing question from the eligibility post — what in your revenue cycle still runs like a fax machine and a prayer — to surface the room's bottlenecks.
Middle.
Show the human cost with the one-coordinator, four-browser-windows story and its 20% clean-claim result, then raise the stakes with the audit near-miss: an O typed as a zero, $47,000 at risk, cleared in seconds by an automated audit trail.
Together, the stories cover routine drag and acute risk.
Groundwork segment.
Use the ETL post to argue that agentic AI helps only when the pipeline carries clean, timely data — clearing unowned bottlenecks can mean up to 25% faster revenue cycle work.
This widens the pitch beyond the AI model and speaks directly to a services company's integration and data work, the same territory as the Cerner/Oracle Health post.
Close and takeaway.
Offer a one-page 'quiet-leaks self-assessment' as a downloadable asset, then invite a direct conversation — the same document-plus-message pattern Baracho uses in the Cerner post.
The HFMA 2026 list gives the partner a shared vocabulary for the invitation.
Roles and caveats.
Baracho carries the practitioner voice and stories; the services company carries the platform and follow-up offer.
The dollar and percentage figures in the posts are Baracho's own framing and are not independently verified, so present them as examples to discuss, not audited benchmarks.
Request current audience data and a documented partnership format before committing.
Choose Justin Nicols when the webinar should lead with an executive research-and-ROI argument rather than a practitioner walkthrough.
Read more
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.
The arguments are analytical and second-hand, built on McKinsey and research-report citations rather than first-person operational scenes.
A webinar with this host would need the partner to supply concrete examples and implementation detail; the partner would carry almost all of the how-to content.
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.
Read more
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.
The revenue cycle specifics are thin: the posts contain no claims, denials, eligibility, coding or payer-audit material, so the partner would need to introduce the agentic-AI-in-RCM premise. Ask whether the partner can supply enough domain content to keep the session focused on the revenue cycle rather than general operational integration.
Choose Matthew Guldin when the webinar doubles as a conference case-study submission or the partner wants results framing to be the draw.
Read more
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.
Guldin’s material is about how to present and assess health IT work, not RCM, agentic AI, claims or payer operations. For an agentic-AI-in-RCM session, Guldin would bring the credibility standard, but the partner would need to provide the domain substance.
Malcolm Baracho's seven LinkedIn posts at linkedin.com/in/malcolm-baracho, alongside two posts each from three other creators who write in adjacent areas of healthcare operations for similar-creator comparisons, cover revenue cycle management and preventable write-offs, payer eligibility verification and billing-staff burnout, audit readiness, claim denial prevention and practice management, ETL and healthcare analytics pipelines, Cerner/Oracle Health integration, and an HFMA 2026 conference post.
All seven appear in full; no videos, transcripts, articles, books, shows, or earlier career material appear alongside these posts, and the posts do not give dates apart from the HFMA 2026 reference, so the patterns described here reflect these posts rather than a dated career trajectory.
Quoted figures, including $160K in recovered revenue, a 20% clean-claim gain, $47K put at risk by a claim typo, and a 25% revenue cycle speed improvement, come from the posts themselves and are not independently verified.
The account shows a follower count of roughly 6,810, but no job-role, seniority, or industry breakdown, and no media kit, rate card, or sponsorship policy appears alongside the posts.
Anyone searching for Baracho is also looking for signature work such as books, shows, or earlier roles; Baracho's posts do not establish whether any exist, and targeted research into those areas is needed before this can be treated as complete name-search coverage.
