releasenotes_2020a

2020/01/22​

The following changes have been made relative to the previously published PS3 2019e release of the standard, by incorporating the​ changes specified in the supplements and correction items.​

The Final Text of all applied Supplements and Correction Proposals is available at ftp://medical.nema.org/medical/dicom/final/​

Production Notes​

The DocBook XML files are the source format, and all other formats are rendered from it.​

The PDF format is rendered from the DocBook XML, and remains the "official" (authoritative) form of the standard. The PDF contains​ hyperlinks to sections, figures and tables both within and between parts (which in the latter case work if you are reading the PDF in​ a tool that supports linking to other parts).​

The two HTML formats are provided for the convenience of those who find them easier to navigate within a browser, and though the​ appearance and organization is different, the content is the same. One form consists of entire parts in one very large HTML page,​ andtheotherconsistofchunksofsectionswithnavigationelements.Bothformsarehyper-linkedwithinandbetweenparts.Thefigures​ in the HTML are SVG, so a browser that supports SVG is required (most contemporary browsers do).​

All paragraphs (<p/> elements) in the HTML files of this release, are uniquely identified with a hypertext anchor (<a/> element), each​ of which has an id attribute (derived from the source DocBook <para/> element xml:id attribute). These unique identifiers will remain​ stable in subsequent releases, so they may be reliably used as the persistent targets of hyperlinks relative to the current release base​ URL, and are more specific than the existing anchors for entire sections or tables. Unlike the section and table anchors, there is no​ semanticsignificancetothesyntaxoftheidentifiers(i.e.,theyareUUIDs,ratherthanbeingderivedfromthesectionortablenumbering​ pattern).Subsequentreleaseswilladdnewidentifiersfornewparagraphsandtextsplitoutofexistingparagraphsintonewparagraphs,​ and will, if possible, empty, rather than entirely remove, existing paragraphs that are retired (in order to avoid dead links).​

The chunked HTML format includes navigation elements in the header and footer, as well as a hyperlink to the current release of that​ page, in case the user happens to find or be using an older release of the page.​

The DOCX (for Word) and ODT (for OpenOffice or LibreOffice) formats are provided for the convenience of future Supplement and​ CPeditors.Theirmainclaimtofameisthattheyexistatall,andthoughtheyareviewableandeditable,theyarelackingmanyfeatures​ of the Word source of previous release, for example the use of styles for section headings. They do contain embedded hyperlinks,​ and these are also present in the table of contents, even though the page numbers rendered in the table of contents may be mean-​ ingless. To reiterate, the intent of these files is to provide a source to cut and past into new Word documents, and not to be functional​ documents in their own right. Since Word does not support SVG, all figures embedded in the DOCX files have been rasterized to a​ fixed resolution and are adequate for position only and are not editable and are not intended to be a substitute for the SVG figures.​

The rendering pipeline used to produce these files is available but requires some expertise to use it. It is not supported. To achieve​ quality rendering, the use of some commercial tools was necessary, to supplement the many open source tools that were also used.​ Oxygen (commercial) was used as the XML editor since it supports a WYSIWG authoring mode. OpenOffice (open source) was used​ as the equation editor. The DocBook (open source, version docbook-xsl-ns-1.78.1) style sheets were used to create the HTML and​ intermediate FO form used to created the PDF and DOCX. MathML equations were converted to SVG using pMML2SVG (open​ source, version pMML2SVG-0.8.5). RenderX XEP (commercial) was used to produce the PDF, and XMLmind FO-Converter (com-​ mercial) was used to produce the DOCX. The difference files were produced using DeltaXML DocBook Compare (commercial). The​ PDF files were post-processed with qpdf to generate object streams to reduce the size of the tagged PDF and improve searching for​ strings that span lines within tables and to linearize the files for streamed web page viewing.​

Some characteristics of the DocBook XML may be of interest to those performing automated processing or extraction:​

•​Zero width spaces (U+200B) are used in some places to allow long words (such as PS3.6 keywords and UIDs) to break within table​ columns and avoid tables becoming too wide to fit on a page. These need to be filtered out before using these words literally.​

•​Enumerated values and defined terms are formalized in PS3.3 as DocBook variablelist elements with a title identifying them as​ such, to facilitate their automated detection and extraction.​

•​Template and context group tables in PS 3.16 are preceded by variablelist elements defining whether or not they are extensible,​ etc., again to enable automated extraction.​

- Standard -​

•​Hyperlinks(xrefandlinkelements)areusedextensivelybutmayobscuretheidentifierofwhatisbeinglinkedtofromtheperspective​ of automated extraction. It may be useful to consult the olink targetdb files that are included in the package to "look up" the target​ of such links, rather than reinventing this mechanism, which is used by the DocBook stylesheets for cross-document linking. E.g.,​ one can look up "sect_TID_300" in "output/html/targetdb/PS3_16_target.db" to determine that it has a "number" of "TID 300" and​ a "ttl" of "Measurement", etc.​

Changes to Parts​

General Changes​

•​

PS3.1​

PS3.2​

•​Correct links to PS3.18 section targets changed by Sup 183.​

•​Correct links to Sup 202 RTV figures.​

•​Sup 176​

•​Sup 208​

PS3.3​

