The Architecture Review Board (ARB) is lead by the Chief Architect. ARB members are community representatives who are committed to the Architecture Governance and Principles. 

  Deliverables 

Error rendering macro 'table-plus'

Notify your Confluence administrator that "Advanced Tables for Confluence" requires a valid license. Reason: EXPIRED

Members of the ARB

IndividualRepresents (OpenHIE Sub-Community and/or Organization)
Shaun Grannis
Regenstrief, Patient Identity Management Community (Chief Architect)
Jack Bowie
Apelon, Terminology Services Community
Bob Jolliffe
OpenHIE Health Management Information System Community
TBA
IntraHealth, InterLinked Registries Community, Health Worker Registry Community

Jose Costa Teixeira

PATH
Ryan Crichton
Interoperability Layer Community, Shared Health Record Community
Bryn Rhodes
Database Consulting Group, FHIR
Derek Ritz
ecGroup
Carl Fourie
Digital Square, Health Financing towards UHC Community
Josh Zamor
VillageReach, Supply Chain Community
Ron G Parker
Parker Digital Health Consulting Inc.
Daniel Futerman
Jembi Health Systems, OpenHIE Implementers, Health Financing towards UHC Community
James Kariuki
CDC

Adam Preston

Facility Registry Community

Steven Wanyee Macharia

Intellisoft
Aisha AbdulahiJohn Snow Incorporated

Kalechristos Negussie

Clinton Health Access Initiative

Vladimer Shioshvili

ICF
Haftamu Kebede YigzawMekelle University

Responsibilities of the ARB

Based upon real-world needs, the Architecture Review Board has the following responsibilities:

Champion the OHIE Community’s principles of "Adaptable" / "implementable", "Standards-based" and "Interchangeable" / "Swappable". 

Map the workflow priorities to real-world implementation needs.  Make decisions based upon expressed needs. 

Ensure the OHIE community is engaging in IHE and other interoperability specification development processes to meet implementer needs.

Develop workflows that appropriately leverage IHE and other standards and standards processes.  

Where standards don’t exist, advocate for the development of future standards solutions.

Advocate for standards-based interfaces.

Track emerging standards development processes and evaluate their usefulness to the OpenHIE community.

Enable plurality of architecture components.

Develop and maintain an architecture roadmap on a yearly basis. 

Support creating, curating, and publishing the OHIE Specification, including the architecture diagram, components specifications, and workflows that support patterns for data exchange.  

Routinely review and publish the specification.  
When changes or updates are requested, the ARB and the Community will discuss and establish consensus.  
Routinely review and publish the specification.  
When changes or updates are requested, the ARB and the Community will discuss and establish consensus.  
Solicit feedback from implementers and other OHIE community members.
Evaluate workflow additions or changes to assess the feasibility of incorporating into the OHIE framework, including determining whether the proposed workflow can be incorporated into an existing workflow with or without modification.
Ensure each workflow has a sponsor.
Make architectural decisions based on the implementer’s expressed needs.
Identify standards that best support the HIE user's needs.

Maintain a process for developing workflows

Determine, curate, and communicate Maturity Model updates.

Maintain a regular process for reviewing and updating the maturity of OHIE workflows
Review sponsor assessments and work with the sponsor(s) to establish consensus on the assessment.  
Determine, curate, and communicate OHIE testing strategy.
Evaluate profile and software changes and determine and prioritize testing needs.
Work with sub-communities to identify testing scenarios and cases to meet the architectural specification.
Routinely review and publish the OpenHIE Conformance Testing Specification.  
Curate the OpenHIE Conformance and Compliance testing approach.
Ensure each component, workflow scenario, and test sets have a sponsor.
Build OHIE community awareness and consensus around OHIE Conformance testing and possible country-level use.
Use Architecture and DevOps community meetings and mailing lists to facilitate discussions, share information, gather input, and establish consensus. 

Curate Reference Software lists.

Engage each of the OpenHIE sub-communities to nominate the proposed reference software(s) of the community.
Validate the community’s evaluation of the software against the Specification and Conformance Testing Framework.
Publish and curate the list of software on the OpenHIE wiki and correlate artifacts with the specification.

NOTE: It is not this board’s responsibility for identifying software (that lies with the sub-communities), however, it is the responsibility to validate the nominees and evaluate their submission based on the specification.

Support the community at large in understanding the OHIE architecture framework

Support emerging and existing OHIE community groups with onboarding on the fundamentals of the OHIE specification and architecture
Engage in other community calls as needed/appropriate to support the introduction to the architecture.  
Represent the OpenHIE architecture in LMIC and digital health community meetings and conferences as appropriate.  

This work is licensed under a Creative Commons Attribution 4.0 International License.