We can see here the differences between R4 and R5 releases of FHIR. I can't imagine an organization migrating FHIR respositories every 3 or 4 years to keep updated to the latest version. What I forsee it's a future with a lot of organizations using different versions of FHIR and trying to communicate among them struggling against the differences...exactly the same that we have right now.

Hi @Yone Moreno !

You can do something like this to filter messages with no OBX:

Do a foreach by OBX, in case that OBX exists you can redirect the message to the proper business component and jump out of the loop. @withOBX is a local variable to check if exists any OBX segment, if the value is "0" then there is no OBX segments and you can redirect the message to another business component.