When you add rules to a compliance map, first copy the compliance map to an alternate location to retain the original map’s integrity. Once you add your business rules to the expanded map and regenerate it, your edited map is ready for use with the associated trading partners.
This section describes copying the map and modifying it with your own business logic.
Refer to the ECMap User’s Guide for detailed information on window entries, menu choices, and the detailed map modification process.
Although ECMap lets customers create rules with any rule number, Sybase allocates a range of numbers for customer use: 25000 to 32767. Confining customer-specific logic to a range lets customers easily identify which rules Sybase created and which rules they created.
Although the program allows you to create rules using
numbers under 25000, there is no guarantee that Sybase will not
overwrite the rule number on a subsequent release. To preserve the
rules you create, use the Sybase-supplied range.
Copying a map
In ECMap’s main menu, select Utilities > Copy Map. The Copy Map window displays.
On the Copy Map window, the program populates the Map Name and Project Name text boxes with the names of the currently selected map and the project in which it is stored.
You can accept the project and map names entered by the program, or you can change them.
To accept the current settings, click Run.
To change the project and its associated map, do the following:
Click the Project Name arrow. The Select Project and Map window displays.
Double-click the appropriate project and its associated map. The Select Project and Map window closes and populates the Project Name and Map Name text boxes in the Copy Map window.
In the Trade Partner Option group, choose one of the following:
Click Include Trade Partner Tables to copy all map-related files and databases, including trading partner tables (tp, tradstat, and wixset).
Click Exclude Trade Partner Tables to copy map-related files and databases, excluding trading partner tables.
You usually include the trading partner tables when you copy a map, but you may want to exclude them for various reasons. For example, if you are copying a map to use in a different project, that project might use an entirely different set of trading partner tables.
Choose the appropriate option in the Map Copy Direction group. Additional text boxes let you specify where you want the copy to reside.
Choose this option |
To do this |
|---|---|
This Map to Map |
Copy the properties of this map to another map. In the Copy Map To group, click the Browse button next to the Map Name box, choose the appropriate Project Name and Map Name from the dialog box. |
This Map from Map |
Move the properties of another map into this map. In the Copy Map From group, click the Browse button next to the Map Name box, choose the appropriate Project Name and Map Name from the dialog box. |
This Map to Directory |
Copy this map to a new directory. In the Copy Map To box, click the Browse button, then choose the destination directory. |
This Map from Directory |
Moves the properties of a map in another directory into this map. In the Copy Map From box, click the browse button, then choose the directory where the map resides. If you want to define a new map based on the copy, click Create This Map Definition from Directory Copy. |
Confirming the copy command
Now that you have set all the options, you are ready to create the copy of your map.
Click Run. The program displays a confirmation dialog box that restates the details of the copy map option you have chosen.
The program asks for your confirmation before the map is actually copied.
If you do not want to proceed or you want to change something, click No to return to the Copy Map window.
If you want to copy the map, click Yes. The map is copied and you return to the main ECMap window.
Viewing the copy map log
If you want to see a listing of the actions that took place during the copy process, click View Log. The View Log window displays.
The information on this window lists each of the databases that were copied. If any problems were encountered, it issues warnings and errors. You should look at all warnings, but they do not necessarily prevent the copied map from running correctly. You must look at errors since they indicate a condition that would prevent the map from running.
Modifying and regenerating
the map
Make you sure you are working in a copy of the map and not the original when adding additional business edits to the compliance map.
Modify your map to add additional logic or data validation that reflects your particular business environment.
When you regenerate and run your modified compliance map, ECMap not only checks for HIPAA compliance but performs the added data checks. Refer to the ECMap User’s Guide for instructions on modifying your map, using features such as conditional logic, cross-reference tables, and rules.
Select Utilities > Generate Compliance Map. The Generate Compliance Map window displays.
Click Generate Error for Ignored Elements with Data.
Click Run.
Click No on the Generate dialog box so that your changes are included in the map file.
Associating cross-reference tables with maps
If errors occur during the generation of the map that indicate that cross-reference tables do not exist, you need to associate the tables with the compliance map elements.
In ECMap’s main window, select Tools > Cross Reference Tables. The Cross Reference Tables window displays a list of all currently used cross-reference tables.
Select Files > Directory Scan from the menu.
Any cross-reference tables that are not used in the map are displayed in the Cross Reference Directory Tables window.
Select all the tables in the Cross Reference Directory Tables window and click OK.
The tables are added to the list in the Cross Reference Tables window.
Regenerate the map.
