Start Your Search
RF07 - Techniques to Accelerate Innovation (ID 28)
- Event: e-Health 2018 Virtual Meeting
- Type: Rapid Fire Session
- Track: Health Business Process
- Presentations: 1
- Coordinates: 5/29/2018, 01:00 PM - 02:00 PM, Fairview I Room, Conference Level
RF07.01 - Staying Agile in HCIS Development (ID 511)
Purpose/Objectives: To describe the creation and development of electronic documentation for clinicians following an agile philosophy that was adapted for use for a large organization with multiple stakeholders. We will review the process, outcomes, successes and lessons learned. In November 2016, the Fraser Health Authority (FHA) implemented electronic documentation at Abbotsford Regional Hospital and Cancer Centre. This was part of a large-scale project called the Integrated Plan of Care (IPOC) and began in 2015. The IPOC project involved multiple stakeholders and the utilization of many resources.
Methodology/Approach: The IPOC project required iterative development with frequent inspection and adaptation, so an agile approach was needed. This philosophy also promotes a leadership style that fosters teamwork and accountability. Agile principles were applied to the IPOC project, with a breakdown of work into sprints and scrums. A sprint is a set period of time during which a defined package of work needs to be completed. A scrum is a short meeting that includes the design and build team to review progress and identify obstacles. In the IPOC, a sprint was the development of each clinical departments documentation with the following phases: an opening day, daily or every second day scrums until complete, and a closing day. Each phase followed a pre-determined script for consistency from one sprint to another. Each sprint consisted of the preliminary build, quality assurance review, final build, stakeholder testing, e-safety and data integrity review.
Finding/Results: Utilizing an agile philosophy for the IPOC project allowed us to identify a large percentage of documentation requirements early in the build, provided a platform for rapid development and accommodated unexpected changes. This also facilitated the detailed tracking of the build progress, and created opportunities for team members to connect on a regular basis with their clinical counterparts. Findings/Results include, but are not limited to: - Resourcing the build with part time staff or staff that had additional duties were a detriment as the project could not maintain the philosophy of an agile process. - Stakeholders reviewing the electronic documentation build need to be engaged as delayed response time slowed down the development cycles. - Unclear role definitions and expectations lead to assumptions around task responsibility and lack of communication. - Lack of predetermined build practices and not following naming convention guidelines and processes lead to inconsistency in product and frequent rebuilds.
Conclusion/Implications/Recommendations: Using an agile philosophy in the IPOC project to implement electronic documentation contributed to the success of the project. Our recommendations include: use of an agile philosophy for informatics projects; ensure staff are dedicated solely to the project during the build, ensure roles and expectations are clearly defined, clearly define build practices and naming conventions and to guarantee stakeholders are engaged with defined timelines for feedback in order to keep the development cycles on track.
140 Character Summary: To describe the creation and development of electronic documentation for clinicians following an agile philosophy that was adapted for use for a large organization with multiple stakeholders. We will review the process, outcomes, successes and lessons learned.
Only Active Members that have purchased this event or have registered via an access code will be able to view this content. To view this presentation, please login or select "Add to Cart" and proceed to checkout.