POST /convert/v1/cdatopdf
This operation converts a CDA document into a PDF document.
The input for this operation is a single CDA document. Supported CDA formats/versions are:
The output is a formatted PDF document suitable for human review.
If the input data is invalid (such as improperly-formatted XML), the PDF will not be created and a “bad request” response returned.
However, in many cases the Convert service can continue processing even when there are issues with the input data, such as missing fields or unexpected data types. In such cases, invalid data will simply be omitted from the resulting PDF.
The input for the CDA to FHIR conversion is XML and the output is PDF, so be sure to specify the following request headers:
content-type: application/xml
accept: application/pdf
CDA documents and the formatted PDFs are verbose, so this just shows a small sample to illustrate how the data is structured. For a more complete example, try out the API in the Developer Portal Sandbox.
For example, a patient
node in the CDA XML:
<patient classCode="PSN" determinerCode="INSTANCE">
<name>
<given>John</given>
<family>Smith</family>
</name>
...
</patient>
would result in a PDF similar to: