OpenHIE 2021

Architecture Summit

Moving from Architecting to Implementing

Virtual Meeting February, 2021

#OHIEArchSummit

Welcome and Introduction

Meeting Goals and Deliverables

Support the Shift from Architecting to Implementing

Goal: WE NEED YOUR INPUT to set stakes in the ground to plan for 2021 and beyond

Expected / Proposed Deliverables:

1. Get input for a 2021 Architecture Community Roadmap
2. Action plan for increasing engagement in 2021
1. Who to engage and how
2. Plan / List of ideas for better supporting implementers
3. Establish next steps on testing
4. Steps for continuing to use FHIR and other standards
5. Topics for 2021 Architecture Discussions

​

​

​

3

Any other input?

Collaborative Engagement Agreement

• Please have open, honest, and constructive conversation
• Please excuse yourself as needed (you know where the refreshments and bathrooms are)
• Please contribute to collaborative notes
• Create an account an OpenHIE ID to collaborate on the wiki and Discourse
• Please remember to be considerate, respectful, and inclusive
• Give space for everyone to speak
• Please mute yourself when you are not speaking

Anything else to add?

4

Home Base - Summit Wiki Page

• Agendas
• Collaborative Notes
• Collaboration Boards
• Meeting Slides
• Meeting Attendees

​

​

https://wiki.ohie.org/display/resources/OpenHIE+Architecture+Virtual+Summit

5

Introductions

1. Name
2. Organization

6

• Please change your Zoom name and list yourself in the wiki attendees list. In both Zoom and the notes, include:
• first name, last name, organization

Today’s Schedule (See Wiki)

7

Based upon real world experiences…

1. Champion the OHIE community’s principles
1. "Adaptable" / "implementable" principle.
2. "Standards-based" principle.
3. "Interchangeability" / "Swappable" principle
2. Creating, curating and publishing the OHIE Specification
• OHIE Architecture Diagram.
• Component specifications
• OHIE Workflows
3. Determine, curate and communicate the maturity of the workflows
4. Determine and support a testing strategy
5. Curate reference software list
6. Build OHIE community awareness and consensus around OHIE Architecture

​

​

​

​

Architecture ARB Responsibilities

8

Highlighted SubCommunity Responsibilities

• Request needed changes to the specification and diagram
• Identifies gaps or opportunities for technical collaboration between sub-communities as it related to the OpenHIE architecture and brings those issues to the Architecture Review Board for discussion
• Ensure someone is representing your sub community on the Architecture Review Board

​

9

Looking Back at 2020

2020 Key Accomplishments

Specification and Diagram Additions / Updates

• Added: lab exchange, maturity
• Updated: CR requirements and terminology workflows
• Added Maturity

ARB Membership Additions

OHIE Testing Processes

• Connecting and learning from other testing communities

Reworked and Refined OHIE Architecture Processes

Continued Investment in FHIR

• Developing FHIR Implementation Guides (IGs)
• FHIR statement
• IHE Profiles

Downloaded 958 times in 2020

11

12

12

12

Evolving Architecture

13

13

13

Supporting Implementers

OHIE Academy

Health information exchange and OpenHIE learning materials

Instant OpenHIE

Getting started with Health Information Exchange.

OHIE Getting Started Guide (in process)

Improved guides on how to get started with OpenHIE

Impact Stories

Examples of Success or Work in Progress with OpenHIE

• Tanzania and Zambia
• Malawi

2020 Subcommunity Accomplishments

See: Updates and Accomplishments

​

14

Moving Forward

Using the Collaborative Tool

• Each Zoom group (“Group 2”) has a square to work in

​

​

• Make sure you are sharing your sticky notes

​

• Click on the group tool and then your Group’s section of the paper to create sticky notes

​

Once you are given the link to the first board, you’ll be asked to use Google or other mechanism to quickly create an account.

16

Moving from Architecting to Implementing Brainstorm Activity

Prompting Questions:

• What are the OpenHIE Architecture topics / issues that we have yet to address or need to address more fully?
• What do we need to do to better support ministries of health and other implementers?

​

Group Exercise:

