Include commas in code lists for your integration configuration file

For an integration between Oracle InForm and Oracle Argus Safety, commas are now supported for code lists in your integration configuration through Oracle Clinical One Digital Gateway.

How does this new enhancement work?

When a code list value contains a comma, the value is properly mapped in Oracle Clinical One Digital Gateway without generating an error. The new mapping in the integration configuration file supports all existing code list requirements.

For example, a value of "KOREA, REPUBLIC OF" will be mapped to a target value of "KR". The string in the integration file will look as displayed in the example below.

<Entry Source="KOREA, REPUBLIC OF" Target="KR" Description="Republic of Korea"/>

How can I update my current integrations?

If your integration must send code list values that contain commas, you must update the integration file to include the new configuration for code list values with commas. The existing integration should be first disabled and then you can upload the new integration template.

Additionally, with the implementation of this code list, the default code list mapper becomes deprecated. Future integrations you might configure should begin using the new code list mapper that support commas.

You can find additional information in the Digital Gateway User Guide after the Release Assessment Environment (RAE) upgrade.