{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":13401,"path":"employee-service-management/validate-vaccine-responses-automatically.md","title":"Validate vaccine responses automatically","bundle":null,"doc_type":null,"release":"australia","body":"\n# Validate vaccine responses automatically\n\nConfigure Vaccination Status so that validator services can validate vaccine responses automatically with information from supported attachments.\n\n## Before you begin\n\nIntegrate with the validator service by doing the following:\n\n- Obtain credentials for a validator service.\n- Create a connection and credentials alias. For more information, see [Create a Connection and Credential alias](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/connection-alias.md).\n\nIf your organization is using an integration that is already supported, such as the CommonTrust Network, then you need only to add your organization's credentials to the validator service record.\n\nRole required: admin\n\n## Procedure\n\n1. Configure the validator service.\n\n 1. Navigate to **Vaccination Status** > **Validator services**.\n\n 2. Select an existing validator service or, if you are creating a new one, click **New**.\n\n If you are selecting an integration that is already supported, such as the CommonTrust Network, you must enter your Connection alias and confirm the form is correct for your validator service.\n\n 3. Fill in the fields on the form.\n\n\n
\n\nField\n\n\n\nAction\n\n
\n\nName\n\n\n\nThe name of the validator service.\n\n
\n\nConnection alias\n\n\n\nThe connection alias for your validator service. For more information on creating a connection alias, see [Create a Connection and Credential alias](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/connection-alias.md).\n\n
\n\nValidation subflow\n\n\n\nThe subflow used to confirm whether a submitted attachment is valid. A template flow is provided by default or you may create a flow and add it to this field. For more information on creating flows, see [Create a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/create-flow.md).If you create your own subflow, it must have the same inputs and outputs as the template subflow.\n\n
\n\nInitial validator state\n\n\n\nThe initial state the validator service starts in prior to the completion of the review, such as **Ready**. The recommended state is **Ready** unless there is a preprocessing step.**Note:** If the initial state is **Preprocessing**, then the redirect page must set the response record validator state to **Ready** so it works with the built-in validation flow.\n\n
\n\nRedirect page\n\n\n\n\\(Optional\\) A reference to a service portal page the user will be redirected to after they report their vaccination.\n\n
\n\nActive\n\n\n\nOption to activate the service.\n\n
\n\nDomain\n\n\n\nThe domain required for the validator service, such as **global**.\n\n
4. Click **Submit**.\n\n2. Configure a vaccine code system used to read vaccine codes and validate submitted data.\n\n The vaccine code your system uses might be provided with Vaccination Status. Refer to your validator service's requirements for more information.\n\n 1. Navigate to **Vaccination Status** > **Vaccine code systems**.\n\n 2. Select **New**.\n\n 3. Enter the name of the vaccine code system.\n\n 4. Enter the URL for the vaccine code system.\n\n 5. Select **Submit**.\n\n3. Configure the vaccine response attachment type supported by the validator service.\n\n This attachment type users should use when they submit their vaccine responses.\n\n 1. Navigate to **Vaccination Status** > **Attachment types**.\n\n 2. Select **New**.\n\n 3. Enter the name of the attachment type.\n\n 4. Enter the name of the validator service.\n\n 5. Enable the attachment type by selecting the **Active** check box.\n\n 6. Set the domain to **global**.\n\n 7. Select **Submit**.\n\n4. Add common vaccine codes required by the vaccine code system and service.\n\n Common codes are provided with Vaccination Status. Refer to [COVID-19 Vaccine Related Codes](https://www.cdc.gov/vaccines/programs/iis/COVID-19-related-codes.html) for additional common codes and the third-party service for codes their system supports.\n\n 1. **Vaccination Status** > **Vaccine codes**.\n\n 2. Select **New**.\n\n 3. In the **Code System** field, add the corresponding system.\n\n 4. In the **Code** field, enter the code used to identify information about the vaccine.\n\n 5. Enter a description.\n\n 6. Select **Submit**.\n\n5. Activate the Auto-validate vaccine response flow.\n\n 1. Navigate to **Process Automation** > **Flow Designer**.\n\n 2. Search for the Auto-validate vaccine response flow.\n\n 3. Select the flow.\n\n 4. Select **Activate**.\n\n\n## Result\n\nYou have enabled automated vaccine response validation. Work notes in the vaccine response record are updated with information on whether the attachments, and therefore the response, are valid. You can use this information to manually review vaccine responses in the approval portal.\n\n## What to do next\n\nTo automate vaccine response reviews so that they are set to **Approved** if validation was successful or left in the state **Not yet reviewed** \\(a manual review is required\\), see [Automate reviews of vaccine responses](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/enable-automated-vaccine-response-reviews.md).\n\n**Parent Topic:**[Automating vaccine response reviews](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/vaccination-status-vaccine-validation.md)\n\n"}}