Access Official Technical PDF

Share Summary:LinkedInEmail

Connected drug delivery devices can make treatment events more visible to patients and care teams by recording information such as a dose, injection time or product identity. For industrial automation engineers, system integrators and healthcare technology leaders, the challenge is not simply adding wireless communication. A useful connected system must capture reliable data, fit established device workflows and make that information available to the people who need it.

Interest in connectivity accelerated as telemedicine and remote care became more important during the COVID-19 pandemic. Connected devices can contribute information to these models, but they are not a standalone solution to treatment adherence or better outcomes. Their practical value depends on how sensing, software, users and healthcare processes work together.

What connected drug delivery devices can capture

A conventional injection device performs a physical task: delivering medication. A connected add-on can also record selected events and transmit related information to another system. For example, a sensor attached to a disposable insulin pen can detect the selected dose and the date and time of an injection, then send those details to a mobile application using Bluetooth.

This can fill a gap in a patient’s digital treatment record. Blood glucose monitors and insulin pumps may already transfer information to mobile devices, while injections made with a conventional pen may otherwise be harder to track automatically. A connected sensor can capture that event without requiring the patient to manually enter every injection.

Data quality starts with the physical sensing method. In one magnetic approach, a magnet is placed in a cap over the pen’s dose knob, while sensors in the attached device track changes in the magnetic field. The knob rotates as a dose is selected and moves inward as the medication is delivered. By analysing changes in the measured field, the system can estimate the selected dose and distinguish the steps in the injection cycle.

Designing for reliable injection data

Capturing a meaningful signal requires more than choosing a sensor. Magnet dimensions, position and strength affect the field that the sensor measures. The design must also account for the sensor’s measurement range and noise, as well as interference from external magnetic sources. These factors can vary with the pen platform, so a model developed for one device may need adaptation for another.

One way to reduce the influence of unwanted signals is to use two magnetic sensors and combine their measurements. The resulting data can be processed to reduce noise and calculate parameters such as the magnet’s angle and distance. Changes in these measurements help identify rotation during dose selection and movement during delivery.

Testing should address both repeatability and real use. A mechanical test bench can reproduce injection movements consistently and help generate training and validation data. However, measurements made with a controlled setup do not fully represent how people handle a pen. User testing can reveal interference or unexpected movements that affect the signal. Validation checks can flag an unusual event rather than presenting uncertain information as a confirmed injection record.

Connectivity is not an automatic adherence fix

Connected data may help care teams understand whether treatment is being followed and direct support where it is needed. But adding connectivity does not, by itself, ensure that a person will take medication as prescribed. People who have difficulty following a treatment routine may also be less likely to use an app or complete device setup.

Each required interaction can add friction: installing an application, pairing a device, connecting to a network, logging in, entering information or charging a battery. Device and service designers should therefore distinguish between data collection that happens automatically and tasks that depend on ongoing user participation. The fewer steps required from the patient, the less the system relies on repeated manual effort.

Connectivity may be most useful when it helps identify where support is needed and enables appropriate follow-up. That requires alignment between the device, the data it records and the care process that uses it. If an injection record is ambiguous or inaccessible to the relevant care team, transmitting it alone does not resolve the underlying problem.

Traceability beyond the individual injection

Connected systems can also associate an administration event with product information. A prefilled syringe with an NFC tag on its piston rod, for example, can carry details such as the drug, concentration, batch number and expiry date. After a complete injection is detected, that information can be transferred through an NFC reader with a date and time stamp.

This approach illustrates how device connectivity can support more than dose tracking. Product identification and administration records may help with traceability and pharmacovigilance, provided the data can be securely accessed and connected to the appropriate patient and healthcare records. The syringe’s design also needs to preserve the familiar injection process; added technology should not introduce unnecessary complexity for the healthcare professional administering it.

For a large vaccination programme, such a system could help record which product was administered and when. The broader workflow would still depend on patient identification, accessible health records, authorised access and secure handling of data. The device can contribute a reliable administration event, but it cannot independently supply every part of that system.

Plan the complete connected-device workflow

For engineering and operational teams evaluating connected drug delivery, several questions are worth addressing early:

  • What event must be recorded? Define whether the system needs to capture dose selection, completed delivery, product identity or another specific event.
  • How will the signal be validated? Consider platform differences, sensor noise, external interference and real-world handling.
  • What must the user do? Map setup, pairing, charging and app interactions, and identify which steps can be removed or automated.
  • Who will use the data? Establish how information moves to patients, healthcare professionals or other systems, and how access and security are managed.
  • What happens when data is uncertain? Define how the device communicates incomplete or unexpected events instead of implying certainty.

Conclusion: build connectivity around a real task

Connected drug delivery devices can make injection events and product details more visible, supporting remote follow-up, traceability and treatment records. Their usefulness depends on accurate sensing, validation across real handling conditions and a workflow that does not place excessive demands on patients or healthcare professionals. For decision-makers, the practical priority is to define the task the technology must support, then design the device, data pathway and user experience around it.

Access Official Technical PDF

About The Author