Develop "patient overview" widget to inform as "initial plug-in" after a patient search

Bug #268522 reported by Saša Janiška
0
Affects Status Importance Assigned to Milestone
GNUmed
Fix Released
Wishlist
Unassigned

Bug Description

Wed 16 Jan 2008 10:16:32 PM UTC, original submission:

Possible content:

- Disabilities that may affect communication, or cognition, or care access, or caregivers if patient is not fully competent
- Active and/or relevant problems from EMR tree
- Existence of inbox items, filtered on patient
- Existence of unreviewed incoming labs, documents, communications
- Existence of to-do items
- Next visit date

(providing links to the item areas, if not showing the items themselves)

--> item copied to wiki ToDo
http://salaam.homeunix.com/bin/view/Gnumed/ToDo#develop_patient_overview_widget

Revision history for this message
Saša Janiška (gour) wrote :

Thu 24 Jan 2008 01:08:51 PM UTC, comment #1:

This should be moved to the TODO list on our Wiki.

Changed in gnumed:
importance: Undecided → Medium
Changed in gnumed:
importance: Medium → Wishlist
Revision history for this message
ncq (karsten-hilbert) wrote : Re: [Bug 268522] Re: Develop "patient overview" widget to inform as "initial plug-in" after a patient search

-------- Original-Nachricht --------
> Datum: Wed, 10 Sep 2008 12:27:05 -0000
> Von: Gour <email address hidden>
> An: <email address hidden>
> Betreff: [Bug 268522] Re: Develop "patient overview" widget to inform as "initial plug-in" after a patient search

> Thu 24 Jan 2008 01:08:51 PM UTC, comment #1:
>
> This should be moved to the TODO list on our Wiki.

It should already be there, no ?

> --
> Develop "patient overview" widget to inform as "initial plug-in" after a
> patient search
> https://bugs.launchpad.net/bugs/268522
> You received this bug notification because you are a member of GNUmed
> development, which is subscribed to GNUmed.
>
> Status in GNUmed - electronic medical record: New
>
> Bug description:
> Wed 16 Jan 2008 10:16:32 PM UTC, original submission:
>
> Possible content:
>
> - Disabilities that may affect communication, or cognition, or care
> access, or caregivers if patient is not fully competent
> - Active and/or relevant problems from EMR tree
> - Existence of inbox items, filtered on patient
> - Existence of unreviewed incoming labs, documents, communications
> - Existence of to-do items
> - Next visit date
>
> (providing links to the item areas, if not showing the items themselves)

--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196

Jim Busser (jbusser)
description: updated
Revision history for this message
Saša Janiška (gour) wrote :

I didn't check - just copied old tracker's content to LP.

If it's on TODO, then maybe we can open a blueprint which connects to it?

Sincerely,
Gour

Revision history for this message
Jim Busser (jbusser) wrote : Launchpad Blueprints vs Bug vs Wiki todo-list

was Re: [Bug 268522] Re: Develop "patient overview" widget to inform
as "initial plug-in" after a patient search

==========================

Blueprint opened.

I expect a Launchpad "blueprint" is best used for things like modules
or other functionality that needs to be built.

Should it also be used to store and manage the status of ToDo items?
I am looking to make clear any separation between what we would want
as bug-reportable items which are however just wishlist, from
anything we would wish to log as a Blueprint request.

For example my suggestion that in the Progress notes, the datetime
stamp and last-editor of a SOAP note be "unwrapped" to make the
clinical content easier to read, also Rogerios's offlist suggestion
that an extra line of white space be added between sections... where
shall we put these?

Maybe the guide should be:

- if it needs enough detail that the detail should link to a
description on the wiki of what is needed, it should be a Blueprint
item.

- if it is only a request that something be changed or adjusted which
requires minimal other information, let it be a bug-report-requested
wishlist item?

Basically I am wondering how much of what is on the ToDo list page
could / should be migrated off into Bugs and Blueprints?

On 10-Sep-08, at 9:29 AM, Gour wrote:

> If it's on TODO, then maybe we can open a blueprint which connects to
> it?
>
>
> Sincerely,
> Gour
>
> --
> Develop "patient overview" widget to inform as "initial plug-in"
> after a patient search
> https://bugs.launchpad.net/bugs/268522
> You received this bug notification because you are a member of GNUmed
> development, which is subscribed to GNUmed.

Revision history for this message
ncq (karsten-hilbert) wrote : Re: [Gnumed-devel] Launchpad Blueprints vs Bug vs Wiki todo-list

I am still not sure about the license of Blueprint *content*. If that would be required to be
BSD we might want to be careful with it - should someone hit on a killer idea and document
it as a blueprint then Canonical would gain rights to market that idea as closed source (if it was BSD licensed).

Karsten

-------- Original-Nachricht --------
> Datum: Thu, 11 Sep 2008 16:52:13 -0700
> Von: James Busser <email address hidden>
> An: GNUmed list <email address hidden>
> CC: Bug 268522 <email address hidden>
> Betreff: [Gnumed-devel] Launchpad Blueprints vs Bug vs Wiki todo-list

> was Re: [Bug 268522] Re: Develop "patient overview" widget to inform
> as "initial plug-in" after a patient search
>
> ==========================
>
> Blueprint opened.
>
> I expect a Launchpad "blueprint" is best used for things like modules
> or other functionality that needs to be built.
>
> Should it also be used to store and manage the status of ToDo items?
> I am looking to make clear any separation between what we would want
> as bug-reportable items which are however just wishlist, from
> anything we would wish to log as a Blueprint request.
>
> For example my suggestion that in the Progress notes, the datetime
> stamp and last-editor of a SOAP note be "unwrapped" to make the
> clinical content easier to read, also Rogerios's offlist suggestion
> that an extra line of white space be added between sections... where
> shall we put these?
>
> Maybe the guide should be:
>
> - if it needs enough detail that the detail should link to a
> description on the wiki of what is needed, it should be a Blueprint
> item.
>
> - if it is only a request that something be changed or adjusted which
> requires minimal other information, let it be a bug-report-requested
> wishlist item?
>
> Basically I am wondering how much of what is on the ToDo list page
> could / should be migrated off into Bugs and Blueprints?
>
>
> On 10-Sep-08, at 9:29 AM, Gour wrote:
>
> > If it's on TODO, then maybe we can open a blueprint which connects to
> > it?
> >
> >
> > Sincerely,
> > Gour
> >
> > --
> > Develop "patient overview" widget to inform as "initial plug-in"
> > after a patient search
> > https://bugs.launchpad.net/bugs/268522
> > You received this bug notification because you are a member of GNUmed
> > development, which is subscribed to GNUmed.
>
>
>
> _______________________________________________
> Gnumed-devel mailing list
> <email address hidden>
> http://lists.gnu.org/mailman/listinfo/gnumed-devel

--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196

ncq (karsten-hilbert)
Changed in gnumed:
status: New → Confirmed
ncq (karsten-hilbert)
tags: removed: savannah-tracker
Revision history for this message
shilbert (sebastian-hilbert) wrote :

This will be made available with the upcoming release GNUmed 1.2

Changed in gnumed:
status: Confirmed → In Progress
ncq (karsten-hilbert)
Changed in gnumed:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.