Search PubMedSearch

PubMed · 8289604

Guidelines for creating a simple database.

Abstract

The advantage of using a simple flat file program is its simplicity and flexibility. The user has control over screen and report design; creating a database that meets the specific needs of a single department is easy and inexpensive. On the other hand, flat file programs have limitations. The main problem with Q&A is the need to duplicate data in two or more files. Other limitations are a result of the menu-oriented system, which requires compromises in report formatting and other areas. Database management systems are improving rapidly. Relational databases are becoming easier to use and can overcome many of the limitations of a flat file system. Flat file systems are becoming more enhanced and are beginning to look relational. Developing a system using a simple flat file approach allows the novice to identify and use information without conceptualizing a relational structure. Information can be entered and used quickly, with a better understanding of how everything works. Fewer things can go wrong and need fixing. Keeping your systems simple and following our other guidelines will allow you to use the computer as a tool to increase productivity.

Explore related subjects

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

A L Harroff, M A France, J R Hayes. Guidelines for creating a simple database.. https://pubmed.ncbi.nlm.nih.gov/8289604/

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

KEEP EXPLORING

Related citations

Adopting a corporate perspective on databases. Improving support for research and decision making.

The Veterans Health Administration (VHA) is at the forefront of designing and managing health care information systems that accommodate the needs of clinicians, researchers, and administrators at all levels. Rather than using one single-site, centralized corporate database VHA has constructed several large databases with different configurations to meet the needs of users with different perspectives. The largest VHA database is the Decentralized Hospital Computer Program (DHCP), a multisite, distributed data system that uses decoupled hospital databases. The centralization of DHCP policy has promoted data coherence, whereas the decentralization of DHCP management has permitted system development to be done with maximum relevance to the users'local practices. A more recently developed VHA data system, the Event Driven Reporting system (EDR), uses multiple, highly coupled databases to provide workload data at facility, regional, and national levels. The EDR automatically posts a subset of DHCP data to local and national VHA management. The development of the EDR illustrates how adoption of a corporate perspective can offer significant database improvements at reasonable cost and with modest impact on the legacy system.

Database Management Systems

Population health and health care use: an information system for policy makers.

University-based researchers in Manitoba, Canada, have used administrative data routinely collected as part of the national health insurance plan to design a population-based health information system (POPULIS). Decision-makers can use this system to make critical comparisons across regions of residents' health status, socioeconomic risk characteristics, and use of hospitals, nursing homes, and physicians. Policy makers have found this information system useful in providing answers to questions they are often asked: Which populations need more physician services? Which need fewer? Are high-risk populations poorly served or do they have poor health outcomes despite being well served? Does high utilization represent overuse or is it related to high need? Three commentaries follow.

Database Management Systems