Model 2.0IG 3.4Content 1.0.0Curated educational coverage
VS / findings
Vital Signs
Repeated measurements make the difference between a collection form and an observation table visible.
Turn measurements into observations
A single encounter object can contain several measurements. Flattening it into one wide record hides the repeating measurement structure. Follow the input observation ID through the mapping manifest to see which source observation produced each output row.
Look inside the structure
8 selected variables. Follow an identifier to its lesson.
Scroll this table horizontally to inspect every field, or read as records.
| Identifier | Domain | Teaching explanation | Example JSON type | Example value |
|---|---|---|---|---|
| STUDYID | VS | The study identifier keeps the vital-signs walkthrough within fictional study CLD-SYN-001. Carry it across the repeated observation rows produced from the synthetic input. | string | CLD-SYN-001 |
| DOMAIN | VS | The value VS identifies the vital-signs context in this lesson. The walkthrough represents separate observations as rows, each with a test code, result, unit and timing context. | string | VS |
| USUBJID | VS | The fictional subject key connects the repeated vital-signs rows to their participant. It repeats across observations, so a subject-level join must preserve each observation’s test and timing context. | string | SYN-001 |
| VSSEQ | VS | This example sequence number separates rows inside the VS teaching extract. It is useful for referring to an observation, but the original collection identifier is retained separately in the mapping manifest. | number | 1 |
| VSTESTCD | VS | The example token identifies one type of fictional observation in the walkthrough. It is an authored teaching token, not verified terminology. | string | DEMO_A |
| VSORRES | VS | The string is the observation's recorded representation. We keep it as text even when it looks numeric, so the lesson separates representation from later interpretation. | string | 72 |
| VSORRESU | VS | An explicitly fictional unit accompanies the result in the example. It demonstrates why a result without contextual fields is ambiguous. | string | DEMO_UNIT |
| VSDTC | VS | This string preserves the recorded date of an authored observation. It is not a processing timestamp or a timezone-normalized instant. | string | 2025-02-03 |
See the relationship in an example
Follow the source
Original ClinDevLab explanations. Publisher material is linked, not reproduced. Reviewed 8 October 2026.
- SDTM 2.0https://www.cdisc.org/standards/foundational/sdtm/sdtm-v2-0 · CDISC · 2.0 · accessed 2026-10-08
- SDTMIG 3.4https://www.cdisc.org/standards/foundational/sdtmig/sdtmig-v3-4 · CDISC · 3.4 · accessed 2026-10-08