Resource and element names are case-sensitive.

Prepare for the FHIR Proficiency Exam with our comprehensive study resources. Practice with flashcards, multiple choice questions, and detailed explanations. Excel in health IT standards!

Multiple Choice

Resource and element names are case-sensitive.

Explanation:
Resource and element names are case-sensitive. In FHIR, every resource type name (for example, Patient, Observation) and every element name (such as id, meta, birthDate, gender) is defined with exact capitalization. When you serialize a resource in JSON or XML, the keys must match exactly; a different capitalization means the processor won’t recognize the field and validation can fail. For example, the resourceType must be "Patient" with a capital P, and "birthDate" uses lowerCamelCase. If you write "BirthDate" or "birthdate," the system won’t treat it as the birthDate element. This rule holds across FHIR versions, so it is not version-dependent.

Resource and element names are case-sensitive. In FHIR, every resource type name (for example, Patient, Observation) and every element name (such as id, meta, birthDate, gender) is defined with exact capitalization. When you serialize a resource in JSON or XML, the keys must match exactly; a different capitalization means the processor won’t recognize the field and validation can fail. For example, the resourceType must be "Patient" with a capital P, and "birthDate" uses lowerCamelCase. If you write "BirthDate" or "birthdate," the system won’t treat it as the birthDate element. This rule holds across FHIR versions, so it is not version-dependent.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy