1 / 7

OHT Architecture Council

OHT Architecture Council. A Call to Action Craig Miller, Vangent Ken Rubin, HP. What are we trying to do?. Clearly articulate the vision and architecture for an integrated Open Health Tools platform Will assess how existing OHT initiatives and tools can be harmonized to establish:

nay
Download Presentation

OHT Architecture Council

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OHT Architecture Council A Call to Action Craig Miller, Vangent Ken Rubin, HP

  2. What are we trying to do? • Clearly articulate the vision and architecture for an integrated Open Health Tools platform • Will assess how existing OHT initiatives and tools can be harmonized to establish: • Interoperability and consistency between tools • Durable and reusable assets that can be leveraged across projects • Roadmap for needed OHT initiatives • Support the business needs identified by Requirements and Clinical Councils • Evolve prior OHT architecture-related initiatives

  3. Who’s going to do it? • Co-Chairs: Craig Miller and Ken Rubin • Membership is open to any member organization with the following provisos: • At most one representative per organization • Members have to declare themselves • Must commit time and resources to actively participate in the group and contribute content and ideas – no lurkers! • We are accountable to the OHT Executive Director and Board of Stewards

  4. How will it be done? • Goal is to strive for consensus on all work • Leverage an open and transparent process (the details of which will be determined in next few weeks) • Weekly teleconferences for Council members • Products and progress will post to a Wiki that is open to all interested parties • Core group will produce the content • Input will be actively sought from the broader community (e.g., peer reviews)

  5. What tools will we use? • Nothing is decided at this point… • ….but one might expect tools such as • Modeling notation • Component repository • Existing frameworks (e.g. SAIF, HSSP, others) • Interface specifications

  6. What will we deliver and when?

  7. If you are Interested… Send email self-declaring your interest and commitment to the responsibilities of the role to: craig.miller@vangent.com ken.rubin@hp.com

More Related