3. Options and recommendation for representing the Logic Profile
Plan for document development:
Subgroup meeting every two weeks.
Lead Editor(s) for the document:
Process: Discussion of scope and content topics at the subgroup meetings. Draft review by the MAG members, other AGs, internal teams, and stakeholders.
Timeline: Early draft to be reviewed at the April meeting. First draft delivered by the end of June.
Scope and Content topics to be covered and discussed:
Scope:
Formal representation of logical constructs for SNOMED CT
Subjects are out of scope:
Define the logic profile for SNOMED CT
OWL2 EL profile
EL features are included/excluded for SNOMED CT
DL could be potentially required in future, but it is out of the scope for this document
Summary of requirements from content development and implementation
Options for representing the logic profile
Recommendation
Technical specification - potentially a separate document.
Child Pages
- A development path towards an OWL-based SNOMED CT
- Examples of OWL in RF2 concept table format
- Examples of Logic Construct use
- Use case: multiple sufficient sets
- Examples of OWL in RF2 reference set format
- Key criteria and considerations for Recommendation
- Also necessary conditions not included in the core set of sufficiently defining conditions
- Face to Face Subgroup Meeting 6 - 8 June
- Options for Drugs Product Role
- Definition Status
- Serialization of OWL Axioms: Consistent Ordering
- Transformation between SNOMED CT and OWL expressions
Copyright © 2026, SNOMED International