Exploring Terminology

Orchestrate maintains reference code systems and provides several API operations to standardize and classify a variety of source data to standard systems and value sets. The Developer Portal allows users to explore these terminology resources within a graphical user interface which provides the same results available via the API.

Browse Reference Code Systems and Value Sets

The Browse tab of the Developer Portal enables users to view terms within all available reference code systems. This feature is typically used to confirm that Orchestrate maintains a particular reference code, to compare reference value set membership, or to identify potential codes to include in a custom value set.

To browse reference codes within a system in the Browse tab:

  • Select a reference code system from the drop-down menu. The most commonly used code systems are grouped at the top of the list and the list is filterable by text.
  • Enter a search term, which can be a code and/or display. Search is exact match for codes (including the . in ICD9 and ICD10 codes) and/or multiple string match (space-separated strings in any order).

Results display all matching terms within the selected code system as well any any related terms (via crosswalks to other reference code systems). Each result also displays the number of reference value sets which contain that reference term.

To explore reference value sets:

  • Click on the ‘Value Sets’ button to display value sets, organized by value set scope, for that term.

To view value set membership across terms in the results:

  • Click on check boxes for one or more value sets to select value sets to be listed in the results table and Click the ‘X’ to close.
  • Each selected value set will display a column, with check marks indicating value set membership for each term.
  • Click the ‘X Clear Comparison’ button to remove/reset the value set columns.

Translate Source Terms

The Translate tab of the Developer Portal enables users to see how the Terminology service translates source terms. This tab uses the $translate operation which is a superset of the domain-specific standardize operations shown in the Developer Portal Sandbox.

To view how the Terminology service translates a term:

  • Select a domain from the drop-down menu. The most commonly used domains are grouped at the top of the list and the list is filterable by text.
  • Optionally enter a source code system. This may be used, for example if the source code system indicates that the term is an ICD-10-CM code, but is not required.
  • Enter a source code and/or display.
  • Click ‘Translate’

The source term criteria is posted to the $translate operation and results are summarized in a simple table. Matches contain reference code, display, and system as well as technique which produced the potential matches. The Terminology service matches to no more than one target term per reference code system.

Techniques may include:

Technique Description
Natural Language Processing The Terminology service applies rules to the source display and matches to reference term displays based on ‘nearness’ scores (‘Bag of Words’ or ‘Category’ are the names of the technique returned in the $translate response).
Exact Code The Terminology service matches source code to target code, ignoring or including dots and dashes depending on the target code system.
Parsed Code The Terminology service identifies potential codes in the source display.
Exact Name The Terminology service matches source display to target display exactly.
Data Dictionary The Terminology service matches source code or display to exactly to specific strings in a data dictionary (‘Alias’ is the name of the technique returned in the $translate response).
Crosswalk The Terminology service applies reference crosswalks to each reference mapping as it is identified. Crosswalks will therefore supercede other mapping techniques when available.

You can provide feedback through a simple form. Any criteria currently populated in the source term fields will be automatically included with your comments. Feedback, including missing or bad mappings or other suggestions, is welcomed and will be reviewed by the CareEvolution team. You will not receive a specific reply, but please know that we work to continuously improve our translation functionality and value your feedback.