For forty years, an Irish builders’ merchant kept a considerable part of its knowledge inside a computer system called Accustar. The interface was a green screen. The business logic was considerably more interesting. By 2026, Chadwicks Group was modernizing that system with J2 Interactive, a consultancy better known for connecting healthcare technology. The old machine had something worth saving.
- J2 connects clinical data, enterprise platforms, and the people who need to act.
- Its main specialties are InterSystems technology and healthcare Salesforce implementations.
- Its work ranges from laboratory-data pipelines to pharmacy coordination and staged ERP modernization.
Chadwicks had a familiar problem: an aging interface made new employees harder to train, while the underlying application held decades of accumulated operating knowledge. Starting over would require deciding which of those old rules were expendable. Anyone who has inherited a complicated business knows how innocent that decision sounds.
The answer was AccuPRO, a web-enabled, cloud-hosted evolution of the existing system. In J2’s May 2026 account, the multi-year program was roughly halfway complete, with modules being modernized in stages and the engagement expanding after a successful pilot. Chadwicks won an InterSystems supply-chain Impact Award. This was progress with unfinished work attached - a more useful story than an immaculate launch announcement.
The valuable part is between the boxes
J2’s principal business sits in healthcare, where an organization can possess excellent software and still struggle to get the right information to the right person. A hospital record, a pharmacy platform, a customer relationship management system, and a laboratory feed have different jobs. Their owners may all be competent. Their handoffs can still be miserable.
J2 designs and builds those connections. Its services include technology strategy, application development, health information exchange, workflow optimization, analytics, and managed cloud operations. Its named customers include Northwell Health, Healthix, Manifest MedEx, and Dubai Health Authority. The buyer is usually an organization responsible for delivering or supporting care; the beneficiary may never learn J2’s name.
The company occupies a particular place in that market. InterSystems supplies platforms such as HealthShare and IRIS. Salesforce supplies CRM tools, including Health Cloud. J2 implements, extends, and connects them to other systems and to local operating needs. A platform can offer an impressive menu of capabilities. Someone must still decide what happens when a referral arrives, a patient leaves, or a laboratory result needs translating.
Editorial schematic of the integration problem. A connection earns its keep when it changes someone’s next action.
A prescription with a deadline
Consider the Meds-to-Beds application J2 built with SCL Health. It combined information from a hospital electronic medical record and an outpatient pharmacy platform in Salesforce. When a patient was leaving, the pharmacy received an alert. Prescription handling, bedside delivery, and a pharmacist consultation could be coordinated in one workflow.
The practical problem was medication adherence after discharge. A patient can leave with instructions and still face a series of inconvenient steps before taking the first medicine. The application moved part of that work into the hospital stay. It gave an existing pharmacy service a timely signal and a way to organize the response.
J2’s second SCL example, Care Share, supported follow-up after joint replacement, tracking patient activity and provider workflow for care coordinators. These are revealing uses of CRM. The relationship being managed continues through recovery; a completed appointment is only one event within it.
The lesson a reader can borrow is to name the handoff before choosing the technology. “Improve engagement” can accommodate almost any slide deck. “Tell the pharmacy a patient is leaving, then coordinate the delivery” gives a team something specific to build and observe. The distinction has consequences for scope, staffing, and acceptance testing.
The laboratory speaks several dialects
Moving a result is one task. Making its meaning consistent is another. J2’s managed terminology service handles clinical vocabularies and custom mappings in a hosted environment, helping organizations normalize diagnoses, laboratory codes, and other clinical descriptions across applications.
“Data means nothing. Information means everything.”Healthix senior VP and CIO, quoted in J2’s terminology account
Healthix is a particularly good illustration because a health information exchange must work across institutions. J2’s published customer profile describes interface development, identity management, clinical repositories, and event notifications, with alerts routed into existing clinical systems. The work addresses both recognition and delivery: which patient is this, what happened, and who needs to know?
J2 also supported Manifest MedEx’s implementation of California’s SaPHIRE laboratory reporting infrastructure. Manifest MedEx designed and manages the system; J2 supplied technical expertise for the interoperability framework and standardization pipelines. Giving the roles their proper names matters. Infrastructure of this size is collaborative work.
The system ingests and processes results around the clock, standardizes and deduplicates data, and supports real-time dashboards. J2 received a 2025 DEVIES award for its strategic and technical services on the project. At that scale, a small inconsistency can repeat a great many times.
The company that survived the previous boom
J2 began in 2001. Lou LaRocca and Mickey Yalon had met at JuniorNet during the dot-com boom; as their jobs disappeared, they started a company together. Today LaRocca is president and CEO, and Yalon is co-founder and CTO.
The InterSystems implementation partnership began in 2004. In a later reflection, LaRocca described how early projects with that partner helped the founders settle on healthcare, where the effect on patients and providers gave the work a purpose they valued. The origin story contains an actual reversal: a collapsing employer preceded a business built around systems that other organizations depended upon.
J2 subsequently broadened its Salesforce practice. Its December 2018 acquisition of Saxa Solutions added healthcare and life sciences implementation capacity. That expansion fits the same operational concern: clinical information should remain useful outside the walls of the hospital and after the visit ends.
Independent market research helps locate the company’s specialization. KLAS’s 2020 technical services report characterized J2 as a specialist valued by InterSystems clients, doing systems integration, interface-engine migration, and application work. It also identified proactive executive involvement as a strength customers associated with J2 and several peers.
The business of making other software work
J2 sells organizational expertise: consulting, architecture, implementation, custom development, and support. Managed terminology and hosting add ongoing operational services. A prospective customer is buying help making its chosen platforms function together and continue functioning as needs change.
There are several alternatives. A capable internal team can do the work. Vendor services may cover parts of it. Healthcare technical consultancies such as Galen Healthcare, Prominence, and Pivot Point Consulting serve overlapping needs. Larger Salesforce consultancies offer another route. The useful comparison is project fit: platform depth, clinical workflow knowledge, and capacity to support the resulting system.
J2 also has tools for the engineers doing the maintenance. Ops Workbench covers source control, configuration settings, and mirror synchronization in InterSystems environments. Its Message Analysis Reporting Solution examines incoming message formats for quality issues. These offerings concern the everyday mechanics of operating a system after the exciting presentation is over.
A million-dollar interest in paperwork
In March 2025, J2 announced a partnership with Morph, committing more than $1 million in capital and other resources. That figure describes J2’s investment in the partnership. It is not an implementation price for a hospital.
Morph extracts information from paper and unstructured digital documents and places it in operating systems. The proposed healthcare use focuses on administrative bottlenecks and manual data entry. J2’s announced intention is practical: apply language-model technology to logistical work along a patient’s care journey. The announcement establishes a direction, rather than proving a clinical outcome.
This is consistent with J2’s older specialty. Information can be trapped in an incompatible database, an unfamiliar code, or a document. Each requires a different technique to make it usable. The glamorous new tool inherits a rather old assignment.
Keep the knowledge. Fix the friction.
J2 describes its culture as shared responsibility even when a consultant has a solo assignment. Employees own customer relationships; colleagues provide knowledge and support. The company also describes an annual paid ski trip. A distributed consultancy needs occasions when its people meet without a customer ticket between them.
The approach has conditions. Incremental modernization makes sense when the inherited logic is useful and the platform can support change. An integrated care workflow needs trustworthy data and people who can respond to its signals. A perfectly routed alert accomplishes little if nobody has responsibility for the next step. These are implementation questions a buyer should settle early.
Chadwicks makes the larger point unusually visible. The interface needed improvement. The accumulated knowledge deserved respect. J2’s opportunity lies in judging the difference, then doing the patient work of connecting what an organization already knows to what its people need to do next.