Aller au contenu principal

FHIR Transform

Category: Healthcare Standards
Node id: fhir-transform

Standards: HIPAA, GDPR, SOC2

Transforms FHIR resources between types using predefined or custom field mappings

What it does​

  • Predefined transformations: Patient-to-Practitioner, Observation-to-DiagnosticReport, MedicationRequest-to-MedicationStatement, Encounter-to-EpisodeOfCare
  • Custom field mappings via JSON configuration
  • Nested path extraction and assignment (dot-notation)
  • Automatic metadata injection (lastUpdated, generated ID)
  • FHIR resource type validation

Use cases​

  • Transform patient records into practitioner resources for role-based workflows
  • Convert observations into diagnostic reports for clinical decision support
  • Map EHR data between FHIR resource types during migration

Runtime​

  • Performance tier: fast
  • Effect: read

Input ports​

NameTypeRequiredDescription
resourcejsonYesSource FHIR resource to transform

Output ports​

NameTypeRequiredDescription
resultjsonNoTransform result (resource, resourceType, source_type, target_type)
successbooleanNoWhether the transformation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Source Typesource_typestringYesSource FHIR resource type
Target Typetarget_typestringYesTarget FHIR resource type
TransformationtransformationstringNoPredefined transformation name (e.g., patient-to-practitioner)

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Source Fieldsource_fieldstringNoresourceInput field name containing source data
Custom MappingsmappingsjsonNoCustom field mappings (target_field -> source_path)

Errors​

CodeDescription
MISSING_SOURCE_TARGETsource_type and target_type are both required
INVALID_RESOURCE_TYPESource or target is not a valid FHIR resource type
UNSUPPORTED_TRANSFORMATIONNamed predefined transformation is not recognized
MAPPINGS_REQUIREDCustom transformation requires mappings configuration

Runtime notes​

  • result.resource is the transformed FHIR resource with a generated ID and lastUpdated meta — wire to a FHIR client node for storage
  • Custom mappings use dot-notation paths (e.g. 'name.0.family') for both source extraction and target assignment
  • Predefined transforms: patient-to-practitioner, observation-to-diagnostic-report, medication-request-to-medication-statement, encounter-to-episode-of-care
  • The source_field config defaults to 'resource' — change it if your upstream node outputs data under a different key

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.