In this article
Custom integrated circuits used in medical equipment, such as sensing, imaging, monitoring or stimulation systems. Their engineering requirements depend on the product's intended function and operating environment.
Engineering within a medical product
A medical-device ASIC can support sensing, signal conditioning, control, communication or processing within a larger medical product. Its requirements should be derived from the device's intended function and system-level risk analysis. The chip itself is only one part of that system. A component description must not imply that the finished device is clinically validated or authorized for a particular use. Define electrical performance, operating conditions, fault behavior and traceability needs with the responsible product and assurance teams before selecting the architecture.
Signal quality and operating states
For a measurement-oriented device, consider the complete path from the sensor to the interpreted result. Input range, noise, filtering, reference behavior, conversion and calibration can all matter. Digital resolution alone does not establish measurement accuracy. Also review startup, low-battery operation, disconnected sensors and invalid data. The design should make relevant faults observable to the surrounding system. Requirements for patient-connected interfaces, isolation or other protections belong in the complete product design and must be handled by the appropriate specialists.
Verification and test evidence
Trace chip-level requirements to suitable analyses and tests. Keep design revisions, test configurations and results controlled so the product team can understand what was demonstrated. Production testing should target relevant defects and functional limits, while characterization evaluates behavior over defined conditions. These activities do not replace system validation. If the ASIC includes programmable behavior, plan software maintenance and configuration control as well. A well-documented component helps the device manufacturer build its assurance case without overstating what a component test alone can establish.
Longevity and support
Medical products may require sustained availability, careful change notification and the ability to investigate failures. Discuss the expected lifecycle, supplier dependencies, traceability and storage of development evidence. A change to a package, process or test method can have implications beyond purchasing. Define who reviews those changes and how their impact is evaluated. Avoid publishing generic lifetime or compliance promises for all medical ASICs. The appropriate commitments depend on the product, intended application, supplier agreement and the evidence required by the responsible organization.
Questions about medical ASICs
Does using an ASIC make a medical device approved?
No. A chip's design and test evidence support the larger product process. Device authorization, clinical performance and application suitability require their own appropriate evaluation.
Is higher converter resolution always better?
Not necessarily. Noise, accuracy, bandwidth, power and the complete sensor chain determine useful measurement performance. Additional digital bits cannot recover information already lost in the analog path.
Derive chip requirements from system behavior
Begin with the product's intended tasks, users and environment. Describe the signals it receives, decisions it makes and outputs it produces. Include timing, energy and operating limits where they matter. Distinguish requirements that the chip can satisfy directly from those that depend on software, sensors, power supplies or other components. This prevents a good component specification from being mistaken for complete product performance. A useful system review identifies the boundaries and assigns an owner to each assumption that crosses them.
Allocate integration and flexibility
Choose which functions belong in fixed logic, software or external devices. Integration can reduce board complexity and communication overhead, but it also connects the functions' revision and manufacturing lifecycles. Preserve flexibility for plausible product changes without assuming that every requirement can remain open indefinitely. Consider configuration, firmware and interface compatibility alongside area and power. The architecture should explain why each function is integrated and what evidence supports the choice. A custom chip is most useful when it addresses a concrete product constraint rather than simply increasing the amount of circuitry on one die.
Exercise realistic operating cases
Test normal use, startup, interrupted power, invalid inputs and the relevant error or recovery sequences. Use representative workloads and environmental assumptions. Include software-visible behavior so the complete product can detect and respond to important conditions. Measurements should state the setup, configuration and product boundary. A chip-only benchmark can answer a narrow question, but it may not represent what a customer experiences. Preserve reproducible tests and distinguish measured results from estimates while the design and evaluation platform are still evolving.
Plan manufacturing and support
Include package, test access, diagnostics and expected production life in the development plan. Discuss traceability and change control according to the application's actual needs. If qualification or regulatory requirements apply to the finished product, coordinate them with the responsible product team; the presence of an ASIC does not establish compliance. Consider how firmware, supplier changes and field issues will be managed over time. A supportable design connects technical behavior with the information and responsibilities needed to manufacture, evaluate and maintain the product after the first successful demonstration.
A practical cross-discipline review
Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.
Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.
Explore the related Avnet offering or discuss your project requirements.
