This
page
is
part
of
the
FHIR
Specification
(v0.0.82:
(v1.0.2:
DSTU
1).
2).
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
This is the narrative for the resource. See also the XML or JSON format.
OPERATION: Generate a 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 the document that would be generated already exists, then the server can return the existing one.
URL:
[base]/Composition/$Generate
a
Document
[base]/Composition/$document
Parameters
| Use | Name | Cardinality | Type | Binding | Documentation |
| IN | persist | 0..1 | boolean |
Whether
to
store
the
document
at
the
|
Certificate
URL
to
use
to
sign
Note:
this
operation
definition
does
not
resolve
the
question
how
document
with.
The
certificate
should
be
associated
with
one
of
signatures
are
created.
This
is
an
open
issue
during
the
attestors
IN
pword
0..1
string
Password
for
private
key
if
certificate
requires
one
period
of
trial
use,
and
the
server
doesn't
know
it
by
some
other
means.
Putting
the
password
in
the
URL
has
obvious
security
implications
to
consider.
An
alternative
feedback
is
for
the
client
to
sign
the
document
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.