[Simon Jamison]

Jim/Paul,

Thanks very much for your help. Moving the additional suppression Xlate to the start of the chain of three translations did the trick.

This is only a temporary workaround so ignoring any downsides/sub-optimal coding 🙂

Simon

[Simon Jamison]

Hi,

Paul’s idea of:

if $x eq =1 || $x eq =2

works OK and I was going to use it but it turns out that in the live environment there are 7 or 8 instances mapping to 1 so too many to hard code especially if changes need to be made for other hospitals using this in future.

Anyway, I now want to try your idea Jim. I have used a table before and indeed if there was only this position to map I would just use one without an IF but other positions in the field (PV1-8) depend on this value.

Could you expand on how to use the variable in conjunction with the table? I’ve used a variable in an ITERATE but that’s all.

If it’s any help in an example I’m mapping (simplified):

GP, GPN, GPR to GP

CON, CPN, CAN to CON

Many Thanks.

[Simon Jamison]

Sorry, translation rather than TCL .Will try the suggestions and get back to you.

[Simon Jamison]

Fixed. There’s a header for each record which contains simply the number of characters to come for the next patient, eg: 000000831

I didn’t know what this was and when I anonymized the data the number of characters changed. The testing tool showed that a different number of characters was present than what was expected (from the header).

Learning every day! Thanks again.

[Simon Jamison]

Thanks guys.

Nothing in SMAT, nothing in the error database. Using fileset-local.

There is a translation involved so, being fairly new to Cloverleaf, I’ll have to find out how to check if it failed on that. Good chance it did as I cut down a large live file to one patient record to do this testing and maybe left something out.

I’ll let you know how I get on.

[Author]

Replies