Full OMOP_ES extract

[linear]

Acceptance Criteria

As a catalogue user, I want to have a full (no filters, in term of cohort but also concepts) real OMOP extract (first, from Caboodle only).

Testing

• A functional OMOP dataset (with all constraints provided by the CDM) on UDS;
• An instance of the ATLAS OHDSI tool;

Documentation

Dependencies

Details and comments

• Having the batch process working in OMOP_ES;
• Define extraction settings;
• Having a new project setup in OMOP_ES;
• Running the extract (on GAE10, by using the 'crdm-tools' container?);
• Importing data in UDS (by using the 'omop-cascade' tool?);

[linear]

SAF-642 Full OMOP_ES extract

Acceptance Criteria

As a catalogue user, I want to have a full (no filters, in term of cohort but also concepts) real OMOP extract (first, from Caboodle only).

Testing

• A functional OMOP dataset (with all constraints provided by the CDM) on UDS;
• An instance of the ATLAS OHDSI tool;

Documentation

Dependencies

Details and comments

• Having the batch process working in OMOP_ES;
• Define extraction settings;
• Having a new project setup in OMOP_ES;
• Running the extract (on GAE10, by using the 'crdm-tools' container?);
• Importing data in UDS (by using the 'omop-cascade' tool?);

[linear]

SAF-642 Full OMOP_ES extract

Acceptance Criteria

As a catalogue user, I want to have a full (no filters, in term of cohort but also concepts) real OMOP extract (first, from Caboodle only).

Testing

• A functional OMOP dataset (with all constraints provided by the CDM) on UDS;
• An instance of the ATLAS OHDSI tool;

Documentation

Dependencies

Details and comments

• Having the batch process working in OMOP_ES;
• Define extraction settings;
• Having a new project setup in OMOP_ES;
• Running the extract (on GAE10, by using the 'crdm-tools' container?);
• Importing data in UDS (by using the 'omop-cascade' tool?);

[milanmlft]

The deployment on GAE05 is now running with a full extract