About Integrating Data for Clinical Subjects

The customer defines events that invoke the Siebel Web service to create and update subject information. The event defines what data entry in Oracle Health Sciences InForm will cause Oracle Health Sciences InForm to call the Siebel Web service. When patients are assigned to patient positions in Oracle Health Sciences InForm, or patient data is entered for a patient position, the integration triggers the creation of a subject in Siebel Clinical. Updates to the information for the patient in Oracle Health Sciences InForm are exported to Siebel Clinical. Deleted data in Oracle Health Sciences InForm is not reflected in Siebel Clinical. Patient data for Oracle Health Sciences InForm and subject data for Siebel Clinical is integrated as follows:

• Subject Messages. When a subject message is received by Siebel Clinical from Oracle Health Sciences InForm, Siebel Clinical evaluates it to determine if a new subject must be created or if an existing subject must be updated. Siebel Clinical searches for the system ID of the subject. If the system ID does not exist, then Siebel Clinical creates a new subject. If it does exist, then Siebel Clinical updates the subject.

• Subject Number and Subject ID. Oracle Health Sciences InForm sends the subject number over as a Subject ID to Siebel Clinical.

• Encounter Date. The customer decides which date from Oracle Health Sciences InForm to map to Encounter Date in Siebel Clinical, and configures the mapping accordingly.

• Screen Date. The customer decides which date from Oracle Health Sciences InForm to map to Screen Date in Siebel Clinical, and configures the mapping accordingly.

• Informed Consent Date. Informed Consent Date is required only if a new Subject Visit Template is being applied. If Siebel Clinical does not have an informed consent date, then an Effective Date (for the Subject View Template) is sent instead of an informed consent date.