<?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: Need Guidance: AEOUT for Split AEs When Severity Increases in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Need-Guidance-AEOUT-for-Split-AEs-When-Severity-Increases/m-p/969126#M376757</link>
    <description>&lt;P&gt;Please check internally if you can mention about episodic nature of event and hence AEOUT value is "not recovered" and as the nature is episodic AEENDTC&amp;nbsp; becomes not applicable.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Jun 2025 14:09:10 GMT</pubDate>
    <dc:creator>cherryblossom</dc:creator>
    <dc:date>2025-06-16T14:09:10Z</dc:date>
    <item>
      <title>Need Guidance: AEOUT for Split AEs When Severity Increases</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Need-Guidance-AEOUT-for-Split-AEs-When-Severity-Increases/m-p/969084#M376725</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm working on SDTM AE data, and we have a case where a single adverse event (e.g., headache) increases in severity and later becomes serious. As per CDISC and FDA guidance, we're splitting this into multiple AE records using &lt;CODE&gt;AELINKID&lt;/CODE&gt;.&lt;/P&gt;&lt;P&gt;The issue we're debating is what to use for &lt;STRONG&gt;&lt;CODE&gt;AEOUT&lt;/CODE&gt;&lt;/STRONG&gt; in the intermediate records. Technically, the AE isn't "recovered" at that point — it's just getting worse. But if we set &lt;CODE&gt;AEOUT = "Not recovered/Not resolved"&lt;/CODE&gt; and still provide an &lt;CODE&gt;AEENDTC&lt;/CODE&gt;, it triggers &lt;STRONG&gt;FDA validation rule SD1332&lt;/STRONG&gt;, which flags this combination as invalid.&lt;/P&gt;&lt;P&gt;So the question is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;How should we populate &lt;CODE&gt;AEOUT&lt;/CODE&gt; in intermediate split records when the AE hasn't truly resolved, but we need to avoid the SD1332 validation error?&lt;/P&gt;&lt;P&gt;Are we supposed to use &lt;CODE&gt;"Recovered/Resolved"&lt;/CODE&gt; just to avoid the rule, even if clinically it feels inaccurate?&lt;/P&gt;&lt;P&gt;Appreciate any thoughts or examples of how others are handling this.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2025 04:38:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Need-Guidance-AEOUT-for-Split-AEs-When-Severity-Increases/m-p/969084#M376725</guid>
      <dc:creator>amiteshm</dc:creator>
      <dc:date>2025-06-16T04:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: Need Guidance: AEOUT for Split AEs When Severity Increases</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Need-Guidance-AEOUT-for-Split-AEs-When-Severity-Increases/m-p/969126#M376757</link>
      <description>&lt;P&gt;Please check internally if you can mention about episodic nature of event and hence AEOUT value is "not recovered" and as the nature is episodic AEENDTC&amp;nbsp; becomes not applicable.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2025 14:09:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Need-Guidance-AEOUT-for-Split-AEs-When-Severity-Increases/m-p/969126#M376757</guid>
      <dc:creator>cherryblossom</dc:creator>
      <dc:date>2025-06-16T14:09:10Z</dc:date>
    </item>
  </channel>
</rss>

