# The GNUmed Manual

## User Guide | Administrator Guide | Developer Guide

## User Guide

### What you need to know

- Principles of the GNUmed System
  - never endanger or render invalid any patient data (such as when providing new forms versions)
    - (understand the above, in reference to GNUmed Error reports which might contain sensitive information, and which you need to judge if it is OK to send)
  - never change user configuration data w/o asking (such as doc types)
- Using the GNUmed Client User Interface
- Understanding the GNUmed EMR

### First Steps

- Starting Gnumed
- Getting to know Gnumed
- Basic Patient Handling
- Basic Usage Tips
- Structuring the EMR

### Record Keeping

- Concepts
- Keeping Progress Notes
- Managing Allergies and Intolerances

### Document Management

- Concepts
- Adding documents
- Viewing archived documents
- Patient photograph handling
- Writing medical (and other) letters

### Test Results Management

- Concepts
- Adding test results
- Viewing test results

### Module Descriptions

- Lab Module

### Menu Reference

- Menu Reference

### Advanced Topics

- the concept of time
- the Report Generator
- adding Forms
- managing Users
- handling appointments
- how to make the paper to EMR transition?

## Administrator Guide

### Server Maintenance

- Account Management
- Database Installation and Upgrade
- Database Backup, Restore and Migration

### Client Maintenance

- Installation and Upgrade (several methods are available)
- Client Configuration
  - Configuration Files
  - Customizing client startup
  - Customizing backend login
  - Hooking into the client workflow
  - Configuring client behaviour (options)
  - Managing master data (reference data sets)
  - Customizing document management
  - Customizing patient search
  - External patient interface
    - 3rd party applications
    - German Krankenversichertenkarte
  - XML-RPC based remote control of the client
- Routine Maintenance

### Tested/Suggested Hardware

- Image Scanner
- Digital Cameras
- Mobile Phones

## Developer Guide

### Introduction

- some development guidelines to keep in mind

### Concepts

- the address concept
- dealing with concurrent database modifications

### The Backend

- database revision handling
- the database structure - a conceptual view
- the full database schema
  - generated daily from a cron job
  - gnumed/client/doc/make-schemadocs.sh -> pg_autodoc
- i18n/l10n issues

### The Frontend

- Design Decisions
- the APIDocumentation
  - epydoc run over the CVS source tree
- Internationalization

### The Middleware

- please ask

### The Source Code Repository

- monitor CVS activity
- browse the CVS tree on the web

### 3rd party projects used with GNUmed

- libchipcard
- the TWAIN Python binding: GPLv2
- the Python Imaging Library (PIL): BSD license (Original)
- the XSane scanning frontend
- the Aeskulap DICOM viewer
- the XMedCon DICOM viewer
- the psycopg2 DB-API module
- gmMimeMagic (magic.py): license ?

### Licensing status of 3rd party data

- read about those licenses here

Archives: draft Developer manuals