Guidance on the Version History

Guidance on the EMDN Version History document This guidance introduces the EMDN Version History document which provides a comprehensive historical record that acts as a bridge between all published EMDN versions and their changelog. What differs from the EMDN Changelog and the Summary of EMDN YYYY Submissions and outcome of annual revision? The EMDN Changelog document contains an overview of the annual updates. The document only reflects yearly changes, but it does not include the full structure and historical evolution of the nomenclature. The Summary of EMDN YYYY Submissions and outcome of annual revision includes all update submissions received through the public consultation and the Nomenclature Working Group. It focuses on the assessment outcomes for both accepted and rejected requests, providing the corresponding rationale for each decision, as well as the specific updates resulting from accepted and partially accepted requests. As an in-depth report on the annual revision, it does not provide a full overview of the Nomenclature or its entire evolution; instead, the focus remains strictly on the update requests received within that specific calendar year. The purpose of the EMDN Version History is to combine the published EMDN versions with their corresponding changelog. This results in a document that acts as a bridge between the two and completes any potential knowledge gaps. What type of information is included in the EMDN Version History? The document is organized into 4 main sections:

- EMDN CODES ARCHIVE-EMDN CURRENT RELEASE

- PREVIOUS RELEASES

- CHANGELOG

The individual sections are detailed below (note that, for clarity, the fields refer to the v.2026 Version History as an example; in future releases, the structure will remain consistent, with additional modules added to include codes, terminality info, and actions for each new publication): EMDN CODES ARCHIVE section dedicated to the historical archive of EMDN codes, allows users to filter out inactive codes and search for obsolete codes

HISTORICAL

(ALL EMDN CODES)

Nomenclature code. This column serves as an archive containing all codes ever created, including those that have been deleted. LEVEL The hierarchical level for all codes (both active and inactive). Displays the hierarchical level for all active and inactive codes. It allows for filtering across the full historical record, maintaining visibility of the hierarchy for deleted codes. ACTIVE/INACTIVE Indicates whether the code is ACTIVE or INACTIVE in the current release. If a code has been deleted, this field will display 'INACTIVE'. EMDN CURRENT RELEASE: v.2026 Section dedicated to the latest published version of the EMDN. ACTIVE EMDN CODES in v_2026 Nomenclature code. This column contains only the codes currently active and present in the latest published release. LEVEL as in v_2026 The hierarchical level assigned to codes present in the current release of the nomenclature.

TERMINAL LEVEL in v_2026 (YES/NO) Indicates whether the level is terminal (the lowest level of a section) in the current version. If a code has been deleted, this field displays 'OBSOLETE'. ACTION in v_2026 If a code or level was updated, this column specifies the type of change from the previous version (e.g., DELETION, NEW CODE, MODIFIED, or SPLIT). TERM as in v_2026 Term in the current release PREVIOUS RELEASES Section dedicated to the previous version(s)of the EMDN TERM as in v_2025 The term as it appeared in the specified EMDN version. In this case EMDN v.2025 TERMINAL LEVEL in v_2025 Indicates whether the level is terminal (the lowest level of a section) in that specific version of the EMDN, in this case EMDN v.2025. If a code has been deleted from the previous version, this field displays 'OBSOLETE'. TERM as in v_2024 The term as it appeared in the specified EMDN version. In this case EMDN v.202 TERMINAL LEVEL in v_2024 Indicates whether the level is terminal (the lowest level of a section) in that specific version of the EMDN, in this case the first release EMDN v.2024. CHANGELOG Full code history, from creation to the latest updates, and detail of changes ACTION DETAILED Change details as documented in the published changelog(s). EMDN RELEASES List of all EMDN versions in which the code has been present. LAST UPDATED IN EMDN RELEASE The most recent version where the code or term was modified. If it has remained unchanged since its creation, this field shows the version of origin (first release of appearance). INTRODUCED IN EMDN RELEASE The specific EMDN release in which the code was first created. TYPE OF UPDATE IN THE EMDN RELEASE A chronological list of updates with their respective EMDN release (e.g., MODIFIED TERM in v.2025; DELETION in v.2026).

