<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clovertech | Yutaka | Activity</title>
	<link>https://clovertech.infor.com/members/ohstaka/activity/</link>
	<atom:link href="https://clovertech.infor.com/members/ohstaka/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Yutaka.</description>
	<lastBuildDate>Fri, 10 Apr 2026 21:38:40 -0400</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">51ca9a33e44adf6b27b1c6848008f899</guid>
				<title>Yutaka started the topic Pros and Cons of filtering messages in TCL vs Xlate in the forum Cloverleaf</title>
				<link>https://clovertech.infor.com/forums/topic/pros-and-cons-of-filtering-messages-in-tcl-vs-xlate/</link>
				<pubDate>Mon, 08 Sep 2025 17:27:31 -0400</pubDate>

									<content:encoded><![CDATA[<p>What are the Pros and Cons of mostly filtering in TCL vs XLT?  I&#8217;ve been at organizations that do it both ways.  I generally prefer to filter messages in XLT since modern hardware can handle the processing, it&#8217;s easier for beginners to read and build, easier to debug, and even if there are errors on one route it should not prevent other routes f&hellip;<span class="activity-read-more" id="activity-read-more-27047"><a href="https://clovertech.infor.com/forums/topic/pros-and-cons-of-filtering-messages-in-tcl-vs-xlate/" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">cbefd44b45454d2b80c61d30f6e1aced</guid>
				<title>Yutaka started the topic Load flat files without breaking recovery DB in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/load-flat-files-without-breaking-recovery-db/</link>
				<pubDate>Mon, 28 Mar 2022 05:38:41 -0400</pubDate>

									<content:encoded><![CDATA[<p>We&#8217;re trying to load 94 HL7 flat files ~15-30MB in size.  Currently if I load ~120MB worth of files into the inbound thread filepath, it seems like all the messages have to get indexed first, then gets loaded into recovery database.  So while it takes some time to output messages on the outbound thread, recovery database gets overloaded and c&hellip;<span class="activity-read-more" id="activity-read-more-24424"><a href="https://usspvlclovertch2.infor.com/forums/topic/load-flat-files-without-breaking-recovery-db/" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">355c00ac97219d748b95bffb1824b1c1</guid>
				<title>Yutaka started the topic Data extract to DFT with 1 message per patient with multiple FT1s in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/data-extract-to-dft-with-1-message-per-patient-with-multiple-ft1s/</link>
				<pubDate>Tue, 04 May 2021 14:56:41 -0400</pubDate>

									<content:encoded><![CDATA[<p>We are receiving a data extract from our Epic instance with patient information and separate FT1s on each line.  The vendor is asking for DFT messages with 1 message per patient with multiple FT1s.  How can I do this translation?  I think I need to ask for the data extract in a different format, but not sure what I&#8217;m asking for.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">9536d6a5d21eb49ba52b3a6323e8ce70</guid>
				<title>Yutaka became a registered member</title>
				<link>https://clovertech.infor.com/activity/p/22205/</link>
				<pubDate>Thu, 20 Aug 2020 19:51:28 -0400</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>