1. 30 minutes - in small breakout Zoom groups
1. Use the tool to create sticky notes in the section for your group
2. One Unique idea to sticky notes
3. MetroRetro Board 1 - https://metroretro.io/board/LB6Y24DOF289
• Share your sticky notes

2. Share with the larger group

17

Testing - Carl Fourie

Testing (conformance & compliance testing)

Brainstorm Activity

Goal: Get input on how we see testing as a community and where to focus.

Prompting Questions:

• What testing means to you in the context of OpenHIE?
• Where should we be starting with Testing?
• How do implementers specify that they are OHIE compliant (does OHIE create that definition or does each implementation get to state that they are OHIE "compliant" )
• Should OHIE "certify" implementations?

​

1. 20 minutes - in small breakout zoom groups
5. Use the tool to create sticky notes in the section for your group
6. One Unique idea to sticky notes
7. MetroRetro Board: - https://metroretro.io/board/LBUU7ZT049OM

​

2. Share with the larger group

Link to testing presentation

19

Conformance Testing Framework Flowdown

OHIE Test Scenarios

​

Driven by workflows and business case. For each component a list of test scenarios to that verify conformance to the specification. Performance testing guidance

​

Technical Test Descriptions

​

Driven by test scenarios. Technical breakdown of scenarios into multiple cases and steps. Provision of data sets and outputs. Leverage languages such as Gherkin etc.

2

1

Technical Test

Harness/Tools

​

Fed by test cases and return results. Implementation of tests for technical evaluation. Dummy/Testing infrastructure

3

1

OHIE Architectural Specification

OHIE Testing Framework

• OpenHIE Component Requirements

​

• Workflow Requirements
• Functional Requirements

The technical instantiation of the test cases/definitions that are executable. The curation of test scripts and functions that action the tests, data inputs, options and outputs.

​

Provision of technical tools / dummy services and or infrastructure.

OHIE Architectural Specification

(version X.xx)

OHIE Test Scenarios

• Driven by workflows and business case
• For each component a list of test scenarios to that verify conformance to the specification
• Performance testing guidance

Technical Test Descriptions

• Driven by test scenarios
• Technical breakdown of scenarios into multiple cases and steps
• Provision of data sets and outputs
• Leverage languages such as Gherkin etc

Technical Test Harness/Tools

• Fed by test cases and return results
• Implementation of tests for technical evaluation
• Dummy/Testing infrastructure

The test scenarios are derived from the architectural specification and will cover the scenarios required to evaluate a tool’s ability to conform to the requirements of selected component and or function as consumer or contributor to an OpenHIE Workflow.

​

OHIE Communities (curators of requirements and specifications) will help contribute test scenarios to support the requirements identified in the requirements

The more granular definition of the test scenarios that outline the behaviour, conditions, actions and outputs for each scenario as well as curating data sets, options, configurations and expected outputs (i.e. patient matching etc).

​

Suggestion to harmonize on a testing language such as Gherkin etc.

OHIE Architectural Specification

(version X.xx)

OHIE Test Scenarios

• Driven by workflows and business case
• For each component a list of test scenarios to that verify conformance to the specification
• Performance testing guidance

Technical Test Descriptions

• Driven by test scenarios
• Technical breakdown of scenarios into multiple cases and steps
• Provision of data sets and outputs
• Leverage languages such as Gherkin etc

Technical Test Harness/Tools

• Fed by test cases and return results
• Implementation of tests for technical evaluation
• Dummy/Testing infrastructure

Country / Project adaption

Country / Implementation Test Scenarios

• Driven by workflows and business case for implementation
• Subset / extension of core OHIE scenarios
• Implementation specific performance requirements

Technical Test Descriptions

• Implementation and context specific test cases and data sets
• Localized repository of definitions

Technical Test Harness/Tools

• Country and possibly tool specific tests
• Country test framework and infrastructure

OHIE Architectural Specification

(version X.xx)

OHIE Test Scenarios

• Driven by workflows and business case
• For each component a list of test scenarios to that verify conformance to the specification
• Performance testing guidance

Technical Test Descriptions

• Driven by test scenarios
• Technical breakdown of scenarios into multiple cases and steps
• Provision of data sets and outputs
• Leverage languages such as Gherkin etc

