Release 4 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ) in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see times).
See the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Operation-composition-document

Example OperationDefinition/Composition-document (Narrative)

Maturity Level : N/A
Responsible Owner: Structured Documents Work Group Standards Status : Informative Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson

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

Generate a Document OPERATION: Generate a Document The official URL for this operation definition is: http://hl7.org/fhir/OperationDefinition/Composition-document A client can ask a server to generate a fully bundled document from a composition resource. The server takes the composition resource, locates all the referenced resources and other additional resources as configured or requested and either returns a full document bundle, or returns an error.

Note that since this is a search operation, the document bundle is wrapped inside the search bundle. If some of the resources are located on other servers, it is at the discretion of the server whether to retrieve them or return an error. If the correct version of formal definition for the document that would be generated already exists, then the server can return operation as an OperationDefinition on Composition. See the existing one. Operation documentation

Generated Narrative: OperationDefinition Composition-document URL: [base]/Composition/$document

URL: [base]/Composition/[id]/$document

Parameters

IN id 0..1 uri
Use Name Cardinality Scope Type Cardinality Binding Type Documentation Binding Identifies the composition to use. This can either be a simple id, which identifies a composition, or it can be a full URL, which identifies a composition on another server. Notes: GET [base]/Composition/[id]/$document is identical in meaning to GET [base]/Composition/$document?id=[id] the id parameter SHALL NOT be used if the operation is requested on a particular composition (e.g. GET [base]/Composition/[id]/$document?id=[id] is not allowed) Servers are not required to support generating documents on Compositions located on another server Documentation
IN persist 0..1 boolean

Whether to store the document at the bundle end-point (/Bundle) or not once it is generated. Value = true or false (default is for the server to decide). If the document is stored, it's its location can be inferred from the Bundle.id, but it SHOULD be provided explicitly in the HTTP Location header in the response

IN graph 0..1 uri

Canonical reference to a GraphDefinition. If a URL is provided, it is the canonical reference to a GraphDefinition that it controls what resources are to be added to the bundle when building the document. The GraphDefinition can also specify profiles that apply to the various resources

OUT return 1..1 Bundle

Note: The bundle containing the composition and resources associated with it. See FHIR Documents for information on resources that may be included in the bundle.

Notes:

  • The server implementing the operation SHOULD determine a 'high-level water-mark' for the document security tags ( Bundle.meta.security )) as a whole, based on an analysis of the resources contained within the document
  • this operation definition does not resolve the question how document signatures are created. This is an open issue during the period of trial use, and feedback is requested regarding this question

 

 

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.