Concrete Implementation WG 1. Concrete Implementation Workgroup »Purpose is to recommend one+ high level concrete implementation mapping to the abstract.

Slides:

Advertisements

Similar presentations

S&I Framework Testing HL7 V2 Lab Results Interface and RI Pilot Robert Snelick National Institute of Standards and Technology June 23 rd, 2011 Contact:

Advertisements

June, 2010 SOAP / IHE Concrete Implementation. We are a group of organizations who have already implemented IHE profiles We recognized the user stories.

Designing and Developing Decision Support Systems Chapter 4.

360Exchange (360X) Project Provider Directory Workgroup 09/07/2012.

Direct Implementation Perspective 0 Mark Bamberg, Vice President Research & Development MEDfx.

Acquiring Information Systems and Applications

Framework Planning Draft 1 Jack Suess Ian Glazer Peter Alterman Andrew Hughes Michael Garcia.

Copyright  2005 Symbian Software Ltd. 1 Lars Kurth Technology Architect, Core Toolchain The Template Engine CDT Developer Conference, Oct 2005.

SE 555 Software Requirements & Specification Requirements Validation.

Fact-Finding Fact-Finding Overview

S&I Framework Doug Fridsma, MD, PhD Director, Office of Standards and Interoperability, ONC Fall 2011 Face-to-Face.

CHAPTER 19 Building Software.

1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7 Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.

THE DIRECT PROJECT UPDATE FOR THE FEDERAL HIT WORKGROUP Arien Malec Coordinator, NHIN Direct Project 8/28/2015.

OSIAM4HE Proposed org structure Authored by the strategy and organization team.

Continuation From Chapter From Chapter 1

May Distribution authorized to U.S. Government Agencies only Symmetric Multimodal Interactive Intelligent Development Environments Dramatic reduction.

Functional Model Workstream 1: Functional Element Development.

Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.

1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.

NHIN Direct Project ONC State HIE Retreat September 1 st, 2010.

DATA FOUNDATION TERMINOLOGY WG 4 th Plenary Update THE PLUM GOALS This model together with the derived terminology can be used Across communities and stakeholders.

Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.

Mount Auburn & MACIPA OneIS Staffing Summit

An XMPP (Extensible Message and Presence Protocol) based implementation for NHIN Direct 1.

Epiphany Partners Corporation HealthTechNet ClerePath TM Solution July 21, 2006.

1 ILE Project Integrated Logistics Environment Kickoff Meeting Subtask 1.2 Sharing Structural Design Data with Manufacturing Systems Presented by: Michael.

Web services sub-team report CPPA June ’02 F2F Reston, Virginia.

Web Services Description Language CS409 Application Services Even Semester 2007.

Public Health Reporting Initiative: Stage 2 Draft Roadmap.

Software Engineering Management Lecture 1 The Software Process.

MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.

ECTL A Support to the Automated Safety Data Monitoring Indicator project.

HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.

Chapter 7 Applying UML and Patterns Craig Larman

NHIN Direct Implementation Group Meeting April 6, 2010.

Assessment of Portal Options Presented to: Technology Committee UMS Board of Trustees May 18, 2010.

CHAPTER 13 Acquiring Information Systems and Applications.

WS-I Submission W3C XML Schema User Experiences Workshop June 2005 Redwood Shores, CA, USA Erik Johnson, Epicor Software.

Nodal Education Initial Staff Concepts 11/30/05. Agenda Integrated Approach Roadmap and Processes Curriculum Development ERCOT Education Advisory Council.

Data Provenance Community Meeting November 6, 2014.

Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.

