Dezső
  • Version: Snow Owl v3.0.1
  • Start date: 11 November 2013
  • End date: 20 December 2013
  • Code name / adopted animal: Dezső, a walking stick at the Budapest Zoo

Local Code Systems, Mapping sets, and Value Domains

Update during Import

It’s now possible to update existing LCS, MS, and VD during import. The attributes of existing components are replaced by the imported ones. Please note, that the import only updates the unpublished content.

This overview compares the different import options:

  • Clear: Overwrites existing database with imported content. Existing content is removed.
  • Merge: Adds new content to the existing database. Existing content is not removed and not changed.
  • Replace: Updates existing content, adds new content. Existing content that is not part of the import is kept and not changed.

Replacing components during import

Local Code Systems

  • Properties: Properties of existing LCSs are updated. New LCSs are added. LCSs that are not not part of the import content will not be changed.
  • Codes: LCSs are updated by adding or removing codes. Properties of existing codes (e.g. alternative term) are updated.
  • Groups: If a group exists, it is updated by adding or removing keywords. New groups are added.

Value Domains

  • Properties: Properties of existing value domains are updated. New Value domains are added. VD that are not not part of the import content will not be changed.
  • Members: Existing VDs are updated by adding or removing members.
  • Groups: If a group exists, it is updated by adding or removing keywords. New groups are added.

Mapping sets

  • Properties: Properties of existing MS are updated. New MS are added. MS that are not not part of the import content will not be changed.
  • Mappings: Existing MSs are updated by adding or removing mappings.
  • Groups: If a group exists, it is updated by adding or removing keywords. New groups are added.

Additional advanced search options

Local Code Systems

New search criteria have been added to the Advanced Search for Local Code Systems. Check the box to specify the search for:

  • Code, Term, Alternative Term
  • Status: Active or inactive
  • Effective time: Use the calendar icon to specify a time range by entering start (left box) and end date (right box). If you enter a date only in the left box, the time range will extend from this date into the future. If you enter a date only in the right box, the time range will extend (from the past) up to this date. You can also search for unpublished Local Code Systems.

The search criteria can be combined by using

  • ANY: At least one criterion has to be met
  • ALL: All selected criteria have to be met

Advanced Search for Local Code Systems

Value Domains

New search criteria have been added to the Advanced Search for Value Domains. Check the box to specify the search for:

  • Name, Definition, Purpose, Version
  • Status: Active or inactive
  • Reason for inactivation
  • Effective time: Use the calendar icon to specify a time range by entering start (left box) and end date (right box). If you enter a date only in the left box, the time range will extend from this date into the future. If you enter a date only in the right box, the time range will extend (from the past) up to this date. You can also search for unpublished Value Domains.
  • Type: Intensional, extensional, expanded, grouping
  • Source, Source URI, Comments
  • Member term: Name of a value domain member
  • Member code: Exact code of a value domain member

The search criteria can be combined by using

  • ANY: At least one criterion has to be met
  • ALL: All selected criteria have to be met

Advanced Search for Value Domain

Mapping Sets

New search criteria have been added to the Advanced Search for Mapping Sets. Check the box to specify the search for:

  • Name, Definition, Purpose, Version
  • Status: Active or inactive
  • Reason for inactivation
  • Effective time: Use the calendar icon to specify a time range by entering start (left box) and end date (right box). If you enter a date only in the left box, the time range will extend from this date into the future. If you enter a date only in the right box, the time range will extend (from the past) up to this date. You can also search for unpublished Mapping Sets.
  • Source, Source URI, Comments
  • Member term: Name of source term, target term, or both
  • Member code: Source Code, target code, or both

The search criteria can be combined by using

  • ANY: At least one criterion has to be met
  • ALL: All selected criteria have to be met

Advanced Search for Mapping Sets

You can customize the advanced search by displaying only selected search tabs. Click on Customize.. in the buttom-right corner to bring up the selection page.

Customizing advanced search

Import validation

When importing mapping sets, value domains, or local code systems from an Excel file, Snow Owl automatically validates the import file. If there are any errors, a dialog will appear, which shows the affected sheets. Expand the nodes to get more information about the type and location of the error. Click OK to close the dialog. You need to fix the Excel sheet before you can run the import again.

Validation of a value domain import

Bookmarks

It’s now possible to bookmark Value Domains, Mapping sets, Local Code Systems and local codes by using the context menu in the navigator.

  • Go to the view, e.g. Mapping sets views. In the LCS view, you can bookmark Local Code Systems as well as local codes.
  • Right-click on the item you want to bookmark and select Add bookmark from the context menu.

Double-click a component in the Bookmarks view to open the editor.

Bookmarks view

Mapping set editor

The new default setting of the mapping set editor displays only the following columns on the mappings tab:

  • Source code system name: Refers to the terminology or local code system that was used as the map source.
  • Source code: The code used in the source terminology or local code system.
  • Source Term: The name of the source code.
  • Target code system name: Refers to the terminology or local code system that was used as the map target.
  • Target code: Code used in the target terminology or local code system.
  • Target Term: The name of the target code.

Mapping set editor, default setting

To display additional columns, go to the Preferences page File > Preferences > Snow Owl > Editor tables > Mapping set editor. You can also open the Preference page by right-clicking on a column header.

Deriving description and relationship reference sets from simple type reference set

