Hospital security questionnaires for imaging vendors

  • Hospitals use security questionnaires to understand a product before connecting it to their network.
  • MDS2 is a medical-device security disclosure worksheet, not a universal questionnaire or legal approval.
  • Imaging-specific MDS2 questions cover DICOM transmission, de-identification, data at rest, and software bills of materials.
  • A maintained answer set helps you respond consistently, but each hospital can ask for more detail.

A hospital security questionnaire asks how a software vendor protects data and access before a product connects to the hospital network. For imaging vendors, the MDS2 worksheet can help answer device-security questions, but each hospital may also use its own form.

This is engineering orientation, not legal advice; a hospital’s security and privacy staff, or your adviser, decides what applies to a specific product.

What is a hospital vendor security questionnaire?

A hospital vendor security questionnaire is a risk-review tool, not a universal certification. The hospital’s security team uses it to understand how your product handles information, access, and connections before approving an integration.

There is no single form every hospital must use. You may receive a hospital’s spreadsheet, a procurement portal, the MDS2 worksheet, or a mix. The questions can cover your product, your company, and services that handle data for you.

This review is normal work in a hospital integration. The hospital needs enough detail to assess its own environment. Your job is to answer for the product you actually ship, not the product you plan to build.

Do not treat every question as a request for a policy document. Some ask about product behavior; others ask for company-level practices or evidence. If you do not know which meaning the reviewer intends, ask before choosing an answer.

What is the MDS2 form, and does it apply to your software?

The MDS2 form is a medical-device security disclosure worksheet that helps hospital professionals assess a device’s security capabilities. Its full name is Manufacturer Disclosure Statement for Medical Device Security, and FDA lists ANSI/NEMA HN 1-2019 as a recognized consensus standard.

The FDA record says MDS2 information is intended to assist professionals who conduct security risk assessments. It also warns that the information may be inappropriate for other purposes. FDA notes that MDS2 conformance may not satisfy all cybersecurity requirements under section 524B of the FD&C Act.

The NEMA worksheet asks for details such as the device model and its intended use in a network-connected environment. Its answer options are Yes, No, N/A, or See Note, with a note number for added detail. The form is written for medical devices. A hospital may still ask a software-only vendor to complete it, but that request does not make the form a legal requirement for every software product.

Whether your software is a medical device is a separate question. Our guide to whether cloud software qualifies as a medical device explains the factors to review with your adviser.

What security questions do imaging products get asked?

The MDS2 worksheet includes questions about data handling, authentication, transmission, and maintenance. Several are directly relevant to medical imaging software.

For example, the worksheet asks whether a device can encrypt data at rest, supports secure transmission methods such as DICOM, and supports DICOM de-identification profiles. It also asks whether personally identifiable information crosses an external network, whether a software bill of materials is available, and whether the manufacturer has a vulnerability disclosure program.

For a DICOM transport question, name the capability and standard that apply to your product. DICOM PS3.15 Section B.12 says servers and clients shall support TLS 1.2 and may support TLS 1.3. A general answer such as “yes, we use encryption” gives a reviewer less useful information than identifying the relevant profile and product configuration.

Authentication questions need the same care. A network connection protected by mutual TLS is different from a user login to your application. Our guide to mutual TLS for DICOM connections explains the transport layer; your application still needs its own accurate access-control answers.

Questions about software bills of materials and vulnerability reporting are part of a broader product-security process. See our overview of medical-device cybersecurity and vulnerability handling. NIST SP 800-66 Rev. 2 is a separate resource for understanding the HIPAA Security Rule; an MDS2 answer does not determine your legal role or obligations.

How do you answer a hospital questionnaire once and reuse the answers?

Use the MDS2 worksheet as a master list, answer it for your own product, and map each hospital’s questions to those answers. That is more useful than starting from a blank spreadsheet for every review.

Start with the exact product name, version, and use case under review. Then assign each question to someone who can verify the answer: for example, the engineer responsible for the feature or the person who owns the relevant company process. If the answer depends on a deployment choice, record that condition instead of giving a general Yes.

Use the note field to explain answers that need context. A short “See Note” is not enough on its own; say what the product does and what the customer must configure, where the question allows that explanation. Do not mark a feature Yes because it appears on a roadmap.

I would keep one reviewed answer set and map custom forms to it. A clear No with a reason is better than a vague Yes. Keep a named owner and review the answers when the product, its hosting, or a third-party service changes.

This approach has a limit: it does not make every hospital accept the same evidence. A reviewer may ask follow-up questions, request documents, or use terms that need clarification. Answers also go stale, so give the file a review date and make corrections when the product changes.

How do third-party services change your answers?

Be prepared to describe the parts of your service that handle hospital data, including third-party services. A hospital may ask who receives data, where it is stored, and which party is responsible for each step.

Do not answer only for the application your team writes. Map the data path in plain language, then check each provider’s public security information and contract. For HIPAA questions, NIST SP 800-66 Rev. 2 gives practical guidance on the Security Rule, but a lawyer or privacy lead should decide how it applies to your service.

Our guide to zero-retention DICOM pipelines explains how storage choices change the questions about imaging data.

If you use a managed DICOM gateway, the hospital may ask about that provider too. Dicomly states that DICOM bytes are not written to disk, a queue, or a cache; see its public security page. That statement covers the connectivity service only. You still need to describe your application and other providers, and a hospital may review the gateway separately.

This boundary is useful. Your team can focus its engineering effort on the imaging product, while still giving the hospital a clear account of the services around it.

What can you do today?

NEMA publishes the MDS2 worksheet for download, so you can begin by answering questions about your own product. Mark every answer you cannot verify, then ask the right owner before you send the form back.

For imaging-specific questions, review the DICOM TLS profile in PS3.15 Section B.12 alongside your actual product settings. A short, honest answer set gives you a useful starting point for the next hospital review.

Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →

Sources

  1. FDA Recognized Consensus Standards: ANSI/NEMA HN 1-2019 (www.accessdata.fda.gov)
  2. NEMA MDS2 Worksheet (www.nema.org)
  3. DICOM PS3.15, Section B.12: TLS Secure Transport Connection Profile (dicom.nema.org)
  4. NIST SP 800-66 Rev. 2: HIPAA Security Rule Resource Guide (csrc.nist.gov)

Start receiving DICOM today.

Early access. No credit card. First endpoint free.