Working with test data
Uploading HL7, FHIR and CDA samples, capturing payloads from sandbox runs, and keeping golden fixtures with the project.
Last updated August 12, 2026
On this page
Good integration work is mostly about the messages that do not look like the specification. The test-data library exists so those become fixtures rather than folklore.
Uploading samples
Each project has a test-data library. You can upload:
- HL7 v2 messages — ADT, ORM, ORU, SIU and anything else your sending system emits
- FHIR resources and bundles, R4 and R4B
- CDA / CCDA documents
Samples are scoped to the project, so everyone working on those channels sees the same set.
Capturing from runs
The more useful source of fixtures is production-shaped traffic you have already seen. From a sandbox run, you can capture the payload at any stage and save it into the library. When a message breaks a mapping, capture it, fix the mapping, and keep the message as a regression fixture.
Golden fixtures
A golden fixture is a sample plus the output you expect from it. Keeping a handful per channel — the common case, one edge case, and whatever broke last time — makes a change to a transformer something you can verify in seconds rather than something you hope about.
Synthetic data only on Free
The Free plan is restricted to synthetic data. Do not upload real patient messages to a Free workspace.
PHI is permitted on Team and Enterprise under a Business Associate Agreement. Even there, the smaller your fixture set of real data, the smaller your exposure — de-identified samples are usually enough to exercise a mapping. See PHI, BAA and data handling.
Where fixtures live
Test data is part of the project, which means it travels with an export. If you later move to self-hosted intu-dev, your fixtures come with the channels they belong to.