Lesson 01.03
Data types, cardinality & flags
Decode the compact notation used throughout every resource page.
Real-World Example
A laboratory code has two translations
An Observation.code can carry a LOINC Coding and a local laboratory Coding inside the same CodeableConcept, plus clinician-friendly text.
What You Will Learn
- Interpret 0..1, 1..1 and 0..*
- Recognize Must Support, modifier and summary flags
- Choose Identifier, Coding, CodeableConcept and Reference correctly
Step-by-Step Explanation
Read cardinality as a contract
The first number is the minimum; the second is the maximum. Profiles may tighten but cannot loosen the base definition.
Match the semantic data type
Identifier is assigned identity; Coding carries a system/code pair; CodeableConcept can carry multiple codings plus text; Reference links resources.
Treat flags as behavior
Modifier elements can change interpretation. Must Support gains operational meaning from the applicable implementation guide.
Inspect and practice
{
"resourceType": "Patient",
"id": "ronaldo",
"identifier": [
{
"system": "https://gotham.example.org/mrn",
"value": "GMH-1007"
}
],
"name": [
{
"family": "Ronaldo"
}
]
}Key Concept / Interview Takeaway
Never interpret Must Support as “required in every instance.” Cardinality and the implementation guide define the actual obligation.
Loading 10 questions
Ask your instructor
Data types, cardinality & flags
Only you and the authorized instructor can view this conversation. Other learners cannot see your messages. Do not include patient information, passwords or payment details.
Loading private conversation...