You can now use an existing simple type reference set to create a new description or relationship reference set. There are three different options

  • Description: Creates a description based reference set from the reference set members. It contains all descriptions of the members in the original reference set.
  • Relationship: Creates a relationship based reference set from the reference set members. It contains all relationships that exist between the members of the original reference set. For example, if a parent concept and its child concept are both members of the original reference set, the derived reference set will contain a member for this relationship. This relationship will be comprised of two concepts, and the relationship type (is a).
  • Duo: Creates two reference sets, one description based, and one relationship based.

Right-click on the simple-type reference set that you want to use, and select Derive to simple type reference set from the context menu. Enter a name for the new reference set and select one of the options, hit Finish.

Deriving a description based reference set

You can open the new reference set from the reference set view. The screenshot below shows a reference set that was derived from the Cardiology reference set. The concept IDs of the referenced components are displayed.

Derived reference set showing relationships between members of Cardiology reference set

The screenshot below shows a reference set that contains all descriptions of the Cardiology reference set.

Derived reference set containing all descriptions of the Cardiology reference set members

The Duo reference sets have “descriptions” or “relationships” added to their name. They can also be distinguished by the icon decorators: A label represents a description based reference set, a tag a relationship based reference set.

Derived reference set duo

Exporting

Update on exporting map type reference sets to Excel

When exporting map type reference sets to Excel, it’s now possible to export the Map target ID, the status ID, and the Module label. Overall the following components can be exported:

  • Referenced component ID
  • Referenced component
  • Map target ID (if the map target is unspecified, this category is omitted)
  • Map target
  • Status code: Machine readable status (active = 0; inactive = 1)
  • Status label: Active, Inactive
  • Effective time
  • Module ID
  • Module label
  • Member ID: Unique identifier of the membership

Exporting map type reference set to Excel

Exporting description and relationship reference sets to Excel

Reference sets that are based on descriptions or relationships can now be exported as a delimiter separated text file.

  • Right-click on a reference set in the Reference Sets View and select Export reference set > Export reference set to Excel format from the context menu.
  • Use the Browse button to specify the file name and location. If the file already exists, you can choose to either overwrite it or append to it.
  • Target effective time: Specify a date for the export.
  • Hit Finish to start the export

Specifying file path and effective time

On the following page, you will be prompted to review all unpublished export components. Hit Next to proceed

Reviewing export components

A message will inform you about the processing time. Hit Yes to continue.

If you are doing a formal publication, you need to update the components to the date you set as target time. If you are exporting for internal use, you should not check the box. In this case the components in the export file will have an effective date, while the ones in Snow Owl remain unpublished.

Hyperlink to exported file

Click on the hyperlink to the exported file to see the file (see screenshot).

Exported relationship based reference set

Collaborative authoring

Modifications in the task editor

The user interface of the task editor has been modified to simplify collaborative work. Additional functions (e.g. batch review, link to artifact) were added to the task editor.

Toolbar

Task status: The toolbar displays the task number and the status. Use the drop-down menu, and save to change the status.

Link to artifact: A link in the toolbar now allows opening the artifact that you are working on directly from the toolbar. For example, if you are working on a reference set, click on the link to open the reference set editor. There is no link for General Authoring tasks.

It’s no longer necessary to submit changes manually, they are submitted automatically when saving. For this reason the submit button was removed from the UI.

Synchronize incoming changes. Updates the local copy of the task to reflect any changes on the server.

Activate: Click on the icon to activate/inactivate your task. A frame around the circle indicates that the task is activated (see screenshot).

Open with Web Browser: Displays the web interface for the task in an internal web browser.

Promote: Use this button to promote changes to the main repository. This button is only enabled if the task has been reviewed.

Task editor toolbar

Task page

The task page consists now of the following sections:

  • Summary: Displays the task name, task summary and task type (e.g. General authoring, reference set authoring)number, task status (e.g. NEW, ASSIGNED, VERIFIED), and when the task was opened and modified.
  • Comments: Use this section to add new comments about the task and view all previous comments. Comments you have read previously are folded. You can expand and re-read individual comments or click the “+” at the top right to expand all comments. The name of the person writing the comment will be displayed. This way, you can see which team member wrote a comment.
  • Assignees: Shows the team members that are involved in this task (e.g. Author, Reviewer). A green circle indicates the team member that is currently assigned to the task. To change the assigned person press Ctrl + Space to display the team members.
  • Attributes: Shows the task repository, and the product category. Read-only.
  • Attachments: Files can be attached here, for more information see Attachments section

Task editor

Review page

The context page was renamed to “Review page”.

Review page for reference set authoring

Batch review

The reviewer can now accept or deny all members of a value domain, reference set, mapping set, map type reference set by using the buttons in the toolbar of the task editor.

  • : Accept all members
  • : Deny all members
  • : Accept all members from author 1 (dual blind authoring)
  • : Accept all members from author 2 (dual blind authoring)

To accept or deny a single item, click on the respective cell in the table.

Review page for reference set authoring

Restricting import to administrator

Import is now restricted to the administrator. The import can only be done from MAIN through the UI. If the assigned role is Editor, Browser, or Reviewer, it is not possible anymore to import. The import restrictions apply to all import content (all terminologies and classification systems, value domains, mapping sets, local code systems).