Interoperability Starts With People: Healthcare IT Staffing for the Teams Behind Connected Care
Health data is moving faster than ever. In June 2026, HHS and ONC reported that more than one billion health records had been exchanged through TEFCA, up from roughly 10 million less than a year earlier. Yet the people who make that exchange work inside real hospitals are in short supply.
The progress is real: 70% of U.S. hospitals engaged in all four domains of interoperable exchange in 2023, up from 23% in 2014, according to ONC.
But networks, standards, and mandates do not configure themselves. One structural shift that stands out as a clear route to sustainable operations is the emphasis on healthcare interoperability, which offers a workable answer to the many personnel and operational issues that hospitals face.
Broken systems negatively impact hospital efficiency. When businesses run in isolated software environments, administrators spend several hours manually transferring data. This lack of integration directly hinders the growth of the healthcare workforce. Professionals who understand HL7, FHIR, and clinical workflows must build, test, and maintain interfaces, which is why healthcare IT staffing has become one of the most decisive factors in whether an interoperability initiative succeeds or fails.
In this article, we explain where the human bottleneck appears, which roles make up a connected care workforce, and how health systems can source, retain, and scale healthcare interoperability talent in a competitive market.
What is Interoperability in Healthcare?
Fundamentally, interoperability is the capacity of one system to communicate with another. Compared to ordinary data transfer, the healthcare standard is intrinsically higher. The ability to send, receive, find, and integrate electronic health information is what ONC defines as interoperability. Integration, the last element, is what sets them apart. Only when the data is incorporated into the workflow and helps a team complete a task more accurately, successfully, or efficiently will it be useful.
Consider a new patient journey, for instance:
A patient schedules an appointment online.
They finalize consent, official documents, and intake forms.
They are sent reminders and follow-up messages.
The appropriate system must contain their clinical and operational data.
Staff members require a comprehensive understanding of the events that transpired, the deficiencies that exist, and the forthcoming events.
If the expedition takes place on a separate, detached platform, each step is put together by hand by the team. Both patients and staff will perceive the trip as fluid and unified if the tools are interoperable. Because of this, interoperability of healthcare data is not just an IT issue. It is a problem that affects operations, patient experience, and care delivery all at once.
Key Takeaways
The technology, procedures, organizational structures, and standards needed to create a network of systems that permits the safe exchange and access of data by only the right people are referred to as interoperability.
Enabling physicians to access complete, accurate patient records is one goal of healthcare interoperability, which will help them provide more efficient care and lower costs.
Organizational, departmental, and systemic bottlenecks must be removed to achieve interoperability.
Technology-Driven Interoperability in Healthcare
Interoperability in healthcare requires the smooth integration of many data types, such as omics, metabolites, microbiota, EHRs, wearable biosensors, ambient sensors, and environmental data, to enable individualized, effective care. These basic data formats are essential to many healthcare developments, including digital clinical trials, hospital-at-home models, and precision health. The four layers of technology-driven interoperability are necessary for the efficient sharing and use of these various datasets.
Foundational: Foundational interoperability, which offers the technical framework necessary for systems to communicate and share data, ensures secure data sharing.
Structural: Because structural interoperability ensures that the data is formatted correctly for interchange, systems can handle complex data types, such as genomic information or wearable biosensor data.
Semantic: Genomic or environmental data can be correctly interpreted across systems because of semantic interoperability, which ensures that the meaning of the data is maintained during the transfer process.
Organizational: Organizational interoperability enables healthcare providers to collaborate on the use of these data types for coordinated care, thereby improving patient outcomes and enabling innovations such as digital twins and virtual health guidance. This is achieved through the facilitation of governance, policies, and processes.
By fully utilizing the potential of these many data sources and addressing all four layers, healthcare systems can enhance care coordination and outcomes, ultimately promoting value-based care. AI and machine learning, cloud-based solutions, instantaneous data interchange capabilities, and patient-centric technologies can all speed up the aforementioned tasks.
Healthcare Data Standards & Regulations
Over time, a wide range of intricate standards, regulations, and security measures have been put in place to enable the safe and reliable handling and sharing of medical data. To properly grasp the challenges and requirements of interoperability, a thorough grasp of the extent of complexity within this regulatory environment is essential. The following is an overview of some of the most important frameworks that affect the actual exchange of information between healthcare systems.
1. HIPAA
One of the fundamental laws in the United States that oversees the privacy and security of health data is the Health Insurance Portability and Accountability Act. This establishes the foundation for the storage, transmission, and access of protected health information (PHI). Any data exchange must adhere to its privacy and security regulations, regardless of whether it pertains specifically to interoperability.
2. HL7
Health Level Seven (HL7) is a collection of international data standards that establish the manner in which health information is packaged and exchanged. It is employed to organize clinical data, such as lab orders, medication listings, and discharge summaries, in a manner that is comprehensible to a variety of systems. The initial standards of HL7 established the foundation for advanced information sharing.
3. CDA
Clinical Document Architecture (CDA) is employed to format clinical documents, such as discharge or progress notes. It ensures the ability to share and interpret the structure and content of these documents across systems.
4. FHIR
Next-generation standards for healthcare data exchange are known as Fast Healthcare Interoperability Resources (FHIR). By utilizing formats such as JSON and XML and modern web protocols such as RESTful APIs, HL7 FHIR developers simplify the process of developing secure, adaptable applications that integrate with existing systems. Today, FHIR is the foundation of numerous of the most ambitious interoperability initiatives, such as federal mandates and commercial APIs.
5. TEFCA
The Trusted Exchange Framework and Common Agreement is a U.S. initiative that aims to establish a "network of networks." It establishes technical specifications and shared principles that facilitate the secure, nationwide exchange of health data. TEFCA also establishes the foundation for national-scale public-private collaboration by establishing regulations for data access and verification.
Standards and mandates set the rules of the road, but every framework still has to be implemented locally, and that work depends on professionals with real expertise in HL7, FHIR API integration, and TEFCA readiness.
The Human Bottleneck in Healthcare Interoperability
The most significant impediment to healthcare organizations' ability to modernize their IT infrastructure and enhance data-sharing capabilities is not always technology or budget. It pertains to the accessibility of proficient professionals.
Limited staffing flexibility, an overreliance on key technical personnel, and a scarcity of healthcare IT specialists can impede interoperability initiatives. These workforce deficits have an impact on the ability to maintain connected clinical workflows, as well as system integration and data exchange.
Consider where the industry's attention has gone. Standards and mandates have rightly dominated the agenda, and hospitals have made real progress, but ONC's own analysis shows that occasional exchange falls short of routine exchange. In its review of 2023 data, 92% of routinely interoperable hospitals had necessary clinical information from outside providers available at the point of care, compared with only 33% of hospitals that were not routinely interoperable.
Closing that gap is rarely a software purchase. It is a staffing question. Every new connection, whether a TEFCA onboarding project, a FHIR API, or a legacy interface, has to be built, tested, mapped to local clinical workflows, and maintained by professionals who understand both the data and the care setting.
Today, health systems also compete with big tech, payers, and digital health companies for the same specialists, which makes healthcare IT staffing a strategic priority rather than a back-office task.
In other words, interoperability is a technology outcome that depends on workforce input. Organizations that treat staffing as part of the interoperability roadmap, rather than an afterthought, are best placed to turn standards and mandates into everyday connected care for clinicians and patients.
What Skills Do Healthcare Interoperability Teams Need?
Successful interoperability teams rely on hybrid professionals, individuals who are very proficient in integration architecture and data standards while also having a thorough understanding of the real-world workings of physicians. When a technically sound interface interferes with a nursing workflow or causes a prescription order to be delayed, it has only relocated the issue rather than solved it. Three skill areas matter most.
1. Technical Fluency in HL7, FHIR, and API Integration
While more recent programs rely on FHIR and RESTful APIs, many health systems still use HL7 v2 messaging for admissions, orders, and results. As an outcome, teams require HL7 FHIR developers and interface analysts who can secure system connections, work with terminology standards like SNOMED CT, LOINC, and RxNorm, map resources to local data models, and design and test FHIR API integration. Experience with interface engines, EHR vendor toolsets, and production monitoring is just as important as knowledge of the specifications.
2. Clinical Workflow Literacy
Standard knowledge is insufficient on its own. Professionals in interoperability need to know how orders, results, medication reconciliation, and discharge plans truly move through a unit and where friction is caused by an extra click or a missing data field. Many of the best applicants have additional technical depth and come from clinical backgrounds like nursing, pharmacy, laboratory, or radiology, while others are IT specialists with years of experience working in hospitals. Either path produces someone who can translate between clinicians and engineers.
3. Governance, Security, and Compliance Awareness
Every data transmission involves privacy and regulatory requirements. A working understanding of HIPAA, information blocking compliance under the Cures Act, patient consent management, and the exchange goals and operational requirements associated with TEFCA are all necessary for interoperability. Health systems prevent rework and lower compliance risk when this information is part of the project team rather than added at the end.
The Anatomy of a Connected Care Workforce
A connected care workforce is not a single hire, but a team. Health systems must consider how complementary positions fit together because no one person can possess the complete range of clinical, technological, and governance capabilities required by an interoperability program. The core consists of four roles.
1. Clinical Informaticists
Clinical informaticists are the bridge between the bedside and the build. They gather requirements from physicians, nurses, and pharmacists, translate those needs into workflow and data specifications, support clinical decision support design, and help leaders such as the CMIO govern change. Strong clinical informaticists are often clinicians themselves, which gives them credibility with end users and a practical sense of what will and will not work on a busy unit.
2. Integration Engineers and EHR Integration Specialists
Integration engineers build, test, and maintain the interfaces and APIs that move data between systems. EHR integration specialists in this role work across HL7 v2 feeds, FHIR resources, interface engines, and monitoring tools, and they are the first responders when an interface fails or a data feed degrades. Their work determines whether information reaches the right system accurately and on time.
3. EHR Architects and EHR Analysts
EHR architects design how the enterprise record is configured, how modules and data models fit together, and how external data is received into clinical workflows. EHR analysts support the build, testing, optimization, and go-live of those designs, and they are often the people clinicians call when something does not look right. Together, they ensure that exchanged data is usable at the point of care, not just present in the system.
4. Data Governance Analysts
Data governance analysts protect the quality and trustworthiness of what is exchanged. They manage terminology standards, patient matching and master patient index practices, data quality monitoring, access controls, and compliance reporting. Their work reduces duplicate records, inconsistent definitions, and semantic mismatches between systems.
Gaps in any one role can slow the entire program: strong engineers without a clinical informaticist can build interfaces that technically work but do not fit practice. Thoughtful health informatics staffing treats the team as a system.
The Real Cost of Healthcare IT Staffing Shortages
The consequences of insufficient healthcare technology teams go beyond missing project deadlines. There is a possibility that they could disrupt daily operations and affect the quality of care:
Delayed integration projects: The limited availability of HL7 and FHIR specialists can impede the development of APIs, EHR integration, and data exchange initiatives.
Growing technical backlogs: Delays in interface problem resolution, system updates, and interoperability maintenance may result from inadequate integration and support staff availability.
Temporary workarounds: Teams that are overburdened may turn to manual data entry or disconnected systems rather than addressing the root causes of integration issues, which can result in increased administrative workload and data inconsistencies.
These staffing shortages also affect clinical teams. Due to inadequate system connectivity, medical personnel are forced to manually transfer patient data, repeat documentation, and conduct cross-platform searches. Over time, these responsibilities worsen annoyance, lead to fatigue among clinicians, and erode trust in medical technology.
The burden on clinicians is well documented. A peer-reviewed time and motion study found that physicians spent 49.2% of the office day on EHR and desk work, compared with 27.0% on direct clinical face time. The study predates today's interoperability push, but it shows what is at stake when systems do not fit clinical workflows. Adequately staffed informatics and integration teams are among the most practical ways to reduce that friction.
How Flexible Workforce Models Help Health Systems Scale Interoperability
Many interoperability needs are project-shaped. TEFCA onboarding, FHIR API enablement, interface rationalization after a merger, and EHR consolidation all create sharp peaks of specialized demand that permanent headcount alone cannot serve efficiently. Flexible healthcare IT staffing gives health systems a way to add the right expertise for the right duration, without overburdening internal HR bandwidth or leaving core teams stretched.
Contract Experts for Specialized, Time-Bound Work: Contract HL7 FHIR developers, EHR analysts, and integration engineers can be brought in to cover a defined scope such as a go-live, a conversion, or an API build. This approach is already common: the CHIME 2025 CIO Survey lists hiring a contractor for a specific, short-term project among the go-to strategies CIOs use to address staffing challenges, alongside reassigning or reorganizing existing IT staff.
Specialized Project Teams: For larger initiatives, a small pod that combines an integration engineer, a clinical informaticist, and an EHR analyst can take ownership of an entire workstream. Because the team is assembled for a defined outcome, scope, timelines, and handoff expectations are clear from the start, and internal staff can stay focused on ongoing operations.
Protecting Internal HR Bandwidth: Sourcing niche informatics talent is time-intensive. A specialized workforce partner can handle candidate identification, credential verification, and onboarding logistics, which frees internal HR and IT leaders to focus on priorities only they can manage. To keep the benefits after a contract ends, build knowledge transfer into every engagement through documentation requirements and structured handoffs.
Conclusion
Healthcare interoperability talent involves more than exchanging patient data or connecting systems. To ensure information is accessible, accurate, secure, and useful across healthcare settings, organizations need the right personnel, skills, and processes in place. Skilled healthcare IT professionals ensure that these systems function efficiently within clinical and operational workflows, despite the technical foundation provided by standards like HL7 and FHIR, APIs, and EHR integration.
Integration projects can be delayed, administrative workloads can be increased, data silos can be created, and clinician frustration can be exacerbated by staffing shortages. Consequently, healthcare organizations must allocate resources to professionals who possess a comprehensive understanding of both clinical requirements and technological advancements. By establishing the appropriate teams, retaining specialized talent, and employing flexible staffing models, hospitals can effectively manage integration projects without imposing additional workload on their current employees.
Ready to build the team behind your interoperability roadmap? CWS Health is a specialized healthcare workforce partner that understands the intersection of clinical environments and enterprise IT. We source niche healthcare IT and informatics talent, including health informatics staffing experts, EHR analysts, integration engineers, and HL7 FHIR developers, that generalist staffing firms often miss. Connect with CWS Health to discuss your health informatics staffing needs and how the right people can make connected care possible for your organization.
Build the Team Behind Connected Care.
Partner with CWS Health to strengthen your healthcare IT workforce.






-03.png)
.png)
Comments