Assumptions
Before this document was created, the following assumptions were made:
- The user is familiar with the Argus application and Database.
- The environment is a working Argus Environment with ESM module enabled.
- The user has access to the ESM Owner schema to execute some of the scripts and to verify the mapping queries.
- It is possible to provide required access to all the database objects created for the extended or customized mapping.
- The user is proficient in PL/SQL.
- The common code list used by R2 and R3 is synchronized with flex bucketing.
Specific to (R2)
- (If R2 profiles contain extension elements) The DTD path or reference is synchronized with the partner where the file is consumed.
- The user is proficient in XML and familiar with DTD.
Specific (R3)
- The user is proficient in XML, XSLT and HL7.
- (If changes are expected to HL7) The user is familiar with the expected output of the final HL7report.
- All the customization and extension done in the profile will be validated.
Note:
The person extending the ICSR profile will manage all the technical aspects and will validate the extensions and customizations before applying them into the system.Parent topic: Overview