Records in source split over two records in OMOP

[boverdui]

Hello,

I performed mapping and transformation for some (fake) test date to come to grips with the Carrot system.

The records from my demographic source table are in the output for OMOP all split up into two records, which doesn't seem right.

Cheers,
Bert

demographic.csv
rules_bert.json
person.tsv.xlsx

[AndrewThien]

Hi,

Our team is looking at this problem but may have a late reply, due to other priorities right now.

Thanks for you patience.

Thien

[DrUrwin]

Hi Bert,

The requirement is 1x table for Demographics, with a minimum of 4 data attributes thus:

• Identifier
• Sex
• Ethnicity
• Date of Birth

Regards,

    Esmond

[boverdui]

Hello Esmond,

That is exactly what I have.

Cheers,
Bert

[AndrewThien]

@anwarfg can you please have a look at this as well?
@DrUrwin so, is that a normal behaviour or a bug from your perspective?
Thanks both!

[DrUrwin]

Hi Bert, it might be useful to discuss this issue over a Teams call - would that of use to you? Please let me know what you think and I can organise a Teams call if needed, thanks.

Regards,

Esmond

[anwarfg]

HI Bert,

Apologies for the delay in dealing with this. We have found the issue to be an issue in the software for carrot transform - it was creating a new record for each different mapping. This is the desired behaviour for other tables, but not for the person table. This has now been fixed in the latest version of carrot transform (v.0.3.5). You should also know that we've been working hard to make it easier to deploy, so it's available on PyPi through pip, and the quickstart instructions have been updated to reflect this.

Could you try out this new version and confirm that it solves the issue?

Kind regards,
Anwar

[boverdui]

Hello Anwar,

I can confirm that this solves the issue. Thanks!

Cheers,
Bert