1. Deliverables
1.1. Scope Statement
1.2. Requirements Document
1.3. Work Breakdown Structure
1.4. Acceptance Deliverables
1.5. Change Requests
2. Defining the Scope
2.1. Objectives
2.1.1. ED focal point for HIVE
2.1.2. Optimise local utilisation of HIVE to improve patient care, efficiency & patient flow
2.1.3. Identify and track local workflow adjustments
2.1.3.1. System updates
2.1.3.1.1. Feed forward to analysts/pathway council
2.1.3.1.2. Local development by physician builders
2.1.3.2. Smart phrases
2.1.3.3. Smart blocks
2.1.3.3.1. Local development by physician builders
2.1.3.3.2. Ticketing jobs to central analysts/pathway council
2.1.3.4. Flowsheets
2.1.4. Assist other ED working groups with projects (limited scope initially during roll out)
2.1.4.1. Governance
2.1.4.2. QIP outcomes/implementations
2.1.4.3. Senior management team
2.1.5. Representation of ED needs to MFT pathway council
2.1.6. Disseminate updates from pathway council to wider team
2.1.6.1. local awareness of system wide proformas- dissemination
2.1.7. Inspire clinicians and nursing staff to make the most of Hive
2.2. Goals
2.2.1. Track cross department/cross MDT Hive ideas/implementations
2.2.1.1. STARTING with only clinical decision making tools. POTENTIALLY the group could move across other areas. e.g. nursing/ops
2.2.1.2. Ensuring continuity & review of projects
2.2.1.3. Ensuring appropriate clinical governance oversight via HWG/SMT
2.2.1.4. Prioritize implementations based on urgency/need
2.2.1.5. initially acting as "liaison point" for clinicians with ideas--> rather than taking the whole workload
2.2.2. Create, ratify, implement workflow changes and then analyse outcome
2.2.2.1. Smartphrases/forms/flowsheets
2.2.2.1.1. Implement locally
2.2.2.1.2. Ultimately system wide /ASAP wide implementation of smartphrases/system edits
2.2.2.1.3. Review impact
2.2.2.1.4. Formally adopt to NMGH dept via pathway council/analysts
2.2.2.2. INPUT- Decide WHAT smart phrases are needed. I.e do we decide only for specific guidelines. WHY the smart phrase is important and WHAT expected outcome on patient care. will they be "enforced"
2.2.3. Create a team of local physician builders
2.2.3.1. This will enable faster system edits and approval via PWC
2.2.3.2. ?local team of advanced users for phrases
2.3. Sub-phases
2.4. Tasks
2.4.1. Member of HWB to attend every MFT pathway council. alternates person. THURS (monthly)
2.4.1.1. Take initial project plan to cons meeting then SMT week after
2.4.2. Create a live document tracking local hive issues/ideas/projects/edits
2.4.3. Develop governance protocol for approval of local smart phrases/rollout protocol. DAN
2.4.4. Implement a number of initial local smart phrases.
2.4.4.1. Disseminate these and complete an audit process
2.4.5. Recruit and train local physician builders
2.5. Resources
2.5.1. TEAM members
2.5.1.1. Medical Lead- ED Cons/SPR
2.5.1.2. ACP leads
2.5.1.3. (Nursing staff)
2.5.1.4. (Operations team)- ? nominated person in ops for input
2.5.1.5. Assisting members- lead ED cons for speciality
2.5.2. Time allocated/protected for team members (TBA)
2.6. Budget
2.7. Schedule
2.7.1. Monthly teams meeting of the HWG
2.7.2. Team representative to attend MFT pathway council