R4 Ballot #1 (Mixed Normative/Trial use) Release 4

This page is part of the FHIR Specification (v3.3.0: (v4.0.1: R4 Ballot 2). - Mixed Normative and STU ) in it's permanent home (it will always be available at this URL). 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 R2

5.4 Resource OperationDefinition - Content

FHIR Infrastructure Work Group Maturity Level : 4 N   Normative (from v4.0.0) Security Category : Anonymous Compartments : Not linked to any defined compartments
Normative Candidate Note:
This page is candidate normative content for R4 in has been approved as part of an ANSI standard. See the Conformance Package . Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made. for further details.

A formal computable definition of an operation (on the RESTful interface) or a named query (using the search interaction).

5.4.1 Scope and Usage

The OperationDefinition resource provides a formal computable definition of an operation or a named query . The OperationDefinition serves two principal purposes:

  • To allow for automatic determination of system compatibility
  • To allow for dynamic generation of forms to drive the operations

See below for further information about these, and about how operations and named queries are executed.

5.4.2 Boundaries and Relationships

OperationDefinitions are published to define operations that servers can implement in a common fashion. The FHIR specification itself describes some (see below), and other organizations (including IHE, national programs, jurisdictions and vendors) are able to publish additional OperationDefinitions.

OperationDefinition resources are referred to from two different places:

  • From a CapabilityStatement , to declare what operations a system does or should implement
  • From another OperationDefinition resource. This allows for a server to describe a limited implementation of a standard operation, or to allow traceability if the server has to rename the operation due to a name clash

This resource is referenced by capabilitystatement CapabilityStatement , CarePlan , Communication , FamilyMemberHistory , itself and Procedure

5.4.3 Resource Content

Structure

