The ID of the FHIR provider to use. Can be either:

• A UUID representing the provider ID
• A provider name (legacy support - will just use the most recently updated provider with this name)

The FHIR resource path to operate on. This follows FHIR RESTful API conventions.
Examples:

• "Patient" (for resource type operations)
• "Patient/123" (for specific resource operations)
• "Patient/123/_history" (for history operations)

Optional header for on-behalf-of authentication. Used when making requests on behalf of another user or entity.
Must be in the format: Patient/{uuid} or Practitioner/{uuid}

Optional header for FHIR provider authentication. Contains credentials in the format {fhir_provider_id}:{oauth2_token}.
Multiple FHIR provider integrations can be provided as comma-separated values.