HCD Design
Introduction:
- What is HCD?
- Use of this Guide
- Considerations:
- Continuous participation
- Patient perspective
- Virtual design
- Measurement and Data Quality
- Spread and scale
Pre-Project Data Gathering:
Intro documentation from stakeholders-
- Logo, mission statement, basic health center/patient data, roles/titles/contact info (Sarah)
Technology capacity: EHR and HIT system info (Raymonde)
Phase 1: Setting the Stage-- HCD document (Sarah)
Pre-Work:
- Stakeholder identification (look at the example stakeholders and roles)
- Contact List
- Roles
- Leadership Buy-In
- Resources
- Environmental Scan
- Materials of interest, Policies and Procedures/SOP, Evidence/Research, Tools and Manuals, Existing Measures
- Needs/Gap analysis
- Each stakeholder should bring a list-- ideally done with their partner stakeholders they represent in a brainstorming session
- Facilitator can ideally do some collation of major issues
- Bring no more than top 2-3 to the group for discussion
- Goals, Scope, Outcomes
- Each stakeholder should define or describe a goal: can be a combination of values/vision and goal statement
- In Scope: what the scope start and end is, who is involved
- Out of Scope: what cannot be controlled by the team, beyond the start or end of the scope
- Outcomes: measures of success (AND failure)
- Clinical
- Experience (patient and care team)
- Financial (payment, equipment, facilities, staffing)
- Process (time, materials, waiting, etc)
Design Meeting:
- Introduction:
- Roles, rules and responsibilities
- Review background materials: summary of environmental scan, stakeholders and gaps
Continuous Improvement (throughout):
- Decision Log
- Lessons Learned Document
- Timeline/Milestones -- (Gantt if available)
- Swim Lanes (for partners-- should incorporate timeline/milestones)
- Project Principles and Rules of the Road--Norms/Guidelines
Phase 2: Understanding the Context (Ray/Julia)
- Personas -- examples, guidance
- Use Cases -- examples, guidance
- Metrics-- Definitions: quality measures, operational measures, patient and care team experience, resources, clinical outcomes
- Data Categories
- Workflow--slides, journal article, examples -- with description of relationship to dataflow (Raymonde)
Phase 3: Understanding the Data (Pedro)
- Dataflow
- Data Validation Plan
- Feasibility/workflow/extraction evaluation
- Data QA
- Data Dictionary
- Baseline Measures
- Baseline Data
Phase 4: Designing a Solution
- Intervention Brainstorming
- Technical Plan
- Standards
- Terminology content
- Data model/element specifications
- API or data extraction
- Conformance Testing
- Site Architecture
- Interoperability Planning
- Site Integration
- Implementation Plan
- Integration Considerations
- Timeline
- Implementation Scope
- User Requirements and User Data
- Training
- Implementation Package
- Evaluation Package-- metrics
- Testing Plan
- Feedback to Users
- Feedback from Users
- Change Plans
- Technical Assistance Plan
- Dashboards and Feedback
- Project Outcomes and Modifications
- Training Package
- Local training materials
Phase 5: Implement and Evaluate
- Build solutions
- Test
- Improve and finalize initial stage
- Implement pilot
- Evaluate
- Plan for scale
- Implementation Guide
Phase 6: Scale and Maintain
- Rollout plan
- Evaluation plan
- Feedback from users
- Maintenance
Curriculum Materials:
- HCD 2 pager--> convert to 1 pager
- HCD graphic
- Gantt chart
- Powerpoint
- Data Dictionary Template
- Data Reference Document
- HCD User Guide
- Branding Materials
Technical Plan:
Standardized content across implementation sites-- describes HIT standards, terminology requirements, transport and data standards, validation and testing requirements, data dictionary, measure specifications, generic flows
Implementation Plan:
Individual site/system level specifications for the technical plan and local requirements
Dear Confluence Users, If you need support for use of Atlassian tools, please contact informatics@nachc.com whether you have technical issues, need feature assistance, or simply have questions.