?!
Name Flags Card. Type Description & Constraints doco
. . OperationDefinition I N DomainResource Definition of an operation or a named query
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 0..1 uri Canonical identifier for this operation definition, represented as a URI (globally unique)
. . . version Σ 0..1 string Business version of the operation definition
. . . name Σ I 1..1 string Name for this operation definition (computer friendly)
. . . title Σ 0..1 string Name for this operation definition (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . kind Σ 1..1 code operation | query
OperationKind ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 0..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher
. . . description 0..1 markdown Natural language description of the operation definition
. . . useContext Σ TU 0..* UsageContext The context that the content is intended to support
. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for operation definition (if applicable)
Jurisdiction ValueSet ( Extensible )
. . . purpose 0..1 markdown Why this operation definition is defined
. . . affectsState Σ 0..1 boolean Whether content is unchanged changed by the operation
. . . code Σ 1..1 code Name used to invoke the operation
. . . comment 0..1 markdown Additional information about use
. . . base Σ 0..1 canonical ( OperationDefinition ) Marks this as a profile of the base
. . . resource Σ 0..* code Types this operation applies to
ResourceType ( Required )
. . . system Σ 1..1 boolean Invoke at the system level?
. . . type Σ 1..1 boolean Invoke at the type level?
. . . instance Σ 1..1 boolean Invoke on an instance?
. . . inputProfile 0..1 canonical ( StructureDefinition ) Validation information for in parameters
. . . outputProfile 0..1 canonical ( StructureDefinition ) Validation information for out parameters
. . . parameter I 0..* BackboneElement Parameters for the operation/query
+ Rule: Either a type must be provided, or parts
+ Rule: A search type can only be specified for parameters of type string
+ Rule: A targetProfile can only be specified for parameters of type Reference or Canonical
. . . . name 1..1 code Name in Parameters.parameter.name or in URL
. . . . use 1..1 code in | out
OperationParameterUse ( Required )
. . . . min 1..1 integer Minimum Cardinality
. . . . max 1..1 string Maximum Cardinality (a number or *)
. . . . documentation 0..1 string Description of meaning/use
. . . . type I 0..1 code What type this parameter has
FHIRAllTypes ( Required )
. . . . targetProfile 0..* canonical ( StructureDefinition ) If type is Reference, Reference | canonical, allowed targets
. . . . searchType I 0..1 code number | date | string | token | reference | composite | quantity | uri | special
SearchParamType ( Required )
. . . . binding 0..1 BackboneElement ValueSet details if this is coded
. . . . . strength 1..1 code required | extensible | preferred | example
BindingStrength ( Required )
. . . . valueSet[x] . valueSet 1..1 canonical ( ValueSet ) Source of value set
. . . . referencedFrom TU 0..* BackboneElement References to this parameter
. . . . . valueSetUri source 1..1 uri string Referencing parameter
. . . . valueSetCanonical . sourceId 0..1 canonical string Element id of reference
. . . . part I 0..* see parameter Parts of a nested Parameter
. . . overload 0..* BackboneElement Define overloaded variants for when generating code
. . . . parameterName 0..* string Name of parameter to include in overload
. . . . comment 0..1 string Comments to go on overload

doco Documentation for this format

UML Diagram ( Legend )

OperationDefinition ( DomainResource ) An absolute URI that is used to identify this operation definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this operation definition is (or will be) published published. This URL can be the target of a canonical reference. It SHALL remain the same when the operation definition is stored on different servers url : uri [0..1] The identifier that is used to identify this version of the operation definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the operation definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A natural language name identifying the operation definition. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the operation definition title : string [0..1] The status of this operation definition. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of an artifact. (Strength=Required) PublicationStatus ! » Whether this is an operation or a named query kind : code [1..1] « Whether an operation is a normal operation or a query. (Strength=Required) OperationKind ! » A Boolean value to indicate that this operation definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The date (and optionally time) when the operation definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the operation definition changes date : dateTime [0..1] The name of the organization or individual that published the operation definition publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the operation definition from a consumer's perspective description : markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate operation definition instances useContext : UsageContext [0..*] A legal or geographic region in which the operation definition is intended to be used jurisdiction : CodeableConcept [0..*] « Countries and regions within which this artifact is targeted for use use. (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this operation definition is needed and why it has been designed as it has purpose : markdown [0..1] Operations that have affects state = false (see [HTTP specification definition of idempotent](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html)) may be invoked by performing an HTTP GET Whether the operation instead of a POST affects state. Side effects such as producing audit trail entries do not count as 'affecting state' affectsState : boolean [0..1] The name used to invoke the operation code : code [1..1] Additional information about how to use this operation or named query comment : markdown [0..1] Indicates that this operation definition is a constraining profile on the base base : canonical [0..1] « OperationDefinition » The types on which this operation can be executed resource : code [0..*] « One of the resource types defined as part of this version of FHIR. (Strength=Required) ResourceType ! » Indicates whether this operation or named query can be invoked at the system level (e.g. without needing to choose a resource type for the context) system : boolean [1..1] Indicates whether this operation or named query can be invoked at the resource type level for any given resource type level (e.g. without needing to choose a specific resource id for the context) type : boolean [1..1] Indicates whether this operation can be invoked on a particular instance of one of the given types instance : boolean [1..1] Additional validation information for the in parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource as a whole inputProfile : canonical [0..1] « StructureDefinition » Additional validation information for the out parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource outputProfile : canonical [0..1] « StructureDefinition » Parameter The name of used to identify the parameter name : code [1..1] Whether this is an input or an output parameter use : code [1..1] « Whether an operation parameter is an input or an output parameter. (Strength=Required) OperationParameterUse ! » The minimum number of times this parameter SHALL appear in the request or response min : integer [1..1] The maximum number of times this element is permitted to appear in the request or response max : string [1..1] Describes the meaning or use of this parameter documentation : string [0..1] The type for this parameter type : code [0..1] « A list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types Types. (Strength=Required) FHIRAllTypes ! » If Used when the type is "Reference", then targetProfile lists "Reference" or "canonical", and identifies a one profile structure or more profiles implementation Guide that applies to the Reference target of the reference this parameter refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can refer be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the target resource SHALL conform to at least one profile defined in the implementation guide targetProfile : canonical [0..*] « StructureDefinition » How the parameter is understood as a search parameter. This is only used if the parameter type is 'string' searchType : code [0..1] « Data types allowed to be used for search parameters. (Strength=Required) SearchParamType ! » Binding Indicates the degree of conformance expectations associated with this binding - that is, the degree to which the provided value set must be adhered to in the instances strength : code [1..1] « Indication of the degree of conformance expectations associated with a binding. (Strength=Required) BindingStrength ! » Points to the value set or external definition (e.g. implicit value set) that identifies the set of codes to be used valueSet[x] valueSet : Type canonical [1..1] « uri | canonical ( ValueSet ) » ReferencedFrom The name of the parameter or dot-separated path of parameter names pointing to the resource parameter that is expected to contain a reference to this resource source : string [1..1] The id of the element in the referencing resource that is expected to resolve to this resource sourceId : string [0..1] Overload Name of parameter to include in overload parameterName : string [0..*] Comments to go on overload comment : string [0..1] Binds to a value set if this parameter is coded (code, Coding, CodeableConcept) binding [0..1] Identifies other resource parameters within the operation invocation that are expected to resolve to this resource referencedFrom [0..*] The parts of a nested Parameter part [0..*] The parameters for the operation/query parameter [0..*] Defines an appropriate combination of parameters to use when invoking this operation, to help code generators when generating overloaded parameter sets for this operation overload [0..*]

XML Template 

<OperationDefinition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 0..1 Canonical identifier for this operation definition, represented as a URI (globally unique) -->

 <version value="[string]"/><!-- 0..1 Business version of the operation definition -->
 <

 <name value="[string]"/><!-- ?? 1..1 Name for this operation definition (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Name for this operation definition (human friendly) -->

 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <kind value="[code]"/><!-- 1..1 operation | query -->
 <

 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->

 <date value="[dateTime]"/><!-- 0..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the operation definition -->
 <</useContext>

 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>

 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for operation definition (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this operation definition is defined -->
 <

 <affectsState value="[boolean]"/><!-- 0..1 Whether content is changed by the operation -->

 <code value="[code]"/><!-- 1..1 Name used to invoke the operation -->
 <comment value="[markdown]"/><!-- 0..1 Additional information about use -->
 <base><!-- 0..1 canonical(OperationDefinition) Marks this as a profile of the base --></base>
 <resource value="[code]"/><!-- 0..* Types this operation applies to -->
 <system value="[boolean]"/><!-- 1..1 Invoke at the system level? -->
 <type value="[boolean]"/><!-- 1..1 Invoke at the type level? -->
 <instance value="[boolean]"/><!-- 1..1 Invoke on an instance? -->
 <</inputProfile>
 <</outputProfile>

 <inputProfile><!-- 0..1 canonical(StructureDefinition) Validation information for in parameters --></inputProfile>
 <outputProfile><!-- 0..1 canonical(StructureDefinition) Validation information for out parameters --></outputProfile>

 <parameter>  <!-- 0..* Parameters for the operation/query -->
  <name value="[code]"/><!-- 1..1 Name in Parameters.parameter.name or in URL -->
  <use value="[code]"/><!-- 1..1 in | out -->
  <min value="[integer]"/><!-- 1..1 Minimum Cardinality -->
  <max value="[string]"/><!-- 1..1 Maximum Cardinality (a number or *) -->
  <documentation value="[string]"/><!-- 0..1 Description of meaning/use -->
  <type value="[code]"/><!-- ?? 0..1 What type this parameter has -->
  <</targetProfile>
  <

  <targetProfile><!-- 0..* canonical(StructureDefinition) If type is Reference | canonical, allowed targets --></targetProfile>
  <searchType value="[code]"/><!-- ?? 0..1 number | date | string | token | reference | composite | quantity | uri | special -->

  <binding>  <!-- 0..1 ValueSet details if this is coded -->
   <strength value="[code]"/><!-- 1..1 required | extensible | preferred | example -->
   <</valueSet[x]>

   <valueSet><!-- 1..1 canonical(ValueSet) Source of value set --></valueSet>

  </binding>
  <referencedFrom>  <!-- 0..* References to this parameter -->
   <source value="[string]"/><!-- 1..1 Referencing parameter -->
   <sourceId value="[string]"/><!-- 0..1 Element id of reference -->
  </referencedFrom>

  <part><!-- ?? 0..* Content as for OperationDefinition.parameter Parts of a nested Parameter --></part>
 </parameter>
 <overload>  <!-- 0..* Define overloaded variants for when  generating code -->
  <parameterName value="[string]"/><!-- 0..* Name of parameter to include in overload -->
  <comment value="[string]"/><!-- 0..1 Comments to go on overload -->
 </overload>
</OperationDefinition>

JSON Template 

{doco
  "resourceType" : "OperationDefinition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // Canonical identifier for this operation definition, represented as a URI (globally unique)

  "version" : "<string>", // Business version of the operation definition
  "

  "name" : "<string>", // C? R!  Name for this operation definition (computer friendly)
  "title" : "<string>", // Name for this operation definition (human friendly)

  "status" : "<code>", // R!  draft | active | retired | unknown
  "kind" : "<code>", // R!  operation | query
  "

  "experimental" : <boolean>, // For testing purposes, not real usage

  "date" : "<dateTime>", // Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the operation definition
  "

  "useContext" : [{ UsageContext }], // The context that the content is intended to support

  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for operation definition (if applicable)
  "purpose" : "<markdown>", // Why this operation definition is defined
  "

  "affectsState" : <boolean>, // Whether content is changed by the operation

  "code" : "<code>", // R!  Name used to invoke the operation
  "comment" : "<markdown>", // Additional information about use
  "

  "base" : { canonical(OperationDefinition) }, // Marks this as a profile of the base

  "resource" : ["<code>"], // Types this operation applies to
  "system" : <boolean>, // R!  Invoke at the system level?
  "type" : <boolean>, // R!  Invoke at the type level?
  "instance" : <boolean>, // R!  Invoke on an instance?
  "
  "

  "inputProfile" : { canonical(StructureDefinition) }, // Validation information for in parameters
  "outputProfile" : { canonical(StructureDefinition) }, // Validation information for out parameters

  "parameter" : [{ // Parameters for the operation/query
    "name" : "<code>", // R!  Name in Parameters.parameter.name or in URL
    "use" : "<code>", // R!  in | out
    "min" : <integer>, // R!  Minimum Cardinality
    "max" : "<string>", // R!  Maximum Cardinality (a number or *)
    "documentation" : "<string>", // Description of meaning/use
    "type" : "<code>", // C? What type this parameter has
    "
    "

    "targetProfile" : [{ canonical(StructureDefinition) }], // If type is Reference | canonical, allowed targets
    "searchType" : "<code>", // C? number | date | string | token | reference | composite | quantity | uri | special

    "binding" : { // ValueSet details if this is coded
      "strength" : "<code>", // R!  required | extensible | preferred | example
      
      ">"
      ">"

      "valueSet" : { canonical(ValueSet) } // R!  Source of value set

    },
    "referencedFrom" : [{ // References to this parameter
      "source" : "<string>", // R!  Referencing parameter
      "sourceId" : "<string>" // Element id of reference
    }],

    "part" : [{ Content as for OperationDefinition.parameter }] // C? Parts of a nested Parameter
  }],
  "overload" : [{ // Define overloaded variants for when  generating code
    "parameterName" : ["<string>"], // Name of parameter to include in overload
    "comment" : "<string>" // Comments to go on overload
  }]
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:OperationDefinition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:OperationDefinition.url [ uri ]; # 0..1 Canonical identifier for this operation definition, represented as a URI (globally unique)

  fhir:OperationDefinition.version [ string ]; # 0..1 Business version of the operation definition
  fhir:OperationDefinition.name [ string ]; # 1..1 Name for this operation definition (computer friendly)
  fhir:OperationDefinition.title [ string ]; # 0..1 Name for this operation definition (human friendly)

  fhir:OperationDefinition.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:OperationDefinition.kind [ code ]; # 1..1 operation | query
  fhir:

  fhir:OperationDefinition.experimental [ boolean ]; # 0..1 For testing purposes, not real usage

  fhir:OperationDefinition.date [ dateTime ]; # 0..1 Date last changed
  fhir:OperationDefinition.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:OperationDefinition.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:OperationDefinition.description [ markdown ]; # 0..1 Natural language description of the operation definition
  fhir:

  fhir:OperationDefinition.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support

  fhir:OperationDefinition.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for operation definition (if applicable)
  fhir:OperationDefinition.purpose [ markdown ]; # 0..1 Why this operation definition is defined
  fhir:

  fhir:OperationDefinition.affectsState [ boolean ]; # 0..1 Whether content is changed by the operation

  fhir:OperationDefinition.code [ code ]; # 1..1 Name used to invoke the operation
  fhir:OperationDefinition.comment [ markdown ]; # 0..1 Additional information about use
  fhir:OperationDefinition.base [ canonical(OperationDefinition) ]; # 0..1 Marks this as a profile of the base
  fhir:OperationDefinition.resource [ code ], ... ; # 0..* Types this operation applies to
  fhir:OperationDefinition.system [ boolean ]; # 1..1 Invoke at the system level?
  fhir:OperationDefinition.type [ boolean ]; # 1..1 Invoke at the type level?
  fhir:OperationDefinition.instance [ boolean ]; # 1..1 Invoke on an instance?
  fhir:
  fhir:

  fhir:OperationDefinition.inputProfile [ canonical(StructureDefinition) ]; # 0..1 Validation information for in parameters
  fhir:OperationDefinition.outputProfile [ canonical(StructureDefinition) ]; # 0..1 Validation information for out parameters

  fhir:OperationDefinition.parameter [ # 0..* Parameters for the operation/query
    fhir:OperationDefinition.parameter.name [ code ]; # 1..1 Name in Parameters.parameter.name or in URL
    fhir:OperationDefinition.parameter.use [ code ]; # 1..1 in | out
    fhir:OperationDefinition.parameter.min [ integer ]; # 1..1 Minimum Cardinality
    fhir:OperationDefinition.parameter.max [ string ]; # 1..1 Maximum Cardinality (a number or *)
    fhir:OperationDefinition.parameter.documentation [ string ]; # 0..1 Description of meaning/use
    fhir:OperationDefinition.parameter.type [ code ]; # 0..1 What type this parameter has
    fhir:
    fhir:

    fhir:OperationDefinition.parameter.targetProfile [ canonical(StructureDefinition) ], ... ; # 0..* If type is Reference | canonical, allowed targets
    fhir:OperationDefinition.parameter.searchType [ code ]; # 0..1 number | date | string | token | reference | composite | quantity | uri | special

    fhir:OperationDefinition.parameter.binding [ # 0..1 ValueSet details if this is coded
      fhir:OperationDefinition.parameter.binding.strength [ code ]; # 1..1 required | extensible | preferred | example
      # . One of these 2
        fhir: ]
        fhir:) ]

      fhir:OperationDefinition.parameter.binding.valueSet [ canonical(ValueSet) ]; # 1..1 Source of value set

    ];
    fhir:OperationDefinition.parameter.referencedFrom [ # 0..* References to this parameter
      fhir:OperationDefinition.parameter.referencedFrom.source [ string ]; # 1..1 Referencing parameter
      fhir:OperationDefinition.parameter.referencedFrom.sourceId [ string ]; # 0..1 Element id of reference
    ], ...;

    fhir:OperationDefinition.parameter.part [ See OperationDefinition.parameter ], ... ; # 0..* Parts of a nested Parameter
  ], ...;
  fhir:OperationDefinition.overload [ # 0..* Define overloaded variants for when  generating code
    fhir:OperationDefinition.overload.parameterName [ string ], ... ; # 0..* Name of parameter to include in overload
    fhir:OperationDefinition.overload.comment [ string ]; # 0..1 Comments to go on overload
  ], ...;
]

