Postgraduate DiplomaElectromobility, Batteries & Hydrogen Applications open

Postgraduate Diploma in IEC 62304: Medical Software Lifecycle

800-hour online Postgraduate Diploma in IEC 62304: Medical Software Lifecycle. 8 modules covering IEC 62304 (software lifecycle processes for medical devices), ISO 14971 and Jira. Assigned tutor and open enrolment.

Duration800 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

Take the controls.

Run a real engineering trade-off from this programme. Move the sliders, watch the model react in real time and beat the challenge.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Determine when software is a medical device and its class.

02

Plan development according to the safety class of IEC 62304.

03

Specify traceable software requirements and architecture.

04

Implement detailed design with secure coding practices.

05

Integrate, test and release software with documented evidence.

06

Manage software risks, including cybersecurity risks.

07

Maintain software and manage its configuration and problems.

Profile

Who it's for

  • Medical device software engineer who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • Software quality manager who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • Verification and validation engineer who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • Medical software architect who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • Software regulatory specialist who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • DevOps engineer in regulated environments who wants to specialise in IEC 62304: Medical Software Lifecycle.
  • Engineering or science graduates looking to enter medical device manufacturers.
Standards & tools

What you'll work with

  • IEC 62304 (software lifecycle processes for medical devices)
  • ISO 14971
  • IEC 82304-1 (health software, standalone)
  • IEC 81001-5-1 (cybersecurity in health software)
  • MDCG 2019-11 (qualification and classification of software)
  • IEC 62366-1
  • FDA guidance Content of Premarket Submissions for Device Software Functions (2023)
Syllabus

8 modules · 800 h

  1. 1.1Software as a medical device (SaMD)
  2. 1.2Software in a medical device
  3. 1.3Rule 11 of the MDR and classification
  4. 1.4MDCG 2019-11 guidance
  5. 1.5IMDRF framework for SaMD
  6. 1.6Relationship between IEC 62304, ISO 13485 and ISO 14971
  7. 1.7Software safety classification A, B and C
  8. 1.8IEC 62304:2015 amendment
  9. 1.9AI software as a medical device
  10. 1.10Case study: classifying a diagnostic app
  1. 2.1Software development plan
  2. 2.2Lifecycle models: waterfall, V-model and iterative
  3. 2.3Agile development in regulated environments: AAMI TIR45
  4. 2.4Standards, methods and tools
  5. 2.5Integration and testing plan
  6. 2.6Configuration management plan
  7. 2.7Problem resolution plan
  8. 2.8Deliverables and documentation
  9. 2.9Risk management in planning
  10. 2.10Practice: development plan for a class B software
  1. 3.1Software requirements analysis
  2. 3.2Functional, safety and usability requirements
  3. 3.3Risk control measures in requirements
  4. 3.4Software architecture and elements
  5. 3.5Segregation of software items
  6. 3.6SOUP: identification and requirements
  7. 3.7Interfaces with hardware and systems
  8. 3.8Architecture verification
  9. 3.9Requirements traceability
  10. 3.10Workshop: architecture design with segregation
  1. 4.1Software units and detailed design
  2. 4.2Unit acceptance criteria
  3. 4.3Coding standards: MISRA and similar
  4. 4.4Static code analysis
  5. 4.5Code reviews
  6. 4.6Unit verification
  7. 4.7Automated unit testing
  8. 4.8Code coverage
  9. 4.9Technical debt management
  10. 4.10Laboratory: unit testing and static analysis in a repository
  1. 5.1Software integration
  2. 5.2Integration testing
  3. 5.3Software system testing
  4. 5.4Regression testing
  5. 5.5Management of known anomalies
  6. 5.6Evaluation of residual anomalies
  7. 5.7Software release and versioning
  8. 5.8Archiving and build reproducibility
  9. 5.9Regulated continuous integration and delivery
  10. 5.10Practice: system verification report
  1. 6.1Analysis of software contribution to hazardous situations
  2. 6.2Causes of software failure
  3. 6.3Risk control measures in software
  4. 6.4Verification of control measures
  5. 6.5Risks associated with SOUP
  6. 6.6Cybersecurity and IEC 81001-5-1
  7. 6.7Change risk management
  8. 6.8Software risk documentation
  9. 6.9Interaction with the risk file
  10. 6.10Case study: risk analysis of a dose calculation module
  1. 7.1Software maintenance plan
  2. 7.2Feedback and surveillance
  3. 7.3Problem and modification analysis
  4. 7.4Configuration management and change control
  5. 7.5SOUP version management
  6. 7.6Security patches
  7. 7.7Legacy software and IEC 62304
  8. 7.8Audits of the software process
  9. 7.9Expectations of notified bodies and the FDA
  10. 7.10Workshop: resolution workflow for a field problem
  1. 8.1Software product definition
  2. 8.2Safety classification
  3. 8.3Development plan
  4. 8.4Requirements and architecture
  5. 8.5Risk analysis
  6. 8.6Verification strategy
  7. 8.7Maintenance plan
  8. 8.8Documentation file
  9. 8.9Report and presentation
  10. 8.10Final review with the tutor
Methodology, software & labs

How you'll learn

Fully 100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. No fixed timetable: students progress at their own pace within the enrolment period, making it possible to combine study with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is Jira, Polarion ALM, Git, SonarQube, in free, academic or evaluation versions. Assessments are studied using real procedures for requirement-to-test traceability reviews, automated unit and integration testing, and static code analysis. Assessment is continuous, module by module, plus the final integrating project.

Accreditable laboratories(EN ISO/IEC 17025) with a rotor test rig, EMC/Lightning pre-compliance, HIL/SIL, vibration/acoustics.
Evidence-driven final project:safety case, test plan, compliance dossier and operating limits.
Industry mentoring:lecturers with experience in training, , eVTOL/UAM and flight test.
Flexible format(hybrid/online), international cohorts and support from SEIUM Career Services.
Ethics and safety:a safety-by-design approach, with cyber-OT, DIH and compliance as its pillars.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Software product definition

Determine when software is a medical device and its class.

Safety classification

Plan development according to the safety class of IEC 62304.

Development plan

Specify traceable software requirements and architecture.

Requirements and architecture

Implement detailed design with secure coding practices.

Risk analysis

Integrate, test and release software with documented evidence.

Career opportunities

Where this takes you

Medical device software engineerSoftware quality managerVerification and validation engineerMedical software architectSoftware regulatory specialistDevOps engineer in regulated environments
Admissions & scholarships

Requirements

  • Prior technical training or professional experience in the sector. A university degree is not required.
  • Internet connection and a computer capable of running the programme's software.
  • Sufficient Spanish to follow technical regulatory texts.

Ready to start?

Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.

FAQ

Frequently asked questions

The programme comprises 800 hours in total, spread over 6 to 8 months. This is between 10 and 15 hours per week on average, compatible with full-time work.

You will work with Jira, Polarion ALM, Git and SonarQube. Free, academic or evaluation versions are used, and the tutor indicates the free alternative where one exists.

An SEIUM diploma on passing the continuous assessment and the integrating project. This is SEIUM's own training, not an official qualification from the Ministry.

Yes. Modules passed in a course or postgraduate diploma in the same area count towards the higher-level programme. Please consult the credit recognition policy when you enrol.

Postgraduate Diploma in IEC 62304: Medical Software LifecycleEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.