Looking at the error you're getting, I'm suspecting that the vendor of the external application that feeds your service intended to include a \r (carriage return) as the EOD character and somehow managed to omit the backslash. That would explain the 'r' character ... it's always an 'r' in the error that's generated, right?

Looks like changing the framing would require a modified Parser anyway. So ...

I think you'll have to create a copy of EnsLib.HL7.Service.Standard (something like OSU.HL7.Service.CrappyFraming) that changes the  %Parser property to be your custom parser:

Property %Parser As OSU.Custom.HL7.CrappyFramingParser [ Internal ];

Then modify the custom service that was developed long, long ago to subclass it:

Class OSU.HL7.Service.TCPService Extends OSU.HL7.Service.CrappyFraming[ ClassType = "", ProcedureBlock, System = 4 ]

This error is usually indicative of a framing issue. Have you looked at what, specifically, this non-HL7 data consists of?

The issue with the "[" option is that it doesn't compare the MRNs individually; it treats the entire PID:3 field (which can contain multiple MRNs) as the value to locate in MRG:1. You'd have to first locate the PID:3 iteration that contains the "CKS" facility identifier, then check the MRG:1 field to see if it's contained within it.

Hi Richard,

The issue in this case was that there could be a variable number of repetitions in the PID:3 and MRG:1 fields, and that there was no guarantee that the MRNs for each facility would appear in the same order. So the actual need was to be able to compare each iteration of the MRN in PID:3 with each iteration of the MRN in MRG:1. This is cumbersome/difficult without a loop construct in the Rules editor, and would require at least as many sequential comparisons as there are repetitions in PID:3.

The example you provided compares only the first iteration of PID:3 with the first iteration of MRG:1, so if the desired match appeared in any subsequent iteration of either of those fields the desired outcome would not be achieved. This is one of those cases where some ObjectScript is a more streamlined solution.

I think the intent is to limit configuration control of business hosts in an Ensemble production based on user role. Effectively, prevent a Cache/Ensemble user from changing the IP address or port number of a TCP/IP Business Operation through the Management Console without restricting the ability to view the settings.

So how is this an ACTUAL solution if you're going to get cursed at for using it in a Production environment?

And if there will always be a fixed number of iterations, you could do "1."_$CASE(k1,1:"a",2:"b",3:"c",4:"d",5:"e",6:"f",:""). It's hard to say which solution is less intuitive, though.

Another variation ... "1."_$EXTRACT("abcdefghijklmnopqrstuvwxyz",k1).  The possibilities are endless!

Barry, Source is the string value from the message header's SourceConfigName property, and source.%Source is an error:

The method takes the message object as its first argument, referenced by the variable Document in the Rule Editor. The call you should be making is, literally, CheckMrnDupForFac(Document,"CKS"). The method will parse the PID:3 and MRG:1 fields for you; you don't need to supply them literally.

The expression editor will often add a period after "Document" ... can you verify that you removed it?

Well, it can ... but you would need to contact the WRC for a version of ServerManager.exe that supports it:

Are you using the correct Context and RuleAssist for EnsLib.EDI.XMLDocument in your routing rule configuration? Here's the documentation link.

@Thembelani Mlalazi, he's specifically looking to get at the element %Source, which is not a field defined by the user in the RecordMap, and is not visible to the Context of the Rule.

@Thembelani, the %Source element is not directly accessible, even with the constraint set. That's why I provided the solution below.

And if they're not always in the same repetition but the number of repetitions is fixed, it gets a little bit messy; you could do something like:

HL7.{MRG:1.1} CONTAINS HL7.{PID:3(1).1}

OR

HL7.{MRG:1.1} CONTAINS HL7.{PID:3(2).1}

OR

HL7.{MRG:1.1} CONTAINS HL7.{PID:3(3).1}

If they're completely arbitrary in the number of repetitions, you're gonna have to write some COS :)