To ensure that you stay on target for a successful deployment, use a structured approach for your implementation methodology. You will need to prepare for your implementation and determine key aspects of the design that will affect the behavior of your application. Defining requirements for an implementation includes these tasks:

• Reviewing extension requirements
• Refining customizations and determining the availability of required data and integrations
• Prioritizing, for example, revising the solution backlog, re-estimating effort for extensions and customizations, and confirming the project scope

Defining your requirements also involves DCO sessions and incorporating those requirements into the application design. During these sessions, you review each of the case types and process flows that the application already provides.

Update the Application Specifications with planned changes as described in the Pega Platform help topic Application Specifications.

Follow these steps to define requirements:

• Step 1: Defining the case type modifications and attributes
• Step 2: Defining the data model
• Step 3: Mapping the application data
• Step 4: Defining common codes management requirements
• Step 5: Defining code set Elastic search requirements
• Step 6: Defining code group requirements
• Step 7: Defining integration
• Step 8: Defining member PII data masking requirements
• Step 9: General Data Protection Regulation (GDPR) support
• Step 10: Defining member PII by enabling HIPAA
• Step 11: Implementing Elastic search on HIPAA security policy
• Step 12: Enabling Elastic search
• Step 13: Defining the security model and organization structure
• Step 14: Customizing the user experience
• Step 15: Defining reporting requirements