publish(file) generates a view of a MATLAB® file in HTML format for sharing your code. For example, publish('myfile.m') executes the code in myfile.m using the base workspace and saves the formatted code and results in /html/myfile.html. The html subfolder is relative to the file folder.
Notice the "executes the code in myfile.m". Your program clinicalreport.m is attempting to call publish within itself. So the call to publish attempts to execute clinicalreport. That run gets to the publish() call which then attempts to execute clinicalreport. That run gets to the publish call... and on and on it goes calling itself until the stack is blown. At which point it errors out of the entire call tree without having finished writing the result of the 499 executions of clinicalreport.m
You are going to continue to have this problem as long as you have a program trying to publish itself, unless you put in specific mechanisms to ensure that the execution due to the publish() run does not trigger another call to publish()
