Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_pipe
-
Labels:
-
Story Points:4
-
Epic Link:
-
Team:Alert Production
Description
Currently, ap_pipe assumes that each dataId passed to it contains exactly one visit (e.g., in doProcessCcd). ap_pipe should be extended to support ranges and other combinations of visits.
This ticket may be partially or entirely superseded by DM-11372.
Is the use case for this primarily in testing and validation, or is it also in environments like catch-up? If we had suitable workflow management that could execute ap_pipe repeatedly, would this still be necessary?