Integrated Campaign Registry (ICR) Implementation Guide
0.1.0 - ci-build
Integrated Campaign Registry (ICR) Implementation Guide
0.1.0 - ci-build
Integrated Campaign Registry (ICR) Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Draft as of 2026-10-29 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="icr-task-output-type-cs"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem icr-task-output-type-cs</b></p><a name="icr-task-output-type-cs"> </a><a name="hcicr-task-output-type-cs"> </a><p>This case-sensitive code system <code>https://icr.healthcampaigns.org/CodeSystem/icr-task-output-type-cs</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">treated-count<a name="icr-task-output-type-cs-treated-count"> </a></td><td>Persons treated / vaccinated (scalar tally)</td><td>The visit's scalar result tally: persons treated or vaccinated.</td></tr><tr><td style="white-space:nowrap">houses-visited<a name="icr-task-output-type-cs-houses-visited"> </a></td><td>Houses visited</td><td>Number of houses visited — house-to-house tasks at area/team-day granularity.</td></tr><tr><td style="white-space:nowrap">eligible-present<a name="icr-task-output-type-cs-eligible-present"> </a></td><td>Eligible persons present</td><td>Number of eligible persons (per the protocol's target definition) present at the visit(s). Program-neutral.</td></tr><tr><td style="white-space:nowrap">eligible-absent<a name="icr-task-output-type-cs-eligible-absent"> </a></td><td>Eligible persons absent</td><td>Number of eligible persons absent at the visit(s) — feeds same-day mop-up lists.</td></tr><tr><td style="white-space:nowrap">children-already-marked<a name="icr-task-output-type-cs-children-already-marked"> </a></td><td>Children already finger-marked</td><td>Number of children found already finger-marked (already covered this round) on arrival — house-to-house campaigns.</td></tr><tr><td style="white-space:nowrap">missed-reason<a name="icr-task-output-type-cs-missed-reason"> </a></td><td>Missed reason</td><td>Why eligible person(s) were missed at this visit — person-level (absent, sleeping) and area-level (insecurity, shortage, access) causes.</td></tr><tr><td style="white-space:nowrap">noncompliance-reason<a name="icr-task-output-type-cs-noncompliance-reason"> </a></td><td>Refusal reason</td><td>Why the household/caregiver refused the intervention (WHO IDHC 'intervention refusal') — drives social mobilization and mop-up targeting.</td></tr><tr><td style="white-space:nowrap">exclusion-reason<a name="icr-task-output-type-cs-exclusion-reason"> </a></td><td>Exclusion reason</td><td>Why a present, age-eligible person was clinically excluded this round (under dose-pole height/age, pregnant, breastfeeding, acutely ill).</td></tr><tr><td style="white-space:nowrap">revisit-outcome<a name="icr-task-output-type-cs-revisit-outcome"> </a></td><td>Revisit outcome</td><td>Outcome of a person-targeted follow-up revisit: already-vaccinated | vaccinated-on-revisit | still-missing.</td></tr><tr><td style="white-space:nowrap">delivery-event<a name="icr-task-output-type-cs-delivery-event"> </a></td><td>Delivery event reference</td><td>Reference to an Immunization / MedicationAdministration / supply event captured inside the visit workflow.</td></tr><tr><td style="white-space:nowrap">coverage-report<a name="icr-task-output-type-cs-coverage-report"> </a></td><td>Coverage report reference</td><td>Reference to the stratified MeasureReport that disaggregates this visit's tally.</td></tr><tr><td style="white-space:nowrap">referred-count<a name="icr-task-output-type-cs-referred-count"> </a></td><td>Persons referred</td><td>Number of people referred at this visit (each referral is an ICRReferral), so visit tallies need not count ServiceRequests and count-only capture can still report referrals.</td></tr><tr><td style="white-space:nowrap">registered-count<a name="icr-task-output-type-cs-registered-count"> </a></td><td>Persons registered</td><td>Number of people registered into the campaign at this visit — on a separate registration visit or during a delivery visit alike.</td></tr><tr><td style="white-space:nowrap">registered-household<a name="icr-task-output-type-cs-registered-household"> </a></td><td>Household registered</td><td>A household (ICRDeliveryUnit) registered into the campaign at this visit: on a household visit the Task's own household, on a site session each household registered there. A household can be registered without any new person being registered. Households registered in a round = the distinct registered-household references.</td></tr><tr><td style="white-space:nowrap">voucher<a name="icr-task-output-type-cs-voucher"> </a></td><td>Voucher issued</td><td>The voucher or QR code issued at registration, as an Identifier with one system per campaign round. The distribution that redeems it carries the same system and value as an identifier of type voucher.</td></tr><tr><td style="white-space:nowrap">entitlement<a name="icr-task-output-type-cs-entitlement"> </a></td><td>Entitlement</td><td>What the registered household is due, as a Quantity (for example 3 LLINs).</td></tr></table></div>
</text>
<url
value="https://icr.healthcampaigns.org/CodeSystem/icr-task-output-type-cs"/>
<version value="0.1.0"/>
<name value="ICRTaskOutputTypeCS"/>
<title value="ICR Task Output Type"/>
<status value="draft"/>
<experimental value="false"/>
<date value="2026-10-29T03:03:58+00:00"/>
<publisher value="UNICEF"/>
<contact>
<name value="UNICEF"/>
<telecom>
<system value="url"/>
<value value="https://www.unicef.org"/>
</telecom>
</contact>
<description
value="The standard axes of what a campaign visit produced — the coded vocabulary of Task.output.type (task-outputs round). Parameters of the work (delivery strategy, task origin) stay Task extensions; RESULTS of executing the visit are coded outputs. A new tally axis is a new code here, not a new extension. The house-to-house axes (houses-visited, eligible-present, eligible-absent, children-already-marked) have no meaning at a fixed post — strategy determines which outputs exist (icr-task-h2h-outputs)."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<caseSensitive value="true"/>
<content value="complete"/>
<count value="16"/>
<concept>
<code value="treated-count"/>
<display value="Persons treated / vaccinated (scalar tally)"/>
<definition
value="The visit's scalar result tally: persons treated or vaccinated."/>
</concept>
<concept>
<code value="houses-visited"/>
<display value="Houses visited"/>
<definition
value="Number of houses visited — house-to-house tasks at area/team-day granularity."/>
</concept>
<concept>
<code value="eligible-present"/>
<display value="Eligible persons present"/>
<definition
value="Number of eligible persons (per the protocol's target definition) present at the visit(s). Program-neutral."/>
</concept>
<concept>
<code value="eligible-absent"/>
<display value="Eligible persons absent"/>
<definition
value="Number of eligible persons absent at the visit(s) — feeds same-day mop-up lists."/>
</concept>
<concept>
<code value="children-already-marked"/>
<display value="Children already finger-marked"/>
<definition
value="Number of children found already finger-marked (already covered this round) on arrival — house-to-house campaigns."/>
</concept>
<concept>
<code value="missed-reason"/>
<display value="Missed reason"/>
<definition
value="Why eligible person(s) were missed at this visit — person-level (absent, sleeping) and area-level (insecurity, shortage, access) causes."/>
</concept>
<concept>
<code value="noncompliance-reason"/>
<display value="Refusal reason"/>
<definition
value="Why the household/caregiver refused the intervention (WHO IDHC 'intervention refusal') — drives social mobilization and mop-up targeting."/>
</concept>
<concept>
<code value="exclusion-reason"/>
<display value="Exclusion reason"/>
<definition
value="Why a present, age-eligible person was clinically excluded this round (under dose-pole height/age, pregnant, breastfeeding, acutely ill)."/>
</concept>
<concept>
<code value="revisit-outcome"/>
<display value="Revisit outcome"/>
<definition
value="Outcome of a person-targeted follow-up revisit: already-vaccinated | vaccinated-on-revisit | still-missing."/>
</concept>
<concept>
<code value="delivery-event"/>
<display value="Delivery event reference"/>
<definition
value="Reference to an Immunization / MedicationAdministration / supply event captured inside the visit workflow."/>
</concept>
<concept>
<code value="coverage-report"/>
<display value="Coverage report reference"/>
<definition
value="Reference to the stratified MeasureReport that disaggregates this visit's tally."/>
</concept>
<concept>
<code value="referred-count"/>
<display value="Persons referred"/>
<definition
value="Number of people referred at this visit (each referral is an ICRReferral), so visit tallies need not count ServiceRequests and count-only capture can still report referrals."/>
</concept>
<concept>
<code value="registered-count"/>
<display value="Persons registered"/>
<definition
value="Number of people registered into the campaign at this visit — on a separate registration visit or during a delivery visit alike."/>
</concept>
<concept>
<code value="registered-household"/>
<display value="Household registered"/>
<definition
value="A household (ICRDeliveryUnit) registered into the campaign at this visit: on a household visit the Task's own household, on a site session each household registered there. A household can be registered without any new person being registered. Households registered in a round = the distinct registered-household references."/>
</concept>
<concept>
<code value="voucher"/>
<display value="Voucher issued"/>
<definition
value="The voucher or QR code issued at registration, as an Identifier with one system per campaign round. The distribution that redeems it carries the same system and value as an identifier of type voucher."/>
</concept>
<concept>
<code value="entitlement"/>
<display value="Entitlement"/>
<definition
value="What the registered household is due, as a Quantity (for example 3 LLINs)."/>
</concept>
</CodeSystem>