Changes since R3

OperationDefinition
OperationDefinition.affectsState OperationDefinition.title
  • Added Element
OperationDefinition.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status to http://hl7.org/fhir/ValueSet/publication-status|4.0.1
OperationDefinition.kind
  • Change value set from http://hl7.org/fhir/ValueSet/operation-kind to http://hl7.org/fhir/ValueSet/operation-kind|4.0.1
OperationDefinition.experimental
  • No longer marked as Modifier
OperationDefinition.affectsState
  • Renamed from idempotent to affectsState
OperationDefinition.comment
  • Type changed from string to markdown
OperationDefinition.base
  • Type changed from Reference(OperationDefinition) to canonical canonical(OperationDefinition)
OperationDefinition.resource
  • Change value set from http://hl7.org/fhir/ValueSet/resource-types to http://hl7.org/fhir/ValueSet/resource-types|4.0.1
OperationDefinition.inputProfile
  • Added Element
OperationDefinition.outputProfile
  • Added Element
OperationDefinition.parameter.use
  • Change value set from http://hl7.org/fhir/ValueSet/operation-parameter-use to http://hl7.org/fhir/ValueSet/operation-parameter-use|4.0.1
OperationDefinition.parameter.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types to http://hl7.org/fhir/ValueSet/all-types|4.0.1
OperationDefinition.parameter.targetProfile
  • Added Element Renamed from profile to targetProfile
  • Max Cardinality changed from 1 to *
  • Type changed from Reference(StructureDefinition) to canonical(StructureDefinition)
OperationDefinition.parameter.binding.valueSet[x] OperationDefinition.parameter.searchType
  • Remove Reference(ValueSet), Change value set from http://hl7.org/fhir/ValueSet/search-param-type to http://hl7.org/fhir/ValueSet/search-param-type|4.0.1
OperationDefinition.parameter.binding.strength
  • Change value set from http://hl7.org/fhir/ValueSet/binding-strength to http://hl7.org/fhir/ValueSet/binding-strength|4.0.1
OperationDefinition.parameter.binding.valueSet
  • Renamed from valueSet[x] to valueSet
  • Add canonical Type canonical(ValueSet)
  • Remove Types uri, Reference(ValueSet)
OperationDefinition.idempotent OperationDefinition.parameter.referencedFrom
  • deleted Added Element
OperationDefinition.parameter.profile OperationDefinition.parameter.referencedFrom.source
  • deleted Added Mandatory Element
OperationDefinition.parameter.referencedFrom.sourceId
  • Added Element

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 <--> R4 Conversion Maps (status = 18 37 tests that all execute ok. 1 fail All tests pass round-trip testing and all 34 r3 resources are valid.). Note: these have note yet been updated to be R3 to R4 invalid (0 errors). )

Structure

