Hostname: page-component-586b7cd67f-tf8b9 Total loading time: 0 Render date: 2024-12-01T02:29:09.486Z Has data issue: false hasContentIssue false
  • English
  • Français

Technology Transfer in Medical Information Systems: The Potential for “groupware” and its Implications

Published online by Cambridge University Press:  10 March 2009

Robert A. Greenes
Robert A. Greenes
Affiliation:
Harvard Medical School
Get access Rights & Permissions [Opens in a new window]

Abstract

The practice of medicine is intrinsically a cooperative activity, involving not only a number of individuals but requiring access to a wide variety of types of data, produced and maintained by different people. Achieving seamless, integrated access to these data requires a new infrastructure of information systems that supports the construction of applications designed to incorporate and use external information resources. The term groupware may be used to connote this collective set of information resources and tools for access to them. Groupware will generate a variety of new kinds of products and services with implications for medical libraries, electronic publishing, and academic and professional collaboration.

Type
Special Section: Industry and the Generation of Technology, Part II
Information
International Journal of Technology Assessment in Health Care , Volume 9 , Issue 3 , Summer 1993 , pp. 324 - 334
Copyright
Copyright © Cambridge University Press 1993

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

REFERENCES

1.ACR-NEMA digital imaging and communications standard. Publication No. 300–1985. Washington, DC: National Electrical Manufacturers Assoc., 1985.Google Scholar
2.ARL, CAUSE, and EDUCOM announce the Coalition for Networked Information. Press Release, 03 16, 1990.Google Scholar
3.Blum, B. I.Cinical information systems: A review. Western Journal of Medicine, 1986, 145, 791–97.Google Scholar
4.Ellis, C. A., Gibbs, S. J., & Rein, G. L.Groupware: Some issues and experiences. Communications ACM, 1991, 34, 38–58.CrossRefGoogle Scholar
5.Fisher, F. D.The electronic lumber yard and builders' rights: Technology, copyrights, patents, and academe. Change, 1989, 21(3), 13–21.CrossRefGoogle Scholar
6.Gallagher, L., (ed.). Proceedings Hypertext Standardization Workshop. Gaithersburg, MD: National Institute of Standards and Technology, 1990.Google Scholar
7.Greenes, R. A.Desktop knowledge: A new focus for medical education and decision support. Methods of Information in Medicine, 1989, 28(4), 332–39.Google ScholarPubMed
8.Greenes, R. A. Medical informatics: Academic and institutional perspectives of an emerging specialty. Proceedings Computer in Health Sciences Symposium, Newark, N November 1988, 1–7.Google Scholar
9.Greenes, R. A., & Deibel, S. R. A.The DeSyGNER knowledge management architecture: A building block approach based on an extensible kernel. Artificial Intelligence in Medicine, 1991, 3, 95–111.CrossRefGoogle Scholar
10.Greenes, R. A.,Tarabar, D. B., Cope, L., et al. Explorer-2: An object-oriented framework for knowledge management. ProceedingsMEDINFO89, Singapore. Amsterdam: Elsevie Science Publishers, 1989, 29–33.Google Scholar
11.Health level seven standards: An application protocol for electronic data exchange in health care environments, version 2, HL7. Philadelphia, PA: HL7, 1988, 1–15.Google Scholar
12.Humphreys, B. L., & Lindberg, D. A. B. Building the Unified Medical Language System. Proceedings Thirteenth Annual Symposium on Computer Applications in Medical Care (SCAMC), Washington, DC. New York: IEEE Computer Society Press, 1989, 475–80.Google Scholar
13.Kahin, B. Toward public information infrastructure: Information policy and the Internet. Report prepared for U.S. Congressional Office of Technology Assessment, Contract No. L3-5445.0, 05 15, 1990.Google Scholar
14.McDonald, C., & Hammond, W.Standard formats for electronic transfer of clinical data. Annals of Internal Medicine, 1989, 110, 333–35.CrossRefGoogle ScholarPubMed
15.MIPS Staff. Graphical user interface now. MIPS Magazine, 1989, 1, 42–50.Google Scholar
16.Nelson, T. H.Literary machines. San Antonio: Project Xanadu, 1987.Google Scholar
17.Neufeld, V. R., Woodward, C. A., & MacLeod, S. M.The McMaster MD program: A case study of a renewal in medical education. Academic Medicine, 1989, 64, 423–32.CrossRefGoogle Scholar
18.Open Systems Interconnection (OSI) standard architecture and protocols. In Folts, H. C. & Des Jardin, R. (eds.), Proceedings of the Institute of Electric and Electronic Engineers. Washington, DC: IEEE Computer Society Press, 1983.Google Scholar
19. Paperwork Reduction and Federal Information Resources Management Act of 1989, 11 17, 1989.Google Scholar
20.Physicians for the twenty-first century: The GPEP report. Report of the Panel on the General Professional Education of the Physician and College Preparation for Medicine. Washington, DC: American Association of Medical Colleges, 1984.Google Scholar
21.Software: It’s a new game. Business Week, 1990, 3162, 102–05.Google Scholar
22.Tosteson, D. C.New pathways in general medical education. New England Journal of Medicine, 1990, 322, 234–38.CrossRefGoogle ScholarPubMed