Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In the current version this is achieved via service requests to the technical team.
You can use the form (or raise an INFRA devops support ticket directly in JIRA) to request a new report (either in an existing category, or requesting a new one), as done for AP issues and improvement requests.
This will be processed and prioritised along with other AP and RP feature/improvement requests for inclusion in a future release.
Go to the Training AP in your web browser.
The Training AP uses the SNOMED International IMS to authenticate and authorise access via a registered account.
If you're already registered with an existing SNOMED International Jira/Confluence account which has been granted AP access then you can use those credentials.
If you are not logged in to the AP, your web browser will be redirected to IMS for account authentication and access authorisation. You will see the IMS login screen in your web browser. Enter your account name and password.
If you check the Automatic log in box before pressing Log In, your credentials will be cached, so that your account name and password are automatically entered in the form when you next need to log in.
With your credentials entered, press Log In.
If your credentials cannot be authenticated or your account is not authorised for access to the AP, then IMS will reload the login screen so you can try again with updated credentials.
Once authenticated and authorised, your web browser will then be redirected back to the AP URL which triggered the authorisation and authentication process.
At this point you will have an authorised account session cookie in your web browser which means you will no longer be prompted for account credentials until either you have explicitly logged off or closed your web browser.
If the main URL above was used to open the AP, you will then see the appropriate Dashboard - My Tasks view, and a blue notification box will show in the page header stating "All tasks loaded" (the header notification will automatically close after a brief interval, or you can press the X button in its upper right corner to close it manually).
The upper left corner of the site header also shows a diagonal ribbon (green/gold) labelled "TRN" to highlight that this is the Training Authoring Platform.
If this is the first time you have used the AP (or all your existing tasks have been either promoted or deleted) then you will see an empty Dashboard listing view. This is where your tasks will be listed once created.
At this point you're in the Training AP and ready to author content in your own tasks or review content created in other tasks by other authors.

Not the Training AP? If the green and gold "TRN" corner banner is not presented in the upper left corner, please verify the domain name in your browser's address bar, as you may have inadvertently logged into the International AP or a Managed Service AP (perhaps via a bookmarked address) which can look almost identical in style and layout apart from the task names of any previously created tasks.
If this is the case, simply logout and start over with the Training AP URL ( ).

Go to the International AP in your web browser.
The International AP uses the SNOMED International IMS to authenticate and authorise access via a registered account.
If you're already registered with an existing SNOMED International Jira/Confluence account which has been granted AP access then you can use those credentials.
If you are not logged in to the AP, your web browser will be redirected to IMS for account authentication and access authorisation. You will see the IMS login screen in your web browser. Enter your account name and password.
If you check the Automatic log in box before pressing Log In, your credentials will be cached, so that your account name and password are automatically entered in the form when you next need to log in.With your credentials entered, press Log In.
If your credentials cannot be authenticated or your account is not authorised for access to the AP, then IMS will reload the login screen so you can try again with updated credentials.
OR In the Review Tasks view, press the feedback status icon (if present), on the task you want to open. This opens the Task View to the context of the Feedback activity tab. This option is only available once at least one review comment has been added by either a reviewer or author.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
The Task Review and Feedback layout is presented, showing concepts to review, concepts approved, and inferred concept changes within the task. This layout maintains the Activities panel (Left Sidebar), as well as the Options panel menu for navigation back to other task contexts.
Once authenticated and authorised, your web browser will then be redirected back to the AP URL which triggered the authorisation and authentication process.
At this point you will have an authorised account session cookie in your web browser which means you will no longer be prompted for account credentials until either you have explicitly logged off or closed your web browser.
If the main URL above was used to open the International AP, you will then see the Dashboard - My Tasks view, and a blue notification box will show in the page header stating "All tasks loaded" (the header notification will automatically close after a brief interval, or you can press the X button in its upper right corner to close it manually).
If this is the first time you have used the AP (or all your existing tasks have been either promoted or deleted) then you will see an empty Dashboard listing view. This is where your tasks will be listed once created.
At this point you're in the International AP and ready to author content in your own tasks or review content created in other tasks by other authors.
Not the International AP? If you have access permissions to more than one Authoring Platform, it's possible to inadvertently log into one of the others (perhaps via a bookmarked address) when the International AP was your intention, and they can appear almost identical in style and layout apart from the task names of any previously created tasks. Please verify the domain name in your browser's address bar if you're not sure, and if it's not what you intended, simply logout and start over with the International AP URL ().
EITHER (from anywhere in the application)
Open the page header drop down menu and press Review Tasks in the overlaid menu options list.
OR (from any Dashboard view)
Press Review Tasks in the Dashboard view left sidebar menu.
The Dashboard Review Tasks view is presented.
EITHER In the Review Tasks view, press the name link on the task you want to open. This opens the Task View to the context of the Feedback activity tab.
If task status is Ready for Review and the review status is Available (not yet claimed) this action will claim it for review and assign you to it as a Reviewer. The task will change state to In Review and its review state will become Claimed.
If task status is In Review and review is Claimed this will re-open the task for review and show any changes made to concepts in the task.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
The Task View Review and Feedback layout is presented, showing concepts to review, concepts approved, and inferred concept changes within the task. This layout maintains the Activities panel (Left Sidebar), as well as the Options panel menu for navigation back to other task contexts.
Claimed for review tasks are only visible in the Review Tasks view to the people named in the Reviewers list. It's possible to add/remove names from the Reviewers list whilst a review is in progress, to support nominating other people deputizing as reviewers, or switching to a replacement reviewer. This means it's also possible that the original claimant will no longer see the task in the Review Tasks list if they have been subsequently removed from the Reviewers list.
An Author can add people to the Reviewers list after submitting for review, which will have the same effect for each Reviewer as if they had claimed the task for review from the Available state. This allows an author to nominate a particular reviewer (or selected set of reviewers) when submitting for review.












US spelling
The international Authoring Platform user interface uses en-US spelling for its labels, hence the spelling of words such as "favorite" in this guide.
In a Task View - Saved List entry, press Add to Project Favorites to extend the Project Favorites list with that concept.
If no project favorites have yet been added then the Task View - Saved List content panel only shows the task saved concepts.
After adding at least one saved list item to the Project Favorites, the content panel updates to show the Project Favorites list below the task Saved List.
If any concepts have been saved as a project favorite in any task within the project, then all tasks in that project will show the Project Favorites list in their Task View - Saved List.
The Task View web page automatically picks up changes when first loaded, but it may need to be refreshed to pick up any changes made by others whilst it remains open in the web browser.
Each item in the Project Favorites list has the following:
Primitive or Fully Defined button (status definition icon)
Preferred Term
View in Taxonomy button
Clone this concept button
Remove from Project Favourites button
Project Favorites actions function in exactly the same way as their Saved List counterparts described in Add a concept to my task Saved List and act on saved concepts, with the notable exception of Remove from Project Favorites which does exactly as it says, as soon as it is pressed.
Removing a concept from the Project Favorites list by mistake
If a concept is removed by mistake and it is not in the Task View - Saved List then it is probably wise to go back to Search, add it into the Task View - Saved List, and then add it back into Project Favorites (in case another task within the project still needs to use it).


Press More details at the start of a search results row (also the definition status icon).
This opens the Concept Information pop-up window (as described in ).
Open a concept for editing, for example: |Secondary diabetes mellitus (disorder)|. The concept header contains the Add GCI Axiom button. The button icon is a solid rounded square containing a "plus" symbol.
Press the Add GCI Axiom button in the concept header. A new General Concept Inclusion panel will appear below the concept relationships containing a single empty Is a attribute.

Press the search result FSN term (Edit) to open the concept in the Edit Panel.
For active search results, press View in Taxonomy to open the concept in the Task View - Taxonomy tab.
The display context changes to Task View - Taxonomy , with the trigger concept as the focus for the taxonomy listing.
For inactive concepts in search results, the View in Taxonomy button is replaced by an Inactive Concept icon.
Press Add to Saved List to add the search result concept to the task Saved List.
Press Clone this concept to create a new unpublished cloned version of the concept in the Edit Panel. This is equivalent to creating a new concept and entering its lexical and logical model content from scratch.
Drag the parent concept (|Diabetes mellitus (disorder)| for this example) as a target for the GCI Is a relationship.
Press the Add New Relationship "plus" button within the GCI panel. Use type-ahead search to enter and select Due to (attribute) as the relationship type.
Use type-ahead search to enter and select |Disease (disorder)| as the target value for the new Due to attribute.
Save the concept.
Show the stated view of the concept diagram. Diagram shows empty GCI box with reverse subtype indicator.


















EITHER (from anywhere in the application)
Open the page header drop down menu and press All Projects in the overlaid menu options list.
OR (from any Dashboard view)
Press All Projects in the Dashboard view left sidebar menu.
The Dashboard All Projects view is presented.
The SNOMED CT Authoring Platform (and related services) is a web-based application for collaborative authoring of SNOMED CT content. It enables content teams to:
Author new concepts in the SNOMED CT International Edition and Local Extensions.
Update published concepts in the SNOMED CT International Edition and Local Extensions.
Review content changes made by authors.
Implement an International concept request submission (submitted/assigned via the International CRS platform).
Implement a US Edition concept request submission (submitted/assigned via the US CRS platform).
Implement Local Extension concept requests (submitted via the SNOMED CT Managed Service Request Management Portal)
Classify content changes.
Validate content changes.
Promote content changes for inclusion in the next SNOMED CT International Edition and Local Extension releases.
Merge changes from other authors into my tasks within the same project (task rebase).
Merge changes from other projects into my project (project rebase).
Press a manual SAC checkbox to toggle its status.
It will show a green ticked box when checked, indicating its condition is met.
When all mandatory task-level SAC conditions are met for a Complex task then promotion is enabled and Promote This Task to the Project in the Task View - Task Details will become active.
The example shown in the screenshot shows a Complex task which requires a review to be completed ("Review complete" mandatory automated Task-level SAC) and also for the author to confirm that the task validation report has no task-level RVF assertion failures ("RVF Report Clean" mandatory manual Task-level SAC).
Once task promotion is enabled, follow the non-complex task steps (included below) to complete promotion of the task.Although the screenshots show simple tasks without task-level SAC, the steps to promote once it is enabled are the same for all tasks.
Press Promote This Task to the Project in the Task View - Task Details panel actions button list
A "Preparing for task promotion" notification is presented in the page header, and the Promote This Task to the Project button is disabled.
Task promotion has implicit checks for the following conditions:
No content changes made in the task.
Classification has been run in the task.
Classification was started but either failed to complete or has not completed.
The Complex slider control in the upper-right of the Task View - Task Details panel defines whether or not a task is Complex.
Move the Complex slider to the right to set the task as Complex.
This activates any task-level >Service Acceptance Criteria (SAC)> which are defined within the parent project SAC configuration.
Task-level SAC are presented in two lists, between the Task Details section and the Edit Task Details button in the Task View - Task Details panel, and are common to all Complex tasks within the project.
Automatic Task-level SAC are listed to the left, with >Manual Task-level SAC to the right.
Automatic SAC have a yellow warning triangle icon if not yet met, and a green tick if their automated system checks confirm they are satisfied.
Manual SAC are presented initially as open checkboxes, each of which can be interactively checked (green-ticked) when the user's role-based access permissions match those configured for that SAC control.
Until all mandatory task-level SAC are met, task promotion will be blocked and Promote This Task to the Project in the Task View - Task Details panel actions button list will not be enabled.
Enter a target value for the Axiom Is a relationship, by typing in the target value box - once 3 or more characters are entered, type-ahead searching populates a drop-down selection box with matching concepts.
Select the desired concept in the options list to be the parent "type" for the new concept.Relationship target values can also be populated by drag and drop from Taxonomy, Search Results or Saved List entries.
When the form elements are fully populated (and adjusted from defaults if needed), press Save Concept in the Concept Header. This sends the entered details to the Terminology Server and the concept is assigned a new SCTID.
A Saving new concept notification is presented in the main page header.
The diagram view is populated with the FSN and SCTID assigned by the save process.
On completion of the save request, a Concept saved: <fsn-description> page header notification is presented.
The diagram view at this stage does not show the Axiom Is a relationship. This is because it defaults to the Inferred view, which requires the new concept to be classified to become populated.
You can use the buttons in the diagram menu bar to switch the diagram to Authoring Form (AF) or Stated view - either of which shows the relationship regardless of the concept classification status.
Press Create New Concept at the top of the left-hand menu bar.
A new outline concept is presented in the Edit panel, with a matching outline in the Diagram Panel, containing the following essential elements:
Fully Specified Name (FSN)
Preferred Term (Synonym)
Axiom (containing one Is a relationship)
All three of these must be populated with content before the concept can be saved.The cursor context is automatically moved to the text box for the Fully Specified Name (FSN), ready to receive its description text.
Enter the text description for the FSN, which must end with a valid SNOMED CT semantic tag (if not valid, warnings will be displayed when saving).
The FSN term (without the semantic tag) is automatically copied into the Preferred Term description field.
The default settings for case sensitivity can be adjusted to suit the content at this point, via the options box to the left of the text term on each description row (if the case sensitivity does not match the content, warnings will be displayed when saving).



Any time, subject to occasional maintenance - the service is an online web-based application running continuously between occasional scheduled or emergency maintenance.
Scheduled maintenance may include new features, improvements, defect fixes and hosting environment updates.
Emergency maintenance may include operating system patches and security updates as well as high priority defect fixes.
The Authoring Platform is a web services application designed to be used on a personal computer with a good internet connection via the Google Chrome web browser.
Recommended client platform requirements:
Operating System and hardware specifications as for Chrome
Minimum monitor resolutions:
1600 x 900 px (HD+ 16:9)
1680 x 1050 px (WSXGA+ 16:10)
Internet connection:
Broadband (4G minimum)
Other combinations of web browsers, machine hardware, lower screen resolutions and slower internet connectivity may still work but are not optimised and not supported.
When Search by Template results are found (and logical and lexical or logical not lexical is selected), a green Transform button will be presented adjacent to the blue Download Selected Results button at the end of the search results listing.
Press the Transform button to present the Template Transformation pop-up dialogue.
EITHER (from anywhere in the application)
Open the page header drop down menu and press My Projects in the overlaid menu options list.
OR (from any Dashboard view)
Press My Projects in the Dashboard view left sidebar menu.
The Dashboard My Projects view is presented.
The SNOMED CT Reporting Platform (RP) is a gateway to reports which can run a range of queries against content created or updated in the active authoring cycle for SNOMED CT.
Queries are structured into categories for ease of definition, navigation and retrieval, such as Ad-Hoc Queries, Release Validation and Quality Improvement.
The results of these queries can support pre-release validation of issues not supported by the Authoring Platform (for instance MRCM rules such as attribute cardinality). They can also be used to analyze the structural quality of SNOMED CT, to identify potential issues (for instance attribute usage for a given sub-hierarchy) which can then be addressed via content change projects in the Authoring Platform.
For the content team it enables iterative work to define complex QA rules that are eventually used for the Release Validation Framework (RVF) assertions (such as case significance). As a content release planning and tracking tool it can show the number and types of changes made during a SNOMED CT release cycle, and from one release to the next.











Classification is current.
Classification has no results to accept.
Classification results have been accepted.
Review has been completed.
If no content has been changed on the task when promotion is initiated, a Promote Task pop-up notification states the there are no changes to promote.
Press Return to Task (or press the X in the upper right corner) to close the pop-up.
If content changes have been made but any of the other conditions are not yet satisfied when promotion is initiated, a Promote Task pop-up notification shows their statuses, with action options to cancel the promotion, or to continue if task changes are considered sufficiently safe to update the project level content without satisfying these conditions.
Press Return to Task (or press the X in the upper right corner) to close the pop-up and cancel the promotion without changing project content or the task status.
Press Promote Anyway to continue promotion.
A "Promoting task..." notification is presented in the page header whilst branch content changes are merged to the project level.
During promotion, the task content branch is locked to prevent any further changes, and a warning notification is presented below the Edit Task Details action button in the Task Details panel.
Whilst this is present, changes cannot be made to the content saved in the task branch, and action buttons other than Edit Task Details and Submit for Review become inactive.
Once task promotion is completed, a "Task successfully promoted for <task-identifer>" notification is presented in the page header.
Following promotion no further changes are allowed on the task content branch, all action buttons in the Task Details panel become inactive, and a warning notification is presented below the now inactive Edit Task Details action button.
Role-based access controls apply to manual task-level SAC
Early Visibility Notice if Required
Manual spell check
Review complete
RVF Report Clean
International Authoring - Task SAC - Examples
If the user's authenticated account session roles do not include edit permissions for the task (such as when viewing another author's task), the current manual SAC status will be shown, but cannot be set.












