10 Publish intake records to a sponsor-owned safety database for case processing

Oracle Safety One Intake supports publishing documents to external systems, such as other Oracle Argus Safety environments or other sponsor-owned safety platforms. This feature is useful for organizations who are responsible for intake processing only and publish the results to their own customers for case management.

For information on how to configure the external publishing features, reach out to your delegated administrator.

If your environment is configured to publish to external systems, Oracle Safety One Intake handles incoming documents as follows:

• To documents that are not compliant with the E2B(R3) format, such as DOC, DOCX, or PDF, Oracle Safety One Intake will make all the necessary adjustments in order to ensure compatibility with receiving systems.

  Note:

  If the system encounters any issues during the conversion of extracted data to the E2B(R3) format, a warning file is generated, which is then embedded into the newly created E2B(R3) file.
• To documents that are compliant with the E2B(R3) format, Oracle Safety One Intake will only add information pertaining to narrative processing, such as product or event tags identified through OCR/ML extraction.

  Note:

  All automated features, including OCR/ML extraction, require an additional subscription to Oracle Safety One Intake. For more information, reach out to your appointed Oracle point of contact.

The Oracle Safety One Intake has the capability to transmit documents that require further case processing to other platforms using the following channels:

• Via email, only if the receiving system is configured appropriately. This applies to any non-Oracle Argus Safety application, as well as Oracle Argus Safety (both on-premise and cloud) applications that are older than version 8.4.1.
• Via REST API, should the recipient be an Oracle Argus Safety environment (both on-premise and cloud), version 8.4.1 or newer.

  Note:

  To import E2B(R3) files received from Oracle Safety One Argus, you need to extend the existing E2B(R3) profile. For more information, see

Whenever Oracle Safety One Intake is configured to publish intake records to a sponsor-owned safety database for case processing, the system only performs tasks related to intake processing. Once intake processing has taken place, case processing is not performed within the system. This means that within the Create New Record and Review Record tasks, Submit is available instead of Search, allowing the record to be published to an external system once intake processing is complete. For more information, see Possible tasks related to processing your records.

In the event that errors occur during the transmission of records to other systems, such as a temporary outage of a recipient's email service, Oracle Safety One Intake automatically assigns the Review Record task to the record. This enables users to re-submit records for transmission. For more information, see Possible tasks related to processing your records.