CP-1701 Private Creator Data Elements only use Default Character Repertoire <informaltable rules="all" frame="box"> <tr> <td rowspan="1" colspan="1" valign="top"><para>Status</para></td> <td rowspan="1" colspan="1" valign="top"><para>Assigned</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Date of Last Update</para></td> <td rowspan="1" colspan="1" valign="top"><para>2017/03/26</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Person Assigned</para></td> <td rowspan="1" colspan="1" valign="top"><para>David Clunie</para><para><link xl:href="mailto:dclunie@dclunie.com"/></para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Submitter Name</para></td> <td rowspan="1" colspan="1" valign="top"><para>David Clunie</para><para><link xl:href="mailto:dclunie@dclunie.com"/></para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Submission Date</para></td> <td rowspan="1" colspan="1" valign="top"><para>2017/03/06</para></td> </tr> </informaltable> <informaltable rules="all" frame="box"> <tr> <td rowspan="1" colspan="1" valign="top"><para>Correction Number CP-1701</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Log Summary: Private Creator Data Elements only use Default Character Repertoire</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"> <para>Name of Standard</para> <para>PS3.5</para> </td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Rationale for Correction:</para> <para>All known implementations use only characters from the Default Character Repertoire as Private Creators, but in some documentation it was observed that special characters such as em dash rather than hyphens were being illustrated thanks to word processor auto-correction, potentially leading to interoperability failure if implemented literally. Accordingly, since there is no reason to permit Extended or Replacement Character Repertoires, forbid them.</para> </td> </tr> <tr> <td rowspan="1" colspan="1" valign="top">Correction Wording:</td> </tr> </informaltable> </chapter> <chapter> <title/> <informaltable rules="all" frame="box"> <tr> <td> <para><emphasis role="italic">Amend DICOM PS3.5 as follows (changes to existing text are bold and <emphasis role="bold"><emphasis role="underline">underlined</emphasis></emphasis> for additions and <emphasis role="bold"><emphasis role="strikethrough">struckthrough</emphasis></emphasis> for removals):</emphasis></para> </td> </tr> </informaltable> <section label="7.8.1" status="3" xml:id="sect_7.8.1"> <title>Private Data Element Tags It is possible that multiple implementers may define Private Elements with the same (odd) group number. To avoid conflicts, Private Elements shall be assigned Private Data Element Tags according to the following rules. Private Creator Data Elements numbered (gggg,0010-00FF) (gggg is odd) shall be used to reserve a block of Elements with Group Number gggg for use by an individual implementer. The implementer shall insert an identification code in the first unused (unassigned) Element in this series to reserve a block of Private Elements. The VR of the private identification code shall be LO (Long String) and the VM shall be equal to 1. A Private Creator identifier may be used only once within a Group; reserving multiple blocks of Elements in the same Group with the same identifier is not allowed.The Private Creator Data Elements shall only contain characters from the Default Character Repertoire and not an Extended or Replacement Character Repertoire, even though the LO VR is one that is affected by the Specific Character Set (0008,0005). If an implementer needs multiple repetitions of a private element, a private Sequence attribute (see ) may be used to contain these multiple items. An implementer may use the same Private Creator identifier for multiple Groups.