OHDSI Home | Forums | Wiki | Github

Atlas/Achilles Integration Clarification

Implementers
#1

Sorry if this was answered anywhere else, but I am a unsure I understand how Achilles is configured to work with Atlas (cV 2.2.0). For older versions you seem to define that relationship in config.js as outlined at http://www.ohdsi.org/web/wiki/doku.php?id=documentation:software:atlas:archive:atlas_setup_v1_x:

define([], function () {
  var config = {};
  config.services = [{
    name: '<YOUR ENVIRONMENT NAME>',
    url: 'http://your_webserver/WebAPI/'
  }];
 
  config.webAPIRoot = config.services[0].url;
 
  config.dataSourcesLocation = '/achilles/data/datasources.json';
  config.dataSourcesRoot = '/achilles/data';
 
  return config;
});

But for newer versions this seems no longer be the case as you mention at http://www.ohdsi.org/web/wiki/doku.php?id=documentation:software:atlas:setup, as your config-local.js example for the integration does not even mention the location of Achilles anymore. I am just trying to understand what is happening here. Thanks!

define([], function () {
	var configLocal = {};
 
	configLocal.api = {
		name: 'My Organization Name',
		url: 'https://webapi.server.com/WebAPI/'
	};
 
	return configLocal;
});
#2

The Achilles reports are located under the ‘Datasources’ on the left nav in Atlas.

When you go to Datasources, you’re presented with a list of sources which is configured via the WebAPI source and source_daimon tables.

You are still required to execute the achilles() packages which generates the summary statistics that are used in the Datasources module of Atlas. Just ensure that you generate the results into the same schema that you specified in your source_daimon’s ‘result’ daimon table qualifier.

You no longer need to exportToJson, or specify a ‘datasourcesLocation’ or datasourcesRoot config variable (as of v2.2.0). The report data is queried directly via WebAPI.

1 Like
#3

Thanks for your help, it’s greatly appreciated!

t