DevTools
The exchange end to end, in a tab: read how an endpoint behaves, build a bundle that validates, and trade claims with a mock payer until every flow passes. Nothing you do here touches your servers.
Two tools and no third thing to choose between: one that teaches and rehearses the exchange in a browser tab, one that carries it in production.
The exchange end to end, in a tab: read how an endpoint behaves, build a bundle that validates, and trade claims with a mock payer until every flow passes. Nothing you do here touches your servers.
The piece you actually deploy. Post a FHIR bundle to it, read a plain callback back, and it does the headers, the encryption, the certificates and the acknowledgements in between. One JSON config, no database.
One binary between your system and NHCX. Your software posts a FHIR bundle to it and reads a plain callback back; the adapter does the x-hcx-* headers, the encryption, the certificates and the acknowledgements. Nothing else about your system changes.
Selected build
macOS · arm64
Apple silicon, M1 and later
tar xzf nhcx-adapter_v1.0.1_<os>_<arch>.tar.gzcd nhcx-adapter_v1.0.1_<os>_<arch>./nhcx-adapter config edit # writes config.json./nhcx-adapter serve # checks, then listens./nhcx-adapter ledger follow # the traffic, live