<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CASE SENSITIVITY in SAS Health and Life Sciences</title>
    <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/CASE-SENSITIVITY/m-p/24903#M1048</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See e.g., SDTM IG v3.1.2 on page 35:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"4.1.3.2 CONTROLLED TERMINOLOGY TEXT CASE &lt;/P&gt;&lt;P&gt;It is recommended that controlled terminology be submitted in upper case text for all cases other than those &lt;/P&gt;&lt;P&gt;described as exceptions below. Deviations to this rule should be described in the define.xml. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a.&amp;nbsp; If the external reference for the controlled terminology is not in upper case then the data should &lt;/P&gt;&lt;P&gt;conform to the case prescribed in the external reference (e.g., MedDRA and LOINC). &lt;/P&gt;&lt;P&gt;b.&amp;nbsp; Units, which are considered symbols rather than abbreviated text (e.g., mg/dL). "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Sergiy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Mar 2013 19:35:40 GMT</pubDate>
    <dc:creator>Sergiy</dc:creator>
    <dc:date>2013-03-08T19:35:40Z</dc:date>
    <item>
      <title>CASE SENSITIVITY</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/CASE-SENSITIVITY/m-p/24902#M1047</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;When i put a SDTM domain through the open CDISC validator, it gives me a warning that the value of a pirticular variable lets say AESEV not found in controlled terminology. But the value actually is present in controlled terminology except that its all UPPER CASE. For example the value of AESEV in the domain is 'Moderate' instead of 'MODERATE' as in Controlled Terminology. Now i can convert the value to uppercase which is not an issue for me. But Will the FDA accept if i dont change it to uppercase and leave it just like that. It just looks better. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Jul 2011 17:47:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/CASE-SENSITIVITY/m-p/24902#M1047</guid>
      <dc:creator>tejabn</dc:creator>
      <dc:date>2011-07-01T17:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: CASE SENSITIVITY</title>
      <link>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/CASE-SENSITIVITY/m-p/24903#M1048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See e.g., SDTM IG v3.1.2 on page 35:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"4.1.3.2 CONTROLLED TERMINOLOGY TEXT CASE &lt;/P&gt;&lt;P&gt;It is recommended that controlled terminology be submitted in upper case text for all cases other than those &lt;/P&gt;&lt;P&gt;described as exceptions below. Deviations to this rule should be described in the define.xml. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a.&amp;nbsp; If the external reference for the controlled terminology is not in upper case then the data should &lt;/P&gt;&lt;P&gt;conform to the case prescribed in the external reference (e.g., MedDRA and LOINC). &lt;/P&gt;&lt;P&gt;b.&amp;nbsp; Units, which are considered symbols rather than abbreviated text (e.g., mg/dL). "&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Sergiy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2013 19:35:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Health-and-Life-Sciences/CASE-SENSITIVITY/m-p/24903#M1048</guid>
      <dc:creator>Sergiy</dc:creator>
      <dc:date>2013-03-08T19:35:40Z</dc:date>
    </item>
  </channel>
</rss>