?!
Name Flags Card. Type Description & Constraints doco
. . OperationDefinition I N DomainResource Definition of an operation or a named query
+ Warning: Name should be usable as an identifier for the module by machine processing applications such as code generation
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . url Σ 0..1 uri Canonical identifier for this operation definition, represented as a URI (globally unique)
. . . version Σ 0..1 string Business version of the operation definition
. . . name Σ I 1..1 string Name for this operation definition (computer friendly)
. . . title Σ 0..1 string Name for this operation definition (human friendly)
... status ?! Σ 1..1 code draft | active | retired | unknown
PublicationStatus ( Required )
. . . kind Σ 1..1 code operation | query
OperationKind ( Required )
. . . experimental Σ 0..1 boolean For testing purposes, not real usage
. . . date Σ 0..1 dateTime Date last changed
. . . publisher Σ 0..1 string Name of the publisher (organization or individual)
. . . contact Σ 0..* ContactDetail Contact details for the publisher
. . . description 0..1 markdown Natural language description of the operation definition
. . . useContext Σ TU 0..* UsageContext The context that the content is intended to support
. . . jurisdiction Σ 0..* CodeableConcept Intended jurisdiction for operation definition (if applicable)
Jurisdiction ValueSet ( Extensible )
. . . purpose 0..1 markdown Why this operation definition is defined
. . . affectsState Σ 0..1 boolean Whether content is unchanged changed by the operation
. . . code Σ 1..1 code Name used to invoke the operation
. . . comment 0..1 markdown Additional information about use
. . . base Σ 0..1 canonical ( OperationDefinition ) Marks this as a profile of the base
. . . resource Σ 0..* code Types this operation applies to
ResourceType ( Required )
. . . system Σ 1..1 boolean Invoke at the system level?
. . . type Σ 1..1 boolean Invoke at the type level?
. . . instance Σ 1..1 boolean Invoke on an instance?
. . . inputProfile 0..1 canonical ( StructureDefinition ) Validation information for in parameters
. . . outputProfile 0..1 canonical ( StructureDefinition ) Validation information for out parameters
. . . parameter I 0..* BackboneElement Parameters for the operation/query
+ Rule: Either a type must be provided, or parts
+ Rule: A search type can only be specified for parameters of type string
+ Rule: A targetProfile can only be specified for parameters of type Reference or Canonical
. . . . name 1..1 code Name in Parameters.parameter.name or in URL
. . . . use 1..1 code in | out
OperationParameterUse ( Required )
. . . . min 1..1 integer Minimum Cardinality
. . . . max 1..1 string Maximum Cardinality (a number or *)
. . . . documentation 0..1 string Description of meaning/use
. . . . type I 0..1 code What type this parameter has
FHIRAllTypes ( Required )
. . . . targetProfile 0..* canonical ( StructureDefinition ) If type is Reference, Reference | canonical, allowed targets
. . . . searchType I 0..1 code number | date | string | token | reference | composite | quantity | uri | special
SearchParamType ( Required )
. . . . binding 0..1 BackboneElement ValueSet details if this is coded
. . . . . strength 1..1 code required | extensible | preferred | example
BindingStrength ( Required )
. . . . valueSet[x] . valueSet 1..1 canonical ( ValueSet ) Source of value set
. . . . referencedFrom TU 0..* BackboneElement References to this parameter
. . . . . valueSetUri source 1..1 uri string Referencing parameter
. . . . valueSetCanonical . sourceId 0..1 canonical string Element id of reference
. . . . part I 0..* see parameter Parts of a nested Parameter
. . . overload 0..* BackboneElement Define overloaded variants for when generating code
. . . . parameterName 0..* string Name of parameter to include in overload
. . . . comment 0..1 string Comments to go on overload

doco Documentation for this format

UML Diagram ( Legend )

OperationDefinition ( DomainResource ) An absolute URI that is used to identify this operation definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this operation definition is (or will be) published published. This URL can be the target of a canonical reference. It SHALL remain the same when the operation definition is stored on different servers url : uri [0..1] The identifier that is used to identify this version of the operation definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the operation definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence version : string [0..1] A natural language name identifying the operation definition. This name should be usable as an identifier for the module by machine processing applications such as code generation name : string [1..1] A short, descriptive, user-friendly title for the operation definition title : string [0..1] The status of this operation definition. Enables tracking the life-cycle of the content (this element modifies the meaning of other elements) status : code [1..1] « The lifecycle status of an artifact. (Strength=Required) PublicationStatus ! » Whether this is an operation or a named query kind : code [1..1] « Whether an operation is a normal operation or a query. (Strength=Required) OperationKind ! » A Boolean value to indicate that this operation definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage (this element modifies the meaning of other elements) experimental : boolean [0..1] The date (and optionally time) when the operation definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the operation definition changes date : dateTime [0..1] The name of the organization or individual that published the operation definition publisher : string [0..1] Contact details to assist a user in finding and communicating with the publisher contact : ContactDetail [0..*] A free text natural language description of the operation definition from a consumer's perspective description : markdown [0..1] The content was developed with a focus and intent of supporting the contexts that are listed. These terms contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate operation definition instances useContext : UsageContext [0..*] A legal or geographic region in which the operation definition is intended to be used jurisdiction : CodeableConcept [0..*] « Countries and regions within which this artifact is targeted for use use. (Strength=Extensible) Jurisdiction ValueSet + » Explanation of why this operation definition is needed and why it has been designed as it has purpose : markdown [0..1] Operations that have affects state = false (see [HTTP specification definition of idempotent](http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html)) may be invoked by performing an HTTP GET Whether the operation instead of a POST affects state. Side effects such as producing audit trail entries do not count as 'affecting state' affectsState : boolean [0..1] The name used to invoke the operation code : code [1..1] Additional information about how to use this operation or named query comment : markdown [0..1] Indicates that this operation definition is a constraining profile on the base base : canonical [0..1] « OperationDefinition » The types on which this operation can be executed resource : code [0..*] « One of the resource types defined as part of this version of FHIR. (Strength=Required) ResourceType ! » Indicates whether this operation or named query can be invoked at the system level (e.g. without needing to choose a resource type for the context) system : boolean [1..1] Indicates whether this operation or named query can be invoked at the resource type level for any given resource type level (e.g. without needing to choose a specific resource id for the context) type : boolean [1..1] Indicates whether this operation can be invoked on a particular instance of one of the given types instance : boolean [1..1] Additional validation information for the in parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource as a whole inputProfile : canonical [0..1] « StructureDefinition » Additional validation information for the out parameters - a single profile that covers all the parameters. The profile is a constraint on the parameters resource outputProfile : canonical [0..1] « StructureDefinition » Parameter The name of used to identify the parameter name : code [1..1] Whether this is an input or an output parameter use : code [1..1] « Whether an operation parameter is an input or an output parameter. (Strength=Required) OperationParameterUse ! » The minimum number of times this parameter SHALL appear in the request or response min : integer [1..1] The maximum number of times this element is permitted to appear in the request or response max : string [1..1] Describes the meaning or use of this parameter documentation : string [0..1] The type for this parameter type : code [0..1] « A list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types Types. (Strength=Required) FHIRAllTypes ! » If Used when the type is "Reference", then targetProfile lists "Reference" or "canonical", and identifies a one profile structure or more profiles implementation Guide that applies to the Reference target of the reference this parameter refers to. If any profiles are specified, then the content must conform to at least one of them. The URL can refer be a local reference - to a contained StructureDefinition, or a reference to another StructureDefinition or Implementation Guide by a canonical URL. When an implementation guide is specified, the target resource SHALL conform to at least one profile defined in the implementation guide targetProfile : canonical [0..*] « StructureDefinition » How the parameter is understood as a search parameter. This is only used if the parameter type is 'string' searchType : code [0..1] « Data types allowed to be used for search parameters. (Strength=Required) SearchParamType ! » Binding Indicates the degree of conformance expectations associated with this binding - that is, the degree to which the provided value set must be adhered to in the instances strength : code [1..1] « Indication of the degree of conformance expectations associated with a binding. (Strength=Required) BindingStrength ! » Points to the value set or external definition (e.g. implicit value set) that identifies the set of codes to be used valueSet[x] valueSet : Type canonical [1..1] « uri | canonical ( ValueSet ) » ReferencedFrom The name of the parameter or dot-separated path of parameter names pointing to the resource parameter that is expected to contain a reference to this resource source : string [1..1] The id of the element in the referencing resource that is expected to resolve to this resource sourceId : string [0..1] Overload Name of parameter to include in overload parameterName : string [0..*] Comments to go on overload comment : string [0..1] Binds to a value set if this parameter is coded (code, Coding, CodeableConcept) binding [0..1] Identifies other resource parameters within the operation invocation that are expected to resolve to this resource referencedFrom [0..*] The parts of a nested Parameter part [0..*] The parameters for the operation/query parameter [0..*] Defines an appropriate combination of parameters to use when invoking this operation, to help code generators when generating overloaded parameter sets for this operation overload [0..*]