Technical Test Harness/Tools

• Fed by test cases and return results
• Implementation of tests for technical evaluation
• Dummy/Testing infrastructure

Possible Tool/Location/Instantiation

OHIE Architectural Specification

(version X.xx)

Code and test scripts

Manage Feature files (Gherkin scripts)

• Projects / Directories etc

​

Calls on execution framework / tool to actually run the tests

• Does not have execution code

Executes test code to validate test cases described in Gherkin Scripts

​

Logs the results and creates reports

Execution Engines

Test Case Tools

Current Testing Sheet: https://docs.google.com/spreadsheets/d/1xKkqMtOcfs5hd7yDfm3wuYHJxO7ctn-G/edit#gid=2102432369

Testing (conformance & compliance testing)

Brainstorm Activity

Goal: Get input on how we see testing as a community and where to focus.

Prompting Questions:

• What testing means to you in the context of OpenHIE?
• Where should we be starting with Testing?
• How do implementers specify that they are OHIE compliant (does OHIE create that definition or does each implementation get to state that they are OHIE "compliant" )
• Should OHIE "certify" implementations?

​

• 20 minutes - in small breakout zoom groups
• Use the tool to create sticky notes in the section for your group
• One Unique idea to sticky notes
• MetroRetro Board: - https://metroretro.io/board/LBUU7ZT049OM

​

2. Share with the larger group

Link to testing presentation

26

FHIR - Shaun Grannis

OpenHIE 2021

Architecture Summit

Moving from Architecting to Implementing

Virtual Meeting February, 2021

#OHIEArchSummit

Agenda

29

FHIR

Prompting Questions:

• What are the opportunities to advance FHIR in the OHIE Community?
• What do we need to do as a community to support implementers?
• Challenges in supporting both HL7 V2 / V3 and FHIR.
• When should we be advancing FHIR?

​

Group Exercise:

1. 30 minutes - in small breakout Zoom groups
1. Use the tool to create sticky notes in the section for your group
2. One Unique idea to sticky notes
3. MetroRetro Board - https://metroretro.io/board/LBIA5UCETMAZ
• Share your sticky notes

2. Share with the larger group

​

​

30

Linking the Specification and FHIR IGs - Carl L

Strengthening the Feedback Loop - Jennifer

Strengthening the Feedback Loop Brainstorm Activity

Goal: Get input on how we engage implementers to get their feedback and learning back into the Architecture specification

Prompting Questions:

• How do we better engage implementers in contributing to the specification / architecture moving forward?
• How do we ensure we get success stores?
• How do we get implementers to bring implementations to the ARB or OHIE?

​

• 20 minutes - in small breakout zoom groups
• Use the tool to create sticky notes in the section for your group
• One Unique idea to sticky notes
• MetroRetro Board - https://metroretro.io/board/LBNITUVIGQX1

​

2. Share with the larger group

33

Unconference Slot - TBD

Expanding the Community - Shaun

Expanding the Community

Brainstorm Activity

Prompting Questions:

• What people or groups do we (the architecture Community) need to engage or engage more?
• How do we engage or better support the groups identified?

​

• 20 minutes - in small breakout zoom groups
• Use the tool to create sticky notes in the section for your group
• One Unique idea to sticky notes
• MetroRetro Board - https://metroretro.io/board/LB74STSAZX1S

​

2. Share with the larger group

36

2020 Roadmap - Jennifer

Expanding the Community

Brainstorm Activity

Prompting Questions:

• Based upon what we heard, what needs to be on our roadmap for 2021?

​

• 20 minutes - in small breakout zoom groups
• Use the tool to create sticky notes in the section for your group
• One Unique idea to sticky notes
• Group work tool-

​

2. Share with the larger group

38

Wrap Up - Jamie

Wrap Up

Whole Group Discussion

Prompting Questions:

• Any additional Action items for 2021?
• What topics do we need to cover in 2021?
• Meeting Feedback - How can we make it better next time?
• https://metroretro.io/board/LB74STSAZX1S

​

​

​

​

What did we want to happen?

40

What happened?

What should we continue?

What should we improve?

41

42

43