Getting Started Guide
OHIE.orgDiscourseWikiAcademy
1.0-Beta
1.0-Beta
  • Getting Started Guide: Paths to Data Exchange
  • Select a Pathway
  • PATHWAY 1: Component and Data Exchange Projects
    • Pathway 1.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Document the Expected Value of the Project
      • Establish a Project Plan
    • Pathway 1.2 - Requirements and Design
      • Establish Training Programs
      • Determine Resources and Identify Constraints and Environmental Factors
      • Analyze the Environment and Context
      • Identify System Constraints
      • Document Requirements
      • Select Software/Component(s)
      • Testing
    • Pathway 1.3 - Implement, Support, and Scale
      • Establish a Support Plan
      • Implement a Scalability Plan
      • Communication and Roll Out
  • PATHWAY 2: Architecture
    • Pathway 2.1 - Governance, Value, and Scope
      • Identify Stakeholders
      • Determine and Document Roles and Responsibilities
      • Establish or Define Governance Structures
      • Determine Project Scope
      • Define Value of Health System Architecture
      • Establish a Project Plan
    • Pathway 2.2 - Requirements and Design
      • Inventory Existing Tools
      • Document Use Cases
      • Establish Architecture Principles
      • Document the Architecture
      • Establish Architecture Processes
      • Establish Standards
    • Pathway 2.3 - Implement, Support, and Scale
      • Communication and Roll Out
  • How to Provide Feedback / Input
  • Change Log
Powered by GitBook
On this page
  1. PATHWAY 2: Architecture
  2. Pathway 2.2 - Requirements and Design

Inventory Existing Tools

Architecture Level Project

PreviousPathway 2.2 - Requirements and DesignNextDocument Use Cases

Last updated 3 years ago

Inventory Existing Tools

When determining your strategy or road map, it may be useful to determine if there are existing tools that can support the desired information exchange use cases. When conducting the inventory, it may be useful to determine some of the following factors that will help in determining if use of the tool can be expanded to support the desired health information exchange use cases:

  • Implementation scope ( for example, the number of cases, patients or geographical scope of the implementation)

  • Ability to support data sharing through standards-based APIs / creation of standard message specifications (IHE profiles - See )

  • Ability to support the tooling

    • Documentation is present and easy to understand

    • Source code is accessible and programming languages are understood by developers

  • Ability to support applicable terminology data standards

Tools:

Reference: : (Chapter 4.2)

OpenHIE Architecture Specification
Digital Health Atlas
Digital Implementation Investment Guide