This chapter discusses the additional steps needed to add ASTM routing interfaces to a production.
Be sure to perform these tasks in the same namespace that contains your production. When you create rule sets, transformations, and search tables, do not use reserved package names; see “Reserved Package Names” in Developing Productions.
Loading ASTM Schemas into InterSystems Products
For information on creating custom schema categories, see “Creating Custom Schema Categories” in Using Virtual Documents in Productions.
Defining Routing Rule Sets for ASTM
Depending on the business process that you create, you may need to create a routing rule set.
For general information on defining business rules, see Developing Business Rules.
When you create a routing rule set for an ASTM routing interface:
On the general tab, Rule Type should be Virtual Document Message Routing Rule. This choice sets the following options:
Rule Assist Class should be EnsLib.MsgRouter.VDocRuleAssistOpens in a new window
Context Class should be EnsLib.MsgRouter.VDocRouting Engine
In the constraint for a rule, specify Message Class as EnsLib.EDI.ASTM.DocumentOpens in a new window.
Defining DTL Data Transformations for ASTM
Your routing rules might need one or more data transformations.
For general information on defining DTL data transformations, see Developing DTL Transformations.
When you create a DTL data transformation for ASTM documents:
On the Transform tab, Source Class and Target Class should both be EnsLib.EDI.ASTM.DocumentOpens in a new window.
Source Doc Type should match the schema category name assigned by the business service.
Target Doc Type should be the name of the target schema category. This must match a schema category name that you have loaded into the InterSystems product.
To integrate the DTL data transformation in the production, enter its full package and class name in the Transform field of a routing rule set.
Defining ASTM Search Tables
The ASTM search table class, EnsLib.EDI.ASTM.SearchTableOpens in a new window, automatically indexes the ASTM document ID, which it gives the name Identifier.
If you need more items to search, you can create a subclass. The subclass inherits the Identifier property, plus the infrastructure that makes search tables work. For details, see “Defining a Search Table Class” in Using Virtual Documents in Productions.
For ASTM, InterSystems products support an additional value for PropType. You can use DateTime:HL7 in addition to the types listed in Using Virtual Documents in Productions.