Scott Beeson · Mar 3, 2016

Filtering incoming records?

We have a situation where we want to detect and ignore documents/records at the earliest possible point based on certain criteria.  We have an existing "CDA Preprocessor" in the workflow which is an XSL transform.  This is what our contractors are planning to utilize to "filter" these documents.  This doesn't really make sense to me.  I see XSLT as a way to manipulate the contents of a document and filter certain peices of data.  In my brain, I would use an Ensemble business rule to detect the criteria and route the document as necessary.

Does anyone have any input on this?  Our contractors have much more experience than I do with Healthshare, so I'd like to know why this makes more sense.

0 334
Discussion (4)0
Log in or sign up to continue

My idea would also be to use business rules to sort/filter messages. You can also define transformations in the business rules and I would guess (without knowing the details) it might even be more efficient to first do the sorting and then transformations if necessary.

(I'm not familiar with Healthshare, I but I have little experience with Ensemble.)

XSLT in combination with %XML.XSLT.CallbackHandler is an excellent way to extract information from a (large) XML file.

We use it to perform XML Shredding and flattening on very large XML.

That's the thing, the goal isn't to extract information.  I guess technically I am extracting information to make a determination, but I'm either sending the entire document or nothing.

That's the point you make the decision based on values of elements or attributes within those elements, XSLTs XPath expressions make it very easy to address and 'extract' those.