GenerateCCDElement StartDate And EndDate Do Not Limit Content Of CCD As Documented
Last updated on JANUARY 09, 2018
Applies to:Oracle Healthcare Data Repository - Version 7.0 and later
Information in this document applies to any platform.
When adding the startDate and endDate to the generateCCDElement request in the MM/DD/YYYY format as documented, it does not appear to work as documented, no results even though there is an encounter that falls within that range.
The dates have no relationship to the effectiveTime or activityTime in the encounter act.
Also, the activityTime is not included in the generated CCD. It is in the configuration file, it is mentioned in the log file as being an attribute to include, but it is not included in the generated CCD.
The expected result would be that only those encounters where the activityTime GTS is between or within the specified interval.
The issue can be reproduced at will with the following steps:
Submit the following request:
It looks as though if either the startDate or the endDate is removed from the request the entire ActCriteria for the ActivityTime is removed. Both startDate and endDate must exist if either is included. When they do exist only the startDate appears to be used as both the GTS.StartDate and GTS.EndDate.
When the endDate is changed to Jan 01, 2017 the ActCriteria changed to this:
1. AttributePredicate : [GTS.StartDate, >=, 20130101000000.000]
2. AttributePredicate : [GTS.EndDate, <=, 20170101000000.000]
Obviously there is some strange processing bewteen the reading of the startDate and endDate from the request and the creation of the ActCriteria in the RimQuery.
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