Clinical data warehouse: Difference between revisions
imported>Supten Sarbadhikari (For February'08 Write-a-thon) |
mNo edit summary |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{subpages}} | {{subpages}} | ||
A '''clinical data warehouse''' or '''CDW''' is a facility that houses all electronic data collected at a clinical center <ref name="titleData Warehouse">{{cite web |url=http://pharmacy.auburn.edu/pcs/review/datawh.htm |title=Data Warehouse |accessdate=2008-02-06 |format= |work=}}</ref>. | A '''clinical data warehouse''' or '''CDW''' is a facility that houses all electronic data collected at a clinical center <ref name="titleData Warehouse">{{cite web |url=http://pharmacy.auburn.edu/pcs/review/datawh.htm |title=Data Warehouse |accessdate=2008-02-06 |format= |work=}}</ref>. | ||
For any modern clinical institute, it is necessary to separate operational data from informational data by creating a clinical data warehouse <ref name="titleClinical Data Warehousing - Clinfowiki">{{cite web |url=http://www.informatics-review.com/wiki/index.php/Clinical_Data_Warehousing |title=Clinical Data Warehousing - Clinfowiki |accessdate=2008-02-06 |format= |work=}}</ref>. | For any modern clinical institute, it is necessary to separate operational data from informational data by creating a clinical data warehouse <ref name="titleClinical Data Warehousing - Clinfowiki">{{cite web |url=http://www.informatics-review.com/wiki/index.php/Clinical_Data_Warehousing |title=Clinical Data Warehousing - Clinfowiki |accessdate=2008-02-06 |format= |work=}}</ref>. | ||
A growing number of technologies for integrating and performing structured analyses of data from disparate sources are competing to win the day for healthcare organisations <ref name="titleHow business intelligence is making healthcare smarter — NHS Connecting for Health">{{cite web |url=http://www.connectingforhealth.nhs.uk/newsroom/worldview/protti10 |title=How business intelligence is making healthcare smarter — NHS Connecting for Health |accessdate=2008-01-30 |format= |work=}}</ref>. | A growing number of technologies for integrating and performing structured analyses of data from disparate sources are competing to win the day for healthcare organisations <ref name="titleHow business intelligence is making healthcare smarter — NHS Connecting for Health">{{cite web |url=http://www.connectingforhealth.nhs.uk/newsroom/worldview/protti10 |title=How business intelligence is making healthcare smarter — NHS Connecting for Health |accessdate=2008-01-30 |format= |work=}}</ref>. | ||
The [http://ycmi.med.yale.edu/TrialDB TrialDB] clinical study data management system of Nadkarni et al was the first to use multiple EAV (''Entity-Attribute-Value model'' or ''Object-Attribute-Value Model'' or ''Open Schema'') tables, one for each DBMS data type. The EAV/CR (with ''Classes'' and ''Relationships'') framework, designed primarily by Luis Marenco and Prakash Nadkarni <ref name="titleThe EAV/CR Data Model">{{cite web |url=http://ycmi.med.yale.edu/nadkarni/eav_cr_frame.htm |title=The EAV/CR Data Model |accessdate=2008-02-06 |format= |work=}}</ref>, overlaid the principles of object-orientation on to EAV; it also built on Slezak's object table approach. | The [http://ycmi.med.yale.edu/TrialDB TrialDB] clinical study data management system of Nadkarni et al was the first to use multiple EAV (''Entity-Attribute-Value model'' or ''Object-Attribute-Value Model'' or ''Open Schema'') tables, one for each database management system ([[DBMS]]) data type. The EAV/CR (with ''Classes'' and ''Relationships'') framework, designed primarily by Luis Marenco and Prakash Nadkarni <ref name="titleThe EAV/CR Data Model">{{cite web |url=http://ycmi.med.yale.edu/nadkarni/eav_cr_frame.htm |title=The EAV/CR Data Model |accessdate=2008-02-06 |format= |work=}}</ref>, overlaid the principles of object-orientation on to EAV; it also built on Slezak's object table approach. | ||
Both TrialDB and EAV/CR are open-source, though they are built on Microsoft technologies rather than Java/Linux. | Both TrialDB and EAV/CR are open-source, though they are built on Microsoft technologies rather than Java/Linux. | ||
In Oracle Clinical, a package for the management of clinical trials data; the clinical data component is stored in an EAV structure where all values are coerced to the ''varchar2'' data type. Here a major DBMS vendor has decided that, despite all the difficulties and hazards of working with EAV, some circumstances make its use unavoidable. | In Oracle Clinical, a package for the management of clinical trials data; the clinical data component is stored in an EAV structure where all values are coerced to the ''varchar2'' data type. Here a major DBMS vendor has decided that, despite all the difficulties and hazards of working with EAV, some circumstances make its use unavoidable. | ||
<ref name="titleAsk Tom Query on design">{{cite web |url=http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:10678084117056 |title=Ask Tom "Query on design" |accessdate=2008-02-06 |format= |work=}}</ref> | <ref name="titleAsk Tom Query on design">{{cite web |url=http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:10678084117056 |title=Ask Tom "Query on design" |accessdate=2008-02-06 |format= |work=}}</ref> | ||
| Line 18: | Line 14: | ||
JANUS <ref name="titlePortal - Janus">{{cite web |url=http://crix.nci.nih.gov/projects/janus/ |title=Portal - Janus |accessdate=2008-02-06 |format= |work=}}</ref> is a standards-based clinical data repository that utilizes the open source data model, Janus. Janus was created by FDA in partnership with IBM under a CRADA. This repository provides a data collection and analysis warehouse for clinical trial data submitted for protocols (what was supposed to happen) as well as clinical outcomes data (what did happen - events, interventions, etc.). | JANUS <ref name="titlePortal - Janus">{{cite web |url=http://crix.nci.nih.gov/projects/janus/ |title=Portal - Janus |accessdate=2008-02-06 |format= |work=}}</ref> is a standards-based clinical data repository that utilizes the open source data model, Janus. Janus was created by FDA in partnership with IBM under a CRADA. This repository provides a data collection and analysis warehouse for clinical trial data submitted for protocols (what was supposed to happen) as well as clinical outcomes data (what did happen - events, interventions, etc.). | ||
==References== | ==References== | ||
{{reflist}}[[Category:Suggestion Bot Tag]] | |||
[[Category: | |||
Latest revision as of 17:00, 29 July 2024
A clinical data warehouse or CDW is a facility that houses all electronic data collected at a clinical center [1]. For any modern clinical institute, it is necessary to separate operational data from informational data by creating a clinical data warehouse [2]. A growing number of technologies for integrating and performing structured analyses of data from disparate sources are competing to win the day for healthcare organisations [3].
The TrialDB clinical study data management system of Nadkarni et al was the first to use multiple EAV (Entity-Attribute-Value model or Object-Attribute-Value Model or Open Schema) tables, one for each database management system (DBMS) data type. The EAV/CR (with Classes and Relationships) framework, designed primarily by Luis Marenco and Prakash Nadkarni [4], overlaid the principles of object-orientation on to EAV; it also built on Slezak's object table approach. Both TrialDB and EAV/CR are open-source, though they are built on Microsoft technologies rather than Java/Linux. In Oracle Clinical, a package for the management of clinical trials data; the clinical data component is stored in an EAV structure where all values are coerced to the varchar2 data type. Here a major DBMS vendor has decided that, despite all the difficulties and hazards of working with EAV, some circumstances make its use unavoidable. [5]
The solution to warehousing the ever-changing structures of clinical data will require (a) a single, multi-trial repository based upon abstract rather than directly representational data models, and (b) adaptive, meta data-driven ETL (extract, transform and load) programming [6].
A virtual laboratory is a managed, networked collection of near patient and traditional laboratory instruments. It is Taylor et al's thesis [7] that dramatic changes in the practice of laboratory medicine will emerge. Information from point-of-care devices and laboratories will be treated in a unified manner and all devices will become components of integrated internet connected virtual laboratories. Instruments will include devices located in traditional laboratories, such as complex multi-channel analyzers and specialty laboratory tests instruments, along with point-of-care devices located at a variety of sites including clinics and at patients’ homes. Virtual laboratories will combine the immediacy offered by point-of-care devices with services offered by traditional laboratories such as quality assessment, quality control, data capture, and the dissemination of results to patients and clinicians.
JANUS [8] is a standards-based clinical data repository that utilizes the open source data model, Janus. Janus was created by FDA in partnership with IBM under a CRADA. This repository provides a data collection and analysis warehouse for clinical trial data submitted for protocols (what was supposed to happen) as well as clinical outcomes data (what did happen - events, interventions, etc.).
References
- ↑ Data Warehouse. Retrieved on 2008-02-06.
- ↑ Clinical Data Warehousing - Clinfowiki. Retrieved on 2008-02-06.
- ↑ How business intelligence is making healthcare smarter — NHS Connecting for Health. Retrieved on 2008-01-30.
- ↑ The EAV/CR Data Model. Retrieved on 2008-02-06.
- ↑ Ask Tom "Query on design". Retrieved on 2008-02-06.
- ↑ Optimal Data Architecture for Clinical Data Warehouses. Retrieved on 2008-02-06.
- ↑ Design of an Integrated Clinical Data Warehouse. Retrieved on 2008-01-30.
- ↑ Portal - Janus. Retrieved on 2008-02-06.