This page is a landing spot for LeeAnn and Andrea to share information on FHIR software development from the design and project management level.
Date:
Date:
Date:
Date:
Desired Outcomes:
Define the needs for centralization of FHIR App software development and the projects to which these apply
Define roles and responsibilities
Establish timeline(s)
Agenda
Describe the ideal situation – Kathy - 5 min
Describe each product and its current stage of development – All – 2 min
Review software development model
Discuss roles, responsibilities, timeline 35 min
Next steps 5 min
Software Development Model (LeeAnn and Andrea to further develop)
Phase 1. Requirements collection - Goal: to gather and document business requirements
Develop user stories for what you WANT the software to do
Define types of users and gather feedback from 3-5 of each type, individually via interview. Focus group(s) optional.
Gather Business Requirements and create a Charter, based on NACHC template and including stakeholders, assumptions, high-level system requirements
Phase 2. Design - Goal: to translate software development requirements into design
Write Software Requirements Document (see Table 1)
Phase 3. Software development -Goal: To build the actual software
Done by software development company in consultation with NACHC
Meet with software company periodically to go down the list of requirements and check off those that are addressed, entertain questions about any that need discussion.
Phase 4. Testing - Goal: To ensure the software meets requirements
User Acceptance Testing with 3-5 of each type of user, individually via interview. Focus group(s) optional.
Phase 5. Deployment - Goal: To deliver completed software to users
Work with CAD Comms and users to identify channels and messages
CAD Comms creates materials and disseminates
Phase 6: Continuous Improvement - Goal: To add, revise, improve functionality per user needs
Table 1
Date:
Andrea and LeeAnne
We each know what the other is thinking for software development process and user acceptance testing.
We have identified any needs/gaps in knowledge (should UAT be designed by or done by a consultant? HealthFlow does not have this strength).
Assignment – watch 1-2 videos from Linked in Learning or read a web site that explains the process of UAT.
Date:
Possible discussion topics:
Review Kathy’s comments
Discuss typical software development process - what we do, what HealthFlow does, where to find information.
Andrea ask LeeAnn for help with questionnaire
Discuss learnings from LinkedIn Learning and web research (see notes below)
Invite Sarah P to talk about what she would do differently and critique the plan?
Andrea’s notes and thoughts prompted by Linked In Learning
There is a standard software development process. HealthFlow takes direction from us, but we are not equipped, experienced, or using a traditional software development process on our end. Example of STEVE (State and Territorial Exchange of Vital Events) -I managed a major overhaul and was guided through the process by the software developers. There is a whole process starting with requirements gathering. LeeAnn dis-covered that in her thinking process, i.e., asking potential users what they want rather than starting with what we think they need.
Add Comment