Search PubMed⌕ Search

PubMed · 14725350

Federating data with Information Integrator.

Abstract

Information Integrator is an extension to IBM's relational database DB2, which uses data federation to provide benefits to molecular biology researchers through two unique capabilities: increased flexibility in combining data from disparate sources, and SQL access to non-SQL data, easing the task of automating data analysis.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Andrew D Arenson. 2003. Federating data with Information Integrator.. https://doi.org/10.1093/bib%2F4.4.375

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related citations

Development of an information model for storing organ donor data within an electronic medical record.

OBJECTIVE: To develop a model to store information in an electronic medical record (EMR) for the management of transplant patients. The model for storing donor information must be designed to allow clinicians to access donor information from the transplant recipient's record and to allow donor data to be stored without needlessly proliferating new Logical Observation Identifier Names and Codes (LOINC) codes for already-coded laboratory tests. DESIGN: Information required to manage transplant patients requires the use of a donor's medical information while caring for the transplant patient. Three strategies were considered: (1) link the transplant patient's EMR to the donor's EMR; (2) use pre-coordinated observation identifiers (i.e., LOINC codes with *(wedge)DONOR specified in the system axes) to identify donor data stored in the transplant patient's EMR; and (3) use an information model that allows donor information to be stored in the transplant patient's record by allowing the "source" of the data (donor) and the "name" of the result (e.g., blood type) to be post-coordinated in the transplant patient's EMR. RESULTS: We selected the third strategy and implemented a flexible post-coordinated information model. There was no need to create new LOINC codes for already-coded laboratory tests. The model required that the data structure in the EMR allow for the storage of the "subject" of the test. CONCLUSION: The selected strategy met our design requirements and provided an extendable information model to store donor data. This model can be used whenever it is necessary to refer to one patient's data from another patient's EMR.

Databases as Topic↗