Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

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:

Date:

Date:

Possible discussion topics:

  • Review Kathy’s comments

  • Discuss typical software development process - what we do, what HealthFlow does, where to find information.

  • 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

  1. 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.

Establish requirements now (Source 2)

Establish acceptance criteria (Source 2)

 

Date:

LeeAnn is developing an app for Opioid care plan app.

We are doing software development for three projects:

  • AIM care plan app - 1 out of 15 sites is using the app.

  •  Opioid Care plan

  •  CAI HIV Care plan app

 

  • No labels