When two companies merge — particularly two that were once competitors — it can be tricky for employees to get to know each other. And in the midst of a pandemic? With travel restrictions? It’s more difficult than ever.
Despite the challenges, two Lyniate employees — Alex Lin and James Hardacre — have managed to forge a friendship thanks to the magic of modern technology.
Alex is Team Lead, Professional Services in Professional Services, North America, and has a long Corepoint history. James is Senior Implementation Consultant in Professional Services. He’s based out of the United Kingdom and an equally extensive tenure with Rhapsody.
We asked Alex and James to sit down for a conference call to learn more about their backgrounds, understand how their roles on Corepoint and Rhapsody are similar (and different), and tackle some industry challenges — such as engine migrations and their gnarliest, most complex integration projects.
Longtime Corepointer, Jeff Zinger, moderates the discussion.
Watch the Full Recording (Approx. 1 hour)
James went from writing software for the gaming industry to working on Rhapsody at a U.K. hospital. Alex started out in the financial industry, but after the tech bubble burst, he landed a job with NeoTool, the predecessor to Corepoint.
James and Alex talk about the difficulties of EHR migrations, and how customers can set themselves up for success before such a major undertaking.
Favorite tools: For James, it’s the fact that Rhapsody is intuitive and easy to use, yet more than capable of doing complex interface work. For Alex, “It’s the significant amount of testing before we turn the [Corepoint] engine and the interfaces on.”
Most difficult projects? James discusses an engine migration, and Alex recalls the time he was sent directly from a friend’s wedding to a customer site in Seattle for a major undertaking.
James highlights some projects that directly benefit patients. “It's adding value to systems that people wouldn't think about,” he said. Alex said, “I really appreciate when we do things that help the providers and the patients. But James and I, we get to know the engine team... It's great to see that the engine and the work that we do improves and enhances their lives sometimes.”
From James: “The first time I really used Rhapsody was back in 2.2 and 2.3, and it was good, but there were issues with it.” From Alex: “There was a significant leap from [Corepoint] 5.0 and beyond 5.0 specifically. At that point, we had SQL server in the backend and our performance probably went up through the roof compared to what it was before.”
Alex and James explain the needs of different market segments, including hospitals, radiology labs, clinics, and vendors, and how Corepoint and Rhapsody are used in these environments.
James and Alex discuss a native, cloud-based offering that would combine the best of Corepoint and Rhapsody.
While a handful of customers are using FHIR in production, many customers aren’t sure how to start using it.
“Mergers or acquisitions are always a little bit interesting because some people will have to figure out, ‘Am I being merged or am I being acquired?’” Alex said.
James discusses a different type of FHIR. We mean fire. He demonstrates how uses the Rhapsody engine to literally fire up his smoker and track the progress of his “low and slow” BBQ.