Integration Is Not a Press Release
What has to be true inside your organization before you can honestly say that care is integrated
Announcing an integration of services and actually establishing one are two completely different things; most organizations have carried out the first, but far fewer have achieved the second.
In a study published in September 2026, dental professionals employed in primary care settings across three areas of France were observed; 18 practitioners were included. Rather than asking whether integration was possible, the study sought to find out why it was not working as it should in settings where integration had already been officially declared.
The researchers discovered a lack of resistance. The dentists were prepared to work with the physicians. The physicians recognized that oral health should be taken into account. However, neither the dentists nor the physicians had a proper place within the coordination system. The referral procedures, the shared records system, and the care management software had all been designed with medical issues in mind. In the case of a diabetic patient who needed a dental consultation, there was no set way to make the request, no shared record to follow the patient, and no protocol indicating what action either provider should take next. Dentistry had been included in the system without being integrated into its way of operating.
The integration was mentioned in the press release but was not present in the workflow.
The difference — that is, the distinction between declared integration and operational integration — is the main failure in almost all attempts to expand health systems. Organizations proclaim their commitment to whole-person care, declare their intention to integrate behavioral health and announce that they will screen for social determinants. The statements are genuine, and so is the intention. What does not happen, however, is the necessary structural work that enables the announced services to function as part of the system rather than just in addition to it.
The Question Organizations Are Not Asking
Most integration assessments pose the wrong question; instead, they ask whether we are providing the service. The answer is yes—the service is there, a provider has been engaged, and a room has been allocated. Thus, integration is considered to be complete.
The appropriate question to ask is: does this service have a proper place in how we coordinate? By that, I mean the tools the team uses to hand off patients include this service. It means the records system can relay a concern to this provider and receive a response. It means there is a protocol, known to all relevant parties, outlining what happens when a patient must be transferred from this service to another. It means the new provider can view the clinical context they need without having to request it separately each time.
So long as those conditions are not met, the service remains integrated; only then does it become adjacent. Adjacent services result in a certain kind of patient experience in which the patient is informed that the organization provides everything they need, turns up for the appointment, and then has to work through the gap between what was promised and what the internal system actually delivers. That gap isn't a communications issue; it is a coordination problem that appears as a communication problem when the patient finally encounters it.
The issue isn't whether you provide integrated care; it's whether your organization's operating system has been rebuilt to incorporate it.
What Operational Integration Actually Requires
The findings of the dental study make the requirements specific. In cases where integration had merely taken place, the following four conditions were missing:
The new service should be included in the coordination tools. Whether or not the referral software, the care management platform, and the shared record system were designed before the service came into existence, they all need to have a proper structural place for the integrated service — not a roundabout solution or a fax number, but a built-in route. If the coordination tool was designed before the service existed, it will automatically go around the service.
Handoff protocols must be explicit and mutual; both the sending and receiving providers must know what triggers a handoff, what information is passed on to the patient, what response is expected and when. A protocol that applies to only one side is not a protocol at all, since it will be disregarded whenever the other side is busy.
The new provider does have access to the relevant clinical information. Consider the case of a dentist who is unable to view the patient's medication list, a behavioral health clinician who cannot see the patient's history of chronic diseases, and a social worker who doesn't have access to the patient's most recent visit notes—these providers are effectively working in the dark even though the system has officially incorporated them. They are unable to give integrated care because the information necessary for it is not integrated.
Responsibility for the handoff is given. When there is no clearly identified owner, the handoff goes to the person with the most slack, which is seldom the appropriate individual and is always inconsistent. For integration, someone must be accountable for ensuring that the connection between the services actually takes place — not just in theory, but in the specific case of this patient on this day.
None of these requirements are glamorous, none of them are mentioned in a press release, and all of them decide if the integration works.
The Brand Consequence
Health systems function within what is known as a trust economy. When patients select a primary care home, they are placing a certain kind of trust in the organization—the kind that it knows them, that their information follows them, and that their doctors communicate with one another. This is the unwritten commitment that underlies integrated care and is the promise most clearly presented in the marketing of health systems.
If the promise does not work in practice—if the dental referral vanishes, if the behavioral health clinician does not receive the medical record, if the patient has to go over their history with four providers who, in theory, were meant to be coordinating—then the damage to the brand is not something that matches the extent of the failure; it is instead proportional to the size of the promise. A company that has promoted whole-person care but has, in fact, provided fragmented care has not merely had an operational failure; it has proved to the patient that its marketing was aspirational and that the experience is different.
That is why operational integration is a brand decision rather than merely an operational one. As soon as an organization includes the phrase "integrated care" in its communications, it establishes a standard that the operations team must meet. In this case, marketing and operations are not following separate paths. It is marketing that sets the expectation, and operations is either able to confirm it or causes it to fail.
When an organization includes integrated care in its messaging, it establishes a standard that the operations team has to meet; marketin creates that expectation, and operations will either confirm it or wipe it out.
The Audit No One Is Running
Integration has been carried out in most health systems, but very few have checked whether the integration they announced is, in fact, the one patients are experiencing.
The audit is structured in that, for every service which the organization has declared to be integrated, three questions should be asked:
Can a provider working in service A perform a handoff to service B using the existing coordination tools without needing a workaround?
Does the provider receiving the patient in service B have the clinical context they need before the patient arrives?
Is there a specific person accountable for ensuring this kind of handoff occurs reliably?
In the majority of organizations, the truthful response to at least one of those questions, concerning at least one of the declared integrated services, is no; that is not merely a small operational shortfall but is in fact the source of brand liability, being the point at which the patient senses the gap between what was promised and what was actually built.
It isn't our job to publicly declare that the integration has taken place; instead, we have to bridge the gap by rebuilding the coordination tool to incorporate the service, drafting the handoff protocol, and assigning responsibility. This kind of work is dull, costly, and invisible to anyone unless they are actually doing it. It is also the only thing that actually makes the integration work.
What This Means for How Organizations Communicate
This means that organizations should not cease marketing integrated care; rather, marketing and operations must be carried out in the correct sequence, with the announcement coming after the build.
It sounds easier than it actually is. There is real pressure on organizations to publicize new services, attract patients to new programs, and demonstrate to funders and community partners the strategic direction they are taking. The pressure from all these areas tends to lead to early announcements. The issue is that making an early announcement sets up an expectation that the system isn't yet capable of meeting, and the patients who come in during that period—the time between the announcement and when the system is ready to operate—will experience the failure themselves and will carry that negative experience over into all their future interactions with the brand.
The correct approach is to regard operational integration as a prerequisite for marketing integration. The issuance of the press release is not the key event; the completion of the rebuilt coordination tool is; the completion of the handoff protocol is; and the assignment of accountability is. Only when these conditions have been fulfilled can the announcement be considered anything other than aspirational; it then becomes a description of something that is already in operation.
It isn't about what you provide; it's about what the patient experiences as they move from one of your offerings to another. That experience is developed within the workflow, not in a brochure.
Some ideas are worth discussing in the context of your organization.