Promoting tasks with warnings
Pressing Promote Anyway is tacit acceptance of any warning statuses, with implied responsibility for by-passing these safeguards and the consequent unclassified and/or unreviewed content changes that will be promoted from the task to the project level.
Promoting unclassified content changes is a quality assurance risk that can be avoided relatively easily, since it typically takes less than ten minutes to run classification (if only to confirm no results).
OR (from any Dashboard view)
Press My Tasks in the Dashboard view left sidebar menu.
The Dashboard My Tasks view is presented.
EITHER Go to the AP domain name web address. The default AP page is the Dashboard My Tasks view.
OR Go to the AP home page web address. This opens the Dashboard My Tasks view.
OR (from anywhere in the application)
Open the page header drop down menu and press My Tasks in the overlaid menu options list.
EITHER Go to the AP domain name web address. The default AP page is the Dashboard My Tasks view.
OR Go to the AP home page web address. This opens the Dashboard My Tasks view.
OR (from anywhere in the application)
Open the page header drop down menu and press My Tasks in the overlaid menu options list.
Go to the International AP in your web browser.
The International AP uses the SNOMED International Identity Management System (IMS) to authenticate and authorise access via a registered account.
If you're already registered with an existing SNOMED International Jira/Confluence account which has been granted AP access then you can use those credentials.
If you are not logged in to the AP, your web browser will be redirected to IMS for account authentication and access authorisation.
You will see the IMS login screen in your web browser. Enter your account name and password.
If you check the Automatic log in box before pressing Log In, your credentials will be cached, so that your account name and password are automatically entered in the form when you next need to log in.
With your credentials entered, press Log In.
If your credentials cannot be authenticated or your account is not authorised for access to the AP, then IMS will reload the login screen so you can try again with updated credentials.
Once authenticated and authorised, your web browser will then be redirected back to the AP URL which triggered the authorisation and authentication process. At this point you will have an authorised account session cookie in your web browser which means you will no longer be prompted for account credentials until either you have explicitly logged off or closed your web browser.
If the main URL above was used to open the International AP, you will then see the Dashboard - My Tasks view, and a blue notification box will show in the page header stating "All tasks loaded" (the header notification will automatically close after a brief interval, or you can press the X button in its upper right corner to close it manually).
If this is the first time you have used the AP (or all your existing tasks have been either promoted or deleted) then you will see an empty Dashboard listing view. This is where your tasks will be listed once created.
At this point you're in the International AP and ready to author content in your own tasks or review content created in other tasks by other authors.
Enter a target template name in the Select Transformation Target field.
Type-ahead search results will show name matches after three characters are entered.
Pick a template from the available list.
The Transform button in the bottom right corner of the dialogue will become active (its background colour changes from grey to blue).
Choose a reason from those presented in the Select Description Inactivation Reason options:
Non-conformance to editorial policy (default selected)
Outdated component
Erroneous component
Press Transform to start the transformation, or Cancel to close the dialogue with no changes saved.
The Transforming Concepts notification will occupy the pop-up window.
Wait for the transformation to complete.
On completion, the pop-up dialogue will close automatically, and view context will change to the Batch Processing tab, showing the selected transformed concept(s), in the same manner as for batch creation from a template.
Use the Edit Full Concept button on the batch entry row to present a "before/after" side-by-side view of the concept transformation.
At this point the transformation is only a preview - no changes have been saved.
If changes are not what was expected/required, then the previewed concept can be removed from the batch listing using the button at the start of its row entry in the batch list.
After previewing (and if necessary removing unwanted concept transformations from the batch), press Save All in the upper right corner of the batch view.
The Saving Batch pop-up notification will be presented - please wait while the transformation batch is saved, and do not navigate away or refresh the page (as it instructs).
Alternatively, should the entire transformation batch need to be abandoned, press the Discard All button in the batch view.
This will cancel the batch transformation and no changes will be made to the concepts.
After the transformation batch has been saved, press the blue Return to Task button to close the Saving Batch pop-up notification.
At this point the template transformations are complete, and the selected concepts are changed in the task.
The view context remains on the Batch Processing tab - from here proceed as needed to other AP features (for instance to task review for approval of the concept transformations - the transformed concepts will appear in the feedback tab To Review list).






Batch upload tasks are identified as such during the upload and task creation process.
When identified as a batch task, the Batch label appears in the upper-right of the Task View - Task Details panel.
The batch task identification activates the task-level Service Acceptance Criteria (SAC) item Validation Report Clean which is defined within the parent project SAC configuration, as a mandatory manual acceptance item.
Manual SAC are presented initially as open checkboxes, each of which can be interactively checked (green-ticked) when the user's role-based access permissions match those configured for that SAC control.
Once task promotion is enabled, follow the non-complex task steps (included below) to complete promotion of the task. Although the screenshots show simple tasks without theBatch label or task-level SAC, the steps to promote once it is enabled are the same for all tasks.
Each Managed Service has its own ??-authoring sub-domain within the ihtsdotools.org domain.
Go to the Managed Service AP in your web browser using the appropriate URL from the References list (sorted by country code in the sub-domain prefix).
The Managed Service AP uses the SNOMED International Identity Management Service (IMS) to authenticate and authorise registered account access.
If you're already registered with an existing SNOMED International Jira/Confluence account which has been granted AP access then you can use those credentials.
MS Australia MS Austria MS Belgium MS Switzerland MS Germany MS Denmark MS Estonia MS France MS Ireland MS Korea MS Netherlands MS Norway MS New Zealand MS Sweden MS United States
If you are not logged in to the AP, your web browser will be redirected to IMS for account authentication and access authorisation. You will see the IMS login screen in your web browser. Enter your account name and password.
If you check the Automatic log in box before pressing Log In, your credentials will be cached, so that your account name and password are automatically entered in the form when you next need to log in.
With your credentials entered, press Log In.
If your credentials cannot be authenticated or your account is not authorised for access to the AP, then IMS will reload the login screen so you can try again with updated credentials.
The MRCM Maintenance Tool supports browsing, creation, testing, review and publication of MRCM rules used in the SNOMED CT Authoring Platform and included in SNOMED CT releases for conformance checking.
Key uses include:
Browsing the MRCM rules The current release MRCM rule set can be browsed by anyone with a SNOMED International Confluence account. This feature supports and enhances the SNOMED CT Editorial Guide via links to interactive navigation of published rules.
Maintain MRCM rules (Version 1.1.0+) The SNOMED International Content Team will use the tool to review, create, modify, inactivate and promote MRCM rule changes.
Version and Publish MRCM rules (version 1.1.0+) The SNOMED International Content Team will version and publish MRCM rules in files that conform to the MRCM reference set specifications.
How do I... ?
Finding concepts with concrete domain values
Existing concepts containing attributes with concrete domain values can be found by searching with an ECL query containing a concrete domain value refinement:
For instance, this ECL query returns all concepts that have an attribute with the concrete value 12.5:
* : * = #12.5
In the Task - Search - ECL Search context panel tab, enter an ECL expression which includes a concrete value reference into the Search Query box.
Press the blue Search action button to the right of theSearch Query box.
The Search Results Panel shows a Searching... notification until the results are collated.
SNOMED CT is based on relationships between concepts, structured and constrained by the Machine Readable Content Model (MRCM), and represented and distributed using the RF2 release file format. The OWL-based (DL) supports the use of classification tools to infer relationships that are not directly stated in concepts, and hence provide additional meaning and context, however there are challenges when concept attributes need to express fixed values.
In the case of numerics - for example, the weight of a particular medicinal substance used in a drug product - it is desirable to be able to represent that amount, and then be able to ask questions like "List all drugs that contain >= 100mg of Paracetamol".
A work-around for this particular attribute was put in place in 2017, namely to create a concept to represent every number needed in the International Drug Model. This solution results in fully correct classification, and in particular has facilitated progression of the Drug Model implementation, however, it also has several drawbacks, particularly when needing to make comparisons and check for equivalencies.
The drawbacks of using concepts as numbers can be resolved by defining concrete values within SNOMED CT in a way that still fully supports classification to reveal inferred relationships, whilst enabling numeric operator comparisons and (subject to appropriate modelling) equivalences between different units to be detected.




By-passing review may also be acceptable under particular circumstances, for instance if the author is also the project manager / project lead.
This scenario can be prevented by setting the task as Complex and also having Review Completed set as a mandatory task-level SAC requirement within its parent project configuration, since task promotion in this case will not be enabled without a completed review.














A "Promoting task..." notification is presented in the page header whilst branch content changes are merged to the project level.
During promotion, the task content branch is locked to prevent any further changes, and a warning notification is presented below the Edit Task Details action button in the Task Details panel.
Whilst this is present, changes cannot be made to the content saved in the task branch, and action buttons other than Edit Task Details and Submit for Review become inactive.
Once task promotion is completed, a "Task successfully promoted for <task-identifier>" notification is presented in the page header.
Following promotion no further changes are allowed on the task content branch, all action buttons in the Task Details panel become inactive, and a warning notification is presented below the now inactive Edit Task Details action button.
Until all mandatory task-level SAC> are met, task promotion will be blocked and Promote This Task to the Project in the Task View - Task Details panel actions button list will not be enabled.
Validation Report Clean must be satisfied to allow batch task promotion
For batch tasks this means as a minimum Validation Report Clean must be interactively checked (green-ticked) before the task can be promoted.
Role-based access controls apply to manual task-level SAC
If the user's authenticated account session roles do not include edit permissions for the task (such as when viewing another author's task), the current manual SAC status will be shown, but cannot be set.
Press the Validation Report Clean manual SAC checkbox to toggle its status. It will show a green ticked box when checked, indicating its condition is met.
When all mandatory task-level SAC conditions are met for the batch task, promotion is enabled, and both Promote This Task to the Project and Begin Promotion Automation in the Task View - Task Details action buttons list become active.
Press Promote This Task to the Project in the Task View - Task Details panel actions button list.
A "Preparing for task promotion" notification is presented in the page header, and the Promote This Task to the Project button is disabled.
Task promotion has implicit checks for the following conditions:
No content changes made in the task.
Classification has been run in the task.
Classification was started but either failed to complete or has not completed.
Classification is current.
Classification has no results to accept.
Classification results have been accepted.
Review has been completed.
If no content has been changed on the task when promotion is initiated, a Promote Task pop-up notification states that there are no changes to promote.
Press Return to Task (or press the X in the upper right corner) to close the pop-up.
If content changes have been made but any of the other conditions are not yet satisfied when promotion is initiated, a Promote Task pop-up notification shows their statuses, with action options to cancel the promotion, or to continue if task changes are considered sufficiently safe to update the project level content without satisfying these conditions.
Press Return to Task (or press the X in the upper right corner) to close the pop-up and cancel the promotion without changing project content or the task status.
Press Promote Anyway to continue promotion.
Additional SAC already defined for tasks within the project
If any other Task-level SAC are defined for the project, these are also presented as described for Complex tasks.


* : * > #0The Search Results Panel lists the concepts matching the ECL query.
Follow up actions can include:



