Saltar al contenido principal

FHIR STU3 → R4 Normalizer

Category: Healthcare Standards
Node id: stu3-to-r4

Standards: GDPR, UK-GDPR

Converts FHIR STU3 (3.0.x) resources/bundles to canonical R4 (4.0.1) using the CareConnect-aware mapper. Lossy — residual losses are reported. Reusable transform for any STU3 source.

What it does​

  • CareConnect-aware STU3→R4 resource normalization
  • Bundle and single-resource input
  • Residual-loss reporting (hazard-log hook)

Use cases​

  • Normalize MAXIMS/CareConnect STU3 records to canonical R4
  • Feed R4 into FHIR-to-OMOP and analytics

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
resourcejsonNoA single STU3 FHIR resource
bundlejsonNoA STU3 FHIR Bundle

Output ports​

NameTypeRequiredDescription
resultjsonNoR4 resource/bundle + losses[]
metadatajsonNocount, loss_count
successbooleanNo

Errors​

CodeDescription
STU3_TO_R4_MISSING_INPUTNeither resource nor bundle provided
STU3_TO_R4_FAILEDA resource could not be converted (e.g. missing resourceType)

Runtime notes​

  • Provide exactly one of resource or bundle.
  • Conversion is LOSSY (code→CodeableConcept widening, removed elements); inspect result.losses and metadata.loss_count.
  • Round-trip back to STU3 is not supported (non-invertible).

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

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..