OHDSI Home | Forums | Wiki | Github

OHDSI-in-a-box ATLAS Results and Performance

General
#1

I’m working with an OHDSI-in-a-box instance from the us-east-1 stack on a t3.medium EC2 instance and am running into a couple of inconsistencies between the dmeo ATLAS and the in-a-box ATLAS I was hoping people could help me understand.

  1. When I search http://atlas-demo.ohdsi.org/ for “Prematurity of infant” I’m given the SNOMED code 771299009 and associated concepts that I anticipate. But when I search the string, the SNOMED code, and the concept ID in both ATLAS and the sql workbench I don’t get any results. Any ideas where this difference comes from? I’m thinking it may be a versioning issue but I’m not sure where the source of the problem would be.

  2. The in-a-box implementation of ATLAS is pretty slow and can be quite laggy. Any ideas for best practices when it comes to performance?

Thanks!

t