This page is part of the FHIR Specification v4.1.0: R4B Ballot. About the R4B version of FHIR. The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

• Content
• Examples
• Detailed Descriptions
• Mappings
• Profiles & Extensions
• R3 Conversions

6.2.10 Resource Consent - Examples

Community Based Collaborative Care Work Group

Maturity Level: N/A

Standards Status: Informative

Security Category: Patient

Compartments: Patient

These are various examples that have been used to drive the creaion of the Consent resource.

Example Name	id	Format
General Consent Example	consent-example-basic	XML	JSON	Turtle
Consent withholding access	consent-example-Out	XML	JSON	Turtle
Consent withholding access to data for Treatment exept for Emergency Treatment	consent-example-Emergency	XML	JSON	Turtle
Withhold or withdraw consent for disclosure of records related to specific domain (e.g. DI, LAB, etc.)	consent-example-notThis	XML	JSON	Turtle
Withhold or withdraw consent for disclosure of a specific timeframe	consent-example-notTime	XML	JSON	Turtle
Withhold or withdraw consent for disclosure to a specific provider organization	consent-example-notOrg	XML	JSON	Turtle
Withhold or withdraw consent for disclosure to a specific provider agent (an individual within an organization)	consent-example-notThem	XML	JSON	Turtle
Withhold or withdraw consent for disclosure of records that were authored by a specific organization (or service delivery location).	consent-example-notAuthor	XML	JSON	Turtle
Patient grants access to a specified individual for read-only access	consent-example-grantor	XML	JSON	Turtle
Example of Patients Know Best Usage	consent-example-pkb	XML	JSON	Turtle
Template for recording a Smart on FHIR Authorization	consent-example-smartonfhir	XML	JSON	Turtle
Consent Example with a signature	consent-example-signature	XML	JSON	Turtle

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.