Track Activity Job Is Not Picking Activities When Criteria Level Is Dcm For Pip (Oc,Sc)

(Doc ID 1318099.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Clinical - Version: 4.6.0 and later   [Release: 4.6 and later ]
Information in this document applies to any platform.

Symptoms


You are trying to verify that your recently installed PIP is working between OC/RDC and Siebel.

After having setup a verification test, running the Track Activity batch job which should determine if the correct data is accessible and indicates an activity completion, the report did not determine that the process was complete.

User has defined an activity where criteria level is DCM and Completion Date level is set to DCM; user has verified that clinical items in Siebel are referred to correctly.  However after data entry from OC for the patient when the track activity batch job is run it does not pick up the patient as per the criteria.

TEST STEPS:

1. Define DCM/DCI/Patient/Site


2. Define Activity in OC based on clinical items defined in SC.

Activity: SCENARIO 4.2
Type: Visit
Status: A
Visit Specific Criteria: Checked
DCI Book: PIM4930G MAINBOOK
Clinical Planned Event: PIP VISIT 3
Completion Data Level: DCM
Completion Date Source: Specific Date
Criteria Level: DCM
Criteria Details:
Use as Specific Date: checked
DCM Name: CLAB
DCM Subset #: 2
Qualifying Value: 02


3. Enter data for the patient to complete the criteria.


4. Run the track activity batch job


5. Job output does not pick up the patient activity that just completed.



This happens consistently.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms