You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am attempting to map data from a patient table to the OMOP Person table using Perseus, but the data is not being populated into the Person table after I execute the "Convert to CDM" operation. Despite no errors being reported during the mapping or execution process, the target OMOP table remains empty.
Here is the scenario and the steps I followed:
Source Table:
My patient table contains the following fields:
row_id (integer): Represents unique row numbers (e.g., 1, 2, 3...).
id (character varying): Represents the patient identifier in the source system.
bod (date): Represents the patient's date of birth.
Mapping:
I mapped the source fields as follows:
row_id → person_id (OMOP required field, integer, primary key).
id → person_source_value (OMOP optional field, varchar).
bod → birth_datetime (OMOP optional field, timestamp).
Screenshot of the mapping configuration in Perseus: [Attach a screenshot of the mapping, like the one you previously shared.]
Expected Result:
Data from the patient table should populate the Person table, with person_id, person_source_value, and birth_datetime correctly mapped.
Actual Result:
The "Convert to CDM" process completes successfully, but no data is inserted into the Person table.
Observed Behavior:
The target Person table remains empty even though:
No errors are reported during the mapping or execution.
The source data is valid, and the mapping configuration seems correct.
The id field's data type I specified 'varchar (50)' automatically changes to character varying data type.
The text was updated successfully, but these errors were encountered:
Hi, I am attempting to map data from a patient table to the OMOP Person table using Perseus, but the data is not being populated into the Person table after I execute the "Convert to CDM" operation. Despite no errors being reported during the mapping or execution process, the target OMOP table remains empty.
Here is the scenario and the steps I followed:
Source Table:
My patient table contains the following fields:
row_id (integer): Represents unique row numbers (e.g., 1, 2, 3...).
id (character varying): Represents the patient identifier in the source system.
bod (date): Represents the patient's date of birth.
Mapping:
I mapped the source fields as follows:
row_id → person_id (OMOP required field, integer, primary key).
id → person_source_value (OMOP optional field, varchar).
bod → birth_datetime (OMOP optional field, timestamp).
Screenshot of the mapping configuration in Perseus: [Attach a screenshot of the mapping, like the one you previously shared.]
Expected Result:
Data from the patient table should populate the Person table, with person_id, person_source_value, and birth_datetime correctly mapped.
Actual Result:
The "Convert to CDM" process completes successfully, but no data is inserted into the Person table.
Observed Behavior:
The target Person table remains empty even though:
No errors are reported during the mapping or execution.
The source data is valid, and the mapping configuration seems correct.
The id field's data type I specified 'varchar (50)' automatically changes to character varying data type.
The text was updated successfully, but these errors were encountered: