Name: transmart-core-api
Owner: The Hyve
Description: null
Created: 2013-03-01 18:26:49.0
Updated: 2016-01-29 10:48:48.0
Pushed: 2016-12-05 12:44:55.0
Homepage: null
Size: 586
Language: Groovy
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|---|---|
| Harm Aarts | 2014-02-11 14:52:40.0 | 1 |
| Kees van Bochove | 2013-12-14 18:35:59.0 | 9 |
| Jan Kanis | 2014-04-10 12:01:41.0 | 5 |
| Ruslan Forostianov | 2014-06-27 13:57:43.0 | 9 |
| Gustavo Lopes | 2015-10-29 11:09:27.0 | 118 |
| Terry Weymouth | 2014-08-04 20:35:28.0 | 13 |
| Robert Horlings | 2014-05-22 07:06:05.0 | 7 |
| Florian Guitton | 2014-06-02 11:07:46.0 | 1 |
| Riza Nugraha | 2013-12-31 10:35:22.0 | 1 |
| Wim van der Linden | 2014-10-24 13:40:07.0 | 8 |
| Peter Rice | 2014-02-24 13:37:26.0 | 1 |
| j-hudecek | 2014-03-07 09:54:42.0 | 1 |
| Carlos Silva | 2014-04-14 16:09:19.0 | 4 |
Other Committers
| User | Most Recent Commit | # Commits | |
|---|---|---|---|
| Carlos Silva | carlos@thehyve.nl | 2014-04-22 12:36:30.0 | 6 |
| Peter Kok | peter@thehyve.nl | 2014-03-19 15:50:55.0 | 2 |
tranSMART Core API is a library with Groovy interfaces that define the interactions and calls between the various components of tranSMART.
To facilitate communications with i2b2 and i2b2-like clinical data resources, two API's are defined which follow the design philosophy behind i2b2 and resemble the i2b2 Ontology Management (ONT) and Data Repository (CRC) RESTful API's.
A ConceptsResource is defined which can be implemented by clinical data sources to expose ontology trees with concepts. See the i2b2 ONT messaging documentation for more background information. Only a few calls are defined, the ones which happen to be used in the legacy tranSMART codebase.
A QueriesResource is defined which can be exposed by clinical data sources as a means of querying clinical data. This resource exposes methods to run queries and retrieve query results. The API is modelled after the i2b2 CRC query message API.
A DataQueryResource is defined which can be exposed by high dimensional data sources to allow querying of high dimensional data. A general DataQueryResult is defined which can be extended for specific data types. For now, all omics data types (inside specific packages) as well as possible queries are defined inside the core API project. To model general query constraints (e.g. on subjects or timepoints), a CommonHighDimensionalQueryConstraints class is defined which can be embedded into specific constraint classes.