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

Python dependency #17

Closed
vojtechhuser opened this issue Sep 1, 2015 · 6 comments
Closed

Python dependency #17

vojtechhuser opened this issue Sep 1, 2015 · 6 comments

Comments

@vojtechhuser
Copy link

Inside CMS VRDC, we are not able to run Python. We initiated a project that ports this ETL to pure SQL that can run in SAS (SAS SQL flavor :-( )

@aguynamedryan
Copy link
Contributor

Sorry to hear that. If you're willing and able, please feel free to submit a pull request with your SAS SQL implementation if you'd like it to live in this repository.

@markdanese
Copy link

Also, don't hesitate to let us know if you have any questions on the ETL spec, or the test cases.

@fabkury
Copy link

fabkury commented Sep 22, 2015

Here is the repository with what we have so far (not much, I admit):
https://github.com/fabkury/cms_vrdc_etl
In short, this is an ETL code built to be executable inside the CMS VRDC. It is not a port of your ETL, but your work was good as an orienting example.
We will be presenting the rationale and challenges about this in-VRDC ETL in a poster at the OHDSI Symposium next month. We referenced your Python work in the poster.

@dckc
Copy link

dckc commented Dec 1, 2015

Can you run Java in the CMS VRDC? If so, consider Jython.

How about .Net stuff? If so, IronPython might work.

On the other hand, SQL might be a more natural way to represent the ETL. I haven't studied the details.

@dckc
Copy link

dckc commented Dec 1, 2015

Now that I have looked into the details a bit, using SQL does seem to be a good approach. In fact, our SamTheEagle project mostly uses SQL. We load the CSV files into Oracle and then use SQL to transform the data.

Our target is i2b2 rather than OMOP, but I think it would be interesting to factor out the common bits.

We haven't managed to publish the SQL code yet. IOU.

@ChristopheLambert
Copy link
Contributor

Closing this request to port the repository to another language.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants