Plans for the transition from Stated Relationship file to OWL refset files

Plans for the transition from Stated Relationship file to OWL refset files

This is part of the wider Drugs and Substances improvements that are currently taking place. Other than the obvious content updates, these technical changes are those which will be likely to have the highest impact on those within our AG.

We need to discuss the plan and ensure that we have answered all of the possible questions in advance, in order that we have a workable plan with no unwanted surprises over the next few release cycles.

As a starting point, we should discuss the following:

1. The schedule of changes (see here: https://snomed.atlassian.net/wiki/display/RMT/Early+Visibility+-+Planned+changes+to+upcoming+SNOMED+International+Release+packages) (ie)

July 2018 - initial OWL refsets introduced
Jan 2019 - included in the Release package: a) Stated Relationship file b) the partial OWL axiom refset including all description logic features that cannot be represented in the stated relationship file.
The Extended OWL refset file will be available on demand.
July 2019 - the stated relationship file will be replaced by the complete OWL Axiom refset file. The stated relationship file will NOT be included in the international release; however, it may still be available on request to support migration to the OWL Axiom refset.

2. The communications required to ensure that ALL impacted parties are completely informed of the Schedule, and the changes that they may need to make in order to transition cleanly to the new format.

3. The technical changes that we need to make to the Release package itself, in order to support the planned schedule.

For example, when we "replace" the Stated Relationship file in July 2019, do we remove the file from the release package immediately (in Jan 2020 once everyone has had a chance to run the inactivation file through their systems), or do we take the more measured approach of inactivating all records and leaving the inactivated file in the package for, say, 2 years, and then planning to deprecate the Stated Relationship file by July 2021?

Further, should we be deprecating the file itself at all, or can we see any other (valid) use for the Stated Relationship file (obviously not just repurposing it for a completely different use!)?

Thanks very much,

Andrew

Copyright © 2026, SNOMED International