Data & schema semantics

x-practice-access

`x-practice-access` appears on operations. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `share_patients" need to be set for data access among practice`, `Data access among practice is available`, `share_appointment_profiles" need to be set for data access`, `share_consent_forms" need to be set for data access among`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
316 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 316

What its value looks like

Value shapeOccurrences
string316

Observed values

Sampled from the specifications, most frequent first.

share_patients" need to be set for data access among practiceData access among practice is availableshare_appointment_profiles" need to be set for data accessshare_consent_forms" need to be set for data access amongshare_communications" need to be set for data access amongshare_clinical_templates" need to be set for data accessshare_reminder_profile" need to be set for data accessshare_inventory" need to be set for data access among practice

Providers publishing it

All 1.

drchrono

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the data & schema semantics job.