Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

Add functional and non-functional requirements, document repository or links to help with TES management.

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

  • 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 - (95%)

  • Content Development - (95%)

    • Reporting Specifications Generation (95%)

    • Condition Grouper generation tooling development (95%)

      • Manifest creation (95%)

      • Package creation & deployment (95%)

    • Condition Grouper generation (99%)

  • Infrastructure (Ruvos) - 45%

  • PRR - 15%

Executive Timeline Overview

image-20240923-195230.png

Supportive Project Documentation and Additional Resources

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

  • ECR-9025 - Getting issue details... STATUS

  • No labels