NIST BIG DATA WG Reference Architecture Subgroup Agenda for the Subgroup Call Co-chairs: Orit Levin (Microsoft) James Ketner (AT&T) Don Krapohl (Augmented.

Query Health Distributed Population Queries Implementation Group Meeting October 11, 2011.

Challenges for Data Architecture in a Package Environment Dawn Michels May 4, 2004 May 2-6, Los Angeles/Century City, California, USA.

Authentication and Authorisation for Research and Collaboration Peter Solagna Milano, AARC General meeting Report and plans Attribute.

A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute

Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,

McIDAS-V Status and Demonstration by Gail Dengel Tom Whittaker University of Wisconsin-Madison SSEC 2005 MUG Meeting October 27-28, 2005 Madison, WI.

C.A.G.I.S. Helpdesk System Sean Winfield March 6, 2006 Senior Design III.

CIWQS Review Phase II: Evaluation and Final Recommendations March 14, 2008.

第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.

Electronic Submission of Medical Documentation (esMD)

Query Health Distributed Population Queries Implementation Group Meeting March 6, 2012.

IS2210: Systems Analysis and Systems Design and Change Twitter:

Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.

Requirements Analysis

ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.

BEA position on W3C ‘Web Services’ Standards Jags Ramnarayan 11th April 2001.

SPP Presentation. Recommendation Status Update Ty Mitchell Entergy Stakeholders Meeting August 22, 2006 Houston, TX.

Middle Fork Project Relicensing Process Plan April 25, 2006.

Lab Results Interface Validation Suite Workgroup and Pilots Workgroup Vision, Charter, NIST Collaboration, July 8,

Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.

GEO Implementation Mechanisms Giovanni Rum, GEO Secretariat GEO Work Programme Symposium Geneva, 2-4 May 2016.

INFSO-RI Enabling Grids for E-sciencE Network Services Development Network Resource Provision 3 rd EGEE Conference, Athens, 20 th.

Device Security in Cognitive Radio

QA Reviews Lecture # 6.

Portfolio, Programme and Project

Proposal of a Geographic Metadata Profile for WISE

Joint Application Development (JAD)

Presentation transcript:

Concrete Implementation WG 1

Concrete Implementation Workgroup »Purpose is to recommend one+ high level concrete implementation mapping to the abstract model for further development and use in the pilots. »Key May 6th Deliverable: Edge and Routing Specification (not there yet….) »Leaders: Sean Nolan & Brian Behlendorf »Topics for today »Overview of approach and timeline »“Minimum Threshold” requirements for implementation groups »Early observations and learning »Status updates from implementation groups »Discussion

Approach and Timeline »Will recommend a single implementation approach for v1, while keeping an eye towards transport evolution over time »Force demonstration of technical and social feasibility of different approaches to input requirements Technical = working code Social = community participation »Four groups have self-formed around: SMTP, REST, IHE/SOAP, XMPP »Group will recommend a winner at IG teleconference on May 18th »Had discussed an “initial cull” today, but seems premature 3

“Minimum Threshold” »Important because it is our attempt to lay the “ground rules” that we will use as a basis for comparing implementations » d+for+Recommendationhttp://nhindirect.org/Concrete+Implementation%3B+Minimum+Threshol d+for+Recommendation »Proposed Requirements Community of Supporters Software “Map” Description of end-user experience for all actors 4

“Minimum Threshold” – Community of Supporters 5 A self-identified community of supporters willing and capable of building a reference software implementation in the overall NHIN Direct desired timeframes, and the other artifacts and deliverables along the way.

“Minimum Threshold” – Software “Map” 6 A software "map" for each implementation. Of the participants in the Abstract Model (plus other actors - a Certificate Authority perhaps, or another sort of directory service), what software does each party need to run in order to fulfill its role in the system? Abstract Model Described at one layer higher than a specification, this should describe the collection of specific software required for a demonstration, biasing towards production-quality software. For functions that are mandatory to fulfill the User Stories, the map must point to software licensed under an Open Source license that allows for integration into proprietarily-licensed software, so to accelerate adoption.Open Source license

“Minimum Threshold” – End-user Experiences 7 For all actors in the system, a description of the end-user experience sufficient to author a user interface OR a similarly Open Source licensed example application that provides the desired end-user interface.

Early observations and learning »Code is a great way to resolve ambiguity! »Folks are moving forward with an assumption of MIME content »We are quickly bumping up against S&T issues that need resolution 8

Status Updates »REST VisionShare, Google, CGC, MedPlus / Quest Diagnostics »SMTP Cerner, Microsoft »IHE / SOAP GE, Epic, MedAllies, Redwood MedNet »XMPP Harris Corporation, Redwood MedNet 9