So many overlapping systems

Over the years and decades, various products are created to solve various workflow problems in healthcare, they end up looking and behaving inconsistently as a system.
A design system that offers comprehensive assets and guidelines can unify the scattered experience.
The “products to SaaS” journey requires a modern design system to be completed.

Inventory of entities

The first challenge is to identify how the systems overlap. Do they have object model/database entities that overlap? if yes how do they overlap?
The backend architecture for such a complex entity blend is to have common entities picked up in such a way that they serve every product line (systems coming together)
The common entities show common properties in the main layout but the system specific properties in a section of the frontend which is fed by the separate systems’ backend. This way even if the systems arent fully merged in the backend, the end users get a combied picture presented to them so they can make configurations all in 1 place.

Inventory investigation
baseline guiding principles
Implementation and adoption strategy
Governance and stakeholder management for adoption accross various product lines and the solutions strategy

System level understanding

How do the systems go from global to local configuration, giving the users for large scale systems a better control over the system behaviour
Merging common entities

An example of a common entity Device, which is being merged by combining the various properties brought in by different systems.
Microfrontend structure

An example for defining messages(alerts/events such that it goes from generic properies to deeper ones.