1. 1561 INITIATIVE Lessons Learned and Future Considerations 10-15-2010

2. Lessons Learned – Data Standardization = Good (or at least necessary) IssueFuture ConsiderationsMitigation through S&I Framework? The need to standardize data elements with a NIEM- like process was championed by stakeholders Engage stakeholders more actively in process, with clear requests and timelines Identify deliverables and artifacts for discussion Provide access to artifacts for refinement Initial education to NIEM processes and artifacts will help foster common understanding Data element standardization became a key discussion point for several working groups, including business rules and interface teams Work across teams to promote transparency and harmonization activities Use Case Steward can work with various WG leads to create cohesion across the teams

3. Lessons Learned – Stewardship & Management IssueFuture ConsiderationsMitigation through S&I Framework? Unclear objectives between teams at onset of project led to rework, confusion, and inefficiencies Clearly document problem statement, business needs, and effort objectives as part of project planning (while maintaining agility) Establish clear expectations for final outcomes Problem statement and related goals maintain focus of an effort Establish agile change process to deal with changes in scope and objectives Consensus on clearly defined work plan Progress was inefficient without Use Case Steward or dedicated Data Element Standardization Project Manager Early identification and engagement of initiative champion to effectively manage the effort and bring the right people to the table Foster vision and transparency for stakeholders to participate throughout lifecycle of the project Use Case Steward provides continuity across framework for a single initiative

4. Lessons Learned – Requirements / Stakeholder Management IssueFuture ConsiderationsMitigation through S&I Framework? Use Case clarification and elaboration Early identification and engagement of SMEs to provide input into use case definition Articulate use cases to scope effort and provide traceability Better define the role of facilitator / modeler (Data Element Team) and experts in the field Clearly defined use cases drive an effort towards a specific goal or metric Key stakeholders need to be engaged throughout project lifecycle Identify key stakeholders and engage during project planning Use NHIN Direct like approach to invite participation and elaborate work products Conduct regular review of artifacts with appropriate SMEs Elaboration of use cases facilitate stakeholder identification and engagement Engage use case and harmonization team

5. Lessons Learned – Modeling and Tooling IssueFuture ConsiderationsMitigation through S&I Framework? Need for consistent UML modeling convention leading to different interpretations of the same concept Outline and adhere to consistent UML modeling conventions and principles Establish UML modeling conventions and guidelines Proper tooling required to support analysis and artifact elaboration Use proper tools for articulation of requirements and capturing of metadata Tools support the usability and transformation of data across S&I lifecycle Proper collaboration tools (wikis, version controls, modeling tools) and principles (problem focused, clear decision processes)

6. If I could do it again, I would… »Identify a clear owner of the 1561 initiative who would drive the project forward, provide clarity around goals and objectives, and provide decision making authority »Work with sponsors and stakeholders to clearly define required deliverables, work products, and technical artifacts to meet expectations »Clearly outline relevant use cases before initiating data analysis and harmonization work »Engage community stakeholders earlier to provide the necessary insight required to understand underlying business rules, policies, etc. for health and human service systems »More clearly define responsibilities and anticipated interface points between working groups »Allow for agility – expectations, requirements, and schedules will change; Create platforms to allow for these and adjust efforts accordingly »Dedicate a S&I data standards project manager and project team to complete the effort