Data & schema semantics

x-fhir-operation-definition

`x-fhir-operation-definition` appears on operations. Its value is a string. Used by 2 providers across 15 OpenAPI documents. Observed values include `https://fhir-ehr.cerner.com/r4/OperationDefinition/binary-autogen-ccd-if`, `https://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-credit`, `https://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-modify`, `https://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-create`. 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.
21 occurrences
15 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 21

What its value looks like

Value shapeOccurrences
string21

Observed values

Sampled from the specifications, most frequent first.

https://fhir-ehr.cerner.com/r4/OperationDefinition/binary-autogen-ccd-ifhttps://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-credithttps://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-modifyhttps://fhir-ehr.cerner.com/r4/OperationDefinition/charge-item-createhttp://hl7.org/fhir/us/core/OperationDefinition/docrefhttps://fhir-ehr.cerner.com/r4/OperationDefinition/organization-get-cg-for-mrcuhttps://spec.smarthealth.cards/artifacts/operation-patient-i-health-cards-issue.

Providers publishing it

All 2.

cerneroracle-health

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.