Key takeaways
- Healthcare depth matters most where the work touches data standards, claims, regulation or clinical workflow.
- Platform projects inside healthcare companies often do fine with strong general IT people.
- Mixing a few domain experts with general IT professionals is often the most cost effective team.
- Screen for the domain first and the tools second when healthcare knowledge is a must have.
A common question on healthcare requisitions
We get this question often from hospitals, payers, health tech companies and the vendors who serve them. Does this role need someone with healthcare experience, or will a strong general IT person do? It sounds like a small question. But the answer changes the candidate pool, the rate and how fast you can fill the role.
The honest answer depends on how much of the work is about the domain. Some roles cannot succeed without healthcare knowledge. Others gain very little from it. And it is not only about business analysts. The same thinking applies to project managers, interface engineers, developers, testers, EHR specialists and revenue cycle staff.
What all good IT professionals bring
Whatever the industry, the core craft travels well. A good analyst runs discovery with stakeholders who disagree and writes requirements developers can build from. A good project manager keeps scope, risk and people under control. A good engineer designs, builds and tests carefully. Tools like Jira, Confluence, SQL, cloud platforms and most programming languages work the same way in a hospital as in a retailer.
So a strong general IT professional is never a bad hire. The question is whether the project needs something extra.
Where healthcare is different
Data standards
Healthcare data moves in formats with strict rules. HL7 v2 messages carry admissions, orders and results between systems. FHIR resources are used for newer APIs and interoperability. X12 transactions such as the 837 claim and the 835 remittance carry billing and payment between providers and payers. Someone who already knows these can read a failed message or a rejected claim and know where to look.
Revenue cycle logic
Eligibility, prior authorization, charge capture, coding, claim submission, adjudication, denials and payment posting all follow payer rules, and those rules change often. A consultant who understands the revenue cycle sees why a small change in a claim field can mean thousands of denials.
HIPAA and regulation
HIPAA privacy and security rules shape how patient data is stored, shared, logged and tested. Federal interoperability rules also set requirements for payers and providers. People who have worked under these rules design with them from the start instead of fixing it at the end.
Clinical workflow
EHR changes affect how clinicians spend their time with patients. A screen that adds three clicks to a nurse's day is a real problem. Consultants with clinical workflow experience know to validate changes with the people who use them, and they know which questions to ask.
Roles that usually need healthcare depth
- Interface and integration engineers working on HL7, FHIR or X12 feeds.
- EHR analysts and consultants configuring or optimizing clinical systems.
- Revenue cycle analysts and specialists working on claims, denials, coding or payment posting.
- Business analysts and project managers on claims systems, payer interoperability, EHR rollouts or revenue cycle projects.
- Data and reporting people building quality measures, claims analytics or clinical reporting where the meaning of the data matters.
In these roles, learning HL7 or claims adjudication on the job slows the whole team down, and mistakes can reach patients or payments.
When general IT experience is the better and cheaper choice
If the project is an ERP rollout, a CRM implementation, a cloud migration, a reporting platform, a network upgrade or an internal tool, deep healthcare knowledge adds little. This is true even when the company is a hospital or a payer. A general IT professional with the right platform experience will often be faster to find, quicker to start and less expensive.
Also, requiring healthcare experience for every role shrinks the candidate pool a lot. You may wait weeks for a "healthcare" cloud engineer when an excellent cloud engineer was available on day one. Is the healthcare label really helping that requisition?
How to decide for your project
A few questions help make the call:
- Will this person read or design HL7, FHIR or X12 data?
- Will they touch claims, payments or payer rules?
- Will they work directly with clinicians or change clinical workflow?
- Will they handle patient data in ways that need HIPAA judgment beyond standard security practice?
- Is there a domain expert on the team who can support a general IT hire?
If the answer to the first four is mostly no, or the fifth is yes, a strong general IT professional is likely the right choice. If several are yes, screen for healthcare depth.
How we screen: domain first, tools second
When healthcare knowledge is a must have, we interview on the domain first. We ask candidates to walk through how a claim moves from submission to payment, how they troubleshot a failed interface message, or how they validated an EHR change with clinicians. Then we check the tools. We review samples of real work where possible, and ask references about delivery and how the person handled stakeholders.
When the domain is not essential, we focus on platform skills and delivery, as we describe in how to identify the right IT candidate. Either way, we match the person to the project, not only to the title on the requisition.
iCareTechno is a division of iCareBilling LLC, a health tech firm that works in medical billing and revenue cycle every day. That is where our healthcare screening comes from. Learn more about our healthcare IT and revenue cycle staffing.
Frequently asked questions
What does a healthcare IT consultant do?
A healthcare IT consultant works on systems such as EHRs, claims platforms, interfaces and revenue cycle tools, using knowledge of standards like HL7, FHIR and X12 and rules such as HIPAA.
Do all IT roles at a hospital need healthcare experience?
No. Roles that touch clinical data, claims or interfaces usually do, but many platform roles like cloud, ERP or network work well with strong general IT experience.
What is the difference between HL7 and FHIR?
HL7 v2 is an older, widely used message standard for sending clinical events between systems. FHIR is a newer standard built around web APIs and resources, used heavily for interoperability.
Staffing a healthcare IT project?
Tell us the role and how much of the work touches the domain. We will match it to a healthcare specialist or a strong general IT professional.
Israr Kazmi
Israr Kazmi is the founder of iCareTechno, the IT staffing, recruitment and consulting division of iCareBilling LLC in Chicago. He writes about hiring, vendor relationships and careers in IT.
More about the author