welcome:overview:cdm:cdm_conversion_best_practices
This is an old revision of the document!
What do I have to have to do an OMOP conversion?
Pre-analysis
- Data from source (or at least range for each field).
- Data dictionary including:
- taxonomies
- OMOP vocabulary (reference codes)
- are any fields masked or modified for privacy and if so, what is the algorithm?
- Identify subject matter expert for source.
- Identify OMOP subject matter expert.
- Use cases for destination.
- List of standard questions:
- Number of records
- How often is data refreshed?
- Is the conversion feasible?
- Draft ETL Specs.
Meeting with subject matter experts
Post-analysis
- Initial ETL Spec including:
- Business rules for mapping in a detailed specification, preferably in a computer readable format, like White Rabbit.
- View of mapping, preferably in a computer readable format, like rabbit in a hat.
- Identify any additional mapping needed:
- custom or local mapping of organizational codes
- country codes not already in OHDSI vocabulary like OHIP codes
- Preferred development methodology
ETL Conversion
- CDM Builder
- SQL Development
- Sample size for development
- Major pieces of work (Scrum Epics)
- Each table
- Dimension table first
- GRA table always last because derived
welcome/overview/cdm/cdm_conversion_best_practices.1498684463.txt.gz · Last modified: by bchristian
