Desired Outcomes:

1. Define the needs for centralization of FHIR App software development and the projects to which these apply

2. Define roles and responsibilities

   1. Julia and Ray are ultimate owner of the FHIR apps - they are SMEs on standardized data elements from data dictionary, measurements from the Bureau, interoperability, value sets.

   2. LeeAnn and Andrea work on each project (funding streams) - design and execute

      1. OUD - From the beginning

      2. CAI - Testing

3. Establish timeline(s)

Agenda

1. Describe the ideal situation – Kathy - 5 min

   1. One FHIR app, with different funding streams and different end users

   2. Standardized how we test and roll out

   3. Need a systematic way to standardize and test with end users (or any time there is software development) - standardize the way we engage end-users in the development process.

   4. How much is content knowledge important on the part of end users, or is it more about how we functionally use apps.

2. Describe each product and its current state – All – 2 min

   1. VAP - Product is out there, being used by one health center. Posted on athena. July 31st end of year, new funding likely.

   2. CAI - Product is there. Launching a new year. Project year just began April 1.

   3. OUD - Initiating requirements gathering process. Project year ends July 31.

3. Review software development model 35 min

4. Discuss roles, responsibilities, timeline

5. Next steps 5 min

Software Development Model (LeeAnn and Andrea to further develop)

Phase 1: Discovery - What are the problems? How can technology assist with this problem?

1. Define the audience(s)/stakeholders who will inform the design. Who is impacted? Who are the gatekeepers who will decide if they will use/not use this tool?

   1. Informatics (at CHCs?)

   2. Data

   3. Clinical

   4. Community Health Workers

• Point person as main contact/champion

  • prepare detailed documents that support what is needed for this person to know

  • this person recruits, knows what is needed, who to recruit, how much time, room, food, av, type of person who needs to be there, number of people

  • confidentiality form - Ellen has a form she uses to get permission to be show in pix and video. Sarah and Wanda have them.

• Informational interviews

• Design group of staff

• Design group of patients

Budget Implications

• Honoraria for health centers to comensate for admin time

• Facilitator

• Report writer

• Travel

Phase 2. Requirements collection - Goal: to gather and document business requirements

• Develop user stories examples of how this app could help solve pain points

• Gather Business Requirements: stakeholders, assumptions, high-level system requirements (does this go in Phase 2 or in 3?)

Phase 3. Design - Goal: to translate software development requirements into design

• Write Software Requirements Document (see example Table 1 - check with software developers to see if they use a different kind of form)

Phase 4. 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 5. Testing & Tweak- 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 6. 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

Action Items

OUD

CAI -

Contracts - Budget and timeline for user testing, interoperability testing