Abstract Model Tracker
Jump to navigation
Jump to search
Action Items | |||||
# |
Date |
Action |
Status |
Owner |
Due Date |
1 |
3/31/2010 |
Send discussion about self describing content vs. non self describing content |
Closed |
Arien |
4/1/2010 |
2 |
3/31/2010 |
Draft a first cut at a dictionary of terms |
Open |
Arien |
4/7/2010 |
3 |
3/31/2010 |
Create one user story that illustrates read/receipt |
Closed |
Arien |
4/7/2010 |
4 |
3/31/2010 |
Formalize the structure of the story |
Closed |
Arien |
4/7/2010 |
Rewrite the overall stories from an end users perspective | |||||
Include key lessons and technical considerations | |||||
Story shouldn’t be overly technical, technical details should be moved to the glossary | |||||
5 |
3/31/2010 |
Review existing stories understanding that Arien will take a pass |
Open |
All |
4/7/2010 |
6 |
3/31/2010 |
Supply comments in the discussion area about: |
Open |
All |
4/7/2010 |
Important considerations | |||||
Additional style issues | |||||
7 |
4/5/2010 |
Review “Must” and “Should” stories |
Open |
All |
4/12/2010 |
In this group, be sure to pay attention to the Lab Story | |||||
8 |
4/5/2010 |
Review User Stories with NHIN Cooperative and State |
Open |
All |
TBD |
9 |
4/5/2010 |
Create Related Stories Section in template |
Open |
Arien |
4/12/2010 |
10 |
4/5/2010 |
Create language around receiver acknowledging the receipt of the message: i.e. “Source (message sender, initiator) has knowledge of their request being delivered” |
Complete |
Arien |
4/12/2010 |
11 |
4/5/2010 |
Keep language high level, as the user experiences it |
Complete |
Arien |
4/12/2010 |
12 |
4/5/2010 |
Correlate use case language to abstract model language |
Open |
Arien |
4/12/2010 |
13 |
4/5/2010 |
To create a succinct sentence which states that the PCP has already decided it is okay to share information |
Complete |
Arien |
4/12/2010 |
14 |
4/12/2010 |
MOVE conversation about rewording the Must definition to “this provider with certified EHR module can use this type of exchange” to a discussion on the Wiki |
Open |
Arien/Peter |
4/19/2010 |
15 |
4/12/2010 |
Have later conversation about how NHIN Direct will incorporate needs of small business partners |
Open |
All |
4/19/2010 |
16 |
4/12/2010 |
Reflect in “Must” definition that all User Stories don’t have to be implemented in their entirety, just the ones that fit |
Open |
Complete |
4/19/2010 |
17 |
4/12/2010 |
Consider writing a User Story for Long Term Care Facility |
Open |
Arien |
4/19/2010 |
18 |
4/12/2010 |
Generalize the title of “Message sender receives delivery receipt” |
Complete |
Arien |
4/19/2010 |
19 |
4/12/2010 |
Create Table correlating all User Stories to their Meaningful Use requirements |
Open |
Arien |
4/19/2010 |
20 |
4/12/2010 |
Specifying the governance process from how stories will get added within the Wiki |
Open |
Arien |
4/19/2010 |
21 |
4/12/2010 |
Language for Must stories tied to meaningful use will be made consistent with NPRM terminology |
Open |
Arien |
4/19/2010 |
22 |
4/21/2010 |
Post example 1 diagram source file |
Complete |
Rich |
4/28/2010 |
23 |
4/21/2010 |
Delete the term “onboarding” |
Complete |
Brett |
4/28/2010 |
24 |
4/21/2010 |
Make a note on the diagram and also in the documentation to indicate the presence of a combined HISP/Destination |
Open |
Vassil & Dan |
4/28/2010 |
25 |
4/21/2010 |
Make a note that it is an earlier version and WG should select the tools that they want to use, and then Dan will export into that |
Open |
Dan & All |
4/28/2010 |
26 |
4/21/2010 |
Simplify 3.x HISP-Destination Language in transaction not to imply polling based model but to still express the intent of the model |
Complete |
Brett |
4/28/2010 |
27 |
4/21/2010 |
Change 2.1 language and M-architecture diagram to express “mutually authenticated” |
Complete |
Rich |
4/28/2010 |
28 |
4/21/2010 |
Put the architectural guidance one pager on the Wiki and we will discuss next week |
Open |
Arien |
4/28/2010 |
29 |
4/21/2010 |
Talk to Arien about cancelling the meeting beyond 5/5 |
Open |
Brett |
5/5/2010 |
30 |
4/21/2010 |
Debate Dan Russler's BPMN diagrams expressing the Abstract Model found on the examples page online. |
Open |
All |
5/5/2010 |
Key Decisions |
|||||
# |
Date |
Decision |
|||
1 |
3/31/2010 |
Peter DeVault will be WG lead |
|||
2 |
3/31/2010 |
Use case style will be representative of the user, but any superfluous technical details will not be included, or will be included in an appendix |
|||
3 |
4/12/2010 |
Must definition is within a limited scope and tied to MU requirements |
|||
4 |
4/28/2010 |
Cancel the 5/5/2010 due to travel |
|||