> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/sdmx-dci-member-example.md). # SDMX: DCI Member example ### DCI Member Statistics Data Structure Definition (DSD) #### Data Structure **ID:** `DCI_MEMBER_STATISTICS` **Name:** DCI Member Aggregated Statistics **Description:** This Data Structure Definition defines aggregated statistics generated from the DCI Core **Member** data object. It enables interoperable exchange of social protection statistics using SDMX. Individual Member and Person records are not exchanged through this dataset; instead, observations represent aggregated counts derived from Member attributes and the embedded Person entity. {% hint style="info" %} This is an illustrative example. Countries should adapt and extend it based on their early warning and social protection systems, the analyses they intend to perform, and the indicators they need to monitor. Where a required dimension already exists in the DCI core models, we recommend reusing it to maximize interoperability. Additional dimensions, including post-intervention outcome indicators (e.g., coverage rate, payment timing, poverty status change, or recovery rate), are not defined in this example and should be introduced through country-level extensions or implementation-specific data structure definitions (DSDs), as appropriate. {% endhint %} #### Dimensions Dimensions define the statistical classification of observations. The combination of dimensions forms the series key. | Component | ID | Description | Representation | | --------- | ------------------- | ------------------------------------------------------------------- | --------------------------------- | | Dimension | `REF_AREA` | Geographic area where members are registered | DCI Administrative Area Code List | | Dimension | `SEX` | Sex of the person associated with the member | CL\_SEX | | Dimension | `DISABILITY_STATUS` | Whether the person has a disability | CL\_DISABILITY\_STATUS | | Dimension | `AGE_GROUP` | Age category derived from Person.birthDate | CL\_AGE\_GROUP | | Dimension | `TIME_PERIOD` | Reference period of the observation | ISO 8601 | | Dimension | `DENOMINATOR_TYPE` | The type of affected population profile used as the local baseline. | CL\_DENOMINATOR\_TYPE | ### Code Lists #### REF\_AREA Source: `Member.demographic_info.address.region_code` Example: | Code | Name | | ------- | ---------- | | AREA001 | District A | | AREA002 | District B | | AREA003 | District C | #### SEX Source: `Member.demographic_info.sex` Code List: `CL_SEX` | Code | Name | | ---- | ------- | | F | Female | | M | Male | | U | Unknown | #### DISABILITY\_STATUS Source: `Member.demographic_info.self_id_disability` Code List: `CL_DISABILITY_STATUS` | Code | Name | | ----- | ------------------------- | | TRUE | Person with disability | | FALSE | Person without disability | | NA | Not available | #### AGE\_GROUP Derived from: `Member.demographic_info.birth_date` Code List: `CL_AGE_GROUP` | Code | Description | | ------ | ------------------ | | LT5 | Less than 5 years | | Y5T17 | 5 to 17 years | | Y18T64 | 18 to 64 years | | GE65 | 65 years and above | | ALL | All ages | #### DENOMINATOR\_TYPE Derived from: Response Profile Metadata Configuration Code List: `CL_DENOMINATOR_TYPE`
IDDescription
IPC_3_PLUSPopulation classified under Integrated Food Security Phase Classification Phase 3 or higher.
STRUCT_DAMAGEHouseholds with verified structural property damage within the emergency buffer zone.
GEOG_DISPLACEDTotal estimated registry of individuals displaced within the designated target area.
#### Measures | ID | Description | | -------------- | ----------------- | | `OBS_VALUE` | Number of Members | | `UNIT_MEASURE` | Persons | The observation value represents the aggregated count of Member records matching the selected dimensions. #### Attributes
AttributeDescriptionAttachement Level
OBS_STATUSObservation status (estimated, provisional, final)Observation
SOURCEData providerDataset
CONFIDENTIALITYConfidentiality classificationObservation
EXCLUSION_INDBoolean indicator flagging if this affected area has zero registered beneficiaries.Observation
NON_MATCH_COUNTRaw count of records that failed verification routines during data cross-referencing.Observation
COVERAGE_RATEPercentage showing recipients as a share of the local affected population profile.Observation
PROFILE_DENOMINATOR_DEFText definition detailing the custom local denominator parameters for this profile.Dataset
LAST_VERIFIED_DATEThe date the beneficiary's eligibility status or registry entry was last updated, verified, or recertified on the SP side.Observation
### Series Key The series key is created from the ordered dimensions: ``` REF_AREA.SEX.DISABILITY_STATUS.AGE_GROUP.DENOMINATOR_TYPE ``` Example: ``` AREA001.F.TRUE.ALL.IPC_3_PLUS ``` means: | Dimension | Value | | ------------------ | ----------------------------------- | | REF\_AREA | AREA001 | | SEX | Female | | DISABILITY\_STATUS | Disability | | AGE\_GROUP | All ages | | DENOMINATOR\_TYPE | Population in IPC Phase 3 or higher | ```json { "meta": { "schema": "https://githubusercontent.com", "id": "IREP000012", "prepared": "2026-09-22T08:45:00Z", "sender": { "id": "SP" }, "receiver": { "id": "DRM" } }, "data": { "dataSets": [ { "action": "Information", "structureRef": "DCI_MEMBER_STATISTICS", // 1. DATASET LEVEL ATTRIBUTES (The profile denominator definition goes here) "attributes": { "SOURCE": "EWS-Shock-Tracker-V2", "PROFILE_DENOMINATOR_DEF": "All households residing within landslide zone buffers with structural damage greater than 40% certified by local municipal engineers." }, // 2. THE MULTI-DIMENSIONAL DATA GRID "observations": { // Series Key: REF_AREA . SEX . DISABILITY_STATUS . AGE_GROUP . DENOMINATOR_TYPE "AREA001.F.TRUE.ALL.IPC_3_PLUS": { "OBS_VALUE": 1250, // Observation-level metrics "EXCLUSION_IND": false, "NON_MATCH_COUNT": 45, "COVERAGE_RATE": 82.5, "OBS_STATUS": "A", "CONFIDENTIALITY": "F" }, "AREA002.M.FALSE.LT5.IPC_3_PLUS": { "OBS_VALUE": 0, // This area has a zero count, triggering the exclusion indicator "EXCLUSION_IND": true, "NON_MATCH_COUNT": 12, "COVERAGE_RATE": 0.0, "OBS_STATUS": "A", "CONFIDENTIALITY": "F" } } } ] } } ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/sdmx-dci-member-example.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.