Versions Compared

Old Version 25

changes.mady.by.user Jennifer E Shivers

Saved on

compared with

New Version 26

changes.mady.by.user Jennifer E Shivers

Saved on

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) 
  2. Refine OHIE and document OpenHIE development release process (How we will work)  
  3. Develop a shared understanding of ADX aggregate data and mACM alerting workflows
  4. Evaluate existing community structure (ege.g. components vs. workflows)
  5. Gain alignment on key architecture topics such as: 
    • Access controls
    • Vocabulary dissemination / validationworkflows
    • Enhancements to existing work flows 
    • Federation Process  (Check the notes from the call)  

Preparing for the Meeting

...

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

...

Day 1 - What will we do?

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 Scope

  • Priorities we know (aggregate data workflow and alerting workflows)
  • Other possible priorities might include:
    • new
    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:

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

Day 2 - How will we do it?

Day 2August 26th
8:30 - 9:00Breakfast and informal discussion
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?

...