Defaults Relationships for OXI_HUB

Relationship Between Defaults and Conversion Codes – Data from External System to ORS

If the conversion table for a data element is activated:

• Check if property-specific conversions exist and convert value
• if fails, check if global conversions exist and convert value
• if fails-> OXI_HUB will validate the data element against valid ORS codes and if that validation passes, insert the original code.
• if fails and property default exists->use property default
• if fails and global default exists->use global default
• if fails->OXI_HUB will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

If the conversion table for a data element is NOT activated:

• Validate the data element against valid ORS codes and if that validation passes, insert the original code.
• if fails, check if property default exists->use property default
• if fails and global default exists->use global default
• if fails->OXI_HUB will fail the message in case the data element is mandatory (e.g., room type), or ignore element in case the data element is optional. In this case the message will still be processed but this data element will be ignored.

Relationship Between Defaults and Conversion Codes – Data from ORS to External System

If the conversion table for a data element is activated:

• Check if property-specific conversions exist and convert value
• if fails, check if global conversions exist and convert value
• if fails and property default exists->use property default
• if fails and global default exists->use global default
• if fails->OXI_HUB will send the data element as it is

If the conversion table for a data element is NOT activated:

• Check if property default exists->use property default
• if fails and global default exists->use global default
• if fails->OXI_HUB will send the data element as it is