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

Convert ehr api to export api #321

Closed
6 of 9 tasks
stefpiatek opened this issue Feb 26, 2024 · 2 comments · Fixed by #370
Closed
6 of 9 tasks

Convert ehr api to export api #321

stefpiatek opened this issue Feb 26, 2024 · 2 comments · Fixed by #370
Assignees
Milestone

Comments

@stefpiatek
Copy link
Contributor

stefpiatek commented Feb 26, 2024

Definition of Done / Acceptance Criteria

Once we have finished off the 100 days integration of new model for redaction in UCLH-Foundry/the-rolling-skeleton/issues/214 , strip out the emap star querying from PIXL

  • Remove tables from PIXL DB relating to EHR data (this is now in the OMOP extract)
  • Convert ehr api to export api and rename endpoints for exporting data (see top level document for step naming)
  • Remove redundant tests, fake cogstack api, fake emap star etc.
  • the pixl CLI create radiology linker table on the fly (and writes to export dir): on export will read in the omop data, query the pixl pipeline database for all images in the project name, and merge the omop data with the hashed imaging identifier to write the linker parquet file
  • Rename EHR env vars and document that these need renaming in config file
  • Remove ehr queue
  • move orthanc anon's ftps export into the export api. orthanc anon tells export api that this resource is ready for export

Testing

No response

Documentation

  • Update documentation to reflect exporting function, documenting pathways for exporting images and parquet files, imaging alone and parquet alone?

Dependencies

  • UCLH-Foundry/the-rolling-skeleton/issues/214

Details and Comments

No response

@jeremyestein
Copy link
Contributor

@stefpiatek Am assuming the pixl az-copy-ehr command can be removed?

@stefpiatek
Copy link
Contributor Author

@stefpiatek Am assuming the pixl az-copy-ehr command can be removed?

Yep!

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

Successfully merging a pull request may close this issue.

3 participants