Record Identifier Variables (RXRECIDX, LINKIDX. The variable RXRECIDX uniquely identifies each record on the file. This 15-character variable is comprised of the following components: prescribed medicine event generated through the HC (positions 1-12) + enumeration number (positions 13-15). The prescribed medicine event generated through the HC (positions 1-12) can be used to link a prescribed medicine event to the conditions file and to other event files, via link files, and is provided on this file as the variable LINKIDX. (For more details on linking, please refer to section 5.2 and to the 2000 Appendix File.) The following hypothetical example illustrates the structure of these ID variables. This example illustrates a person in Round 1 of the household interview who reported having purchased Amoxicillin three times. The following example shows three acquisition level records, all having the same RXNDC (00364021802), for one person (DUPERSID=00002026) in one round. Only one NDC is associated with a prescribed medicine event because matching was performed at an event level, as opposed to an acquisition level. (For more details on matching, please see section 3.0). The LINKIDX (000020260083) remains the same for all three records, whereas the RXRECIDX (000020260083001, 000020260083002, 000020260083003) differs for all three records. 00002026 000020260083001 000020260083 00364021802 00002026 000020260083002 000020260083 00364021802 00002026 000020260083003 000020260083 00364021802
Appears in 1 contract
Samples: Data Use Agreement
Record Identifier Variables (RXRECIDX, LINKIDX. The variable RXRECIDX uniquely identifies each record on the file. This 15-character variable is comprised of the following components: prescribed medicine event generated through the HC (positions 1-12) + enumeration number (positions 13-15). The prescribed medicine event generated through the HC (positions 1-12) can be used to link a prescribed medicine event to the conditions file and to other event files, via link files, and is provided on this file as the variable LINKIDX. (For more details on linking, please refer to section Section 5.2 and to the 2000 1999 Appendix File.) The following hypothetical example illustrates the structure of these ID variables. This example illustrates a person in Round 1 of the household interview who reported having purchased Amoxicillin three times. The following example shows three acquisition level records, all having the same RXNDC (00364021802), for one person (DUPERSID=00002026) in one round. Only one NDC is associated with a prescribed medicine event because matching was performed at an event level, as opposed to an acquisition level. (For more details on matching, please see section Section 3.0). The LINKIDX (000020260083) remains the same for all three records, whereas the RXRECIDX (000020260083001, 000020260083002, 000020260083003) differs for all three records. 00002026 000020260083001 000020260083 00364021802 00002026 000020260083002 000020260083 00364021802 00002026 000020260083003 000020260083 00364021802
Appears in 1 contract
Samples: Data Use Agreement
Record Identifier Variables (RXRECIDX, LINKIDX. The variable RXRECIDX uniquely identifies each record on the file. This 15-character variable is comprised of the following components: prescribed medicine event generated through the HC (positions 1-12) + enumeration number (positions 13-15). The prescribed medicine event generated through the HC (positions 1-12) can be used to link a prescribed medicine event to the conditions file and to other event files, via link files, and is provided on this file as the variable LINKIDX. (For more details on linking, please refer to section 5.2 and to the 2000 2005 Appendix File.) The following hypothetical example illustrates the structure of these ID variables. This example illustrates a person in Round 1 of the household interview who reported having purchased Amoxicillin three times. The following example shows three acquisition acquisition-level records, all having the same RXNDC (0036402180200093310905), for one person (DUPERSID=00002026) in one round. Only one NDC is associated with a prescribed medicine event because matching was performed at an event level, as opposed to an acquisition level. (For more details on matching, please see section 3.0). The LINKIDX (000020260083) remains the same for all three records, whereas the RXRECIDX (000020260083001, 000020260083002, 000020260083003) differs for all three records. 00002026 000020260083001 000020260083 00364021802 00093310905 00002026 000020260083002 000020260083 00364021802 00093310905 00002026 000020260083003 000020260083 0036402180200093310905
Appears in 1 contract
Samples: Data Use Agreement
Record Identifier Variables (RXRECIDX, LINKIDX. The variable RXRECIDX uniquely identifies each record on the file. This 15-character variable is comprised of the following components: prescribed medicine event generated through the HC (positions 1-12) + enumeration number (positions 13-15). The prescribed medicine event generated through the HC (positions 1-12) can be used to link a prescribed medicine event to the conditions file and to other event files, via link files, and is provided on this file as the variable LINKIDX. (For more details on linking, please refer to section 5.2 and to the 2000 2003 Appendix File.) The following hypothetical example illustrates the structure of these ID variables. This example illustrates a person in Round 1 of the household interview who reported having purchased Amoxicillin three times. The following example shows three acquisition acquisition-level records, all having the same RXNDC (0036402180200093310905), for one person (DUPERSID=00002026) in one round. Only one NDC is associated with a prescribed medicine event because matching was performed at an event level, as opposed to an acquisition level. (For more details on matching, please see section 3.0). The LINKIDX (000020260083) remains the same for all three records, whereas the RXRECIDX (000020260083001, 000020260083002, 000020260083003) differs for all three records. 00002026 000020260083001 000020260083 00364021802 00093310905 00002026 000020260083002 000020260083 00364021802 00093310905 00002026 000020260083003 000020260083 0036402180200093310905
Appears in 1 contract
Samples: Data Use Agreement