@Eyal Levin, the IRIS for Health team is working on a FHIR registry client that will resolve dependencies, download, and install packages to an endpoint. 

We're planning to support Simplifier.net as well as manual uploads in IRIS for Health 2026.3. Note that this planned release is subject to change, so keep an eye out for release notes, or contact me directly!

Hi @André Sheydin, for standardized FHIR conformance testing, we recommend specialist tools like Inferno or Touchstone. You can take a look at open-source FHIR tests available here: https://github.com/inferno-framework or https://inferno.healthit.gov/test-kits/

For example, we regularly test the IRIS for Health FHIR Server against the ONC G10 standardized APIs required for US health modules, plus a handful of other test plans. We typically use Synthea to generate sample bundles conformant to a particular profile (e.g, US Core 6.1.0) with some manual curation. These tools do provide detailed reports and case-handling which you can dashboard or diff, but lots of opportunity to customize further for your needs.

@Hassan Mirza , 4101 is a response code used by Epic to mean "no results found", the Patient.$match API spec and codes can be found here: https://fhir.epic.com/Specifications?api=10423

 If you think this is being returned incorrectly, definitely reach out to Epic directly for support!