| Siebel CRM Siebel Clinical Trial Management System Guide Siebel Innovation Pack 2015, Rev. A E52416-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Siebel Clinical Trial Management System Guide Siebel Innovation Pack 2015, Rev. A E52416-01 |
|
Previous |
Next |
View PDF |
Siebel Clinical controls the integration of investigator data between Siebel Clinical and Oracle Clinical. When Siebel Clinical triggers the synchronization of protocol sites, and a protocol site is synchronized between Siebel Clinical and Oracle Clinical, the investigator is created in Oracle Clinical if it does not exist, or it is updated if the investigator name or phone number changed. Deleting investigator data in Siebel Clinical does not trigger the same operation in Oracle Clinical. Investigator data for Siebel Clinical and Oracle Clinical is integrated and processed as follows:
Principal investigator. In Siebel Clinical, the principal investigator (PI) is stored directly with the protocol site, the PI Last Name is used to search for the row ID at the contact level. This row ID is the UID for the investigator that is used in Oracle Clinical for the investigator ID. However, if the row ID is more than 10 characters long, then the system ID from Oracle Clinical for the investigator is used as the ID for the investigator.
Investigator phone number. This field is required in Oracle Clinical, but it is an optional field in Siebel Clinical. The principal investigator phone number must be populated in Siebel Clinical so that the integration can create the investigator in Oracle Clinical.
Investigator data deleted in Siebel Clinical does not trigger a deletion in Oracle Clinical. If the contact specified as the principal investigator for the protocol site in Siebel Clinical is deleted, then this deletion does not trigger the deletion of the investigator in Oracle Clinical. The investigator might be assigned to another study that is not participating in the integration.
Start date. This value, which does not exist by default in Siebel Clinical, is set in Oracle Clinical to the date that the principal investigator is assigned to the study site by the integration.
End date. This value, which does not exist by default in Siebel Clinical, is set in Oracle Clinical to the date that a different investigator is assigned to the study site by the integration. That is, the start date of the newly assigned investigator also serves as the end date for the previously assigned investigator. The end date for a given investigator cannot be prior to the corresponding start date.
All investigators transferred as active. All investigators transferred by the integration are created with a status of Active.
Updates in Oracle Clinical to investigator data might be overwritten. Any updates made in Oracle Clinical to the investigator data assigned to a study site in an integrated study might be overwritten by updates from Siebel Clinical.
Updates in the Contacts screen to the principal investigator. Updates made to the principal investigator on the Contacts screen in Siebel Clinical, such as a name or phone number, are not sent to Oracle Clinical until a change is made to a protocol site that the principal investigator is assigned to, or the principal investigator is assigned to a protocol site that is synchronized.
