[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] encounter type pre-selection
From: |
Karsten Hilbert |
Subject: |
[Gnumed-devel] encounter type pre-selection |
Date: |
Mon, 17 Jun 2013 19:46:33 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
I have implemented a long-standing FIXME:
When creating a new encounter GNUmed first looks whether
"encounter.default_type" is set.
If not it will now (and that's new) look for the most
commonly used encounter type in the database (this is likely
a sane default in most cases). Potential problems:
- there's a close tie between several types which might make
it bounce back and forth based on current usage
- there's a perfect tie between several types which will
return the alphabetically lowest type by localized name.
If there are no encounters just yet it will fall back to "in
surgery" (as it always did).
If THAT doesn't work out it will fall back to whatever has
got PK=1 in clin.encounter_type (like it did before). There
better be one :-)
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-devel] encounter type pre-selection,
Karsten Hilbert <=