Sure! FHIRCraft is built using InterSystems IRIS for Health and works through an interoperability production.
When you send a request (e.g. from the web UI), it goes through a REST service that transforms the input JSON into an IRIS message. From there, a business process handles the generation logic. Depending on the configuration, it can reuse existing resources from a FHIR repository or generate new ones.
The generated resources (like Patient, Observation, etc.) are optionally posted back to a FHIR server — either the default IRIS repository or any external one via REST.
It’s modular and easy to extend with new resource types. If you're curious, I wrote a short technical walkthrough here 😉
Wow, thank you very much for this full explanation!! Now I understand better how BPL's work 😊
I don't know if this apply, but I have written an article about the application. And I have translated it.
Also, I have seen that I have 2 points for finding FHIR bug, but I think I don't have found any 😅