{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":19566,"path":"healthcare-life-sciences/pss-ext-point-enrollment-form.md","title":"Configure the submission flow of the enrollment request form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure the submission flow of the enrollment request form\n\nUse scripted extension points to decide what records are created or updated after an enrollment request form is submitted.\n\n## Before you begin\n\n**Important:**\n\nStarting with the Yokohama release, Patient Support Services is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.\n\nFor details, see the [Deprecation Process \\[KB0867184\\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support knowledge base.\n\nSet the application scope to Patient Support Services using the application picker. For more information, see Application picker.\n\nRole required: admin\n\n## About this task\n\nThe Patient Support Services application installs the `sn_patientservice.EnrollmentCaseUtilService` script, the `EnrollmentCaseUtilService` script include, and the `EnrollmentCaseServiceExtPoint` extension point.\n\nThe sn\\_patientservice.EnrollmentCaseUtilService script is preconfigured for the enrollment request form available by default within the application. Before creating an enrollment case, the application runs the sn\\_patientservice.EnrollmentCaseUtilService script and uses the following submission workflow logic to create records and avoid duplication of records:\n\n1.  Create a patient record if one doesn't exist.\n2.  Create a consumer record if one doesn't exist.\n3.  Create a practitioner record if one doesn't exist.\n4.  Create a member plan if one doesn't exist.\n\nUsing extension points makes it easier to integrate customizations without actually altering the base code. You can extend standard base functionality using customized scripts. For more information, see Using extension points to extend application functionality.\n\nAn implementation is available in the base system for scripted extension points. You can modify the data and add additional fields.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **System Extension Points** &gt; **Scripted Extension Points**.\n\n2.  In the **API Name** column, search for and click **sn\\_patientservice.EnrollmentCaseServiceExtPoint**.\n\n3.  On the Extension Point form, select a script include to use the `EnrollmentCaseServiceExtPoint` extension point.\n\n    -   Modify the existing script by going to the Implementations related list and clicking **sn\\_patientservice.EnrollmentCaseServiceExtPoint**.\n    -   Create and register a custom script include.\n4.  Customize the submission workflow logic of your enrollment form by adding the `createPatient`, `createMemberPlan`, and `createPractitioner` methods to your script include that implements the `EnrollmentCaseServiceExtPoint` extension point.\n\n    You can create multiple implementations for an extension point and provide an order number for each implementation. The implementation that has the lowest order number is executed first.\n\n<table id=\"table_fkq_ww3_jtb\"><thead><tr><th>\n\nCustomization\n\n</th><th>\n\nImplementation\n\n</th></tr></thead><tbody><tr><td>\n\nCreate a patient record if none exist.\n\n</td><td>\n\nInclude the `createPatient` method of the `EnrollmentCaseServiceExtPoint` extension point in the implementation.\n\n</td></tr><tr><td>\n\nCreate a member plan if none exist.\n\n</td><td>\n\nInclude the `createPatient` method of the `EnrollmentCaseServiceExtPoint` extension point in the implementation.\n\n</td></tr><tr><td>\n\nCreate a practitioner record if none exist.\n\n</td><td>\n\nInclude the `createPatient` method of the `EnrollmentCaseServiceExtPoint` extension point in the implementation.\n\n</td></tr></tbody>\n</table>5.  On the Extension Point form, click **Update**.\n\n\n"}}