# Validate your development

Now that your development is done, let’s confirm you’re ready to onboard successfully. Complete this checklist to make sure you’re ready:

- You have a strategy for handling any identifiers (e.g., patient, visit, order) and mappings.
- You have a strategy for managing source, destination, and API key identifiers for your connection’s systems.
- You can construct and send any scoped data models or FHIR resources you plan to send to your connection’s system.

> **FHIR validator**
>
> FHIR can be complicated. [Learn about validating FHIR resources](https://www.hl7.org/fhir/validation.html), which contains useful information from HL7. You can also [check out the official HL7 FHIR web validator tool](https://validator.fhir.org/) or [review other profile tooling](https://confluence.hl7.org/display/FHIR/Profile+Tooling). Using tools like these to validate your FHIR workflows may help you catch discrepancies with the structure of your FHIR messages early on. 
>
> _Tip_: If you use the HL7 FHIR validator, make sure to remove the Redox-specified `Meta` object, if you have it in your FHIR bundles. 
>
> For other high-level tips or reminders, make sure to always include the `Bundle.entry.fullUrl` and correctly reference other resources within the bundle. [Review recommendations for handling FHIR identifiers](/implementation-guide/handle-fhir-identifiers-and-match-patient-data).


- If applicable, you can send files successfully. [Learn about sending files](/basics/data-exchange-with-redox/sending-a-file).
- You can test your workflow by [using developer test tools](/how-to-use-redox/use-developer-test-tools) and [testing your configured destinations](/quickstart-for-redox/send-test-messages-via-redox) in the Redox dashboard.

Once you complete this checklist, we run a few validation tests against your endpoints to make sure everything looks ship-shape. To let us know you’re ready for tech validation, [open the request form in our Help Center](https://redoxengine.zendesk.com/hc/en-us/requests/new?+ticket+form+id=41788017411860&ticket_form_id=41788017411860) and select **Tech Validation** from the <u>Request Type</u> drop-down.

During tech validation, we do the following:

- <u>**Endpoint testing**</u>. We test your endpoint, or destination, to see if your system performs validation after successfully receiving and responding to inbound messages. [Learn about receiving data from Redox](/basics/data-exchange-with-redox/receiving-data-from-redox). During this process, we send messages without required fields or variations to check that your system still sends a `200 OK` response to acknowledge the message was successfully delivered _before_ your system performs data validation. 
- <u>**Message payload testing**</u>. We make sure that your outgoing messages are appropriately populated and contain test data from your system rather than Redox test data.

After we complete technical validation, you can focus on creating your staging and production API keys, sources, and destinations. Learn how to:

- [Create an OAuth API key](/api-reference/redox-data-model-api/authenticate-an-oauth-api-key)
- [Set up sources](/how-to-use-redox/manage-your-redox-setup/set-up-sources)
- [Set up destinations](/how-to-use-redox/manage-your-redox-setup/set-up-destinations)

> **Keep your onboarding team engaged**
>
> Since things don't always go according to plan after go-live, we recommend keeping your product and engineering team engaged throughout your first implementation project. Engaging your team means you can more easily adjust before starting to scale.