eDHR

Electronic Device History Record System

Excel VBA

The Mission

Generate Device History Records digitally and on-the-fly while following and confirming work-instructions for MedTech equipment.

Overview

eDHR was a self-initiated continuous improvement project to digitise Device History Records in a regulated environment. I identified issues with paper-based records, including occasional incomplete data, which posed an audit risk. The solution became a configurable digital workflow engine, supporting multiple products and manufacturing flows while enforcing sequencing, validation and traceability.

// FIG_01: Entry screen guiding operators into validated workflows
Result // 01

Replaced manual Device History Records with validated, step-based digital workflows

Result // 02

Eliminated common documentation errors through enforced sequencing and validation

Result // 03

Delivered audit-ready electronic traceability approved by quality and regulatory teams

Result // 04

Achieved strong operator adoption through collaborative design

01 // Discovery & Design

// Discovery

Shadowed shop-floor users to understand issues with paper-based records

// Key Decisions

The system had to be configurable and useable for other products; the 'Next' and 'Back' buttons had to be displayed in random positions to avoid operator fatigue and automatic clicking

// Trade-offs

Developed in Excel VBA to leverage existing infrastructure, IT-approval constraints and user familiarity

🛠️ One thing we changed after launch

Integrated with a dedicated line printer, as compliance meant all records had to be physically signed and stored

02 // Technical Execution

// Tech Stack

Excel VBA, integration with IFS to automatically upload the eDHRs

// Implementation

Master template controlled by IT QA; product-specific master copies controlled by Manufacturing Engineers; product working files in a networked location

💡 One thing I would do different now

Implement stronger version control and structured logging to improve long-term maintainability across multiple product configurations

03 // Ownership

// Team

Me, myself and I. I worked closely with Production, Engineering, shop floor managers, QA, IT and operators to ensure usability, trust and adoption

// Timeline

Developed over a few months, as it was not my main focus of work

// Ownership

I owned the whole eDHR application and IT owned the ERP-connector

❤️ The thing I enjoyed the most

Designing something practical that operators trusted daily and that measurably reduced audit risk

04 // Evidence

// FIG_01: Entry screen guiding operators into validated workflows
// FIG_02: Configurable step-based workflow
// FIG_03: Breaking down automatic (A) and manual (M) steps in the end-of-line tester to separate what should be automated from what required operator input
Previous
Next