Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Use Case]: Ares #337

Open
kzollove opened this issue Jun 24, 2024 · 0 comments
Open

[Use Case]: Ares #337

kzollove opened this issue Jun 24, 2024 · 0 comments
Labels
Use Case A development-driving use case

Comments

@kzollove
Copy link
Collaborator

kzollove commented Jun 24, 2024

Description

OHDSI GIS workgroup hopes to work with the Achilles and Ares development teams to contribute new data characterizations derived from non-OMOP sources related to OMOP data.

TODO:

  • Propose an overall strategy for getting non-Achilles data into Ares
  • Develop an "Achilles Results Compliant" model that could interface with Ares
  • Define requirements for the types of data that might go in to Ares from this alternative route
  • Set up the overall mechanism for pushing these data to Ares

Infrastructure

This can be done within the OHDSI GIS Infrastructure, but will require new means of interfacing with Achilles/Ares. Or rather, a new way to form "Achilles Compliant" results that can be easily ingested by the Ares front end.

Timeline

No response

Credit

No response

Support

No response

Datasets of Interest

No response

Depends On

No response

@kzollove kzollove added the Use Case A development-driving use case label Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Use Case A development-driving use case
Projects
Status: 🏷TODO
Development

No branches or pull requests

1 participant