Release 5 R6 Ballot (2nd Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot2: Release 6 Ballot (2nd Draft) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions

Example OperationDefinition/DocumentReference-generate (Narrative)

Orders and Observations Work Group Maturity Level : N/A Standards Status : Informative Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson

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

Note that this is the formal definition for the generate operation as an OperationDefinition on DocumentReference. See the Operation documentation

Generated Narrative: OperationDefinition DocumentReference-generate

URL: [base]/DocumentReference/$generate

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN url 1..1 uri

The URL to the source document. This may be a general URL or a Binary or a Composition or a Bundle.

IN persist 0..1 boolean

Whether to store the document at the document end-point (/Document) or not, once it is generated (default is for the server to decide).

OUT return 1..1 Bundle

The bundle type is "searchset"containing DocumentReference resource and may include a Binary. If the input url refers to another server, it is at the discretion of the server whether to retrieve it or return an error.

The server either returns a search result containing a single document reference, or it returns an error. If the URI refers to another server, it is at the discretion of the server whether to retrieve it or return an error.

 

 

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.