Customer 360 for Healthcare > Integrating Customer 360 with source systems > Ingress records that comply with FHIR R4 standard
  

Ingress records that comply with FHIR R4 standard

You can ingress records in a file format that comply with the Fast Health Interoperability Resources (FHIR) R4 standard from a source system into MDM SaaS in batches.

Ingress data

You can import organization and practitioner records that comply with the FHIR R4 standard into HCO and HCP business entities in batches. You can import files in NDJSON format.
To onboard records to MDM SaaS, run an ingress job. The ingress job imports data from the NDJSON file to the MDM SaaS data store. When you run the ingress job, a flat file connector parses the flat file into an individual JSON response. Each JSON response gets converted into a relational output. After the transformation of data, the Business 360 FEP Connector uses Cloud Data Integration to maps the source fields to the business entity fields.
For more details about ingress jobs, see Batch jobs.
The following image shows the process to ingress FHIR R4 standard-compliant records to MDM SaaS:
When you run an ingress job, a flat file connector parses the NDJSON file into a JSON response. The JSON response gets converted into a relational output. The Business 360 FEP connector maps the source fields to the corresponding Customer 360 business entities.