Versions Compared

Old Version 26

changes.mady.by.user Jennifer E Shivers

Saved on

compared with

New Version 27

changes.mady.by.user Jennifer E Shivers

Saved on

Key

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

...

Objectives

  1. Establish priorities and timelines milestones for next OHIE Release (What we will do) 
  2. Refine and document OpenHIE development release process (How we will work)  
  3. Develop a shared understanding of aggregate data and alerting workflows
  4. Evaluate existing community structure (e.g. components vs. workflows)
  5. Gain alignment on key architecture topics such as: 

...

Day 1August 25th
7:30 - 9:00Breakfast and informal discussion
9:00 - 9:30 AM

Welcome and Meeting Overview

  • Review meeting goals

9:30 - 11:30 am

Release 2 Priorities and ScopeSet priorities for next release and other key activities

  • Priorities we know (aggregate data workflow and alerting workflows)
  • Other possible priorities might include:
    • new workflows / updated workflows
    • ICP (Integrated care pathways)
    • Exemplar software development needed
    • Documentation needed (success stories or examples of common use cases)
    • Federation
    • Access controls
    • what else?
  • Other priorities not in the scope of release 2?
  • Impacts on community roadmaps?

Notes: prepare a slide with topics that we know are priorities and topics that seem to be popping up a lot.

DELIVERABLES:

  • Priorities
  • Draft scope for OpenHIE Release 2
  • Priorities
  • Action items
11:30 - 12:30 Lunch and informal discussions

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?

...