Cumuluz Translate Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Logical Models

Logical Models

Purpose

Logical models are the intermediate semantic layer between the selected source profile and target profile. They are used for STU3-to-R4, STU3-to-STU3, R4-to-STU3, and R4-to-R4 resource translations.

They keep the target maps readable and prevent the HTTP layer from carrying hidden mapping behavior.

Main Groups

Group	Examples
BgZ core	LogicalPatient, LogicalProblem, LogicalProcedure
additional BgZ exchange concepts	LogicalFunctionalOrMentalStatus, LogicalAllergyIntolerance, LogicalEncounter, LogicalCareTeam, LogicalAppointment, medication models, LogicalMetadata
PZP ACP	LogicalConsent, LogicalRelatedPerson, LogicalPractitioner, LogicalPractitionerRole, LogicalCommunicationRequest, LogicalDevice, LogicalDeviceUseStatement, LogicalGoal, LogicalObservation
QuestionnaireResponse extraction	LogicalQuestionnaireForm, LogicalQuestionnaireAnswer, LogicalQuestionnaireTelecom, LogicalExtractionBundle

Where To Inspect Them

The source FSH lives in:

• logical-models/input/fsh

The IG publishes generated StructureDefinition pages for the logical models. Use Artifacts and filter for StructureDefinition-logical-*.

Reading Guidance

Start with:

• LogicalPatient
• LogicalProblem
• LogicalProcedure

Then inspect the resource-specific model for the route you are reviewing. You usually do not need to read the full logical model inventory to integrate with the service.