Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

SCDM CCDM Exam - Topic 3 Question 17 Discussion

A relational database has tables for PATIENT_DEMOGRAPHY and VITAL_SIGNS data collected during a visit. The primary key for the VITAL_SIGNS table is a composite key that includes the unique patient identifier, visit number, and vital signs parameter name. The two tables are joined on the patient identifier. What will be the number of records in the result set?
C) One record per patient per visit per vital sign parameter
A) One record per patient
B) One record per visit
D) One record per patient per visit

SCDM CCDM Exam - Topic 3 Question 17 Discussion

Actual exam question for SCDM's CCDM exam
Question #: 17
Topic #: 3
[All CCDM Questions]

A relational database has tables for PATIENT_DEMOGRAPHY and VITAL_SIGNS data collected during a visit. The primary key for the VITAL_SIGNS table is a composite key that includes the unique patient identifier, visit number, and vital signs parameter name. The two tables are joined on the patient identifier. What will be the number of records in the result set?

Show Suggested Answer Hide Answer
Suggested Answer: C

In a relational database structure, each record in a table is uniquely identified by a primary key. In this case, the VITAL_SIGNS table uses a composite primary key consisting of:

Patient Identifier,

Visit Number, and

Vital Signs Parameter Name.

This means each record represents a unique measurement of a specific parameter (e.g., blood pressure, pulse) for a patient at a specific visit.

When joining PATIENT_DEMOGRAPHY and VITAL_SIGNS tables on the patient identifier, the result set will include one record for every combination of patient, visit, and parameter --- i.e., one record per patient per visit per vital sign parameter.

Therefore, option C correctly describes the expected number of records.

Reference (CCDM-Verified Sources):

SCDM GCDMP, Chapter: Database Design and Build, Section 5.2 -- Primary and Foreign Key Relationships in Relational Models

CDISC SDTM Implementation Guide, Section 5.3 -- Observation-Level Data Structures

ICH E6(R2) GCP, Section 5.5.3 -- Data Organization and Integration Principles


Contribute your Thoughts:

0/2000 characters
Eleonora
3 days ago
But what about D? One record per visit seems simpler.
upvoted 0 times
...
Anglea
8 days ago
I agree, C makes sense. More details per visit.
upvoted 0 times
...
Dante
14 days ago
I think it's C. Each vital sign counts.
upvoted 0 times
...
Evangelina
19 days ago
Just to clarify, each visit can have multiple vital signs recorded.
upvoted 0 times
...
Gail
24 days ago
I'm not so sure about this. Can we really have multiple records for one visit?
upvoted 0 times
...
Alva
29 days ago
Wait, why would it be C? Isn't it just one record per visit?
upvoted 0 times
...
Olive
1 month ago
Totally agree, C makes the most sense here.
upvoted 0 times
...
Lindsey
1 month ago
C is correct! Each patient can have multiple vital signs per visit.
upvoted 0 times
...
Desmond
1 month ago
I remember we discussed how joins work, and since we're joining on the patient identifier, it seems like we might end up with multiple records per visit, so I’m leaning towards C.
upvoted 0 times
...
Lynelle
2 months ago
I feel like I practiced a similar question, and it was about visits, so could it be D? But then again, the vital signs part confuses me.
upvoted 0 times
...
Harrison
2 months ago
I'm not entirely sure, but I remember something about composite keys meaning more detailed records, so maybe it's C too?
upvoted 0 times
...
Eleni
2 months ago
I think the answer might be C because the composite key suggests we will have multiple records for each vital sign parameter.
upvoted 0 times
...

Save Cancel