pidgeon conform probes a live FHIR endpoint against a published Implementation Guide. Install the IG you’re testing against, then either target a single resource or walk the whole endpoint.
Install the IG you’re testing against
Conform grades against the IG packages you have installed:fhir-us-core-6.0, fhir-davinci-pas-2.1, fhir-davinci-crd-2.1, fhir-davinci-dtr-2.0. See CMS-0057-F for which IG maps to which requirement.
One resource against one profile
--profile takes an IG short name (us-core-patient) or a canonical URL. --resource is ResourceType/id.
Walk the whole endpoint
--walk reads the endpoint’s CapabilityStatement and probes every resource × profile pair it declares:
--only-resources Patient,Encounter, or scope it to one IG with --ig http://hl7.org/fhir/us/core/.
Authenticate
Most real endpoints need a token. Conform supports two paths. Static bearer token:.well-known/smart-configuration, signs an RS384 client assertion with your private key, and exchanges it for an access token:
--token-endpoint to skip discovery. --auth and --auth-smart-backend are mutually exclusive.
Check coded fields against terminology
--check-terminology validates every coded field in the fetched resources against a live FHIR terminology service. A code that doesn’t resolve flips the exit code to 1:
From the Post app
The Conformance panel in Post runs the same walk. Wire the endpoint, pick the IG, run it, and read the pass/fail per rule with streaming results. See Get started with Post.Next
- Evidence and CI: exit codes, scorecards, readiness packs, and badges
- Conform CLI reference: every flag