[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Measurement workflows
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Measurement workflows |
Date: |
Tue, 9 Jul 2013 13:13:38 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Jul 08, 2013 at 11:16:14PM +0000, Jim Busser wrote:
> >> (4) "Meta type"
> >>
> >> The tooltip says "Select the meta type as which to aggregate for display
> >> results with this test type."
> >>
> >> Does this enable to create new, or only to select among existing?
> >
> > It only selects among existing.
>
> This creates a problem, because
>
> GNUmed menu > Master data > Meta test/measurement types
>
> provides only the button Edit, which on clicking provides only the dialog
>
> Showing meta test types
>
> (list of existing)
>
> [ OK ] [ Cancel ]
I know :-) You are riding the very edge of implementation ...
> Also, if one examines the dialog, what is included in an
> aggregation -- after an aggregation would exist -- is not
> clear.
The tooltip will - once implemented - say so. Like now. Your
foray into uncharted territory prompts me to make meta test
types a first class citizen of the GNUmed object universe.
> Will there exist a constraint that all items to be
> aggregated must each have a LOINC?
No. And if they do they don't need to have the same either.
> This will not result in a
> 1:1 relationship because LOINC does not in every case (if it
> does in any case) assign units which is why my in praxis
> values for
>
> weight
>
> have one value for kg and another value for pounds. I am
> not sure how to complete an aggregation for these items,
There is no GUI way in 1.3. It is currently only effectable
by other means.
> nor to achieve a conversion factor.
It is not yet needed.
> I am wondering also whether
> to differentiate weights reported to me by the patient. Are
> such values still permitted to be in measurements
Sure.
> and should they be assigned some separate test type as
>
> weight, kg, self-reported
>
> ??
If you think that to be of value, sure.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
screenshot_001.png
Description: PNG image