Most FHIR work stalls in the same place. You have a real payload that reproduces
the bug, and you cannot put it in a ticket, a test fixture, or a screen share.
So you hand-edit a copy, miss a field, and end up debugging your redaction
instead of the thing you were chasing.
The factory is the way out of that loop: wash, check, compare — three tools
that hand off to each other, all running on synthetic data you can actually
share.
Bring your own payload, or don't
You do not need a real payload to try this. The Washer ships with fixtures, and
Compare has a built-in example with a deliberate resource gap and two field
drifts. On the preview channel the Workbench also has a Scenario Library of
synthetic PAS bundles; it is switched off on stable production, so paste or
upload there instead.
If you do bring your own: it must already be synthetic or properly
de-identified. The Washer produces test data — it is not a HIPAA
de-identification method, and it does not make PHI safe to paste.
What you end up with
A synthetic payload that keeps the shape of the real one, a conformance report
that says what a validator will say, and a field-level diff you can put in front
of a partner without a redaction pass. All of it shareable, none of it PHI.
Step 1
Wash it
Client-side only · not HIPAA de-idPaste a production-shaped FHIR payload. The Washer replaces names, addresses, identifiers, and dates with synthetic stand-ins that keep the same shape — so the result still exercises the same code paths. Nothing is uploaded: the wash runs entirely in your browser, and an automated network-silence test in CI keeps it that way.
When the wash finishes, hit Send to Analyze — the washed payload travels with you.
Step 2
Check it
The Analysis Workbench validates PAS payloads — Submit and Inquiry — against the Da Vinci PAS profiles, and tells you what conforms, what does not, and which requirement each finding traces back to. US Core requirements come along with it, because the PAS profiles build on them. Other guides in the catalog (DTR, CRD, CDex, PDex, HRex, CARIN Blue Button) are tracked for requirement and version analysis, not payload validation — paste a DTR Questionnaire here and you will not get conformance findings.
From the results, Open in Compare carries the payload into the next step.
Step 3
Compare it
Client-side only · no networkLoad a second payload — a partner's variant, an older capture, a known-good reference — and Compare shows you exactly which fields drifted, which resources are missing entirely, and which differences are only cosmetic. Also fully client-side.
No payload handy? Try an example loads two bundles with a deliberate resource gap and two field drifts.