This section contains recommendations on how best to use these features to facilitate upgrading HIPAA compliance maps from one release to the next.
To let customers modify compliance maps to meet their specific business requirements, Sybase HIPAA Accelerator includes compliance maps with source code. Previously, when you upgraded your version of Sybase HIPAA Accelerator, you had to merge your business-specific edits into the new map or maps manually.
This section describes development conventions for Sybase HIPAA Accelerator administrators who modify compliance maps.
When upgrading maps, there are three cases that Sybase HIPAA Accelerator administrators may need to address: Adding to a rule, replacing or deleting a rule, and deleting a command. The following procedures describe these cases.
Adding to a rule or command
Select the rule and the location within the rule where the additional logic is required.
At the selected location, insert a Perform Rule command or an IF …THEN command that calls a new rule from the customer-reserved region, which contains the new logic.
Replacing or deleting rules
Write the new replacement rule in the customer-reserved region.
Modify every Perform Rule command in the map that calls the rule to be replaced to call the new rule instead.
Deleting commands
Identify the command that needs to be deleted.
Depending on which EDI version you are running, perform one of the following steps:
Disable the command if you are working with EDI 4.x
Delete the command if you are working with EDI 2.9
In each case, carefully document all modifications as well as the locations of the modifications. This includes, as stated previously, new rules or commands and deleted rules or commands. When merging the changes from one version of Sybase HIPAA Accelerator to the next, refer to your documentation.
For more detailed information on working with rules, see the ECMap User’s Guide.
