[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Measurements - adding and abbreviations

From: Jim Busser
Subject: Re: [Gnumed-devel] Measurements - adding and abbreviations
Date: Tue, 19 Jul 2011 22:45:32 -0700

-- Jim

On 2011-07-19, at 9:57 PM, Jim Busser wrote:

> Also, new measurements result in null values for
>       code, coding_system
> How shall these better be handled?


1) upon selecting from the phrasewheel (or in putting an exact match) for an 
existing test_type, can the value for


be refreshed to take the value from conversion_unit


2) when the inputter of a measurement is a clinician, given that the current 
user should in gnumed-future pre-populate

        "In charge" (fk_intended_reviewer)

then can the

        Review: [  ] SIgn as

checkbox be pre-checked?

(I recognize that the user must still decide whether to mark the result as 
'abnormal' or 'relevant')

(this can BTW risk to become a medicolegal issue unless the view is taken in a 
praxis that it is the signature that is most important – from the point of view 
of "acknowledging" what an assistant might have entered – whereas 
non-completion of the other checkboxes ('abnormal' or 'relevant') can be argued 
as decisions about flagging… it can be possible to know in a given patient 
whether the blood pressure of 140/90 is acceptable or not based on other 
information about the patient and to have to complete every check-box with 
every measurement becomes non-added-value.

Ideally the target could be set per-patient and, in the case of any new 
measurement, could pre-populate the target fields based on the measurement code 
of interest if a target had been previously defined for the patient.

-- Jim

reply via email to

[Prev in Thread] Current Thread [Next in Thread]