Driver Information Systems

1
OHT Architecture Project Q2 2009
Content
Added
Pressures

• Architecture principles
• Tool classification mechanism
• a set of templates, patterns and
• processes that enable
• interoperability of OHT tools.
• Identification of potential barriers
• Recommendation of a governance
• process for the harvesting,
• categorization and custodianship
• of architecture artifacts.
• Executed internal and external
• communication plan

• Expectation for detailed Technical
• Architecture Solutions
• Expectation for Architectural
• Framework that allows for a Tooling
• Architecture to emerge through
• Projects
• Desire to reuse tooling components
• Desire to relearn from best practices
• Customer expectations to optimize
• and align Tooling investments

Deleted Changed


Dependencies
Packaging Editions

• Principles, Architecture Framework
• Specification Stack w examples
• Tool classification
• Recommendations to the Board

• Funding for Architecture Project
• team members
• Active cooperation from other
• OHT Project Committers
• Successful communication to
• OHT projects Q2/Q3

Milestones

• Architectural Principles Q2/09
• Tooling Architectural Vision Q3/09
• Architectural Framework Q3/09
• Tooling Classification and
• Governance recommendations Q4/09

Statistics
Contributing Participants NCI, Infoway, NHS,
NextJ, IHTSDO, NEHTA, HL7
2
OHT Architecture Project Q2 2009
4Q09
Tooling Classification Governance
recommendations
Draft Framework Current State Examples
3Q09
Architecture Principles Best Practices -harmoniz
ed with current projects
2Q09
Informal Organizational Meetings Orlando/Paris
1Q09
First Conceptual Meeting
4Q08