1. Change Log
  2. Oracle Clinical One Platform and Oracle Clinical One Digital Gateway 22.1 (April 2022)
  3. Fixed issues
  4. Integrations

Integrations

Fisher Clinical Services integration is failing after upgrade of Apache Mina to version 2.7.0

Integration managers: To address this issue, the SHA1 algorithm has been added to the newer version of Apache Mina 2.7.0.

Retracted workaround: None. (Issue 34142164)

Generic error message displayed when Oracle Central Coding Return Codes job fails

Oracle Central Coding administrators: Now, if the Oracle Central Coding Return Codes job fails when attempting to return medical coding data to a Oracle Clinical One Platform study, Oracle Central Coding displays an error message that is relevant to the error. Previously, Oracle Central Coding would display a generic error message making it difficult to troubleshoot the issue.

Retracted workaround: None. (Issue 34064421)

Multiple answers to a question are not supported in an integration (former known issue)

Note:

This fixed issue does not impact the Oracle InForm to Oracle Argus Safety integration.

Integration managers: Now, you can integrate multiple answer options for a drop-down or a question with checkboxes (options introduced through a code list) without running into any issues. Previously, you could not select several answer options to integrate for a multiple-choice question.

(Issue 33520631)

Out-of-range data can still be loaded into Oracle Clinical One Platform forms (former known issue)

Integration managers: Now, when you attempt to load data that does not match the criteria specified in Oracle Clinical One Platform, an appropriate validation error is displayed in the application. Previously, you may have noticed that the integration could load data that was out of range. For example, when a text field’s limit for the number of characters was 3, and you loaded a data point that contained more than 3 characters, the job was successfully completed. Moreover, the Oracle Clinical One Platform UI did not highlight the field. Instead, anything that exceeded the 3-character limit was truncated and not displayed in the text field.

Retracted workaround: None. (Issue 33367269)

Parent topic: Fixed issues