DICOM Conformance Statement - InCenter - Philips
DICOM Conformance Statement - InCenter - Philips
DICOM Conformance Statement - InCenter - Philips
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
7. SECURITY<br />
7.1. Security Profiles<br />
Not applicable.<br />
7.1.1. Security use Profiles<br />
Not applicable<br />
<strong>DICOM</strong> <strong>Conformance</strong> <strong>Statement</strong> Page 57 of 78<br />
7.1.2. Security Transport Connection Profiles<br />
Eleva AE conforms to the Basic TLS Secure Transport Connection Profile.<br />
Since Eleva AE acts only as SCU (except Verify) no IP port is specified to accept TLS<br />
connections.<br />
Eleva AE provides a service accessible tool to configure private keys and certificates<br />
of the local and remote <strong>DICOM</strong> nodes.<br />
7.1.3. Digital Signature Profiles<br />
Not applicable<br />
7.1.4. Media Storage Security Profiles<br />
Not applicable<br />
7.1.5. Attribute Confidentiality Profiles<br />
Not applicable<br />
7.1.6. Network Address Management Profiles<br />
Not applicable<br />
7.1.7. Time Synchronization Profiles<br />
Not applicable<br />
7.1.8. Application Configuration Management Profiles<br />
Eleva AE conforms to the Basic Application Level Confidentiality Profile as deidentifier.<br />
De-identified SOP Instances will be created on <strong>DICOM</strong> Media if specified by the user.<br />
No instances of the Encrypted Attributes Data Set are created. No Transfer Syntaxes<br />
are supported for encoding/decoding of Encrypted Attributes Data Sets.<br />
7.1.9. Audit Trail Profiles<br />
Not applicable<br />
© Koninklijke <strong>Philips</strong> Electronics N.V.<br />
Document Number: XPR 031-090167.00 MammoDiagnost DR 1.0 18-March-2009
Change language