Siebel CRM Web Services Reference > Siebel CRM Primary Web Services >

ClinicalSubject

Use this Web service to perform the following:

• Create a subject record in the Siebel database from details provided by an external application. The Screen and Enrollment template is applied to each new record with a default informed consent date, if a date is not provided by the external application. If a valid informed consent date is provided by the external application, then the Web service updates the default value with the valid informed consent date.
• Create additional Siebel Life Science statuses for a subject apart from the statuses Screened and Enrolled.
• Mark a subject visit as missed.
• Override the subject visit completion or missed value.
• Create subject statuses using Visit Type.
• Delete the subject status.
• Designate the latest subject status as Primary.
• Designate any record at Primary.
• Mark Visits/Activities as completed with the Completed Date details, and other information provided by the external application.
• Generate an error when the IntegrationId is not sent in the Web service for Visit Completion.
• Use new custom tags: ActCustom1 through ActCustom25 in the Action (No Owner Lock) and SubCustom1 through SubCustom23 on the Clinical Subject integration component.

  NOTE:  SubCustom24 and SubCustom25 are reserved for Delete Non Applicable Visits flag and SVT Effective Date.

• Use special status values: Randomized Date, Early Terminated Date, Screen Failure Date and Screen Failure Reason.
• Mark Visits/Activities as completed with the Completed Date details, and other information provided by the external application.

  NOTE:  This Web service assumes that the Visits/Activities Clinical Item is unique for the given Subject Visit Template.

• Support Subject Transfer from one Study site to another.

This Web service returns the Integration ID when a subject creation is successful. The Integration ID is used for identifying the subject for any future operations. An error message is presented in the event of an error.

ClinicalSubject Operations

For a list of operations associated with this Web service, see Table 80.

Request Message Description: Upsert

For a description of this request message, see Table 81.

Response Message Description: Upsert

For a description of this response message, see Table 82.

ClinicalSubject Application Interface

This topic describes the application objects called by this Web service. For more information on application implementation, refer to your application development documentation on Oracle Technology Network.

Service Object (Business Service or Workflow)

For a description of the service objects for this Web service, see Table 83.

Data Object (Integration Object)

For a description of data objects for this Web service, see Table 84.

Example Package for ClinicalSubject

To view an example of messages for this Web service, navigate to the documentation library for Siebel Business Applications on Oracle Technology Network, and click the Related Files link next to the link for Siebel CRM Web Services Reference to access a zip file. Extract the files in the zip file.

Request

See the following file to view the sample code:

...\ClinicalSubject\ClinicalSubject_request.xml

Interface Description (WSDL) for ClinicalSubject

To view the interface description for this Web service, navigate to the documentation library for Siebel Business Applications on Oracle Technology Network, and click the Related Files link next to the link for Siebel CRM Web Services Reference to access a zip file. Extract the files in the zip file.

...\ClinicalSubject\ClinicalSubject_asi_ClinicalSubject.wsdl