|
Note
|
The GNUmed Manual
Content is being resurrected from the wiki. If you need
information that is not available send us an inquiry on
either mailing list:
|
1. User Guide
1.1. Before you start
-
Principles of the GNUmed System
-
never endanger or render invalid any patient data (eg. when retiring forms) - Caveat: error reports
-
never change user configuration data w/o asking for confirmation (eg. doc types)
-
1.2. First Steps
1.3. Record Keeping
-
Keeping textual Progress Notes
-
Keeping visual Progress Notes
-
Managing Allergies and Intolerances
-
Managing Hospital Stays
-
Managing Procedures
1.4. Medication / Substance Use Management
1.5. Test Results Management
1.6. Vaccinations Management
1.7. Document Management
1.8. Workflow Management
-
Using the waiting list
-
Handling appointments
1.9. Module Descriptions
-
link:Lab Module[Lab Module]
1.10. Menu Reference
-
link:Menu Reference[Menu Reference]
1.11. Advanced Topics
-
the concept of time
-
the Report Generator
-
adding Forms
-
managing Users
-
managing Organizations / your Praxis
-
planning your paper to EMR transition
-
planning link:Fax Integration[Fax Integration]
#AdministratorGuideInManual
2. Administrator Guide
2.1. Server Maintenance
-
Database Installation
-
Database Upgrade
-
Account/Access Management
-
Client/Access Management
-
Going into production
-
Database Backup, Restore and Migration
-
Managing Reference data (including data packs)
#AdminGuideClientMaintenance
2.2. Client Maintenance
-
Installation and Upgrade (several methods are available)
-
Client Configuration
-
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
-
-
3rd party applications
-
German Krankenversichertenkarte
-
-
XML-RPC based remote control of the client
3. Developer Guide
3.1. Introduction
-
some development guidelines to keep in mind
3.2. Concepts
-
the address concept
-
the organisation concept
-
dealing with concurrent database modifications
3.3. 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
-
3.4. The Frontend
-
the APIDocumentation
-
epydoc run over the CVS source tree
-
3.5. The Middleware
-
please ask
3.6. The Source Code Repository
-
browse the Git tree on the web
3.7. 3rd party projects used with GNUmed
-
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 Orthanc DICOM server
-
the psycopg2 DB-API module
-
gmMimeMagic (magic.py): license ?
-
the FreeDiams drug reference
-
the ARRIBA CV risk calculator (free use)
-
the Ginkgo CADx (http://ginkgo-cadx.com) DICOM viewer
-
the Gelbe Liste/MMI German drug database (commercial)
3.8. Licensing status of 3rd party data
-
read about those licenses