<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments for The eCTD summit</title>
	<atom:link href="http://theectdsummit.com/summit/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://theectdsummit.com/summit</link>
	<description></description>
	<pubDate>Thu, 09 Sep 2010 11:35:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Update to Study Tagging File valid-values: What Does It Mean? by News Roundup Part 1: Agency News &#171; The eCTD summit</title>
		<link>http://theectdsummit.com/summit/?p=841&cpage=1#comment-289</link>
		<dc:creator>News Roundup Part 1: Agency News &#171; The eCTD summit</dc:creator>
		<pubDate>Thu, 12 Aug 2010 15:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=841#comment-289</guid>
		<description>[...] issued a new valid-values.xml for study tagging files see my Blog Post on The eCTD Summit for [...]</description>
		<content:encoded><![CDATA[<p>[...] issued a new valid-values.xml for study tagging files see my Blog Post on The eCTD Summit for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Top FDA Processing Issues with eCTD: A Recent Update by Bookmarks &#8211; Collapsed or Expanded? &#124; Ask Cato</title>
		<link>http://theectdsummit.com/summit/?p=806&cpage=1#comment-288</link>
		<dc:creator>Bookmarks &#8211; Collapsed or Expanded? &#124; Ask Cato</dc:creator>
		<pubDate>Tue, 10 Aug 2010 14:02:27 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=806#comment-288</guid>
		<description>[...] Top FDA Processing Issues with eCTD: A Recent Update (theectdsummit.com) [...]</description>
		<content:encoded><![CDATA[<p>[...] Top FDA Processing Issues with eCTD: A Recent Update (theectdsummit.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updated Study Data Specifications and the eCTD Dataset Problem by Kathie Clark</title>
		<link>http://theectdsummit.com/summit/?p=788&cpage=1#comment-280</link>
		<dc:creator>Kathie Clark</dc:creator>
		<pubDate>Mon, 19 Jul 2010 13:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=788#comment-280</guid>
		<description>Mallikaarjunan, I  have been waiting for the ICH to update the valid-values.xml to answer this question - see my latest post for the answer. http://theectdsummit.com/summit/?p=841</description>
		<content:encoded><![CDATA[<p>Mallikaarjunan, I  have been waiting for the ICH to update the valid-values.xml to answer this question - see my latest post for the answer. <a href="http://theectdsummit.com/summit/?p=841" rel="nofollow">http://theectdsummit.com/summit/?p=841</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updated Study Data Specifications and the eCTD Dataset Problem by Update to Study Tagging File valid-values: What Does It Mean? &#171; The eCTD summit</title>
		<link>http://theectdsummit.com/summit/?p=788&cpage=1#comment-279</link>
		<dc:creator>Update to Study Tagging File valid-values: What Does It Mean? &#171; The eCTD summit</dc:creator>
		<pubDate>Mon, 19 Jul 2010 13:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=788#comment-279</guid>
		<description>[...] Does It Mean?  posted by Kathie Clark @ 6:01 PM   Monday, July 19, 2010     As I discussed in my previous post, FDA issued version 1.5.1 of Study Data Specifications in January of 2010.  Although the changes [...]</description>
		<content:encoded><![CDATA[<p>[...] Does It Mean?  posted by Kathie Clark @ 6:01 PM   Monday, July 19, 2010     As I discussed in my previous post, FDA issued version 1.5.1 of Study Data Specifications in January of 2010.  Although the changes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updated Study Data Specifications and the eCTD Dataset Problem by mallikaarjunan</title>
		<link>http://theectdsummit.com/summit/?p=788&cpage=1#comment-273</link>
		<dc:creator>mallikaarjunan</dc:creator>
		<pubDate>Mon, 31 May 2010 10:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=788#comment-273</guid>
		<description>Thanks for this Information. I have a question on this.

For creating sub folders for datasets under analysis and legacy, sdtm under tabulation--- what will be the document file tag?

Thanks
Malli</description>
		<content:encoded><![CDATA[<p>Thanks for this Information. I have a question on this.</p>
<p>For creating sub folders for datasets under analysis and legacy, sdtm under tabulation&#8212; what will be the document file tag?</p>
<p>Thanks<br />
Malli</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a porp?  How RPS XML is different (and scarier) than eCTD by joelfinkle</title>
		<link>http://theectdsummit.com/summit/?p=828&cpage=1#comment-270</link>
		<dc:creator>joelfinkle</dc:creator>
		<pubDate>Fri, 28 May 2010 13:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=828#comment-270</guid>
		<description>Sorry -- hit the enter too soon.  What you left out is that the PORP is the top-level XML object in an RPS file, or more exactly, </description>
		<content:encoded><![CDATA[<p>Sorry &#8212; hit the enter too soon.  What you left out is that the PORP is the top-level XML object in an RPS file, or more exactly,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is a porp?  How RPS XML is different (and scarier) than eCTD by joelfinkle</title>
		<link>http://theectdsummit.com/summit/?p=828&cpage=1#comment-269</link>
		<dc:creator>joelfinkle</dc:creator>
		<pubDate>Fri, 28 May 2010 13:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=828#comment-269</guid>
		<description>Kathie,
Nice basics article on RPS's guts... but still, what's a PORP?

I'm pretty sure the "RP" stands for Regulated Product... but much of HL7's naming is pretty opaque.</description>
		<content:encoded><![CDATA[<p>Kathie,<br />
Nice basics article on RPS&#8217;s guts&#8230; but still, what&#8217;s a PORP?</p>
<p>I&#8217;m pretty sure the &#8220;RP&#8221; stands for Regulated Product&#8230; but much of HL7&#8217;s naming is pretty opaque.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updated Study Data Specifications and the eCTD Dataset Problem by Evan Richardson</title>
		<link>http://theectdsummit.com/summit/?p=788&cpage=1#comment-268</link>
		<dc:creator>Evan Richardson</dc:creator>
		<pubDate>Mon, 03 May 2010 14:07:52 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=788#comment-268</guid>
		<description>Thanks for this information Kathie.  I suspect that many of us will go with the 1st and 3rd options you've presented.  We'll look to our publishing software vendors to provided updates, and then be forced to go through the re-validation process.  In the meantime, we'll likely need to ask the FDA for a waiver.</description>
		<content:encoded><![CDATA[<p>Thanks for this information Kathie.  I suspect that many of us will go with the 1st and 3rd options you&#8217;ve presented.  We&#8217;ll look to our publishing software vendors to provided updates, and then be forced to go through the re-validation process.  In the meantime, we&#8217;ll likely need to ask the FDA for a waiver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Structuring of Clinical Study Reports: Common Practices, Good Practices by montelevinson</title>
		<link>http://theectdsummit.com/summit/?p=767&cpage=1#comment-267</link>
		<dc:creator>montelevinson</dc:creator>
		<pubDate>Wed, 28 Apr 2010 23:27:18 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=767#comment-267</guid>
		<description>There's one important caveat to Joel's comment, above.  For granular reports it's highly advantageous to follow the E3 guidance numbering in section 16 of the CSR, which includes all the appendices

When you submit the CSR, each appendix gets attached to the eCTD backbone as a separate file.  Using the E3 numbering in the file name will make it **much** easier to find the correct spot to attach the file in your publishing software.  

Putting the section number in the document (in the header, for example) will make it easier to QC the submission.

Whatever you do, don't change the numbering in section 16.  If you don't have a particular appendix in your study report just skip that number.</description>
		<content:encoded><![CDATA[<p>There&#8217;s one important caveat to Joel&#8217;s comment, above.  For granular reports it&#8217;s highly advantageous to follow the E3 guidance numbering in section 16 of the CSR, which includes all the appendices</p>
<p>When you submit the CSR, each appendix gets attached to the eCTD backbone as a separate file.  Using the E3 numbering in the file name will make it **much** easier to find the correct spot to attach the file in your publishing software.  </p>
<p>Putting the section number in the document (in the header, for example) will make it easier to QC the submission.</p>
<p>Whatever you do, don&#8217;t change the numbering in section 16.  If you don&#8217;t have a particular appendix in your study report just skip that number.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Structuring of Clinical Study Reports: Common Practices, Good Practices by joelfinkle</title>
		<link>http://theectdsummit.com/summit/?p=767&cpage=1#comment-266</link>
		<dc:creator>joelfinkle</dc:creator>
		<pubDate>Wed, 14 Apr 2010 01:28:12 +0000</pubDate>
		<guid isPermaLink="false">http://theectdsummit.com/summit/?p=767#comment-266</guid>
		<description>While you're discussing the CSR... my little Public Service Announcement is that you do NOT need to number the sections of the report with the same section numbers as the ICH E2 guidance.

Really.

I mean it.

Take a look at the guidance.  It doesn't have anything about the numbering in the document, only the *sections of the guidance* are numbered.

So go ahead, do something rational and number your document with "1" at the body.  Don't number your title, synopsis, or TOC.

FDA has never, ever, ever, rejected a CSR because of the TOC numbering. Nor has any of the EMA agencies, Japan, or anybody else, to my knowledge.</description>
		<content:encoded><![CDATA[<p>While you&#8217;re discussing the CSR&#8230; my little Public Service Announcement is that you do NOT need to number the sections of the report with the same section numbers as the ICH E2 guidance.</p>
<p>Really.</p>
<p>I mean it.</p>
<p>Take a look at the guidance.  It doesn&#8217;t have anything about the numbering in the document, only the *sections of the guidance* are numbered.</p>
<p>So go ahead, do something rational and number your document with &#8220;1&#8243; at the body.  Don&#8217;t number your title, synopsis, or TOC.</p>
<p>FDA has never, ever, ever, rejected a CSR because of the TOC numbering. Nor has any of the EMA agencies, Japan, or anybody else, to my knowledge.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
