Ending the MedTech Spreadsheet Era: Cognition Launches Compass MED 3.0

LEXINGTON, Mass. – November 09, 2026 — For years, medical device manufacturers have operated on a volatile fault line. On one side, software and systems engineers push for agile velocity, living in dynamic tools like Jira and Azure DevOps to iterate quickly. On the other side, quality assurance and regulatory teams enforce rigid, sequential documentation to satisfy complex FDA and ISO 13485 mandates. The resulting friction often manifests in chaotic spreadsheets, disconnected Design and Development Files (DDF), delayed time-to-market, and a persistent dread of regulatory audits.

Today, Cognition Corporation, a Lexington-based SaaS provider for life sciences, released Compass MED 3.0, a major upgrade to its design control and risk management platform. The release targets this exact operational chasm, introducing automated impact assessments, bi-directional engineering integrations, and tag-based variant management. By synchronizing engineering workstreams directly with quality assurance requirements, the platform aims to make the static, spreadsheet-based compliance model obsolete.

"With Compass MED 3.0, teams no longer have to choose between engineering speed and rigorous design control documentation; they can do both concurrently," noted Ben Higgitt, Compass MED Product Manager at Cognition.

Bridging the Agile-Compliance Divide

The medical device industry is undergoing a massive digital transformation, but it has repeatedly stumbled over toolchain silos. Developers understandably resist leaving their preferred Application Lifecycle Management (ALM) environments, while quality teams require structured, gated systems to prove compliance. When these systems don't talk, organizations are forced into double-data entry, a practice that introduces human error and compliance vulnerabilities.

Compass MED 3.0 addresses this through bi-directional connectors to Jira and Azure DevOps. These integrations push and pull critical data—including requirements, test cases, protocols, and defects—on a schedule, on an event, or on demand. Crucially, every synchronization event is logged within an immutable audit trail, ensuring that software teams keep their agile tools and quality teams keep their defensible evidence.

Industry consultants point out that the real-world failure mode of such integrations usually lies in conflict resolution and data mapping. In a traditional setup, when a developer alters a requirement in Jira, the quality team’s traceability matrix can silently break. Cognition’s system counters this by actively flagging "suspect links" upstream and downstream whenever a controlled item is modified. Instead of a dangerous "last write wins" scenario, the platform forces a visible reconciliation, bridging the gap between moving fast and staying compliant.

The Death of Static Audits

The era of managing medical device design controls in disconnected documents is rapidly closing. Regulatory bodies, armed with stricter frameworks like the EU Medical Device Regulation (MDR) and updated FDA guidances on software as a medical device (SaMD), are scrutinizing the integrity of digital records more closely than ever before.

To meet stringent standards like FDA 21 CFR Part 11, electronic records must be trustworthy, reliable, and entirely equivalent to paper records. Compass MED 3.0 enforces this through mandatory approval gates. When the system's automated impact assessment triggers a suspect link, an approval gate holds the unresolved impact until it is assessed and closed with an electronic signature. Tracked action items take each issue through to closure, ensuring nothing falls through the cracks.

"During our evaluation of Compass MED, what impressed me was how well the software supports best practices for risk management, human factors, and design controls," said Aaron Joseph, Principal Consultant at Sunstone Pilot, in the company's release. "It's clear that Cognition has really invested in making the software fit the needs of medical device companies."

This automated tracking replaces the manual, error-prone process of cross-referencing hundreds of requirements across a complex system. Side-by-side diffs and in-context suspect indicators show teams exactly what changed. Furthermore, the enhanced test management functionality allows verification and validation teams to define test plans, capture deviations during execution, and approve execution records with 21 CFR Part 11 compliant electronic signatures. The resulting immutable audit trail provides the transparency required during an FDA inspection, ensuring that every decision is logged, time-stamped, and highly defensible.

Managing Complexity Without Losing Traceability

As medical device companies scale, they rarely build entirely new products from scratch. Instead, they develop platform technologies that spawn numerous regional or hardware variants. A base device might need slight software modifications to meet European data privacy laws, or a hardware tweak to accommodate different power grids in Asia. Managing these complex System and Subsystem development programs often leads to a collapse in traceability.

Historically, copying and pasting an entire project to create a new variant severs the historical link to the original design inputs, creating a nightmare for global regulatory strategists. Compass MED 3.0 introduces tag-based project variants to solve this scaling problem. Rather than cloning a massive project file, teams can select specific content using tags to quickly stand up a new variant.

The reused data maintains its traceability back to the source. As the source or the new project evolves, teams can manually sync one or more changes in either direction. This feature directly challenges competitors in the ALM and Quality Management System (QMS) space by offering a highly nuanced approach to branching. It allows product operations leaders to manage geographical iterations without sacrificing the core control required by ISO 13485, accelerating global rollouts without compounding regulatory risk.

The Migration Hurdle

Despite the clear advantages of unified, automated SaaS platforms, the transition for established manufacturers is rarely seamless. The ease and fidelity of migrating legacy Design and Development File data remain the most significant barriers to adoption across the MedTech sector.

Extracting discrete requirements, risks, and test cases from unstructured legacy documents—like Word files, massive Excel matrices, or PDFs—and structuring them into a relational database requires substantial operational effort. Recreating traceability links that were previously managed implicitly is a daunting task that carries its own compliance risks. If a migration is poorly executed, traceability gaps can emerge, making subsequent audits incredibly difficult.

Cognition acknowledges this hurdle, noting that legacy test data from prior software versions carries forward into the new enhanced test and defect management module. However, for organizations moving away from paper-based or rudimentary digital systems, the validation burden will be heavy. They must definitively prove that the newly digitized records accurately reflect their original approved documentation, a process that demands rigorous Installation, Operational, and Performance Qualification (IQ/OQ/PQ) protocols.

As the MedTech sector continues to modernize, the companies that succeed will be those that can successfully migrate their historical data while embracing the automated, integrated workflows required to survive the next generation of regulatory scrutiny. The release of Compass MED 3.0 suggests that the software tools to achieve this balance are finally maturing, shifting the ultimate burden of compliance from software limitations to true organizational readiness.