Starting From the Specification: The Contract of the Program

The specification is the program’s contract. In a medical display program, it must capture not only optical and mechanical parameters but also the quality and documentation requirements:

• Functional specification — resolution, luminance, interface, touch, and environmental limits.
• Quality requirements — inspection plans, traceability, and change control expectations.
• Documentation deliverables — the records and reports that must accompany samples and production.

If the specification is vague, every later gate is vague. The supplier and the device manufacturer should agree the specification in writing before tooling or sampling begins.

The Certification Gate: Verifying the Supplier’s Quality System

ISO 13485 certification is not a feature of the display; it is a property of the supplier’s quality system. The certification gate is where you verify that the system exists and covers the processes you rely on:

• Certificate and scope — check the certificate, its scope, and its validity with the issuing body; the scope must cover the activities you are buying.
• Process coverage — confirm that design control, production, and any relevant processes sit inside the certified system.
• Evidence, not claims — treat marketing statements about certification as unverified until the certificate and scope are checked.

The certification gate qualifies the supplier’s system; the sample gates qualify the product. Keep the two separate.

Sample and Validation: Proving the Design

Sample phases in a medical program exist to prove the design against the specification under controlled conditions. Expect each sample round to come with:

• Test evidence — optical, electrical, environmental, and any application-specific measurements against the specification.
• Design documentation — drawings and records that reflect what was actually built.
• Approval gates — formal sign-off points where the device manufacturer accepts each round before the program advances.

The panel selection and customization decisions inside a medical program are their own topic; here, the point is that samples carry evidence and gates, not just hardware.

Production Under ISO 13485: Batch Records and Controls

Once the design is approved, production runs inside the supplier’s quality system. What the device manufacturer should expect:

• Batch records — production records that tie each lot to its materials, process settings, and test results.
• Change control — any change to materials or process is managed and notified, because a silent change can invalidate a qualified design.
• Nonconformance handling — defects are recorded, dispositioned, and corrected through the supplier’s system, with visibility to the buyer where the agreement requires it.

Day-to-day traceability and PCN mechanics are covered in the medical display supply chain guide; this article describes where those practices fit in the program flow.

The Output: A Qualified Module and Regulatory-Ready File

The output of the program is not just a module—it is a module plus a file the device manufacturer can use in its own regulatory work. That file typically includes:

• Specification and drawings — the agreed design baseline.
• Test reports — validation evidence for the module’s performance.
• Certificate and scope records — the supplier quality system evidence.
• Batch and change records — traceability for production and future changes.

The module file supports the device manufacturer’s design history and regulatory submission; it does not replace the device-level work. IEC 60601-1 and ISO 13485 requirements for the finished device are covered in the medical display requirements guide.

Typical Timeline: From Specification to Production

A medical display program follows the same shape as other custom programs—specification, tooling and samples, validation, pilot, and production—with added gates for quality-system verification and documentation. Timelines vary with complexity, so treat any week count as an example range rather than a commitment. What does not vary is the sequence: specification before tooling, certification checks before production, samples before pilot, and documentation at every step. The generic development phase gates and sample timing guides describe those stages in more detail; this program adds the medical quality-system layer on top.

Lessons for the Next Program: Sequence and Documentation

Programs go faster the second time when the first one leaves reusable assets:

• Reusable specification templates — medical display requirements repeat across programs; a solid baseline spec shortens the next round.
• Known supplier evidence — certificates and scope records verified once still need re-checking, but the checklist is faster.
• Documentation discipline — programs that document at each gate avoid the end-of-program scramble for missing reports.

The sequence is the lesson: keep gates in order and keep documents attached to the gate that produced them, and the next program starts ahead instead of from zero.

Frequently Asked Questions