XML Template 

<OperationDefinition xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <

 <url value="[uri]"/><!-- 0..1 Canonical identifier for this operation definition, represented as a URI (globally unique) -->

 <version value="[string]"/><!-- 0..1 Business version of the operation definition -->
 <

 <name value="[string]"/><!-- ?? 1..1 Name for this operation definition (computer friendly) -->
 <title value="[string]"/><!-- 0..1 Name for this operation definition (human friendly) -->

 <status value="[code]"/><!-- 1..1 draft | active | retired | unknown -->
 <kind value="[code]"/><!-- 1..1 operation | query -->
 <

 <experimental value="[boolean]"/><!-- 0..1 For testing purposes, not real usage -->

 <date value="[dateTime]"/><!-- 0..1 Date last changed -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (organization or individual) -->
 <contact><!-- 0..* ContactDetail Contact details for the publisher --></contact>
 <description value="[markdown]"/><!-- 0..1 Natural language description of the operation definition -->
 <</useContext>

 <useContext><!-- 0..* UsageContext The context that the content is intended to support --></useContext>

 <jurisdiction><!-- 0..* CodeableConcept Intended jurisdiction for operation definition (if applicable) --></jurisdiction>
 <purpose value="[markdown]"/><!-- 0..1 Why this operation definition is defined -->
 <

 <affectsState value="[boolean]"/><!-- 0..1 Whether content is changed by the operation -->

 <code value="[code]"/><!-- 1..1 Name used to invoke the operation -->
 <comment value="[markdown]"/><!-- 0..1 Additional information about use -->
 <base><!-- 0..1 canonical(OperationDefinition) Marks this as a profile of the base --></base>
 <resource value="[code]"/><!-- 0..* Types this operation applies to -->
 <system value="[boolean]"/><!-- 1..1 Invoke at the system level? -->
 <type value="[boolean]"/><!-- 1..1 Invoke at the type level? -->
 <instance value="[boolean]"/><!-- 1..1 Invoke on an instance? -->
 <</inputProfile>
 <</outputProfile>

 <inputProfile><!-- 0..1 canonical(StructureDefinition) Validation information for in parameters --></inputProfile>
 <outputProfile><!-- 0..1 canonical(StructureDefinition) Validation information for out parameters --></outputProfile>

 <parameter>  <!-- 0..* Parameters for the operation/query -->
  <name value="[code]"/><!-- 1..1 Name in Parameters.parameter.name or in URL -->
  <use value="[code]"/><!-- 1..1 in | out -->
  <min value="[integer]"/><!-- 1..1 Minimum Cardinality -->
  <max value="[string]"/><!-- 1..1 Maximum Cardinality (a number or *) -->
  <documentation value="[string]"/><!-- 0..1 Description of meaning/use -->
  <type value="[code]"/><!-- ?? 0..1 What type this parameter has -->
  <</targetProfile>
  <

  <targetProfile><!-- 0..* canonical(StructureDefinition) If type is Reference | canonical, allowed targets --></targetProfile>
  <searchType value="[code]"/><!-- ?? 0..1 number | date | string | token | reference | composite | quantity | uri | special -->

  <binding>  <!-- 0..1 ValueSet details if this is coded -->
   <strength value="[code]"/><!-- 1..1 required | extensible | preferred | example -->
   <</valueSet[x]>

   <valueSet><!-- 1..1 canonical(ValueSet) Source of value set --></valueSet>

  </binding>
  <referencedFrom>  <!-- 0..* References to this parameter -->
   <source value="[string]"/><!-- 1..1 Referencing parameter -->
   <sourceId value="[string]"/><!-- 0..1 Element id of reference -->
  </referencedFrom>

  <part><!-- ?? 0..* Content as for OperationDefinition.parameter Parts of a nested Parameter --></part>
 </parameter>
 <overload>  <!-- 0..* Define overloaded variants for when  generating code -->
  <parameterName value="[string]"/><!-- 0..* Name of parameter to include in overload -->
  <comment value="[string]"/><!-- 0..1 Comments to go on overload -->
 </overload>
</OperationDefinition>

JSON Template 

{doco
  "resourceType" : "OperationDefinition",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "

  "url" : "<uri>", // Canonical identifier for this operation definition, represented as a URI (globally unique)

  "version" : "<string>", // Business version of the operation definition
  "

  "name" : "<string>", // C? R!  Name for this operation definition (computer friendly)
  "title" : "<string>", // Name for this operation definition (human friendly)

  "status" : "<code>", // R!  draft | active | retired | unknown
  "kind" : "<code>", // R!  operation | query
  "

  "experimental" : <boolean>, // For testing purposes, not real usage

  "date" : "<dateTime>", // Date last changed
  "publisher" : "<string>", // Name of the publisher (organization or individual)
  "contact" : [{ ContactDetail }], // Contact details for the publisher
  "description" : "<markdown>", // Natural language description of the operation definition
  "

  "useContext" : [{ UsageContext }], // The context that the content is intended to support

  "jurisdiction" : [{ CodeableConcept }], // Intended jurisdiction for operation definition (if applicable)
  "purpose" : "<markdown>", // Why this operation definition is defined
  "

  "affectsState" : <boolean>, // Whether content is changed by the operation

  "code" : "<code>", // R!  Name used to invoke the operation
  "comment" : "<markdown>", // Additional information about use
  "

  "base" : { canonical(OperationDefinition) }, // Marks this as a profile of the base

  "resource" : ["<code>"], // Types this operation applies to
  "system" : <boolean>, // R!  Invoke at the system level?
  "type" : <boolean>, // R!  Invoke at the type level?
  "instance" : <boolean>, // R!  Invoke on an instance?
  "
  "

  "inputProfile" : { canonical(StructureDefinition) }, // Validation information for in parameters
  "outputProfile" : { canonical(StructureDefinition) }, // Validation information for out parameters

  "parameter" : [{ // Parameters for the operation/query
    "name" : "<code>", // R!  Name in Parameters.parameter.name or in URL
    "use" : "<code>", // R!  in | out
    "min" : <integer>, // R!  Minimum Cardinality
    "max" : "<string>", // R!  Maximum Cardinality (a number or *)
    "documentation" : "<string>", // Description of meaning/use
    "type" : "<code>", // C? What type this parameter has
    "
    "

    "targetProfile" : [{ canonical(StructureDefinition) }], // If type is Reference | canonical, allowed targets
    "searchType" : "<code>", // C? number | date | string | token | reference | composite | quantity | uri | special

    "binding" : { // ValueSet details if this is coded
      "strength" : "<code>", // R!  required | extensible | preferred | example
      
      ">"
      ">"

      "valueSet" : { canonical(ValueSet) } // R!  Source of value set

    },
    "referencedFrom" : [{ // References to this parameter
      "source" : "<string>", // R!  Referencing parameter
      "sourceId" : "<string>" // Element id of reference
    }],

    "part" : [{ Content as for OperationDefinition.parameter }] // C? Parts of a nested Parameter
  }],
  "overload" : [{ // Define overloaded variants for when  generating code
    "parameterName" : ["<string>"], // Name of parameter to include in overload
    "comment" : "<string>" // Comments to go on overload
  }]
}

Turtle Template 

@prefix fhir: <http://hl7.org/fhir/> .doco


