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
| Official URL: https://hl7.eu/fhir/ig/hl7.eu.fhir.protect-child/ValueSet/imm-pat-dose-unit-vs | Version: 0.1.0-ci-build | |||
| Draft as of 2026-09-28 | Computable Name: ImmPatDoseUnitVS | |||
Allowed UCUM dose units for immunosuppressant therapy records (DMv1.2 imm_pat.unit field).
PROTECT-CHILD records the dose given at each administration, not the total for a day. So a DM-sourced record uses one of the plain amount units below and states the frequency in dosage.timing — invariant pc-dose-1 requires it, because '0.1 mg/kg' on its own does not say per dose or per day, and for a twice-daily drug the two differ by a factor of two.
The rate units (…/d) are listed for data from sources that record a daily total, so that such a record can say so rather than being silently mistaken for a per-administration one.
References
http://unitsofmeasure.org version Not Stated (use latest from terminology server)| Code | Display |
| mg.kg-1 | mg/kg |
| mg.m-2 | mg/m² |
| mg | mg |
| mg.kg-1.d-1 | mg/kg/day |
| mg.m-2.d-1 | mg/m²/day |
| mg.d-1 | mg/day |
Expansion from tx.fhir.org based on codesystem UCUM version 2.2
This value set contains 6 concepts
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |