hl7-eu-logo
PROTECT-CHILD Pediatric Transplant Data Implementation Guide
0.1.0-ci-build -

PROTECT-CHILD Pediatric Transplant Data Implementation Guide
0.1.0-ci-build - ci-build

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

Data Model (ERD)

The Entity–Relationship Diagram (ERD) for the PROTECT-CHILD data model (DMv1.2), followed by an accessible list of entities and the full relationship table.

PROTECT-CHILD data model ERD (DMv1.2)

Entities

Entity FHIR resource Description
patient Patient (EU base) + Observation (panels) + Condition (primary disease) Transplant recipient.
donor Patient (EU base) + Observation (donor type, liver type, age) Organ donor (living/deceased).
visit Encounter + EpisodeOfCare (graft episode) + Encounter (transplant admission) Central hub — every clinical record links to a visit. FHIR adds a GraftEpisode (EpisodeOfCare) anchored on the transplant date and a separate TransplantAdmission Encounter; neither is a DM table.
transplant Procedure + Observation (panel) + Procedure (anastomoses) + Condition (complications) The transplant event and intraoperative details.
immunological_data DiagnosticReport (EU core) + one Observation per result ABO/Rh, HLA (one Observation per allele), DSA and ANCA under an ImmunologicalDataReport; Banff, C4d and the liver RAI under a GraftBiopsy.
bio_sample Specimen + ServiceRequest (analysis request) Biospecimen collection (→ genomic/epigenomic analysis).
pre_medication MedicationStatement, one per drug Pre-transplant medication incl. desensitisation.
clinical_variable Observation (panel) + Condition (concomitant disease) + Procedure (concomitant procedure) Symptoms, comorbidities, organ dysfunction.
vital_sign Observation (panel) Vitals incl. 24-h ABPM.
concomitant_medication MedicationStatement Concomitant medications.
microbiology DiagnosticReport (EU core) + one Observation per test + Condition (diagnoses) EBV, CMV, BKV, and other virology + cultures.
instrumental_investigation Observation Imaging and functional studies.
immunosuppressant Medication (EU core) Immunosuppressant drug catalogue.
imm_pat MedicationStatement + Observation (drug levels) Immunosuppression to patient (induction/maintenance) + PK.
lab_test ObservationDefinition Laboratory test catalogue.
lab_result Observation Laboratory results.
clinical_event_type CodeSystem + ValueSet Controlled vocabulary of clinical event types.
clinical_event Condition + Observation (flags) + Procedure (dialysis, retransplantation, listing) Post-transplant complications and outcomes.

Relationships

The 19 relationships come from the data model's RELATIONSHIPS definition. Visit is the hub: almost every per-visit record has a visit_id foreign key.

Parent   Child Key Cardinality Notes
patient → visit patient_id One-to-Many  
visit → transplant visit_id One-to-Many  
donor → transplant donor_id One-to-Many  
visit → immunological_data visit_id One-to-Many  
donor → immunological_data donor_id One-to-Many This can be 0-to-N
visit → pre_medication visit_id One-to-Many  
visit → clinical_variable visit_id One-to-Many  
visit → vital_sign visit_id One-to-Many  
visit → concomitant_medication visit_id One-to-Many  
visit → microbiology visit_id One-to-Many  
donor → microbiology donor_id One-to-Many This can be 0-to-N
visit → instrumental_investigation visit_id One-to-Many  
immunosuppressant → imm_ind_pat imm_id One-to-Many  
visit → imm_ind_pat visit_id One-to-Many  
lab_test → lab_result lab_test_id One-to-Many  
visit → lab_result visit_id One-to-Many  
clinical_event_type → clinical_event clinical_event_type_id One-to-Many  
visit → clinical_event visit_id One-to-One  
visit → bio_sample visit_id One-to-Many  

Note: the DM's RELATIONSHIPS sheet calls the imm_pat table imm_ind_pat; it is the ImmPat profile in this IG. visit → clinical_event is one-to-one in the data model; this guide relaxes it so a visit can carry several events (see the Clinical Event map).