[ a fhir:OperationDefinition;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root

  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:

  fhir:OperationDefinition.url [ uri ]; # 0..1 Canonical identifier for this operation definition, represented as a URI (globally unique)

  fhir:OperationDefinition.version [ string ]; # 0..1 Business version of the operation definition
  fhir:OperationDefinition.name [ string ]; # 1..1 Name for this operation definition (computer friendly)
  fhir:OperationDefinition.title [ string ]; # 0..1 Name for this operation definition (human friendly)

  fhir:OperationDefinition.status [ code ]; # 1..1 draft | active | retired | unknown
  fhir:OperationDefinition.kind [ code ]; # 1..1 operation | query
  fhir:

  fhir:OperationDefinition.experimental [ boolean ]; # 0..1 For testing purposes, not real usage

  fhir:OperationDefinition.date [ dateTime ]; # 0..1 Date last changed
  fhir:OperationDefinition.publisher [ string ]; # 0..1 Name of the publisher (organization or individual)
  fhir:OperationDefinition.contact [ ContactDetail ], ... ; # 0..* Contact details for the publisher
  fhir:OperationDefinition.description [ markdown ]; # 0..1 Natural language description of the operation definition
  fhir:

  fhir:OperationDefinition.useContext [ UsageContext ], ... ; # 0..* The context that the content is intended to support

  fhir:OperationDefinition.jurisdiction [ CodeableConcept ], ... ; # 0..* Intended jurisdiction for operation definition (if applicable)
  fhir:OperationDefinition.purpose [ markdown ]; # 0..1 Why this operation definition is defined
  fhir:

  fhir:OperationDefinition.affectsState [ boolean ]; # 0..1 Whether content is changed by the operation

  fhir:OperationDefinition.code [ code ]; # 1..1 Name used to invoke the operation
  fhir:OperationDefinition.comment [ markdown ]; # 0..1 Additional information about use
  fhir:OperationDefinition.base [ canonical(OperationDefinition) ]; # 0..1 Marks this as a profile of the base
  fhir:OperationDefinition.resource [ code ], ... ; # 0..* Types this operation applies to
  fhir:OperationDefinition.system [ boolean ]; # 1..1 Invoke at the system level?
  fhir:OperationDefinition.type [ boolean ]; # 1..1 Invoke at the type level?
  fhir:OperationDefinition.instance [ boolean ]; # 1..1 Invoke on an instance?
  fhir:
  fhir:

  fhir:OperationDefinition.inputProfile [ canonical(StructureDefinition) ]; # 0..1 Validation information for in parameters
  fhir:OperationDefinition.outputProfile [ canonical(StructureDefinition) ]; # 0..1 Validation information for out parameters

  fhir:OperationDefinition.parameter [ # 0..* Parameters for the operation/query
    fhir:OperationDefinition.parameter.name [ code ]; # 1..1 Name in Parameters.parameter.name or in URL
    fhir:OperationDefinition.parameter.use [ code ]; # 1..1 in | out
    fhir:OperationDefinition.parameter.min [ integer ]; # 1..1 Minimum Cardinality
    fhir:OperationDefinition.parameter.max [ string ]; # 1..1 Maximum Cardinality (a number or *)
    fhir:OperationDefinition.parameter.documentation [ string ]; # 0..1 Description of meaning/use
    fhir:OperationDefinition.parameter.type [ code ]; # 0..1 What type this parameter has
    fhir:
    fhir:

    fhir:OperationDefinition.parameter.targetProfile [ canonical(StructureDefinition) ], ... ; # 0..* If type is Reference | canonical, allowed targets
    fhir:OperationDefinition.parameter.searchType [ code ]; # 0..1 number | date | string | token | reference | composite | quantity | uri | special

    fhir:OperationDefinition.parameter.binding [ # 0..1 ValueSet details if this is coded
      fhir:OperationDefinition.parameter.binding.strength [ code ]; # 1..1 required | extensible | preferred | example
      # . One of these 2
        fhir: ]
        fhir:) ]

      fhir:OperationDefinition.parameter.binding.valueSet [ canonical(ValueSet) ]; # 1..1 Source of value set

    ];
    fhir:OperationDefinition.parameter.referencedFrom [ # 0..* References to this parameter
      fhir:OperationDefinition.parameter.referencedFrom.source [ string ]; # 1..1 Referencing parameter
      fhir:OperationDefinition.parameter.referencedFrom.sourceId [ string ]; # 0..1 Element id of reference
    ], ...;

    fhir:OperationDefinition.parameter.part [ See OperationDefinition.parameter ], ... ; # 0..* Parts of a nested Parameter
  ], ...;
  fhir:OperationDefinition.overload [ # 0..* Define overloaded variants for when  generating code
    fhir:OperationDefinition.overload.parameterName [ string ], ... ; # 0..* Name of parameter to include in overload
    fhir:OperationDefinition.overload.comment [ string ]; # 0..1 Comments to go on overload
  ], ...;
]

Changes since DSTU2 Release 3

OperationDefinition
OperationDefinition.affectsState OperationDefinition.title
  • Added Element
OperationDefinition.status
  • Change value set from http://hl7.org/fhir/ValueSet/publication-status to http://hl7.org/fhir/ValueSet/publication-status|4.0.1
OperationDefinition.kind
  • Change value set from http://hl7.org/fhir/ValueSet/operation-kind to http://hl7.org/fhir/ValueSet/operation-kind|4.0.1
OperationDefinition.experimental
  • No longer marked as Modifier
OperationDefinition.affectsState
  • Renamed from idempotent to affectsState
OperationDefinition.comment
  • Type changed from string to markdown
OperationDefinition.base
  • Type changed from Reference(OperationDefinition) to canonical canonical(OperationDefinition)
OperationDefinition.resource
  • Change value set from http://hl7.org/fhir/ValueSet/resource-types to http://hl7.org/fhir/ValueSet/resource-types|4.0.1
OperationDefinition.inputProfile
  • Added Element
OperationDefinition.outputProfile
  • Added Element
OperationDefinition.parameter.use
  • Change value set from http://hl7.org/fhir/ValueSet/operation-parameter-use to http://hl7.org/fhir/ValueSet/operation-parameter-use|4.0.1
OperationDefinition.parameter.type
  • Change value set from http://hl7.org/fhir/ValueSet/all-types to http://hl7.org/fhir/ValueSet/all-types|4.0.1
OperationDefinition.parameter.targetProfile
  • Added Element Renamed from profile to targetProfile
  • Max Cardinality changed from 1 to *
  • Type changed from Reference(StructureDefinition) to canonical(StructureDefinition)
OperationDefinition.parameter.binding.valueSet[x] OperationDefinition.parameter.searchType
  • Remove Reference(ValueSet), Change value set from http://hl7.org/fhir/ValueSet/search-param-type to http://hl7.org/fhir/ValueSet/search-param-type|4.0.1
OperationDefinition.parameter.binding.strength
  • Change value set from http://hl7.org/fhir/ValueSet/binding-strength to http://hl7.org/fhir/ValueSet/binding-strength|4.0.1
OperationDefinition.parameter.binding.valueSet
  • Renamed from valueSet[x] to valueSet
  • Add canonical Type canonical(ValueSet)
  • Remove Types uri, Reference(ValueSet)
OperationDefinition.idempotent OperationDefinition.parameter.referencedFrom
  • deleted Added Element
OperationDefinition.parameter.profile OperationDefinition.parameter.referencedFrom.source
  • deleted Added Mandatory Element
OperationDefinition.parameter.referencedFrom.sourceId
  • Added Element

See the Full Difference for further information

This analysis is available as XML or JSON .

See R2 <--> R3 <--> R4 Conversion Maps (status = 18 37 tests that all execute ok. 1 fail All tests pass round-trip testing and all 34 r3 resources are valid.). Note: these have note yet been updated to be R3 to R4 invalid (0 errors). )

 

