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

Logical Models

Each entity of the PROTECT-CHILD data model (DMv1.2) is a FHIR logical model. The worked examples show how they fit together in a real record: liver and kidney.

Organ scope and requiredness

The data model has two submitter actors:

A combined liver–kidney transplant is submitted under both. Each element carries an obligation per applicable actor, from the DM spreadsheet's Organ and Required columns:

DM Required Obligation Meaning
M — Mandatory SHALL:populate Always sent.
R — Recommended SHOULD:populate-if-known Sent whenever the centre has the value.
O — Optional MAY:able-to-populate Sent at the centre's discretion.

An element with no obligation for an actor does not apply to that organ (e.g. liver_type for the kidney actor). scripts/dm-obligations.py regenerates the obligations from the spreadsheet.

Full list