Creating a Map

Creating a map simply requires selecting a source catalog and a target catalog (terminologies) that are in the same domain. Additional settings define user privileges, referential information, workflow tools, etc. See the following topics for steps on creating maps and setting map properties.

• Creating a New Map

• Versioning a Map

• Deleting a Map

• Setting Up Content Security

• Setting Up Map Runtime

Creating a New Map

Follow these steps to create a new map. The example below creates a map that associates local drug terms to standard RxNorm terms. The example below illustrate values set for a map associating a local catalog of dispensable drugs to the standard RxNorm terminology.

1. Click within the Waypoint dashboard. See the Waypoint Dashboard topic for a detailed view of the window.

2. In Create New Map, select a mapping template based on the type of data contained within the source and target catalog you intend to use. See the Map Properties topic for a detailed view of the window.

   

3. Select the terms to be mapped by assigning a source catalog and a target catalog. When assigning catalogs, ensure your target catalog contains the terms that meet your terminology criteria, such as using a catalog containing ICD-CM-10 codes for billing purposes.

   

   Please Note: Map template and catalog associations are defined in Symedical. If your desired catalogs do not appear within the Mapping From Source Catalog or the To Target Catalog menus, ensure your mapping template is correct.

4. For referential purposes, define the following properties:

   • Map Name — A custom name for the map or click to regenerate a name based on the source catalog name and the target catalog name.

   • Additional Description — Information that further defines the use or intent of the map.

   • Mnemonic — A unique map identifier for the map in the Symedical runtime services.

   • Version — An identifier for the variant of the map.

   • Status (Required) — Indicates whether the map is active, retired, or a work-in-progress.

   • Owner (Required) — The person creating or managing the map.

   

5. Set content security to implement map accessibility validations. See the Setting Up Content Security procedure for more information.

   

6. Select a flag set to represent mapping workflow statuses or notifications. The options provided here are defined within Symedical. The default Clinical Architecture notifications are as follows:

   • Review (Immediate)

   • Review (1-2 days)

   • Review (1-5 days)

   • Verify

   

7. To utilize target term relationships for determining mapping results, select Show Hierarchy Browse and then select a content model. Once selected, a hierarchical view of the content model is displayed within the Hierarchical Browse tab in Symedical. Waypoint does not display this tab.

   

8. Set the Use in Runtime option to enable the Symedical runtime services and define mode options.

   Please Note: You must also complete the Mnemonic and Originating Site fields to enable Symedical runtime services.

   

   See the Setting Up Map Runtime procedure for instructions.

9. If your target catalog contains alias values that you would prefer to use in the runtime over the term descriptions, select an alias from the Publish Target Alias drop-down menu. When determining the alias value to use, the publish looks for the following:

   • If the Preferred alias purpose is selected, the publish first looks for the local preferred value for the same language. If no value exists, the publish looks for the preferred value, and then if no value exists, the term original is used.

   • For any other alias purpose, the publish first looks for that specified purpose/language value. If no value exists, the term original is used.

   This option is only available for Symedical runtime-enabled maps.

10. Click OK to view the new map in the map dashboard.

Versioning a Map

Follow these steps to version or speed up the process of creating a map by duplicating the definition of an existing one. A map consists of a source and target catalog. When duplicating, the catalogs of the original map are assigned to the new map and cannot be changed. However, the remaining catalog properties can be modified. The example below provides a use case of versioning a map in order to test some changes before implementing it.

1. Click within the Waypoint dashboard to open Duplicate Map. See the Waypoint Dashboard topic for a detailed view of the window.

   

2. Enter the following map properties values. These are required.

   • Name — The map name.

   • Version — An identifier for the variant of the map.

   • Mnemonic — The map’s unique identifier for Symedical runtime.

   • Additional Description — Information that further defines the new version and/or the intent of the map.

3. Clear the Include Term Mappings check box to version the map using only the original map’s catalogs and settings. Select this option to include the mappings contained in the original map.

4. Click OK to retain settings and view the new map in Map Manager. See the Map Manager topic for a detailed view of the window.

5. In Map Manager,click the Map menu and then click Properties. See the Map Properties topic for a detailed view of the window.

   

6. Change the Status of the map to Work in Progress to reflect its work state. See the Map Properties topic for a detailed view of the window.

7. Click OK to return to Map Manager.

8. If you close Map Manager and the map does not appear in the Waypoint dashboard, click to update the grid. Identify your new map through the version number and additional description value.

   

9. Once all changes are made, activate the new map and retire the v1.0 map by opening each map and following steps #5 and #6.

Deleting a Map

Follow these steps to permanently remove the map from Waypoint and Symedical. Maps cannot be deleted when they are:

• Checked out in Symedical.

• Assigned as the target map or the reference map of an algorithm.

• Used by site channels.

The example below illustrates deleting a map that was created to test some changes before implementation.

1. In the Waypoint dashboard, search for and then select the map you wish to delete.

   

2. Click to delete the map.

3. Click Yes in the Confirm Map Delete dialog that appears.

   

Setting Up Content Security

Follow these steps to define access to a map based on user privileges set within Symedical. The example below illustrates setting the content security to the organization level where CA represents the administrative privilege and Clinical Architecture represents the editor privilege.

1. Open Create a New Map, by doing one of the following in the Waypoint dashboard:

   • Click when creating a new map.

   • Double-click to open an existing map from the grid.

   See the Waypoint Dashboard topic for a detailed view of the window.

2. In Create New Map, select Content Security Enabled to activate the security level options.

   

   See the Map Properties topic for a detailed view of the window.

3. Define permissions while keeping the following in mind:

   • Namespace — The highest security level by including organizations and sites. Select a namespace without selecting an organization or site to permit access to users assigned this level of security.

   • Organization — A middle security level, including sites. Select an organization without selecting a site to permit access at this level.

   • Site — The lowest security level. Select a site to permit access at this level.

   • Originating Site — A map location that is used in Symedical runtime services to set up runtime channels for transcoding.

   When assigning security levels, a site must have a defined organization and an organization must have a defined namespace. Once assigned, the content appears in User Content Security to grant or deny privileges for a specific user.

   Please Note: When user content security is enabled at the site level, users are only allowed to edit and view information for those sites.

   To quickly assign the source or target catalog’s content security settings to the map, click Copy Source or Copy Target.

4. Click OK to retain settings and return to Map Manager. If creating a new map, remain in the form and see the Creating a New Map procedure for additional property information.

Setting Up Map Runtime

Follow these steps to define the mapping capabilities provided through the Symedical runtime services. The steps below illustrate setting up the runtime to automate catalog population and mappings using the Symedical runtime services for transcoding.

1. Open Create a New Map, by doing one of the following within the Waypoint dashboard:

   • Click when creating a new map.

   • Double-click a selection within the grid when opening an existing map.

   See the Waypoint Dashboard and Map Properties topics for a detailed view of the windows.

2. Ensure the map is assigned a mnemonic. This unique identifier is required for identifying the map in the Symedical runtime services.

   

3. Select Use in Runtime to allow the map to be published to the Symedical runtime services. If you wish to modify the map within the services, select from these runtime mode options:

   • Add New Terms to Source Catalog — Allows Symedical runtime services to add terms to the source catalog.

   • Attempt to Auto-Map New Terms — Allows Symedical runtime services to add terms to the source catalog and attempt to map terms. When enabled, Symedical automatically generates candidates every 60 seconds for map terms that are transcoded as unmapped and do not already have candidates. This process is implemented within the Background Windows Service configuration file by enabling the “recognize” mode. Additionally, the default processing interval of 60 seconds is also maintained in this file and can be modified, if desired.

   • Enable Quick Map Agent — Enables manual mapping through email. During processing, whenever multiple candidates are returned by the “map” algorithms, an email is sent to the map owner listing the returned candidates. Selecting a candidate maps those terms automatically within Symedical during runtime processing.

     Please Note: This feature only applies to maps processed through Symedical runtime services with the Attempt to Auto-Map New Terms runtime mode option selected. It does not apply to bulk processing.

Please Note: If Use in Runtime is the only option selected, Symedical runtime services are used but they do not modify the map.



4. Select Log Source Term Differences to allow the Symedical runtime services to compare incoming source term values (description, attributes, and external codes) to the published source term values and log differences within the Anomaly Manager in Symedical.

   

5. Select Publish Target Attributes to publish the target catalog’s term attributes.

   Please Note: Attributes can only be defined for a catalog in Symedical.

   

6. Select Publish Target Alias to publish an alias from the map’s target catalog to use its values for target term descriptions when publishing to Symedical runtime services for transcoding. Only target aliases that do not allow multiples can be published. When determining the alias value to use, the publish looks for the following:

   • If the Preferred alias purpose is selected, the publish first looks for the local preferred value for the same language. If no value exists, the publish looks for the preferred value; then if no value exists, the term original is used.

   • For any other alias purpose, the publish first looks for that specified purpose/language value. If no value exists, the term original is used.

   

7. Originating Site — Click to select a location for the map. This value is used in Symedical runtime services to configure environments and set up runtime channels for transcoding.

   

8. Click OK to retain settings and return to Map Manager. If creating a new map, remain in the form and see the Creating a New Map procedure for additional information.