Copyright © 2020-2021 Shenzhen CDTech Electronics LTD. All rights reserved. Site Map Powered by iwonder.cn
display / touch / bonding solutions
display / touch / bonding solutions
A medical display programme differs from an industrial one less in the engineering than in the paperwork that surrounds each decision. Requirements are traced to verification, samples are built against frozen documents, and every change after release has a record. This is what that looks like in phases, with the documents that gate each one – and why the timeline is longer in a predictable way.
Every requirement needs a partner verification method.
Design control begins with documented requirements and a stated intended use, then traces each requirement to a design output and a verification activity. For a display module this means the customer requirements – luminance, temperature, touch behaviour, cleaning agents, lifetime – become a specification with measurable limits and a test method for each. The value is practical rather than bureaucratic: it eliminates the ambiguity that produces arguments at sample review.
The first gate in a display programme is therefore a requirement specification that both parties agree is complete. CDTech’s notes on the medical display requirements side of this process are a useful reference for what belongs in that document.
The device manufacturer owns the file; the supplier contributes to it.
The design history file belongs to the organisation responsible for the device, and the display supplier’s role is to provide component-level records that the manufacturer incorporates: the specification, the verification results, material declarations and change history. Where the display is itself developed specifically for the device – a custom cover glass, a custom FPC, a new bonding configuration – the design work becomes part of the device’s design control, and the interface between the two organisations needs a documented boundary.
Draw that boundary explicitly. The most common source of confusion in a custom medical display programme is who is responsible for verifying a characteristic that is created by one party and used by the other, such as the optical performance of a bonded stack.
Each sample phase closes a set of documents, not just a build.
Typical phases and the documents that close each one
| Phase | Purpose | Records |
|---|---|---|
| Concept and requirements | Intended use, requirements, constraints | Requirement specification, intended use statement, risk input |
| Design and drawing release | Mechanics, stack, interface defined | Evaluation drawings, material list, interface specification |
| A-sample | Prove the concept functions | Build record, functional test results |
| B-sample | Prove the design in representative conditions | Optical and mechanical test results, review record |
| C-sample and process validation | Prove production tooling and process | Process validation, capability data, cosmetic standards |
| Pilot and release | Confirm readiness at production rate | First-article inspection, inspection criteria, change control entry |
The gate discipline matters more than the labels. Each phase should end with a documented decision to proceed, with the evidence attached, because that record is what supports the device’s technical file later.
Verification asks whether it meets the specification; validation asks whether it works in use.
Verification is the measurable part: luminance within limits, temperature range achieved, touch accuracy on a grid, cleaning cycles survived. Validation is use-based: does the display actually serve the clinical workflow, can staff clean it as intended, do they read it correctly under real lighting? A programme can pass verification and fail validation, which is why clinical or simulated-use evaluation usually follows the technical tests.
Plan validation early enough to influence the design. A large part of the cost of a late validation failure is the tooling that has already been released.
Design the evidence package before the first sample ships.
Packaging this at the outset means the file can be assembled from existing documents rather than reconstructed under submission pressure. CDTech’s quality certifications page lists the current quality-system scope as a starting point.
The process is part of the product.
Where a programme involves custom tooling or optical bonding, the process itself becomes a validated element: bonding thickness, cure profile, lamination pressure and inspection criteria all affect the delivered module, and variation in them produces variation in the product. Process validation therefore needs defined parameters with limits and evidence that the process holds them, plus an inspection that detects when it does not.
For bonding in particular, the inspection criterion should be measurable – haze, edge condition, luminance uniformity – rather than a visual opinion, because optical defects are exactly the class of characteristic that two inspectors will classify differently.
Run at production rate before committing to release.
Pilot production demonstrates that the line can build the module at the intended rate without losing yield or quality. The useful evidence is first-article inspection across the build, capability data for the critical characteristics, and a yield and defect Pareto. Where a characteristic is measured on 100 per cent of units, state that; where it is sampled, state the sampling plan.
The pilot is also the right moment to confirm the cosmetic acceptance standard with boundary samples, since appearance differences are the most frequent source of disputes in display supply and the least amenable to written description alone.
Release is the start of the obligation, not the end.
After release, any change to a material, process, site or firmware that could affect the product must be notified, assessed and approved. For displays, the changes most likely to affect performance silently are in the polarizer, the bonding adhesive, the LED bin and the cover glass coating, because none of them changes the electrical behaviour. A change control system that only covers drawings will miss them.
The supplier should be able to show the change categories it manages, and evidence that it has applied the requirement to its own sub-suppliers for critical materials.
Medical programmes take longer for structural reasons.
Indicative timeline shape by programme type
| Programme type | Main drivers | Timeline shape |
|---|---|---|
| Standard module, custom cable and bracket | Specification, sample, verification | Shortest; tooling minimal |
| Standard module, custom cover glass and bonding | Glass tooling, bonding process validation | Adds tooling and process validation time |
| Custom FPC, backlight or module | Tooling, process capability, cosmetic standard | Longest; all phases plus pilot |
CDTech’s notes on the sample process and tooling payment describe what each stage should deliver before the next payment, which is the practical control a buyer has over schedule risk.
Compare documentation and validation scope, not unit price.
Two quotations for the same module can differ by a factor because one includes tooling, process validation, verification reports, material declarations and a traceability programme, and the other supplies a module to a drawing. The comparison should be made line by line against the required evidence package, with the responsibilities for each verification activity stated. Where a supplier does not offer a service, that work moves to the customer at their cost and with their schedule risk.
Device-level regulatory obligations remain with the manufacturer under frameworks such as IEC 60601-1 and the EU medical devices framework, with supplier quality expectations described through bodies such as AAMI.
What does an ISO 13485 display programme involve?
Documented requirements with traced verification, sample phases that close with records, process validation for tooling and bonding, pilot production with capability evidence, and change control after release. The engineering is similar to an industrial programme; the difference is the evidence produced at each step.
How long does a medical display project take?
It depends on how much of the module is custom. A standard module with a custom cable and bracket is the shortest case; custom cover glass and bonding add tooling and process validation time; a fully custom module adds capability studies and pilot production. Add time for verification and any clinical or simulated-use validation.
Who owns the design history file for a custom display?
The device manufacturer owns it, and the display supplier contributes component-level records. Where the display is developed specifically for the device, the boundary between the two parties’ design control responsibilities must be documented, especially for characteristics created by one party and used by the other.
What should a buyer check before paying for tooling?
That the specification is frozen, the cosmetic acceptance standard is agreed with boundary samples, the process validation plan is defined, and the verification tests and their acceptance criteria are documented. Tooling released before those exist is the most common cause of late rework.
Send the intended use, customisation scope and required evidence package to CDTech; the reply will set out the programme phases, the documents produced at each gate and the timeline shape for that scope.
Contact [email protected] or use the contact page.
For related engineering guidance, see our medical LCD display guide.
By continuing to use the site you agree to our privacy policy Terms and Conditions.