The Authoring Platform (AP) supports the following concrete value data types:
Integer
Decimal
String
The MRCM can apply the following types of constraints to concrete values assigned to attributes:
List (predefined fixed values)
Range (any numeric value between predefined limits; applicable to Integer and Decimal data types)
Attributes previously using concepts as numbers have the same FSN term when represented using concrete domains, however, the target value box has a green background, and the concrete domain values don't have a semantic tag since they are no longer concepts.
Drag and drop is supported for concrete values, so the "drag handle" arrows icon is still available, however concepts dragged from other fields, search results or taxonomy entries cannot be dropped as the target for a concrete domain attribute value, and likewise a concrete value cannot be dragged and dropped onto a concept target slot. Dropping a concrete domain value onto other concrete domain attributes will also be disabled if the drop value doesn't satisfy any MRCM constraints applicable to the target attribute.
A concrete value is represented by a solid green rectangle with diagonal lines in the corners, and the value centred within the box.
Numeric values are represented in Unicode text expressions preceded by a # (hash) symbol. For example:
#0.09
#0.5
#99.99
#1
#20
#500
Strings are represented in Unicode text enclosed by double quotes. A backslash is used as an escape character for quotes within the string, and hence any backslashes within the string also need to be escaped by an additional backslash.
"Product Name"
"Product Name \"containing\" quotes"
"Product Name \"containing\" quotes and a backslash (\\) character"
Since concrete domains are simply a form of attribute target value, as well as the above examples from the Task - Concept - Edit Panel they can appear in any feature of the Authoring Platform that presents attributes and their values, for instance:
The search results are filtered to only show projects matching the search query which are also in the selected category.
If more than one category is available, select another to filter the same query on a different category.
The results then only show those matching the query which are also in the new selected category.
In the Dashboard - All Projects view, when an author has access roles granted in projects which span more than a single category, a drop-down selector will appear to the right of the Search All Projects query slot in the view header.
The default selection is All (to search all projects).
Entering a query will trigger a type-ahead search of all projects after each character is entered.
Keep typing to narrow down the results set as the query becomes more defined.
Project search queries and matches
The All Projects search query will return any project that matches the query string in any of the following project details, not just the project name:
key (project key)
Press the caret-down icon button to the right-hand side of the category selector to show a drop-down list of project categories.
Select a category.
OR (from any Dashboard view)
Press My Tasks in the Dashboard view left sidebar menu.
The Dashboard My Tasks view is presented.
Not the International AP? If you have access permissions to more than one Authoring Platform, it's possible to inadvertently log into one of the others (perhaps via a bookmarked address) when the International AP was your intention, and they can appear almost identical in style and layout apart from the task names of any previously created tasks. Please verify the domain name in your browser's address bar if you're not sure, and if it's not what you intended, simply logout and start over with the International AP URL ( https://authoring.ihtsdotools.org/ ).




Once authenticated and authorised, your web browser will then be redirected back to the Authoring Platform URL which triggered the authorisation and authentication process.
At this point you will have an authorised account session cookie in your web browser which means you will no longer be prompted for account credentials until either you have explicitly logged off or closed your web browser.
If one of the main URLs above was used to open the Authoring Platform, you will then see the appropriate Dashboard - My Tasks view, and a blue notification box will show in the page header stating "All tasks loaded" (the header notification will automatically close after a brief interval, or you can press the X button in its upper right corner to close it manually).
The example screens in this page are for a Managed Service Ireland test account login, but others follow an identical pattern.
If this is the first time you have used the AP (or all your existing tasks have been either promoted or deleted) then you will see an empty Dashboard listing view. This is where your tasks will be listed once created.
At this point you're in the AP and ready to author content in your own tasks or review content created in other tasks by other authors.

Press the Search tab in the Task View - Context Panel tabs list.
The Task View - Context Panel switches to the Text Search form, with a query entry box prompting for at least three characters to be entered.
Below the text query box are two buttons:
Status Type shows the concept status type to be included in the search results (default Active Only)
Switch to ECL for changing the search type from text/numeric query to ECL
Press Run New Query in the right-hand top corner of the report description panel. This opens the Report Details form in a pop-up dialogue box.
Each report type has a relevant set of query parameters which may be specified.
Example Report Details form: Term Contains X
This query takes the following values:
Subhierarchy - a constraining sub-hierarchy of SNOMED CT to limit the query scope.
Starts With
Selected search results can be downloaded for further local/offline processing or importing into other tools.
Press the Download Selected Results button to the right of the results footer (it will be activated when results are found).
This will trigger your web browser download file feature, and prompt to save the search results as a .tsv (tab separated values) text file to your local web browser environment.
Once saved to disk, the results can be viewed in any text editor.
The first row has header labels for each item in the results rows below it.
Each row contains the following:
id (concept SCTID)
fsn (concept Fully Specified Name)
EITHER In the Review Tasks view, press the name link on the task you want to open. This opens the Task View to the context of the Feedback activity tab.
If task status is Ready for Review and the review status is Available (not yet claimed) this action will claim it for review and assign you to it as a Reviewer. The task will change state to In Review and its review state will become Claimed.
If task status is In Review and review is Claimed this will re-open the task for review and show any changes made to concepts in the task.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
In the current version this is achieved via service requests to the technical team.
You can use the form (or raise an INFRA devops support ticket directly in JIRA), as done for Authoring Platform (AP) issues and improvement requests, and noting the Reporting Platform (RP) in the form details.
Your request will be processed and prioritized along with other AP and RP feature/improvement requests for inclusion in a future release.




Promoting tasks with warnings
Pressing Promote Anyway is tacit acceptance of any warning statuses, with implied responsibility for by-passing these safeguards and the consequent unclassified and/or unreviewed content changes that will be promoted from the task to the project level.
Promoting unclassified content changes is a quality assurance risk that can be avoided relatively easily, since it typically takes less than ten minutes to run classification (if only to confirm no results).
However there are occasions when it is clear that inferred classification results won't change, such as a description-only content change, in which case this option may be acceptable.
By-passing review may also be acceptable under particular circumstances, for instance if the author is also the project manager / project lead.
This scenario can be prevented by setting the task as Complex and also having Review Completed set as a mandatory task-level SAC requirement within its parent project configuration, since task promotion in this case will not be enabled without a completed review.












Not your Managed Service AP? If you have access permissions to more than one Authoring Platform, it's possible to inadvertently log into one of the others (perhaps via a bookmarked address) when a Managed Service AP was your intention, and they can appear almost identical in style and layout apart from the task names of any previously created tasks.
Please verify the domain name in your browser's address bar if you're not sure, and if it's not what you intended, simply logout and start over with the appropriate AP URL from the References list in the first step above.



project lead (account name)
project lead (display name)









Results listings will appear below these buttons (or the panel will state "No results" for no matches, as seen when first loaded).
An End of Results footer completes the Text Search panel.
This presents further actions once results are obtained.
Enter at least three characters in the query box to trigger searching.
The application waits for a slight pause in the typing before triggering the search, so multiple words and phrases can be entered if desired.
The results panel shows "Searching..." until all results become available.
Some searches with small results sets may be almost instantaneous - larger results sets may take a few seconds to load.
Matches to the search query are then listed, along with the total number of concepts found.
Each result row has the following:
Definition Status icon (primitive or fully defined) which also acts as an Information button
Fully Specified Name (FSN) of the concept
Taxonomy button which opens the concept in the Taxonomy panel (Active concepts only)
Add To Saved List button
Clone This Concept button
Select this result checkbox
There is also a Select All checkbox to the upper right of the listing above the row checkboxes.
This selects the entire results set, not just those visible in the results listing (but currently constrained to a maximum of 1000 entries to prevent excessive bulk downloading).
Press Status Type once to switch to inactive concept matches only.
Note the Taxonomy button is replaced by an Inactive Concept status icon in the results listing (the Taxonomy view does not show inactive concepts)
Press Status Type again to show results containing both active and inactive concept matches.
Press Status Type once more to return to active concept matches only.
Pressing Status Type repeatedly will cycle the results sets through the three options:
Active Only (default on entering Search)
Inactive Only
Active and Inactive
Numeric values for text search
Numeric values can be entered in the text query box.
If the entered numeric value is an exact match for a SNOMED CT concept SCTID, then that concept will be presented as the only search result.


Words (mandatory field) - words to find within concept terms
Attribute Type - a constraining attribute type to limit the query scope.
Note the Words field which is labelled as a mandatory field. If this is not populated, the report run will fail when the details are submitted, with Failed showing in the Status column of the reports list entry.
Later versions of the Reporting Platform will introduce deeper form validation to prevent submission with invalid report details (form validation varies according to the complexity and dependencies of the different report details).
Enter your desired query details.
Subhierarchy and Attribute Type are examples of type-ahead select fields - start typing a word in the field box and the form will present a drop-down list of matching options (it may take a few seconds to query the server and present the selection list).
Press a list option to set the field value.
Complete your desired query details and then press the Run Query button in the lower right-corner of the Report Details dialogue box. This will submit the report for running on the server.
If you wish to cancel, press the x in the upper right corner of the dialogue box to close it without running the query.
On submitting the Report Details, the report Status changes to Scheduled. At this point the report request is queued on the server.
When the queue processing reaches your scheduled report, the report Status changes to Running. At this point the report query is run against the mainline content on the Authoring Platform. The report run time depends on the complexity of the query and its related hierarchy size, available server resources and queue length.
report running time
The current query run time limit is 2 minutes on the server - sufficient for most reporting needs whilst preventing performance issues associated with "runaway" queries. Time to update the report list Status may be longer if there is significant concurrent server processing, and is also be influenced by network communications latency between the server and the requestor's web browser.
If the run time limit is exceeded, the report run will stop and be marked as Failed in the report list. This may happen with queries that would return excessively large result sets , for instance a query with unconstrained scope that returns everything below a high-level concept.
After successful completion of the report, its Status is updated to Complete, and the Google Sheet report is then available in Google Drive, linked from the report entry Status label/icon.

effectiveTime (SNOMED CT release in which it was published)
active (true if active, false if inactive)
moduleId (module SCTID)
definitionStatus (primitive or fully-defined)
Uncheck Select All and press individual row select checkboxes to make ad-hoc selections of search matches.
Press Load Next 100 in the results footer for large results set to extend the listing with the next 100 results.
Each time this is done the listing is expanded to include all the previous results, and a vertical scroll bar will appear to the right of the results panel to allow the list to be scrolled.
Ad-hoc selections are preserved when the next 100 results are loaded, so selections can be added from throughout the entire results set if needed (although a better strategy might be to refine the search query to get a smaller results set).
Once all desired ad-hoc selections are made, press Download Selected Results to save the results as a .tsv file in your local web browser environment.
Open the downloaded .tsv file in any text editor to see that it contains only the selected result entries, regardless of the total number of results.



On completion of the search, the panel below the search query is populated with the tasks with names (titles) either partially or fully matching the entered text query (or a single exact match to a task ID).
Each matching task result row includes a blue Open in new Tab icon button, and the task name which is an active link.
Additional information for each task is presented in the same format and styling as the My Tasks view listing.
EITHER
Press the Open in new Tab icon button to open the task in a new web browser tab (or window, if set by your personal web browser preferences). This allows the task to be viewed whilst retaining the Task Search dialogue results for further use (to review other task matches, or to modify the query for new search results).
OR Follow the task name link to open the task in the same web browser tab. This closes the Task Search dialogue and takes you into the task Edit panel view as if the task had been opened from the My Tasks view listing.
The task Edit panel view is presented (either in a new tab/window, or replacing the search dialogue in the current tab according to which option is used).</p
Press Search Tasks in any Dashboard view left sidebar menu.
The Search Tasks pop-up dialogue is presented, containing a single text query field and a Search action button.
Enter text to match the labels of your tasks, then press Search. You can also search for exact matches to a task ID - but see the note below.
A blue Searching... prompt box is presented below the search query whilst the server finds matches to the entered text query.
Task title
As well as searching for task names (either partially or fully entered in the search query), you can also enter a specific task ID if known. If a task is matched to an ID then only that task is presented in the results panel. Note searching via ID cannot find partial matches - a result will only be found if the entered ID is an exact match to an existing task ID.
Hovering over one of the newly presented entries presents a tooltip which expands the full name of the context-specific language reference set and the acceptability setting.
When working in a task within a Managed Service extension, context-specific language reference set acceptability entries can be enabled in Concept Editor within the Edit Panel, by selecting from a list of those available in the author's Settings and Preferences.
From the Task View , press the cogwheel icon in the upper right of the page header, to open the Settings and Preferences pop-up dialogue.
When context-specific language reference sets are available, they are listed above the Page Layout section.
Each entry has a checkbox to enable display of those entries in the Concept Editor.
Check the box for the desired entry, then press Save in the Setting and Preferences dialogue.
The Settings and Preferences dialogue closes, and a header notification for "Application preferences updated" is presented.
With the settings saved, and an appropriate concept loaded into the Edit Panel, the language acceptability entries for each term are updated to include those for the selected context-specific language reference set (abbreviated in the same style as the other language acceptability entries).
Open the Classification Results for a task and Preview a changed concept which has concrete domain attributes.
The Preview Panel presents concrete values using the "green concrete value box" style.
Vertically scroll the Preview Panel if needed to see all attributes for a complex concept definition.
The Task View Review and Feedback layout is presented, showing concepts to review, concepts approved, and inferred concept changes within the task. This layout maintains the Activities panel (Left Sidebar), as well as the Options panel menu for navigation back to other task contexts.
OR In the Review Tasks view, press the feedback status icon (if present), on the task you want to open. This opens the Task View to the context of the Feedback activity tab. This option is only available once at least one review comment has been added by either a reviewer or author.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
The Task Review and Feedback layout is presented, showing concepts to review, concepts approved, and inferred concept changes within the task. This layout maintains the Activities panel (Left Sidebar), as well as the Options panel menu for navigation back to other task contexts.
Claimed for review tasks are only visible in the Review Tasks view to the people named in the Reviewers list. It's possible to add/remove names from the Reviewers list whilst a review is in progress, to support nominating other people deputizing as reviewers, or switching to a replacement reviewer. This means it's also possible that the original claimant will no longer see the task in the Review Tasks list if they have been subsequently removed from the Reviewers list.
An Author can add people to the Reviewers list after submitting for review, which will have the same effect for each Reviewer as if they had claimed the task for review from the Available state. This allows an author to nominate a particular reviewer (or selected set of reviewers) when submitting for review.


From the Dashboard - My Tasks view:
EITHER
Press New Task in the left-hand menu bar.
OR
Press the blue circular + button in the upper right corner of the Dashboard - My Tasks content panel.
The Create New Task pop-up form is presented, centred on the page and overlaying the Dashboard - My Tasks view which is dimmed but still visible "below" the form.
This form has three content entry fields, and three calls to action at the bottom of the form:
Task title field (required).
Select project
Enter a single line Task title for identification of this task in the Authoring Platform.
Press Select project to see an overlaid list of all available projects on the Authoring Platform. Pick one from the list by moving the cursor to its title and pressing it, or using the keyboard up-arrow / down-arrow buttons to scroll the list and then press Enter on the desired selection.
Enter some further descriptive text in Task Details and use the text formatting options menu to enhance readability if desired (select some text within the field, then press the desired option button in the menu). This field is optional and can be left blank but some additional background information on the task can often be useful, particularly if many tasks end up with similar titles.
Determine which report category is applicable to your query.
If there are many categories, and yours is not visible in the main content area, press a category heading in the left-hand sidebar Categories menu to only show that category’s reports.
Pressing the heading again restores the full Categories view.
Each press toggles between the only the selected category and showing all categories.
Service Acceptance Criteria (SAC) are used to assure that authored SNOMED CT content meets specific quality measures before the content can be promoted. The purpose of this is to ensure a specific level of quality is met at each promotion level. This in turn assures the quality of the content that is eventually promoted to the code system branch, with the benefit of minimising the quality checks required at that level (in general, the later the stage of the content release process, the greater the amount of work needed to correct any issues, so catching issues earlier in the process has many benefits).
SAC may be either automated or manual.
Automated SAC are checks which the system can sign off automatically without user intervention.
Manual SAC are checks that require sign-off via a particular user interaction, with that interaction governed by role-based access controls.
SAC may also be mandatory or optional.
RBAC is an access-control mechanism defined by mapping user-assignable roles to related privileges and features, governed by three core aspects: role assignment, role authorization, and permission authorization.
The Authoring Platform uses RBAC to authorize an authenticated user account with permissions to perform particular actions within the platform, defined by role-group mapping and membership.
The current roles defined on the AP can be considered in three groups:
















Creating new concept entries
These entries can be used in the same way as the other acceptability settings which are always present in the Edit Panel.
If a new concept is created, or a new description is added to an existing concept, and a value is set for one of the context-specific settings, a new entry will be created in the appropriate context-specific language reference set within the task branch, in exactly the same way as those for the other language reference set acceptability settings.
The default entry for these in the Concept Editor for new concepts is Not Acceptable.
Editing/saving an existing setting will also update the corresponding existing context-specific language reference set entry.








Task Details optional multi-line rich text field, with a sub-menu for formatting selected contents as bold font, italic font, button list, and numbered sequential list.
Create Task button.
Create and Open Task button.
Cancel button.
The pop-up form also has a small X button in its top right corner. This has the same effect as the Cancel button.
Cancelling the task creation
At any stage up to this point:
EITHER
Press Cancel
Can't cancel after requesting creation
Once one of the following steps are taken, the specified task creation cannot be cancelled, however a task can be subsequently deleted if created in error, or it is no longer needed.
When the form fields are ready:
EITHER
Press Create Task
OR
Press Create and Open Task
A full-width "Creating task..." notification banner appears above the call to action buttons (which are greyed out) whilst the task is being set-up - this typically takes a few seconds.
On completion, a "Task initialization complete" notification banner is presented in the page header.
If Create Task was used, then the pop-up form will close and the original underlying Dashboard My Tasks view will be restored. The new task title will appear in the task list.If Create and Open Task was used, then the pop-up form will close and the task will be opened as if its listing entry link had been followed from the Dashboard - My Tasks view, allowing authoring to start immediately within the task.
Task title
Task titles can be up to 255 characters maximum, but it should be as concise as possible whilst still conveying sufficient information to identify it alongside other text entries in task lists.



Optional SAC do not block promotion, but best practice would be to inform the Project Manager and/or Project Lead of reasons for promoting without the check being satisfied (an example may be a task-level spelling check, which might depend on the nature of the content being changed, and the availability of related spell-checking resources).
SAC are defined at the global level by users with the ADMIN role, as are their mapping to required RBAC roles. This is currently constrained as a technical support feature.
Globally defined SAC are then available as an options list to those with relevant permissions (set by RBAC role group definitions on the branch or its parents), to decide which to include in task-level or project-level gateway controls.
SAC are presented as checklist items in either the task details (for task level SAC) or project view (for project level SAC). The ability to modify the manual items to check them off via the AP user interface is a permission granted by the role assigned to each item in the SAC list. Task level manual SAC are usually available to all authors. Some project level manual SAC may also be available to all authors, but many will require additional permissions such as those for Project Managers or Project Leads to update (specific role mappings are set in the SAC global configuration definitions).
Some aspects of acceptance gateway controls are implicit in the AP branch promotion process - for instance, diverged content branches cannot be promoted: each branch must be rebased from its immediate parent branch with all merge conflicts resolved before the branch can be promoted.
Service Acceptance Criteria are components in a technical architecture solution which includes the Authoring Acceptance Gateway (AAG) and various data stores associated with acceptance and sign-off of content changes for promotion via AP tasks and projects, and also for the generation and packaging of SNOMED CT releases.
The following schematic illustrates the subset of this architecture directly related to AP features and their inter-relationships and dependencies (components relating to release preparation and packaging are omitted here for clarity, but are essential aspects of the overall technical architecture):
Early Visibility Notice if Required Manual spell check Review complete RVF Report Clean
Project Documentation (TIG Editorial Guide) Complete Project Lead (Peer reviewer): All Release Validation Reports Checked Project Lead (Peer reviewer): Exceptions Checked and Signed off Project Lead (Peer reviewer): Final Sign-Off Project Manager: Signed Off Project as Ready to Promote Relevant MRCM Changes Implemented Report: Case Significance Clean Report: Duplicate Terms Clean Report: KPI Patterns Clean Report: New Descriptions Clean Report: Release Issues Clean Report: Template Compliance Clean Report: Validate Inactivations with Associations Clean Validation Report Clean
Editing the query will immediately trigger a search and present an updated results set (due to the relaxed trigger requirement of only a single character when Filter by PT in ZH is selected).
In the Task View - Context Panel tab, when alternative language reference sets are available. the search panel shows additional options for:
Language Refsets reference set selection (combination checklist)
Filter by term (single choice selector)
The language reference set selection controls which results to include, and the term choice decides which language is used to search and present the results.
To search using Chinese queries, first select Filter by PT in ZH.
Enter a character in the query box to trigger searching.
The results panel shows "Searching..." until all results become available.
Some searches with small results sets may be almost instantaneous - larger results sets may take a few seconds to load.
Since a character-based writing system such as Chinese can associate each logogram with an entire sound or phrase, the three-character minimum used to optimize type-ahead search phrases for other languages and dialects does not apply when Filter by PT in ZH is selected.
This will however be re-applied if the Filter by selection is changed to a non-Chinese option (for instance FSN in US).
Term matches to the search query are then listed, along with the total number of concepts found.
Use the and features as needed.
AUTHOR PROJECT_MANAGER PROJECT_LEAD
RELEASE_USER RELEASE_MANAGER RELEASE_LEAD RELEASE_ADMIN
ADMIN
These roles are assigned to particular access control groups, which are mapped to global or project level content branch permissions on the Terminology Server. The technical support and platform administration, and SNOMED CT release control roles are outside the scope of this AP user guide, but mentioned here for completeness. When an account login is authenticated, it is then assigned AP feature access and permissions according to the roles defined for the groups of which the account is a member.
Authoring and content promotion control
SNOMED CT release control
Technical support and platform administration
AUTHOR is the core permission which enables an authenticated account to work on SNOMED CT content through authoring projects and their related tasks.
PROJECT_MANAGER adds permissions to define Service Acceptance Criteria (SAC) which are used by Authoring Access Gateway (AAG) controls to grant (or deny) permissions for promotion of content at task and project level.
PROJECT_LEAD adds permissions to approve SAC items which allow project content promotion to the content mainline.
These roles also determine the visibility and presentation of access-controlled features in the AP user interface.
Find the report to remove, as described in Find an existing report.
Move your cursor over the report row entry (the row background will change shade when your cursor is in its context). A red “minus” icon will also appear to the right of the label link icon.
Press the red minus sign to remove the report from the list. This presents the Delete Report pop-up dialogue.
Press the Delete Report button in the lower right-corner of the dialogue box to remove the report entry from the report listing. Press the x in the upper right corner of the dialogue box to close the box without changing the report listing.
Use type-ahead search to enter and select (for instance) Disorder of endocrine system (disorder)as the target value for the new Associated with relationship.
Save the new GCI via the concept header Save Concept button.
Modify the original GCI, for example using type-ahead search to find and select Alteration in nutrition (finding) as a new target for the Due to attribute.
Press Save in the concept header to save the GCI attribute changes.
Confirm the changes via the Stated view of the concept diagram.
With a GCI present in the concept edit panel (eg via the steps above), use the Add GCI Axiom button in the concept header to add a new GCI to the edit panel. Drag and drop the concept parent Diabetes mellitus (disorder) as the target for the new GCI Is a relationship.
Using the Add General Concept Inclusion button in the concept header, add another GCI to the concept edit panel.
Press the Add New Relationship "plus" button within the GCI panel to add a new relationship. Use type-ahead search to enter and select Associated with (attribute) as the relationship type.
In the Taxonomy panel, press the Language drop-down selector control in the top right corner of the panel.
A list of language display options are presented for the Fully Specified Name (FSN) and Preferred Term (PT) for each available language-dialect.
As an example, these are the options for ms-belgium:
FSN in US
PT in US
PT in FR
PT in NL
Press an option to select that language-dialect for the Taxonomy listing preferred terms.
The preferred terms in the Taxonomy listing are updated to show the selected language option.
Press the header label for your category to show the reports listed under that heading. The screenshot shows the available Semantic Tag Hierarchy reports after pressing its heading.
Pressing the header label again will collapse the reports listing.
Each press of the report heading toggles the expansion/collapsing of the reports listing.
With your category expanded, find the report in the list of those available.
If a particular report that you need cannot be seen, you can run a new query for that report.




Task title
There is no second chance if you press a task name link. When the task opens in the Edit panel, the task search results are gone, so the previous search would need to be repeated should you need to get back to them. If this is not desired, please use the Open in new Tab option!














Press Add to Saved List in a search result.
This extends the current Task View - Saved List to include the search result concept, but does not move away from the search results (in case other actions are needed on other results).
Once a concept has been added then Add to Saved List is no longer active for that search result (so it can only be added once).
Press Saved List in the Task View header tabs.
This opens the Task View - Saved List , showing the concept that was added.
Each item in the list has the following:
Primitive or Fully Defined button (status definition icon)
When searching, the search query will match against any content, including translated terms, and the default search results presents the matched concepts using the Preferred Term in the first available extension language or dialect.
The search results panel is initially empty, awaiting entry of a search query (type at least three characters to trigger type-ahead searching).
Extension authoring search has two additional filtering options (not available in International authoring), to focus the results based on:
Language Reference Set membership (multiple combination options).
To constrain the search to a specific language reference set, press the Language Refsets multi-option selector, and make a selection of any combination from those available.
The search results will only show matches to content found in the selected language reference sets.
The screenshot example shows the options available in the ms-belgium extension, which are:
US English
EITHER (from anywhere in the application)
Open the page header drop down menu and press Review Tasks in the overlaid menu options list.
OR (from any Dashboard view)
Press Review Tasks in the Dashboard view left sidebar menu.
The SNOMED CT Reporting Platform (RP) is a gateway to reports which can run a range of queries against content created or updated in the active authoring cycle for SNOMED CT.
Queries are structured into categories for ease of definition, navigation and retrieval, such as Ad-Hoc Queries, Release Validation and Quality Improvement.
The results of these queries can support pre-release validation of issues not supported by the Authoring Platform (for instance, MRCM rules such as attribute cardinality).
They can also be used to analyze the structural quality of SNOMED CT, to identify potential issues (for instance, attribute usage for a given sub-hierarchy) which can then be addressed via content change projects in the Authoring Platform.
For content authors, it enables iterative work to define complex QA rules that are eventually used for the Release Validation Framework (RVF) assertions (such as Case Significance).
As a content release planning and tracking tool it can show the number and types of changes made during a SNOMED CT release cycle, and from one release to the next.
This is a guide to using the SNOMED CT Authoring Platform (AP), based on the Snowstorm terminology server. The AP supports SNOMED CT content authoring using full OWL Axiom Description Logic modeling.
Through the AP you can:
Create new SNOMED CT content in the International Edition, including concepts requested from external sources such as the International CRS platform.
Create new SNOMED CT content in the US Edition, including concepts requested from external sources such as the US CRS platform.

X,br />This will close the form without creating a task (any contents in the fields will be lost), and the original underlying Dashboard - My Tasks view will be restored with no changes.
















Delete Report removes the list entry - not the report itself
This action removes the report entry from the Reporting Platform listing but does not remove the Google sheet report saved in Google Drive, which can still be viewed directly from Google Drive if needed.
Any report removed from the listing can be added back simply by running that report again (although the date-time and account name will be those of the re-run rather than any previously run report).









Preferred terms that are not yet translated
If no translated term is available in a selected extension language-dialect, the terms will fall back to the en-US PT (required for all concepts), so a mix of the selected language-dialect and en-US terms should be expected until full coverage of PT translations is available for a given extension.





Preferred Term
View in Taxonomy button
Add to Project Favorites button
Clone this concept button
Remove from Saved List button
Press Primitive or Fully-defined to see the Concept Information (as described in View concept details when browsing the taxonomy).
Press the Preferred Term to open the concept in the Edit Panel.
Press View in Taxonomy to open the Taxonomy view focused on that concept.
Press Add to Project Favorites to extend the Project Favorites List with that concept.
Project favourites are immediately available for all tasks within the same project.
If any concepts have been saved as a project favorite in any task within the project, then all tasks int hat project will show the Project Favorites list in their Task View - Saved List (the Task View web page may need to be refreshed to pick up any changes made by others whilst it remains open in the web browser, but it automatically picks up changes when first loaded).
Press Clone this concept to create a new unpublished concept with the same lexical model and logical model content as the search result.
This is equivalent to creating a new unpublished concept and entering all of its terms and relationships via search/lookup, so can be quite a time-saver.
Press Remove from saved list to do just that!
Removing from the Saved List
Pressing Remove from saved list is immediate - no second chance! If done accidentally, it can be restored to the Saved List by returning to Search and adding it back from there.
If the concept has been added to the Project Favorites list it will still appear there - the action only applies to its specific list entry.



These are available below the Active Only | Inactive Only | Active and Inactive publication status filter button and the Switch to ECL button in the search panel header bar (below the search query box).
Belgian Dutch language reference set
GB English
Enable the desired filtering by pressing the relevant checkboxes (toggle on/off).
Once a specific selection has been made, the choices made are shown in the button in place of the initial Language Refsets label.
The initial search filtering is equivalent to enabling all options.Be aware that some combinations of language reference set constraints and language or dialect filtering may give no results - for instance, searching for a Dutch word with only the French Language Reference Set selected - since the Dutch word is only present in the Belgian Dutch language reference set, it will only be found if that option is selected.
To constrain the search to a specific language or dialect, press the Filter by single option selector.
A list of language display options are presented for the Fully Specified Name (FSN) and Preferred Term (PT) for each available language/dialect.
As an example, these are the options for ms-belgium:
FSN in US
PT in FR
PT in NL
Press an option to select that language/dialect for the Search results preferred terms (PT in FR is the default option for ms-belgium).
Each extension will show variations matching the PT language and dialect options presented when editing a new concept.
These are defined in the extension codesystem metadata when the extension is first setup for authoring.
The preferred terms in the Search results are updated to show the selected language option.
If there is no translated term available in a selected extension language-dialect, the terms will fall back to the en-US PT (required for all concepts).
So a mix of the selected language/dialect and en-US terms should be expected if full coverage of PT translations is not available for a given extension and set of search matches.





It can reveal trends and particular faceted searches of SNOMED CT content created through the SNOMED CT Authoring Platform that are not easily obtainable via other tools and services.
It can help with quality assurance review of promoted content prior to publication in the next SNOMED CT release.
It can help to quickly modify and adapt rules which can enable more rapid SNOMED CT content updates via Authoring Platform authoring projects/tasks.
It helps focus on potential content issues that may or may not be a problem, so can help with impact assessment, prioritization and planning.
For quality checks that are not currently supported in the Authoring Platform by Drools Rules (concept save validation) or Release Validation Framework assertions (task and project validation against an entire release), for instance string handling.
Anytime you need to query the content within the current authoring cycle for SNOMED CT.
In particular, many of the reports are designed to help with content quality assurance reviews before creating the alpha-release version for each SNOMED CT release cycle.
RP queries run against the content which has been promoted to the mainline branch of the Authoring Platform (ie promoted project content), so some coordination with project content team leaders may be advisable if your report is influenced by or needs to include specific project content for analysis.
The Reporting Platform is linked from the SNOMED CT Authoring Platform (AP) header drop-down menu (available on all pages within the Authoring Platform).
The International AP can be bookmarked and opened with: https://authoring.ihtsdotools.org/
The RP can also be bookmarked and opened directly with: https://authoring.ihtsdotools.org/reporting/
These links will redirect you to the login page if you’re not already logged in within your current browser session. Once your login completes, your browser will be redirected on to the AP Dashboard and RP main page respectively. If already logged in, these pages will load without the login redirect.
Anyone who has a use for the results of queries run against content updates for the current authoring cycle through the SNOMED CT Authoring Platform, such as (but by no means limited to):
Content authors
Content project managers
Content team leaders
Consultant terminologists
Clinicians
SNOMED CT release teams
Technical specialists
Find the desired applicable attribute name in the Applicable Attributes panel listing.
Press the name to change the context of the Attribute Range panel to those matching the attribute, and also show the Attribute Details sub-panel at the base of the Applicable Attributes panel. The selected attribute name is highlighted.
The Attribute Details sub-panel shows values for:
Grouped
The Attribute Details sub-panel can be toggled closed/open when an attribute is selected.
When open, press on the right of the sub-panel title bar to close the Attribute Details sub-panel.
When closed, press in the sub-panel title bar to open it.
Find the desired domain name in the Domain panel of the MRCM Maintenance Tool.
Press the name to change the context of the Applicable Attributes panel to those matching the domain, and also expand the Domain Details sub-panel at the base of the Domain panel. The selected domain name is highlighted.
The Domain Details sub-panel contains:
Domain Constraint
Parent Domain (sub-domains only)
Proximal Primitive Constraint
Guide URL
Precoordination Domain Template
Postcoordination Domain Template
The Applicable Attributes list can be filtered by typing a text pattern into the Filter Attributes... box. As soon as text is entered, the attributes list will update to only show those matching the filter text.
If a sub-domain is selected, the Applicable Attributes results will show all those applicable to its parent domain, however only those applicable to the selected sub-domain will be active in the list.
Any attributes not applicable to the selected sub-domain will be inactive, and moving the cursor onto them will show a symbol, indicating they cannot be viewed for the selected sub-domain.
The opt-in checkbox enables the form to capture details about your current web browser environment. You can press the What is included in the data about my current environment? link to preview those details and help decide whether or not to include them if unsure. Including them can help the technical support teams when troubleshooting defect reports, particularly anything related to screen presentation/layout, but of course it's entirely optional.
Press Submit in the form footer to submit your entered feedback details. A Thank you for your feedback! message will appear for 5 seconds and then the pop-up form will automatically close, returning you to whatever AP context you were in when the Raise an Issue button was pressed.
For the International Authoring Platform this creates a Devops Support (INFRA) ticket, which the Technical Team will assess, prioritise and respond to with appropriate notifications and follow-up actions (your patience is appreciated!).
Alternatively, if you have decided not to raise an issue since opening the form, simply press Close in the form footer to immediately close the pop-up dialogue and return to your AP context.
Press Raise an Issue to report issues or submit change requests related to AP usability and features.
The Raise an Issue pop-up form is presented. If the form height is larger than your available web browser display height, a vertical scroll bar will appear to allow you to scroll down and see all the form content (the form header title and footer actions remain visible whilst scrolling). The following fields are available:
Summary (required, single line text, maximum of 255 characters)
Description (multi-line text with markup formatting support for structured text)
Attach file (browser's local file selector)
Priority (single choice option list selector)
Name (single line text, maximum of 255 characters)
Email (single line text, maximum of 255 characters)
Include data about your current environment, like the browser and page URL (opt-in checkbox)
The form footer has a Submit action button and a Close link.
Enter the desired details. The more information included the better, but also try to be as concise as possible and ideally keep to one identifiable issue per submission - this will simplify subsequent processing and hence make it quicker to assess, prioritise and investigate further if needed.
The minimum needed is a brief one-line Summary of the issue. Everything below that on the form is optional.
The Description field supports formatting options for structured text. Press the small question mark icon to open a Text Formatting Notation Help pop-up window with guidelines on including advanced formatting (wiki) markup.
You can use the Attach file (Choose Files) field to include a file attachment such as a screenshot.
An indication of the issue impact or urgency can be included using the Priority drop-down selector options. This will be taken into account when assessing the submitted issue but it will be treated as advisory and considered with additional contexts, including capacity and release scheduling.
Please elaborate any critical dependencies in the Description to help with follow-up prioritisation.
Including your Name and Email will help in identification, tracking and follow-up notifications/discussions.
On completion of the promotion process, a "Project successfully promoted for " notification is presented in the page header, and the Project-level SAC are reset (if so configured in their definition - see the info panel), ready for the next cycle of project content updates.
Project-level SAC are presented in the Project View as two lists within the Acceptance Criteria accordion-style expandable/collapsible content section, located below the Project Details and above the Classification Results section.
Automated Project-level SAC are listed to the left, with Manual Project-level SAC to the right.
Automated SAC have a yellow warning triangle icon if not yet met, and a green tick if their automated system checks confirm they are satisfied.
Manual SAC are presented initially as open checkboxes, each of which can be interactively signed-off (green-ticked) when the user's role-based access permissions match those configured for that SAC control.
For many projects it may be appropriate to only enable Manual SAC. In this case the Automated Criteria heading is still present, but that list is empty, and the project may then be promoted when all Manual SAC are signed-off.
Particular manual SAC require a specific role to be able to sign-off, such as PROJECT_LEAD, so more than one person may be needed to get all SAC satisfied, and those without a required role will see the current status of those SAC, but will not be able to change it.
When all mandatory project-level SAC are satisfied, the project is not diverged, and the project configuration enables promotion, the Promote button will be active for those with the PROJECT_LEAD role.
Press Promote to promote the project contents to the mainline branch.
A "Preparing for project promotion..." notification is presented in the page header.
Go to the International AP in your web browser.
The International AP uses the SNOMED International IMS to authenticate and authorise access via a registered account.
If you're already registered with an existing SNOMED International Jira/Confluence account which has been granted AP access then you can use those credentials.
If you are not logged in to the AP, your web browser will be redirected to IMS for account authentication and access authorisation. You will see the IMS login screen in your web browser.
Enter your account name and password.
If you check the Automatic log in box before pressing Log In, your credentials will be cached, so that your account name and password are automatically entered in the form when you next need to log in.
With your credentials entered, press Log In.
If your credentials cannot be authenticated or your account is not authorised for access to the AP, then IMS will reload the login screen so you can try again with updated credentials.
Once authenticated and authorised, your web browser will then be redirected back to the AP URL which triggered the authorisation and authentication process.
At this point you will have an authorised account session cookie in your web browser which means you will no longer be prompted for account credentials until either you have explicitly logged off or closed your web browser.
If the main URL above was used to open the International AP, you will then see the Dashboard - My Tasks view, and a blue notification box will show in the page header stating "All tasks loaded" (the header notification will automatically close after a brief interval, or you can press the X button in its upper right corner to close it manually).
If this is the first time you have used the AP (or all your existing tasks have been either promoted or deleted) then you will see an empty Dashboard listing view. This is where your tasks will be listed once created.
At this point you're in the International AP and ready to author content in your own tasks or review content created in other tasks by other authors.
With the new concept loaded in the Edit Panel, press the More details icon button to the left of the concept header.
The More Details pop-over dialogue shows the extension Module Id for the new concept.
The example shows a Belgian module concept.
Press any description row More details icon button (to the left of the description row) to see a similar pop-over for each description.
The example shows a Belgian module concept, in which the fr and nl languages can also be seen in the Lang. (language reference set) setting for each translated description, as well as its extension Module Id.
Note that en:US is the language reference set for the FSN and first PT.
Since the report itself is a Google Sheet, all the options and services associated with a shared Google Sheet are available for further processing and analysis as needed, such as copying to a personal sheet for further analysis/manipulation, download as a file in various formats for offline review and processing (including exporting to other tools and services).
Reports for queries that have been run and already available are listed with status Complete. This status links to the completed report which is stored as a Google Sheet in a Google Drive shared folder - press the label or the icon to open the Google Sheet report.
If you are not already signed in to your Google account in an existing browser session, you’ll be prompted for your Google credentials. Enter these to proceed and view the report sheet.
An example report is shown in the screenshot for
TermContainsXReport 71388002 |Procedure| 20181220_103142_prod_sulrich.
The sheet name contains the report title followed by the run date-time (in YYYYMMDD_HHMMSS format), a platform identifier (prod), and finally the account name of the originator (ie the account login under which the report query was run).
Create new SNOMED CT content in Local Extensions, including concepts requested from external sources such as the SNOMED International Managed Service Request Portal.
Add new terms and/or modeling to published SNOMED CT concepts.
Classify content changes.
Validate content changes.
Review and approve content for publication in the relevant next SNOMED CT release.
The SNOMED CT Authoring Platform is in use here: https://authoring.ihtsdotools.org/
© Copyright 2026 International Health Terminology Standards Development Organisation, all rights reserved.
This document is a publication of International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED International owns and maintains SNOMED CT®.
Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of SNOMED International. This document may be subject to updates. Always use the latest version of this document published by SNOMED International. This can be viewed online and downloaded by following the links on the front page or cover of this document.
SNOMED®, SNOMED CT® and IHTSDO® are registered trademarks of International Health Terminology Standards Development Organisation. SNOMED CT® licensing information is available at
The Dashboard Review Tasks view is presented.



Press Promote This Task to the Project in the Task View - Task Details panel actions button list.
A "Preparing for task promotion" notification is presented in the page header, and the Promote This Task to the Project button is disabled.
From the Dashboard - My Tasks view, press Upload a Batch in the left-hand menu bar.
Content translation terms are imported via .tsv (tab-separated values) text files, with three format types corresponding to the following actions:
Description Additions
Description Changes
The Upload a Batch pop-up form is presented, centred on the page and overlaying the Dashboard - My Tasks view which is dimmed but still visible "below" the form.
This form has the following fields and calls to action:
Task Title (single line text entry, freely editable)
Select Project (drop-down select list of projects available to the authenticated author)
EITHER Press MRCM in the Authoring Platform header menu.
OR Enter the MRCM Maintenance Tool address directly in your web browser (for example from a bookmark).
The MRCM Maintenance Tool opens in a new tab/window (depending on your web browser options), containing:
Branding and identity header
Context and actions bar
Domain panel
The domain names are active - pressing one will change the context of the Applicable Attributes panel to those matching the domain, and also expand the Domain Details sub-panel at the base of the Domain panel.
When in text search mode (default on opening Task View - Search tab), press Switch to ECL.
If previously switched to template search mode, press Switch to Text, then press Switch to ECL.
Enter an ECL expression into the search query box.
The Machine Readable Concept Model (MRCM) represents rules in the SNOMED CT concept model in a form that can be read by a computer and applied to test that concept definitions and expressions comply with the rules. The MRCM may be used for a variety of purposes, including the authoring and validation of SNOMED CT concepts, expressions, expression constraints and queries, Natural Language Processing and terminology binding to support semantic interoperability.
The MRCM may be useful in a number of use cases, including:
Development of precoordinated terminology content.
Authoring and validation of SNOMED CT expressions, constraints and queries.
Natural Language Processing.
Terminology binding to information models, for purposes such as data capture and semantic interoperability.
The MRCM contains a set of domains and a set of attributes, which may be applied to one or more domains. The cardinality and valid range of each attribute is specified, and indicates whether or not the attribute should be grouped. The domain, range, cardinality and grouped indicator for each attribute is also combined into a single 'attribute rule', which is represented using a .
For each domain, the set of valid attributes and their associated rules are compiled into two SNOMED CT 'domain templates' – for precoordinated concept authoring and postcoordinated expression authoring respectively. These domain templates may be further specialized to support customized authoring of specific subdomains.
The following diagram summarizes the logical structure of the MRCM:
The MRCM is distributed as the following types of reference set in the SNOMED CT RF2 release file format:
MRCM Domain Reference Set
MRCM Attribute Domain Reference Set
MRCM Attribute Range Reference Set
MRCM Module Scope Reference Set
The following diagram summarizes these reference sets and their properties:
The Authoring Platform Terminology Server (Snowstorm) maintains SNOMED CT content in a controlled hierarchical structure of project and task branches originating from the mainline (or simply MAIN) branch.
MAIN carries controlled changes to SNOMED CT content in the current authoring cycle, which is periodically used to generate a new SNOMED CT International Release. It contains a set of project child branches, which can promote content for inclusion in the next SNOMED CT International release.
Each project branch contains any number of task child branches, which can promote content to the project level for sharing and synchronizing across the other tasks. Project branches can be synchronized (rebased from MAIN) with content updates from other projects which have promoted their changes to MAIN.
Task branches can be synchronized (rebased from project) with content updates from other tasks which have promoted their changes to the parent project.
Up-to-date
Branch is synchronized with parent
Forward
Branch has at least one change whilst its parent branch is unchanged. This is the required state for merging a branch.
Behind
Parent branch has at least one change whilst the branch is unchanged. Branch can be safely rebased in this state, to bring in the parent changes.
Diverged
Both branch and its parent have at least one change since branch creation. Branch must be rebased before it can be safely promoted, to bring in the parent changes before promoting the branch.
Stale
Branch is no longer associated with its original parent (and should be deleted).
Working in a Managed Service or Training authoring extension has some significant differences from International authoring:
Extension mainline branch The promoted project content "mainline" is an extension base branch instead of MAIN (International mainline). This doesn't directly affect authoring interactions, but project leads and release quality assurance testers need to know what this means when releases are prepared.


















Attribute in Group Cardinality
Rule Strength
Content Type
The Attribute Range panel shows the following details for the selected attribute:
Range Constraint
Attribute Rule
Mandatory
Content Type
On selecting an applicable attribute, a search is performed to retrieve all concepts matching the range constraints. After a brief pause (search time depends on the complexity of the search and number of results obtained) the results are presented in a sub-panel at the base of the Attribute Range panel.







Close has no second chance!
Be wary there is no guard on the Close action - as soon at it is pressed, any entered information is lost. If you want to preserve anything for a later submission please use your local environment cut/paste tools to capture anything essential first!






SAC Definitions and Acceptance Roles
With more frequent delivery of SNOMED CT releases, project-level SAC are an essential aspect of the International Edition content quality control process. However, it is technically feasible for projects not to have project-level SAC defined, and some may have Manual SAC but no Automated SAC or vice versa.
Project-level (and task-level) SAC definitions can be set by those who have the PROJECT_MANAGER role, usually in close consultation with those in the PROJECT_LEAD and RELEASE_LEAD roles.Individual user accounts may also be granted more than one access control role (via membership of the appropriate access control groups).
SAC Definitions and Acceptance Roles
Usual configuration practice is to set Project-level SAC to automatically reset to the "unsatisfied" state when project content is promoted to the parent mainline branch. This is in anticipation of subsequent, often repeated, project content updates from its authoring tasks, within each mainline release version authoring cycle. Such resetting ensures that these checks are re-confirmed before promoting project content, and hence reduces the risk of unexpected content changes reaching the project mainline.
However, since this is a configuration option, there may be scenarios in which the "satisfied" status is maintained across project promotions once it has been set. Such authoring process decisions are the remit of those with the PROJECT_MANAGER and/or PROJECT_LEAD role(s) to identify and confirm for the relevant content releases.




Not the International AP? If you have access permissions to more than one Authoring Platform, it's possible to inadvertently log into one of the others (perhaps via a bookmarked address) when the International AP was your intention, and they can appear almost identical in style and layout apart from the task names of any previously created tasks.
Please verify the domain name in your browser's address bar if you're not sure, and if it's not what you intended, simply logout and start over with the International AP URL ( https://authoring.ihtsdotools.org/ ).


No SCTID information until new concept is saved
The examples above show a new extension module concept that has not yet been saved, so their SCTID values are empty in the More Details pop-over dialogues.
Once a new concept has been saved, the appropriate SCIDs will be shown for the concept and its descriptions, which can also be seen to contain the namespace identifier for the extension module (1000172 for the Belgian extension namespace).
Closing information pop-overs
Press the More details icon button to toggle its related pop-over open/closed.
Press anywhere in the Edit Panel outside a pop-over box to close all open pop-overs.

















Description Inactivations
See Import extension language/dialect batch file formats for some examples of these files, including sample download .tsv files.
Select Assignee (drop-down select list of all registered AP accounts)
Select Reviewer (drop-down select list of all registered AP accounts)
Number of Concepts Per Task (drop-down select list)
Select Import Type (drop-down select list; must match the upload file format)
Select Batch File (opens the browser's local file selector dialogue to specify a batch file for upload)
Create Tasks (inactive until a batch .tsv file is uploaded)
Cancel (closes the pop-up form without making any changes)
When all fields are defined, the Create Tasks button is enabled - press the button to upload the batch file start the import process.The imported changes are allocated to new tasks according to the number of change rows and the maximum number of concepts per task defined on the form, which has the following options: _5, 10, 15, 20, 15, 50, 100 (default), 200, 500.
So, for instance if the source file contains 41 rows, and the number of concepts per task is set to 15, then 3 new tasks will be created, with the last one containing 11 changes, and the others 15 each.
The default option of 100 is chosen so that most use cases only need one new task, but a smaller number may make it easier to review changes.
If multiple tasks are created they are identified by reference numbers which are automatically suffixed to the Task Title.
Following upload and processing of the batch file, successful complete of processing is indicated via a header notification for "All tasks loaded", newly created task(s) in the My Tasks listing, and a browser download .tsv file which contains the import result for each processed row from the uploaded batch source file.
The example below shows a success result file for 3 description additions to existing published International concepts, adding Maori language translations in the New Zealand (NZ) extension:
Following successful import, the changes made can be seen in the Authoring Platform by opening each related import task.
On first opening the task, the edit panel will be empty, since no manual editing has occurred.
Use the Switch to Feedback View context tab to see each modified concept in the To Review list.
Loading the modified concepts into the Review Panel highlights their changes, in exactly the same way as those made manually via regular editing.
The example shown here shows two NZ extension description changes made via batch import.
Another example showing two NZ extension description inactivations made via batch import.
Another example showing three Maori translated terms added to existing International published concepts, with the new descriptions added to the NZ extension module.
(Google translations of en-US terms into Maori are for illustration purposes only!)


Applicable Attributes panel
Attribute Range panel
Copyright notice, help and contact us footer
The header contains site branding and an MRCM version selector to its left (the default selection is the current authoring cycle content, ie the MRCM content for the next SNOMED CT release). To its right is the the authenticated account name, which when pressed expands the header downwards to reveal a Logout link (pressing the account name toggles the link visibility). Follow that link to log out and exit the application (this returns you to the IMS Log in to the International Authoring Platform screen).
Below the header, the context and actions bar runs across the three main content panels. Currently selected items appear to the left of this bar (initially empty when nothing is selected), and a RESET button is available to its right (this clears any selections and initialises the content panels).
The Domain panel shows a nested tree-view listing of SNOMED CT domains. Navigate the tree-view listing to browse the domains.
By default the Applicable Attributes panel shows all available attributes. When an applicable attribute is selected, the Attribute Range panel shows that attribute's range details.
The footer contains a copyright notice, help link (which opens the MRCM Maintenance Tool section of this use guide), and a contact us link (identical to that in the Authoring Platform footer).
The Domain Details sub-panel can be toggled closed/open when a domain name is selected.
When open, press on the right of the sub-panel title bar to close the Domain Details sub-panel.
When closed, press in the sub-panel title bar to open it.
The listed domains can be filtered by typing match text into the Filter Domains... text box above the list.
Clear the Filter Domains... box by deleting the text or pressing the X button at the right of the text box, to remove the filtering and re-show all domains.
Alternatively, press RESET to the right of the context and actions bar (upper right corner above the three main content panels). This clears all three content panels back to their initial view state.
Login needed
If you are not logged in to the Authoring Platform and enter the MRCM Maintenance Tool address directly in your web browser, or follow a bookmark link, you will first be prompted to log in. Once logged in with an authenticated account you will be automatically be directed back to the MRCM Maintenance Tool address.


Browse older versions of the MRCM
Use the header Version drop-down selector to set the version of MRCM to be browsed.
In the initial stage of classification, the task content branch is locked to prevent any further changes, and a warning notification is presented above the Classify action button in the Task Details panel.
Whilst this warning is present, changes cannot be made to the content saved in the task branch, and action buttons other than Edit Task Details become inactive.
Whilst classification is running, a status icon is presented in the page header, to the right of the task identifier.
When the task classification is completed, a header notification is presented which includes a link to the Classification Report containing the classification results.
EITHER
Follow the link in the header notification to open the Classification Report.
OR
Press View Classification (completed <em>< date-time-stamp></em>) in the left-hand button bar Classification sub-menu.
The Classification Report is presented in place of the Edit Panel, Concept Diagram, and left-hand context panels.
This contains the following:
Header bar with
Report label showing "Classification finished at < date-time-stamp>".
Each result can be previewed to confirm/review the changes prior to saving the classification results.
See for details.
Classification results can be downloaded to your local machine in .tsv format.
The download file contains each classification result on a new line (line 1 is a header line with field labels) with tab-delimited field values for changeNature, sourceId, sourceFsn, typeId, typeFsn, destinationId, destinationNegated, characteristicTypeId, group, id, unionGroup and modifier.
Press Accept Classification Results to save the classification changes to the task.
A "Saving classification" header notification is presented whilst the results are saved to the task branch on the Terminology Server.
A "Classification saved" header notification indicates changes are now in the task branch contents, and the Accept Classification Results button becomes deactivated with the label changed to Classification saved.
From this point the report can still be retrieved (via the left-hand button bar Classification sub-menu) for viewing and downloading of results, but no further changes are possible with this set of results.
If further changes are made in the editor, another classification must be run to pick up those changes.
Either
Press Classify in the Task View - Task Details panel actions button list.
Or
Press Run New Classification from the left-hand button bar Classification sub-menu.
A "Starting classification for task <task-id>" notification is presented in the page header.
A "Classification is RUNNING" notification follows once the Classification Service has received the task details.
Language and/or dialect variations Each extension may have language reference sets and dialect variations which modify the task presentation and interactions (see Working in an extension task below). Since AP 7.1.0 the Authoring Platform also supports searching using the Chinese (ISO 639-1 code zh) character set when the relevant language reference set is configured.
Template-based authoring constraints Templates are not yet available for extension-based authoring due to current constraints on language and dialect variations support for templates, so any features dependent on the use of templates are not available. When suitable templates become available which can support the variations needed for extension-based authoring, these features can be enabled, but until then they are switched off by project configuration settings.
International SNOMED CT International dependency version Member countries can extend SNOMED CT International Edition concepts by adding content within their own extension. Extensions are usually upgraded when an International SNOMED CT Member release becomes available which is typically one month before the public release date (on the current bi-annual release cycle).
Key differences compared to working in an International authoring task are:
There is no Create New Concept from Template option via the left-hand action menu button bar.
A new release of the International Edition is published monthly.
In SNOMED CT directional relationships can be made between concepts with a source concept and a destination concept. This is done by authoring axioms which are turned into relationships during the classification process.
On upgrading, an extension may contain one or more axioms which refer to a concept in the International Edition where the concept has become inactive in the new release.
Axioms are not allowed to refer to a concept which is inactive, so such issues must be identified via an , as part of the extension upgrade process.
The model diagram can be toggled between Inferred and Stated views.
The "before" model diagram in the Stated view shows the concept model defined in the task.
For simple new lead-node concepts defined as children of a high-level SNOMED CT concept, the before/after model diagrams may well be identical, but much depends on the concept ancestors and their inferred relationships.
For concepts created "deeper" in SNOMED CT there are likely to be additional inferred relationships in the "after" modelling.
The left-hand side of the Preview Pane presents the Taxonomy View panel, showing the concept's location within the SNOMED CT taxonomy.
This can also be toggled between Stated View and Inferred View, via the drop-down selector in the top left of the taxonomy view panel.
In the Inferred view this has no location to show yet, since the classification results are not yet saved.
The Taxonomy View panel can also be toggled between showing the FSN (in en-US) or the Preferred Term (in en-US), via the drop-down selector in the top right of the taxonomy view panel.
Press View Classification (completed <em><date-time stamp></em>) in the LH button bar Classification sub-menu.
The Classification Report is loaded, showing a tabulated list of concepts affected by task classification.
Press the Preview button to the right of a classification result.
A "retrieving concept before/after information..." notification panel is presented in the page header whilst the information is being loaded.
The preview pane then opens below the classification results, showing a before/after Inferred model diagram view of the concept.
The "before" model diagram in the Inferred view shows an incomplete model since classification results are not yet saved.
Task promotion has implicit checks for the following conditions:
No content changes made in the task.
Classification has been run in the task.
Classification was started but either failed to complete or has not completed.
Classification is current.
Classification has no results to accept.
Classification results have been accepted.
Review has been completed.
If no content has been changed on the task when promotion is initiated, a Promote Task pop-up notification states the there are no changes to promote.
Press Return to Task (or press the X in the upper right corner) to close the pop-up.
If content changes have been made but any of the other conditions are not yet satisfied when promotion is initiated, a Promote Task pop-up notification shows their statuses, with action options to cancel the promotion, or to continue if task changes are considered sufficiently safe to update the project level content without satisfying these conditions.
Press Return to Task (or press the X in the upper right corner) to close the pop-up and cancel the promotion without changing project content or the task status.Press Promote Anyway to continue promotion.
A "Promoting task..." notification is presented in the page header whilst branch content changes are merged to the project level.
During promotion, the task content branch is locked to prevent any further changes, and a warning notification is presented below the Edit Task Details action button in the Task Details panel.
Whilst this is present, changes cannot be made to the content saved in the task branch, and action buttons other than Edit Task Details and Submit for Review become inactive.
Once task promotion is completed, a "Task successfully promoted for <task-identifier>" notification is presented in the page header.
Following promotion no further changes are allowed on the task content branch, all action buttons in the Task Details panel become inactive, and a warning notification is presented below the now inactive Edit Task Details action button.


Press the <i class""fa-magnifying-glass">:magnifying-glass: Search button to the right of the query box, or press Enter on the keyboard.
Whilst the search is running, the results panel shows "Searching...".
Complex ECL queries
Complex ECL expressions which require analysis of many hundreds or even thousands of nodes may take some time to execute - from a few seconds to a minute or perhaps longer for extreme cases (for instance searching for all leaf nodes in SNOMED CT can take up to a minute).
Working with ECL search results
ECL search results are formatted and presented in the same way as text search results.
See and for more information.
After obtaining ECL expression search results, the results set can be refined by entering an additional term filter in the query box below the expression.
For example the ECL expression >!* returns all concepts that are leaf nodes.
By adding an additional term filter a particular set of matching leaf nodes can be found, such as all leaf nodes containing the word "limb" in their FSN.
Changing ECL search parameters triggers the search
Whenever the ECL expression or additional term filter is modified, or the Inferred / Fully Defined / All or All / Primitive / Fully Defined options are changed, a new search will be triggered.
ECL search results can be switched between the Inferred (default) and Stated view.
ECL search results can also be filtered by their Definition Status:
All (Primitive and Fully Defined)
Primitive
Fully Defined





After making the desired content changes, press Begin Promotion Automation in the Task View - Task Details panel actions button list.
A "Preparing for task promotion automation..." notification is presented in the page header bar.
The automated promotion process first checks to see if the task has been reviewed.
If a review has not yet been completed the Promote Task dialogue presents a warning message with calls to action to either continue or return to task editing and cancel the promotion.
Press Promote Anyway to continue the promotion process.
Press Return To Task to close the dialogue and stop the promotion process.
New concepts created in the task
New concepts created in the task may be tricky to get back into the Edit Panel if removed but not added to the task Saved List for later easy retrieval.
If removed unintentionally before adding to the Saved List, concepts created in the task can be found in the To Review list in the Feedback View (even if not yet submitted for review).
EITHER
Load a concept from the Taxonomy listing: Single-Press a node label to load that concept into the Edit panel.
OR
Load a concept from Search results :Press the search result FSN term (Edit) to open the concept in the Edit panel.
The concept loaded in the Edit panel shows two distinct content panels:
Concept Diagram view of the concept in various forms of logical modelling.
Concept Editor with its active descriptions and axiom details, and various options for editing/modifying the concept, either via action icon buttons in the concept header (which act on the entire concept) or via controls associated with each description and axiom.
Concept Diagram actions are:
Press the Taxonomy tab in the Task View - Context Panel tabs list.
The Task View - Context Panel switches to the Taxonomy view with a hierarchical tree-node representation of SNOMED CT concepts, based on their parent-child (Is-a) relationships.
Each row in this view represents a hierarchy node, and is preceded by one of two icon buttons:
(child nodes expanded)
(child nodes collapsed)
Rebase eligibility is indicated as an active (yellow) Pull in Mainline Changes icon button in the project actions button bar in the upper right corner of the Project View.
Press Pull in Mainline Changes to initiate the rebase process.
EITHER
On any page in the Authoring Platform , press the icon to the left of the word Dashboard in the header. This presents a pop-up navigation menu.
Press Reporting Platform in the pop-up menu options (last item).
OR
Enter the URL https://authoring.ihtsdotools.org/reporting directly into your web browser address bar (save the URL to your web browser bookmarks for easy retrieval if desired).
With an International published concept loaded into the editor, view the concept descriptions.
Translated terms appear as individual descriptions set to be the Preferred Term (PT) for the languages-dialects available in a specific SNOMED CT extension.
The example shown here is the International published concept which was loaded by searching for the French word "événement" and pressing "événement accidentel" in the search results.
Note the language-dialect acceptability settings for each description row:
The first description is always the Fully Specified Name (FSN). This is always defined as Preferred in the en-US dialect.
The second description is the International Edition PT, which is defined as a SYN (synonym) set to Preferred in the en-US dialect.
Taxonomy Language options: As well as the FSN in en-US, there are additional options for Preferred Term (PT) in en-US (default) and PT in extension dialects. When PT dialect options are selected, any translated PTs available in that dialect will be shown in the taxonomy listing (if no translated PTs are available, it will show the en-US PT).
Search
Filter by language/dialect options: Search results can be filtered by FSN in en-US, or PT in the available extension languages / dialects.
There is no Switch to Template search option (Text Search and ECL Search only), and by implication no Transform using template feature (this is only available for template search matches).
There is no template-based authoring Batch mode tab in the Task View context panel options. However, as noted below, batch translation description imports are supported for extension authoring.
Upload a Batch. Available from the left-hand menu button bar, this feature supports uploading of formatted text files which can contain multiple description additions, description changes, and description inactivations, for batch processing and review of translation terms via authoring tasks within a Managed Service extension project. This is not to be confused with the template-based batch authoring features, which support logical as well as lexical modelling for International authoring.
Editor
Concept descriptions presentation: Extensions may show additional descriptions for Preferred Terms in their dialect variations.
Concept dialect PT automation: When creating a new concept, the en-US PT will be automatically populated from the FSN term (as for International), but the additional dialect variations will not be populated since their terms need manual translation verification.
More details pop-ups - Module Id: New concepts created in an extension are saved in the extension module. This can be seen in the More details pop-up dialogue via the ellipsis icon button to the left of the concept header and each description row. If translated terms are added to a published International concept, each dialect PT will also show as being saved in the extension module, rather than the SNOMED CT core module or model module (which the concept header will show).
Promoting tasks with warnings
Pressing Promote Anyway is tacit acceptance of any warning statuses, with implied responsibility for by-passing these safeguards and the consequent unclassified and/or unreviewed content changes that will be promoted from the task to the project level.
Promoting unclassified content changes is a quality assurance risk that can be avoided relatively easily, since it typically takes less than ten minutes to run classification (if only to confirm no results).
However, there are occasions when it is clear that inferred classification results won't change, such as a description-only content change, in which case this option may be acceptable.
By-passing review may also be acceptable under particular circumstances, for instance if the author is also the project manager / project lead.
This scenario can be prevented by setting the task as Complex and also having Review Completed set as a mandatory task-level SAC requirement within its parent project configuration, since task promotion in this case will not be enabled without a completed review.
















The default option is MAIN which selects the MRCM content defined on the International Authoring Platform for the current authoring cycle, and so which will be in the next SNOMED CT release (by its nature this content is subject to change). The other options are previous published versions of SNOMED CT, each of which shows the version of MRCM included on their release.


















Download Classification Results icon action button
Accept Classification Results icon/text action button.
Report change listing, with tabs for Classification Results, Removed Inferred Relationships, Inferred Not Previously Stated, and Equivalency Errors.
Each report tab shows Differences, Source, Type, Destination and Group information, and also a Preview Results button for each result row.
Classification results download file (.tsv format)












View in Taxonomy
Open diagram in a new tab
View diagram in Authoring Form (AF)
View diagram in Stated Form
View diagram in Inferred Form
Concept Editor actions available from the concept header for an unpublished concept (one that has been created within the current authoring cycle and hence not yet included in a SNOMED CT release) are:
Left of header bar title (concept FSN):
More details
Attach template (if template services are enabled for the project)
Concept information helper pop-up menu (cut/paste buffer helper)
Copy Conceptid
Copy FSN
Copy FSN and Conceptid
Right of header bar title (concept FSN):
Save concept
Show/hide inactive components
Revert to version
Delete unpublished concept
Switch to inferred view / Switch to Stated view (toggles between the two options)
See project version
Remove concept (from edit panel)
Collapse / Expand the concept component panel
The concept header also includes status display icons for:
Shortcuts active
Definition status (set by axiom Definition status - if any axiom in the concept is set to Fully defined, then the concept status is >Fully defined)
published concepts have editing constraints
If the loaded concept has been previously published in a SNOMED CT release, the following Edit panel constraints apply to the concept:
Published descriptions (those with an
Maximum of 10 concepts in Edit panel
The Edit panel can load a maximum of 10 concepts concurrently (for optimal web browser performance). If 10 are already loaded, a header notification will be presented when attempting to load more:
If this limit is reached and another concept needs to be loaded, at least one of the currently displayed concepts must be removed from the
Content panel widths can be adjusted
The Settings and Preferences pop-up panel (available via the top right corner "cogwheel" button) includes a Page Layout visual control which sets the relative widths of the sidebar, model diagram and concept editor panels. If modified and saved, the change will persist for the authenticated user.


The initial view shows 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)| at the top of the listing, in its expanded presentation, revealing the SNOMED CT top level concepts.
Each taxonomy row also has the following:
Primitive or Fully Defined definition status icon
Text label showing either the concept FSN or Preferred Term (PT) in the en-US dialect
Press Primitive or Fully Defined to open a Concept Details pop-up box as described in View concept details when browsing the taxonomy.
Single-press a node label to load that concept into the edit panel.
Double-press a node label to change the focus of the taxonomy tree to that concept.
This presents the same view as opening a concept in the taxonomy from a Task View - Search result (see Act on concept search results) or Task View - Saved List entry (see Add a concept to my task Saved List and act on saved concepts).
Above the taxonomy listing are two presentation controls:
Switch between Inferred View (default) and Stated View
Switch between FSN in US (default) and PT in US for the node label text
Navigate down the taxonomy nodes by successively expanding selective child nodes.
When a concept is reached that has no child concepts (ie it is a taxonomy "leaf" node), the row entry is preceded with a icon, indicating that no further expansion is possible.
Any taxonomy node that is visible can be expanded or collapsed independently of the others. Changing one node does not affect others previously expanded or collapsed at that level or above - only direct descendants are affected.


The third description is the French language PT, which is defined as a SYN set to Preferred in the fr language.
The fourth description is the Dutch language PT, which is defined as a SYN set to Preferred in the nl language.
Use the More details buttons on the description rows to compare details for the various concept descriptions:
The FSN and en-US PT are defined in the SNOMED CT core module with Lang. setting en.
The extension translated PTs are defined in the Belgian module, with Lang. settings fr and nl respectively.
The SCTID of each translated PT contains the Belgian extension namespace identifier: 1000172.
Since this is an International Edition published concept the More Details panels include an Eff. Time (Effective Time) value (the release of SNOMED CT in which they were last published).
The Effective Time for extension descriptions will be the last publication date for their extension, whereas the FSN and en-US PT show International Edition release dates.
As can be seen in this example, the description Effective Time may differ from that of the concept itself.


Following the review check, the task is then placed in a promotion automation queue.
A notification panel showing "Automated promotion in progress: Status Queued" is presented between Edit Task Details and Classify in the Task View - Task Details panel actions button list.
An "Automated promotion: Queued" status icon is also presented in the page header bar.
When picked up from the queue, the task is checked to see if needs to be rebased.
If the task content is diverged from its parent project content, the process initiates a task rebase, and the notification panel changes to "Automated promotion in progress: Status: Rebasing".
If rebase completes with no conflicts, the auto-promotion process continues.
Task review check
If merge conflicts are found during rebase, the automatic promotion process is stopped, and the process notification changes to state that rebase conflicts must be resolved before restarting automatic promotion.
After confirming that the task does not have any rebase conflicts, classification is invoked to ensure all content changes are classified prior to promotion.
The process notification panel changes to "Automated promotion in progress: Status Classifying"
The page header bar icon changes to "Classification Running".
Once the promotion automation invokes the classification process, the My Tasks view task Status column entry changes to Auto Classifying.
If classification detects results (unclassified task content), a header notification states that classification completed successfully with changes found.
Unclassified content blocks auto-promotion
If classification results are found, the auto-promotion process is stopped, and the process notification panel changes to inform that classification results were detected, with an instruction to review and accept classification results before restarting the auto-promotion process.
If classification does not detect any changes, a header notification states that classification completed successfully with no changes found.
The automation process proceeds with task promotion, following which a header notification states that automated promotion completed for the task.
At this point task actions become inactive, and the process notification panel changes to inform that the task has been promoted and no further changes are allowed.
Promoted tasks are hidden by default in the My Tasks view, however they can be brought into the view listing by checking the Show Promoted checkbox.
Their task status shows Promoted, with a blue background.
All historical promoted tasks are shown when the box is checked, not just the most recently promoted.
Unmet SAC items block automatic promotion
If the task has any Service Acceptance Criteria (SAC) items, task promotion will be blocked and the Begin Promotion Automation action button will not be enabled until all mandatory task-level SAC are met.
Role-based access controls apply to automatic promotion
If the user's authenticated account session roles do not include permissions for task promotion (such as when viewing another author's task), the Begin Promotion Automation action button will not be enabled.
Task review check
The warning is only presented if a review has not been completed.
Task status
After pressing Begin Promotion Automation, the My Tasks view task Status column remains In Progress until the review check is completed.


The main display panel changes to show a blue "Comparing project to mainline content, please wait just a moment..." full display panel notice (with an animated timer indication that the comparison process is taking place).
If the rebase comparison shows that merging can be completed with no content conflicts, the main display panel changes to show a green "Project can be merged with mainline content without issues, pulling changes in from mainline content..." full display panel notice (with an animated timer indication that the merge process is taking place).
Project rebase issues
Project merges generally complete without issues, however some conditions such as a component integrity issue may occur, for instance where a dependent concept is missing or inactivated unintentionally.
These situations may trigger a red alert box overlay in the page header with an indication that technical support should be sought to resolve the problem. The message below shows an example of a missing or inactive referenced concept in an axiom triggering a rebase problem:
Once the merges are completed, the main display panel changes to show a green a green "Success! Switching to project view in five seconds..." full display panel notice, which closes automatically after five seconds have elapsed (during which the merges are finalized in the project branch content).
The Project View is reloaded, with the Pull in Mainline Changes (rebase project) button now inactive (greyed out).
At this point the project branch status has been returned to Forward, and changes made within the project are once again eligible for promotion to the mainline.


The Reporting Platform entry view is presented, showing a Categories selection panel to the left, and an associated Query List panel to its right.












On first opening a task which has upgraded content, an Integrity Report check is triggered which scans the content for issues.
Whilst this is proceeding, the task content area shows the Integrity Report check is running. Please Wait... notice.
On completion of the checks, if integrity issues have been found the Integrity Report view is presented.
This contains the following:
Left-hand context tab panel, containing:
Issues List - all concepts with integrity issues, with select and preview actions
Either
In the Task View - Task Details panel actions button list, press Validate with MRCM or Validate without MRCM.
Or
From the left-hand button bar Validation sub-menu press Start New Validation with MRCM or Start New Validation without MRCM
A "Task successfully submitted for validation" notification is presented in the page header, along with a validation status icon to the right of the task identifier, and a Validation has been scheduled status message replaces the request button in the left-hand button bar Validation sub-menu.
On initial submission for validation, the task content branch is locked briefly to prevent any further changes, and a warning notification is presented below the Edit Task Details button in the Task Details panel.
Whilst this warning is present, changes cannot be made to the content saved in the task branch, and action buttons other than Edit Task Details become inactive.
The task is typically unlocked for editing within a few seconds before the header notification is removed.
Press a concept's Definition Status icon.
The Concept Information pop-up overlay window is opened.
A loading message is shown until the window contents are available (loading from the Terminology Server).
Description Logics (DLs) exist to enable a reduction in content maintenance costs with a concurrent increase in content quality. Processing power and reasoning algorithms have improved such that a more expressive DL is now practical to use in SNOMED CT.
The principle benefit of more DL features is the ability to represent content in a more fully systematised and thus more machine processable way, to enable the following benefits:
increased efficiency, consistency, precision and quality of authoring through reduced manual effort to organise content
lower costs to author and maintain content through reduced manual effort











Copy Term and Conceptid
More detailscannot have their description terms edited;
cannot be deleted (but can be inactivated and replaced if needed);
cannot have their language and dialect preferences changed.
Published axioms (those with an Eff. Time value in their More details properties:
cannot be deleted (but can be inactivated and replaced if needed);
cannot have their relationship types or target value edited (but entire relationships can be removed and replaced if needed).
















Search
Taxonomy View
Right-hand concept preview/edit panel, showing:
Prior Version of the concept with issues
Suggested Resolution for the issue
The Search and Taxonomy tab views are the same as those available in the usual task view, and are provided here to support investigation and location of alternative target concepts to resolve the integrity issue.
When first presented, this view automatically previews the first concept in the list (as indicated by the inactive status of its preview icon in the Issues List.
List paging controls and visible list size options are presented below the list.
Each concept in the list can be individually previewed and resolved via editing in the Resolution panel, but the platform can also apply the suggested resolutions automatically if they do not cause validation errors.
To apply a suggested resolution to an individual concept, press the Save and next icon button in the Resolution panel.
A header notification indicates that the concept is being saved.
Drools Rules warnings may appear briefly when saving the concept, but do not prevent saving.
Saved concepts can be reviewed later via the usual feedback and review process, so integrity resolution save warnings can be followed-up as needed.
After manually saving a concept, the next concept in the Issues List is automatically previewed for issue resolution.
The saved concept is removed from the list, and the Total Items count is decremented.
Once loaded, the new first item on the Issues List is previewed, ready to repeat the process for this next concept.
As well as resolving each suggested resolution manually on a concept-by-concept basis, a number of concepts can be selected and processed automatically as a batch.
To do this, press the checkboxes alongside each desired Issues List item to define a batch list.
With the desired concepts selected via their check-boxes, press the Auto-fix icon button to the upper-right corner of the Issues List.
A header notification shows that the selected concept resolution suggestions are being saved.
A header notification shows the number of concepts which were successfully saved, and the Issues List updates to preview the new first item, with the Total Items count decremented by the number of saved concepts.
For rapid processing of the entire list, press the Select all checkbox in the Issues List header.
With all Issues List concepts selected, press the Auto-fix icon button to processing the entire list.
Whilst most integrity check suggestions will likely save without manual intervention, with a long Issues List , it's also quite probable that some suggested resolutions will trigger Drools Rules errors that prevent saving.
Once the automated process has saved all the items that don't need manual resolution, a header notification shows the number saved successfully, and also the number that failed to validate on attempting to save.
The items that were unable to be saved due to validation errors remain on the Issues List , with the new first item automatically previewed, and the item count is updated to show the total remaining.
These items must be manually fixed concept-by-concept by editing in the Resolution preview panel.
To see the errors that prevented automated saving, press Save and next in the Resolution preview panel.
The header and concept panel notifications are the same as those that would be obtained through normal editing.
Use the Resolution panel editor details information and the Search and Taxonomy View context tabs to identify alternative solutions to resolve the issue.
When the last item on the list has been successfully saved, the Integrity Report automatically runs again to confirm the changes.
When the Integrity Report completes with no issues, the usual Task Details view is presented.
From this point onwards the Integrity Report check will no longer be triggered when opening the task.
All concepts saved from Integrity Report issue resolutions are available in the task Feedback context tab, in the same way that manually authored content is listed (any other concepts edited in the task will also be in this list).
Load a list concept in the Feedback Preview panel to see its change details.
Closing and re-opening a task with integrity issues
After running an Integrity Report and detecting items with issues, any time the task is subsequently closed and re-opened (perhaps in a new session), the Integrity Report check will trigger.
Further task editing is not possible until all integrity check issues have been resolved.
Automated integrity issue resolution
Running the Integrity Report automatically resolves issues due to an inactive concept having an active description which is missing an "inactive concept" indicator, and also when an inactive description is referenced in a language reference set.


If the terminology server encounters such an issue when trying to merge project and mainline content, it may roll back changes to restore the pre-rebase branch states to avoid leaving them in an unusable condition. As the message states, please contact technical support if such an alert occurs.




The opt-in checkbox enables the form to capture details about your current web browser environment. You can press the What is included in the data about my current environment? link to preview those details and help decide whether or not to include them if unsure.
Including them can help the technical support teams when troubleshooting defect reports, particularly anything related to screen presentation/layout, but of course it's entirely optional.
Press Submit in the form footer to submit your entered feedback details. A Thank you for your feedback! message will appear for 5 seconds and then the pop-up form will automatically close, returning you to whatever AP context you were in when the Raise an Issue button was pressed.
For the International Authoring Platform this creates a Devops Support (INFRA) ticket, which the Technical Team will assess, prioritise and respond to with appropriate notifications and follow-up actions (your patience is appreciated!).
Alternatively, if you have decided not to raise an issue since opening the form, simply press Close in the form footer to immediately close the pop-up dialogue and return to your AP context.
Create a new project in the Jira workflow instance associated with the Authoring Platform, and associate the project schemes with those needed for content authoring.
Technical Team support activity.
Create a new "project" ticket type in the new project. Ensure that the "product code" matches that configured for the Authoring Platform deployment.
Technical Team support activity.
Verify the new project is available in the Authoring Platform (use the Create New Task form to view the available projects list).
Technical Team support activity.
Press Raise an Issue to report issues or submit change requests related to AP usability and features.
The Raise an Issue pop-up form is presented. If the form height is larger than your available web browser display height, a vertical scroll bar will appear to allow you to scroll down and see all the form content (the form header title and footer actions remain visible whilst scrolling). The following fields are available:
Summary (required, single line text, maximum of 255 characters)
Description (multi-line text with markup formatting support for structured text)
Attach file (using your browser's local file upload features)
Priority (single choice option list selector)
Name (single line text, maximum of 255 characters)
Email (single line text, maximum of 255 characters)
Include data about your current environment, like the browser and page URL (opt-in checkbox)
The form footer has a Submit action button and a Close link.
Authoring projects are managed and configured in the Authoring Platform (AP) underlying workflow instance (Jira), using particular field configurations, issue types, workflows and permissions schemes.
The process is outlined here to show the underlying platform dependencies and steps to prepare a project for SNOMED CT content authoring, but managing them for the International Authoring Platform is currently a SNOMED International Technical Team support activity.
Please note this is not a detailed definition of the support activity steps or Jira setup requirements - those are available in other Technical Team process documentation.
An authoring project is defined by a "project" type ticket in the AP workflow Jira instance which must exist for that project to be seen in the AP projects list (it's not sufficient just to create a Jira project). The instance of Jira used is an AP deployment configuration setting.
Once defined there is an association between the project tickets in Jira and their corresponding project content branches in the AP terminology server (Snowstorm for AP 6), which are named to match their associated Jira project key.
Similarly, authoring tasks have an associated branch under their parent project branch which is named to match their task ticket Jira ID.
These project keys and task IDs can be seen in the various page addresses when using the AP.
AP project visibility depends on a "product code" (Jira custom field) set in the project ticket. Particular AP deployments are configured to use a particular product code (or list of codes).
This allows a single Jira instance to support projects across multiple Authoring Platform deployments if needed.
You can use the Raise an Issue process outlined below to request creation of a new authoring project.
Enter the desired project details in the Raise an Issue form. The more information included the better, but the minimum needed is a new project name (this will be what appears in the AP projects listings) and a brief summary of its purpose.
Confirmation of which Authoring Platform, a preferred project key satisfying Jira key conventions, and in particular a reference to any similar existing projects, can significantly simplify and hence speed up the process, although these can also be inferred/defined by the Technical Team if not specified.
Enter the desired details. The more information included the better, but also try to be as concise as possible and ideally keep to one identifiable issue per submission - this will simplify subsequent processing and hence make it quicker to assess, prioritise and investigate further if needed.
The minimum needed is a brief one-line Summary of the issue. Everything below that on the form is optional.
The Description field supports formatting options for structured text. Press the small question mark icon to open a Text Formatting Notation Help pop-up window with guidelines on including advanced formatting (wiki) markup.
You can use the Attach file (Choose Files) field to include a file attachment such as a screenshot.
An indication of the issue impact or urgency can be included using the
The following steps are not done in the Authoring Platform itself, but are included here for information and to complete this overview of how an AP authoring project becomes available
a more complete and consistent product that is, as a consequence, more usable (for implementers and end users) and attractive (to drive adoption and implementation)
reduction in the cost of assessing the impact of modelling change, because changes also become systematically describable (and transformable).
simplification of content modelling by removing workarounds
close interoperability with an international standard, OWL, allowing easier application of other standards and tools
explicitly specified logic profile for Description Logic features used in SNOMED CT
Attribute concepts have the ability to declare DL property characteristics as Transitive or Reflexive.
Property characteristics are currently maintained via the Terminology Server Application Programming Interface (TS API). Changes can be made via service requests to the technical team.
Example concept JSON data structure showing a Transitive property characteristic
When saved via the TS API, the changes are written into the Owl Axiom Reference Set as shown in the following examples:
900000000000012004
733073007
116680003
TransitiveObjectProperty(sct:116680003)
900000000000012004
OWL DL Property Chains can now be used within the authoring platform to infer additional concept properties during classification.
These inferred attributes appear in classification results along with all other inferred relationships.
Property chains are currently maintained via the TS API. Changes can be made via service requests to the technical team.
Example
This feature allows |Has active ingredient| to be linked with |Is modification of| such that a medicinal product that has an active ingredient which is the modification of another substance, could classify as a child of a product containing the less modified substance.
This behaviour is critical to controlling the effect of changes to the |Substance (substance)| hierarchy on other hierarchies.
Axioms are a relatively new part of SNOMED CT concepts. Each Axiom is like another mini concept definition including definition status and a set of stated relationships. These are presented and maintained through the concept edit panel in the same way as the earlier version stated relationships, visually located below the existing stated relationships of the concept. Axioms have a named concept on the left and an expression on the right.
The relationships within each additional axiom follow MRCM rules just like the stated relationships. At least one is-a relationship is required in an Axiom. The concept editor panel supports creation, editing and removing of axiom relationships. There is no released or active state on axiom relationships - they can always be modified or deleted.
Each Axiom of a concept is necessarily true. The attributes from all Axioms are in the inferred form and are inherited by children through inference. The normal form process may reduce these attributes if a more specific attribute or group of attribute is present, in the same way that is does for attributes from the stated relationships. Attributes in an Axiom are inferred on the named concept and its descendants.
Example
Concept A has Axiom A1 (stated relationships) and A2. Concept B has Axiom B1 (stated relationships). Concept A subsumes Concept B - Concept B gets the inferred attributes of Axiom A1 AND A2.
Non-attribute concepts have the ability to declare general class Axioms in addition to the stated relationships.
General Concept Inclusions (GCIs) with Axioms provide authors with greater flexibility in how concepts are defined, and provide classifiers with a greater ability to make appropriate inferences.
For example, these features can be used to state that a subset of attributes is sufficient to define a concept, and therefore that this sufficient set can be used to classify other concepts as descendants in the hierarchy.
Each GCI is recorded as a separate Axiom expression within a separate member of the Owl Axiom Reference Set. A GCI has a definition status which is represented using a SubClassOf or EquivalentClasses axiom expression.
{
"effectiveTime": "20110131",
"moduleId": "900000000000012004",
"active": true,
"released": true,
"conceptId": "123005000",
"fsn": "Part of (attribute)",
"definitionStatus": "PRIMITIVE",
"preferredSynonym": "Is a",
"propertyCharacteristics": ["Transitive"],
"descriptions": [],
"relationships": [],
"isLeafStated": true,
"isLeafInferred": true
}Once the desired changes are specified and available in a local .tsv file, return to the Upload a Batch dialogue to specify the upload with:
Task Title
Select Assignee (type-ahead search for names list)
On successful completion of the batch upload, the Batch Upload Complete header notification will appear, and a local machine file save dialogue box will be presented to allow local saving of a batch results .tsv file with the outcome of the upload process.
Opening the batch result .tsv file on your local machine will show tab separated values with a row corresponding to each change row in the upload file. The final column of the results data indicates the outcome of the upload for that row (true for success).
The My Tasks dashboard view will also be updated to show the task(s) created by the batch upload, which carry the related content changes.
If an error is encountered during batch processing of particular rows, whilst other changes are successful, the Batch Upload Completed With Errors header banner will be presented.
In either of these failure cases, a batch result .tsv file is generated.The local operating system file download dialogue is invoked to allow saving of the batch result file.
Inspecting the batch result file shows further information to help understand the failure cause(s) for the rows which could not be processed successfully.
If the batch upload process fails during parsing of the upload file, the Batch Upload Failed header notification will be presented.
The header notification includes additional diagnostic information, but a results file is not generated.
Press Upload a Batch in the left-hand navigation menu. The Upload a Batch dialogue box is overlaid on the screen.
Download the latest version of the Translation Import Template (Batch Upload) template file using the here link in the text below the dialogue box title.
The Batch Upload template is a spreadsheet in Microsoft .xslx format, with multiple tabs corresponding to the type of batch change supported.
Follow the instructions in the first tab to define a set of changes in the appropriate sheet tab, then download that tab as a local file in .tsv (tab separated values) format.
Whilst validation is being processed, status icons are presented in the page header, to the right of the task identifier, and the Validation has been scheduled status message replaces the request button in the left-hand button bar Validation sub-menu.
Validation takes many minutes to complete
Validation is one of the most computationally intensive activities for the Authoring Platform, so takes some time to complete.
Each validation request is placed in a queue for processing by the Release Validation Service (RVF) so completion time can depend on how many are queued as well as the computational performance of the RVF.
Completion time can be up to 30 mins, perhaps longer in extreme cases, but is more typically around 10-20 mins.
When the task validation is completed, a header notification is presented which includes a link to the Validation Report containing the validation results.
EITHER
Follow the link in the header notification to open the Validation Report.
OR
Press View Validation Report in the left-hand button bar Validation sub-menu.
The Validation Report is presented in place of the Edit Panel, Concept Diagram, and left-hand context panels, with an "Initialisation complete" header notification.
This contains the following:
Header bar with:
Report label showing "Validation Report Completed <date-time-stamp>".
Show Full Report text action button.
Show Exceptions text action button.
Report panel.
If the task contains no validation errors, the message "No validation results to display" is presented in the report panel.
If the task has validation issues then the validation report will contain listings of Failed Assertions and Warning Assertions.
Each list entry contains:
Validation assertion description.
Total number of cases (concepts) related to that assertion.
Load Cases icon/text action button.
Press Load Cases on an assertion list entry to see the concepts which triggered the assertion.
The report panel switches to a tabulated list of concepts below a header line which contains the Assertion Failure text, and a Back to Report icon/text action button (which returns to the case listing view).
Each concept row has the following:
Select box.
Concept Id (SCTID).
FSN term.
Semantic Tag
Error Message.
Add to Exceptions text action button.
View/Edit Concept icon button.
The table rows can be sorted by Concept Id, FSN, Semantic Tag and Error Message by toggling the column header labels.
The select boxes on each row work in combination with the Add selected to Exceptions and View/Edit Selected Concepts action buttons in the rightmost two column headers. These actions will be applied to all selected concept rows to quickly process them as a group.
Press Add to Exceptions (on a single concept row) or Add Selected to Exceptions (selected rows) to open the Add to Exceptions dialogue overlay.
Exceptions can be added as either a Permanent Exception or Temporary Exception.
Add a Reason for the exception, then press Save to put the assertion on the relevant exceptions list, or press Cancel to return to the validation report without adding to the Exceptions list.
Exceptions lists have project scope
Note that any exceptions added from a task will apply to all tasks within the same project.
Exception listed cases are removed from the Failed Assertions and Warning Assertions listings.
The Exceptions List is initially presented for the task's project, but the list scope can be switched between This Project and All Projects.Such cases can be viewed by pressing Show Exceptions in the Validation Report header.
Press Hide Exceptions to remove the Exceptions List from view.
Press View/Edit Concept (on a single concept row) or View/Edit Selected Concepts (selected rows) to see case concepts in an embedded Taxonomy/Editor panel below the cases table. This supports direct inspection and editing of concepts on a case-by-case basis without leaving the Validation Report.
To remove a concept from the Taxonomy/Editor panel press its "X" (Remove concept from edit panel) icon button in the concept header icon button list (as for the main Editor view).
Press Download to save a list file to your local machine in .tsv format. The file contains the Concept ID (SCTID) and FSN term for each concept in the cases list (one per line, tab-delimited; line 1 is a header line with field labels).
Validation download file (.tsv format)
By default the Validation Report shows only assertion failures triggered by concepts modified within the task.
Press Show Full Report to see all assertion failures for the entire branch contents.
These may include assertion failures carried into the task from the project level, either on task creation or via task rebase.
When viewing the full report, press Show Task Report to return to the default view and only present assertion failures triggered by changes made within the task.
Validation with or without MRCM
Validation with or without MRCM depends on the checkbox setting in Task Details.






Concept Information - Incoming Relationships
Incoming Relationships - Filtering by characteristic type (stated/inferred) or by relationship type
Paging for large lists - page number buttons, page left and page right buttons
Paging for large lists - items per page
Concept Information - Incoming Historical Associations
Concept Information - Details
Concept Information - Taxonomy


Google sheets can be used to quickly generate .tsv files from a worksheet tab, via its File > Download > Tab separated values (current sheet) menu function. Google sheets also offers useful file sharing and commenting options, so can be an efficient approach to defining, reviewing, and refining extension translation terms prior to importing into the Authoring Platform.
Here are some example .tsv translations (New Zealand) batch upload files:
Reference file:
Reference file:
Reference file:
To help with editing efficiency and convenience (as well as helping to minimize RSI impact associated with extended use of mouse/trackpads) the Authoring Platform supports the use of keyboard shortcuts. Shortcuts are defined so as not to collide with operating system (OS-X and Windows) and web browser (Chrome) provided defaults, and are provided in the context of dashboard navigation, task view navigation/search, task concept editing, and project view navigation.
?
Show / hide the dashboard context keyboard shortcuts help menu (this list)
When in text search mode (default on opening Task View - Search tab), first press Switch to ECL.
When in ECL search mode, press Switch to Template.
The search tab changes to Template search mode, with a template name query box at the top of the search panel.
Type a template name (or part of a name) into the search query box - type-ahead searching starts after at least three characters are entered, with matching available template names presented in a drop-down selection box below the query.
With a published unchanged source concept from the extension loaded into the Editing panel, press the caret-up button on the right of the concept header panel to open the concept header extended menu.
Press Request Promotion in the extended menu options list.
alt + p
Go to Projects
alt + w
Go to Review Tasks
alt + 1
Go to Taxonomy
alt + 2
Go to Search
alt + 3
Go to Saved List
alt + 4
Go to Review
alt + 5
Go to Batch
alt + i
Go to Info
alt + e
Go to Editing
alt + y
Start classification
alt + v
Start validation
alt + n
Create a new concept
alt + d
Create a new description (in focus concept)
alt + r
Create a new relationship (in focus concept)
alt + g
Create a new role group (in focus concept)
alt + a
Show/hide inactive components
alt + s
Save (in focus) concept
alt + x
Close (in focus) concept in edit panel
alt + →
Select next concept
alt + ←
Select previous concept
tab
Step through all tab-ordered control elements (including header navigation, menu buttons, context panel actions, concept edit panel form elements)
enter
Defocus text field, go to next field in editor
alt + p
Go to Projects
alt + w
Go to Review Tasks
alt + y
Start classification
alt + v
Start validation
alt + l
Go to notification link
alt + h
Go to Home - My Tasks
alt + b
Open TS Browser
alt + p
Go to Projects
alt + w
Go to Review Tasks
alt + n
Create a New Task
alt + l
Go to notification link
alt + q
Close all concepts
?
Show / hide the task context keyboard shortcuts help menu (this list)
alt + h
Go to Home - My Tasks
alt + b
Open TS Browser
?
Show / hide the task context keyboard shortcuts help menu (this list)
alt + h
Go to Home - My Tasks
alt + b
Open TS Browser

733073007
733928003
ReflexiveObjectProperty(sct:733928003)
900000000000012004
733073007
733928003
TransitiveObjectProperty(sct:733928003)


































PriorityIncluding your Name and Email will help in identification, tracking and follow-up notifications/discussions.
Create test task in the new project and perform a search to initialize the project branch in the Terminology Server.
Technical Team support activity.
Notify the request originator (INFRA ticket reporter) that the new project is ready for use in the Authoring Platform.
Technical Team support activity
Close has no second chance!
Be wary there is no guard on the Close action - as soon at it is pressed, any entered information is lost. If you want to preserve anything for a later submission please use your local environment cut/paste tools to capture anything essential first!







706689003
Application programme software (physical object)
He raupaparorohiko raupaparorohiko
mi
cI
SYNONYM
Maori
PREFERRED
442376007
Test with result pending (observable entity)
Whakamatau me te hua ka tatari
mi
cI
SYNONYM
Maori
PREFERRED
70056012
Insertion of catheter into heart chamber
cI
SYNONYM
NZ English
ACCEPTABLE
US English
ACCEPTABLE
GB English
ACCEPTABLE
3658267015
Inflammatory disorder due to increased blood urate level
ci
SYNONYM
NZ English
PREFERRED
US English
ACCEPTABLE
GB English
ACCEPTABLE
150085018
Gout
CS
SYNONYM
NZ English
ACCEPTABLE
US English
PREFERRED
GB English
PREFERRED
51631000210119
Screening for diabetes mellitus during pregnancy
Outdated
706690007
Web-based application software (physical object)
Me tono rorohiko-a-paetukutuku
mi
cI
SYNONYM
Maori
PREFERRED
51691000210118
GDM-Gestational diabetes mellitus screening
Erroneous
Download icon/text action button.


















Enable Drools Validation (optional)
Select Project (from available projects list)
Select Reviewer (type-ahead search for names list)
Select Import Type (from available list matching the Batch Upload template change type tabs)
Select Batch File (invokes your local machine's file selection dialogue to pick the relevant .tsv file)
When all required parameters are defined, the Create Tasks button will be enabled.
Press Create Tasks to start the batch upload process.
Out of date batch template format
This scenario may be caused by trying to upload batch changes using an earlier version of the template file rather than the latest version expected by the Authoring Platform. The screenshot shows an example of the error message when this occurs.
To resolve this error condition, download the latest version of the template (described above), and enter and save the required change data using the updated specification format, and then repeat the upload process with the updated format file.












If the rebase comparison shows that merging can be completed with no content conflicts, the main display panel changes to show a green "Task and project can be merged without issues, pulling changes in from project..." full display panel notice (with an animated timer indication that the merge process is taking place).
Once the merges are completed, the main display panel changes to show a green "Success! Switching to task view in five seconds..." full display panel notice, which closes automatically after five seconds have elapsed (during which the merges are finalized in the task branch content).
If the merge comparison detects conflicting changes in the task branch and the project branch content, then the Concept Merges screen appears when the comparison screen closes.
This presents a list of the concepts that need merge conflicts to be reviewed and resolved in a context tab navigation panel to the left, with a Conflict Resolution display panel to the right (initially this will be blank).
In the Merges To Review tab Press the blue "pencil" icon button to the right of a concept FSN in the concepts list.
The display panel shows a 3-panel Concept Merge Resolution view, with the Project Version to the left, the Task Version to the right, and between them a Merged Version of the concept needing review for merge resolution.
Pick one of the three versions by pressing the small purple Accept This Version icon button in its concept header action icons menu.
A "Saving accepted merged concept..." header notification is presented and the version being saved is greyed out.
An "Accepting merged version for concept <SCTID>" header notification is presented.
On merge completion, a "Merge accepted for concept <SCTID>" header notification is presented, the display panel is cleared, the concept FSN is removed from the Merges To Review list, and it is added to the Merges Accepted list in the context tab navigation panel.
Repeat the concept merge resolution steps for every concept in the Merges To Review list, until the list is empty.
On accepting the final concept merge, the context tab navigation switches to the Merges Accepted list, and a Finalize Merges action button is presented below the list of accepted concepts.
At this stage the Merges To Review list is empty (although still available as a context panel tab).
Press Finalize Merges to complete the rebase concept merges process and persist the changes in the task branch content.
An "Applying merged changes..." header notification is presented whilst all the accepted merge changes are saved to the task branch content.
Once the merges are completed, the main display panel changes to show a green a green "Success! Resolved merges applied. Switching to task view in five seconds..." full display panel notice, which closes automatically after five seconds have elapsed (during which the merges are finalized in the task branch content).
The Task View is reloaded, with the LH menu panel Pull new changes from project (rebase task) button now disabled (greyed out).
Any concepts loaded into the edit panel which were updated during the merge process now show the newly merged version of their content.
The Dashboard - My Tasks view REBASE column icon for this task will also now be inactive.
At this point the task branch status has been returned to Forward, and changes made within the task are once again eligible for promotion to the project.
Task rebase eligibility is indicated in two places:
In the Dashboard - My Tasks entry, as an active (yellow) Rebase this task from project icon button in its task row.
In an open task, as an active (yellow) Pull new changes from project icon button in the LH action button panel of the Edit Task view.
Either
From Dashboard - My Tasks, press the Rebase this task from project icon button in the task row REBASE column.
Or
From the Edit Task view, press the Pull new changes from project icon button in the LH action button panel.
A "Loading task details..." header notification is presented and the main display panel is cleared.
Task divergence and rebasing
A task becomes diverged from its project when the project content gets updated after content has been modified within the task.<>br />
This may happen through other tasks being promoted to the project, and also through project rebase from its mainline.<>br />
A task may also fall behind its parent branch, when the parent content changes before any changes are made to content within the task.<>br />
This may happen when a task is created but no changes are made within it or some time whilst other changes occur in project content for instance via a subsequent project level rebase, and/or another task being promoted to the project.<>br />
When either of these situations occur the task becomes eligible for rebasing from the project, to synchronize its content with the parent branch changes since the task was created.
Diverged tasks cannot be promoted
Task promotion is not possible whilst a task is diverged, so periodic rebasing is an important aspect of project and task management - ideally as soon as possible following divergence (fewer differences make for simpler content merges).
Attempting to promote a task which is diverged (indicated by an active rebase action button for that task) will trigger a _Promote Task_ pop-up notification that the task and project are not synchronized. The only available action on that notification is to return to the task - the promotion request is blocked.
A "Task details loaded" header notification is presented, and the main display panel changes to show a blue "Comparing task to project, please wait just a moment..." full display panel notice (with an animated timer indication that the comparison process is taking place).
Select a template from the drop-down selection box.
The selected full template name is placed into the query box and a search commences for matching concepts.
The phrase "Searching..." shows in the results panel until results are available.
When matches are found the search results list all concepts that match the selected template, with the default options of:
Stated view
All definition statuses ( Primitive and Fully defined )
Logical model matches
The default Template search finds matches in the Stated view, however this can be switched to Inferred view matches using the drop-down view mode selector.
The Def. (definition status) results filter option defaults to All ( Primitive and Fully Defined ) but also allows Primitive only and Fully Defined only matches to be listed in the search results.
A third results filter supports matching different aspects of the concept modelling defined by the selected template:
Logical (default) - concepts which match the logical model regardless of their lexical content.
Logical and Lexical - concepts which match both the logical and lexical models.
Logical not Lexical - concepts with the same logical model but which do not conform to the lexical model.
/ul>



The Promote concept pop-up dialogue box is then presented, with the concept SCTID and FSN noted in the dialogue header, and a notification that dependencies are being checked against this concept.There are two possible check outcomes:
No dependencies found
Dependencies are found
If no dependencies are found, the Promote concept notification box is updated accordingly, and option buttons to Cancel or Continue are presented.
Press Cancel to return to concept editing without requesting promotion.
Press Continue to make the promotion request.
If dependencies are found, a tabulated list of the dependencies are shown in the dialogue box, followed by option buttons to Cancel, Continue without Dependencies, or Continue with Dependencies are presented.
Press Cancel to return to concept editing without requesting promotion.
Press Continue without Dependencies to make the promotion request for just the request concept itself.
Press Continue with Dependencies to make the promotion request including all the listed dependency concepts as well as the request concept.
The form processing triggers a new content request in the International CRS platform, with a related AP header notification.
Following creation of a linked International CRS request, the AP header notification is updated to include the CRS ticket reference.
A CRS Request section with the reference link is added to the Task Details (the CRS ticket number is the link text).
Follow the link to open the International CRS request ticket.
International CRS access
The CRS link expects the requisite group memberships are already granted to the AP Author's account for the International CRS platform to view the linked CRS request details.
Additional permissions may need to be requested via Technical Support if this is not the case.
At this point the promotion request is completed in the Authoring Platform, and fulfilment of the request moves to the International CRS platform process flow.
The linked CRS ticket includes the extension promotion request concept details.
If Continue with Dependencies was followed, the linked CRS ticket includes the extension promotion request concept and its dependencies details.
Published unedited concepts only
The Request Promotion option only appears if the concept has been published in an extension release.
Previously published concepts modified in the extension since publication cannot be promoted to the International Edition until after re-publication in the extension.
Pressing Request Promotion on a previously published concept that has subsequently been changed but not yet re-published will present an error notification in the concept header, with the related change(s) highlighted in the editing panel:
If this concept needs to be promoted to the International Edition before the next local extension release, the concept can be reverted to its published version to allow the promotion request to proceed.
Of course any local extension changes made since publication are then discarded, so that may have to be considered when the International CRS promotion request is reviewed.


Working with Template search results
Template search results are formatted and presented in the same way as text search and ECL search results.
See Work with large search results sets and Act on search results for more information.













Stated dependencies only
Listed dependencies in the promotion popover dialogue are Stated only (not Inferred).










Silent merging
Although this sequence indicates content can be automatically merged without user intervention, any differences are still saved in the task branch to bring it back in synchronization with the project content.
This path simply means that none of the content changes in the project since the task was first created are in conflict with the changes made in the task since then.
All subsequent concept changes at the project level that were not directly related to the concepts being changed within the task become available within the task after rebasing.
Silent merging also occurs for changes within a concept being modified within the task if the changes do not conflict - for instance new descriptions may be added that were brought into the project concept version from another task or from the project's mainline.
Saving a merged concept is usually very rapid
These two stages usually happen quickly, so these header notifications may be very brief!




















EITHER In the My Tasks view, press the name link on the task you want to open. This opens the Task View to the context of the default Task Editing layout.
The Task View is presented with the default Task Editing layout, showing 4 key content regions below the site header:
Edit panel, showing concepts loaded or created within the task (initially empty for a new task).
Concept Model panel, showing a SNOMED CT schematic representation (in SNOMED CT Diagramming Guideline notation) of concepts in the Edit panel (initially empty for a new task).
Activities (Left Sidebar) panel, containing tabs for:
Taxonomy
Search
Saved List
Feedback
Create Batch
Task Details
Options menu panel, containing buttons for:
Create new concept
Create new concept from template
Task Classification
Task Validation
Task Rebase
Show Task Editing layout
Hide the Left Sidebar
Hide all concept models
On opening the task, any concepts previously loaded into the editor will be reloaded to restore the editing context from your most recent task editing session (the task state is automatically saved and restored by the application). After completing loading, a blue header notification will state "All concepts loaded" for a brief interval (or until you press the X in the upper right corner of the notification box).
OR In the My Tasks view, press the classification status icon (if present), on the task you want to open. This opens the Task View to the context of the current Classification report.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
The Task Classification layout is presented, showing the latest Classification report. This is a full-width layout, maintaining the Options panel menu for navigation back to other task contexts.
OR In the My Tasks view, press the validation status icon (if present), on the task you want to open. This opens the Task View to the context of the current Validation report.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded".
The Task Validation layout is presented, showing the latest Validation Report. This is a full-width layout, maintaining the Options panel menu for navigation back to other task contexts.
OR In the My Tasks view, press the feedback status icon (if present), on the task you want to open. This opens the Task View to the context of the Review and Feedback activity tab.
Whilst loading, the main content panel is cleared, and a blue header notification stating "Loading task details..." is presented. When completed, the header notification changes to "Task details loaded". ,p>
The Task Review and Feedback layout is presented, showing concepts to review, concepts approved, and inferred concept changes within the task. This layout maintains the Activities panel (Left Sidebar), as well as the Options panel menu for navigation back to other task contexts.













