Child pages
  • Architecture Review Board Members, Responsibilities and Deliverables
Skip to end of metadata
Go to start of metadata


DeliverableDescriptionDeliverable TypeReview CycleLast Review Date
OpenHIE SpecificationDocumentation of the OpenHIE Architecture, components and workflows.  OHIE Website
Dec 2019
OpenHIE Architecture & Standards  Description of the OHIE Architecture and the components.Wiki Page
Sept 2019
OpenHIE Diagram Movable OptionsVersion of OHIE diagram with movable components for use by project teams and implementers.  Movable Diagram Wiki Page AnnuallyJan 2020
Reference TechnologiesList of reference technologies with links to their repositories.   Wiki Page
July 2018
OpenHIE Testing Strategy
Coming Soon

Workflow Collection MaturityOpenHIE Workflows and the ARB's description of their known use and maturity.  

Multiple Wiki Pages

Sept 2019
OpenHIE IHE Integration StatementsIHE Integration testing statements for OpenHIE reference software.  Wiki Page
May 2016
OpenHIE Standards and ProfilesMessage standards and profiles used in OpenHIE.  Wiki Page
June 2019
Privacy and SecurityOpenHIE Architecture Topic Page that makes a statement on Privacy and Security.  Wiki Page
June 2016
Team Governance ArtifactsDescriptionDeliverable TypeReview Cycle Last Review Date
Architecture Review Board Members, Responsibilities and Deliverables ARB Members, ARB / Architecture Community Responsibilities and Deliverables.  Wiki Page (This page
Dec 2019
Architecture Processes
Update Coming Soon

Based upon real-world needs, the architecture community has the following responsibilities:

  1. Champion the OHIE Community’s principles of "Adaptable" / "implementable", "Standards-based" and "Interchangeable" / "Swappable"
    • HOW:  Map the workflow priorities to real-world implementation needs.  Make decisions based upon expressed needs. 
    • HOW:  Ensure the OHIE community is engaging in IHE and other interoperability specification development processes to meet implementer needs.
    • HOW:  Develop workflows that appropriately leverage IHE and other standards and standards processes.  
    • HOW: Where standards don’t exist, advocate for the development of future standards solutions.
    • HOW:  Advocate for standards-based interfaces.
    • HOW: Track emerging standards development processes and evaluate their usefulness to the OpenHIE community.
    • HOW:  Enable plurality of architecture components.
    • HOW: Develop and maintain an architecture roadmap on a yearly basis. 
  2. Support creating, curating, and publishing the OHIE Specification, including the architecture diagram, components specifications, and workflows that support patterns for data exchange.  
    • HOW: Routinely review and publish the specification.  
    • HOW: when changes or updates are requested, the ARB and the Community will discuss and establish consensus.  
    • HOW: Routinely review and publish the specification.  
    • HOW: when changes or updates are requested, the ARB and the Community will discuss and establish consensus.  
    • HOW: solicit feedback from implementers and other OHIE community members.
    • HOW: 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.
    • HOW: Ensure each workflow has a sponsor.
    • HOW: Make architectural decisions based on the implementer’s expressed needs.
    • HOW: Identify standards that best support the HIE user's needs.
    • HOW: Maintain a process for developing workflows
  3. Determine, curate, and communicate Maturity Model updates.
    • HOW: Maintain a regular process for reviewing and updating the maturity of OHIE workflows
    • HOW: Review sponsor assessments and work with the sponsor(s) to establish consensus on the assessment.  
  4. Determine, curate, and communicate OHIE testing strategy.
    • HOW: Evaluate profile and software changes and determine and prioritize testing needs.   
    • HOW: Work with sub-communities to identify testing scenarios and cases to meet the architectural specification.
    • HOW: Routinely review and publish the OpenHIE Conformance Testing Specification.  
    • HOW: Curate the OpenHIE Conformance and Compliance testing approach
    • HOW: Ensure each component, workflow scenario, and test sets have a sponsor.
    • HOW: Build OHIE community awareness and consensus around OHIE Conformance testing and possible country-level use.
    • HOW: Use Architecture and DevOps community meetings and mailing lists to facilitate discussions, share information, gather input, and establish consensus. 
  5. Curate Reference Software lists.
    • HOW: Engage each of the OpenHIE sub-communities to nominate the proposed reference software(s) of the community.
    • HOW: Validate the community’s evaluation of the software against the Specification and Conformance Testing Framework.
    • HOW: 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.
  6. Support the community at large in understanding the OHIE architecture framework
    • HOW: Support emerging and existing OHIE community groups with onboarding on the fundamentals of the OHIE specification and architecture
    • HOW:  Engage in other community calls as needed/appropriate to support the introduction to the architecture.  
    • HOW:  Represent the OpenHIE architecture in LMIC and digital health community meetings and conferences as appropriate.