fig3 all these processes are handled maintained and executed at regular daily weekly and monthly intervals there are some processes which are done out of the routine process such as generation of doi zip state region icd 9 etc tables fig3 shows a high level overview of the processes used to create cubes the load oracle tables process step 301 can be divided into two logically different steps daily and monthly processes described in further detail below with respect to fig4 8 the daily routines convert the text format data supplied from site 1 into u201c rx u201d and u201c do not use company name dnu u201d daily oracle tables the monthly processes convert hospital hx and medical mx data into monthly oracle tables note that all run times provided below correspond to approximate run times the daily rx load process 401 is described below with respect to fig4 rx control file to convert the rx text file from site 1 into the monthly mx load process 501 is described below with respect to fig5 the load hx text data process 601 is described below with respect to fig6 sql loader process reads hx text file and control file to 46 50 60 61 66 70 80 90 tables for hx the quarter monthly rx merge process 701 is described below with respect to fig7 combine all the daily approx 8 days of tables rx and the prepare mx data process 801 is described below with respect to fig8 the produce patient data process of step 302 fig3 is described below in.