FHIR custom implementation
When Geoprism Registry exchanges data with a Fast Healthcare Interoperability Resources (FHIR) server through a FHIR synchronization, the data is transformed by an implementation:
An export implementation (
FhirDataPopulator) turns list data into FHIR resources.An import implementation (
FhirResourceProcessor) turns FHIR resources into Geo-Objects.
Geoprism Registry includes these implementations, which you can choose in a synchronization configuration without writing any code:
Basic Export Implementation
Export
net.geoprism.registry.etl.fhir.BasicFhirDataPopulator
mCSD Export Implementation
Export
net.geoprism.registry.etl.fhir.MCSDFhirDataPopulator
Basic Resource processor
Import
net.geoprism.registry.etl.fhir.BasicFhirResourceProcessor
If these don't fit your data, a developer can write a custom implementation. Implementations are found with the Java ServiceLoader, so you add one by building a JAR that registers its classes. The steps are:
Last updated