Project Overview

The Terminology Exchange Service (TES) will support public health agencies (PHAs) to process, ingest, and utilize eCR data more efficiently and effectively. The TES will centralize the curation of condition-associated codes, such as the Reportable Conditions Knowledge Management System (RCKMS) value sets, the electronic Reporting and Surveillance Distribution (eRSD), and other sources, making them readily accessible to PHAs through an API and a searchable user interface accessible via aimsplatform.org. The TES will be customizable, designed to meet the unique needs of public health and facilitate integration within PHA infrastructure.

The TES will offer condition-curated value sets for codes that both identify and contextualize a given condition, such as lab results and symptoms, to help ensure that data is relevant and actionable. It will also streamline vocabulary management by centralizing and curating relevant codes, reducing duplication of effort across PHAs.

In addition, the TES will provide narrative description look-ups for value sets captured within the tool and keep users informed of content and value set updates.

Components:

• Interface Methods

  • GUI Web Application

  • API

• Infrastructure

  • HAPI FHIR Server

  • aimsplatform.org URLs

• Curated Content

  • eRSD

  • RCKMS Reporting Specifications

High Level Scope

The primary objective of this project is to deploy a minimum viable product (MVP) version of the TES within Q3 2024, containing all components listed above.

A secondary objective of this project is to provide continuous updates to the TES, including but not limited to the following features:

• Integration with Value Set Manager and tooling within Value Set Manager for streamlined content updates

• Additional code sources, such as RxNorm with medication to condition associations

Timeline & Critical Path

Critical Path Deliverable & Status

• App & API Development - (90%)

• Content Development - (90%)

  • Reporting Specifications Generation (95%)

  • Condition Grouper generation tooling development (85%)

    • Manifest creation (75%)

    • Package creation & deployment (95%)

  • Condition Grouper generation (95%)

• Infrastructure (Ruvos) - 30%

Executive Timeline Overview

Image RemovedImage Added

Supportive Project Documentation and Additional Resources

• View file
  name condition_list_20240827.xlsx

  - here is a current export of the conditions that RCKMS will generate reporting spec groupers for.

• View file
  name TES_Condition_Groupers_20240911.xlsx

• Jira Legacy
  server System Jira serverId 10cfeb5a-36fc-31d7-beda-13e50b1effe2 key ECR-9025