Reporting Dropped from Three-to-Six Months to Hours

NYBC had grown by absorbing other blood centers. Each one came with its own systems, its own reporting methodologies, and its own definitions of what data meant. None of them talked to each other.

Critical workflows ran in Excel. Staff emailed files back and forth, manually entering data, risking version mismatches and quiet data loss. Generating some reports took three to six months — stakeholders logged into multiple systems, exported data, imported it somewhere else, then analyzed it by hand.

The obvious fix — buy a single industry-regulated system and implement it top-down — was off the table. Cost, time, and compliance made it unrealistic. They needed a different path.

Rather than replace everything at once, we proposed an Integrated Portal Development approach: build a standard portal, then deliver business-function modules one at a time. The portal would give NYBC a single login, a shared identity model, and a consistent experience. The modular release path meant we could ship value incrementally without disrupting operations.

NYBC agreed. The engagement ran across multiple releases — the portal foundation and identity first, then function-specific modules delivered on their own cadences. Because modules were independent, different teams inside NYBC could maintain them in parallel with minimal coordination.

The portal foundation. A single web portal with a standardized user experience across every business function — accounting, HR, legal, operations. One sign-on. One identity model. Role-based access that determined what each user could see.

Standardized identity and security. Every user had one login. Role dictated data access, with the flexibility to grant additional permissions through portal administration when the data access rules needed to flex. Forgotten-password flows and other identity chores were handled consistently instead of per-system.

Automated workflows between modules. Data flowed from one module to the next without export-import detours. Critical steps — approvals, rejections, hand-offs — became visible and auditable, not buried in someone’s email.

Integrated analytics. We built widgets that plugged the portal into Microsoft PowerBI, so dashboards and interactive analytics showed up inside the portal. Users didn’t need to learn PowerBI or have their own license. Analytics moved from “a few power users” to “everyone who needs it.”

The data dictionary. The disparate data definitions from each merged organization had to reconcile somewhere. We built a data dictionary module and handed it to NYBC’s data governance team to manage. That gave them a living, authoritative source of truth for what the data meant, organization-wide.

Reporting went from months to hours. The reports that used to take three to six months — log into five systems, export, reconcile, analyze — now come together in a few hours. Streamlined data access and permission-driven automated workflows replaced most of the manual steps.

One corporate identity across functions. Users sign in once. IT has a single source of authoritative access data. Adding a new employee to the portal is a routine operation; revoking access when someone leaves is a routine operation. Standard identity flows — forgotten passwords, role changes — work consistently.

Lower training cost, higher internal mobility. The consistent UX means a user who moves between roles at NYBC already knows how to use the portal. Training time dropped. Internal mobility got easier.

Analytics accessible to everyone. Dashboards and analytics moved from “a licensed few” to “anyone with a role that needs them.” PowerBI power was exposed through standard widgets, not direct tool access, so the learning curve came down and the licensing cost went down with it.

Auditable by design. Every process runs through the portal with a permission-driven audit trail. Risk goes down because what happened is recoverable — not reconstructed from emails and spreadsheets.

The portal is now a core part of how NYBC runs. Modular and flexible, it’s absorbed new use cases and future acquisitions as they’ve come up — without the disruption or cost that a top-down system replacement would have carried.