STATISTICAL LINKAGE KEY - SEQUENTIAL MATCH CODE
ABS short name: PSN_SLK_MATCH
ABS Template reference (Child URL): Column C
METeOR Technical name: N/A
METeOR identifier: N/A
METeOR link: N/A
METeOR definition: N/A
Note: This is an additional ABS data element, requested for the following purpose: To accurately connect episodes of preschool to a child record.
Scope
Inclusions: Children who have experienced episodes of preschool at multiple service providers, during the reference period.
Exclusions: Child records that have only one discrete episode record.
Underlying Concepts
Concept: Statistical Linkage Key (SLK) – Sequential Match Code, identifies where two or more episode records relate to the SLK of one child. Within a jurisdictional dataset, the SLK sequential match code must increase by 1 for each child with episodes of preschool at multiple service providers, during the reference period.
Nominal definition: N/A.
Operational definition: N/A
Supporting data elements: The following data element is used to support the matching statistical linkage keys:
Conceptual issues:
- This data element facilitates correct handling of complex scenarios where duplicate SLKs are supplied in a given dataset. Duplicate SLKs flagged as non-coincidental matches (using this SLK sequential match code) are processed as one child. Duplicate SLKs identified as coincidental matches are processed as separate children.
Standard Jurisdictional Output Categories
Representation class: Code
Data type: Number
Format: NNNNN, for example 2
Maximum character length: 5
Classification values:
Blank - Non matching SLK
1 to 99,999 - Matching SLK number (sequential number corresponding to the number of children with preschool episode records at multiple service providers)
2.1.1 LEGAL VALUE CHECKS
|
|
 | Edit specifications | Edit resolution |
|
| 1. | If SLK Match is not numeric or Blank | Provide a valid SLK Match. |
|
| 2. | If character length is not sequential compared with the preceding matched SLK. | Provide SLK Match numbers that increment by units of 1. |
|
| 3. | If character length is greater than 5. | Provide a valid SLK Match. |
|
Guide for Use
Counting rules:
Refer to the table below for further detail regarding correct use of matching SLK codes.
MATCHING STATISTICAL LINKAGE KEY, SCENARIOS AND INSTRUCTIONS
|
|
Matching scenario | Observation | Validity status | Jurisdiction action | Matching SLK code |
|
1. Child record has no matching SLK anywhere else
in the dataset. | All records that do not have a matching SLK. | Unique SLK | No action | Blank:
Non Matching SLK |
|
| 2. Coincidental match of SLKs produced for 2 discrete children in the same dataset. Can be across the same or different service providers. | Confirm that matched SLKs represent
different children. This may entail cross-checking other characteristics of the child
such as address, indigenous status etc. | Matching SLK but valid multiple children i.e. coincidental SLKs for separate children.
| No action | Blank:
Non Matching SLK |
|
3. Non-coincidental match of SLKs i.e. same child with preschool episodes at different service providers in
the same dataset. | Confirm that matched SLKs represent
the same child. This may entail cross-checking other
characteristics of the child such as address, indigenous status etc. | Matching SLK for the same child i.e. non-coincidental SLKs. | Set SLK Sequential Match
Code
Note: Each child will have a unique SLK sequential match code to enable grouping of his/her episodes across multiple service providers within the dataset. | Set sequential SLK Match Code against all episodes for that child, to indicate that they are linked, i.e.
Assign ‘1’ – to all episodes of the first matched child.
Assign ‘2’ – to all episodes of the 2nd matched child.
Assign ‘3’ – to all episodes of the 3rd matched child.
Operationally this will necessitate two or more occurrences of the same SLK Match code (one for each episode) within the dataset. |
|
Other Information
Related aggregate data elements: No related aggregate data element.
Print Page
Print All