Validate your development

Last updated: Jan 8, 2024

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

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, which contains useful information from HL7. You can also check out the official HL7 FHIR® web validator tool or review other 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.
If applicable, you can send files successfully. Learn about sending files.
You can test your workflow by using developer test tools and testing your configured endpoints in the Redox dashboard.

After completing this checklist, you can submit a technical validation ticket via our Help Desk. We run a few validation tests against your endpoints to make sure everything looks ship-shape:

Endpoint testing. We test your endpoint, or destination, to see if your system performs validation after successfully receiving and responding to inbound messages. We send messages without all the variations or required fields to make sure your system still sends a success response before performing data validation. Review our data exchange docs with expectations for common variations and integrating via Redox.
Message payload testing. 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 endpoints and API keys. Learn how to:

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.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.