which made linking them quite challenging. We offered a solution to map those structures, considering nesting levels, entities, and other nuances.
To allow the data transfer in FHIR format, we created FHIR profiles for the TPA and determined the required FHIR resources as well as corresponding business processes. Our team used three main FHIR resources: Organization, Practitioner, and PractitionerRrole.
When all necessary profiles, FHIR extensions, and terminologies were ready, the team ran an FHIR server. We used our custom solution — the Kodjin FHIR Server, built from scratch for high-load systems.