Migration and integration asked different questions of the same technical practice.

For a healthcare SaaS and medical-records client, Howard Pearlmutter served two separate divisions.

One needed strategy and tactics for migrating a multimillion-line legacy codebase toward a future target-platform architecture. Another needed integration strategy, architecture, and hands-on prototypes around standards, gateways, hospitals, and partners.

The work crossed accumulated software capability and the relationships among several systems and organizations.

Migration: carry value into a new technical form.

A large codebase can contain operating knowledge whose importance is easier to recognize through behavior than a platform inventory.

The migration question includes which capability should survive, what the future architecture requires, and how the organization can move without losing useful understanding.

Howard's work in this territory connects technical assessment with architectural direction. His Goldmine & Greenfield model provides a way to examine both the accumulated asset and the room for new work.

See legacy migration.

Integration: make several participants work together.

Standards and gateways supply important structures. The practical system also needs clear responsibility, meaningful information exchange, and behavior that fits the work around it.

Hands-on prototypes can examine a consequential boundary before the organization treats the architecture as settled. They can reveal what the selected mechanism supports and what remains open.

Howard's wider healthcare work also included web applications, reporting, and configurable portal and dashboard capabilities. In separate team work, the Direct and Connect protocols of the US Nationwide Health Information Network were implemented and harmonized.

These examples show several levels at which architecture has to become practical.

The interface participates in the information system.

A dashboard can expose useful relationships or make them harder to inspect. A summary can serve one purpose while omitting context necessary for another.

The design needs to connect the underlying model with the person using it. That is a human-interface question and an architectural question together.

Howard's background includes graphics, simulation, enterprise development, and human interaction with complex systems. The representation can be examined alongside the mechanisms supplying it.

Examine the crossing that matters now.

Your organization may face a different sector and a similar pattern: valuable old systems, new platform goals, external participants, and information whose interpretation changes at the boundary.

The useful first contribution might be an architecture assessment, qualification exercise, or prototype. Technical transfer can help the team carry a new model into practice.

Begin with the behavior or information relationship that has to remain meaningful through the change. That gives the architecture a concrete responsibility to examine.