CDA Export
The CDA Export configuration category includes the following configurable options:
Store Generated Bundle
Store Generated Composition
Store Generated CDA Document as Binary
Store Generated CDA Document as DocumentReference
|
Store Generated Bundle |
|
|
BOOLEAN | |
Stores the Bundle resource that is generated as part of the CDA export process in the repository. This option has no effect if the document is generated based on a pre-existing Bundle. NOTE: This property is not used by the Camel module. Please see the Sample CDA Export Route Configuration section for a CDA Export route that persists a generated Bundle. | |
|
|
false
|
|
|
|
Store Generated Composition |
|
|
BOOLEAN | |
Stores the Composition resource that is generated as part of the CDA export process in the repository. This option has no effect if the document is generated based on a pre-existing Composition or Bundle. NOTE: This property is not used by the Camel module. Please see the Sample CDA Export Route Configuration section for a CDA Export route that persists a generated Composition. | |
|
|
false
|
|
|
|
Store Generated CDA Document as Binary |
|
|
BOOLEAN | |
Stores the generated CDA document as a Binary resource. NOTE: This property is not used by the Camel module. Please see the Sample CDA Export Route Configuration section for a CDA Export route that stores a generated CDA Document as a Binary resource. | |
|
|
false
|
|
|
|
Store Generated CDA Document as DocumentReference |
|
|
BOOLEAN | |
Stores the generated CDA document as a DocumentReference resource. NOTE: This property is not used by the Camel module. Please see the Sample CDA Export Route Configuration section for a CDA Export route that stores a generated CDA Document as a DocumentReference resource. | |
|
|
false
|
|
|
You are about to leave the Smile Digital Health documentation and navigate to the Open Source HAPI-FHIR Documentation.