•​Correct name of Multi-energy CT Processing Macro Attributes table and use of th rather than td in tbody of Multi-energy CT X-Ray​ Detector Macro​

•​Add line breaks in failure reason code descriptions in C.14.1.1​

Add Frame of Reference Module for RTSS IOD in Overview table to match IOD.​

•​Correct tag for Applicable Safety Standard Description in Specific Absorption Rate Definition.​

•​Make IOD section names consistent with SOP Class names (cf. PS3.4 Table B.5-1).​

•​CP 1931​

•​CP 1932​

•​CP 1947​

•​CP 1949​

•​Sup 176​

•​Sup 208​

PS3.4​

•​Fix incorrect form of some DateTime attributes​

•​CP 1479​

•​CP 1954​

•​Sup 208​

PS3.5​

•​CP 1943​

- Standard -​

•​CP 1947​

PS3.6​

•​CP 1933​

•​CP 1945​

•​Sup 176​

•​Sup 208​

PS3.7​

•​CP 1954​

PS3.8​

PS3.10​

•​CP 1948​

PS3.11​

PS3.12​

PS3.14​

PS3.15​

•​Correct tag for known safe Elscint Acquisition Duration element​ •​CP 1928​

•​CP 1942​ •​CP 1946​

PS3.16​

•​Remove spurious "no purpose of reference"​

•​Correct SCOORD row number reference in content item description for TID 1406​

•​Clean up and hyperlink notes about incorrect codes in prior context group versions and update replacements with SCT rather than​ SRT (to be consistent with CP 1850 approach).​

•​CP 1929​ •​CP 1930​ •​CP 1931​ •​CP 1933​ •​CP 1935​ •​CP 1936​ •​CP 1937 (FT2)​ •​CP 1941​

- Standard -​

•​CP 1945​

•​CP 1952​

•​CP 1953​

•​Sup 176​

•​Sup 208​

PS3.17​

•​CP 1937​

•​CP 1938​

•​CP 1939​

•​CP 1940​

•​CP 1941​

•​Sup 208​

PS3.18​

•​CP 1861​ •​CP 1862​ •​CP 1889​ •​CP 1919​ •​CP 1920​ •​CP 1924​ •​CP 1925​ •​CP 1948​

PS3.19​

•​Correct formatting of soap xml element in WSDL​ •​CP 1889​

•​CP 1920​ •​CP 1922​

PS3.20​

PS3.21​

PS3.22​

Supplements Incorporated​

Sup 176​ Second Generation Radiotherapy – Tomotherapeutic and Robotic-Arm Treatment Modalities​

- Standard -​

Sup 208​ DICOM Encapsulation of OBJ Models for 3D Manufacturing and Virtual Reality​

Correction Items Incorporated​

CP 1479​ Update PS3.4 for expanded Code Sequence​

CP 1861​ Consistency between DICOM VR definition of DS & IS, and JSON Value Representation​

CP 1862​ Necessity of returning the Specific Character Set (0008,0005) attribute in a QIDO-RS response​

CP 1889​ Recently added OV, SV and UV VRs were not included in PS3.18 or PS3.19.​

CP 1919​ Clarify the Media Type sections for Studies Service​

CP 1920​ Padding in DICOM JSON and XML (Native) Models​

CP 1922​ Update PS3.19 WADO-RS and STOW-RS to PS3.18 Studies Service Retrieve and Store​

CP 1924​ PS3.18 Section 5.1.1 does not have a definition for NON-ZERO-DIGIT​

CP 1925​ PS3.18 Section 8.3.1 has syntax mistakes​

CP 1928​ Add multi-energy CT attributes to de-identification profile​

CP 1929​ Add precoordinated measurement CODE content item parameter to TID 300​

CP 1930​ Erectile dysfunction test drug administration​

CP 1931​ SCOORD3D should be allowed for Planar ROIs in TID 1411 and be more flexible for Volumetric ROIs in TID 1410​

CP 1932​ Add Series Date and Time to missing Modules​

CP 1933​ Add PIRADS V2.1 base PZpm sector anatomy​

CP 1935​ Correction of child node relation to parent node within part 16, TID 11005​

CP 1936​ Correction of "Adverse Event" child node relation to parent node within TID 11021 and 11022​

CP 1937​ Extend semantic of TID 11003 to be more flexible to the needs and correct node numbering in example (FT2)​

CP 1938​ Inconsistent representation of CODE values within example MMMM.1 in part 17​

CP 1939​ Semantic issue in consumable parts​

CP 1940​ Correction of an incorrect datetime value​

CP 1941​ ChangenameofTID11003forbettercomprehensibilityincontextwithchangesofCP-1937inthecasesofnon-automated​

administration​

CP 1942​ DDNS/DHCP updates​

CP 1943​ Incorrect Frame Time's value for Video Type 60 Hz HD​

CP 1945​ Add coding scheme designator for RadElement​

CP 1946​ Update Part 15 Annex H (add conformance)​

CP 1947​ Add security considerations for encapsulated formats​

CP 1948​ Part 10 Format security considerations​

CP 1949​ Specify the identity window level values​

CP 1952​ Remove common name from taxonomic rank code meanings​

- Standard -​

CP 1953​ Add more specific tumor graft histologic types​

CP 1954​ Fix inconsistent DIMSE status code meaning​

- Standard -​