Configuration targets for OEM discussion. These are not approved model numbers or a ranking of best-selling products. Final specifications, availability, MOQ and market documentation require project review. Read the industry format references.
OEM CONFIGURATION 01A prefilled cartridge format for programs that need more than one selectable dose. The core decisions are the usable fill volume, dose increment, maximum dose and the end-of-content behavior.
3 mL cartridge target
Variable dose; increment to define
OEM CONFIGURATION 02A smaller cartridge presentation for a variable-dose development brief. A reduced nominal capacity can change the intended number of administrations, packaging and usable volume assumptions.
1.5 mL cartridge target
Variable dose; range to define
OEM CONFIGURATION 03A multi-dose prefilled concept in which each intended administration uses a defined dose. Fixed-dose architecture needs a clear relationship between fill volume, dose volume and available administrations.
3 mL cartridge target
Repeated fixed dose; amount to define
OEM CONFIGURATION 04A compact fixed-dose cartridge concept for an application with a defined administration volume. The smaller container target is a project input, not a claim about a particular medicine.
1.5 mL cartridge target
Fixed dose; count to define
OEM CONFIGURATION 05A dose-dial development direction for applications where small changes in the selected dose are important. The appropriate increment depends on the formulation and intended dosing scheme.
Cartridge volume to define
Fine dose increment; validation required
OEM CONFIGURATION 06A branding and packaging program around a defined prefilled device configuration. Brand differentiation can include color, graphics and package presentation, subject to the underlying design controls.
Compatible cartridge to confirm
Platform-dependent dose format
OEM CONFIGURATION 07A durable-body concept built around a replaceable 3 mL cartridge target. The device lifetime and the cartridge replacement sequence are central parts of the specification.
3 mL cartridge target
Variable or fixed; project-specific
OEM CONFIGURATION 08A reusable device direction with a metal exterior for projects prioritizing feel, appearance and mechanical design. Exterior material alone does not establish accuracy, durability or drug compatibility.
Cartridge interface to define
Dose range to define
OEM CONFIGURATION 09A reusable-body development brief emphasizing handling weight and portability. Lower mass should be evaluated with the intended users and protection requirements rather than treated as an automatic benefit.
Cartridge interface to define
Dose increment to define
OEM CONFIGURATION 10A cartridge pen concept for a dose scheme requiring carefully defined selection increments. Reusability adds reset, wear and replacement questions to the dose-setting requirements.
Compatible cartridge to confirm
Fine increment; evidence required
OEM CONFIGURATION 11An ergonomic development direction for intended users who may have difficulty gripping, turning or pressing a device. Suitability must be demonstrated with representative users and realistic tasks.
Container to define
Operating force to evaluate
OEM CONFIGURATION 12A reusable pen direction emphasizing clear product identification and a readable dose interface. Contrast, type size and feedback need to work together in the intended lighting and use environment.
Container to define
Display scale to define
OEM CONFIGURATION 13A prefilled-syringe autoinjector direction for a defined small-volume application. A 1 mL container target does not mean every project delivers the full nominal container capacity.
1 mL PFS target
Single administration; fill to define
OEM CONFIGURATION 14An autoinjector direction built around a 2.25 mL prefilled-syringe target. The container format is seen in public industry platforms, but suitability still depends on the intended formulation.
2.25 mL PFS target
Fill and usable dose to define
OEM CONFIGURATION 15A development brief for related product presentations that may use different fill volumes. The requirement is to understand how the mechanism handles the proposed stopper positions and dose volumes.
PFS format to confirm
Fixed delivered dose per configuration
OEM CONFIGURATION 16An application-led autoinjector project in which formulation resistance is a central design input. The relevant viscosity range should be measured under conditions that reflect the intended product use.
Container and needle to define
Viscosity envelope to measure
OEM CONFIGURATION 17A user-sequence direction emphasizing a short activation workflow. The term two-step describes a proposed interaction and does not by itself demonstrate intuitive or error-free operation.
PFS interface to define
Activation sequence to evaluate
OEM CONFIGURATION 18An autoinjector direction using a distinct activation control. The button geometry, required force and any interlock should be reviewed in the context of the complete intended user sequence.
Container to define
Button and interlock to evaluate
OEM CONFIGURATION 19An autoinjector project focused on the interaction between delivery and a protective needle feature. A shield needs a clearly defined state before, during and after the administration sequence.
Compatible PFS to confirm
Shield sequence to define
OEM CONFIGURATION 20A feasibility direction for programs whose required volume exceeds their current handheld presentation. Larger volume can affect the container, drive, handling and time needed to complete delivery.
Volume above standard brief; assess
Volume and delivery time to validate
OEM CONFIGURATION 21A digital pen direction with local information about prior use. The project must define what is recorded, how long it remains available and how the user interprets the display.
Compatible platform to define
Memory function to specify
OEM CONFIGURATION 22A connected device project using Bluetooth as a proposed communication interface. The app, firmware and phone environment are part of the scope rather than optional details after hardware selection.
Pen and firmware to define
Bluetooth integration; feasibility review
OEM CONFIGURATION 23A connected pen direction using near-field communication for a defined data transfer workflow. The intended user action and supported reading devices need explicit requirements.
Pen and memory to define
User-initiated transfer concept
OEM CONFIGURATION 24A device and app project centered on reminders and user feedback. A reminder can support a workflow, but it should not be presented as proof of treatment adherence or a dose recommendation.
Device and app scope to define
Reminder logic to specify
OEM CONFIGURATION 25An integration brief connecting pen records with a compatible glucose data source. The initial scope should state whether it is visualization, review or another defined function.
Named integration to evaluate
Data sharing; not default closed loop
OEM CONFIGURATION 26A connected device program organized around a study protocol and its data needs. The intended measure determines the event definitions, version control and site support requirements.
Protocol-specific platform
Event data and exports to define
OEM CONFIGURATION 27A connected delivery project that makes records available for a defined remote review workflow. Transmitting information does not itself provide continuous clinical supervision or emergency response.
Device, app and service to define
Monitoring responsibilities required
OEM CONFIGURATION 28A feasibility inquiry for a precisely stated AI function associated with an injection device. The goal may involve event interpretation or analysis; no autonomous dosing capability is assumed.
Hardware and algorithm to define
AI function and evidence to specify
OEM CONFIGURATION 29A device project for a defined insulin presentation and intended user group. Container compatibility and dose-scale interpretation need to be established for the exact medicine configuration.
Compatible insulin presentation required
Scale tied to specified concentration
OEM CONFIGURATION 30A prefilled device project for a specified peptide formulation. Cosmetic-grade raw material capability does not establish suitability for an injectable medicine or a finished combination product.
Formulation-specific cartridge
Dose and stability inputs required
OEM CONFIGURATION 31A multi-dose delivery inquiry for a defined GLP-1 development program. This is a device project category and does not offer a branded medicine or establish therapeutic equivalence.
Formulation-specific container
Multi-dose scheme to define
OEM CONFIGURATION 32An autoinjector development direction for a specified biologic presentation. The formulation, container and delivery mechanism need to be evaluated together before performance can be promised.
Formulation and PFS to define
Volume and viscosity to assess
OEM CONFIGURATION 33A cartridge-based device brief for a specified hormone delivery application. Similar therapeutic categories can still require different dose scales, containers and handling instructions.
Medicine-specific cartridge
Dose range and increment to define
OEM CONFIGURATION 34A device development direction for a defined fertility treatment presentation. Dose selection and clear instructions should be considered alongside formulation and container compatibility.
Medicine-specific container
Precision dose scheme to define
OEM CONFIGURATION 35A distinct delivery technology inquiry using a liquid jet rather than a conventional pen needle. Suitability depends on the intended medicine, volume, route and device operating conditions.
Formulation and consumable to define
Pressure-driven delivery feasibility
OEM CONFIGURATION 36A powered delivery concept where motor, controls and energy supply become part of the mechanism specification. The development brief must define both normal operation and failure behavior.
Container and drive to define
Powered actuation; controls to evaluate