Aligned Elements is a Medical Device application lifecycle management (ALM) solution enabling fast development and regulatory compliance through improved Design History File management.

February 19 2015

Having questions on how to apply and implement IEC 62304 in your company?

Join us as Robert Ginsberg, one of the co-authors of "IEC 62304 Medical Device Software - Software Life Cycle Processes" reveals the initial intent, best practices and lessons learned of this software standard.

In this half-day seminar we will address the practical challenges of implementing IEC 62304 in medical device software development.

Key Learning Objectives:

  • IEC 62304: best practices and lessons learned
  • IEC 82304: how will it fit in next to other standards
  • IEC 62304 Amendment 1: key changes and their consequences
  • Software risk management, architecture and software safety classification: bringing it together

Take the opportunity to confront a co-author of IEC 62304 with your own thoughts and questions.

A 30% earlybird discount applies to all registrations made before March 1st!

When: Tuesday March 31st, 08:30 - 13:00

Where: Hotel Marriott Courtyard Oerlikon, Zurich (directions)

Price: 250 CHF  (Note! 30% earlybird discount for registrations before March 1st)

Register here!

Hosted by: Qadvis / Aligned AG

Presented by: Robert Ginsberg CEO, Qadvis, co-author of IEC 62304 and Anders Emmerich, CEO, Aligned AG

February 03 2015

To accelerate your development documentation process, Aligned Elements supplies a number of free downloadable extensions.

These include:

  • regulatory wizards, generating requirements, risks and other Design Control Items based on how you apply a given regulation
  • example content, such as requirements, potential hazards, risks and other Design Control Items
  • regulatory checklists for verifying your content towards medical device norms and regulations
  • import tools, template packs, unit testing integrators, xml transformations and much more.

The extensions can be used in your existing projects to speed up the documentation work, to serve as inspiration or to be used as enhanced control mechanisms.

 accelerate:Courtesy of Malene Thyssen/Wikimedia

Is your device qualified for eIFU (EU No 207/2012)?

For those considering using electronic instructions for use (eIFU) according to EU 207/2012, take a closer look at the "Electronic Instructions For Use Checklist (EU 207/2012)" that helps you finding out weather your device and its intended use makes is it qualified for the regulation.

The QA-based checklist provides objective evidence, once completed, that you have made a careful and detailed analysis of your device according to EU 207/2012.

The advantages of eIFUs are many and compelling, including:

  • Reduced costs for printing and distribution
  • Possibility to include rich media content
  • Faster distribution of critical updates
  • Reduced burden on the environment

Use this checklist to confirm that the regulation applies to your device.

If the checklist establishes that EU 207/2012 applies to your device, proceed and download the 38 predefined eIFU Requirements extracted from the EU 207/2012 and import them into your project.

Accelerating the development documentation work could not be easier!

January 30 2015

As an example of Aligned Elements project consistency control, the Aligned Elements Pre-Submission checklist demonstrates how various aspects of the project content can be analyzed in order to avoid failed audits and unwelcome FDA 483 warning letters.

Both EN/ISO 13485 and EN/ISO 14971 are concerned with the completeness and consistency of the project content and this checklists serves as an instrument to make that effort easier and faster.  

The checklist guides the user through a number of analysis action steps and optionally records the results in a checklist report, which serves as objective evidence of the analysis. Detailed instructions and screenshots accompanies the steps to facilitate the execution.

The checklist has been designed to check a project that uses the Aligned Elements default templates.

The checklist verifies test points such as:

  • Have all the Requirements traces to Specifications?
  • Have all Specifications been tested?
  • Are all Tests passed?
  • Have all Risks been mitigated?
  • Have all Mitigations been either tested or traced to a Specification?
  • Have all Document Objects been placed in Word files?
  • Do any Word files contain outdated Document Objects?

The check list further performs optional checks, if you have selected to use features such as:

  • The integrated Issue Management System
  • The integrated Design reviews
  • The integrated Risk Summary
  • The integrated DHF Index

 The Checklist, which is implemented as a Regulatory Wizard, is available for Aligned Elements users on the Extensions page in the Wizard section. 

January 29 2015

"If it is not documented, then it has not been done", according to the FDA saying. "Documentation not available", or "Documentation not adequate" are most frequently cited deviations in FDA Warning Letters. The effects of inconsistent documentation can be devastating, implying postponed market launches, product withdrawals and fines.

The reason for this flood of FDA 483 warning letters, addressing seemingly obvious and simple errors, is not that the medical device manufacturers are ignorant or incompetent.

It is simply hard to keep the DHF documentation consistent. 

The documentation requirements are many and detailed, the development projects often spans over a long time-period, involves a large number of alternating team members, all contributing to the large set of deliverables that make up the Design History File / Technical File. The deliverables are highly interdependent and a small change can cause unexpected ripple-effects over large parts of the documentation.   A considerable amount of the total project effort is thus placed in the handling and management of the DHF.

Not long ago, I was contacted by a customer. He had recently taken over a project with the objective to take the product to market. After a brief introduction, he found the project to be in a miserable state. The project had switched project manager four times during the last four years, the team members were all new, knowledge about the documentation process was lacking.

 In short, the situation was very opaque. 

The project manager wanted help with assessing the current state of the development documentation and within 10 minutes, we could extract the following information from Aligned Elements:  

  • About 20 Requirements lacked traces to Specifications. They were all software related and entered by the same person during a short time-span about two years ago.
  • All Specifications had adequate Test Cases assigned.
  • About 10 Test Cases had never been executed. None of these were functional Test Cases and they had all been entered after the last milestone.
  • About 10 Test Cases had the current state "Failed". Most of them had to do with reliability, maintenance, spare-parts and life-time tests.
  • About 15 Risks were insufficiently mitigated.
  • About 10 Mitigations were not verified or implemented.
  • All Word documents were up to date.

The project manager finally felt that he had some grip of the situation. He now had concrete errors to fix and also the names of the people to contact to get detailed information about each individual inconsistency. 

Design History File - DHF

Aligned Elements addresses the issue of incompleteness with a range of integrated and automatic consistency and control functions. Aligned Elements is able to:

  • In real-time, highlight any gaps and inconsistencies on any content set in the project.
  • Provide reports that present a clear overview of the current consistency state of the project.
  • Guide the user through a predefined process path to make sure errors are not created in the first place.

Coverage 

By the application of configurable validation rules, real-time checks can be executed on the documentation continuously. Faults and gaps are uncovered well in time before the auditor arrives or before the documentation is submitted to the notified body. 

Knowing the state of the development documentation is invaluable for a medical device manufacturer. The list of open errors, representing the project’s “Documentation Quality Debt”, is an excellent estimator for how much work remains until the documentation is ready for release.

Reducing project risk by making the current documentation state transparent is an excellent way to increase the chances of a successful product launch. 

Learn how Aligned Elements can help to organize your Design History File

Schedule a live demo and let us show you how Aligned Elements keeps your DHF complete and consistent

January 23 2015

With the Hotfix Aligned Elements V2.3 Service Pack 1 (2.3.2.10145) we have fixed a small number of crucial bugs fixing some serious inconviniences in Aligned Elements V2.3.

Note that these issues in Aligned Element do not pose any danger to the data integrity of the projects. It is only a matter of fixing GUI problems that degrades the usability.

googleplus facebook