Alternate See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions & the dependency analysis

5.4.3.1 Terminology Bindings

Path Definition Type Reference
OperationDefinition.status The lifecycle status of an artifact. Required PublicationStatus
OperationDefinition.kind Whether an operation is a normal operation or a query. Required OperationKind
OperationDefinition.jurisdiction Countries and regions within which this artifact is targeted for use use. Extensible Jurisdiction ValueSet
OperationDefinition.resource One of the resource types defined as part of this version of FHIR. Required Resource Types
OperationDefinition.parameter.use Whether an operation parameter is an input or an output parameter. Required OperationParameterUse
OperationDefinition.parameter.type A list of all the concrete types defined in this version of the FHIR specification - Abstract Types, Data Types and Resource Types Types. Required All Types
OperationDefinition.parameter.searchType Data types allowed to be used for search parameters. Required SearchParamType
OperationDefinition.parameter.binding.strength Indication of the degree of conformance expectations associated with a binding. Required BindingStrength

5.4.3.2 Constraints

id Level Location Description Expression
opd-0 Warning (base) Name should be usable as an identifier for the module by machine processing applications such as code generation name.matches('[A-Z]([A-Za-z0-9_]){0,254}')
opd-1 : On OperationDefinition.parameter: Rule OperationDefinition.parameter Either a type must be provided, or parts ( expression on OperationDefinition.parameter: type.exists() or part.exists() )
opd-2 : On OperationDefinition.parameter: Rule OperationDefinition.parameter A search type can only be specified for parameters of type string ( expression on OperationDefinition.parameter: searchType.exists() implies type = 'string' )
opd-3 Rule OperationDefinition.parameter A targetProfile can only be specified for parameters of type Reference or Canonical targetProfile.exists() implies (type = 'Reference' or type = 'canonical')

5.4.3.3 Operations defined as part of this Specification

Base Operations (All resource types)
Validate a resource [base]/[Resource]/$validate | [base]/[Resource]/[id]/$validate
Access a list of profiles, tags, and security labels [base]/$meta | [base]/[Resource]/$meta | [base]/[Resource]/[id]/$meta
Add profiles, tags, and security labels to a resource [base]/[Resource]/[id]/$meta-add
Delete profiles, tags, and security labels for a resource [base]/[Resource]/[id]/$meta-delete
Convert from one form to another [base]/$convert
Execute a graphql statement [base]/$graphql | [base]/[Resource]/[id]/$graphql
Return a graph of resources [base]/[Resource]/[id]/$graph
Operations Defined by Resource Types
Apply [base]/ActivityDefinition/$apply | [base]/ActivityDefinition/[id]/$apply
Data Requirements [base]/ActivityDefinition/[id]/$data-requirements
Fetch a subset of the CapabilityStatement resource [base]/CapabilityStatement/$subset | [base]/CapabilityStatement/[id]/$subset
Test if a server implements a client's required operations [base]/CapabilityStatement/$implements | [base]/CapabilityStatement/[id]/$implements
Test if a server implements a client's required operations [base]/CapabilityStatement/$conforms
Discover what versions a server supports [base]/$versions
Apply [base]/ChargeItemDefinition/[id]/$apply
Submit a Claim resource for adjudication [base]/Claim/$submit
Concept Look Up & Decomposition [base]/CodeSystem/$lookup
Code System based Validation [base]/CodeSystem/$validate-code | [base]/CodeSystem/[id]/$validate-code
Subsumption Testing [base]/CodeSystem/$subsumes | [base]/CodeSystem/[id]/$subsumes
Code Composition Finding codes based on supplied properties [base]/CodeSystem/$compose [base]/CodeSystem/$find-matches | [base]/CodeSystem/[id]/$compose [base]/CodeSystem/[id]/$find-matches
Generate a Document [base]/Composition/$document | [base]/Composition/[id]/$document
Concept Translation [base]/ConceptMap/$translate | [base]/ConceptMap/[id]/$translate
Closure Table Maintenance [base]/$closure
Submit an EligibilityRequest resource for assessment [base]/EligibilityRequest/$submit [base]/CoverageEligibilityRequest/$submit
Fetch Encounter Record [base]/Encounter/[id]/$everything
Fetch a group of Patient Records [base]/Group/[id]/$everything
Data Requirements [base]/$data-requirements | [base]/Library/[id]/$data-requirements
Find a functional list [base]/List/$find
Evaluate Measure [base]/Measure/$evaluate-measure | [base]/Measure/[id]/$evaluate-measure
Data Requirements [base]/Measure/[id]/$data-requirements
Process Message Submit Data [base]/$process-message [base]/Measure/$submit-data | [base]/Measure/[id]/$submit-data
Fetch Preferred it Collect Data [base]/NamingSystem/$preferred-id [base]/Measure/$collect-data | [base]/Measure/[id]/$collect-data
Observation Statistics Care Gaps [base]/Observation/$stats [base]/Measure/$care-gaps
Last N Observations Query Fetch Product Record [base]/Observation/$lastn [base]/MedicinalProduct/$everything | [base]/MedicinalProduct/[id]/$everything
Find patient matches using MPI based logic Process Message [base]/Patient/$match [base]/$process-message
Fetch Patient Record Preferred it [base]/Patient/$everything | [base]/Patient/[id]/$everything [base]/NamingSystem/$preferred-id
Apply Observation Statistics [base]/PlanDefinition/[id]/$apply [base]/Observation/$stats
Data Requirements Last N Observations Query [base]/PlanDefinition/[id]/$data-requirements [base]/Observation/$lastn
Submit an ProcessRequest resource for assessment Find patient matches using MPI based logic [base]/ProcessRequest/$submit [base]/Patient/$match
Populate Questionnaire Fetch Patient Record [base]/Questionnaire/$populate [base]/Patient/$everything | [base]/Questionnaire/[id]/$populate [base]/Patient/[id]/$everything
Generate HTML for Questionnaire Apply [base]/Questionnaire/$populatehtml [base]/PlanDefinition/$apply | [base]/Questionnaire/[id]/$populatehtml [base]/PlanDefinition/[id]/$apply
Generate a link to a Questionnaire completion webpage Data Requirements [base]/Questionnaire/$populatelink | [base]/Questionnaire/[id]/$populatelink [base]/PlanDefinition/[id]/$data-requirements
Build Questionnaire [base]/StructureDefinition/$questionnaire | [base]/StructureDefinition/[id]/$questionnaire
Generate Snapshot [base]/StructureDefinition/$snapshot | [base]/StructureDefinition/[id]/$snapshot
Model Instance Transformation [base]/StructureMap/$transform | [base]/StructureMap/[id]/$transform
Value Set Expansion [base]/ValueSet/$expand | [base]/ValueSet/[id]/$expand
Value Set based Validation [base]/ValueSet/$validate-code | [base]/ValueSet/[id]/$validate-code

5.4.3.4 Describing Operation Parameters

There are 2 ways to describe the input and output parameters for an operation:

  • Using OperationDefinition.parameter to describe the parameters
  • Using OperationDefinition.inputProfile and OperationDefinition.outputProfile

The parameters is a simple list of possible parameters, along with cardinalities and types. The profiles allow a rich set of validation rules etc. to be provided. OperationDefinitions SHALL always define the parameters using OperationDefinition.parameter in the resource, and MAY also provide profiles for the parameters. If present, the profiles SHALL NOT disagree with the parameters defined for the operation.

As an example, consider an operation that defines 3 parameters, 2 in and 1 out:

In Parameters:
Name Cardinality Type Binding Profile Documentation
a 0..1 integer

An integer parameter

b 0..1 Patient

A patient parameter

