Which type of version is usually managed by a server and changes each time the resource itself changes?

• A. Record Version
• B. Business Version
• C. FHIR Version
• D. User Version

Answer: (A)

The server-managed per-resource version is the record version. In FHIR, every resource carries a versionId in its metadata, and the server increments this version each time the resource’s stored state changes. This versionId lets clients refer to a particular state of the resource, enables optimistic locking (for example, using If-Match with the versionId), and supports history retrieval to see all past versions.

This is different from a FHIR release version (the specification version, like R4 or STU3), which applies to the standard itself, not to an individual resource’s state. It’s also not a business or user-defined version, which aren’t standardized concepts for tracking resource changes.