Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Establish priorities and timelines for next OHIE Release (What we will do)
    1. OpenHIE level and component level
  2. Refine OHIE development release process (How we will work)  
  3. Develop a shared understanding of ADX and mACM workflows
  4. Determine ho we organize ourselves (ie. 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

Each attendee should ...re familiarize themselves with the following content:  

Attendees List

Planning (Attendees)

...

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

Welcome and Meeting Overview

9:30 - 11:30 am

Release 2 Priorities and Scope

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

DELIVERABLEDELIVERABLES:

  • 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?

...