[Roadmap] Gaia

[rtmill]

[working]
Create stable release of Gaia that is tested, documented and versioned. To that end, we have a list of outstanding questions and gaps to be addressed that we be binned into either necessary for the stable release or to be addressed afterwards.

• Address outstanding questions. Determine if needed before or after stable release. Create bins, define work and create tickets
  • Determine, strictly, the functional scope of Gaia and what is outside of it
  • Settle on approach for '_spec' (move away from R)
  • Distribution strategies for:
    • GaiaCore
    • GaiaDB
    • Deployment/automation stack
    • Discuss Single source DDL
  • Vocabulary integration strategy
  • Data source management
    • Accounting for changes to data sources (e.g. EPA 2008 had an edit in 2024)
    • Unique identification of data sources ( approach for minting new IDs asynchronously)
• Stable release of Gaia
  • Separate into distinct repos
  • GaiaCore (https://github.com/oHDSI/gaiacore)
  • GaiaDB
  • Adequate documentation
• Sufficiently triage work determined to be out of scope for stable release into future development work (make tickets for future work)
  • Derivation provenance
    • geom to person
    • geocoding method

[AEW0330]

Thanks for doing this roadmap.

The need for relatively complete documentation is urgent.

Can we get you help from the CHIRON cohort or elsewhere to do this soon? I think buy in for further development could be delayed if more adequate documentation waits until the prior issues re refactoring, etc. are resolved.

Work on the documentation for the current approach also seems like it could also help clarify the thinking about new options.