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
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
Mila (7) is registered as a transplant candidate (Patient). During evaluation and waiting-list follow-up (Visit), clinicians capture vitals and growth (VitalSign, ClinicalVariable), record lab tests and results (LabTest, LabResult), document imaging and functional studies (InstrumentalInvestigation), and monitor infectious serology (Microbiology). Intercurrent episodes (e.g. cholangitis) are logged as clinical events (ClinicalEventType, ClinicalEvent), alongside concomitant medications (ConcomitantMedication) and pre-transplant medications including desensitisation (PreMedication).
When a suitable organ becomes available (Donor), the transplant procedure and operative details are recorded (Transplant). Post-operatively, induction and maintenance immunosuppression — including drug-level monitoring — are captured in a single unified record (ImmPat) referencing the immunosuppressant catalogue (Immunosuppressant). Post-transplant complications such as rejection, delayed graft function, and AKI episodes are represented as typed clinical events (ClinicalEvent). Blood group, Rh factor, HLA typing, DSA, and Banff grading are captured at each relevant visit (ImmunologicalData). Biosamples collected for biobanking are tracked as well (BioSample).