What protecting a connected implant means
Medical device cybersecurity concerns protecting device functions and associated information against unauthorised access, modification or use and availability problems. The FDA treats these risks as part of product safety throughout its life cycle. The scope depends on the particular device and its actual connections.
At work, this requires distinguishing a person using a medical device from the company’s information technology assets. An implant does not become a corporate asset because its user enters the premises. Nor do all implants have wireless connections, applications or adjustable functions. This entry addresses preventive coordination when a specific compatibility or continuity need exists. It does not attribute identical capabilities to different products or assume vulnerability simply because a person has an implant.
Sources: [1]
Cybersecurity and electromagnetic interference are different risks
A cybersecurity issue involves digital systems and authorised uses. Electromagnetic interference belongs to assessment of fields and device compatibility with the environment. In Spain, Royal Decree 299/2016 requires specific consideration of workers with active or passive implanted medical devices and other body-worn devices when assessing relevant risks.
A corporate antivirus therefore does not resolve electromagnetic exposure, and a field measurement does not establish that an application is secure. We propose keeping two assessment questions separate: which physical workplace conditions need checking, and which digital dependencies need coordination? Both may concern the same individual, but they require different information and responsibilities. A technology alert should not be used to infer general incompatibility with any industrial job or to replace assessment of actual conditions.
Sources: [3]
Understanding the system without invading privacy
Organising a response requires identifying only dependencies relevant to work. An external unit, application or communication with a healthcare service may exist; the presence and purpose of each component need confirmation. A manager should not reconstruct a person’s medical history independently or request all their access credentials.
As a coordination proposal, occupational health can translate a preventive need into conditions the organisation understands: access to an appointment, adjustment of a task or review of an environmental source. Information technology staff can assess an authorised corporate connection without receiving unnecessary diagnoses. The useful question is not which disease a person has, but which workplace condition needs to be resolved and who has a legitimate role in processing the necessary information. The answer should guide the information request.
Official alerts and device maintenance
The FDA advises following manufacturer and healthcare professional instructions, using permitted connections and attending to relevant updates and alerts. It also advises against applying internet fixes independently. Unusual behaviour should be discussed with clinical professionals or the manufacturer, as directed by the device instructions.
For an employer, the practical application is to facilitate appropriate contact and avoid improvised interventions. Information technology support should not be asked to reprogramme an implant or test a vulnerability on somebody’s device. A security notice needs checking against the model and circumstances through the competent channel. A general news story does not establish that a particular worker is affected. A pending update requires the appropriate assessment, rather than a clinical decision made by the employer.
Sources: [2]
Work compatibility and individual adjustments
Assessment should start with the actual job: tasks, equipment, movement within the premises and planned changes. A label such as administration or maintenance may hide very different conditions. We propose describing relevant activities and passing technical information to the professionals responsible for compatibility assessment while keeping clinical information separate.
The useful organisational outcome is a concrete measure with an owner and review date: adjusting a task, checking an environmental condition or supporting necessary continuity of care. Having an implant does not justify automatic exclusion from an occupational category. Nor is an unsupported declaration that everything is compatible sufficient when a well-founded concern exists. Decisions need individual consideration within clinical and preventive competence, without turning technical uncertainty into a judgement about the person’s overall ability.
Confidentiality and access to information
The AEPD guide, updated in December 2025, restricts employer access to occupational health surveillance information and distinguishes preventive conclusions from medical records. Specific information may be needed to meet an obligation, but it must remain strictly relevant. Protection also applies to particularly sensitive workers.
In the proposed pathway, record which conclusion each recipient needs without attaching complete clinical reports to an information technology ticket. A workplace adjustment should not appear on a noticeboard alongside its underlying diagnosis. Contractor coordination does not authorise disclosure of implant details either. Review access, retention and communication channels before creating a new form: the mere existence of a field does not make its contents necessary. Where responsibilities differ, information should follow the task rather than broad organisational visibility.
Responsibilities worth clarifying
We propose a simple division: the treating team and manufacturer advise on the device; occupational health assesses its relationship with the job within its competence; prevention staff assess working conditions; information technology staff address corporate systems actually within their remit. The worker participates in decisions and has a clear contact for communicating needs.
This arrangement avoids two gaps: everyone assuming somebody else will solve the problem, or one department taking decisions beyond its competence. Before changing equipment, a network or a task, check whether an agreed measure could be affected. Every general technology incident need not become a medical alarm. Relevant dependencies should nevertheless be identified so they are not interrupted without assessment. The contact arrangements should remain usable when the usual responsible person is absent.
Responding without improvising clinical decisions
An organisational procedure can distinguish a compatibility enquiry, an official alert and a situation requiring assistance. Its purpose is to direct each to the appropriate channel. When urgent healthcare is needed, the site’s response arrangements take priority; assistance should not be delayed to complete forms or first prove a cyberattack.
This entry does not propose disconnecting treatment or changing implant settings. Technical management needs coordination with those who understand clinical implications and manufacturer instructions. Preserve necessary incident information with restricted access and avoid public speculation about the cause. An observed failure can have several explanations; classifying it as an attack without investigation can impair the response and create unjustified alarm. Record confirmed facts separately from hypotheses and questions still awaiting specialist assessment.
Hypothetical example of appropriate coordination
A company changes an access system and a person using a medical device requests a compatibility check. In this hypothetical example, the manager does not demand a copy of the medical record or impose automatic exclusion. The technical description is passed through the established preventive and healthcare pathway, with an appropriate temporary arrangement while assessment takes place.
Separately, the team checks whether any authorised communication needed for care depends on the site’s network. The two questions are investigated independently. The organisation receives the practical conclusions it needs rather than all the medical details. The case closes when the measure is implemented and the person knows how to request review if conditions change. This example is not an authorisation for any specific device model or access technology.
Indicators that respect people
Process assessment can use response times for enquiries, completed adjustments, reviewed changes and completion of agreed reviews. Indicators should assess the ability to resolve working conditions, rather than counting implants or classifying people as vulnerable because of their device.
We also propose reviewing excessive information requests, inappropriate access and questions left without an owner. Even aggregate data may identify someone in a small team, so consider what is displayed and to whom. A good outcome is not the disappearance of all enquiries, but needs being reported confidently and resolved proportionately. Metrics do not replace individual review or establish a device’s clinical safety on their own. Learning should focus on making coordination reliable while reducing unnecessary disclosure.
Relationship to OSH and useful documentation
This entry connects cybersecurity, confidentiality, occupational health surveillance and work adjustment. It complements the entry on implants and electromagnetic fields without conflating it with industrial network security. Prevention means coordinating relevant information and actual measures while respecting boundaries between healthcare and business management.
A document system can record responsibilities, review dates and preventive actions with appropriate permissions, depending on its available functions. It should not become an indiscriminate copy of medical records or a console for changing medical devices. This entry attributes no implant connections or therapeutic functions to Sabentis. The final criterion is that a person can work under assessed conditions and receive necessary care without unnecessary exposure of their information. Documentation supports that outcome; it is not a substitute for the assessment itself.
Frequently asked questions
Are cybersecurity and electromagnetic interference the same?
No. One concerns digital systems; the other concerns compatibility with fields. They need assessment through their respective mechanisms and responsibilities.
Can an employer reprogramme an implant?
It should not make clinical interventions or improvised changes. It should support contact with competent healthcare and manufacturer teams.
Does an implant prevent industrial work?
Not automatically. Compatibility needs individual assessment of tasks, exposures and relevant instructions.
Must the complete medical record be shared for a work adjustment?
No. The organisation should receive strictly necessary information and preventive conclusions through authorised channels.
