Release 4B R5 Final QA

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0-draft-final: Final QA Preview for R5 - STU see ballot notes ). 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

Operation-structuredefinition-snapshot

Example OperationDefinition/StructureDefinition-snapshot (Narrative)

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any defined compartments

This is the narrative for the resource. See also the XML , JSON or Turtle format.

Snapshot OPERATION: Snapshot The official URL for

Note that this operation definition is: http://hl7.org/fhir/OperationDefinition/StructureDefinition-snapshot Generates a StructureDefinition instance with a snapshot, based on a differential in a specified StructureDefinition . If the operation is not called at the instance level, either formal definition or url 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with for the parameter of their choice. If called at snapshot operation as an OperationDefinition on StructureDefinition. See the instance level, these parameters will be ignored. Operation documentation

URL: [base]/StructureDefinition/$snapshot

URL: [base]/StructureDefinition/[id]/$snapshot

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN definition type 0..1 StructureDefinition

The StructureDefinition is provided directly as part of the request. Servers may choose not to accept profiles in this fashion

IN url type 0..1 string
( token )

The StructureDefinition's canonical URL (i.e. 'StructureDefinition.url'). The server must know the structure definition, or be able to retrieve it from other known repositories.

OUT return 1..1 StructureDefinition

The structure definition with a snapshot

 

 

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.