IPTp-SP Digital Support System Implementation Guide
0.1.0 - ci-build
IPTp-SP Digital Support System Implementation Guide, published by IPTp-SP Digital Support System Implementation Team. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/daviemukungi/IPTp-FHIR-implementationIG/ and changes regularly. See the Directory of published versions
| Official URL: http://iptp.kemri.go.ke/fhir/ValueSet/iptp-message-category-vs | Version: 0.1.0 | |||
| Draft as of 2026-06-30 | Computable Name: IPTpMessageCategoryVS | |||
Categories of outbound/inbound SMS messages exchanged on the dedicated short code (25332) or the InfoAFYA sender ID
References
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system version 📦0.1.0| Code | Display | Definition |
| reminder-t3 | T-3 Reminder | Reminder sent 3 days before dose date |
| reminder-t0 | T-0 Reminder | Reminder sent on dose day |
| reminder-24h | 24h Nudge | 24-hour follow-up nudge |
| reminder-72h | 72h Escalation | 72-hour escalation to CHP queue |
| msg-onboarding-enrollment | Onboarding: Enrollment Confirmation | Onboarding message 1 sent on short code immediately after USSD enrollment |
| msg-onboarding-how-it-works | Onboarding: How It Works | Onboarding message 2 |
| msg-onboarding-how-to-take | Onboarding: How to Take SP | Onboarding message 3 |
| msg-onboarding-safety-bridge | Onboarding: Safety + InfoAFYA Bridge | Onboarding message 4 |
| msg-confirmation-ack-taken | Confirmation Ack: Took It | Sent after patient replies 1 (took it) |
| msg-confirmation-ack-pending | Confirmation Ack: Not Yet | Sent after patient replies 2 (not yet) |
| msg-issue-problem-type | Issue Flow: Problem Type Prompt | Have-an-issue step 1 prompt |
| msg-issue-side-effect-severity | Issue Flow: Side Effect Severity Prompt | Have-an-issue side-effect severity prompt |
| msg-issue-mild-response | Issue Flow: Mild Side Effect Response | Response sent for mild side effects |
| msg-issue-severe-response | Issue Flow: Severe Side Effect Response | Response sent for severe side effects |
| msg-issue-lost-medicine-response | Issue Flow: Lost Medicine Response | Response sent for lost medicine reports |
| msg-issue-other-prompt | Issue Flow: Other - Free Text Prompt | Prompt asking patient to type their concern |
| msg-issue-other-ack | Issue Flow: Other - Auto-Reply | Auto-reply after free-text concern received |
| msg-stop-ack | STOP Acknowledgement | Sent when patient texts STOP |
| msg-infoafya-trust | InfoAFYA: Trust | 24-48h post enrollment |
| msg-infoafya-autonomy | InfoAFYA: Autonomy Transition | 3-5 days post DOT |
| msg-infoafya-norm | InfoAFYA: Norm Reinforcement | 7 days before next dose |
| msg-infoafya-identity | InfoAFYA: Identity Reinforcement | 3-5 days after Dose 2 confirmation |
| msg-infoafya-reassurance | InfoAFYA: Side-Effect Reassurance | Mid-cycle window between two IPTp doses |
| msg-infoafya-completion | InfoAFYA: Completion Mindset | 7 days before final cycle |
| msg-infoafya-anc-continuity | InfoAFYA: ANC Continuity | After final dose confirmation |
| msg-feedback-prompt | Feedback Prompt | Sent 5 days after final dose confirmation |
| msg-feedback-yes-ack | Feedback Ack: Yes | Sent when patient replies 1 (Yes, supported) |
| msg-feedback-no-ack | Feedback Ack: No | Sent when patient replies 2 (No), requests suggestions |
Expansion performed internally based on codesystem IPTp-SP Code System v0.1.0 (CodeSystem)
This value set contains 28 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | reminder-t3 | T-3 Reminder | Reminder sent 3 days before dose date | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | reminder-t0 | T-0 Reminder | Reminder sent on dose day | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | reminder-24h | 24h Nudge | 24-hour follow-up nudge | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | reminder-72h | 72h Escalation | 72-hour escalation to CHP queue | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-onboarding-enrollment | Onboarding: Enrollment Confirmation | Onboarding message 1 sent on short code immediately after USSD enrollment | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-onboarding-how-it-works | Onboarding: How It Works | Onboarding message 2 | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-onboarding-how-to-take | Onboarding: How to Take SP | Onboarding message 3 | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-onboarding-safety-bridge | Onboarding: Safety + InfoAFYA Bridge | Onboarding message 4 | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-confirmation-ack-taken | Confirmation Ack: Took It | Sent after patient replies 1 (took it) | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-confirmation-ack-pending | Confirmation Ack: Not Yet | Sent after patient replies 2 (not yet) | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-problem-type | Issue Flow: Problem Type Prompt | Have-an-issue step 1 prompt | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-side-effect-severity | Issue Flow: Side Effect Severity Prompt | Have-an-issue side-effect severity prompt | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-mild-response | Issue Flow: Mild Side Effect Response | Response sent for mild side effects | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-severe-response | Issue Flow: Severe Side Effect Response | Response sent for severe side effects | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-lost-medicine-response | Issue Flow: Lost Medicine Response | Response sent for lost medicine reports | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-other-prompt | Issue Flow: Other - Free Text Prompt | Prompt asking patient to type their concern | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-issue-other-ack | Issue Flow: Other - Auto-Reply | Auto-reply after free-text concern received | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-stop-ack | STOP Acknowledgement | Sent when patient texts STOP | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-trust | InfoAFYA: Trust | 24-48h post enrollment | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-autonomy | InfoAFYA: Autonomy Transition | 3-5 days post DOT | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-norm | InfoAFYA: Norm Reinforcement | 7 days before next dose | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-identity | InfoAFYA: Identity Reinforcement | 3-5 days after Dose 2 confirmation | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-reassurance | InfoAFYA: Side-Effect Reassurance | Mid-cycle window between two IPTp doses | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-completion | InfoAFYA: Completion Mindset | 7 days before final cycle | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-infoafya-anc-continuity | InfoAFYA: ANC Continuity | After final dose confirmation | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-feedback-prompt | Feedback Prompt | Sent 5 days after final dose confirmation | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-feedback-yes-ack | Feedback Ack: Yes | Sent when patient replies 1 (Yes, supported) | ||
http://iptp.kemri.go.ke/fhir/CodeSystem/iptp-code-system | msg-feedback-no-ack | Feedback Ack: No | Sent when patient replies 2 (No), requests suggestions |
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 |