StrategyCore
Back to Resources
13/cybersecurity 2 min read

Planning a medical-device security evaluation in Japan

Work with clinical engineering, information security and the equipment manufacturer.

A hospital needs to assess connected-device risks while protecting clinical operations. Start with the equipment list, manufacturer guidance and the restrictions set by clinical engineering and IT. Agree the information to collect and the testing method before any discovery or scanning begins.

Medical-device review responsibilities

SC-LY-02 · REV A · 2026.07

Clinical operations

use and continuity

T1

Device maintenance

manufacturer and support

T2

Information security

access and monitoring

T3

Joint review

evidence and approved action

T4

Illustrative responsibilities; the hospital’s actual organisation and manufacturer instructions govern the work.

Clinical operations, device maintenance and information security contribute different evidence.
01

Set the clinical and technical scope

Identify the devices, clinical owners, maintenance contracts and information systems in scope. Check which activities can be performed while equipment is in use and which need a maintenance window or manufacturer involvement. Device categories and protocol names do not establish whether a particular model supports an agent, a query or an update.

02

Collect and validate device information

Use maintenance records, approved inventory sources and authorised monitoring to establish model, version and support status. Network protocols can add clues, but they do not always expose complete identity or firmware information. An intelligence service can enrich supplied records; it does not itself prove that every device has been found or that a vulnerability applies.

03

Plan mitigations with the responsible teams

Validate security findings against manufacturer advisories and the actual configuration. Where an update is available, review its supported installation process and operational impact. Where it cannot be applied immediately, assess controls such as restricted access, segmentation and monitoring with the hospital and manufacturer. Do not prescribe a device change solely from a generic risk score.

04

Use current Japanese guidance

MHLW lists version 7.0 of its medical information system safety-management guidance, issued in June 2026. PMDA’s notice collection includes a September 2026 revision of medical-device cybersecurity guidance for healthcare institutions. Confirm which documents and responsibilities apply to the specific hospital, device and service. A product purchase or an overseas certification does not establish compliance with all Japanese requirements.

Sources and further reading

// Key Takeaways

What to remember

  • Agree evaluation work with the clinical and equipment owners.
  • Validate device identity and findings before planning changes.
  • Check current MHLW and PMDA guidance for the actual scope.

// FAQ

Frequently asked questions

Q1

Can a security vendor promise a scan will have no clinical impact?

No. The hospital and equipment manufacturer must assess the actual method, model, configuration and operating conditions. Agree scope and approval before testing.

Q2

Does a protocol fingerprint prove a device’s model and firmware?

Not necessarily. Validate it against maintenance or other trusted records and retain uncertainty. A risk match depends on the identity information being applicable.

Last updated:

Plan a device security proposal for Japan’s healthcare organisations.

Discuss the medical equipment your product can identify and the evidence it returns. StrategyCore can coordinate Japanese discussions with healthcare prospects and delivery partners, including data collection limits, licensing and vendor escalation.