Technology Continuum
Options for registry technical architectures can be mapped along a continuum, ranging from "low tech" to "high tech" solutions:
![]()
Different solutions are appropriate for different components of the architecture, particularly those involved in data capture versus data access. Mixing and matching components from along this continuum must be done prudently when assembling an optimal architectural solution. In most cases, operating procedures at provider clinics need to change to accommodate the registry.
Online Web Application
Data entry and/or data query are performed through an application ("thin client") accessed through a standard web browser.
Strengths Weaknesses data remains on a central server and is current whenever users are accessing
"thin" client little desktop support beyond browser and necessary "plug-ins"
GUI
many users already using Web browsers for other purposes
cross platform support easier (if application designed carefully)
good possibilities for integration of multi-media elements into an application, including educational material and resources out on the Web application development tools immature but getting better difficult to select in an expanding marketplace
performance likely not be as good as other options
requires a robust TCP/IP network to function properly
printer support may be difficult for some kinds of web pages
may be difficult to maintain "state" (i.e., sense of a continuing browser to server session)
three tier architecture (browser, web/application server, data server) may be difficult to develop and support requires more robust data and application servers than may be currently deployed