Out Parameters:
Name Cardinality Type Binding Profile Documentation
c 1..1 decimal

A result parameter

In addition to specifying the operation parameters directly, an operation definition can also provide a profile: 


 "inputProfile" : "http://example.org/StructureDefinition/op.x.in.profile"

This profile would describe a parameters resource with 2 parameters (using slicing), with the same details as the table above. The operation definition would still list the parameters directly to save applications consuming the definition (e.g. to produce an OpenAPI document ) from parsing and interpreting the profile.

5.4.3.5 Executing Operations and Named Queries

Operations OperationDefinitions with kind = operation are executed by POSTing to a URL that is as defined by in the operation definition Operations Framework .

5.4.3.6 Executing Named Queries

Named queries (OperationDefinitions with kind = query ) are executed by performing a search with the value of the search parameter "_query" set to the name provided in the definition.

If the named query is to be performed over the RESTful API, all the parameters must be simple search parameters, so that they can be represented directly in the URL without tricky encoding issues. Named queries always return a bundle containing a set of resources, so all the out parameters must be resources, not data types.

For named queries, all the standard search parameters are automatically in scope (though servers do not need to support them unless explicitly documented).

5.4.3.6

5.4.3.7 Passing Resources to Operations

There are two ways to pass resources to an operation: directly or by reference. The definition of an operation distinguishes between these two, since they have very different behaviors and consequences.

As an example, take the Questionnaire.$populate ValueSet.$expand operation . This operation takes a questionnaire valueset as a direct parameter. The type of the parameter is defined as 'Questionnaire'. 'ValueSet'. In a Parameters resource, it would be represented like this: 

  <parameter>
    <name value="questionnaire"/>

    <name value="valueset"/>

    <resource>
      <Questionnaire>
        <!-- Questionnaire contents -->
      </Questionnaire>

      <ValueSet>
        <!-- Valueset contents -->
      </ValueSet>

    </resource>
  </parameter>

or, in JSON: 

 "parameter": [
    {
      "name": "questionnaire",

      "name": "valueset",

      "resource": {
        "resourceType": "Questionnaire",
        // Questionnaire contents 

        "resourceType": "ValueSet",
        // Valueset contents 

      }
    }
  ]

Other parameters are passed by reference. For example, $populate the ChargeItemDefinition.$apply operation takes a set two parameters of references to other resources that should be used type Reference - one to pre-populate the questionnaire. These are passed by reference, chargeItem and the other to the account. The type of the parameter parameters is Reference(Any) Reference(Charge) - a reference to any kind and Reference(Account) , respectively. The expectation is that the server performing the operation will resolve those references as part of resource. the operation execution. In a parameters resource, it the chargeItem parameter would be represented like this: 

  <parameter>
    <name value="content"/>

    <name value="chargeItem"/>

    <valueReference>
      <reference value="Patient/123">
      </Questionnaire>

      <reference value="ChargeItem/123"/>

    </valueReference>
  </parameter>

or, in JSON: 

 "parameter": [
    {
      "name": "questionnaire",

      "name": "chargeItem",

      "valueReference" : {
        "reference" : "Patient/123"

        "reference" : "ChargeItem/123"

      }
    }
  ]

Some operations can take either form; in that case, two distinct parameters must be defined, defined: one for a resource as a direct parameter, and one for a reference.

5.4.3.7

5.4.3.8 Renaming OperationDefinition.name

It is possible for two different organizations to create different operation definitions with the same name or, perhaps more likely, to define equivalent operations that have the same name but incompatible approaches in their parameter lists.

It is also possible, though unlikely, that a server will be required to support both of these operations. If this is the case, the server is able to do this by giving one of them a new name and referring to it by definition in the capability statement. To illustrate this, assume that two different organizations, "orgA" and "orgB", both define an operation called "dothis", and the definitions are incompatible. OrgA publishes its operation definition at http://orga.com/fhir/dothis.xml, and OrgB publishes its operation at http://fhir.orgb.com/meta/OperationDefinition/dothis. The server is able to implement both. Its capability statement will say: 

<CapabilityStatement xmlns="http://hl7.org/fhir">
  <!-- snip -->
  <rest>
    <!-- snip -->
    <operation>
      <name value="dothis"/>
      <definition>
        <reference value="http://orga.com/fhir/dothis.xml"/>
      </definition>
    </operation>
    <operation>
      <name value="dothis2"/>
      <definition>
        <reference value="http://fhir.orgb.com/meta/OperationDefinition/dothis"/>
      </definition>
    </operation>
    <!-- snip -->
  </rest>
  <!-- snip -->
</CapabilityStatement>

If a general purpose cross server client is looking for the implementation of the http://fhir.orgb.com/meta/OperationDefinition/dothis operation and wants to be robust against this name clash problem, instead of simply executing the $dothis operation, it can look at the server's CapabilityStatement for the underlying definition URI and then execute the name given in the capability statement.

5.4.3.8

5.4.3.9 Determining System Compatibility

A client can determine the compatibility of the server by processing its capability statement and ensuring that the server implements the specific operation definitions and parameters required by the client. The client can then report a useful error to the user rather than allowing mystifying operational errors to occur.

However, there are fundamental limitations to this approach because there are many aspects of these operations that are not (or cannot be) defined in a formal fashion using OperationDefinition, for example, co-occurrence constraints among parameters.

In the same sense, a 3rd party tool can examine a server's CapabilityStatement and a client's definition of an acceptable server to determine whether those two system are interoperable or not.

5.4.3.9

5.4.3.10 Dynamically Generating Forms

Finally, it is possible to generate user interface forms automatically from the OperationDefinition. The documentation in the OperationDefinition.description and OperationDefinition.parameter.documentation should be sufficient to allow moderately technical users to guess at the correct content of the form. For this reason, highly technical documentation should go in OperationDefinition.comment .

It is anticipated that this would be used to automate development processes, rather than to generate end-user forms: such users will usually need more support than can be offered in a generated form.

5.4.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
base TU reference Marks this as a profile of the base OperationDefinition.base
( OperationDefinition )
code TU token Name used to invoke the operation OperationDefinition.code
context TU token A use context assigned to the operation definition (OperationDefinition.useContext.value as CodeableConcept)
context-quantity TU quantity A quantity- or range-valued use context assigned to the operation definition (OperationDefinition.useContext.value as Quantity) | (OperationDefinition.useContext.value as Range)
context-type TU token A type of use context assigned to the operation definition OperationDefinition.useContext.code
context-type-quantity TU composite A use context type and quantity- or range-based value assigned to the operation definition On OperationDefinition.useContext:
  context-type: code
  context-quantity: value.as(Quantity) | value.as(Range)
context-type-value TU composite A use context type and value assigned to the operation definition On OperationDefinition.useContext:
  context-type: code
  context: value.as(CodeableConcept)
date TU date The operation definition publication date OperationDefinition.date
description TU string The description of the operation definition OperationDefinition.description
input-profile TU reference Validation information for in parameters OperationDefinition.inputProfile
( StructureDefinition )
instance TU token Invoke on an instance? OperationDefinition.instance
jurisdiction TU token Intended jurisdiction for the operation definition OperationDefinition.jurisdiction
kind TU token operation | query OperationDefinition.kind
name TU string Computationally friendly name of the operation definition OperationDefinition.name
output-profile TU reference Validation information for out parameters OperationDefinition.outputProfile
( StructureDefinition )
publisher TU string Name of the publisher of the operation definition OperationDefinition.publisher
status TU token The current status of the operation definition OperationDefinition.status
system TU token Invoke at the system level? OperationDefinition.system
title TU string The human-friendly name of the operation definition OperationDefinition.title
type TU token Invoke at the type level? OperationDefinition.type
url TU uri The uri that identifies the operation definition OperationDefinition.url
version TU token The business version of the operation definition OperationDefinition.version