Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Task marked complete

...

Dates: See schedule below Location: Conference Line/Adobe Connect Lync see below

These meetings are being held to 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.  

...

    • Access controls
    • Vocabulary workflows
    • Enhancements to existing work flows 
    • Federation Process  (Check the notes from the call)  

Deliverables

  • Shared understanding 

  • Alignment on the topic

  • Open issues, action items and next steps for the topic

Pre-work for Meetings

Sponsors / Topic Lead  - Prepare an overview of the topic: (upload materials 24hrs. prior to discussion) 

  • Country Needs / Use Case 
  • Workflow draft or strawman proposal 

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

Framework for Discussions

Joining Meetings

Dialing in: OpenHIE Architecture Call 1 (317) 274-3025 Conference ID: 4789672  

Web LyncScreen sharehttps://connectlync.ads.iu.edu/ohie-arch

Agenda

Panel
titleBGColor#009FC8
titleJuly 20th (Leads Call) - OpenHIE Leadership Model - What does it mean to be a leader?

Agenda:

  1. Review and discuss what is means to be an OpenHIE leader?

DELIVERABLES: 

  • List of what the OpenHIE leadership does.   

Outcome:

Panel
titleBGColor#009FC8
titleJuly 31st (Architecture Call) - Release Process Framework

 Pre-Work:  

Agenda:  

  1. Present release process "strawman"  
  2. Group discussion

DELIVERABLES:

  • Release process draft
Panel
titleBGColor#009FC8
titleAugust 10th (Architecture Call) - Set priorities for the next release and, other key activities

Pre-Work:  

Agenda:

  1. What needs to be included in the release?  OpenHIE Next Release
  2. What additional topics need to be prioritized for discussion?

DELIVERABLES:

Panel
titleBGColor#009FC8
titleAugust 17th (Leads Call) - OpenHIE Leadership Model (How)

Pre-Work:  

Agenda:

DELIVERABLES:

Panel
titleBGColor#009FC8
titleAugust 25th - 27th (Architecture Calls)

Time: 9:00 AM to 12:30 AM EDT

Pre-Work:

  • Sponsors / Topic Lead  - Prepare an overview of the topic: (when possible, share this ahead of time) 

    • Country Needs / Use Case 
    • Workflow draft or strawman proposal 

Prioritized list of topics:

Items to be discussed will be priorities from 31-July Discussion:  

Topic

Sponsor / Topic Lead

  1. Aggregate Data Workflow(s)

James

2. Alerting Workflow(s)

Dykki, Ed

Framework for the Discussion:  

  1. Overview of the topic

    1. Country needs / Use Cases
    2. Workflow draft / draft proposal 
  2. Group Discussion 

  3. Next Steps 

DELIVERABLES:

  • Shared understanding 

  • Alignment on the topic

  • Open issues, action items and next steps for the topic

...

titleBGColor#009FC8
titleAugust 28th (Architecture Calls)

/iu/meet/miclcox/H9QBTZ6M

Agenda - Tuesday, August 25 - Friday, August 28

Day 1: Tuesday, August 25

Notes for Day 1

Video for Day 1 - Part 1, Video For Day 1 - Part 2 

Time (EDT)TopicPresenters MaterialsNext Steps/Consensus
9:00 - 10:30

Aggregate Data Exchange Workflow(s)

Sponsor: James Kariuki and Denise Johnson

Goals: Understanding of how the workflow interacts with the architecture in V2.0.

ADX Workflow Presentation
  •  Clarify the role of the IL
  •  Create diagrams for workflows
  •  Make Diagram more clear (Sender and receiver IL or source and destination)) 
  •  Walk through the Validate and Save Aggregate data workflows
  •  Determine the Role of the InfoMan in validating data

CONSENSUS: Move forward with these two workflows. One is further along. One needs more refining.

10:30 - 10:45

Break  
10:45 - 12:15

Alerting Workflow(s)

Sponsor: Dykki Settle, Eduardo Jezierski and Carl Leitner

Goals: Understanding of how the workflow interacts with the architecture in V2.0.

150825 openhie_alert_workflow.pptx
  •  Do a detailed review by looking at actual alert messages to make sure the alerting workflow works at scale
  •  Revise sequence diagrams based upon feedback and map to OHIE Actors
  •  Ensure OHIE Community has a better understand the aggregator and how it fits with the IL or OHIE Architecture
  •  Begin socialization with mHealth providers to cultivate interest in implementing other candidates at Connectathon in January
  •   IHE test and have one implementation ready for OpenHIE 2.0
CONSENSUS: This workflow is on a good path and we will move forward to try and get this in the 2.0 release.
12:15-12:30Review Next Steps/Action Items  

Day 2: Wednesday, August 26

Notes for Day 2

Video for Day 2 Part 1, Video For Day 2 Part 2

Time (EDT)TopicPresenters MaterialsNext Steps/Consensus
9:00 - 10:30

Privacy and Security

Sponsor: Derek Ritz (ecGroup) and Justin Fyfe

Goals: Understand the current frameworks that have been developed.

Determine what needs to be delivered in V2.0.

15-04-13 OpenHIE Consent Doc

15-08-25 Consent Directive Management.pptx

  •  Create maturity model around privacy, consent, etc. (including: maturity model will include exemplar policy considerations, technology standards, prioritization of what trajectory looks like)
  •  Justin will investigate PD!-12 as a place to start for disclosure.

CONSENSUS:  Derek and Justin will create a draft maturity model for the group to give thought and input.

10:30 - 10:45

Break  
10:45 - 12:15

Strategy for TS Validation

Sponsor: Jack Bowie

Goals: Finalize strategy for TS validation and determine next steps.

TS Validation Transaction.pptx
  •  Define the lift in creating a workflow for V2 that exposes a FHIR transaction to externally expose a way to get a value set.  
  •  Provide more details about what can be transfered (hierarchy and metadata)  after connectathon.
  •  Identify a sponsor for the PoS get code list workflow.

CONSENSUS: Want version 2 compliant server that is able to support fetch of the codes in a value set (value set could also include all of the codes in LOINC).

12:15-12:30Review Next Steps/Action Items  

Day 3: Thursday, August 27

Notes for Day 3

Video for Day 3

Time (EDT)TopicPresenters MaterialsNext Steps/Consensus
9:00 - 10:30

ODD Implementation

Sponsor: Ryan Crichton

Goals: Shared understanding of the capabilities, implementation and work left to do.

ODD presentation
  •  Come up with the sections of documents we want to support (Immunizations are a prirority)
  •  Define support for which summary documents we are able to generate -APS and General medical summary
  •  Update the workflow documents
  •  IHE testing to demonstrate ODD
  •  Ian Fine and others should look at the specifications to tell us if they meet the requirements or not

CONSENSUS: Creating a summary document for next release is too high a bar but can start implementing support for existing documents. Can also do something in the short-term if necessary.

10:30 - 10:45

Break  
10:45 - 12:15

Open Time Slot

  
12:15-12:30Review Next Steps/Action Items  

...