Why is MedDRA needed for ATLAS?

Thank you @mik @Chris_Knoll .

Here are my current vocabulary IDs

  • Relationship
  • US Census
  • Plan Stop Reason
  • Cost Type
  • SNOMED
  • SOPT
  • Cancer Modifier
  • Visit
  • Device Type
  • Obs Period Type
  • UB04 Point of Origin
  • Sponsor
  • UB04 Pt dis status
  • CDM
  • Note Type
  • Medicare Specialty
  • Condition Status
  • Revenue Code
  • RxNorm
  • Episode
  • Read
  • NUCC
  • Cost
  • NAACCR
  • Metadata
  • Meas Type
  • UB04 Typ bill
  • CMS Place of Service
  • Nebraska Lexicon
  • ABMS
  • Procedure Type
  • Vocabulary
  • Observation Type
  • UB04 Pri Typ of Adm
  • Currency
  • Korean Revenue Code
  • Type Concept
  • Condition Type
  • Language
  • Drug Type
  • UCUM
  • Domain
  • None
  • Visit Type
  • Death Type
  • OSM
  • Concept Class
  • OncoTree
  • Cohort Type
  • MeSH
  • Plan
  • Gender
  • LOINC

A few updates: I commented out lines that used MedDRA in ddl scripts for generating results table, and Achilles generated all the results. I’m now able to view all my reports in Atlas. But like @Chris_Knoll said, I see NAs in the conditions and drugs treemap, and a few of the measurements and observations treemaps. It is fine for now, but I would like something more than a band-aid fix.

I could be wrong here but without MedDRA and ATC vocabularies Achilles was not generating treemaps (like condition treemap ) because it uses concept_hierarchy_id. I was seeing only patient reports before because Achilles does not use concept_hierarchy_id for patient report generatoin. I have something working now by commenting out the MedDRA inner join lines when generating results tables, but it would be nice to not rely on my hacks. Is paying for MedDRA the solution?