The first section (EMDN CODES ARCHIVE) is an archive of all codes ever published, showing their hierarchical level and whether they are currently active or inactive. The second section (EMDN current release) contains the details of the newly published EMDN version: code, term, level and terminal level indication. There is also indicated the status of the code, that is to say the change made from the previous version to the current one (i.e. modified/obsolete/new/split). When a code is deleted and marked as 'obsolete', the version history replaces the term with the word 'OBSOLETE'. The third section (Previous Releases) lists the terms used in previous versions of the Nomenclature, along with an indication of whether the level was terminal in that specific release. The last section (Changelog) contains a detailed changelog, chronologically listing all modifications made to the code. The log includes the precise details of each change, the EMDN releases where the code is included, the specific EMDN release in which it was introduced, and when/in which version the last update was made (If it has remained unchanged since its creation, this field shows the first release of appearance, if this corresponds to the first one it shows v.2024). Finally, it specifies the list of each update type with the corresponding EMDN release.

This structure enables a direct comparison between the level terms and offers convenient access to the list of changes that occurred on that specific level. Examples on the Best Ways to Read the document This section illustrates practical scenarios where the EMDN Version History document can be used to resolve specific queries regarding code history and evolution.

1. 1. "I need to know exactly when my code was first introduced into the EMDN nomenclature." Start by searching for your code in the ' Historical (all EMDN codes)' column of the Archive section. You can then find its initial version by checking the 'INTRODUCED IN EMDN RELEASE' column in the Changelog section.
2. 2. "I need to understand what the old term was for my code before the latest update, to ensure continuity." This document allows for a direct comparison between current and previous terms. First, locate your code in the Active EMDN Codes list, then refer to the 'Last Updated' column to see when the change occurred. You can then compare terms side-by-side across the Current and Previous Release sections.
3. 3. "My code is no longer in use. I need to identify when it became obsolete or was removed from the active list." Start by searching for your code in the ' Historical (all EMDN codes)' column of the Archive section. You can then identify when a specific code became obsolete in different ways, you can check out:

• - the changelog section; this section explicitly shows the version and year a code became obsolete. You can filter the Action Detailed column using the keyword "DISCARDED" or the Type of Update column using "Deletion".
• - the ACTION in v.# column in the EMDN current release section; here, codes deleted in the current update cycle indicate 'DELETION’ and you will find ‘OBSOLETE’ in the corresponding term column.

1. 4. "I know my code was modified, but I need to know in which year/version the change occurred and what exactly was done." Start by searching for your code in the ' Historical (all EMDN codes)' column of the Archive section, then look at the changelog section. The column “ TYPE OF UPDATE IN THE EMDN RELEASE ” chronologically lists all modifications made to the code. This allows you to determine when a specific code was modified (or changed) and specifies the update type and corresponding release for every revision. The detail of each modification is listed in the “ACTION DETAILED” column.
2. 5. "I need a full, high-level view of how the EMDN nomenclature has evolved over the past few years, not just the latest changes." The Version History provides a comprehensive record that acts as a bridge between all published versions and their respective changelogs. For a complete overview, consult the Previous Releases

section for historical terms and integrate this with the Changelog section to view a chronological list of modifications. The Archive section lists every code that has ever existed in the nomenclature, including its hierarchical level and whether it is currently active or inactive.

1. 6. "I need to verify that my code has never undergone any modifications since its initial release." Start by searching for your code in the ' Historical (all EMDN codes)' column of the Archive section, then refer to the Changelog. If a code is unchanged, the ' Type of update ' and ' Action detailed ' columns will be blank. Additionally, for codes never modified since their creation, the 'Last updated in EMDN release' field will reflect the version where the code first appeared (e.g., v.2024).

7. "How can I verify if my code is no longer terminal?”

Start by searching for your code in the ' Historical (all EMDN codes)' column of the Archive section. Then you can either:

• - compare the terminal level indication in the EMDN Current Release section with that in the Previous Releases section. If the previous version showed the level as terminal but the current version does not, the status has changed.
• - check the 'Last updated in EMDN release' column, as this field indicates the release in which the code was split and is no longer terminal.
• - check the ‘Type of update in the EMDN release ' column, this field indicates the type of modification the code underwent and will therefore report 'split' and the corresponding release in which it occurred."

1. 8. “How can I verify any modifications made specifically to the 4th level?” Filter, using the level column, for entries corresponding only to the 4th level. Once filtered, use the action in v.# (YYYY), type of update in the EMDN release, and last updated in EMDN release columns to view all the modifications, even less evident ones such as splits where the code is no longer a terminal level.