[Aaron Oxenreider]

Jim-

I saw you working on this before, and I was hoping you’d respond.

Copying the values to the non-iterate segment worked perfectly.  That’s exactly what I was looking for.

Thank you.

Aaron

[Aaron Oxenreider]

Thanks Max and Levy.  That last code set worked great.  I still have to tweak the format, but overall, it greatly reduces the spaces, and clears out the OBX5 with just the double spaces.

Again, thank you for the help, and everyone who posted suggestions too.

[Aaron Oxenreider]

Well that worked, but a little too good.  the ” +” is taking all of the spaces out of the OBX5 field, and smashes all the data together.  Great for SMS, but not so good for the nice reporting (cough, cough, that was a joke) that Centricity is trying to do.

Can I use the regsub with an If statement?  If @obxdata eq =”  ” then regsub….   then copy that back to OBX5?

[Aaron Oxenreider]

I like the echo ability.

[Aaron Oxenreider]

Oh. That’s right. I didn’t set that up or use it.

I’ll take it out and see if it works, and I still need to insert the echo.

When I insert the echo, can I see that in the testing tool?  I use that the most as it allows quick changes and refreshes easily.

[Aaron Oxenreider]

I tried both of the suggestions, and I believe I even tried the {  } in the regsub when I was first developing the script.

Neither seems to work, so I suspect there is further processes at work stopping it from working correctly.

This is all being done within a second iterate, with the first having settings as follows: Type: Group, Basis: 2, Variable %g1  and then I have the second iterate set as: Type: Group, Basis: 2(%g1).1(0).1, Variable %g2.  Usually when I screw up the iterates, I see my xlate only correct the first line of the OBX, but in this case, I see no changes.

Screenshot is most of the xlate, with most data not being shown is just correcting/changing values at the end.

Hoping someone can see where my configuration is not working correctly.

[Aaron Oxenreider]

So now you’ve got me looking at this different.

I have a separate ORC, and therefor one 1 OBR per group.  Correct?

If that’s the case, then I really don’t want to enumerate as they really are separate orders, and therefor the system is working as designed.

[Aaron Oxenreider]

Jim Kosloskey wrote:

Go to the HL/7 Configurator and select your variant.

Then in the message tab select your Message/Event. The right hand pane will have the messges structure.

Take a screen shot of that and post.

Oh, that’s right.  Been a while since I’ve looked in there.

I’m just using the default ORM_O01, with no specific varient.

[Aaron Oxenreider]

I would like to.  What would be the best way.

I can see what seems to be separate groups when I use the testing tool.

[Aaron Oxenreider]

Jim Kosloskey wrote:

Are you using %s1 for your ITERATE variable?

Also are you sure the OBR for the message you are receiving is a repeating segment and not part of a repeating group?

I’m using %g1 as the Iterate variable. (see attached #2)

I’m not sure how to tell the difference between a repeating segment and repeating group.  Here is the section from a test message i’m using.

ORC|NW|600062-1|||||||20130220|||abcdefghi

OBR|1|600062-1||80162^DIGOXIN|||20130220||1||N|||||abcdefghi|||||||||||^^^^^R

DG1|1|I9|427.32^ATRIAL FLUTTER^I9|ATRIAL FLUTTER

ORC|NW|600062-2|||||||20130220|||abcdefghi

OBR|1|600062-2||80048^BMP|||20130220||1||N|||||abcdefghi|||||||||||^^^^^R

DG1|1|I9|427.32^ATRIAL FLUTTER^I9|ATRIAL FLUTTER

ORC|NW|600062-3|||||||20130220|||abcdefghi

OBR|1|600062-3||81003^UA m if,culture if|||20130220||1||N|||||abcdefghi|||||||||||^^^^^R

DG1|1|I9|427.32^ATRIAL FLUTTER^I9|ATRIAL FLUTTER

[Author]

Replies