[OpenVPMS Developers] [JIRA] Created: (OVPMS-975) Add support for clinician 'follow up' work lists

Add support for clinician 'follow up' work lists ------------------------------------------------

Key: OVPMS-975 URL: https://openvpms.atlassian.net/browse/OVPMS-975 Project: VPMS Web Application Issue Type: Improvement Components: Workflow Affects Versions: 1.4 Reporter: Tim Anderson Assignee: Tony De Keizer

From http://www.openvpms.org/project/followup-task-lists-enhancements

# Add support in associate work lists with a clinician This requires changes to security.user to add a node with a 0..* relationship to party.organisationWorkList If a clinician has multiple work lists, one should be marked as the default There is only a single user archetype (security.user) so the app needs to restrict work lists to those with a CLINICIAN classification # Add support to create 'follow up' tasks for the current clinician and their default work list This will prompt for a date and notes and create the a follow-up task in the clinicians default follow-up worklist. If no worklist is assigned to the clinician the system will prompt for one. # Add buttons to create follow up tasks to the: #* Patient Information workspace #* Patient Medical Records workspace #* Customer workspaces (Information, any others?) Alternatively, they could be added at the bottom of the customer and patient summary, depending on L&F # Add a status area beneath the customer and patient summary to display the no. of messages and follow ups. Based on the start date of the follow up task could even say "you have 3 messages, 5 current and 3 overdue follow up's" etc. # Include a button in the status area to go to the current clinician's default work list in the Work Lists workspace

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

[OpenVPMS Developers] [JIRA] Updated: (OVPMS-975) Add support fo

[ https://openvpms.atlassian.net/browse/OVPMS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Anderson updated OVPMS-975: -------------------------------

Original Estimate: 12h Remaining Estimate: 12h Description: From http://www.openvpms.org/project/followup-task-lists-enhancements

# Add support in associate work lists with a clinician This requires changes to security.user to add a node with a 0..* relationship to party.organisationWorkList If a clinician has multiple work lists, one should be marked as the default There is only a single user archetype (security.user) so the app needs to restrict work lists to those with a CLINICIAN classification # Add support to create 'follow up' tasks for the current clinician and their default work list This will use the existing Task editor, but display the clinician's default follow-up worklist. The work list may be changed to another associated with the clinician. If the current clinician has no work lists, raise an error and don't launch the editor # Add buttons to create follow up tasks to the: #* Patient Information workspace #* Patient Medical Records workspace #* Customer workspaces (Information, any others?) Alternatively, they could be added at the bottom of the customer and patient summary, depending on L&F # Add a status area beneath the customer and patient summary to display the no. of messages and follow ups. Based on the start date of the follow up task could even say "you have 3 messages, 5 current and 3 overdue follow up's" etc. # Include a button in the status area to go to the current clinician's default work list in the Work Lists workspace

was: From http://www.openvpms.org/project/followup-task-lists-enhancements

# Add support in associate work lists with a clinician This requires changes to security.user to add a node with a 0..* relationship to party.organisationWorkList If a clinician has multiple work lists, one should be marked as the default There is only a single user archetype (security.user) so the app needs to restrict work lists to those with a CLINICIAN classification # Add support to create 'follow up' tasks for the current clinician and their default work list This will prompt for a date and notes and create the a follow-up task in the clinicians default follow-up worklist. If no worklist is assigned to the clinician the system will prompt for one. # Add buttons to create follow up tasks to the: #* Patient Information workspace #* Patient Medical Records workspace #* Customer workspaces (Information, any others?) Alternatively, they could be added at the bottom of the customer and patient summary, depending on L&F # Add a status area beneath the customer and patient summary to display the no. of messages and follow ups. Based on the start date of the follow up task could even say "you have 3 messages, 5 current and 3 overdue follow up's" etc. # Include a button in the status area to go to the current clinician's default work list in the Work Lists workspace

> Add support for clinician 'follow up' work lists > ------------------------------------------------ > > Key: OVPMS-975 > URL: https://openvpms.atlassian.net/browse/OVPMS-975 > Project: VPMS Web Application > Issue Type: Improvement > Components: Workflow > Affects Versions: 1.4 > Reporter: Tim Anderson > Assignee: Tony De Keizer > Original Estimate: 12h > Remaining Estimate: 12h > > From http://www.openvpms.org/project/followup-task-lists-enhancements > # Add support in associate work lists with a clinician > This requires changes to security.user to add a node with a 0..* relationship to party.organisationWorkList > If a clinician has multiple work lists, one should be marked as the default > There is only a single user archetype (security.user) so the app needs to restrict work lists to those with a CLINICIAN classification > # Add support to create 'follow up' tasks for the current clinician and their default work list > This will use the existing Task editor, but display the clinician's default follow-up worklist. > The work list may be changed to another associated with the clinician. > If the current clinician has no work lists, raise an error and don't launch the editor > # Add buttons to create follow up tasks to the: > #* Patient Information workspace > #* Patient Medical Records workspace > #* Customer workspaces (Information, any others?) > Alternatively, they could be added at the bottom of the customer and patient summary, depending on L&F > # Add a status area beneath the customer and patient summary to display the no. of messages and follow ups. > Based on the start date of the follow up task could even say "you have 3 messages, 5 current and 3 overdue follow up's" etc. > # Include a button in the status area to go to the current clinician's default work list in the Work Lists workspace

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf

Syndicate content