This is a known problem with HealthFrames CCD support.
Really - its two problems - which is why there is no easy fix.
The first 'problem' - is that when running OpenHealthService plugins - HealthFrame has a TIMEOUT period. Since OpenHealthServices are plugins which anybody can write, HealthFrame cannot be sure if they take a long time that they are not hung, so it times out after 2 minutes.
There is an open bug report to track this issue, and we will probably add a configuration setting to HealthFrame letting users change the default OpenHealthServices timeout (http://bugzilla/show_bug.cgi?id=627).
The second problem is that the current CCR -> CCD conversion code we have runs as an OpenHealthService plugin, and it is slow. Really - the problem is that it is slow. We have another bug report to track the issue of speeding up CCR -> CCD conversion, but that bug report is currently LOW priority (http://bugzilla/show_bug.cgi?id=628). You are the first to have complained. If you consider it serious, please let us know, and we will consider escalating the issue.
Finally - a workaround - of sorts. Run on a faster computer. There is (essentially) no limitation on how LARGE a CCD you can create, except that the transformations get slower as the files get larger. If you try your transformation on a faster computer, it may succeed. I've tried exporting that particular file on a 3 year old laptop, and it was fast enough (took about 45 seconds).