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 (eg. when retiring forms) - Cave: error reports
  • never change user configuration data w/o asking (eg. 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 textual Progress Notes
• Keeping visual Progress Notes
• Managing Allergies and Intolerances
• Managing Hospital Stays
• Managing Procedures

Medication / Substance Use Management

• Concepts

Test Results Management

• Concepts
• Adding test results
• Viewing test results

Document Management

• Concepts
• Adding documents
• Viewing archived documents
• Patient photograph handling

Workflow Management

• Using the waiting list
• Handling appointments

Module Descriptions

• Lab Module
• Implanted Cardiac Device Module

Menu Reference

• Menu Reference

Advanced Topics

• the concept of time
• the Report Generator
• paperwork
• adding Forms
• managing Users
• planning your paper to EMR transition
• planning Fax Integration

Administrator Guide

Server Maintenance

• Account/Access Management
• Client/Access Management
• Database Installation
• Going into production
• Database 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 ?
• the maxiDoc USB stick - EMR on USB drive

Licensing status of 3rd party data

• read about those licenses here

Archives: draft Developer manuals