PROTECT-CHILD Pediatric Transplant Data Implementation Guide, published by Protect Child. This guide is not an authorized publication; it is the continuous build for version 0.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/protect-child/ and changes regularly. See the Directory of published versions

Model Maps

How each PROTECT-CHILD data model entity maps to the FHIR profiles in this IG.

Cardinality key — M = Mandatory (1..1) · R = Recommended (0..1) · O = Optional (0..1)

Information Flow

The diagram shows how the entities relate and which FHIR R4 base resource each maps to. Solid arrows are mandatory references; dashed arrows are optional or calculated links.

Key relationships:

• Patient is the anchor. Each patient has one or more Visits, which anchor all per-visit clinical data.
• Donor links to Transplant (the surgical event).
• Visit is the central hub. Every clinical, laboratory, medication, specimen and outcome record carries a visit_id foreign key, which becomes an Encounter reference in FHIR.
• Transplant is a Procedure for the surgical event. Linked to it are:
  • peri-operative measurements (ischemia times, weight ratio, etc.) as components of a TransplantDetails Observation, via Observation.partOf;
  • each surgical anastomosis as a TransplantAnastomosis Procedure, via Procedure.partOf;
  • each intraoperative complication as an IntraoperativeComplication Condition, via Procedure.complicationDetail.

Entity Index

Each entity's map is also published as a machine-readable ConceptMap from its logical model to the profiles, one group per target profile. The OMOP side is published the same way: see the DM → FHIR → OMOP Crosswalk.

Value Maps

The profiles bind to standard codes (SNOMED CT, LOINC, ATC). The data model's own value lists are kept as local CodeSystems (e.g. TransplantTypeCS, ClinicalEventTypeCS). Seventeen ConceptMaps translate between the two:

• 13 code-list maps take each DM value to its standard code: TransplantTypeToStandard, BiliaryAnastomosisTypeToStandard, UreteralAnastomosisTypeToStandard, IntraoperativeComplicationToStandard, VascularComplicationTypeToStandard, ClinicalEventTypeToStandard, ClinicalEventProcedureTypeToStandard, DonorLiverTypeToStandard, ConcomitantDiseaseCategoryToStandard, InstrumentalInvestigationNameToStandard, ImmunosuppressantDrugTypeToStandard, PreMedicationAntihypertensiveDrugToStandard, MicrobiologyToStandard.
• 2 column maps take a microbiology or immunological_data column to the LOINC test code of its Observation: DmMicrobiologyToFhir, DmImmunologicalDataToFhir.
• 2 result maps turn a DM yes/no into Positive/Negative or Detected/Not detected: DmBooleanToSerologyResult, DmBooleanToDetectionResult.

The validator does not use them. They are for sites that recorded data with the DM values, to convert before submitting, and they are the starting point for a FHIR → OMOP transform. All ConceptMaps are listed under Terminology: Concept Maps on the Artifacts page.