2017-12-04 SOLOR Dev Meeting notes

Date

Attendees

Goals

  • Restrospective on skin wound assessment extension v.1

Discussion items

TimeItemWhoNotes
Call meeting to order


 

Skin/Wound Assessment Retrospective 

An agile retrospective, is a practice used by teams to reflect on their way of working, and to continuously become better in what they do. 

  • What went well?
  • What went wrong?
  • What could we do differently to improve?
 

 What went well?

KEC – huge amount of learning accept and adapt with an early stage project. We're not trying to sweep issues under the rug - we are trying to improve. One aspect of the learning - what the different parts are and what are the interdependencies are. What does SOLOR deliver and to whom. When issues arised we worked to resolve them.

Susan M – JIRA, ask questions and between each other. Getting principles down on in confluence.

John K – we developed a workflow and this workflow allowed content process to proceed (liz, holly, john).

Jay L – We have a publication! And we have something to move forward.

Holly – Agreed with all of the above. Definition of a process was good. 

Stephanie – what is the bigger picture? 

What went wrong/bumps/ in the road?

Keith – Clear articulation of the bigger picture. What is within our scope. Resources left project. How do we stay in contact with CIMI and aligned - what aspect of CIMI and who do we need to stay in alignment. Keith how do we know we're making things better?

Susan M – understanding the scope of what SOLOR is responsible for was a bit unclear. We didn't look at questions from CIMI to determine if we have the right values and do we answer the CIMI questions. How does SOLOR relate to CIMI models is still unclear.

John K – need to get clear on the scope and what SOLOR is. The more tangible and clear what we're producing and who is going to use it. "guess what I'm thinking" – seems like how we progress. 

Jay L – we don't know how the product is going to perform. and if it is right to it's use

Holly – difficulties in resolving points of confusion, communication could be better - different orgs, different schedules, getting answers sometimes delayed

Stephanie – observable entities and findings – need tangible answers

Susan C – who has the final say on what is in refset, what is the purpose of the refset, feedback from SMEs needs to be quicker

What could we do differently to improve?

Keith – shared document on where we are heading. how can we get others up to speed on what we are doing in SOLOR. 

Susan M – Review scope of project – we need a clear scope and objectives as a group. Need to stay in contact and alignment with CIMI

John K – what is the scope? 

Jay L – communicate the vision e.g. SOLOR artifact that is implemented for CIMI ...

Holly – better define scope, big picture, relationship between SOLOR and CIMI. Have something more concrete for the SMEs...i.e. an implementation of what was delivered...

Stephanie – in service training to understand the big picture, concrete clear documentation for folks on the project, coming in to the project. What is driving what we're working on? 

Susan C –


-This SOLOR call is about clinical input forms. In KNART and IA small group - analysis normal form, can we analyze that data

TODO 

  1. Documentation from IA group on the vision 
  2. What is SOLOR? How do we get projects prioritized and approved? 




Content next steps for skin/wound assessment

  • review JIRAs


Action items

  •