Requirements (mainly: N3C outside-enclave desired features)
Sigfried opened this issue · 6 comments
Summary
There are features we want to use for N3C work but want available outside of the N3C enclave. See: Google sheet
Outside-enclave requirements
(last updated: 2022/07/11)
Other requirements
Security
Stuff to get from Enclave
- Concept sets (All maybe, or start with:)
- Defaults VSAC
- Defaults HCUP
- LL
- LL/DL pairs?
- Concept sets -- All maybe, or start with:
- Defaults VSAC
- Defaults HCUP
- LL
- LL/DL pairs?
Data sources
We can have the app (i) fetch some stuff on load, (ii) also let users fetch stuff.
Caching
We can use GitHub, or an RDBMS or AWS S3 for example to cache data fetched.
Infrastructure integrations
Enclave -> GitHub -> TermHub?
Cronjob?
I think GitHub actions can run on a schedule, and can update GitHub static files. This will be our cache.
UI features
A button that lets them fetch from Enclave manually? We can probably have it call GitHub API to call the action.
@Sigfried I was going to make a new issue but I figured this was close enough that I should rename it. If you want I can create a new issue though.
@DaveraGabriel FYI at the meeting this morning Chris mentioned Vulcan / FHIR::OMOP in relation to requirements. He didn't say much; I think what he was asking was for us to have something about the requirements for that here. If you have anything to add on that here, feel free!
edit 2022/07/21: Davera Said
There MAY be features relating to access / permissions but I would think that's secondary to other functionality. Mostly this supports governance processes relating to IP of the content.
Took this from the BIDS agenda from today: https://docs.google.com/document/d/1ojHRjh_IWItT4xul1z1XaHzDQPctOUCe/edit
This is basically complete but I'll leave it.