FHIRSTU3toR4
FHIR Plugin – FHIR STU3 to R4
Summary (SEO Meta Description):
The FHIR STU3 to R4 converter plugin in WeHub transforms FHIR resources from STU3 into the R4 standard.
Supports a wide range of resource templates, ensuring compatibility with modern FHIR systems.
Overview
The FHIR STU3 to R4 action converts resources from FHIR STU3 (3.0.1) into FHIR R4 (4.0.1).
This ensures interoperability across systems where older STU3-based data must be integrated into workflows or applications expecting R4 compliance.
It is especially critical in healthcare ecosystems migrating to newer FHIR standards while maintaining legacy integrations.
⚙️ Action: FHIR STU3 to R4
- Description: Transforms a FHIR STU3 resource into its equivalent R4 representation.
- Use Case: Upgrade legacy data structures, enable downstream systems to work with consistent R4 resources.
Configuration Options:
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the node (e.g., "Convert Patient STU3 to R4"). |
| Root Template | Enum | Select the FHIR resource to be converted. Supported options include: |
Account, ActivityDefinition, AllergyIntolerance, AdverseEvent, Appointment, AppointmentResponse, AuditEvent, Basic, Binary, BodySite, Bundle, CapabilityStatement, CarePlan, CareTeam, ChargeItem, Claim, ClaimResponse, ClinicalImpression, CodeSystem, Communication, CommunicationRequest, CompartmentDefinition, Composition, ConceptMap, Condition, Consent, Contract, Coverage, DataElement, DetectedIssue, Device, DeviceComponent, DeviceMetric, DeviceRequest, DeviceUseStatement, DiagnosticReport, DocumentManifest, DocumentReference, EligibilityRequest, EligibilityResponse, Encounter, Endpoint, EnrollmentRequest, EnrollmentResponse, EpisodeOfCare, ExpansionProfile, ExplanationOfBenefit, FamilyMemberHistory, Flag, Goal, GraphDefinition, Group, GuidanceResponse, HealthcareService, ImagingManifest, ImagingStudy, Immunization, ImmunizationRecommendation, ImplementationGuide, Library, Linkage, List, Location, Measure, MeasureReport, Media, Medication, MedicationAdministration, MedicationDispense, MedicationRequest, MedicationStatement, MessageDefinition, MessageHeader, NamingSystem, NutritionOrder, Observation, OperationDefinition, OperationOutcome, Organization, Parameters, Patient, PaymentNotice, PaymentReconciliation, Person, PlanDefinition, Practitioner, PractitionerRole, Procedure, ProcedureRequest, ProcessRequest, ProcessResponse, Provenance, Questionnaire, QuestionnaireResponse, ReferralRequest, RelatedPerson, RequestGroup, ResearchStudy, ResearchSubject, RiskAssessment, Schedule, SearchParameter, Sequence, ServiceDefinition, Slot, Specimen, StructureDefinition, StructureMap, Subscription, Substance, SupplyDelivery, SupplyRequest, Task, TestScript, TestReport, ValueSet, VisionPrescription. |
💡 Example Use Cases
- Patient Migration: Convert legacy
PatientSTU3 resources into R4 to ensure interoperability with new EHR systems. - Clinical Data Exchange: Normalize
ObservationorDiagnosticReportSTU3 data into R4 for downstream analytics pipelines. - Terminology Mapping: Convert
CodeSystemandValueSetresources to R4 to align with the latest standard vocabularies. - Billing: Transform
ClaimandExplanationOfBenefitresources for R4-based financial integrations.
FAQ
Q: Why do I need to convert from STU3 to R4?
A: Many systems are phasing out STU3 support and adopting R4 as the standard for FHIR interoperability.
Q: What happens if a field doesn’t exist in R4?
A: The converter applies WeHub’s mapping templates and gracefully excludes or transforms deprecated fields.
Q: Can I batch convert multiple resources?
A: Yes. You can use multiple nodes or workflows to process collections of resources.
Keywords: WeHub FHIR Plugin, FHIR STU3 to R4, FHIR migration, healthcare interoperability, FHIR conversion, HL7 FHIR upgrade