Before healthcare technology became a parade of ambient scribes, predictive models and agents, Michelle Blackmer was in the room with radiology information systems. The screens were less polished. The category names were less fashionable. The problem underneath was already perfectly modern: one system had something another system needed, and the handoff was unreliable.
Blackmer began her career implementing those radiology systems, then moved to early electronic medical records, including the Centricity products assembled by GE through acquisition. In theory, the portfolio was becoming more complete. In practice, customers could not always share information even among applications owned by the same company. A suite of software had arrived before a shared language.
That frustration gave her a subject sturdy enough for an entire career. She moved from implementation into product and marketing roles, following healthcare data through Initiate Systems, IBM, Informatica, CareEvolution, Verato and finally Rhapsody. Job titles changed. Corporate names changed. The stubborn little drama remained: identify the person, move the information, preserve its meaning and make it useful at the other end.
“And that's how I became really passionate about interoperability.”Michelle Blackmer, recalling the moment disconnected systems became her career's central problem
A career built at the handoff
There is something fitting about an interoperability executive working at the intersection of marketing, sales, product and customers. Those functions are notorious for speaking compatible dialects while misunderstanding one another anyway. Blackmer's formal brief at Rhapsody is to define go-to-market strategy and lead marketing. Her practical role is broader: carry the customer's problem across organizational borders without dropping it.
Her public leadership biography emphasizes a natural instinct for convening and building trust. Former colleagues use more operational language. They point to clear direction, high standards, carefully framed questions and an unusual combination of strategic range and execution discipline. The portrait is not of a promoter standing outside the machinery. It is of a translator who has spent enough time near the machinery to know which details cannot be edited out.
At Initiate Systems and later IBM, the issue was master data and identity. At Informatica, her leadership work ranged from healthcare product marketing to global customer advocacy. CareEvolution put her close to consumer-directed exchange and population health. Verato brought the focus back to matching people across multiplying data sources, this time through a cloud service.
When Verato announced her arrival as vice president of marketing in 2019, Blackmer spoke about inaccurate and growing data sources as a direct obstacle to value-based initiatives. She saw cloud-based referential matching approaching an inflection point. Her remit included product and partner marketing, demand generation, communications and the full go-to-market plan. It was the familiar problem at a new altitude.
One person, one record, one very large consequence
Patient matching is easy to dismiss as database housekeeping until the abstraction becomes a person. A misspelled name, an old address or a duplicate registration can split one life across records. Meanwhile, common names and incomplete details can pull separate people uncomfortably close together. The arithmetic is dull. The consequence is not.
Blackmer's route from identity into broader interoperability follows that logic. It is not enough to move a message if the receiving system cannot confidently attach it to the right person. It is not enough to match the person if the clinical terms lose meaning in transit. It is not enough to normalize the content if it arrives too late for the workflow that needs it.
This is why her language tends to climb from transport to context. In a 2022 conversation at ViVE, she described the industry's evolution in plain steps. First came the demand to get the data. Then came harder questions: How should it be normalized? Where does it live? Who has it? What does the metadata say about the data itself?
“Now it's not just ‘let's get the data.’ It's, ‘how do we normalize the data?’”Michelle Blackmer on the industry's move from access to usable context
The line is useful because it refuses an easy finish. Connectivity is not a ribbon-cutting event. Once the pipe opens, the questions multiply. A technically successful exchange can still produce an operational mess. The person who markets this work must explain progress without pretending the work is complete.
The AI era discovers the basement
Generative AI has given healthcare a fresh reason to inspect its foundations. Agents can summarize, route and recommend, but they need reliable, real-time and governed feeds from systems that were not designed around an agent's appetite. An API may open a door. It does not guarantee that what comes through is timely, clean, correctly identified or safe to use.
Blackmer and her team have described the requirement as agent-ready interoperability. The phrase performs a neat trick. It attaches a new ambition to old disciplines without pretending the disciplines have suddenly become new. Integration, identity, terminology and governance are still doing the basement work. AI merely invites more guests upstairs.
When a market becomes enchanted by a new interface, look for the neglected dependency beneath it. The durable opportunity often belongs to the team that can make the foundation reliable and explain why it matters.
This framing also reveals Blackmer's instinct as a marketer. She does not begin with an acronym. She begins with the constraint. Engineers spending nights and weekends reconciling records have less time for innovation. A public-health team waiting on brittle connections has less room to respond. A technology company that must build every integration itself reaches the market more slowly. The infrastructure story becomes legible when told through the work it releases.
Her 2024 reflections after ViVE sounded hopeful rather than triumphant. She had talked with attendees about Corepoint for analysts, Rhapsody for developers, the data they needed and what FHIR could become. She left excited by how far interoperability had come. Optimism, in her telling, was not evidence that the problem had disappeared. It was evidence that more people could now see it clearly.
Marketing the thing nobody sees
Infrastructure has an awkward publicity problem: its finest hour looks like an ordinary Tuesday. No one sends a congratulatory note because an interface delivered every message, an identity service avoided a duplicate or a terminology layer kept a code intelligible. Success removes the drama that might have advertised it. Failure, by contrast, is an excellent publicist. It arrives with a queue, an alert and several people asking who owns the problem.
Blackmer's career gives her a way through that asymmetry. She can connect the invisible mechanism to visible time. A dependable integration lets an engineering team stop tending custom feeds and return to its product. Better matching reduces manual review. Reusable connections shorten customer onboarding. The story is not that infrastructure deserves admiration for being complicated. The story is that other people recover hours, options and attention when it works.
That distinction matters in enterprise marketing, where technical fluency can become a thicket and simplification can drift into vapor. Blackmer's recurring territory is the middle path: make the business consequence concrete while leaving the engineering reality intact. The task resembles data normalization in miniature. Different audiences arrive with different vocabularies. The meaning has to survive translation.
Making room, making meaning
Blackmer's public writing offers one more clue about how she thinks leadership should work. Reflecting on women in leadership, she praised empathy, collaboration, perspective and strength, and argued that leadership means making room for others to thrive. The sentiment matches the professional descriptions around her: convening, listening and using questions to help people solve problems rather than simply handing down answers.
There is no need to romanticize the committee meeting. Collaboration can become a pleasant word for delayed decisions. Blackmer's colleagues pair it with standards, focus and operational discipline. Trust, in this version, is not endless agreement. It is the confidence that the person guiding the room understands the machinery, has heard the customer and will still choose a direction.
In June 2026, Becker's Hospital Review named her among 170 women in health IT to know. The recognition cited her global go-to-market leadership, her work translating interoperability and AI for technical and executive audiences, and her role in Rhapsody's agent-ready positioning. It also reached backward through the résumé, noting work around identity management and an early Watson-based predictive analytics solution.
Awards compress a career into a paragraph. Blackmer's is better understood as a sequence of handoffs. Radiology to electronic records. Implementation to product. Identity to integration. Customer voice to company strategy. Established standards to AI agents. Each move widened the frame without abandoning the original irritation: systems that ought to understand one another often do not.
The glamorous version of healthcare technology arrives as a revelation. Blackmer's version arrives as a connection that holds. It is quieter, more testable and usually more useful. Somewhere, a message reaches the right system, attaches to the right person, retains its meaning and appears in time. Nothing sparkles. The work proceeds. In infrastructure, that is close to a standing ovation.