ARS-toscana / ConcePTIONAlgorithmPregnancies

Repository of the script of the ConcePTION Algorithm for Pregnancies
GNU Affero General Public License v3.0
5 stars 3 forks source link

Error in step_04_01_T2.2 - FISABIO #57

Closed elisacm98 closed 1 year ago

elisacm98 commented 1 year ago

Hi @GiorgioLimoncella,

We had the following error running the pregnancy script:

image

Can you help us to solve it?

Thanks!

GiorgioLimoncella commented 1 year ago

Hi @elisacm98,

It seems that the variable "pregnancy_with_dates_out_of_range" was not created.

This variable is constructed in internal consistency checks, basically checking that the date of the pregnancy record is included in the data reliability period.

The data reliability period is retrieved from the INSTANCE table.

Could you please check that the variabial "source_table_name" in the INSTANCE.csv file takes the same value as the origin variables in the others tables? (e.g. mo_origin in MEDICAL_OBSERVATION, origin_of_event in EVENT, so_origin in SUVEY_OBS, ...)

These variables should match the name of the original table before ETL.

elisacm98 commented 1 year ago

Hi @GiorgioLimoncella,

Thanks for your help. As you said there was an error in some of the "origin variables". We run again the script, and now we had an error in step_01_03_T2.1:

image

The error was produced while creating the PROCEDURES conceptsets.

Can you help us again? Thanks!

GiorgioLimoncella commented 1 year ago

Hi @elisacm98,

unfortunately I can't figure out the problem, there might be some issue with the original tables, if you agree I will contact you by email to arrange a call to check them together.

elisacm98 commented 1 year ago

Hello again @GiorgioLimoncella, @OlgaPaoletti and @DavideMessinaARS,

We ran the step again without ths strange procedure code and now it worked.

Thanks for your help!

elisacm98 commented 1 year ago

Hello again, 

We had another issue while running the pregnancy script. This time it was in step_05_01_T2.3, and it seems that the problem is that we don't have an identification for the born child. We saw in the script that some other values are created empty if they are missing, however this is not the case for child_id. Creating an empty record would be a solution to our problem or is this variable important for the next steps of the script? At the moment and in the near future, we are not going to have this variable. So if it´s important we would need to discuss how to implement the script without it.

 I attach a screenshot of the error:

  MicrosoftTeams-image (2)

I include my colleague @urchuegu, so she can participate.

Thanks a lot for your help! 

GiorgioLimoncella commented 1 year ago

Hi @elisacm98,

the child_id is not mandatory, you are right it should have been created empty like the other variables. I corrected the step by adding the line you suggested, you can download it from GH and replace.

In addition, could you replace also step 5_03 as well? we made some minor changes, you can find that updated in GH as well!

links:

Thanks!

elisacm98 commented 1 year ago

Hi @GiorgioLimoncella,

Thanks for the updated steps. We have run the script and now it has worked.

Thank you very much for your help during the process!