You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

THIS EVENT IS TENTATIVE AND EVERYTHING ON THIS PAGE IS IN DRAFT FORM.


Overview

August 25-27, 2015 at Regenstrief Institute.   

The face-to-face meeting will enable the team to more effectively and efficiently reach consensus and shared understanding on key technical and organizational processes.   This alignment is needed to refine the OpenHIE architecture roadmap and the organizational processes needed to drive toward the next OpenHIE release and will include activities such as setting priorities, working toward consensus on group processes and defining key workflows that use emerging message standards for alerting and data aggregation.  

Objectives

  1. Establish priorities and timelines for next OHIE Release (What we will do) 
  2. Refine OHIE development release process (How we will work)  
  3. Develop a shared understanding of ADX and mACM workflows
  4. Evaluate existing community structure (eg. components vs. workflows)
  5. Gain alignment on key architecture topics such as: 
    • Access controls
    • Vocabulary dissemination / validation
    • Enhancements to existing work flows 
    • Federation Process  (Check the notes from the call)  

Meeting Preparation

Prior to the meeting, each attendee should familiarize themselves with the following content:  

Attendees List

Planning (Attendees)

Logistics

  • Hotel
  • Transport
  • Meals

Joining the Meeting Remotely

 

Agenda

Day 1 - What will we do?

Day 1August 25th
9:00 - 9:30 AM

Welcome and Meeting Overview

  • Review meeting goals

9:30 - 11:30 am

Release 2 Priorities and Scope

  • New workflows / updated workflows
  • Exemplar software development needed
  • Documentation needed
  • Impacts on community roadmaps

DELIVERABLES:

  • Draft scope for OpenHIE Release 2
  • Priorities
11:30Lunch

12:30 - 5:00

Based upon priorities, build architecture alignment on new and updated workflows

  • Alerting (mACM)
  • Aggregation (ADX)
  • Vocabulary dissemination / validation

Notes: maybe use small groups to design with feedback to the larger group? Maybe break this slot into 3 time chunks for mACM and ADX and other? Maybe start with a presentation of use cases that we currently know about.

 

DELIVERABLES:

  • Workflow sponsors
  • Draft high-level workflows and a shared understanding of the architecture needed to support the workflow
DinnerGroup dinner?

Day 2 - How will we do it?

Day 2August 26th
9:00 - 10:30Finalize workflow discussion / review draft workflows
10:30- 10:45Break

10:45 - 12:30

Release Process Framework – how will we work through new releases?

  • Pre-reads – current workflow process
  • Draft framework for releases

DELIVERABLE: framework for releases

12:30 - 1:30Lunch
1:30 - 2:30

Community Organization - How might we organize ourselves for optimum communication and effectiveness?

DELIVERABLE: framework for community organization

2:30 - 2:45break

2:45 - 4:30

Standards and Profile Development Strategy

  • Pre-read – message from Carl F, Ed and Scott

DELIVERABLE: Framework for engaging in standards development

DinnerGroup dinner?

Day 3 - Other Architecture Topics

Day 3August 27th
9:00 - 12:30

Other architecture topics -

  • Federation
  • Access Controls
  • security
  • requirements for OpenHIE architecture components
12:30 - 2:00Lunch and wrap-up
  • No labels