Page History

{scrollbar:icons=false}
h1. {page-info:title}

|| Time | 9:00 - 10:00 AM \\ |
|| Date | 04/19/2010 |
|| Location | telecon |
Lead: Denise Warzel

Moderator/Facilitator: Beate Mahious

h2. Attendees

||Team Member || Organization ||
| Denise Warzel \\ | NCI CBIIT |
| Beate   Mahious | SemanticBits |
| Joshua Phillips | SemanticBits |
| Rick   Kiefer | Mayo   Clinic |
| Patrick McConnell | SemanticBits |
| Alan Blair | SemanticBits |
| Baris Suzek | Georgetown |
| Shantanu Deshpande \\ | Persistent \\ |
| Zoran Milosevic \\ | Deontik \\ |
| Tom Digre \\ | SemanticBits \\ |

h2. Apologies

None

h2. Meeting Agenda

1. Update on ISO 11179 (Joshua 5 min)
2. Update on caEHR  (Denise 5min)
3. Simple User Stories (50 min)
3.a. Presentation to leadership
3.b. Preparation for software developers

h2. Meeting Minutes

*1.Update on ISO 11179*
Our basic technical approach remains unchanged. ISO 11179 is not part of our requirements.

Q: Is "value domain" a 11179 term?
A: Yes, it is, but we can still use it as a domain for a particular property.

*2.Update on caEHR*

Dave Hau has been assigned with ca EHR ( = cancer Electronic Health Record). This week we will find out more about it and whether or not there might be another analyst involved on the caEHR side, or whether one of our analysts will take on the caEHR use cases.

*3.Simple User Stories*

We reviewed and discussed the following two pages:

* Patrick's simple user stories : [User Story Drafts]

* Rick's matrix with list of user stories and what  functional profiles they address: [Semantic Infrastructure Services User Story Matrix]

The idea is that user story titles from the second link will link to  user stories in format as displayed in the first link.

Each user story has three parts to it: Domain Description, Technical Description, and Cross Reference.

User stories need to be reviewed and if possible further consolidated to come up with the shortest list of use cases which will cover all of Initiative 1 requirements. Those will be pesented to leadership and then entered into the matrix by Alan Blair (Second link above) with an "x" in the appropriate column of functional profile that is addressed in the user stories.

Baris will take on the domain description for workflow/ pipeline.

For traceability each user story has a list of links to requirements from the master list in its "cross reference" section.

*3.a.Presentation to leadership*

The domain stories are fit for presentation to members of CBIIT leadership.

*3.b.Preparation for software developers*

The matrix is for internal use of the team to easily keep track of which user story covers with functional profile.

h2. Action Items

|| Name Responsible || Action Item || Date Due \\ || Notes \\ ||
| Bea \\ | send list of analysts and what teams they are in to Denise \\ | 4/19/2010 | done \\ |
| Bea \\ | create project plan for presentation at meeting May 4-6 and send to Denise \\ | 4/23/2010 |--- |
| Denise \\ | read through and give feedback on user stories [User Story Drafts] | 4/26/2010 |--- |
| Baris \\ | write domain description for workflow / pipeline \\ | 4/21/2010 |--- |
| Bea \\ | assign "ICRi WG Use Case Scenarios" to Baris in master list \\ | 4/19/2010 | done |
| Denise \\ | update "activities" column in master list \\ | 5/3/2010 |--- |
| Alan \\ | after consolidation and review of all user stories, place the titles into matrix and place "x" in the appropriate column of functional profile that is addressed in the user stories. \\ | 5/3/2010 |--- |
\\
{scrollbar:icons=false}