Smile CDR v2023.02.PRE
On this page:

28.0Da Vinci Clinical Data Exchange (CDex)

 

This page describes Smile CDR's support of various features as defined in the Da Vinci Clinical Data Exchange (CDex) implementation guide.

The current published version of this implementation guide can be found at the following URL:

  • https://hl7.org/fhir/us/davinci-cdex/index.html

Operation Submit Attachment --Experimental--

Smile CDR supports the $submit-attachment operation as defined in version 1.1.0 - STU1.1 US of the CDex implementation guide.

  • https://hl7.org/fhir/us/davinci-cdex/STU1.1/OperationDefinition-submit-attachment.html

Mapping TrackingId to Task.Identifier

Note that input parameter TrackingId is of type string; however, it corresponds to Task.identifier of type Identifier. When evaluating $submit-attachment requests, Smile CDR effectively treats the TrackingId input parameter as a token search parameter. Specifically, values conforming to the following formats are supported:

Only Identifier.value is provided:

{
   "name": "TrackingId",
   "valueString": "1234567890"
},

Alternatively:

{
   "name": "TrackingId",
   "valueString": "|1234567890"
},

Both Identifier.system and Identifier.value are provided:

{
   "name": "TrackingId",
   "valueString": "http://example.org/fhir/request-attachment-identifier|1234567890"
},

Note that at a minimum a value corresponding to Task.identifier.value must be provided. A system alone is insufficient when mapping the TrackingId to a Task in the repository.

Limitations and Exceptions

  • Presently, only solicited attachments are supported (as described at the links below). A $submit-attachment request must reference a Task, which is known to the server, which in turn references the target Claim.
    • https://hl7.org/fhir/us/davinci-cdex/STU1.1/solicited-unsolicited-attachments.html#solicited-attachments
    • https://hl7.org/fhir/us/davinci-cdex/STU1.1/requesting-attachments.html#technical-workflow
  • Presently, the Final input parameter is not supported; it's value is always assumed to be true regardless of it being present in the request.