On 19/11/2014 14:04, Karsten Hilbert wrote:
> On Wed, Nov 19, 2014 at 01:35:06PM +0000, Thomas Beale wrote:
>
>> Consider: the proof that something
>> really is considered a 'problem', out of all the non-problems and trivial
>> problems (e.g. one-off throat infection) is that some clinical professional
>> wants to create a care plan, to define ongoing treatment and track
>> interventions (all medications, other interventions etc).
> While I agree that that's something to consider I am creating
> "care plans" all day, for both "complex" and "trivial"
> problems. It is very much in the eye of the beholder what's
> trivial and what's not. My patients are so much the happier
> for their "plan" for "one-off throat infection".
>
> It's an interesting point of view.
>

well that's my point actually. If a doc wants to create a care plan for 
X, then X for patient P is by definition a 'problem' in that doc's 
opinion, and consequently in P's care. So there it doesn't matter what 
the problem is - fractured toe or cancer, it's up to some health care 
professional to decide. I am just thinking of abstractions that can be 
usefully concretised to provide a good framework for applications to 
enable the patients care team to do their work, and to find & create 
information in a natural way.

- thomas

Reply via email to