GNUMed: Developers's Manual
Prev
Next
Chapter 5. Design
Table of Contents
5.1.
GNUMed Database Architecture
5.1.1.
Client-Server architecture with optional middleware layers
5.1.2.
Distribution of database services
5.1.3.
Normalization of data
5.1.4.
Audit trailing
5.1.5.
Access control
5.1.6.
Multigenerational concurrency control and backups
5.2.
List of distributed database services
5.2.1.
Configuration - the service administering all other services
5.2.2.
Person related services
5.2.3.
Medical history related services
5.2.4.
External results
5.2.5.
Correspondence
5.2.6.
Pharmaceutical reference
5.2.7.
General medical reference
5.2.8.
Decision support database
5.2.9.
Large binary objects (BLOBS)
5.2.10.
Accounting related services
5.2.11.
Office related services
5.3.
List of GnuMed client internal signals
5.4.
FAQ
5.5.
Gnumed EMR
5.5.1.
Required reading
5.5.2.
Structural considerations
5.5.3.
Implementation considerations
5.5.4.
Medical relation between entities
5.6.
Table auditing
5.6.1.
INSERT
5.6.2.
UPDATE/DELETE
5.6.3.
SELECT
5.6.4.
How to add an audit trail to a table
5.6.5.
Audit trail handling
5.7.
GUI design
5.7.1.
General
5.7.2.
Date Entry Paradigm - The Editing Area
5.7.3.
Full Screen Design
5.8.
Login Screen
5.8.1.
Short description
5.8.2.
Data Shown/Accessible
5.8.3.
Functionality
5.8.4.
Internals / Additional Information
5.9.
Main Toolbar
5.9.1.
Short Description
5.9.2.
Data Shown/Accessible
5.9.3.
Functionality
5.9.4.
Internals / Additional Information
5.10.
Pharmaceutical Reference Browser
5.10.1.
Short Description
5.10.2.
Data Shown/Accessible
5.10.3.
Functionality
5.10.4.
Internals / Additional Information
5.11.
Prescription Dialog
5.11.1.
Short Description
5.11.2.
Data Shown/Accessible
5.11.3.
Functionality
5.11.4.
Internals / Additional Information
5.12.
Appointment book
5.12.1.
Functionality
5.12.2.
The "schedule widget"
5.12.3.
Calendar navigation
5.12.4.
Context sensitive popup menus
5.12.5.
TO DO:
Prev
Home
Next
wxpython/patient - "patient page" plugin widgets
GNUMed Database Architecture