MDS2 (Medical Device)
Data protection, connectivity and service capabilities (2.3.8, 2.3.9, 2.3.11, 2.3.13, 2.3.14, 2.3.16, 2.3.21 to 2.3.25) – MDS2 (Medical Device)

MDS2 (Medical Device) TXCF: Transmission confidentiality: disclose cabling, encryption in transit, destination limits, authenticated connections and secure protocols

What does TXCF require?

Discloses the device's ability to keep transmitted PII confidential: whether PII can be transmitted only over point-to-point dedicated cables, meaning cabling not accessible to the public, inside a physically controlled room or building (TXCF-1); whether PII is encrypted before transmission over a network or removable media, with the standards noted (TXCF-2), and whether customers can configure encryption where it is not on by default (2.1); whether PII can only be sent to a fixed set of network destinations, meaning an explicit per-device mechanism limiting connections and their nature (TXCF-3); whether connections are limited to authenticated systems, with how the limit is achieved and which access-management methods are supported (TXCF-4); and whether secure transmission methods are supported or implemented for DICOM, HL7 or IEEE 11073 (TXCF-5).

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Other controls in Data protection, connectivity and service capabilities (2.3.8, 2.3.9, 2.3.11, 2.3.13, 2.3.14, 2.3.16, 2.3.21 to 2.3.25) – MDS2 (Medical Device)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.