Which resource is a record of a healthcare consumer's choices, which permits or denies identified recipient(s) or recipient role(s) to perform actions within a policy context, for specific purposes and periods of time?

Which resource is a record of a healthcare consumer's choices, which permits or denies identified recipient(s) or recipient role(s) to perform actions within a policy context, for specific purposes and periods of time?

• A. DocumentManifest
• B. Composition
• C. Consent
• D. Provenance

Answer: (C)

The main idea is capturing a patient’s authorization for how their health information can be accessed and used, including who is allowed to act, for what purposes, under what policy, and for how long. The Consent resource in FHIR is designed exactly for this purpose: it records a consumer’s choices about data sharing and actions that may be taken, tying those permissions to specific recipients or recipient roles, a defined policy or purpose, and a defined time period. It can specify allowed actions (for example, read or transfer), who may perform them (individuals or organizations), and the time frame during which the permissions apply, all within a policy context. DocumentManifest groups together a set of documents for exchange, but it does not encode permissions or consent decisions. Composition represents a single structured clinical document, not the authorization to act on data. Provenance documents the history of who created or modified resources, not the patient’s or surrogate’s authorization preferences. Therefore, the resource that best fits the description of a record of choices permitting or denying actions within a policy context for specific purposes and periods is the Consent resource.

The main idea is capturing a patient’s authorization for how their health information can be accessed and used, including who is allowed to act, for what purposes, under what policy, and for how long. The Consent resource in FHIR is designed exactly for this purpose: it records a consumer’s choices about data sharing and actions that may be taken, tying those permissions to specific recipients or recipient roles, a defined policy or purpose, and a defined time period. It can specify allowed actions (for example, read or transfer), who may perform them (individuals or organizations), and the time frame during which the permissions apply, all within a policy context.

DocumentManifest groups together a set of documents for exchange, but it does not encode permissions or consent decisions. Composition represents a single structured clinical document, not the authorization to act on data. Provenance documents the history of who created or modified resources, not the patient’s or surrogate’s authorization preferences. Therefore, the resource that best fits the description of a record of choices permitting or denying actions within a policy context for specific purposes and periods is the Consent resource.