The decision-support logic is the DAK’s component 6: the decisions the journeys make, as decision tables in the OMG Decision Model and Notation (DMN 1.3), as the WHO SMART Guidelines DAK writes them. Each table names the business-process tasks it serves, the requirements it applies, the data elements it reads and the FHIR artifacts that show it in the examples. Each is also a PlanDefinition (type eca-rule) with one action per rule, so it is listed in the artifact index.
The sources are processes/content/decisions/*.dmn; this page and the PlanDefinitions are generated from them. The entries use the FEEL subset the harness’s decision-table interpreter accepts: - (any), literals, comparisons and one-of. Every table’s hit policy is FIRST: the rules are tried in order and the first that matches applies, so the order is part of the logic. Where a rule says “by national policy”, the policy is the home country’s; the tables illustrate the decisions, they are not a country’s rules.
TD.DT.01 What does a scanned DVC become in the child’s record?
From the result of reading one foreign DVC, decide whether its dose is recorded as verified, kept as reported and not verified, or not recorded from it at all.
- Serves: J2 Discover and refer an unregistered infant in Country B: Read each DVC unverified (triage) (
Task_Read); Add the infant; save doses as reported (Task_Register); J3 Verify, import and schedule at the home clinic: Verify each HCERT against the trust list (Task_Verify); Every DVC verified? (Gateway_Verified); Note the failure; decide doses by policy (Task_Unverified); Import the doses as FHIR Immunization resources (Task_Import) - Requirements: STT-VER-001, STT-VER-006, STT-VER-008, STT-VER-011
- Data elements: TD.J3A.DE05 Verification result, TD.J3A.DE07 Failure reason, TD.J3A.DE09 Record outcome
- In the examples: StructureDefinition TrustDemoOnesaReportedImmunization, StructureDefinition TrustDemoOnesaDvcVerification, Provenance TrustDemoJ3Verification
- Computable form: PlanDefinition TrustDemoDT01; source dvc-record-outcome.dmn, hit policy FIRST
| # | Verification result (result) |
Failure reason (failureReason) |
Record outcome (outcome) |
Action (action) |
Annotation |
|---|---|---|---|---|---|
| 1 | unverified |
any | reported-unverified |
Save the dose as reported by the family (primarySource false, the caregiver as information source, a note that nothing is verified) and refer the child to the clinic for verification. | The CHW’s triage read in J2 (STT-VER-011): nothing is verified, so the dose is reported, never verified. Example Immunization TrustDemoJ2HepBReported. |
| 2 | verified |
any | verified |
Import the dose with primarySource true and a verification Provenance that names the signer’s key and removes the reported dose it replaces; then map its vaccine code (TD.DT.02). | J3’s yes path (STT-VER-001): the dose is recorded from its primary source. Examples Immunization TrustDemoJ3HepB and Provenance TrustDemoJ3Verification. |
| 3 | failed |
KidNotFound |
reported-unverified |
Keep the dose as reported; record the step and reason (STT-VER-008); verify the DVC again after the next trust-list refresh. | The signer’s certificate is not in the clinic’s cached trust list (STT-VER-006), for example a signer added after the last refresh: J3’s no path “until the next refresh”. |
| 4 | failed |
one of Expired, NotYetValid |
reported-unverified |
Keep the dose as reported; record the step and reason; the clinician decides by national policy whether to give or repeat the dose. | The signature verified, but the certificate is outside its validity period. The dose is not verified; the clinician decides by national policy. |
| 5 | failed |
one of BadPrefix, UnsupportedContextVersion, Base45Invalid, InflateFailed, LimitExceeded, CoseMalformed |
not-read |
Scan again; if it still fails, treat the card as paper and record why it was not verified. | Decoding failed before any signature check (STT-VER-001 order), so nothing was read: three states, not two, since a bad scan is not evidence either way. |
| 6 | failed |
any | rejected |
Do not record a dose from this certificate; record the step and reason; the clinician decides by national policy, as for an undocumented dose. | Any other failure (signature, key usage, header, algorithm, hcert claim or payload): the certificate is not evidence of a dose. |
TD.DT.02 Which national schedule code does an imported dose carry?
For one dose, decide whether and how the national schedule code is added beside the issuer’s product code, which is always kept.
- Serves: J3 Verify, import and schedule at the home clinic: Add national codes beside foreign ones (
Task_Map) - Requirements: STD-SEM-001
- Data elements: TD.J3A.DE09 Record outcome, TD.J3B.DE01 Issuer’s product code, TD.J3B.DE02 National schedule code, TD.J3B.DE03 Mapping basis
- In the examples: ConceptMap TrustDemoProductToOnesaEpi, Provenance TrustDemoJ3Adjudication, Immunization TrustDemoJ3HepB
- Computable form: PlanDefinition TrustDemoDT02; source vaccine-code-mapping.dmn, hit policy FIRST
| # | Record outcome (TD.DT.01) (outcome) |
Entry in the national map (mapEntry) |
Clinician confirms an equivalent (clinicianConfirms) |
Mapping basis (mappingBasis) |
Action (action) |
Annotation |
|---|---|---|---|---|---|---|
| 1 | one of reported-unverified, rejected, not-read |
any | any | not-imported |
No schedule code is added. | Only a verified dose is imported and mapped (J3’s yes path); a reported dose keeps the issuer’s code alone. |
| 2 | verified |
equivalent |
any | concept-map |
Add the mapped schedule code beside the product code. | STD-SEM-001 (map): the published national map has an equivalent; both codings are kept, as in TrustDemoJ3Bcg. |
| 3 | verified |
none |
yes |
clinician-confirmed |
Add the confirmed schedule code beside the product code; record the clinician’s attestation as a Provenance; add the pair to the national map. | The map has no entry and the clinician confirms the equivalent (J3: the Hep B product). Her decision is recorded and added to the map so the next clinic need not repeat it. |
| 4 | verified |
none |
no |
unmapped |
Keep the product code as it is and show the dose to the clinician as unmapped; the schedule does not count it (TD.DT.03). | STD-SEM-001 (unmapped): no equivalent is known, and none is guessed. |
TD.DT.03 Does the national schedule count this dose?
For one Immunization in the child’s record, decide whether the schedule evaluation counts it as given.
- Serves: J3 Verify, import and schedule at the home clinic: Evaluate the national schedule (
Task_Schedule) - Requirements: STD-SCH-001, STD-SEM-001
- Data elements: TD.J3B.DE02 National schedule code, TD.J3B.DE05 Counts toward the schedule
- In the examples: StructureDefinition TrustDemoOnesaImmunization, StructureDefinition TrustDemoOnesaReportedImmunization
- Computable form: PlanDefinition TrustDemoDT03; source dose-counts.dmn, hit policy FIRST
| # | Recorded from its primary source (primarySource) |
Has a national schedule code (hasScheduleCode) |
Counts (counts) |
Why (why) |
Annotation |
|---|---|---|---|---|---|
| 1 | false |
any | false |
Reported, not verified. | A reported dose (J2: TrustDemoJ2HepBReported) is shown but not counted. |
| 2 | true |
false |
false |
Unmapped: shown to the clinician. | A verified dose with no schedule code (TD.DT.02 unmapped) cannot be read by the schedule, which works on schedule codes. |
| 3 | true |
true |
true |
Counted as given. | STD-SCH-001: counted by its schedule code and date, wherever it was given (J3: TrustDemoJ3HepB, TrustDemoJ3Bcg). |
TD.DT.04 Is this dose of the national schedule due?
For one action of the national schedule, decide whether the evaluation recommends it now, and from which date.
- Serves: J3 Verify, import and schedule at the home clinic: Evaluate the national schedule (
Task_Schedule); Give due doses and book the next visit (Task_Plan) - Requirements: STD-SCH-001
- Data elements: TD.J3B.DE05 Counts toward the schedule, TD.J3B.DE07 Schedule dose, TD.J3B.DE08 Forecast status, TD.J3B.DE09 Due date
- In the examples: PlanDefinition TrustDemoOnesaInfantSchedule, ImmunizationRecommendation TrustDemoJ3Recommendation, Task TrustDemoJ3Reminder
- Computable form: PlanDefinition TrustDemoDT04; source dose-due.dmn, hit policy FIRST
| # | A counted dose has this action’s code (TD.DT.03) (counted) |
This action’s timing age is the earliest among the actions with no counted dose (isNextVisit) |
Forecast (forecast) |
Due date (dueDate) |
Annotation |
|---|---|---|---|---|---|
| 1 | true |
any | complete |
— | J3: the Hep B and BCG birth doses count once imported, so they are not recommended again (STD-SCH-001). |
| 2 | false |
true |
due |
birthDate + timingAge | J3: pentavalent 1, bOPV 1 and PCV 1 at 6 weeks, due 2025-12-09 (ImmunizationRecommendation TrustDemoJ3Recommendation), with a reminder Task for that date. |
| 3 | false |
false |
not-yet |
— | J3: measles-rubella 1 at 9 months belongs to a later visit and is not in this recommendation. |
TD.DT.05 Does the portal release the manifest for this request?
For one manifest request (ITI-YY5), decide whether the portal releases the manifest, and what the access log records.
- Serves: J4.1 Read a family member’s records at the point of care abroad: Check passcode, log access, return manifest (
Task_Release) - Requirements: STD-ACC-001
- Data elements: TD.J40.DE06 Valid until, TD.J40.DE09 Withdrawn at, TD.J41.DE06 Released, TD.J41.DE07 Audit outcome, TD.J41.DE08 Refusal reason
- In the examples: Consent TrustDemoJ4Consent, AuditEvent TrustDemoJ41Access, AuditEvent TrustDemoJ41WrongPasscode
- Computable form: PlanDefinition TrustDemoDT05; source vhl-release.dmn, hit policy FIRST
| # | The holder withdrew the link (withdrawn) |
The request is within the period the holder chose (withinPeriod) |
The passcode matches (passcodeMatches) |
Release (release) |
Audit outcome (auditOutcome) |
Refusal reason (refusalReason) |
Annotation |
|---|---|---|---|---|---|---|---|
| 1 | true |
any | any | false |
4 |
withdrawn |
STD-ACC-001 (revoke): a withdrawn link releases nothing; the attempt is logged. |
| 2 | false |
false |
any | false |
4 |
expired |
STD-ACC-001 (expiry): a link opened outside the holder’s period (J4: 2026-10-26 to 2026-11-09, Consent TrustDemoJ4Consent) releases nothing. |
| 3 | false |
true |
false |
false |
4 |
wrong-passcode |
STD-ACC-001 (passcode): a wrong passcode releases nothing and is logged at home (AuditEvent TrustDemoJ41WrongPasscode). |
| 4 | false |
true |
true |
true |
0 |
— | The manifest is released and the access logged (AuditEvent TrustDemoJ41Access). |
TD.DT.06 Does the receiver follow the VHL?
For one scanned VHL, decide whether the receiver requests the manifest or treats the family’s records like paper.
- Serves: J4.1 Read a family member’s records at the point of care abroad: Verify the HCERT and read the VHL at key 5 (
Task_Verify); HCERT verified? (Gateway_Verified); Not verified: treat records as paper (Task_Unverified); Request the manifest (ITI-YY5), signed (Task_Fetch) - Requirements: STT-VER-001, STT-VER-008, STT-VHL-009, STT-VHL-005
- Data elements: TD.J41.DE01 Requested at
- In the examples: Provenance TrustDemoJ41Received
- Computable form: PlanDefinition TrustDemoDT06; source vhl-follow.dmn, hit policy FIRST
| # | HCERT verification result (result) |
The VHL has expired (vhlExpired) |
Next step (next) |
Annotation |
|---|---|---|---|---|
| 1 | failed |
any | treat-as-paper |
STT-VER-008: the typed result names the step and reason, for example a DSC missing from the cached trust list (STT-VER-006). The clinician records why it was not verified. |
| 2 | verified |
true |
treat-as-paper |
STT-VHL-009: an expired link is not followed. |
| 3 | verified |
false |
fetch |
Request the manifest by ITI-YY5 with an HTTP Message Signature (STT-VHL-005); the portal then applies TD.DT.05. Provenance TrustDemoJ41Received. |