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
| Name | Type | Required | Description |
|---|---|---|---|
resource | json | No | A single STU3 FHIR resource |
bundle | json | No | A STU3 FHIR Bundle |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | R4 resource/bundle + losses[] |
metadata | json | No | count, loss_count |
success | boolean | No |
Errors
| Code | Description |
|---|---|
STU3_TO_R4_MISSING_INPUT | Neither resource nor bundle provided |
STU3_TO_R4_FAILED | A 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.
Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..