syngo® MR B17 DICOM Conformance Statement - Siemens ...

More documents

Recommendations

Info

Ssyngo MR B17DICOM Conformance StatementTransfer Syntax Selection PoliciesThe syngo MR product DICOM application currently supports• the Implicit VR Little Endian, the Explicit VR Little Endian and Explicit VR Big Endian TransferSyntaxes• the JPEG Lossless Non-hierarchical Transfer Syntax• the JPEG Baseline and JPEG Extended Transfer Syntaxes (JPEG Lossy).• the RLE Lossless Transfer Syntax• the JPEG 2000 Lossless and Lossy Transfer SyntaxAny proposed presentation context including one of these Transfer Syntaxes will be accepted.Any proposed presentation context that does not include one of these Transfer Syntaxes willbe rejected.The order of preference in accepting Transfer Syntaxes within Presentation Contexts orPresentation Contexts with single Transfer Syntaxes is:1. JPEG Lossy Extended2. JPEG Lossless non-hierarchical3. JPEG Lossy Baseline4. RLE Lossless5. Explicit VR Little Endian6. Explicit VR Big Endian7. Implicit VR Little Endian8. JPEG 2000 Lossy9. JPEG 2000 LosslessWith RLE Lossless, JPEG 2000 Lossy and JPEG 2000 Lossless Transfer Syntax the syngoMR product DICOM application will decompress the image before storing it into the database.With Implicit VR Little Endian Transfer Syntax the syngo MR product DICOM application willremove any Private Attributes not known to the application. Decision on removal of a PrivateElement is done if there is NO entry in the attribute-dictionary of the syngo MR productDICOM application.Therefore any Explicit VR Transfer Syntax shall preferably be used by the Storage SCU’swhen sending Composite Image Instances to the syngo MR product DICOM application.© Siemens AG, Healthcare, 2009 Rev. 9.0 Page 30 of 149
Ssyngo MR B17DICOM Conformance Statement6 Implementation Model Storage CommitmentThe Storage Commitment service class defines an application-level class of service whichfacilitates the commitment to storage. It performs an additional task of commitment ofcomposite objects apart from the network based storage of images as defined by the StorageService class. The syngo MR product DICOM implementation supports the StorageCommitment Push Model as SCU and SCP.6.1 Application Data Flow DiagramThe syngo MR product DICOM network implementation acts as SCU/SCP for the StorageCommitment Push Model Service using the Storage Commitment Service Class. The producttarget Operating System is .JobcompletedDICOM Standard InterfaceUpdateFlagsStorageCommitment SCUDICOM ApplicationN-ACTIONN-EVENT-REPORTStorageCommitSCPData BaseStorageCommitment SCPDICOM ApplicationN-ACTIONN-EVENT-REPORTStorageCommitSCUFigure 3: Application Data Flow Diagram – Storage Commitment SCU/SCP6.2 Functional Definitions of Application EntitiesWith each successfully completed send job, the syngo MR product DICOM Application willcreate a Storage Commitment Push Model Identifier from the SOP Instances sent. Then an aStorage Commit Request is triggered. Depending on configuration, the syngo MR productDICOM application will keep the association open for responses with a configurable time-out,or closes the association and expects responses on a different association that has to beestablishes by the remote Storage Commitment SCP.The commitment status derived from the related trigger response will be indicated in therelated Status Flags of the related entity. It is possible to create triggers (“auto rules”) from thisevent.The Transaction UIDs of the pending commitment request are kept “open” for a configurableamount in time (default: 1h). If the “open time” for a pending commitment request has elapsedw/o a related response from the provider, the Transaction UID is removed and the relatedentities are indicated as “commit failed”.In any case, commitment will only be requested for previously and successfully sent images.© Siemens AG, Healthcare, 2009 Rev. 9.0 Page 31 of 149
Page 1 and 2: Siemenssyngo® MR B17XXXXXXXXXXXXxx
Page 3 and 4: Ssyngo MR B17DICOM Conformance Stat
Page 7: Ssyngo MR B17DICOM Conformance Stat
Page 81 and 82:
Ssyngo MR B17DICOM Conformance Stat
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
General Series ModuleAttribute Name
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
S• Inline-Processing:MIP_SAGMIP_C
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
show all

syngo® MR B17 DICOM Conformance Statement - Siemens ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?